Avaya Business Communication Manager Interoperability with Communication Server 1000 Manual de usuario descargar pdf (Pagina 14)

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

ERSION 5.2 JUNE 2007 PAGE 14 OF 20

Table 7: Known H.323 Interop Issues between BCM and Meridian 1 with IP Trunk 3.0x

Known Issues with

Meridian 1 with

IP Trunk 3.0x

Description BCM 3.7 BCM 4.0

and and

BCM50R1 BCM50R2

Advertised Codec Payload Configuration Supported Supported Support for

Multiple Codecs,

Payload Sizes

Notes:

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

• Refer to

Table 8 for details on codec configuration rules and diagnostic information.

T. 38 Fax detection & renegotiation Supported Supported T.38 Fax over IP

Notes:

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

TRO - BA (Before Answer):

(Pre -Succession 3.0 feature)

Supported Supported MCDN Networking

TRO - CM (Call modification) Not

Supported

Not

Supported

(New Succession 3.0 feature)

Notes:

TRO-CM feature works as follows in a mixed Meridian 1 with IP Trunk 3.0x and

BCM VoIP environment:

• 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).

• 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) Supported Supported

(Pre -Succession 3.0 implementation)

Trunk Anti-Tromboning (TAT)

Supported

BCM 3.7:

Supported

BCM50:

(Succession 3.0 enhancement)

Not directly

Supported

Notes:

• 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 and/or IP Trunk 3.01 call

servers.

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

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

1 2 ... 9 10 11 12 13 14 15 16 17 18 19 20

Comentarios a estos manuales

Sin comentarios

Avaya Business Communication Manager Interoperability with Communication Server 1000 Manual de usuario Pagina 14

Comentarios a estos manuales

Relacionado con productos y manuales para Redes Avaya Business Communication Manager Interoperability with Communication Server 1000