
BCM INTEROPERABILITY WITH COMMUNICATION SERVER 1000 AND MERIDIAN 1 WITH IP TRUNK
V
ERSION 5.2 JUNE 2007 PAGE 9 OF 20
Supported
Functionality
(with IP Trunk 3.0x)
Description
BCM 3.7
and
BCM50R1
BCM 4.0
and
BCM50R2
connection via the BCM (Node B).
• IP Trunk 3.01 side (Node B) never initiates H.245 Media Channel Signaling for direct
media path between BCM nodes (A and C) that have a tandem H.323 Trunk call
signaling connection via IP Trunk 3.01 (Node B).
• IPT 3.0x systems require a PEP (reference
T2 in Table 3) when networked with BCMs
that do not have MCDN functionality activated.
IP Trunk 3.01 Node
Not Registered with
NRS
(cont’d)
Supported Supported
QoS Monitor for Fallback to PSTN
Notes:
• In direct call signaling mode on the BCM, remote gateway table entries in the Element
Manger give the options to enable QoS and set thresholds. For BCM50R1, BCM50R2
and BCM 4.0 systems, in order for any calls to the IP Trunk 3.01 to succeed when
QoS is enabled on a remote gateway entry, a second remote gateway row may be
required. The first remote gateway entry is provisioned with the IPT’s Node IP. If the
Node IP is different from the Card IP, a second remote gateway table row must be
added containing the Card IP of the IPT card. QoS must be enabled for this new entry.
(This additional entry is not required for BCM 3.7.) Note that this requires using
different Destination Digits in the second remote gateway entry, which will in turn
require the routing tables to be modified to include these digits as well.
Call connection w/ Calling Line ID
H.323 Basic Call Supported Supported
CDP dial plan
Supported Supported
UDP dial plan
Supported Supported
Private Dial Plan
• BCM private dial plan can only be configured for either CDP or UDP, not both
simultaneously.
Applications:
The following are typical applications that can be
supported using MCDN features:
• Centralized Voicemail,
• Central Attendant (Basic),
• Centralized Trunking
Supported Supported
MCDN Networking
Features supported:
Private Name/Number
Supported Supported
Trunk Anti-Tromboning (TAT)
* Refer to
Table 7
Supported*
Supported
(See note)
Notes:
• BCM 4.0 and BCM50R2 have enhanced the BCM TAT implementation to enable
TAT support on CTI based calls (eg. calls using BCM AutoAttendant functionality).
Trunk Route Optimization:
• Before Answer (TRO-BA)
• Call Modification (TRO-CM)
* Refer to
Table 7
Supported*
Not Supported*
Supported*
Not Supported*
Network Call Redirection
Supported Supported
Supported Supported
Message Waiting Indication (MWI)
(Using call server RCAP of MWI)
Supported Supported
Message Indicator Key (MIK)
Supported Supported
Message Cancel Key (MCK)
Supported Supported
Station Camp-on
Supported Supported
Barge-In
Supported Supported
ISDN Call Connection Limit (ICCL)
Comentarios a estos manuales