05.03.2013 Views

Hardware Description and Reference for Avaya ... - Avaya Support

Hardware Description and Reference for Avaya ... - Avaya Support

Hardware Description and Reference for Avaya ... - Avaya Support

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Circuit packs, channel service units, <strong>and</strong> power supplies<br />

channels support the LAPD protocol. However, the TN2185B does not terminate on LAPD<br />

protocol. The S-interface does not support switching of both B channels together as a 128-kbps<br />

wideb<strong>and</strong> channel.<br />

The TN2185B has a maximum range up to 18,000 feet (5486 meters) from the system to the<br />

NT1 device. In an environment with multiple telephones, the B channels are shared only on a<br />

per-call basis. For example, if Channel B2 is <strong>for</strong> data, then the use of this channel by one<br />

telephone excludes the others from having access to Channel B2. When a device<br />

communicates over the D-channel to access B1 or B2, that channel is owned until the call is<br />

taken down. The D-channel is always shared among the terminals. The TN2185B circuit pack<br />

can be used as an alternative to the TN464 circuit pack or the TN2464 circuit pack.<br />

The TN2185B supports the ability to outpulse in-b<strong>and</strong> DTMF signals or end-to-end signaling.<br />

QSIG Call Completion is supported, but QSIG Supplementary Services are not. ISDN-BRI<br />

trunks can be used as inter-PBX tie lines that use the QSIG peer protocol.<br />

TN2198 ISDN-BRI U interface (2-wire, 12 ports)<br />

The TN2198 circuit pack allows connection to the ANSI st<strong>and</strong>ard 2-wire U-Interface. The 2-wire<br />

interface from the TN2198 connects to an NT1 network interface. The 4-wire interface on the<br />

other side of the NT1 can connect to one or two telephones. Unlike the TN2185 circuit pack, the<br />

TN2198 does not provide a trunk-side interface.<br />

The TN2198 contains 12 ports that interface at the ISDN U reference point. For each port,<br />

in<strong>for</strong>mation communicates over two 64-kbps bearer channels called B1 <strong>and</strong> B2. In<strong>for</strong>mation<br />

also communicates over a 16-kbps channel called the dem<strong>and</strong> channel, or D-channel. The<br />

D-channel is used <strong>for</strong> signaling. Channels B1 <strong>and</strong> B2 can be circuit-switched simultaneously.<br />

The D-channel is always packet-switched. The TN2198 requires a packet control circuit pack.<br />

Each port supports one telephone, such as the 500 rotary dial analog telephone <strong>and</strong> 2500<br />

DTMF dial telephones.<br />

The D-channel supports the LAPD protocol <strong>and</strong> is consistent with the CCITT Q.920<br />

recommendations <strong>for</strong> D-channel signaling.<br />

In an environment with multiple telephones, the B channels are shared only on a per-call basis.<br />

For example, if the B2 channel is used <strong>for</strong> data, then the use of B2 by one telephone excludes<br />

the other telephones from having access to the B2 channel. When a device communicates over<br />

the D-channel to access B1 or B2, that channel is owned until the call is taken. The D channel is<br />

always shared among the telephones. The TN2198 interfaces with the TDM bus <strong>and</strong> the packet<br />

bus in the switch backplane <strong>and</strong> terminates with 12 ISDN basic access ports.<br />

The TN2198 has a maximum range of 18,000 feet (5486 meters) from the system to the NT1<br />

device <strong>and</strong> uses st<strong>and</strong>ard protocol ANSI T1.601. The TN2198 has a 160-kbps line rate, that<br />

consists of:<br />

● Two bearer channels at 64 kbps each<br />

● A D-channel at 16 kbps<br />

250 <strong>Hardware</strong> <strong>Description</strong> <strong>and</strong> <strong>Reference</strong> <strong>for</strong> <strong>Avaya</strong> Communication Manager

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!