Avaya BCM50 Konfigurationsanleitung PDF herunterladen (Seite 384)

384 Chapter 44 Configuring VoIP trunk gateways

NN40020-603NN40020-603

— 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 389 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.

• RAS port: If the VoIP application requires a non-standard RAS port, enter the port number

here. 0 = the system uses the first available port.

• Enable H245 tunneling: Select or deselect the check box to allow or disallow H.245

messages within H.225. Note that the VoIP Gateway service must be restarted for any

change to take effect.

• Gatekeeper Support: Fill out these fields if the network is controlled by a Gatekeeper: Also

refer to “VoIP interoperability: Gatekeeper configuration” on page 389.

— Primary Gatekeeper IP: This is the IP address of the primary gatekeeper.

— Backup Gatekeepers: NetCentrex gatekeeper does not support RAS, therefore, any

backup gatekeepers must be entered in this field. Gatekeepers that use RAS can

provide a list of backup gatekeepers for the end point to use in the event of the primary

gatekeeper failure.

• In the Alias names field, enter all the alias names required to direct call signals to your

system.

• Gateway protocol - Select SL-1 for BCM 2.5 systems. Select CSE for BCM 3.0 and newer

systems. Or select None.

• Registration TTLs: Specifies the KeepAlive interval

• Gateway TTLs: This protocol should match all other systems on the network.

• Status: This field displays the current status of the gatekeeper.

3 Suggested next steps:

• Ensure router settings, firewalls and system ports are set correctly to support IP traffic over

the trunks.

• “Configuring lines” on page 129

• “Configuring lines: Target lines” on page 141

• “Setting up VoIP trunks for fallback” on page 391

• Ensure private network dialing plan and access settings matches the rest of the private

network: “Dialing plan: Private network settings” on page 281

• Private networking: “Private networking: Basic parameters” on page 315

• Assigning the VoIP line pools to system telephones: “Line Access - Line Pool Access tab”

in the Device Configuration Guide (NN40020-300).

1 2 ... 379 380 381 382 383 384 385 386 387 388 389 ... 567 568

Kommentare zu diesen Handbüchern

Keine Kommentare

Avaya BCM50 Konfigurationsanleitung Seite 384

Kommentare zu diesen Handbüchern

Verwandte Produkte und Handbücher für Software Avaya BCM50