Avaya Business Communication Manager Interoperability with Communication Server 1000 Uživatelský manuál stáhnout pdf (Strana 12)

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

ERSION 5.2 JUNE 2007 PAGE 12 OF 20

Known Issues with

CS1000 4.5 and 4.0

Description BCM 3.7 and BCM 4.0 and

BCM50R1 BCM50R2

Notes:

• BCM50R1 does not support the TAT and NAS enhancement of the Nortel Networks

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.

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

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.

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

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

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

MCDN Networking:

(cont’d)

Interop with ESN5 Signaling

Not Supported

Notes:

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

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

• If ESN5 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 calls in Element

Manager from BCM to a Virtual Trunk route that has ESN5 signaling enabled.

• 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

signaling

BCM:

Not Supported

BCM:

Not Supported

SRG:

Partially

Supported

SRG:

Partially

Supported

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

Komentáře k této Příručce

Žádné komentáře

Avaya Business Communication Manager Interoperability with Communication Server 1000 Uživatelský manuál Strana 12

Komentáře k této Příručce

Související produkty a manuály pro Sítě Avaya Business Communication Manager Interoperability with Communication Server 1000