Specifications

3-16 Module Installation
Chapter 3 - Installation
LAN
LAN LAN
LAN Wiring Structures
Wiring StructuresWiring Structures
Wiring Structures
The LAN wiring architecture used for connecting Telenium
IP
Modules to form a Telenium
IP
Zone is dependent upon several factors including:
 Shared or Telenium
IP
-only LAN infrastructure
 External VoIP calling requirements
 New or existing voice and/or data installation
 Remote LAN power or local AC power for IP Keysets
For a shared environment, the desktop PC is connected to the IP LCD 2P Keyset, which is
connected with a standard LAN cable to an RJ-45 LAN jack. The LAN jack is wired to a
hub, which is connected to the MFIM and other IP KTS Modules and IP Keysets. This last
connection can be through a connection to the same hub or by an indirect connection
through multiple hubs.
For a new installation, or where LAN power to the IP Keyset is required, the SHUB8 can
be employed for the corporate LAN. For existing installations, it will be necessary to
replace existing hubs in a shared environment in order to provide remote power to the IP
Keysets.
In the shared environment, both data and voice will have access to the WAN, which also
permits external VoIP calling. In the non-shared LAN environment, the system must be
connected to the WAN to support external VoIP connections.
Due to the advantages of the shared environment, support for remote LAN power, and
external VoIP calling, the SHUB8, which is a standard switching hub, should be employed.
The recommended structure, called a "hierarchal" wiring, employs all "straight" LAN
cables (MDI to MDIX) and is shown in
Figure 3-13. Additional SHUB8 Modules are
connected using the UPLINK port to the switched ports of the primary SHUB8. A sufficient
number of SHUB8 modules are connected to provide the total number of ports required.
Each Module, IP Keyset, and IP DSS requires a single port and the MFIM will require two
ports.