
62 Chapter 2 System telephony networking overview
NN40020-603NN40020-603
Naming convention
Choose the protocol type for consistency with PRI trunk configuration. The PRI protocol type can
be either User (Slave) or Network (Master). The BRI protocol type can be extended with T-T
(Network). You can connect two BCMs through a BRI link.
S-T refers to a far end which has an S interface (Line in M1 terminology).
T-T refers to a far end which has a T interface (Trunk in M1 terminology).
In both cases, User is the user or slave end of the connection.
Application level differences
BRI Euro Protocol gives you the option to set the protocol type as S-T user or T-T user. The
default setting is S-T user.
The S-T user type provides lines in Pool X mode, which already exist. If the far end interface is
BRI loop choose the S-T user type. The T-T user type provides the lines in BlocX mode, which is
newly introduced. If the far end interface is BRI trunk choose the T-T user type.
Protocol level differences
The following are the protocol level differences in the Kapsch enhancement:
• The S-T user type has the existing functionality which does not support
PROGRESS_MESSAGE.
• The T-T user type supports PROGRESS_MESSAGE.
• After the destination telephone starts to ring in the S-T user, BCM does not send a message to
the network.
• After the tandem occurs in the T-T user, BCM sends a message to the network.
• In the S-T user type, the BRI call is answered prior to the tandem, while in the T-T user type,
the message is sent when the call is tandemed and answered only when the destination
telephone answers the call.
• When the S-T user type is chosen, this can impact the billing in tandem cases. The billing
metrics start once the call is tandemed and not when the destination telephone is answered. But
in the case of the T-T user type, the billing is triggered when the far end answers the call and
not when the call is tandemed.
Kommentare zu diesen Handbüchern