Avaya Business Communication Manager Interoperability User Manual

Business Communication Manager Interoperability with Communication Server 1000 and Meridian 1 IP Trunk

Document issue: 5.2 Document status: Standard Product release: BCM 4.0 / BCM50R2 Date : June 2007

BCM INTEROPERABILITY WITH COMMUNICATION SERVER 1000 AND MERIDIAN 1 WITH IP TRUNK

Revision History

Version

1.0 Dec 2003 Introduction of BCM 3.5 and Communication Server 1000Rls 3.0

2.0 June 2004 Introduction of BCM 3.6

3.0 March 2005 Update to include Communication Server 1000 Rls 4.0

4.0 May 2005 Update to include BCM 3.7 and BCM50

5.0 Nov 2006 Update to include BCM 4.0, BCM50R2, Communication Server 1000 Rls 4.5

5.1 Dec 2006 Corrected Table 1 to reflect SRG 1.5 support with Succession 3.0.

5.2 June 2007 Corrected Tables 6 and 7 to reflect the correct operation and support level of

Date Reason for Release

TRO-CM functionality from a BCM perspective.

List of Tables

Table 1: H.323 Interoperability by Software Release 3 Table 2: SIP Interoperability by Software Release 4 Table 3: Interoperability Patch Reference Table 5 Table 4: Supported H.323 Functionality - BCM and Communication Server 1000 Release 4.0 and 4.5 6 Table 5: Supported H.323 Functionality between BCM and Meridian 1 with IP Trunk 3.0x 8 Table 6: Known H.323 Interop Issues Between BCM and CS1000 Release 4.5 and 4.0 11 Table 7: Known H.323 Interop Issues between BCM and Meridian 1 with IP Trunk 3.0x 14 Table 8: Succession and Meridian 1with IP Trunk Codec Configuration Rules 16 Table 9: Supported SIP Functionality - BCM and Communication Server 1000 Release 4.0 and 4.5 18 Table 10: Known SIP Interop Issues - BCM and Communication Server 1000 Release 4.0 and 4.5 19

ERSION 5.2 JUNE 2007 PAGE 2 OF 20

BCM INTEROPERABILITY WITH COMMUNICATION SERVER 1000 AND MERIDIAN 1 WITH IP TRUNK

Business Communications Manager Interoperability with

Communication Server 1000 and Meridian 1 with IP Trunk

Table 1 and Table 2 represent the H.323 and SIP trunk interoperability, 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. 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, the latest BCM releases and the Communication Server 1000 Rls 4.5 and 4.0, and IP Trunk 3.01 releases, respectively.

Table 8 provides additional detail into codec configuration rules and diagnostic information.

Note: In this document, “CS1000 4.0” or “CS1000 4.5” refers to Communication Server 1000 Release 4.0 or

4.5 respectively.

Note: 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, BCM50R1 or BCM50R2 release.

Table 1: H.323 Interoperability by Software Release

Table 6 and Table 7 identify the known issues that exist between

Table 3

BCM3.5 BCM 3.6 SRG 1.0 BCM 3.7

Succession 1000 Rls 2

Meridian 1 IP Trunk 3.0

Meridian 1 or Succession 1000M w/ IP Trunk 3.01

Succession 3.0 (using Signaling Server 2.10.81)

Succession 3.0 (using Signaling Server 2.11.03)

Communication Server 1000 Rls 4.0

Communication Server 1000 Rls 4.5

BCM50

Supported

Supported Supported Supported Supported Supported Supported

Supported Supported Supported Supported Supported

Supported Supported Supported Supported Supported Supported Supported

BCM 4.0

Supported

SRG 1.5

Supported

SRG 1.5

BCM50

ERSION 5.2 JUNE 2007 PAGE 3 OF 20

BCM INTEROPERABILITY WITH COMMUNICATION SERVER 1000 AND MERIDIAN 1 WITH IP TRUNK

Table 2: SIP Interoperability by Software Release

BCM 4.0

Communication Server 1000 Rls 4.0

Communication Server 1000 Rls 4.5

Supported Supported

BCM50

ERSION 5.2 JUNE 2007 PAGE 4 OF 20

BCM INTEROPERABILITY WITH COMMUNICATION SERVER 1000 AND MERIDIAN 1 WITH IP TRUNK

Table 3: Interoperability Patch Reference Table

Meridian 1 or Succession 1000M IP Trunk 3.01

Communication Server 1000 Rls 4.0

Communication Server 1000 Rls 4.5

BCM 3.7 BCM50R1 BCM 4.0 BCM50R2

T1, T2, B1, B3 T1, T2, B2, B3 T1, T2, B3 T1, T2, B3

S1, B1, B3 S1, B2, B3 S1, B3 S1, B3

Succession Patch References:

Reference Patch ID Status

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:

Reference Patch Name Status

T1 MPLR18316 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 BCM

Note: This has been fixed in IP Trunk upissue 3.01.09

BCM Patch References:

Reference Patch Name Status

B1 BCM370.175-FEPS (FEPS

37.222.0.33)

B2 BCM050.108-FEPS (FEPS:

40.330.0.33)

B3 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.

Generally Available.

ERSION 5.2 JUNE 2007 PAGE 5 OF 20

BCM INTEROPERABILITY WITH COMMUNICATION SERVER 1000 AND MERIDIAN 1 WITH IP TRUNK

Table 4: Supported H.323 Functionality - BCM and Communication Server 1000 Release 4.0 and 4.5

Supported Functionality (with CS1000 4.0 and

4.5)

CS1000 4.0/45 Network Routing Server (NRS)

Succession 4.0/4.5 IP Peer Gateway (Signaling Server)

H.323 Basic Call Private Dial Plan

MCDN Networking

Description BCM 3.7

and

BCM50R1

Registration:

Supported Supported

BCM 4.0

and

BCM50R2

• Registers as an H.323 Endpoint Signaling method:

Supported Supported

• Gatekeeper Resolved Alternate Gatekeeper

H.225 Call Signaling (using Nortel Interoperability

Supported

(Programmable)

Supported

(Programmable)

Supported Supported

format)

H.245 Media Channel Signaling Call connection with Calling Line ID

CDP dial plan UDP dial plan

Supported Supported Supported Supported

Supported Supported

• 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:

Supported

• Centralized Voicemail,

• Central Attendant (Basic),

• Centralized Trunking

T.38 Fax

MCDN Features:

Private Name/Number Trunk Anti-Tromboning (TAT)

* Refer to

Table 6

Supported Supported

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 6

Network Call Redirection Message Waiting Indication (MWI) Message Indicator Key (MIK) Message Cancel Key (MCK) Station Camp-on Barge-In ISDN Call Connection Limit (ICCL)

Not Supported*

Supported*

Not Supported*

Supported*

Supported Supported Supported Supported Supported Supported Supported Supported Supported Supported Supported Supported Supported 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”.

Fax detection during H.323 call; renegotiation to T.38

* Refer to

Table 6

Supported* Supported*

ERSION 5.2 JUNE 2007 PAGE 6 OF 20

+ 14 hidden pages