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

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

ERSION 5.2 JUNE 2007 PAGE 19 OF 20

Table 10: Known SIP Interop Issues - BCM and Communication Server 1000 Release 4.0 and 4.5

Known SIP Issues

with CS 1000

Release 4.0 and 4.5

Description BCM 4.0

and

BCM50R2

SIP Transport

• The BCM default is UDP transport. Although the Element Manager interface

Protocol

displays a selection for TCP, this functionality is not currently supported.

• The Communication Server 1000 Rls 4.5/4.0 default is TCP.

Tandeming between

• VAD must be enabled on all sites and codec and payload settings configured per

SIP and H.323

Nortel recommendation to be able to support tandeming between a SIP and H.323

trunk on BCM. Note that this requirement is also valid for MCS5100 Rls 3.5 and Rls

3.0 interoperability.

• When BCM is tandeming between SIP and H.323 IP trunks and TAT is attempted,

the TAT attempt will fail. Note that this does not impact the call; the call will remain

stable with direct media connection between the two endpoints but will use all of the

original signaling resources for the duration of the call.

Advertised Codec Payload Configuration 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 SIP, 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.

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

Notes:

• Note that BCM allows the use of V.34 based faxed machines, (although it rejects

V.34 negotiation attempts) while CS1000 does not.

TRO - BA (Before Answer):

(Pre -Succession 3.0 feature)

Supported MCDN Networking:

TRO - CM (Call modification)

(New Succession 3.0 feature)

Partially

Supported

Notes:

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

environment:

o When BCM is a transferring party node (B), not an originating or terminating node

(A or C), TRO-CM works and both the Media and Signaling are direct (A 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.5/4.0 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.

Trunk Anti-Tromboning (TAT) Supported

(Pre -Succession 3.0 implementation)

1 2 ... 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 19

Comentarios a estos manuales

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