BIBLIOGRAFÍA Libros y revistas

The following figure shows the H323 Settings tab.

Figure 37 H323 Settings

The following table describes the fields on the H323 Settings tab.

Remote capability MWI

<check box> Default: Selected

This setting must coordinate with the functionality of the remote system that hosts the remote voice mail.

Ignore in-band DTMF in RTP

<check box> Default: Unselected

If you select the check box, the BCM ignores audible in- band DTMF tones received over VoIP trunks after the BCM connects the remote end to a locally hosted call center application, or a locally hosted CallPilot application such as auto attendant, or voice mai.l

Attention: Use this setting when the far end is a CS 2000 and Packet Voice Gateway (PVG) combination where the PVG is provisioned for OOBDTMFSupp=FullSupport resulting in the PVG + CS 2000 sending out-of-band, as well as in-band, DTMF tones at the same time to the BCM. The PVG may not send both tone notifications depending on the version of the CS 2000 software release and whether the call is using G711.

Coordinate this setting with CS 2000 settings. See the CS 2000 administrator.

Table 18 IP Trunk Settings field descriptions

Table 19 H323 Settings field descriptions

Attribute Value Description

Telephony Settings Fallback to circuit- switched Enabled-All Enabled-TDM Disabled

Your choice determines how the system will handle calls if the IP network cannot be used.

• Enabled-All: All calls are rerouted over specified PSTN trunks lines.

• Enabled-TDM: All TDM (digital telephones) voice calls will be rerouted over specified PSTN trunks lines.

• Disabled: Calls will not be rerouted.

Attention: Enabled-TDM enables fallback for calls that originate on digital or analog 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.

Gatekeeper digits 0-9 If dialed digits match gatekeeper digits, the call is routed via H.323 protocol.

If the digits do not match, the call is routed via SIP protocol. Normal route

fallback to

None Prime set

Select None or Prime set. If Prime set is selected and the outgoing IP trunk leg of the call in a tandem scenario cannot be completed, the call will terminate on the prime set for the line.

Default: None MCDN protocol None

SL1 CSE

These protocols require a keycode.

SL1: Use this protocol only for BCM 2.5 systems

CSE: Use this protocol for BCM 3.0 and later systems. This protocol supports Meridian 1 IPT.

Otherwise, use None. Gatekeeper

wildcard

<check box> Default: Unselected

If you select the check box, all dialed digits match

gatekeeper digits and VoIP calls will be routed through the gatekeeper.

Configuration

Modify <button> Click to modify the parameters.

Attention: If you change any field in the Configuration section, all active H.323 calls are dropped. You must click Modify to restart the H.323 subsystem.

Call signaling Direct Gatekeeper Resolved Gatekeeper Routed Gatekeeper Routed no RAS

The routing table in Business Element Manager defines a destination code (digits) for each remote system to direct the calls for that system to route.

Gatekeeper Resolved: The gatekeeper resolves the phone numbers into IP addresses, but the gatekeeper is not involved in call signaling. All call signaling occurs directly between H.323 endpoints.

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 uses none of the gatekeeper Registration and Admission Services (RAS). Enable H245

tunneling

<check box> Default: Unselected

If you select the check box, the VoIP Gateway tunnels H.245 messages within H.225. You must restart the VoIP Gateway service for the change to take effect.

Primary Gatekeeper IP

<IP Address> If Gatekeeper Routed, Gatekeeper Resolved or Gatekeeper Routed no RAS are selected under Call Signaling, type the IP address of the machine that is running the gatekeeper.

Backup Gatekeeper(s)

<IP Address> <IP Address>

NetCentrex gatekeeper does not support RAS; therefore, any backup gatekeepers must be entered in this field.

Attention: 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.

Table 19 H323 Settings field descriptions

Alias Names If you select Gatekeeper Routed, Gatekeeper Resolved, or Gatekeeper Routed no RAS for Call Signaling, enter one or more alias names for the gateway: Alias names are comma delimited, and can be one of the following types:

• E.164 — numeric identifier containing digits in the range 0-9. Identified by the keyword TEL: Example: the BCM is assigned an E.164 and an H.323 Identifier: Alias Names: TEL:76, NAME:bcm10.nortel.com

• NPI-TON — also referred to as a PartyNumber alias. Similar to E164 except that the keyword indicates the NPI (numbering plan identification), as well as the TON (type of number). Identified by one of the following keywords: PUB

(Public Unknown Number); PRI (Private Unknown Number); UDP (Private Level 1 Regional Number (UDP)); CDP (Private Local Number (CDP)).

• H.323Identifier — alphanumeric strings representing names, e-mail addresses, etc. Identified by the keyword NAME:

Example: The BCM is assigned a public dialed number prefix of 76, a private CDP number of 45, and an H.323 Identifier alias: Alias Names: PUB:76, CDP:45, NAME:bcm10.nortel.com

• H.225 (Q.931) CallingPartyNumber (NetCentrex gatekeeper) — The NetCentrex gatekeeper uses the H.225(Q.931) CallingPartyNumber to resolve the call originator for billing purposes. This number must then contain a unique prefix, or location code that is unique across all endpoints that use the NetCentrex gatekeeper. Identified by the keyword src:. Example for private networks: CDP alias = src:<DN>; UDP alias =

src:<LOC><DN>. Example for public network: src:<public OLI>

Attention: E164 or NPI-TON alias types are commonly used because they fit into dialing plans. A BCM alias list should not mix these types. Also, the type of alias used should be consistent with the dialing plan configuration. Use the same alias naming method on all BCMs within a network.

Call signaling port 0-65535 Default: 1720

This field allows you to set non-standard call signaling port for VoIP applications that require special ports.

0 = The first available port is used.

Ensure that you do not select a port that is assigned elsewhere in the BCM.

RAS port 0-65535 Default: 0

Use this field to assign a non-standard Registration and Admission (RAS) port for VoIP applications that require special ports.

0 = The first available port is used.

Ensure that you do not select a port that is assigned elsewhere in the BCM. To ensure the port is not in use, run netstat-a from the command line.

Table 19 H323 Settings field descriptions