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

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

ERSION 5.2 JUNE 2007 PAGE 15 OF 20

Known Issues with

Meridian 1 with

IP Trunk 3.0x

Description BCM 3.7 BCM 4.0

and and

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.

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

Interop with ESN5 Signaling Not

Supported

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 Communication Server 4.5/4.0 nodes in order to control access to

PSTN trunk facilities at a remote Call Server and Media Gateway.

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

• The IP Trunk 3.0x must be configured with a Gatekeeper-resolved Network

Numbering.

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

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

Sin comentarios

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