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

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

ERSION 5.2 JUNE 2007 PAGE 8 OF 20

Table 5: Supported H.323 Functionality between BCM and Meridian 1 with IP Trunk 3.0x

Supported

Functionality

(with IP Trunk 3.0x)

Description

BCM 3.7

and

BCM50R1

BCM 4.0

and

BCM50R2

Registration:

• Stand-alone or Co-resident GK

Supported Supported

Signaling method (to IP Trunk 3.01 nodes registered

with the NRS)

• Gatekeeper Resolved

Supported Supported

Network Routing

Server (NRS)

Note that NRS can

refer to the NRS on

CS1000 Rls 4.5 or 4.0

Alternate NRS (Stand-alone or Co-resident):

• IP Address received during the registration process

Supported

(Programmable)

Supported

(Programmable)

H.225 Call Signaling using:

• Direct routed to standard UDP port (15000)

• NRS to resolve destination telephone number

• Nortel Networks Interoperability format

capability, including GK-resolved MCDN Non-Call-

Associated Signaling (NCAS).

Supported Supported

IP Trunk 3.01 Node

Registered with

NRS as

H323 Endpoint

Notes:

• The BCM H.323 Gatekeeper Settings tab should have the Gateway Protocol set to

“CSE”.

• BCM supports the Redirect FACILITY message that IP Trunk 3.01 Node Leader uses

to redirect all incoming calls to a reserved trunk resource in the node.

• BCM supports codec negotiation with IP Trunk 3.01 using Fast Start signaling

elements and H.245 Media Path signaling.

• BCM side (Node B) initiates H.245 Media Channel Signaling for direct media path

etween IP Trunk 3.01 nodes (A and C) that have a tandem IP Trunk call signaling

connection via the BCM (Node B).

• IP Trunk 3.01 side (Node B) never initiates H.245 Media Channel Signaling for direct

media path between BCM nodes (A and C) that have a tandem IP Trunk call signaling

connection via IP Trunk 3.01 (Node B).

H.225 Call Signaling using:

• Direct routed to standard TCP port

• Local BCM and IP Trunk dialing plan to resolve the

destination telephone number,

• ITG ISDN IP Trunk format.

MCDN NCAS using:

• Direct routed to a proprietary TCP port

• Local BCM and IP Trunk dialing plan to resolve the

destination telephone number.

Supported Supported IP Trunk 3.01 Node

Not Registered with

NRS

Notes:

• The BCM should be configured to use “CSE” as the Gateway Protocol in the BCM

Remote Gateway Table. The IPT should be configured to use “CSE” mode in the dial

plan table.

• BCM supports the Redirect FACILITY message that IP Trunk 3.01 Node Leader uses

to redirect all incoming calls to a reserved trunk resource in the node.

• BCM supports codec negotiation with IP Trunk 3.01 using Fast Start signaling

elements and H.245 Media Path signaling.

• BCM side (Node B) initiates H.245 Media Channel Signaling for direct media path

between IP Trunk 3.01 nodes (A and C) that have a tandem IP Trunk call signaling

1 2 3 4 5 6 7 8 9 10 11 12 13 ... 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 8

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