Avaya Business Communication Manager Interoperability with Communication Server 1000 User's Manual
Contents
1. Network Routing Server NRS Private Dial Plan CDP dial plan Supported UDP dial plan Supported e BCM private dial plan can only be configured for either CDP or UDP not both simultaneously MCDN Networking Applications The following are typical applications that can be Supported supported using a combination of MCDN features and information contained in SIP messages e Centralized Voicemail e Central Attendant Basic e Centralized Trunking Features Private Name Number Supported Trunk Anti Tromboning TAT Supported Refer to Table 6 See note Notes e BCM 4 0 and BCMSOR2 have enhanced the BCM TAT implementation to enable TAT support on CTI based calls eg calls using BCM AutoAttendant functionality Trunk Route Optimization e Before Answer TRO BA Supported e Call Modification TRO CM Not Supported Refer to Table 6 Network Call Redirection Supported Message Waiting Indication MWI Supported Message Indicator Key MIK Supported Message Cancel Key MCK Supported Notes e 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 Fax detection during SIP call renegotiation to T 38 Supported using UDP transport VERSION 5 0 NOVEMBER 2006 PAGE 18 OF 20 BCM INTEROPERABILITY WITH COMMUNICATION SERVER 1000 AND MERIDIAN 1 WITH IP TRUNK Table 10 Known SIP Interop Issues BCM and Communication Server 1000 R2. calls in Element Manager from BCM to a Virtual Trunk route that has ESNS signaling enabled e Succession 4 0 3 0 IP Peer H 323 Gateways insert a default NCOS value in the ESN5 prefix for calls received from BCM without the extended ESN5 information element VPNI IE for Bandwidth Management Zone BCM BCM signaling Not Supported Not Supported SRG SRG Partially Partially Supported Supported VERSION 5 0 NOVEMBER 2006 PAGE 12 OF 20 BCM INTEROPERABILITY WITH COMMUNICATION SERVER 1000 AND MERIDIAN I WITH IP TRUNK Known Issues with Description BCM 3 7 and BCM 4 0 and CS1000 4 5 and 4 0 BCMSORI1 BCM50R2 Notes e Communication Server 4 5 4 0 provides an optional MCDN Information Element that signals the Virtual Private Network Identifier and the Bandwidth Management Zone over IP Peer Virtual Trunk routes to allow Call Servers to coordinate codec selection appropriately for different Internet Telephones depending on network location This VPNI IE is not generated or used on BCM systems In SRG mode this VPNI IE is generated so that the Communication Server 4 5 4 0 can determine which zone calls are originated or destined for bandwidth management However SRG does not process any incoming VPNI IE and does not provide bandwidth management capabilities Network Routing Server Functionality NRS Notes e BCM uses the Registration Time To Live TTL value in the BCM Gatekeeper settings to establish the point at which re registration
3. gt BUSINESS MADE SIMPLE Business Communication Manager Interoperability with Communication Server 1000 and Meridian 1 IP Trunk Document issue 5 0 Document status Standard Product release BCM 4 0 Date November 2006 Version 1 0 2 0 3 0 4 0 5 0 Table 1 Table 2 Table 3 Table 4 Table 5 Table 6 Table 7 Table 8 Table 9 Table 10 Date Dec 2003 June 2004 March 2005 May 2005 Nov 2006 Revision History Reason for Release Introduction of BCM 3 5 and Communication Server 1000RIs 3 0 Introduction of BCM 3 6 Update to include Communication Server 1000 Rls 4 0 Update to include BCM 3 7 and BCM50 Update to include BCM 4 0 BCMS50R2 Communication Server 1000 Rls 4 5 List of Tables H 323 Interoperability by Software Release SIP Interoperability by Software Release Interoperability Patch Reference Table Supported H 323 Functionality BCM and Communication Server 1000 Release 4 0 and 4 5 Supported H 323 Functionality between BCM and Meridian 1 with IP Trunk 3 0x Known H 323 Interop Issues Between BCM and CS1000 Release 4 5 and 4 0 Known H 323 Interop Issues between BCM and Meridian 1 with IP Trunk 3 0x Succession and Meridian 1 with IP Trunk Codec Configuration Rules Supported SIP Functionality BCM and Communication Server 1000 Release 4 0 and 4 5 Known SIP Interop Issues BCM and Communication Server 1000 Release 4 0 and 4 5 Table 1 and Table 2 represent the H 323 and SIP trunk inte
4. optional Not Supported MCDN Information Element that signals the Virtual Private Network Identifier and the Bandwidth SRG Management Zone over IP Peer Virtual Trunk routes Partially to allow Call Servers to coordinate codec selection Supported appropriately for different Internet Telephones depending on network location This VPNI IE is not generated or used on BCM systems In SRG mode this VPNI IE is generated so that the Communication Server 4 5 4 0 can determine which zone calls are originated or destined for bandwidth management However SRG does not process any incoming VPNI IE and does not provide bandwidth management capabilities VERSION 5 0 NOVEMBER 2006 PAGE 20 OF 20
5. 01 will not be optimized by TAT because the Called and Calling numbers do not match on the two sides of the tromboned call e In a private IP telephony voice network with mixed CDP Steering Codes and UDP Location Codes incoming calls to BCM that are forwarded using a different type of number in a trombone connection back to Communication Server 4 5 4 0 or IP Trunk 3 01 will not be optimized by TAT because the Called and Calling numbers do not match on the two sides of the tromboned call e BCM sets up a direct media path between the two ends of the tromboned connection but this can still result in multiple transcoding and voice quality degradation due to media path loopback via Communication Server 4 5 4 0 Voice Gateway Media Cards or IP Trunks Notes e Communication Server 4 5 4 0 and Meridian 1 with IP Trunk use ESN5 signaling with MCDN to signal the Network Class of Service NCOS of the originating terminal among Succession 4 0 3 0 nodes in order to control access to PSTN trunk facilities at a remote Call Server and Media Gateway e The Nortel Networks Interoperability format introduced in Succession 2 0 supports an extended ESN5 Information Element in the Non standard data of the H 225 Call Setup message but BCM does not send optional ESN5 Information Element in the H 225 Call Setup message e If ESNS signaling is enabled on a Succession 4 0 3 0 IP Peer virtual trunk route you must configure an appropriate default NCOS value for incoming
6. 8 Fax detection amp renegotiation O Supported Notes e Note that BCM allows the use of V 34 based faxed machines although it rejects V 34 negotiation attempts while CS1000 does not MCDN Networking TRO BA Before Answer O Lee Pre Succession 3 0 feature occ la New Succession 3 0 feature Supported Notes eTRO CM works as follows in a mixed Succession 4 5 4 0 and BCM SIP environment o When BCM is a transferring party node B not an originating or terminating node A or C TRO CM works and both the Media and Signaling are direct A to C o If BCM is originating or terminating node A or C TRO CM does not work the Media is direct A to C but a tandem Signaling path is maintained A to B to C o TRO CM does not work in Succession 4 0 3 0 for Blind Transfer calls to a station that is Call Forward No Answer The transferring user must remain on the transferred call until it is answered to ensure that TRO CM will optimize the call when the Call Transfer is completed o TRO BA and TRO CM depend on implementation of a perfectly coordinated CDP and or uniform UDP dialing plan across all nodes in the private IP Telephony network o All Succession 4 5 4 0 routes must be configured to enable automatic insertion of UDP access codes INAC YES in order for UDP Location Codes to work with TRO All nodes must send TRO BA Offer and TRO CM Invoke messages with the correct NPI TON values for the destination telephone num
7. M OO WE eee 30109 BCM Patch References Patch Name B1 BCM370 175 FEPS FEPS Generally Available 37 222 0 33 BCM050 108 FEPS FEPS Generally Available 40 330 0 33 Refer to the BCM Software Downloads web site at www nortel com by following Support and Training Technical Support Software Downloads for latest BCM patch information BCM INTEROPERABILITY WITH COMMUNICATION SERVER 1000 AND MERIDIAN I WITH IP TRUNK Table 4 Supported H 323 Functionality BCM and Communication Server 1000 Release 4 0 and 4 5 Supported Description BCM 3 7 BCM 4 0 Functionality and and with CS1000 4 0 and BCM50R1 BCM50R2 4 5 Network Routing e Registers as an H 323 Endpoint e Gatekeeper Resolved Programmable Programmable Succession 4 0 4 5 H 225 Call Signaling using Nortel Interoperability Supported Supported IP Peer Gateway format Signaling Server H 245 Media Channel Signaling H 323 Basic Call Call connection with Calling Line ID Supported Supported Private Dial Plan CDP dial plan Supported Supported UDP dial plan Supported Supported e BCM private dial plan can only be configured for either CDP or UDP not both simultaneously MCDN Networking Applications The following are typical applications that can be Supported Supported supported using MCDN features e Centralized Voicemail e Central Attendant Basic e Centralized Trunking MCDN Features Refer to Table 6 Se
8. M PLAN PRIVATE ABBREVIATED CDP DCH 10 OMSG REL COMP REF 00008021 CH 84 0 0 0 TOD 17 18 46 CAUSE SWED EQIP CONGESTION DIAG 171 For incoming calls from BCM that terminate to a non ISDN PRI trunk CH 10 IMSG SETUP REF 00008001 CH 83 0 0 0 TOD 18 33 18 CALLING 1405 NUM PLAN PRIVATE ABBREVIATED CDP CALLED 5010 NUM PLAN PRIVATE ABBREVIATED CDP DCH 10 OMSG REL COMP REF 00008001 CH 83 0 0 0 TOD 18 33 18 CAUSE NO CHANNEL CIRC AVAIL DIAG 095 Succession to BCM Calls from S Communication Server 4 5 4 0 to BCM with a codec mismatch ring the terminating telephone until the call is answered then BCM disconnects the call Communication Server 4 5 4 0 Overlay 96 D Channel monitor shows the following diagnostic messages DCH 10 IMSG CONNECT REF 000001A1 CH 84 DCH 10 OMSG CONN ACK REF 000001A1 CH 84 DCH 10 IMSG DISC REF 000001A1 CH 84 CAUSE INCOMPATIBLE DEST DCH 10 OMSG RELEASE REF 000001A1 CH 84 DCH 10 IMSG REL EF 000001A1 CH 84 VERSION 5 0 NOVEMBER 2006 PAGE 17 OF 20 BCM INTEROPERABILITY WITH COMMUNICATION SERVER 1000 AND MERIDIAN I WITH IP TRUNK Table 9 Supported SIP Functionality BCM and Communication Server 1000 Release 4 0 and 4 5 Supported SIP Description BCM 4 0 Functionality with and Communication BCM50R2 Server 1000 Release 4 0 and 4 5
9. and or IP Trunk 3 01 call servers e In the absence of the extended TAT IE in H 225 messages received from BCM Communication Server 4 5 4 0 and IP Trunk 3 01 D Channel H 323 Gateway falls back to comparing the Called and Calling numbers on the outgoing and incoming side of the tromboned trunk connection e If the Called and Calling numbers on the two sides of the call don t match then the TAT Invoke message from BCM is discarded regardless of matching Call Reference VERSION 5 0 NOVEMBER 2006 PAGE 14 OF 20 BCM INTEROPERABILITY WITH COMMUNICATION SERVER 1000 AND MERIDIAN I WITH IP TRUNK Known Issues with Description BCM 3 7 BCM 4 0 Meridian 1 with and and IP Trunk 3 0x BCM50R1 BCM50R2 This prevents wrong connections that can occur due to false TAT optimization when Call References assigned by different Gateways across the network randomly matched for unrelated calls e Incoming calls to BCM that are answered and transferred within the BCM before being routed in a trombone connection back to Communication Server 4 5 4 0 or IP Trunk 3 01 will not be optimized by TAT because the Called and Calling numbers do not match on the two sides of the tromboned call eIn a private IP telephony voice network with mixed CDP Steering Codes and UDP Location Codes incoming calls to BCM that are forwarded using a different type of number in a trombone connection back to Communication Server 4 5 4 0 or IP Trunk 3 01 will not be optimized by TAT because t
10. ber Trunk Anti Tromboning TAT Supported Pre Succession 3 0 implementation VERSION 5 0 NOVEMBER 2006 PAGE 19 OF 20 BCM INTEROPERABILITY WITH COMMUNICATION SERVER 1000 AND MERIDIAN I WITH IP TRUNK Known SIP Issues Description BCM 4 0 with CS 1000 and Release 4 0 and 4 5 BCM50R2 MCDN Networking Trunk Anti Tromboning TAT ee el cont d Succession 3 0 enhancement Interop with ESN5 Signaling Notes Not Supported e Communication Server 4 5 4 0 and Meridian 1 with IP Trunk use ESN5 signaling with MCDN to signal the Network Class of Service NCOS of the originating terminal among Succession 4 5 4 0 nodes in order to control access to PSTN trunk facilities at a remote Call Server and Media Gateway eThe Nortel Networks Interoperability format introduced in Succession 2 0 supports an extended ESN5 Information Element in the Non standard data of the H 225 Call Setup message but BCM does not send optional ESN5 Information Element in the H 225 Call Setup message e If ESNS signaling is enabled on a Succession 4 5 4 0 IP Peer virtual trunk route you must configure an appropriate default NCOS value for incoming calls in Element Manager from BCM to a Virtual Trunk route that has ESN5 signaling enabled e Succession 4 5 4 0 IP Peer SIP Gateways insert a default NCOS value in the ESNS5 prefix for calls received from BCM without the extended ESNS5S information element Notes BCM e Communication Server 4 5 4 0 provides an
11. e node e BCM supports codec negotiation with IP Trunk 3 01 using Fast Start signaling elements and H 245 Media Path signaling e BCM side Node B initiates H 245 Media Channel Signaling for direct media path between IP Trunk 3 01 nodes A and C that have a tandem IP Trunk call signaling connection via the BCM Node B e 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 IP Trunk call signaling connection via IP Trunk 3 01 Node B IP Trunk 3 01 Node H 225 Call Signaling using Supported Supported Not Registered with e Direct routed to standard TCP port NRS e Local BCM and IP Trunk dialing plan to resolve the destination telephone number e ITG ISDN IP Trunk format MCDN NCAS using e Direct routed to a proprietary TCP port e Local BCM and IP Trunk dialing plan to resolve the destination telephone number Notes e The BCM should be configured to use CSE as the Gateway Protocol in the BCM Remote Gateway Table The IPT should be configured to use CSE mode in the dial plan table e BCM supports the Redirect FACILITY message that IP Trunk 3 01 Node Leader uses to redirect all incoming calls to a reserved trunk resource in the node e BCM supports codec negotiation with IP Trunk 3 01 using Fast Start signaling elements and H 245 Media Path signaling e BCM side Node B initiates H 245 Media Channel Signaling for direct media path be
12. e note Notes e BCM 4 0 and BCMSOR2 have enhanced the BCM TAT implementation to enable TAT support on CTI based calls eg calls using BCM AutoAttendant functionality Trunk Route Optimization e Before Answer TRO BA Supported Supported e Call Modification TRO CM Not Supported Not Supported Refer to Table 6 Notes e 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 Fax detection during H 323 call renegotiation to T 38 Supported Supported Refer to Table 6 VERSION 5 0 NOVEMBER 2006 PAGE 6 OF 20 BCM INTEROPERABILITY WITH COMMUNICATION SERVER 1000 AND MERIDIAN I WITH IP TRUNK Supported Description BCM 3 7 BCM 4 0 Functionality and and with CS1000 4 0 and BCM50R1 BCM50R2 4 5 Overlap Signaling Ability for the CS1000 to be configured to use Supported Supported Overlap Signaling on call setup Notes e The BCM will interoperate with the CS1000 when the CS1000 has been configured to use Overlap Signaling However the BCM rejects the Overlap Signaling call setup attempts and requires Enbloc Signaling to be used H 245 Tunneling H 245 messages use existing H 225 connection Supported Supported instead of new TCP connection Notes e By default CS1000 4 0 will attempt to use H 245 tunneling If the BCM is configured for its default setting H 245 Tunneling Off then it negotiates with the CS1000 to t
13. elease 4 0 and 4 5 Known SIP Issues Description BCM 4 0 with CS 1000 and Release 4 0 and 4 5 BCMS50R2 SIP Transport eThe BCM default is UDP transport Although the Element Manager interface Protocol displays a selection for TCP this functionality is not currently supported e The Communication Server 1000 Rls 4 5 4 0 default is TCP Tandeming between e VAD must be enabled on all sites and codec and payload settings configured per SIP and H 323 Nortel recommendation to be able to support tandeming between a SIP and H 323 trunk on BCM Note that this requirement is also valid for MCS5100 Rls 3 5 and Rls 3 0 interoperability e When BCM is tandeming between SIP and H 323 IP trunks and TAT is attempted the TAT attempt will fail Note that this does not impact the call the call will remain stable with direct media connection between the two endpoints but will use all of the original signaling resources for the duration of the call Support for Advertised Codec Payload Configuration _ Supported Multiple Codecs Notes Payload Sizes e As per the previous release s of BCM CS1000 and Meridian 1 with IP Trunk for optimum BCM to Communication Server 4 5 4 0 and IP Trunk 3 01 interoperability the codec settings must be coordinated for all SIP H 323 and Unistim endpoints in the network particularly if H 323 tandem call scenarios are anticipated such as blind transfers Payload sizes must match across the network T 38 Fax over IP T 3
14. fferent 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 Private Dial Plan UDP dial plan Supported Supported e BCM private dial plan can only be configured for either CDP or UDP not both simultaneously MCDN Networking Applications The following are typical applications that can be Supported Supported supported using MCDN features e Centralized Voicemail e Central Attendant Basic e Centralized Trunking Features supported Trunk Anti Tromboning TAT Supported Supported Refer to Table 7 See note Notes e BCM 4 0 and BCMSOR2 have enhanced the BCM TAT implementation to enable TAT support on CTI based calls eg calls using BCM AutoAttendant functionality Trunk Route Optimization e Before Answer TRO BA Supported Supported e Call Modification TRO CM Refer to Table 7 Network Call Redirection Supported Message Waiting Indication MWI Supported Using call server RCAP of MWI Station Camp on Supported Barge In Supported Supported ISDN Call Connection Limit ICCL Supported Supported VERSION 5 0 NOVEMBER 2006 PAGE 9 OF 20 BCM INTEROPERABILITY WITH COMMUNICATION SERVER 1000 AND MERIDIAN I WITH IP TRUNK Supported Description BCM 3 7 BCM 4 0 Functionality and and with IP Trunk 3 0x BCM50R1 BCM50R2 T 38 Fax Fax detection during H 323 call and renegotiation to Supported Suppor
15. for interoperation with BCM G 729A Silence suppression VAD is enabled by default Ensure that the VAD setting on IP Trunk matches the Silence suppression setting on BCM G 723 1 Silence suppression or VAD is enabled by default Ensure that the VAD setting on IP Trunk matches the Silence suppression setting on BCM IPT 3 00 G 723 1 VAD is always enabled regardless of VAD setting IPT 3 01 G 723 1 VAD is enabled or disabled according to the VAD setting VAD was previously referred to as Silence Suppression on BCM but was renamed to align with Communication Server 4 5 4 0 terminology Fax Setting T 38 FAX and V 21 FAX tone detection is enabled by default Verify that V 21 FAX tone detection remains enabled for T 38 FAX Group 3 T 38 FAX protocol is wrongly identified as T 30 in OTM 2 1 ITG ISDN IP Trunk Node Properties DSP Profile General tab Don t be misled the FAX protocol is T 38 Codec Mismatch Diagnostics BCM to Succession Calls from BCM to Communication Server 4 5 4 0 with a codec mismatch are released immediately by Communication Server 4 5 4 0 without ringing the terminating telephone and without seizing an outgoing trunk for a tandem routed call Succession 3 0 Overlay 96 D Channel monitor shows the following diagnostic messages For incoming calls from BCM that terminate to a station or an outgoing ISDN PRI DCH 10 IMSG SETUP REF 00008021 CH 84 0 0 0 TOD 17 18 46 CALLING 1405 NUM PLAN PRIVATE ABBREVIATED CDP CALLED 4015 NU
16. he Called and Calling numbers do not match on the two sides of the tromboned call e BCM sets up a direct media path between the two ends of the tromboned connection but this can still result in multiple transcoding and voice quality degradation due to media path loopback via Communication Server 4 5 4 0 Voice Gateway Media Cards or IP Trunks Interop with ESN5 Signaling Not Not Supported Supported Notes e Communication Server 4 5 4 0 and Meridian 1 with IP Trunk use ESN5 signaling with MCDN to signal the Network Class of Service NCOS of the originating terminal among Communication Server 4 5 4 0 nodes in order to control access to PSTN trunk facilities at a remote Call Server and Media Gateway e If BCM sends H 225 Call Setup with ITG ISDN IP Trunk format IP Trunk 3 0x does not recognize BCM as non ESN5 signaling originating endpoint e The IP Trunk 3 0x must be configured with a Gatekeeper resolved Network Numbering e If ESN5 signaling is enabled on a IPT Trunk route or upgraded Succession 1000M you must configure an appropriate default NCOS value on the IP Trunk node for incoming calls from BCM to a Virtual Trunk route that has ESN5 signaling enabled VERSION 5 0 NOVEMBER 2006 PAGE 15 OF 20 Table 8 Succession and Meridian 1with IP Trunk Codec Configuration Rules Payload The following are the default values of the IP Trunk 3 0x e G 711 payload size defaults to 20 ms e G 729A payload size defaults to 20 ms e G 723 1 pay
17. is attempted If no response is received from the primary NRS the BCM will send up to two additional registration requests each 12 seconds apart at which point the alternate NRS registration process is initiated with a total elapsed time 24 seconds longer than the TTL setting e The Communication Server NRS also supports a mechanism to instruct gateways to switch to the Alternate NRS for maintenance purposes Communication Server 4 5 4 0 gateways and IP Trunk 3 01 nodes will re register to the Alternate GK almost immediately while the BCM will treat the condition as a failure and use the Alternate NRS failover procedures identified above VERSION 5 0 NOVEMBER 2006 PAGE 13 OF 20 BCM INTEROPERABILITY WITH COMMUNICATION SERVER 1000 AND MERIDIAN 1 WITH IP TRUNK Table 7 Known H 323 Interop Issues between BCM and Meridian 1 with IP Trunk 3 0x Known Issues with Description BCM 3 7 BCM 4 0 Meridian 1 with and and IP Trunk 3 0x BCM50R1 BCM50R2 Support for Multiple Codecs Notes Payload Sizes e As per the previous release s of BCM CS1000 and Meridian 1 with IP Trunk for optimum BCM to Communication Server 4 5 4 0 and IP Trunk 3 01 interoperability the codec settings must be coordinated for all H 323 and Unistim endpoints in the network particularly if H 323 tandem call scenarios are anticipated such as blind transfers Payload sizes must match across the network e Refer to Table 8 for details on codec configuration rules and diag
18. load size is fixed at 30 ms The BCM payload size is now configurable but does not default to these same values For optimum interoperability of a BCM Communication Server 4 5 4 0 and IP Trunk 3 01 network the following rules should be adhered to e For each BCM SRG and CS 1000 node in the network the codec list including payload size must be identical and the BCM SRG should be provisioned to advertise a list of CODECS i e NOT a single CODEC with the biggest payload BCM50 does not support G 723 1 codecs on calls terminating or originating on TDM sets or circuit switched trunks on the BCM50 but is supported calls with two IP endpoints H 323 to IP set or IP trunk tandem calls Note that the advertised payload size for BCM H 323 negotiation when the BCM endpoint is an IP set is the higher of the payload size assigned to IP Trunk codecs or IP Set codec settings Voice Activity G 711 Silence suppression or Voice Activity Detection VAD is disabled and Detection VAD cannot be enabled G 729A setting on the Communication Server 1000is equivalent to G 729 Silence suppression disabled setting on the BCM i e VAD is disabled G 729AB setting on the Communication Server 1000is equivalent to G 729 Silence suppression enabled setting on the BCM i e VAD is enabled Both devices must be configured with equivalent settings G 723 1 Silence suppression or Voice Activity Detection VAD is disabled and cannot be enabled VAD was previo
19. nostic information T 38 Fax over IP Notes e Note that BCM and M1 with IP Trunk 3 01 allow the use of V 34 based faxed machines although they do reject V 34 negotiation attempts while Communication Server 1000 does not MCDN Networking TRO BA Before Answer Pre Succession 3 0 feature New Succession 3 0 feature Supported Supported Notes e TRO CM feature works as follows in a mixed Meridian 1 with IP Trunk 3 0x and BCM VolP environment e When BCM is a transferring party node B not an originating or terminating node A or C both the Media and Signaling are direct A to C e When BCM is an originating or terminating node A or C the Media and the Signaling path is maintained between the three sites Trunk Anti Tromboning TAT Pre Succession 3 0 implementation Trunk Anti Tromboning TAT BCM 3 7 Supported Succession 3 0 enhancement Supported BCM50 Not directly Supported Notes e BCM50R1 does not support the TAT and NAS enhancement of the Nortel Networks H 323 Interoperability format that was introduced in Communication Server 3 0 and IP Trunk 3 01 to accurately validate the trombone condition by comparing the unique gateway id MAC address or IP address in the extended TAT information element in the non standard data of the H 225 Setup Alerting and Facility messages The following text describes what is necessary for TAT to function between these versions of BCM and the Communication Server 4 5 4 0
20. roperability respectively between various software releases of the Business Communications Manager BCM the Communication Server 1000 and Meridian 1 IP Trunk formerly known as ITG Trunk products Blank cells indicate an unsupported configuration Table 3 provides a summary of the PEPs and BCM Patches that are applicable to interoperability between the products Table 4 and Table 5 provide a list of specific features that are supported between the latest releases of the BCM i e 4 0 BCM50R2 and 3 7 BCM50 with the Communication Server 1000 Rls 4 5 4 0 and Meridian 1 IP Trunk 3 01 releases respectively Similarly Table 6 and Table 7 identify the known issues that exist between the latest BCM releases and the Communication Server 1000 Rls 4 5 and 4 0 and IP Trunk 3 01 releases Business Communications Manager Interoperability with Communication Server 1000 and Meridian 1 with IP Trunk respectively Table 8 provides additional detail into codec configuration rules and diagnostic information Note Note In this document CS1000 4 0 or CS1000 4 5 refers to Communication Server 1000 Release 4 0 or 4 5 respectively Except where otherwise specifically noted in the document the Survivable Remote Gateway SRG interoperability is the same as the corresponding BCM 3 7 BCM 4 0 BCMS50R1 or BCMS50R2 release Table 1 H 323 Interoperability by Software Release BCM3 5 BCM36 SRG 1 0 BCM3 7 BOM gcmao POP Succe
21. ssion 1000 Soora Rls 2 pp Meridian 1 Suprored IP Trunk 3 0 i Meridian 1 or Succession 1000M Supported Supported Supported Supported Supported Supported w IP Trunk 3 01 Succession 3 0 using Signaling Supported Supported Supported Supported Supported Server 2 10 81 Succession 3 0 using Signaling Supported Supported Supported Supported Supported Server 2 11 03 TE ie 4 0 Supported Supported Supported Supported Supported Supported Supported a ne 45 Supported Supported Supported Supported Supported Supported Supported Table 2 SIP Interoperability by Software Release BCM50 Communication Supported Supported Server 1000 RIs 4 0 pp ppo Communication Supported Supported Server 1000 RIs 4 5 PP ppc Table 3 Interoperability Patch Reference Table Meridian 1 or Succession T1 T2 B1 B3 T1 T2 B2 B3 T1 T2 B3 T1 T2 B3 1000M IP Trunk 3 01 Communication Server S1 B1 B3 S1 B2 B3 S1 B3 S1 B3 1000 Ris 4 0 Communication Server S1 B1 B3 S1 B2 B3 S1 B3 S1 B3 1000 RIs 4 5 Succession Patch References Patch ID S1 Refer to Nortel Enterprise Solutions PEP Library http www nortel com espl for Core and Interop DepLists Meridian 1 with IP Trunk Patch References Optional Required to allow V 34 fax machines to revert to G3 operation for T 38 Note This has been fixed in IP Trunk upissue 3 01 52 T2 MPLR17721 Required when MCDN not configured on BC
22. sues with Description BCM 3 7 and BCM 4 0 and CS1000 4 5 and 4 0 BCM50R1 BCM50R2 Notes MCDN Networking e BCM50R1 does not support the TAT and NAS enhancement of the Nortel Networks cont d H 323 Interoperability format that was introduced in Succession 3 0 and IP Trunk 3 01 to accurately validate the trombone condition by comparing the unique gateway id MAC address or IP address in the extended TAT information element in the non standard data of the H 225 Setup Alerting and Facility messages The following text describes what is necessary for TAT to function between these versions of BCM and the Communication Server 4 5 4 0 and or IP Trunk 3 01 call servers e In the absence of the extended TAT IE in H 225 messages received from BCM Communication Server 4 5 4 0 and IP Trunk 3 01 D Channel H 323 Gateway falls back to comparing the Called and Calling numbers on the outgoing and incoming side of the tromboned trunk connection e If the Called and Calling numbers on the two sides of the call don t match then the TAT Invoke message from BCM is discarded regardless of matching Call Reference This prevents wrong connections that can occur due to false TAT optimization when Call References assigned by different Gateways across the network randomly matched for unrelated calls e Incoming calls to BCM that are answered and transferred within the BCM before being routed in a trombone connection back to Communication Server 4 5 4 0 or IP Trunk 3
23. ted T 38 VERSION 5 0 NOVEMBER 2006 PAGE 10 OF 20 BCM INTEROPERABILITY WITH COMMUNICATION SERVER 1000 AND MERIDIAN I WITH IP TRUNK Table 6 Known H 323 Interop Issues Between BCM and CS1000 Release 4 5 and 4 0 CS1000 4 5 and 4 0 BCMS50R1 BCMS50R2 Support for Multiple Codecs Notes Payload Sizes e As per the previous release s of BCM CS1000 and Meridian 1 with IP Trunk for optimum BCM to Communication Server 4 5 4 0 and IP Trunk 3 01 interoperability the codec settings must be coordinated for all H 323 and Unistim endpoints in the network particularly if H 323 tandem call scenarios are anticipated such as blind transfers Payload sizes must match across the network e Refer to Table 8 for details on codec configuration rules and diagnostic information T 38 Fax over IP T 38 Fax detection amp renegotiation Supported Supported Notes e Note that BCM and IP Trunk 3 01 allow the use of V 34 based faxed machines although they do reject V 34 negotiation attempts while CS1000 does not MCDN Networking TRO BA Before Answer Pre Succession 3 0 feature New Succession 3 0 feature Supported Supported Notes eTRO CM works as follows in a mixed Succession 4 0 3 0 and BCM VoIP environment o When BCM is a transferring party node B not an originating or terminating node A or C TRO CM works and both the Media and Signaling are direct A to C o If BCM is originating or terminating node A or C TRO CM does not
24. tween IP Trunk 3 01 nodes A and C that have a tandem IP Trunk call signaling VERSION 5 0 NOVEMBER 2006 PAGE 8 OF 20 BCM INTEROPERABILITY WITH COMMUNICATION SERVER 1000 AND MERIDIAN I WITH IP TRUNK Supported Description BCM 3 7 BCM 4 0 Functionality and and with IP Trunk 3 0x BCM50R1 BCM50R2 IP Trunk 3 01 Node connection via the BCM Node B Not Registered with e IP Trunk 3 01 side Node B never initiates H 245 Media Channel Signaling for direct NRS media path between BCM nodes A and C that have a tandem H 323 Trunk call cont d signaling connection via IP Trunk 3 01 Node B e IPT 3 0x systems require a PEP reference T2 in Table 3 when networked with BCMs that do not have MCDN functionality activated QoS Monitor for Fallback to PSTN Supported Supported Notes e 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 BCMS50R1 BCMS50R2 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 di
25. urn H 245 tunneling off e The BCM data services NAT and Firewall do not support H 323 when H 245 Tunneling is configured VERSION 5 0 NOVEMBER 2006 PAGE 7 OF 20 BCM INTEROPERABILITY WITH COMMUNICATION SERVER 1000 AND MERIDIAN 1 WITH IP TRUNK Table 5 Supported H 323 Functionality between BCM and Meridian 1 with IP Trunk 3 0x Supported Description BCM 3 7 BCM 4 0 Functionality and and with IP Trunk 3 0x BCM50R1 BCM50R2 Network Routing Registration Supported Supported Server NRS e Stand alone or Co resident GK Signaling method to IP Trunk 3 01 nodes registered Supported Supported Note that NRS can with the NRS refer to the NRS on e Gatekeeper Resolved CS1000 Ris 4 5 or 4 0 Alternate NRS Stand alone or Co resident Supported Supported e IP Address received during the registration process Programmable Programmable IP Trunk 3 01 Node H 225 Call Signaling using Supported Supported Registered with e Direct routed to standard UDP port 15000 NRS as e NRS to resolve destination telephone number H323 Endpoint eNortel Networks Interoperability format capability including GK resolved MCDN Non Call Associated Signaling NCAS Notes e The BCM H 323 Gatekeeper Settings tab should have the Gateway Protocol set to CSE e BCM supports the Redirect FACILITY message that IP Trunk 3 01 Node Leader uses to redirect all incoming calls to a reserved trunk resource in th
26. usly referred to as Silence Suppression on BCM but was renamed to align with Communication Server 4 5 4 0 terminology Payload The following are the default values of the IP Trunk 3 0x e G 711 payload size defaults to 10 ms e G 729A payload size defaults to 30 ms e G 723 1 payload size is fixed at 30 ms e G 729A and G 723 1 cannot be selected together for IP Trunk 3 0x The BCM payload size is now configurable but does not default to these same values For optimum interoperability of a BCM Communication Server 4 5 4 0 and IP Trunk 3 01 network the following rules should be adhered to e For each BCM SRG and CS 1000 node in the network the codec list including payload size must be identical and the BCM SRG should be provisioned to advertise a list of CODECS i e NOT a single CODEC with the biggest payload e BCMS5S0 does not support G 723 1 codecs on calls terminating or originating on TDM sets or circuit switched trunks on the BCM50 but is supported calls with two IP endpoints H 323 to IP set or IP trunk tandem calls e Note that the advertised payload size for BCM H 323 negotiation when the BCM endpoint is an IP set is the higher of the payload size assigned to IP Trunk codecs or IP Set codec settings BCM INTEROPERABILITY WITH COMMUNICATION SERVER 1000 AND MERIDIAN I WITH IP TRUNK Voice Activity G 711 Silence suppression or VAD is disabled by default Verify that it remains Detection VAD disabled
27. work the Media is direct A to C but a tandem Signaling path is maintained A to B to C o TRO CM does not work in Succession 4 0 3 0 for Blind Transfer calls to a station that is Call Forward No Answer The transferring user must remain on the transferred call until it is answered to ensure that TRO CM will optimize the call when the Call Transfer is completed o TRO BA and TRO CM depend on implementation of a perfectly coordinated CDP and or uniform UDP dialing plan across all nodes in the private IP Telephony network o All Succession 4 0 3 0 and IP Trunk 3 01 routes must be configured to enable automatic insertion of UDP access codes INAC YES in order for UDP Location Codes to work with TRO All nodes must send TRO BA Offer and TRO CM Invoke messages with the correct NPI TON values for the destination telephone number o In Succession 4 0 3 0 and Meridian 1 with IP Trunk all network translations where TRO is required must point to a Route List Block RLB with an ENTR 0 that contains an IP Peer Virtual Trunk or IP Trunk 3 01 route with idle trunk members o Pre Succession 3 0 implementation Trunk Anti Tromboning TAT BCM 3 7 Supported Succession 3 0 enhancement Supported BCMSORI Not directly Supported See notes Known Issues with Description BCM 3 7 and BCM 4 0 and VERSION 5 0 NOVEMBER 2006 PAGE 11 OF 20 BCM INTEROPERABILITY WITH COMMUNICATION SERVER 1000 AND MERIDIAN I WITH IP TRUNK Known Is
Download Pdf Manuals
Related Search