
BCM INTEROPERABILITY WITH COMMUNICATION SERVER 1000 AND MERIDIAN 1 WITH IP TRUNK
V
ERSION 5.2 JUNE 2007 PAGE 18 OF 20
Table 9: Supported SIP Functionality - BCM and Communication Server 1000 Release 4.0 and 4.5
Supported SIP
Functionality with
Communication
Server 1000 Release
4.0 and 4.5
Description
BCM 4.0
and
BCM50R2
Static Registration
Supported
Network Routing
Server (NRS)
Not Supported
Dynamic Registration
SIP Basic Call Supported
Call connection with Calling Line ID
CDP dial plan
Supported
UDP dial plan
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 a combination of MCDN features and
information contained in SIP messages:
• Centralized Voicemail,
• Central Attendant (Basic),
• Centralized Trunking
Supported
MCDN Networking:
Features:
Supported
Private Name/Number
Supported
(See note)
Trunk Anti-Tromboning (TAT)
* Refer to
Table 6
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:
Supported*
• Before Answer (TRO-BA)
Not Supported*
• Call Modification (TRO-CM)
* Refer to
Table 6
Supported
Network Call Redirection
Supported
Message Waiting Indication (MWI)
Supported
Message Indicator Key (MIK)
Supported
Message Cancel Key (MCK)
Supported
Station Camp-on
Barge-In
Supported
ISDN Call Connection Limit (ICCL)
Supported
Notes:
• On the BCM, these capabilities are enabled via the Nortel Voice Networking
(MCDN) keycode. The BCM Gateway Protocol must be set to “CSE”.
T.38 Fax Supported*
Fax detection during SIP call; renegotiation to T.38
using UDP transport
Comentarios a estos manuales