Avaya Business Communication Manager Interoperability with Communication Server 1000 Manual do Utilizador descarregar pdf (Página 11)

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

ERSION 5.2 JUNE 2007 PAGE 11 OF 20

Table 6: Known H.323 Interop Issues Between BCM and CS1000 Release 4.5 and 4.0

Known Issues with

CS1000 4.5 and 4.0

Description BCM 3.7 and BCM 4.0 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 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.

TRO - BA (Before Answer):

(Pre -Succession 3.0 feature)

Supported Supported MCDN Networking:

TRO - CM (Call modification)

(New Succession 3.0 feature)

Not

Supported

Not

Supported

Notes:

• TRO-CM works as follows in a mixed Succession 4.5/4.0 and BCM VoIP

environment:

o When BCM is a transferring party node (B), 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 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.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

Trunk Anti-Tromboning (TAT)

(Pre -Succession 3.0 implementation)

Supported Supported

Trunk Anti-Tromboning (TAT) BCM 3.7:

Supported

BCM50R1:

(Succession 3.0 enhancement)

Not directly

Supported

(See notes)

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

Comentários a estes Manuais

Sem comentários

Avaya Business Communication Manager Interoperability with Communication Server 1000 Manual do Utilizador Página 11

Comentários a estes Manuais

Manuais e produtos relacionados com Redes Avaya Business Communication Manager Interoperability with Communication Server 1000