Avaya BCM 4.0 Networking Guide de configuration télécharger pdf (Page 417)

100

101

Chapter 45 Configuring VoIP trunk gateways 417

BCM 4.0 Networking Configuration Guide

If the network has a gatekeeper (H.323 trunks, only), the BCM can request a method for call

signaling, this request is granted depending on the configuration of the gatekeeper. Ultimately, the

gatekeeper decides which call signaling method to use. Refer to “VoIP interoperability:

Gatekeeper configuration” on page 423.

The following path indicates where to access the local gateway in Element Manager:

Element Manager: Configuration > Resources > Telephony Resources > IP Trunks

1 On the Modules panel, in the Module type column, select the IP Trunks line.

2 In the bottom panel, select the Local Gateway tab.

3 Choose the settings that you need for your system:

• Fallback to circuit-switched: define how you want the system to handle calls that the

system fails to send over the VoIP trunk.

• Forward redirected OLI - If the box is selected, the OLI of an internal telephone is

forwarded over the VoIP trunk when a call is transferred to an external number over the

private VoIP network. If the box is cleared, only the CLID of the transferred call is

forwarded.

• Send name display - When selected, the telephone name is sent with outgoing calls to the

network.

• Remote capability MWI - This setting must coordinate with the functionality of the remote

system hosting the remote voice mail.

• Call Signaling: Determine how the calls are delivered over the network:

— Direct: call signaling information is passed directly between endpoints.

Note: You will need to set up remote gateways (“Setting up remote gateways” on

page 418).

— Gatekeeper Resolved: all call signaling occurs directly between H.323 endpoints.

This means that the gatekeeper resolves the phone numbers into IP addresses, but the

gatekeeper is not involved in call signaling.

— Gatekeeper Routed: uses a gatekeeper for call setup and control. In this method, call

signaling is directed through the gatekeeper.

— Gatekeeper Routed no RAS: Use this setting for a NetCentrex gatekeeper. With this

setting, the system routes all calls through the gatekeeper but does not use any of the

gatekeeper Registration and Admission Services (RAS).

—Refer to “Using CS 1000 as a gatekeeper” on page 423 for specific information about

configuring the gatekeeper for H.323 trunks.

Network note: If your private network contains a Meridian 1-IPT, you cannot use

Radvision for a gatekeeper.

• Call signaling port: If there are VoIP applications that require non-standard call signaling

ports, enter the port number here. 0 = the system uses the first available port.

Note: Enabled-TDM enables fallback for calls originating on digital telephones.

This is useful if your IP telephones are connected remotely, on the public side of

the BCM network, because PSTN fallback is unlikely to result in better quality of

service in that scenario.

1 2 ... 412 413 414 415 416 417 418 419 420 421 422 ... 757 758

Commentaires sur ces manuels

Pas de commentaire

Avaya BCM 4.0 Networking Guide de configuration Page 417

Commentaires sur ces manuels

Produits connexes et manuels pour Mise en réseau Avaya BCM 4.0 Networking