Cisco Unified CallManager Administration Guide, Release 4.2(3)
Gateway Configuration
Downloads: This chapterpdf (PDF - 803.0KB) The complete bookPDF (PDF - 6.99MB) | Feedback

Gateway Configuration

Table Of Contents

Gateway Configuration

Adding Gateways to Cisco Unified CallManager

Adding a Cisco IOS MGCP Gateway

Adding Ports to an MGCP Gateway

Adding FXS Ports to an MGCP Gateway

Adding FXO Ports to an MGCP Gateway

Adding T1-CAS Ports to an MGCP Gateway

Adding a T1 PRI or E1 PRI Device to an MGCP Gateway

Adding a BRI Port to an MGCP Gateway

Adding a Cisco IOS SCCP Gateway

Adding a Non-IOS MGCP Gateway

Adding a Cisco IOS H.323 Gateway

Adding an Analog Access Gateway and Ports

Adding a Cisco VG248 Analog Phone Gateway

Gateway Configuration Settings

MGCP Gateway Configuration Settings

FXS/FXO Gateway Configuration Settings

E1/T1 PRI Gateway Configuration Settings

BRI Gateway Configuration Settings

T1-CAS Gateway Configuration Settings

H.323 Gateway Configuration Settings

Analog Access Gateway Configuration Settings

Cisco VG248 Gateway Configuration Settings

Cisco IOS SCCP Gateway Configuration Settings

Port Configuration Settings

POTS Port Configuration Settings

Loop-Start Port Configuration Settings

Ground-Start Port Configuration Settings

E & M Port Configuration Settings

Finding Specific Gateways

Searching by Device Name

Searching by Description

Searching by Directory Number/Route Pattern

Searching by Calling Search Space

Searching by Device Pool

Searching by Route Group

Searching by Device Type

Modifying Gateways and Ports

Using Dependency Records

Deleting Gateways

Resetting and Restarting Gateways

Updating Gateways and Ports


Gateway Configuration


Cisco IP telephony gateways enable Cisco Unified CallManager to communicate with non-IP telecommunications devices. Cisco Unified CallManager supports several gateway types as described in the Cisco Unified CallManager System Guide.

These sections provide information about using Cisco Unified CallManager for working with and configuring Cisco gateways.

Adding Gateways to Cisco Unified CallManager

Gateway Configuration Settings

Port Configuration Settings

Finding Specific Gateways

Modifying Gateways and Ports

Understanding Cisco Unified CallManager Voice Gateways, Cisco Unified CallManager System Guide

Adding Gateways to Cisco Unified CallManager

To enable Cisco Unified CallManager to manage IP telephony gateways in your network, you must first add each gateway to the Cisco Unified CallManager configuration database. The procedures, windows, and configuration settings for adding a gateway vary according to the gateway model that you are adding.

The following procedure describes how to add a new gateway in Cisco Unified CallManager.

Procedure


Step 1 To display the Find/List Gateways window, choose Device > Gateway.

Step 2 Click the Add a New Gateway link. The Add a New Gateway window displays.

Step 3 From the Gateway type drop-down list box, choose the gateway type that you want to add.

Step 4 The Device Protocol field automatically populates, depending on which gateway type you choose. For certain gateway types, you can change the device protocol by choosing one of the available protocols from the drop-down list box.

Step 5 Click Next.

Step 6 In the following table, click the specific procedure for the combination of gateway type and device protocol that you are configuring. After you are in the correct procedure, start with the step where you enter the appropriate settings for that particular gateway type.


Table 58-1 Gateways 

Type of Gateway
Procedure to Add

Cisco Voice Gateway 200 (VG200)

Cisco IOS 1751, 1760, 269X, 26XX, 362X, 364X, 366X, 3725, 3745 Gateways

Cisco 2801, 2811, 2821, 2851, 3825, 3845 Gateways

Cisco Catalyst 4000 Access Gateway Module

Cisco Catalyst 4224 Voice Gateway Switch

Communication Media Module

Cisco IAD 2420

VG224 Gateway

Adding a Cisco IOS MGCP Gateway

Cisco IOS 26XX, 269X, 2801, 2811, 2821, 2851, 3725, 3745, 3825, 3845 Gateways

VG224 Gateway

Adding a Cisco IOS SCCP Gateway

Cisco Catalyst 6000 E1 VoIP Gateway

Cisco Catalyst 6000 T1 VoIP Gateway

Cisco DT-24+ or DE-30+ Gateway

Adding a Non-IOS MGCP Gateway

Other Cisco IOS Gateway that is configured in H.323 mode

Adding a Cisco IOS H.323 Gateway

Cisco Catalyst 6000 24 Port FXS Gateway

Analog Access AS-2, AS-4, AS-8, AT-2, AT-4, AT-8

Adding an Analog Access Gateway and Ports

Cisco VG248 Gateway

Adding a Cisco VG248 Analog Phone Gateway


Adding a Cisco IOS MGCP Gateway

Use the following procedure to add and configure a Cisco IOS MGCP gateway to Cisco Unified CallManager. The following Cisco IOS gateways support MGCP:

Cisco VG200 Cisco Unified Communications Voice Gateway

Cisco IOS 1751 and 1760 Gateways

Cisco IOS 26xx and 269xGateways

Cisco 2801, 2811, 2821, 2851, 3825, 3845 Gateways

Cisco IOS 362x, 364x, 366x Gateways

Cisco IOS 3725 and 3745 Gateways

Cisco Catalyst 4000 Access Gateway Module

Cisco Catalyst 4224 Voice Gateway Switch

Communication Media Module

Cisco IAD2420 Gateway

VG224 Gateway


Note Like other IOS MGCP gateways, MRP/ASI gateways may work with a Cisco Unified CallManager group that contains three Cisco Unified CallManagers. ASI/MRP gateways testing occurs, however, with only one backup Cisco Unified CallManager.


Before You Begin

Before configuring a Cisco IOS MGCP gateway for use with Cisco Unified CallManager, you must configure the gateway by using the Cisco IOS command-line interface (CLI). For procedures and commands that are required to perform this configuration, refer to the configuration documentation that is supplied with the gateway.

Procedure


Step 1 Choose Device > Add a New Device.

The Add a New Device window displays.

Step 2 From the Device type drop-down list box, choose Gateway and click Next.

The Add a New Gateway window displays.

Step 3 From the Gateway Type drop-down list box, choose one of the following MGCP gateways:

VG200

Cisco IOS 362x, 364x, 366x gateways

Cisco IOS 3725 and 3745 gateways

Cisco IOS 26xx gateways

Cisco 2801, 2811, 2821, 2851, 3825, 3845 Gateways

Cisco Catalyst 4000 Access Gateway Module

Cisco Catalyst 4224 Voice Gateway Switch

Communication Media Module

Cisco IAD2420 gateway


Note The Cisco Catalyst 6000 gateways also support MGCP but are configured differently. See the "Adding a Non-IOS MGCP Gateway" section.


Step 4 Ensure that the Device Protocol drop-down list box displays the MGCP device protocol.

Cisco IOS MGCP gateways support different device protocols for interfacing to the PSTN or other non-IP devices, depending on the gateway model and the type of installed network modules and voice interface cards (VICs). A subsequent web window provides configuration for these interfaces.

Step 5 Click Next. The MGCP Configuration window displays.

Step 6 Enter the appropriate settings and choose the type of network modules that are installed in each slot, as described in the "MGCP Gateway Configuration Settings" section, including any product-specific configuration settings.

Step 7 Click Insert.

The MGCP Gateway Configuration window updates and displays drop-down list boxes with options for configuring the type of voice interface cards (VICs) in each subunit of each network module.

The available choices depend on the type of network modules that are configured in the MGCP Configuration window.

Step 8 From the drop-down list boxes, choose the type of VICs that are installed in each subunit and click Update.

The window updates to add links for configuring endpoint information and ports for the chosen type of VICs.

Step 9 Click an endpoint identifier (for example, 1/0/0) to configure device protocol information and add ports for the installed types of VICs.

For detailed instructions, see the following procedures:

Adding FXS Ports to an MGCP Gateway

Adding FXO Ports to an MGCP Gateway

Adding T1-CAS Ports to an MGCP Gateway

Adding a T1 PRI or E1 PRI Device to an MGCP Gateway

Adding a BRI Port to an MGCP Gateway

Step 10 Reset the gateway to apply the changes.

Step 11 Continue configuring endpoint information and ports as needed.

Step 12 After you finish configuring the endpoint and adding ports, you need to add the MGCP gateway device to a route group/route list or assign a route pattern to the gateway, so calls can be routed to the gateway.


Note You need to add the MGCP gateway to a route pattern only for outbound calling.



Adding Ports to an MGCP Gateway

The device protocols and port types that can be configured on MGCP gateways vary by the type of installed voice interface cards. This section contains the following procedures:

Adding FXS Ports to an MGCP Gateway

Adding FXO Ports to an MGCP Gateway

Adding T1-CAS Ports to an MGCP Gateway

Adding a T1 PRI or E1 PRI Device to an MGCP Gateway

Adding a BRI Port to an MGCP Gateway

Adding FXS Ports to an MGCP Gateway

You can use Foreign Exchange Station (FXS) ports to connect to any POTS device. Use this procedure to configure FXS ports on an MGCP gateway.

Before You Begin

You must add an MGCP gateway before configuring ports. See the "Adding a Cisco IOS MGCP Gateway" section for instructions.

Procedure


Step 1 To display the Find/List Gateways window, choose Device > Gateway or skip to Step 4 if you have already located the MGCP gateway to which you want to add FXS ports.

Step 2 Enter the appropriate search criteria to locate the MGCP gateway to which you want to add FXS ports.

Step 3 Click the name of the desired gateway to display its MGCP configuration settings and endpoint identifiers.

Step 4 From the MGCP Configuration window, click the endpoint identifier for the FXS VIC that you want to configure.

The window refreshes and displays the Gateway Configuration window.

Step 5 Enter the appropriate Gateway Information and Port Information settings. See the following sections for details about these fields:

FXS/FXO Gateway Configuration Settings

POTS Port Configuration Settings

Step 6 Click Insert.


Note After you insert a POTS port, the window refreshes and displays the POTS port in the list on the left side of the window. An Add DN link displays to the right of the new port.


Step 7 Click Add DN to add directory numbers to the POTS port or, if you configured another type of port, go to Step 9.


Note See the "Adding a Directory Number" section on page 59-49 and "Directory Number Configuration Settings" section on page 59-55 for information about adding and configuring DNs.


Step 8 To return to the main MGCP gateway configuration window for the gateway to which you just added the ports, click Back to MGCP Configuration.

Step 9 Reset the gateway to apply the changes.

Step 10 Repeat Step 4 through Step 8 to add additional FXS ports.


Related Topics

Adding Gateways to Cisco Unified CallManager

Adding a Cisco IOS MGCP Gateway

Port Configuration Settings

Adding FXO Ports to an MGCP Gateway

You can use Foreign Exchange Office (FXO) ports for connecting to a central office or PBX. Use this procedure to add and configure FXO ports for loop start or ground start on an MGCP gateway.


Note Cisco Unified CallManager assumes all loop-start trunks lack positive disconnect supervision. Configure trunks with positive disconnect supervision as ground start, so active calls can be maintained during a Cisco Unified CallManager server failover.


Before You Begin

You must add an MGCP gateway before configuring ports. See the "Adding a Cisco IOS MGCP Gateway" section for instructions.

Procedure


Step 1 To display the Find/List Gateways window, choose Device > Gateway or skip to Step 4 if you have already located the MGCP gateway to which you want to add FXO ports.

Step 2 Enter the appropriate search criteria to locate the MGCP gateway to which you want to add FXO ports and click Find. The search results window displays.

Step 3 Click the name of the desired gateway to display its MGCP configuration settings and endpoint identifiers.

Step 4 From the MGCP Configuration window, click the endpoint identifiers of the FXO port that you want to configure.

Step 5 From the Port Type drop-down list box, choose either Ground Start or Loop Start.


Note You must choose the same port type for both endpoint identifiers of the VIC-2FXO port. If you choose different port types, a message displays.


Step 6 Enter the appropriate Gateway Configuration and Port Information settings as described in the following sections:

FXS/FXO Gateway Configuration Settings

Loop-Start Port Configuration Settings

Ground-Start Port Configuration Settings

Step 7 Click Insert.

Step 8 To return to the main MGCP gateway configuration window for the gateway to which you just added the ports, click Back to Main Gateway Configuration.

Step 9 To add more FXO ports, repeat Step 4 though Step 7.

Step 10 To apply the changes, reset the gateway.


Related Topics

Adding Gateways to Cisco Unified CallManager

Port Configuration Settings

Adding T1-CAS Ports to an MGCP Gateway

Use this procedure to add T1-CAS ports to an MGCP gateway.


Step 1 To display the Find/List Gateways window, choose Device > Gateway or skip to Step 4 if you have already located the MGCP gateway to which you want to add T1-CAS ports.

Step 2 To locate the MGCP gateway to which you want to add a T1-CAS port, enter the appropriate search criteria.

Step 3 To display its MGCP configuration settings and endpoint identifiers, click the name of the desired gateway.

Step 4 From the MGCP Configuration window, click the endpoint identifier of the T1-CAS port that you want to configure.

Step 5 From the drop-down list box, choose the T1-CAS protocol.

Step 6 Enter the appropriate Gateway Configuration settings. See the "T1-CAS Gateway Configuration Settings" section for details.

Step 7 Click Insert.

Step 8 Click Add New Port. A port configuration dialog box opens.

Step 9 From the Port Type drop-down list box, choose a port type. See the "Port Configuration Settings" section for the appropriate settings for the port type that you choose.

Step 10 Click Insert or Insert and Close.

Step 11 To apply the changes, reset the gateway.


Related Topics

Adding Gateways to Cisco Unified CallManager

Port Configuration Settings

Adding a T1 PRI or E1 PRI Device to an MGCP Gateway


Step 1 To display the Find/List Gateways window, choose Device > Gateway or skip to Step 4 if you have already located the MGCP gateway to which you want to add a port.

Step 2 To locate the MGCP gateway to which you want to add a T1 PRI or E1 PRI port, enter the appropriate search criteria.

Step 3 To display the configuration information for the selected gateway, click the name of the desired gateway in the list.

Step 4 From the MGCP Configuration window, click the endpoint identifier of the T1 or E1 PRI port that you want to configure.

Step 5 Configure the T1 PRI or E1 PRI device protocol settings. See the "E1/T1 PRI Gateway Configuration Settings" section for detailed field descriptions.

Step 6 Click Insert.

Step 7 To apply the changes, reset the gateway.


Related Topics

Adding a Cisco IOS MGCP Gateway

Adding Gateways to Cisco Unified CallManager

E1/T1 PRI Gateway Configuration Settings

Adding a BRI Port to an MGCP Gateway

The device protocols and port types that you can configure on MGCP gateways vary by the type of installed voice interface cards (VICs). This section contains the procedures for adding a BRI port to an MGCP gateway.

Procedure


Step 1 To display the Find/List Gateways window, choose Device > Gateway, or if you have already located the MGCP gateway to which you want to add a port, skip to Step 4.

Step 2 To locate the MGCP gateway to which you want to add a BRI port, enter the appropriate search criteria.

Step 3 To display the configuration information for the chosen gateway, click the name of the desired gateway in the list.

Step 4 From the MGCP Configuration window, click the endpoint identifier of the BRI port that you want to configure.

Step 5 Configure the BRI device protocol settings. See the "BRI Gateway Configuration Settings" section for detailed field descriptions.

Step 6 Click Insert.

Step 7 To apply the changes, reset the gateway.


Related Topics

Gateway Configuration Checklist, Cisco Unified CallManager System Guide

Adding a Cisco IOS MGCP Gateway

BRI Gateway Configuration Settings

Adding a Cisco IOS SCCP Gateway

Use the following procedure to add and configure a Cisco IOS SCCP gateway to Cisco Unified CallManager. The following Cisco IOS gateways support SCCP:

Cisco IOS 26xx and 269x Gateways

Cisco IOS 2801, 2811, 2821, and 2851 Gateways

Cisco IOS 3725, 3745, 3825, and 3845 Gateways

Cisco VG224 Gateway

Before You Begin

Configure a Cisco IOS SCCP gateway by adding the gateway first to Cisco Unified CallManager. Afterward, configure the gateway by using the Cisco IOS command-line interface (CLI). For procedures and commands that are required to perform this configuration, refer to the configuration documentation that is supplied with the gateway.

Procedure


Step 1 Choose Device > Add a New Device.

The Add a New Device window displays.

Step 2 From the Device type drop-down list box, choose Gateway and click Next.

The Add a New Gateway window displays.

Step 3 From the Gateway Type drop-down list box, choose one of the following SCCP gateways:

Cisco IOS 26xx and 269x Gateways

Cisco IOS 3725 and 3745 Gateways

Cisco VG224

Step 4 From the Device Protocol drop-down list box, choose the SCCP device protocol.

Cisco IOS SCCP gateways support SCCP for interfacing to the PSTN or other non-IP devices, depending on the gateway model and the type of installed network modules and voice interface cards (VICs). A subsequent web window provides configuration for the interface.

Step 5 Click Next. The SCCP Configuration window displays.

Step 6 Enter the appropriate settings and choose the type of network modules that are installed in each slot, as described in the "Cisco IOS SCCP Gateway Configuration Settings" section, including any product-specific configuration settings.

Step 7 Click Insert.

The SCCP Gateway Configuration window updates and displays drop-down list boxes with options for configuring the type of voice interface cards (VICs) in each subunit of each network module.

The available choices depend on the type of network modules that are configured in the SCCP Configuration window.

Step 8 From the drop-down list boxes, choose the type of VICs that are installed in each subunit and click Update.

The window updates to add links for configuring endpoint information and ports for the chosen type of VICs.

Step 9 Click an endpoint identifier (for example, 1/0/0) to configure device protocol information, add ports for the installed types of VICs and add FXS/BRI port to a SCCP gateway.

Step 10 Reset the gateway to apply the changes.

Step 11 Continue configuring endpoint information and ports as needed.

Adding a Non-IOS MGCP Gateway

Use the following procedure to add the following non-IOS Cisco MGCP gateways to Cisco Unified CallManager:

Cisco DT-24+ Gateway

Cisco DE-30+ Gateway

Cisco Catalyst 6000 E1 VoIP Gateway

Cisco Catalyst 6000 T1 VoIP Gateway

Procedure


Step 1 Choose Device > Add New Device.

The Add a New Device window displays.

Step 2 From the Device type drop-down list box, choose Gateway.

From the Gateway Type drop-down list box, choose one of the following digital gateways:

Cisco DT-24+ Gateway

Cisco DE-30+ Gateway

Cisco Catalyst 6000 E1 VoIP Gateway

Cisco Catalyst 6000 T1 VoIP Gateway

Step 3 From the drop-down list box, choose the appropriate device protocol for the type of interfaces that you are configuring on the gateway. The available choices vary according to gateway model:

DT-24+ or Cisco Catalyst 6000 T1 VoIP Gateway—Choose either Digital Access PRI (T1 PRI) or Digital Access T1 (T1-CAS).

DE-30+ or Cisco Catalyst E1 VoIP Gateway—Choose Digital PRI (E1 PRI).

Step 4 Click Next.

The Gateway Configuration window displays.

Step 5 Enter the appropriate settings, depending on whether you are configuring a Digital T1 or E1 PRI interface or a Digital T1-CAS interface as described in following sections:

E1/T1 PRI Gateway Configuration Settings

T1-CAS Gateway Configuration Settings

Step 6 Click Insert.

Step 7 If you are configuring a T1-CAS interface on a DT-24+ or Catalyst 6000 T1 VoIP Gateway, click Add a New Port to configure ports.

See the "Adding T1-CAS Ports to an MGCP Gateway" section and begin with Step 9.

Step 8 To apply the changes, reset the gateway.


Related Topics

Adding Gateways to Cisco Unified CallManager

E1/T1 PRI Gateway Configuration Settings

T1-CAS Gateway Configuration Settings

Adding a Cisco IOS H.323 Gateway

Follow these procedures to add a Cisco IOS H.323 gateway to Cisco Unified CallManager.

Before You Begin

Before configuring a Cisco IOS H.323 gateway for use with Cisco Unified CallManager, you must configure the gateway by using the Cisco IOS command-line interface (CLI). Compared to MGCP gateways, H.323 gateways require more configuration on the gateway because the gateway must maintain the dial plan and route pattern. For procedures and commands that are required to perform this configuration, refer to the configuration documentation that is supplied with the gateway.

Procedure


Step 1 Choose Device > Add a New Device.

The Add a New Device window displays.

Step 2 From the Device type drop-down list box, choose Gateway.

Step 3 Click Next.

The Add a New Gateway window displays.

Step 4 From the Gateway Type drop-down list box, choose H.323 Gateway.

Step 5 In the Device Protocol drop-down list box, the H.225 device protocol displays.

Step 6 Click Next.

Step 7 Enter the appropriate settings as described in "H.323 Gateway Configuration Settings" section.

Step 8 Click Insert.

Step 9 To apply the changes, reset the gateway.


Related Topics

Adding Gateways to Cisco Unified CallManager

H.323 Gateway Configuration Settings

Adding an Analog Access Gateway and Ports

Use the procedure in this section to add and configure ports for the following non-IOS Cisco analog access gateways:

Cisco AS-2, AS-4, and AS-8 Gateways

Cisco AT-2, AT-4, and AT-8 Gateways

Cisco Catalyst 6000 24 Port FXS Gateway

Procedure


Step 1 Choose Device > Add a New Device.

The Add a New Device window displays.

Step 2 From the Device type drop-down list box, choose Gateway.

Step 3 Click Next.

The Add a New Gateway window displays.

Step 4 From the Gateway type drop-down list box, choose a supported analog gateway:

Cisco AS-2, AS-4, and AS-8 Gateways

Cisco AT-2, AT-4, and AT-8 Gateways

Cisco Catalyst 6000 24 Port FXS Gateway

When you choose an analog gateway, Cisco Unified CallManager automatically chooses the appropriate device protocol for the gateway (in this case, Analog Access).

Step 5 Click Next.

The Gateway Configuration window displays.

Step 6 Enter the appropriate settings, as described in the "Analog Access Gateway Configuration Settings" section.

Step 7 Click Insert.

Step 8 Click Add New Port.

A port configuration dialog opens in a separate window.

Step 9 From the drop-down list box, choose POTS or Loop Start as the port type depending on the gateway model that you are configuring.

Step 10 Enter the appropriate port configuration settings as described in the following sections:

POTS Port Configuration Settings

Loop-Start Port Configuration Settings

Step 11 Click Insert or Insert and Close.

If you have inserted POTS ports, the window refreshes and displays the POTS port in the list on the left side of the window. An Add DN link displays to the right of the new port.

Step 12 To add a directory numbers to an FXS port, click Add DN.

For information about adding and configuring directory numbers, see the "Adding a Directory Number" section on page 59-49 and the "Phone Configuration Settings" section on page 59-13.

Step 13 To apply the changes, click Reset Gateway.


Related Topics

Adding Gateways to Cisco Unified CallManager

Analog Access Gateway Configuration Settings

Adding a Cisco VG248 Analog Phone Gateway

Adding a Cisco VG248 Analog Phone Gateway

The Cisco VG248 Analog Phone Gateway, a standalone, rack-mounted, 48-FXS port product, allows on-premise analog telephones, fax machines, modems, voice-messaging systems, and speakerphones to register with one Cisco Unified CallManager cluster.

The Cisco VG248 connects to a Cisco Unified CallManager by using the Skinny Client Control Protocol to allow for enhanced features.

Cisco Unified CallManager recognizes the Cisco VG248 as a gateway device, called a "Cisco VG248 Gateway." Additionally, Cisco Unified CallManager treats each of the 48 ports as an individual device, similar to a Cisco Unified IP Phone, called a "Cisco VGC Phone."

Use the following procedure to add a Cisco VG248 Gateway and to add and configure ports to the gateway.

Procedure


Step 1 Choose Device > Add a New Device.

The Add a New Device window displays.

Step 2 From the Device type drop-down list box, choose Gateway.

Step 3 Click Next.

The Add a New Gateway window displays.

Step 4 From the Gateway type drop-down list box, choose Cisco VG248 Gateway.

Step 5 Click Next.

The Gateway Configuration window displays.

Step 6 Enter the appropriate settings, as described in the "Cisco VG248 Gateway Configuration Settings" section.

Step 7 Click Insert.

The ports 00 through 48 display in the Endpoint Identifiers list.

Step 8 Click a port.

The Phone Configuration window displays and lists the phone model as VGCPhone. From the Gateway Configuration window, the MAC address automatically displays.

Step 9 Enter the appropriate settings, as described in the "Phone Configuration Settings" section on page 59-13.

Step 10 Click Insert.

Step 11 To configure a directory number for the port, click the VGC line that displays in the list on the left side of the window.

The Directory Number Configuration window displays. For information about adding and configuring directory numbers, see the "Adding a Directory Number" section on page 59-49.

Step 12 To configure more ports for the gateway, click the Gateway Configuration link.

The Gateway Configuration window displays. To configure the phone settings and directory numbers for additional ports, repeat steps 8 through 11.

When you configure port 01, the Configure all Ports like Port 1 button displays on the Gateway Configuration window. This button allows you to configure ports 02 - 48 with the same parameters and settings as port 01, regardless of whether the ports are already configured.

Step 13 To apply the changes, click Reset Phone.


Related Topics

Adding Gateways to Cisco Unified CallManager

Cisco VG248 Gateway Configuration Settings

Phone Configuration Settings, page 59-13

Cisco VG248 Analog Phone Gateway Software Configuration Guide

Gateway Configuration Settings

See the following sections for tables that list detailed descriptions for all gateway configuration fields:

MGCP Gateway Configuration Settings

FXS/FXO Gateway Configuration Settings

E1/T1 PRI Gateway Configuration Settings

BRI Gateway Configuration Settings

T1-CAS Gateway Configuration Settings

H.323 Gateway Configuration Settings

Analog Access Gateway Configuration Settings

Cisco VG248 Gateway Configuration Settings

Cisco IOS SCCP Gateway Configuration Settings

For detailed information about port configuration settings, see the "Port Configuration Settings" section.

MGCP Gateway Configuration Settings

Table 58-2 provides detailed descriptions for MGCP gateway configuration settings.

Table 58-2 MGCP Gateway Configuration Settings 

Field
Description

MGCP Domain Name

Enter a name of up to 64 characters that identifies the Cisco MGCP gateway.

Use the Domain Name Service (DNS) host name if it is configured to resolve correctly; otherwise, use the host name as defined on the Cisco MGCP gateway.

If you are using the host name as it is configured on the IOS gateway, the name that you enter here must match exactly.

For example, if the hostname is configured on the gateway to resolve to vg200-1 and the IP domain name is not configured, enter the hostname in this field (in this case, vg200-1).

If the hostname is configured on the gateway as vg200-1 and the IP domain name is configured on the gateway as cisco.com, enter vg200-1.cisco.com in this field.

Description

Enter a description that clarifies the purpose of the device.

Cisco Unified CallManager Group

From the drop-down list box, choose a Cisco Unified CallManager redundancy group.

A Cisco Unified CallManager redundancy group includes a prioritized list of up to three Cisco Unified CallManagers. The first Cisco Unified CallManager in the list serves as the primary Cisco Unified CallManager. If the primary Cisco Unified CallManager is not available or fails, the gateway attempts to connect with the next Cisco Unified CallManager in the list and so on.

Installed Voice Interface Cards

Note You must specify the beginning port number for some VICs. For example, if the VIC in Subunit 0 begins at 0 and has two ports (0 and 1), then the VIC in Subunit 1 must begin at a port number greater than 1 and have two ports (2 and 3 or 4 and 5).

Note The correct number of slots displays for each model of MGCP gateway. (The VG200 gateway has only one slot.)

Module in Slot 0
Module in Slot 1
Module in Slot 2
Module in Slot 3

(and so on)

For each available slot on the chosen MGCP gateway, choose the type of module installed; for example:

NM-1V—Has one voice interface card (VIC) in Subunit 0 for FXS or FXO. When you use the VIC-2BRI-S/T-TE card with a NM-1V module, you can make two calls, because the second BRI port is shut down.

NM-2V—Has two VICs, one in Subunit 0 and one in Subunit 1 for either FXS or FXO. When you use the VIC-2BRI-S/T-TE card with a NM-2V module, you can make four calls. If another VIC is in the second slot of the NM-2V, the second port on the VIC-2BRI-S/T-TE gets shut down.

NM-HDV—Has one VIC in Subunit 0 for either T1-CAS or T1-PRI, or E1-PRI.

NM-HDA—Has three VICs, one in Subunit 0, one in Subunit 1, and one in Subunit 2.

VWIC-SLOT—Has a slot for any of the following modules: VIC (FXS or FXO), T1-CAS, T1-PRI, or E1-PRI.

AIM-VOICE-30—Has two VICs, one in Subunit 0 and one in Subunit 1 for T1-CAS, T1-PRI, or E1-PRI.

WS-X6600-24FXS—Has 24 FXS ports.

WS-X6600-6T1—Has 6 ports for T1 PRI or CAS.

WS-X6600-6E1—Has 6 ports for E1 PRI.

WS-SVC-CMM-MS—Has 2 port adapters, one for a T1 interface and one for an E1 interface for Europe and other countries.

None—Has no network modules installed.

Product-Specific Configuration

Model-specific configuration fields defined by the gateway manufacturer

The gateway manufacturer specifies the model-specific fields under product-specific configuration. Because they are dynamically configured, they can change without notice.

To view field descriptions and help for product-specific configuration items, click the "i" information icon to the right of the Product Specific Configuration heading to display help in a popup dialog box.

If you need more information, refer to the documentation for the specific gateway that you are configuring or contact the manufacturer.


Related Topics

Adding Gateways to Cisco Unified CallManager

Adding a Cisco IOS MGCP Gateway

Adding a Non-IOS MGCP Gateway

Updating Gateways and Ports

FXS/FXO Gateway Configuration Settings

Table 58-3 provides detailed descriptions for FXS/FXO gateway configuration settings.


Note For the VG200 gateway, not all switch emulation types support the network side. Depending on how you configure the gateway switch type, you may or may not be able to set network side.


Table 58-3 FXS/FXO Gateway Configuration Settings 

Field
Description
Gateway Information

Description

This display-only field contains a string that is generated by Cisco Unified CallManager that uniquely identifies the analog MGCP description.

For example:

AALN/S0/SU1/1@domain.com

You can edit this field.

Device Pool

From the drop-down list box, choose the appropriate device pool.

The device pool specifies a collection of properties for this device including CallManager Group, Date/Time Group, Region, and Calling Search Space for auto registration of devices.

Call Classification

For FXO gateways, this parameter determines whether an incoming call that is using this gateway is considered off the network (OffNet) or on the network (OnNet).

When the Call Classification field is configured as Use System Default, the setting of the Cisco Unified CallManager clusterwide service parameter, Call Classification, determines whether the gateway is OnNet or OffNet.

This field provides an OnNet or OffNet alerting tone when the call is OnNet or OffNet, respectively.

Calling Search Space

From the drop-down list, choose the appropriate calling search space. A calling search space comprises a collection of route partitions that are searched to determine how a collected (originating) number should be routed.

You can configure the number of calling search spaces that display in this drop-down list box by using the Max List Box Items enterprise parameter. If more calling search spaces exist than the Max List Box Items enterprise parameter specifies, the ellipsis button (...) displays next to the drop-down list box. Click the ... button to display the Select Calling Search Space window. Enter a partial calling search space name in the List items where Name contains field. Click the desired calling search space name in the list of calling search spaces that displays in the Select item to use box and click OK.

Note To set the maximum list box items, choose System > Enterprise Parameters and choose CCMAdmin Parameters.

AAR Calling Search Space

Choose the appropriate calling search space for the device to use when it performs automated alternate routing (AAR). The AAR calling search space specifies the collection of route partitions that are searched to determine how to route a collected (originating) number that is otherwise blocked due to insufficient bandwidth.

Media Resource Group List

This list provides a prioritized grouping of media resource groups. An application chooses the required media resource, such as a Music On Hold server, from among the available media resources according to the priority order that is defined in a Media Resource List.

Network Audio Hold Source

This audio source plays when the network initiates a hold action.

Location

Choose the appropriate location for this device. The location specifies the total bandwidth that is available for calls to and from this location. A location setting of None means that the locations feature does not keep track of the bandwidth that this device consumes.

AAR Group

Choose the automated alternate routing (AAR) group for this device. The AAR group provides the prefix digits that are used to route calls that are otherwise blocked due to insufficient bandwidth. An AAR group setting of None specifies that no rerouting of blocked calls will be attempted.

Network Locale

From the drop-down list box, choose the locale that is associated with the gateway. The network locale identifies a set of detailed information to support the hardware in a specific location. The network locale contains a definition of the tones and cadences that the device uses in a specific geographic area.

Note Choose only a network locale that is already installed and supported by the associated devices. The list contains all available network locales for this setting, but not all are necessarily installed. If the device is associated with a network locale that it does not support in the firmware, the device will fail to come up.

Signaling Packet Capture Mode (for Cisco IOS MGCP gateways only)

Configure this field only when you need to troubleshoot encrypted signaling information for the Cisco IOS MGCP gateway. Configuring packet capturing may cause call-processing interruptions. For more information on this field, refer to the Cisco Unified CallManager Security Guide.

Packet Capture Duration (for Cisco IOS MGCP gateways only)

Configure this field only when you need to troubleshoot encrypted signaling information for the Cisco IOS MGCP gateway. Configuring packet capturing may cause call-processing interruptions. For more information on this field, refer to the Cisco Unified CallManager Security Guide.

Port Information

Prefix DN
(for FXS ports)

Enter the prefix digits that are appended to the digits that this trunk receives on incoming calls.

The Cisco Unified CallManager adds prefix digits after first truncating the number in accordance with the Num Digits setting.

Num Digits
(for FXS ports)

Enter the number of significant digits to collect, from 0 to 32.

Cisco Unified CallManager counts significant digits from the right (last digit) of the number called.

Use this field for the processing of incoming calls and to indicate the number of digits starting from the last digit of the called number that are used to route calls that are coming into the PRI span. See Prefix DN.

Expected Digits
(for FXS ports)

Enter the number of digits that are expected on the inbound side of the trunk. For this rarely used field, leave zero as the default value if you are unsure.

Port Direction
(for FXO ports)

Choose the direction of calls that are passing through this port:

Inbound—Use for incoming calls only.

Outbound—Use for outgoing calls.

Bothways—Use for inbound and outbound calls (default).

Attendant DN
(for FXO ports)

Enter the directory number to which you want incoming calls routed; for example, zero or a directory number for an attendant.

Product-Specific Configuration

Model-specific configuration fields defined by the gateway manufacturer

The gateway manufacturer specifies the model-specific fields under product-specific configuration. Because they are dynamically configured, they can change without notice.

To view field descriptions and help for product-specific configuration items, click the "i" information icon to the right of the Product Specific Configuration heading to display help in a popup dialog box.

If you need more information, refer to the documentation for the specific gateway that you are configuring or contact the manufacturer.


Related Topics

Adding FXS Ports to an MGCP Gateway

Adding FXO Ports to an MGCP Gateway

Adding Gateways to Cisco Unified CallManager

Adding a Cisco IOS MGCP Gateway

Adding a Non-IOS MGCP Gateway

Updating Gateways and Ports

E1/T1 PRI Gateway Configuration Settings

Table 58-4 provides detailed descriptions for E1/T1 PRI configuration settings.


Note To determine whether your gateway supports the QSIG protocol, refer to the gateway product documentation. For information on QSIG support with Cisco Unified CallManager, refer to the "Q.Signaling (QSIG)" section on page 37-9.


Table 58-4 E1/T1 PRI Configuration Settings 

Field
Description
Device Information

Domain Name (MGCP gateways)

For MGCP gateways, this display-only field contains a string that Cisco Unified CallManager generates that uniquely identifies the MGCP endpoint.

For example:

S1/DS1-0@VG200-2

S1 indicates slot 1, DS1-0 designates the digital interface, and @VG200-2 designates the MGCP domain name.

MAC Address

Enter the MAC address of the gateway device.

Description

Enter a description that clarifies the purpose of the device.

Device Pool

From the drop-down list box, choose the appropriate device pool.

The device pool specifies a collection of properties for this device including CallManager Group, Date/Time Group, Region, and Calling Search Space for auto-registration of devices.

Call Classification

This parameter determines whether an incoming call that is using this gateway is considered off the network (OffNet) or on the network (OnNet).

When the Call Classification field is configured as Use System Default, the setting of the Cisco Unified CallManager clusterwide service parameter, Call Classification, determines whether the gateway is OnNet or OffNet.

This field provides an OnNet or OffNet alerting tone when the call is OnNet or OffNet, respectively.

Network Locale

From the drop-down list box, choose the locale that is associated with the gateway. The network locale identifies a set of detailed information to support the hardware in a specific location. The network locale contains a definition of the tones and cadences that the device uses in a specific geographic area.

Note Choose only a network locale that is already installed and supported by the associated devices. The list contains all available network locales for this setting, but not all are necessarily installed. If the device is associated with a network locale that it does not support in the firmware, the device will fail to come up.

Signaling Packet Capture Mode (for Cisco IOS MGCP gateways only)

Configure this field only when you need to troubleshoot encrypted signaling information for the Cisco IOS MGCP gateway. Configuring packet capturing may cause call-processing interruptions. For more information on this field, refer to the Cisco Unified CallManager Security Guide.

Packet Capture Duration (for Cisco IOS MGCP gateways only)

Configure this field only when you need to troubleshoot encrypted signaling information for the Cisco IOS MGCP gateway. Configuring packet capturing may cause call-processing interruptions. For more information on this field, refer to the Cisco Unified CallManager Security Guide.

Media Resource Group List

This list provides a prioritized grouping of media resource groups. An application chooses the required media resource, such as a Music On Hold server, from among the available media resources according to the priority order that a Media Resource List defines.

Location

Choose the appropriate location for this device. The location specifies the total bandwidth that is available for calls to and from this location. A location setting of None means that the locations feature does not keep track of the bandwidth that this device consumes.

AAR Group

Choose the automated alternate routing (AAR) group for this device. The AAR group provides the prefix digits that are used to route calls that are otherwise blocked due to insufficient bandwidth. An AAR group setting of None specifies that no rerouting of blocked calls will be attempted.

Load Information

Enter the appropriate firmware load information for the gateway.

The value that you enter here overrides the default firmware load for this gateway type.

V150 (subset)

Check this box to enable v150 (subset) modem relay support on the gateways. IP-STEs currently use this feature to support end-to-end secure calls to an ISDN-STE. (Applies only to T1 PRI and T1 CAS.)

The default value specifies unchecked.

Multilevel Precedence and Preemption (MLPP) Information

MLPP Domain (e.g., "0000FF")

Enter a hexadecimal value between 0 and FFFFFF for the MLPP domain that is associated with this device. If you leave this field blank, this device inherits its MLPP domain from the value that is set for the device pool of the device. If the device pool does not have an MLPP Domain setting, this device inherits its MLPP Domain from the value that is set for the MLPP Domain Identifier enterprise parameter.

MLPP Indication

If available, this setting specifies whether a device that is capable of playing precedence tones will use the capability when it places an MLPP precedence call.

From the drop-down list box, choose a setting to assign to this device from the following options:

Default—This device inherits its MLPP indication setting from its device pool.

Off—This device does not handle nor process indication of an MLPP precedence call.

On—This device does handle and process indication of an MLPP precedence call.

Note Do not configure a device with the following combination of settings: MLPP Indication is set to Off or Default (when default is Off) while MLPP Preemption is set to Forceful.

MLPP Preemption

If available, this setting specifies whether a device that is capable of preempting calls in progress will use the capability when it places an MLPP precedence call.

From the drop-down list box, choose a setting to assign to this device from the following options:

Default—This device inherits its MLPP preemption setting from its device pool.

Disabled—This device does not allow preemption of lower precedence calls to take place when necessary for completion of higher precedence calls.

Forceful—This device allows preemption of lower precedence calls to take place when necessary for completion of higher precedence calls.

Note Do not configure a device with the following combination of settings: MLPP Indication is set to Off or Default (when default is Off) while MLPP Preemption is set to Forceful.

Interface Information

PRI Protocol Type

Choose the communications protocol for the span.

T1 PRI spans include several options, depending on the carrier or switch; for example

PRI 4ESS—AT&T Interexchange carrier

PRI 5E8—AT&T family 5ESS ISDN switch that runs in NI-1 or custom mode.

PRI 5E8 Custom—Cisco Unified IP Phone

PRI 5E9—AT&T family local exchange switch or carrier

PRI DMS—MCI family local exchange switch or carrier; Canadian local exchange carrier

PRI ETSI SC—European local exchange carrier on T1; also, Japanese, Taiwan, Korean, and Hong Kong local exchange.

PRI NI2—AT&T family local exchange switch or carrier


Note If you specify the PRI NI2 PRI protocol type, configure the Cisco IOS gateway with the following command:
isdn switch-type primary-ni


PRI NTT—Japanese NTT exchange switch

PRI ISO QSIG T1—PBX T1 tie trunk using ISO QSIG

PRI ISO QSIG E1—PBX E1 tie trunk using ISO QSIG

Determine the switch to which you are connecting and the preferred protocol; for example

Nortel Meridian—DMS, 5E8 Custom

Lucent Definity—4ESS or 5E8

Madge (Teleos) box—5E8 Teleos

Intecom PBX—5E8 Intecom

Protocol Side

Choose the appropriate protocol side. This setting specifies whether the gateway connects to a Central Office/Network device or to a User device.

Make sure that the two ends of the PRI connection use opposite settings. For example, if you connect to a PBX and the PBX uses User as its protocol side, choose Network for this device. Typically, use User for this option for central office connections.

Channel Selection Order

Choose the order in which channels or ports are enabled from first (lowest number port) to last (highest number port), or from last to first.

Valid entries include TOP_DOWN (first to last) or BOTTOM_UP (last to first). If you are not sure which port order to use, choose TOP_DOWN.

Channel IE Type

Choose one of the following values to specify whether channel selection is presented as a channel map or a slot map:

Timeslot Number—B-channel usage always indicates actual timeslot map format (such as 1-15 and 17-31 for E1).

Slotmap—B-channel usage always indicates a slot map format.

Use Number When 1B—Channel usage indicates a channel map for one B-channel but indicates a slot map if more than one B-channel exists.

Continuous Number—Configures a continuous range of slot numbers (1-30) as the E1 logical channel number instead of the noncontinuous actual timeslot number (1-15 and 17-31).

PCM Type

Specify the digital encoding format. Choose one of the following formats:

a-law: Use for Europe and other countries, except North America, Hong Kong, Taiwan, and Japan.

mu-law: Use for North America, Hong Kong, Taiwan, and Japan.

Delay for first restart (1/8 sec ticks)

Enter the rate at which the spans are brought in service. The delay occurs when many PRI spans are enabled on a system and the Inhibit Restarts at PRI Initialization check box is unchecked. For example, set the first five cards to 0 and set the next five cards to 16. (Wait 2 seconds before bringing them in service.)

Delay between restarts (1/8 sec ticks)

Enter the time between restarts. The delay occurs when a PRI RESTART gets sent if the Inhibit Restarts check box is unchecked.

Inhibit restarts at PRI initialization

A RESTART or SERVICE message confirms the status of the ports on a PRI span. If RESTART or SERVICE messages are not sent, Cisco Unified CallManager assumes the ports are in service.

When the D-Channel successfully connects with another PRI D-Channel, it sends a RESTART or SERVICE message when this check box is unchecked.

Enable status poll

Check the check box to enable the Cisco Unified CallManager advanced service parameter, Change B-Channel Maintenance Status. This service parameter allows you to take individual B-channels out of service for an MGCP T1/E1 PRI gateway in real time.

Uncheck this check box to disable the service parameter "Change B-Channel Maintenance Status."

Note Default leaves this field unchecked.

Call Routing Information
Inbound Calls

Significant Digits

Choose the number of significant digits to collect, from 0 to 32 or All. Cisco Unified CallManager counts significant digits from the right (last digit) of the number called. If you choose All, the Cisco Unified CallManager does not truncate the inbound number.

EXAMPLE
Digits received are 123456.
Significant digits setting is 4.
Digits translated are 3456.

Use for the processing of incoming calls and to indicate the number of digits, starting from the last digit of the called number, that are used to route calls that are coming into the PRI span. See Prefix DN.

Calling Search Space

From the drop-down list box, choose the appropriate calling search space. A calling search space designates a collection of route partitions that are searched to determine how a collected (originating) number should be routed.

You can configure the number of calling search spaces that display in this drop-down list box by using the Max List Box Items enterprise parameter. If more calling search spaces exist than the Max List Box Items enterprise parameter specifies, the ellipsis button (...) displays next to the drop-down list box. Click the ... button to display the Select Calling Search Space window. Enter a partial calling search space name in the List items where Name contains field. Click the desired calling search space name in the list of calling search spaces that displays in the Select item to use box and click OK.

Note To set the maximum list box items, choose System > Enterprise Parameters and choose CCMAdmin Parameters.

AAR Calling Search Space

Choose the appropriate calling search space for the device to use when automated alternate routing (AAR) is performed. The AAR calling search space specifies the collection of route partitions that are searched to determine how to route a collected (originating) number that is otherwise blocked due to insufficient bandwidth.

Prefix DN

Enter the prefix digits that are appended to the digits that this trunk receives on incoming calls.

The Cisco Unified CallManager adds prefix digits after first truncating the number in accordance with the Num Digits setting.

Outbound Calls

Calling Line ID Presentation

Choose whether you want the Cisco Unified CallManager to allow or restrict the display of the calling party phone number.

Choose Default if you do not want to change calling line ID presentation. Choose Allowed if you want Cisco Unified CallManager to send "Calling Line ID Allowed" on outbound calls. Choose Restricted if you want Cisco Unified CallManager to send "Calling Line ID Restricted" on outbound calls.

For more information about this field, see Table 15-6 in the "Calling Party Number Transformations Settings" section in the Cisco Unified CallManager System Guide.

Calling Party Selection

Any outbound call on a gateway can send directory number information. Choose which directory number is sent:

Originator—Send the directory number of the calling device.

First Redirect Number—Send the directory number of the redirecting device.

Last Redirect Number—Send the directory number of the last device to redirect the call.

First Redirecting Party (External)—Send the directory number of the first redirecting device with the external phone mask applied.

Last Redirecting Party (External)—Send the directory number of the last redirecting device with the external phone mask applied.

Called party IE number type unknown

Choose the format for the number type in called party directory numbers.

Cisco Unified CallManager sets the called directory number (DN) type. Cisco recommends that you do not change the default value unless you have advanced experience with dialing plans such as NANP or the European dialing plan. You may need to change the default in Europe because Cisco Unified CallManager does not recognize European national dialing patterns. You can also change this setting when you are connecting to a PBX that expects the called directory number to be encoded to a non-national type numbering plan.

Choose one of the following options:

CallManager—The Cisco Unified CallManager sets the directory number type.

International—Use when you are dialing outside the dialing plan for your country.

National—Use when you are dialing within the dialing plan for your country.

Unknown—The dialing plan is unknown.

Calling party IE number type unknown

Choose the format for the number type in calling party directory numbers.

Cisco Unified CallManager sets the calling directory number (DN) type. Cisco recommends that you do not change the default value unless you have advanced experience with dialing plans such as NANP or the European dialing plan. You may need to change the default in Europe because Cisco Unified CallManager does not recognize European national dialing patterns. You can also change this setting when you are connecting to a PBX that expects the calling directory number to be encoded to a non-national type numbering plan.

Choose one of the following options:

CallManager—The Cisco Unified CallManager sets the directory number type.

International—Use when you are dialing outside the dialing plan for your country.

National—Use when you are dialing within the dialing plan for your country.

Unknown—The dialing plan is unknown.

Called Numbering Plan

Choose the format for the numbering plan in called party directory numbers.

Cisco Unified CallManager sets the called DN numbering plan. Cisco recommends that you do not change the default value unless you have advanced experience with dialing plans such as NANP or the European dialing plan. You may need to change the default in Europe because Cisco Unified CallManager does not recognize European national dialing patterns. You can also change this setting when you are connecting to PBXs by using routing as a non-national type number.

Choose one of the following options:

CallManager—Cisco Unified CallManager sets the Numbering Plan in the directory number.

ISDN—Use when you are dialing outside the dialing plan for your country.

National Standard—Use when you are dialing within the dialing plan for your country.

Private—Use when you are dialing within a private network.

Unknown—The dialing plan is unknown.

Calling Numbering Plan

Choose the format for the numbering plan in calling party directory numbers.

Cisco Unified CallManager sets the calling DN numbering plan. Cisco recommends that you do not change the default value unless you have advanced experience with dialing plans such as NANP or the European dialing plan. You may need to change the default in Europe because Cisco Unified CallManager does not recognize European national dialing patterns. You can also change this setting when you are connecting to PBXs by using routing as a non-national type number.

Choose one of the following options:

CallManager—Cisco Unified CallManager sets the Numbering Plan in the directory number.

ISDN—Use when you are dialing outside the dialing plan for your country.

National Standard—Use when you are dialing within the dialing plan for your country.

Private—Use when you are dialing within a private network.

Unknown—The dialing plan is unknown.

Number of digits to strip

Choose the number of digits to strip on outbound calls, from 0 to 32.

For example, when 8889725551234 is dialed, and the number of digits to strip is 3, Cisco Unified CallManager strips 888 from the outbound number.

Caller ID DN

Enter the pattern that you want to use for calling line ID, from 0 to 24 digits.

For example, in North America:

555XXXX = Variable calling line ID, where X equals an extension number. The CO appends the number with the area code if you do not specify it.

5555000 = Fixed calling line ID, where you want the Corporate number to be sent instead of the exact extension from which the call is placed. The CO appends the number with the area code if you do not specify it.

SMDI Base Port

Enter the first SMDI port number of the T1 span.

Type Specific Information

Display IE Delivery

Check the check box to enable delivery of the display information element (IE) in SETUP, and NOTIFY messages (for DMS protocol) for the calling and connected party name delivery service.

Note Default leaves the check box checked.

Redirecting Number IE Delivery— Outbound

Check this check box to indicate the first redirecting number and the redirecting reason of the call when the call is forwarded. (The UUIE part of the outgoing SETUP message from the Cisco Unified CallManager includes the Redirecting Number IE.)

Uncheck the check box to exclude the first redirecting number and the redirecting reason.

You use Redirecting Number IE for voice-messaging integration only. If your configured voice-messaging system supports Redirecting Number IE, you should check the check box.

Note Default leaves the check box checked.

Redirecting Number IE Delivery— Inbound

Check this check box to accept the Redirecting Number IE in the incoming SETUP message to the Cisco Unified CallManager. (The UUIE part of the SETUP message includes the Redirecting Number IE.)

Uncheck the check box to exclude the Redirecting Number IE.

You use Redirecting Number IE for voice-messaging integration only. If your configured voice-messaging system supports Redirecting Number IE, you should check the check box.

Note Default leaves the check box checked.

Send Extra Leading Character in DisplayIE

Check this check box to include a special leading character byte (non ASCII, nondisplayable) in the DisplayIE field.

Uncheck this check box to exclude this character byte from the DisplayIE field.

This check box only applies to the DMS-100 protocol and the DMS-250 protocol.

Default leaves this setting disabled (unchecked).

Setup non-ISDN Progress Indicator IE Enable

Default leaves this setting disabled (unchecked).

Enable this setting only if users are not receiving ringback tones on outbound calls.

When this setting is enabled, Cisco Unified CallManager sends Q.931 Setup messages out digital (that is, non-H.323) gateways with the Progress Indicator field set to non-ISDN.

This message notifies the destination device that the Cisco Unified CallManager gateway is non-ISDN and that the destination device should play in-band ringback.

This problem usually associates with Cisco Unified CallManagers that connect to PBXs through digital gateways.

MCDN Channel Number Extension Bit Set to Zero

To set the channel number extension bit to zero, check the check box. To set the extension bit to 1, uncheck the check box.

This setting only applies to the DMS-100 protocol

Send Calling Name in Facility IE

Check the check box to send the calling name in the Facility IE field. By default, Cisco Unified CallManager leaves the check box unchecked.

Set this feature for a private network that has a PRI interface enabled for ISDN calling name delivery. When this check box is checked, the calling party name gets sent in the Facility IE of the SETUP or FACILITY message, so the name can display on the called party device.

Set this feature for PRI trunks in a private network only. Do not set this feature for PRI trunks that are connected to the PSTN.

Note This field applies to the NI2 protocol only.

Interface Identifier Present

Check the check box to indicate that an interface identifier is present. By default, Cisco Unified CallManager leaves the check box unchecked.

This setting only applies to the DMS-100 protocol for digital access gateways in the Channel Identification information element (IE) of the SETUP, CALL PROCEEDING, ALERTING, and CONNECT messages.

Interface Identifier Value

Enter the value that was obtained from the PBX provider.

This field applies to only the DMS-100 protocol. Valid values range from 0 to 255.

Connected Line ID Presentation (QSIG Inbound Call)

Choose whether you want Cisco Unified CallManager to allow or block the connected party phone number from displaying on an inbound caller phone.

This field applies only to gateways that are using QSIG protocol. The gateway applies this setting for incoming calls only.

Choose Default if you do not want to change the connected line ID presentation. Choose Allowed if you want Cisco Unified CallManager to send "Connected Line ID Allowed" to enable the connected party number to display for the calling party. Choose Restricted if you want Cisco Unified CallManager to send "Connected Line ID Restricted" to block the connected party number from displaying for the calling party.

For more information about this field, see Table 15-9 in the "Connected Party Presentation and Restriction Settings" section in the Cisco Unified CallManager System Guide.

UUIE Configuration

Passing Precedence Level Through UUIE

Check this check box to enable passing MLPP information through the PRI 4ESS UUIE field. The system uses this box for interworking with DRSN switch.

The system makes this check box available only if the PRI Protocol Type value of PRI 4ESS is specified for this gateway.

The default value specifies unchecked.

Security Access Level

Enter the value for the security access level. Valid values include 00 through 99. The system makes this field available only if the Passing Precedence Level Through UUIE check box is checked. The default value specifies 2.

Product-Specific Configuration

Model-specific configuration fields that are defined by the gateway manufacturer

The gateway manufacturer specifies the model-specific fields under product-specific configuration. Because they are dynamically configured, they can change without notice.

To view field descriptions and help for product-specific configuration items, click the "i" information icon to the right of the Product Specific Configuration heading to display help in a popup dialog box.

If you need more information, refer to the documentation for the specific gateway that you are configuring or contact the manufacturer.


Related Topics

Adding a Non-IOS MGCP Gateway

Adding Gateways to Cisco Unified CallManager

Updating Gateways and Ports

Gateway Configuration Settings

Adding a BRI Port to an MGCP Gateway

BRI Gateway Configuration Settings

Table 58-5 provides detailed descriptions for BRI configuration settings.

Table 58-5 BRI Configuration Settings 

Field
Description
Device Information

End-Point Name (MGCP gateways)

For MGCP gateways, this display-only field contains a string that Cisco Unified CallManager generates that uniquely identifies the MGCP endpoint.

For example:

BRI/S1/SU0/P0@SC3640.cisco.com

S1 indicates slot 1, SU0 indicates subunit 0, P0 indicates port 0, and @SC3640.cisco.com designates the MGCP domain name.

Description

Enter a description that clarifies the purpose of the device.

Device Pool

From the drop-down list box, choose the appropriate device pool.

For this device, the device pool specifies a collection of properties that includes CallManager Group, Date/Time Group, Region, and Calling Search Space for auto-registration of devices.

Call Classification

This parameter determines whether an incoming call that is using this gateway is considered off the network (OffNet) or on the network (OnNet).

When the Call Classification field is configured as Use System Default, the setting of the Cisco Unified CallManager clusterwide service parameter, Call Classification, determines whether the gateway is OnNet or OffNet.

This field provides an OnNet or OffNet alerting tone when the call is OnNet or OffNet, respectively.

Network Locale

From the drop-down list box, choose the locale that is associated with the gateway. The network locale identifies a set of detailed information to support the hardware in a specific location. The network locale contains a definition of the tones and cadences that devises use in a specific geographic area.

Signaling Packet Capture Mode (for Cisco IOS MGCP gateways only)

Configure this field only when you need to troubleshoot encrypted signaling information for the Cisco IOS MGCP gateway. Configuring packet capturing may cause call-processing interruptions. For more information on this field, refer to the Cisco Unified CallManager Security Guide.

Packet Capture Duration (for Cisco IOS MGCP gateways only)

Configure this field only when you need to troubleshoot encrypted signaling information for the Cisco IOS MGCP gateway. Configuring packet capturing may cause call-processing interruptions. For more information on this field, refer to the Cisco Unified CallManager Security Guide.

Media Resource Group List

This list provides a prioritized grouping of media resource groups. An application chooses the required media resource, such as a Music On Hold server, from among the available media resources according to the priority order that a Media Resource List defines.

Location

Choose the appropriate location for this device. The location specifies the total bandwidth that is available for calls to and from this location. A location setting of None means that the locations feature does not keep track of the bandwidth that this device consumes.

AAR Group

Choose the automated alternate routing (AAR) group for this device. The AAR group provides the prefix digits that are used to route calls that are otherwise blocked due to insufficient bandwidth. An AAR group setting of None specifies that no rerouting of blocked calls will be attempted.

Load Information

Enter the appropriate firmware load information for the gateway.

The value that you enter here overrides the default firmware load for this gateway type.

Interface Information

BRI Protocol Type

Choose the communications protocol for the span.

BRI-NET3

Protocol Side

Choose the appropriate protocol side. This setting specifies whether the gateway connects to a Central Office/Network device or to a User device.

Note BRI supports only the User side.

Channel Selection Order

Choose the order in which channels or ports are enabled from first (lowest number port) to last (highest number port) or from last to first.

Valid entries include TOP_DOWN (first to last) or BOTTOM_UP (last to first). If you are not sure which port order to use, choose TOP_DOWN.

PCM Type

Specify the digital encoding format. Choose one of the following formats:

a-law: Use for Europe and other countries, except North America, Hong Kong, Taiwan, and Japan.

mu-law: Use for North America, Hong Kong, Taiwan, and Japan.

Delay for First Restart (1/8 sec ticks)

Enter the rate at which the spans are brought in service. The delay occurs when many BRI spans are enabled on a system and the Inhibit Restarts at BRI Initialization check box is unchecked. For example, set the first five cards to 0 and set the next five cards to 16. (Wait 2 seconds before bringing them in service.)

Delay Between Restarts (1/8 sec ticks)

Enter the time between restarts. The delay occurs when a BRI RESTART gets sent if the Inhibit Restarts check box is unchecked.

Inhibit Restarts at BRI Initialization

A RESTART message confirms the status of the ports on a BRI span. If RESTART messages are not sent, Cisco Unified CallManager assumes that the ports are in service.

When the data link successfully connects with another BRI data link, it sends a RESTART message when this check box is unchecked.

Enable Status Poll

Check the check box to view the B-channel status in the debug window.

Establish Datalink on First Call

Cisco Unified CallManager establishes the data link to the gateway when the gateway registers with Cisco Unified CallManager.

When you configure the gateway and switch to negotiate the TEI (terminal endpoint identifier) on the first call, you can check the check box to establish the data link on the first call.

Note Default leaves the check box unchecked.

Call Routing Information
Inbound Calls

Significant Digits

Choose the number of significant digits to collect, from 0 to 32 or All. Cisco Unified CallManager counts significant digits from the right (last digit) of the number called. If you choose All, Cisco Unified CallManager does not truncate the inbound number.

EXAMPLE
Digits received are 123456.
Significant digits setting is 4.
Digits translated are 3456.

Use for the processing of incoming calls and to indicate the number of digits, starting from the last digit of the called number, that are used to route calls that are coming into the BRI span. See Prefix DN.

Calling Search Space

Choose the appropriate calling search space. A calling search space designates a collection of route partitions that are searched to determine how a collected (originating) number should be routed.

AAR Calling Search Space

Choose the appropriate calling search space for the device to use when automated alternate routing (AAR) is performed. The AAR calling search space specifies the collection of route partitions that are searched to determine how to route a collected (originating) number that is otherwise blocked due to insufficient bandwidth.

Prefix DN

Enter the prefix digits that are appended to the digits that this trunk receives on incoming calls.

Cisco Unified CallManager adds prefix digits after first truncating the number in accordance with the Num Digits setting.

Outbound Calls

Calling Party Presentation

Choose whether you want Cisco Unified CallManager to transmit or block caller ID.

Choose Default if you do not want to change calling party presentation. Choose Allowed if you want Cisco Unified CallManager to send caller ID. Choose Restricted if you do not want Cisco Unified CallManager to send caller ID.

Calling Party Selection

Any outbound call on a gateway can send directory number information. Choose which directory number is sent:

Originator—Send the directory number of the calling device.

First Redirect Number—Send the directory number of the redirecting device.

Last Redirect Number—Send the directory number of the last device to redirect the call.

First Redirecting Party (External)—Send the directory number of the first redirecting device with the external phone mask applied.

Last Redirecting Party (External)—Send the directory number of the last redirecting device with the external phone mask applied.

Called party IE number type unknown

Choose the format for the number type in called party directory numbers.

Cisco Unified CallManager sets the called directory number (DN) type. Cisco recommends that you do not change the default value unless you have advanced experience with dialing plans such as NANP or the European dialing plan. You may need to change the default in Europe because Cisco Unified CallManager does not recognize European national dialing patterns. You can also change this setting when you are connecting to a PBX that expects the called directory number to be encoded to a non-national numbering plan type.

Choose one of the following options:

CallManager—Cisco Unified CallManager sets the directory number type.

International—Use when you are dialing outside the dialing plan for your country.

National—Use when you are dialing within the dialing plan for your country.

Unknown—The dialing plan is unknown.

Subscriber—Use when you are dialing a subscriber by using a shortened subscriber number.

Calling party IE number type unknown

Choose the format for the number type in calling party directory numbers.

Cisco Unified CallManager sets the calling directory number (DN) type. Cisco recommends that you do not change the default value unless you have advanced experience with dialing plans such as NANP or the European dialing plan. You may need to change the default in Europe because Cisco Unified CallManager does not recognize European national dialing patterns. You can also change this setting when you are connecting to a PBX that expects the calling directory number to be encoded to a non-national numbering plan type.

Choose one of the following options:

CallManager—Cisco Unified CallManager sets the directory number type.

International—Use when you are dialing outside the dialing plan for your country.

National—Use when you are dialing within the dialing plan for your country.

Unknown—The dialing plan is unknown.

Subscriber—Use when you are dialing a subscriber by using a shortened subscriber number.

Called Numbering Plan

Choose the format for the numbering plan in called party directory numbers.

Cisco Unified CallManager sets the called DN numbering plan. Cisco recommends that you do not change the default value unless you have advanced experience with dialing plans such as NANP or the European dialing plan. You may need to change the default in Europe because Cisco Unified CallManager does not recognize European national dialing patterns. You can also change this setting when you are connecting to PBXs by using routing as a non-national type number.

Choose one of the following options:

CallManager—Cisco Unified CallManager sets the Numbering Plan in the directory number.

ISDN—Use when you are dialing outside the dialing plan for your country.

National Standard—Use when you are dialing within the dialing plan for your country.

Private—Use when you are dialing within a private network.

Unknown—The dialing plan is unknown.

Subscriber—Use when you are dialing a subscriber by using a shortened subscriber number.

Calling Numbering Plan

Choose the format for the numbering plan in calling party directory numbers.

Cisco Unified CallManager sets the calling DN numbering plan. Cisco recommends that you do not change the default value unless you have advanced experience with dialing plans such as NANP or the European dialing plan. You may need to change the default in Europe because Cisco Unified CallManager does not recognize European national dialing patterns. You can also change this setting when you are connecting to PBXs by using routing as a non-national type number.

Choose one of the following options:

CallManager—Cisco Unified CallManager sets the Numbering Plan in the directory number.

ISDN—Use when you are dialing outside the dialing plan for your country.

National Standard—Use when you are dialing within the dialing plan for your country.

Private—Use when you are dialing within a private network.

Unknown—The dialing plan is unknown.

Subscriber—Use when you are dialing a subscriber by using a shortened subscriber number.

Number of digits to strip

Choose the number of digits to strip on outbound calls, from 0 to 32.

For example, when 8889725551234 is dialed, and the number of digits to strip is 3, Cisco Unified CallManager strips 888 from the outbound number.

Caller ID DN

Enter the pattern that you want to use for caller ID, from 0 to 24 digits.

For example, in North America:

555XXXX = Variable caller ID, where X equals an extension number. The CO appends the number with the area code if you do not specify it.

5555000 = Fixed caller ID, where you want the Corporate number to be sent instead of the exact extension from which the call is placed. The CO appends the number with the area code if you do not specify it.

BRI Protocol Type Specific Information

Redirecting Number IE Delivery— Outbound

Check this check box to indicate the first redirecting number and the redirecting reason of the call when the call is forwarded. (The UUIE part of the outgoing SETUP message from the Cisco Unified CallManager includes the Redirecting Number IE.)

Uncheck the check box to exclude the first redirecting number and the redirecting reason.

You use Redirecting Number IE for voice-messaging integration only. If your configured voice-messaging system supports Redirecting Number IE, you should check the check box.

Note Default leaves the check box checked.

Redirecting Number IE Delivery— Inbound

Check this check box to accept the Redirecting Number IE in the incoming SETUP message to the Cisco Unified CallManager. (The UUIE part of the SETUP message includes the Redirecting Number IE.)

Uncheck the check box to exclude the Redirecting Number IE.

You use Redirecting Number IE for voice-messaging integration only. If your configured voice-messaging system supports Redirecting Number IE, you should check the check box.

Note Default leaves the check box checked.

Setup non-ISDN Progress Indicator IE Enable

Default leaves this setting disabled (unchecked).

Enable this setting only if users are not receiving ringback tones on outbound calls.

When this setting is enabled, Cisco Unified CallManager sends Q.931 Setup messages out digital (that is, non-H.323) gateways with the Progress Indicator field set to non-ISDN.

This message notifies the destination device that the Cisco Unified CallManager gateway is non-ISDN and that the destination device should play in-band ringback.

This problem usually associates with Cisco Unified CallManagers that connect to PBXs through digital gateways.

Product-Specific Configuration

Model-specific configuration fields that are defined by the gateway manufacturer

The model-specific fields under product-specific configuration define the gateway manufacturer. Because they are dynamically configured, they can change without notice.

To view field descriptions and help for product-specific configuration items, click the "i" information icon to the right of the Product Specific Configuration heading to display help in a popup dialog box.

If you need more information, refer to the documentation for the specific gateway that you are configuring or contact the manufacturer.


Related Topics

MGCP BRI Call Connections, Cisco Unified CallManager System Guide

Gateway Configuration Checklist, Cisco Unified CallManager System Guide

T1-CAS Gateway Configuration Settings

Table 58-6 provides detailed descriptions for T1-CAS configuration settings.

Table 58-6 T1-CAS Configuration Settings 

Field
Description

MAC Address

(non-IOS gateway)

Enter MAC address of the gateway. The MAC address uniquely identifies the hardware device.

You must enter a 12-hexadecimal character value.

Domain Name

For MGCP gateways, this display-only field contains a string that Cisco Unified CallManager generates that uniquely identifies the MGCP digital interface.

For example:

S1/DS1-0@VG200-2

S1 indicates slot 1, DS1-0 designates the digital interface, and @VG200-2 designates the MGCP domain name.

Note Enter either a MAC address or a domain name, whichever applies.

Description

Enter a description that clarifies the purpose of the device.

Device Pool

From the drop-down list box, choose the appropriate device pool.

The device pool specifies a collection of properties for this device including CallManager Group, Date/Time Group, Region, and Calling Search Space for auto-registration of devices.

Call Classification

This parameter determines whether an incoming call that is using this gateway is considered off the network (OffNet) or on the network (OnNet).

When the Call Classification field is configured as Use System Default, the setting of the Cisco Unified CallManager clusterwide service parameter, Call Classification, determines whether the gateway is OnNet or OffNet.

This field provides an OnNet or OffNet alerting tone when the call is OnNet or OffNet, respectively.

Media Resource Group List

This list provides a prioritized grouping of media resource groups. An application chooses the required media resource, such as a Music On Hold server, from among the available media resources according to the priority order that is defined in a Media Resource List.

Calling Search Space

From the drop-down list box, choose the appropriate calling search space. A calling search space designates a collection of route partitions that are searched to determine how a collected (originating) number should be routed.

You can configure the number of calling search spaces that display in this drop-down list box by using the Max List Box Items enterprise parameter. If more calling search spaces exist than the Max List Box Items enterprise parameter specifies, the ellipsis button (...) displays next to the drop-down list box. Click the ... button to display the Select Calling Search Space window. Enter a partial calling search space name in the List items where Name contains field. Click the desired calling search space name in the list of calling search spaces that displays in the Select item to use box and click OK.

Note To set the maximum list box items, choose System > Enterprise Parameters and choose CCMAdmin Parameters.

AAR Calling Search Space

Choose the appropriate calling search space for the device to use when automated alternate routing (AAR) is performed. The AAR calling search space specifies the collection of route partitions that are searched to determine how to route a collected (originating) number that is otherwise blocked due to insufficient bandwidth.

Location

Choose the appropriate location for this device. The location specifies the total bandwidth that is available for calls to and from this location. A location setting of None means that the locations feature does not keep track of the bandwidth that this device consumes.

AAR Group

Choose the automated alternate routing (AAR) group for this device. The AAR group provides the prefix digits that are used to route calls that are otherwise blocked due to insufficient bandwidth. An AAR group setting of None specifies that no rerouting of blocked calls will be attempted.

MLPP Domain (e.g., "0000FF")

Enter a hexadecimal value between 0 and FFFFFF for the MLPP domain that is associated with this device. If you leave this field blank, this device inherits its MLPP domain from the value that is set for the device pool of the device. If the device pool does not have an MLPP Domain setting, this device inherits its MLPP Domain from the value that is set for the MLPP Domain Identifier enterprise parameter.

MLPP Indication

If available, this setting specifies whether a device that is capable of playing precedence tones will use the capability when it places an MLPP precedence call.

From the drop-down list box, choose a setting to assign to this device from the following options:

Default—This device inherits its MLPP indication setting from its device pool.

Off—This device does not handle nor process indication of an MLPP precedence call.

On—This device does handle and process indication of an MLPP precedence call.

Note Do not configure a device with the following combination of settings: MLPP Indication is set to Off or Default (when default is Off) while MLPP Preemption is set to Forceful.

MLPP Preemption

If available, this setting specifies whether a device that is capable of preempting calls in progress will use the capability when it places an MLPP precedence call.

From the drop-down list box, choose a setting to assign to this device from the following options:

Default—This device inherits its MLPP preemption setting from its device pool.

Disabled—This device does not allow preemption of lower precedence calls to take place when necessary for completion of higher precedence calls.

Forceful—This device allows preemption of lower precedence calls to take place when necessary for completion of higher precedence calls.

Note Do not configure a device with the following combination of settings: MLPP Indication is set to Off or Default (when default is Off) while MLPP Preemption is set to Forceful.

Handle DTMF Precedence Signals

Check this box to enable this gateway to interpret special DTMF signals as MLPP precedence levels.

Load Information

Enter the appropriate firmware load information for the gateway.

The values that you enter here override the default values for this gateway.

Port Selection Order

Choose the order in which channels or ports are allocated for outbound calls from first (lowest number port) to last (highest number port) or from last to first.

Valid entries are TOP_DOWN (first to last) or BOTTOM_UP (last to first). If you are not sure which port order to use, choose TOP_DOWN.

Digit Sending

Choose one of the following digit sending types for out-dialing:

DTMF—Dual-tone multifrequency. Normal touchtone dialing

MF—Multifrequency

PULSE—Pulse (rotary) dialing

Network Locale

From the drop-down list box, choose the locale that is associated with the gateway. The network locale identifies a set of detailed information to support the hardware in a specific location. The network locale contains a definition of the tones and cadences that the device uses in a specific geographic area.

Note Choose only a network locale that is already installed and supported by the associated devices. The list contains all available network locales for this setting, but not all are necessarily installed. If the device is associated with a network locale that it does not support in the firmware, the device will fail to come up.

Signaling Packet Capture Mode (for Cisco IOS MGCP gateways only)

Configure this field only when you need to troubleshoot encrypted signaling information for the Cisco IOS MGCP gateway. Configuring packet capturing may cause call-processing interruptions. For more information on this field, refer to the Cisco Unified CallManager Security Guide.

Packet Capture Duration (for Cisco IOS MGCP gateways only)

Configure this field only when you need to troubleshoot encrypted signaling information for the Cisco IOS MGCP gateway. Configuring packet capturing may cause call-processing interruptions. For more information on this field, refer to the Cisco Unified CallManager Security Guide.

SMDI Base Port

Enter the first SMDI port number of the T1 span.

V150 (subset)

Check this box to enable v150 (subset) modem relay support on the gateways. This feature is currently used by IP-STEs to support end-to-end secure calls to an ISDN-STE. (Applies only to T1 PRI and T1 CAS.)

The default value specifies unchecked.

Product-Specific Configuration

Model-specific configuration fields defined by the gateway manufacturer

The gateway manufacturer specifies the model-specific fields under product-specific configuration. Because they are dynamically configured, they can change without notice.

To view field descriptions and help for product-specific configuration items, click the "i" information icon to the right of the Product Specific Configuration heading to display help in a popup dialog box.

If you need more information, refer to the documentation for the specific gateway that you are configuring or contact the manufacturer.


Related Topics

Adding Gateways to Cisco Unified CallManager

Adding a Non-IOS MGCP Gateway

Updating Gateways and Ports

Gateway Configuration Settings

H.323 Gateway Configuration Settings

Table 58-7 lists configuration settings for H.323 gateways.

Table 58-7 H.323 Gateway Configuration Settings 

Field
Description
Device Information

Device Name

Enter a unique name that Cisco Unified CallManager uses to identify the device. Use either the IP address or the host name as the device name.

Description

Enter a description that clarifies the purpose of the device.

Device Pool

From the drop-down list box, choose the appropriate device pool.

The device pool specifies a collection of properties for this device including CallManager Group, Date/Time Group, Region, and Calling Search Space for auto-registration of devices.

Call Classification

This parameter determines whether an incoming call that is using this gateway is considered off the network (OffNet) or on the network (OnNet).

When the Call Classification field is configured as Use System Default, the setting of the Cisco Unified CallManager clusterwide service parameter, Call Classification, determines whether the gateway is OnNet or OffNet.

This field provides an OnNet or OffNet alerting tone when the call is OnNet or OffNet, respectively.

Media Resource Group List

This list provides a prioritized grouping of media resource groups. An application chooses the required media resource, such as a Music On Hold server, from among the available media resources according to the priority order that a Media Resource Group List defines.

Location

Choose the appropriate location for this device. The location specifies the total bandwidth that is available for calls to and from this location. A location setting of None means that the locations feature does not keep track of the bandwidth that this device consumes.

AAR Group

Choose the automated alternate routing (AAR) group for this device. The AAR group provides the prefix digits that are used to route calls that are otherwise blocked due to insufficient bandwidth. An AAR group setting of None specifies that no rerouting of blocked calls will be attempted.

Tunneled Protocol

Choose the QSIG option if you want to use H.323 gateways to transport (tunnel) non-H.323 protocol information in H.323 signaling messages from Cisco Unified CallManager to other Annex M.1-compliant H.323 PINXs. QSIG tunneling supports the following features: Call Completion, Call Diversion, Call Transfer, Identification Services, Message Waiting Indication, and Path Replacement.

Note Refer to the Cisco Unified CallManager Compatibility Matrix for information about Annex M.1 feature compatibility with third-party vendor(s).

Signaling Port

This field applies only to H.323 devices. The value designates the H.225 signaling port that this device uses.

Default value specifies 1720. Valid values include 1 through 65535.

Media Termination Point Required

If you want a Media Termination Point to implement features that H.323 does not support (such as hold and transfer), check the check box.

Use this check box only for H.323 clients and H.323 devices that do not support the H.245 Empty Capabilities Set message.

If you check this box to require an MTP and this device becomes the endpoint of a video call, the call operates as audio only.

Retry Video Call as Audio

This check box applies only to video endpoints that receive a call.

By default, the system checks this check box to specify that this device should immediately retry a video call as an audio call (if it cannot connect as a video call) prior to sending the call to call control for rerouting.

If you uncheck this check box, a video call that fails to connect as video does not try to establish as an audio call. The call then fails to call control. Call control reroutes the call within the route/hunt list. If Automatic Alternate Routing (AAR) is configured and enabled, call control also reroutes the call between route/hunt lists.

Wait for Far End H.245 Terminal Capability Set

This field applies only to H.323 devices.

By default, the system checks this check box to specify that Cisco Unified CallManager needs to receive the far-end H.245 Terminal Capability Set before it sends its H.245 Terminal Capability Set. Unchecking this check box specifies that Cisco Unified CallManager should initiate capabilities exchange.

Note Uncheck this check box to allow calls through H.320 gateways for ISDN calls to and from other H.323 and H.320 endpoints.

Path Replacement Support

This check box displays if you choose the QSIG option from the Tunneled Protocol drop-down list box. This setting works with QSIG tunneling (Annex M.1) to ensure that non-H.323 information gets sent on the leg of the call that uses path replacement.

Note The default setting leaves the check box unchecked. When you choose the QSIG Tunneled Protocol option, the system automatically checks the check box.

Multilevel Precedence and Preemption (MLPP) Information

MLPP Domain (e.g., "0000FF")

Enter a hexadecimal value between 0 and FFFFFF for the MLPP domain that is associated with this device. If you leave this field blank, this device inherits its MLPP domain from the value that is set for the device pool of the device. If the device pool does not have an MLPP Domain setting, this device inherits its MLPP Domain from the value that is set for the MLPP Domain Identifier enterprise parameter.

MLPP Indication

The system does not make this setting available on this device type.

MLPP Preemption

The system does not make this setting available on this device type.

Call Routing Information
Inbound Calls

Significant Digits

Significant digits represent the number of final digits that are retained on inbound calls. Use this setting for the processing of incoming calls and to indicate the number of digits that are used to route calls that are coming in to the H.323 device.

Choose the number of significant digits to collect, from 0 to 32. Cisco Unified CallManager counts significant digits from the right (last digit) of the number that is called.

Calling Search Space

From the drop-down list box, choose the appropriate calling search space. A calling search space specifies the collection of Route Partitions that are searched to determine how a collected (originating) number should be routed.

You can configure the number of calling search spaces that display in this drop-down list box by using the Max List Box Items enterprise parameter. If more calling search spaces exist than the Max List Box Items enterprise parameter specifies, the ellipsis button (...) displays next to the drop-down list box. Click the ... button to display the Select Calling Search Space window. Enter a partial calling search space name in the List items where Name contains field. Click the desired calling search space name in the list of calling search spaces that displays in the Select item to use box and click OK.

Note To set the maximum list box items, choose System > Enterprise Parameters and choose CCMAdmin Parameters.

AAR Calling Search Space

Choose the appropriate calling search space for the device to use when it performs automated alternate routing (AAR). The AAR calling search space specifies the collection of route partitions that are searched to determine how to route a collected (originating) number that is otherwise blocked due to insufficient bandwidth.

Prefix DN

Enter the prefix digits that are appended to the called party number on incoming calls.

Cisco Unified CallManager adds prefix digits after first truncating the number in accordance with the Significant Digits setting.

Redirecting Number IE Delivery—Inbound

Check this check box to accept the Redirecting Number IE in the incoming SETUP message to the Cisco Unified CallManager. (The UUIE part of the SETUP message includes the Redirecting Number IE.)

Uncheck the check box to exclude the Redirecting Number IE.

You use Redirecting Number IE for voice-messaging integration only. If your configured voice-messaging system supports Redirecting Number IE, you should check the check box.

By default, the check box remains checked for the H.323 gateway.

Enable Inbound FastStart

Check this check box to enable the H.323 FastStart call connections on incoming calls.

By default, the check box remains unchecked for the H.323 gateway.

For intercluster calls, you must check the Enable Inbound FastStart check box on Cisco Unified CallManager servers in other clusters for the outbound FastStart feature to work.

Note If you updated Cisco CallManager 3.3(2) servers in other clusters with support patch B, do not enable inbound FastStart because 3.3(2)spB does not support the inbound FastStart feature over intercluster trunks.

Outbound Calls

Calling Party Selection

Any outbound call on a gateway can send directory number information. This field determines which directory number is sent.

Choose one of the following options to specify which directory number is sent:

Originator—Send the directory number of the calling device.

First Redirect Number—Send the directory number of the redirecting device.

Last Redirect Number—Send the directory number of the last device to redirect the call.

First Redirecting Party (External)—Send the directory number of the first redirecting device with the external phone mask applied.

Last Redirecting Party (External)—Send the directory number of the last redirecting device with the external phone mask applied.

Calling Party Presentation

Choose whether Cisco Unified CallManager transmits or blocks the calling line ID.

Choose Allowed if you want Cisco Unified CallManager to send calling line ID.

Choose Restricted if you do not want Cisco Unified CallManager to send calling line ID.

Called party IE number type unknown

Choose the format for the number type in called party directory numbers.

Cisco Unified CallManager sets the called directory number (DN) type. Cisco recommends that you do not change the default value unless you have advanced experience with dialing plans, such as NANP or the European dialing plan. You may need to change the default in Europe because Cisco Unified CallManager does not recognize European national dialing patterns. You can also change this setting when you are connecting to a PBX that expects the called directory number to be encoded to a non-national type numbering plan type.

Choose one of the following options:

CallManager—Cisco Unified CallManager sets the directory number type.

International—Use when you are dialing outside the dialing plan for your country.

National—Use when you are dialing within the dialing plan for your country.

Unknown—This option specifies that the dialing plan is unknown.

Calling party IE number type unknown

Choose the format for the number type in calling party directory numbers.

Cisco Unified CallManager sets the calling directory number (DN) type. Cisco recommends that you do not change the default value unless you have advanced experience with dialing plans, such as NANP or the European dialing plan. You may need to change the default in Europe because Cisco Unified CallManager does not recognize European national dialing patterns. You can also change this setting when you are connecting to a PBX that expects the calling directory number to be encoded to a non-national type numbering plan type.

Choose one of the following options:

CallManager—Cisco Unified CallManager sets the directory number type.

International—Use when you are dialing outside the dialing plan for your country.

National—Use when you are dialing within the dialing plan for your country.

Unknown—This option specifies that the dialing plan is unknown.

Called Numbering Plan

Choose the format for the numbering plan in called party directory numbers.

Cisco Unified CallManager sets the called DN numbering plan. Cisco recommends that you do not change the default value unless you have advanced experience with dialing plans, such as NANP or the European dialing plan. You may need to change the default in Europe because Cisco Unified CallManager does not recognize European national dialing patterns. You can also change this setting when you are connecting to a PBX that expects the called numbering plan to be encoded to a non-national type numbering plan.

Choose one of the following options:

CallManager—Cisco Unified CallManager sets the Numbering Plan in the directory number.

ISDN—Use when you are dialing outside the dialing plan for your country.

National Standard—Use when you are dialing within the dialing plan for your country.

Private—Use when you are dialing within a private network.

Unknown—This option specifies that the dialing plan is unknown.

Calling Numbering Plan

Choose the format for the numbering plan in calling party directory numbers.

Cisco Unified CallManager sets the calling DN numbering plan. Cisco recommends that you do not change the default value unless you have advanced experience with dialing plans, such as NANP or the European dialing plan. You may need to change the default in Europe because Cisco Unified CallManager does not recognize European national dialing patterns. You can also change this setting when you are connecting to a PBX that expects the calling numbering plan to be encoded to a non-national type numbering plan.

Choose one of the following options:

CallManager—Cisco Unified CallManager sets the Numbering Plan in the directory number.

ISDN—Use when you are dialing outside the dialing plan for your country.

National Standard—Use when you are dialing within the dialing plan for your country.

Private—Use when you are dialing within a private network.

Unknown—This option specifies that the dialing plan is unknown.

Caller ID DN

Enter the pattern that you want to use for calling line ID, from 0 to 24 digits.

For example, in North America

555XXXX = Variable calling line ID, where X equals an extension number. The CO appends the number with the area code if you do not specify it.

5555000 = Fixed calling line ID. Use when you want the Corporate number to be sent instead of the exact extension from which the call is placed. The CO appends the number with the area code if you do not specify it.

Display IE Delivery

Check the check box to enable delivery of the display IE in SETUP, CONNECT, and NOTIFY messages for the calling and called party name delivery service.

Default leaves Display IE Delivery check box checked.

Redirecting Number IE Delivery—Outbound

Check this check box to indicate the first redirecting number and the redirecting reason of the call when the call is forwarded. (The UUIE part of the outgoing SETUP message from the Cisco Unified CallManager includes the Redirecting Number IE.)

Uncheck the check box to exclude the first redirecting number and the redirecting reason.

You use Redirecting Number IE for voice-messaging integration only. If your configured voice-messaging system supports Redirecting Number IE, you should check the check box.

By default, the check box remains checked for the H.323 gateway.

Enable Outbound FastStart

Check this check box to enable the H.323 FastStart feature on outgoing calls.

By default, the check box remains unchecked for the H.323 gateway or trunk.

Note When you check the Enable Outbound FastStart check box, you must set the Media Termination Point Required, Media Resource Group Lists, and Codec for Outbound FastStart.

Codec For Outbound FastStart

Choose the codec for use with the H.323 device for an outbound FastStart call:

G711 mu-law 64K (default)

G711 a-law 64K

G723

G729

G729AnnexA

G729AnnexB

G729AnnexA-AnnexB

Note When you check the Enable Outbound FastStart check box, you must choose the codec for supporting outbound FastStart calls.


Related Topics

Adding a Cisco IOS H.323 Gateway

Updating Gateways and Ports

Gateway Configuration Settings

Analog Access Gateway Configuration Settings

Table 58-8 lists configuration settings for Analog Access gateways (Cisco AS-2, AS-4, and AS-8 gateways; Cisco AT-2, AT-4, and AT-8 gateways).

Table 58-8 Analog Access Gateway Configuration Settings 

Field
Description

MAC Address

Enter MAC address of the gateway. The MAC address uniquely identifies the hardware device.

You must enter a 12-hexadecimal character value.

Description

Enter the purpose of the device.

Device Pool

From the drop-down list box, choose the appropriate device pool.

The device pool specifies a collection of properties for this device including CallManager Group, Date/Time Group, Region, and Calling Search Space for auto-registration of devices.

Call Classification

This parameter determines whether an incoming call that is using this gateway is considered off the network (OffNet) or on the network (OnNet).

When the Call Classification field is configured as Use System Default, the setting of the Cisco Unified CallManager clusterwide service parameter, Call Classification, determines whether the gateway is OnNet or OffNet.

This field provides an OnNet or OffNet alerting tone when the call is OnNet or OffNet, respectively.

Load Information

Enter the appropriate load information for the custom software for gateway.

The values that you enter here override the default values for this gateway.

Network Locale

From the drop-down list box, choose the locale that is associated with the gateway. The network locale identifies a set of detailed information to support the hardware in a specific location. The network locale contains a definition of the tones and cadences that the device uses in a specific geographic area.

Note Choose only a network locale that is already installed and supported by the associated devices. The list contains all available network locales for this setting, but not all are necessarily installed. If the device is associated with a network locale that it does not support in the firmware, the device will fail to come up.

Signaling Packet Capture Mode (for Cisco IOS MGCP gateways only)

Configure this field only when you need to troubleshoot encrypted signaling information for the Cisco IOS MGCP gateway. Configuring packet capturing may cause call-processing interruptions. For more information on this field, refer to the Cisco Unified CallManager Security Guide.

Packet Capture Duration (for Cisco IOS MGCP gateways only)

Configure this field only when you need to troubleshoot encrypted signaling information for the Cisco IOS MGCP gateway. Configuring packet capturing may cause call-processing interruptions. For more information on this field, refer to the Cisco Unified CallManager Security Guide.

Location

Choose the appropriate location for this device. The location specifies the total bandwidth that is available for calls to and from this location. A location setting of None means that the locations feature does not keep track of the bandwidth that this device consumes.

AAR Group

Choose the automated alternate routing (AAR) group for this device. The AAR group provides the prefix digits that are used to route calls that are otherwise blocked due to insufficient bandwidth. An AAR group setting of None specifies that no rerouting of blocked calls will be attempted.

Calling Search Space

From the drop-down list box, choose the appropriate calling search space. The calling search space specifies a collection of partitions that are searched to determine how a collected (originating) number should be routed.

You can configure the number of calling search spaces that display in this drop-down list box by using the Max List Box Items enterprise parameter. If more calling search spaces exist than the Max List Box Items enterprise parameter specifies, the ellipsis button (...) displays next to the drop-down list box. Click the ... button to display the Select Calling Search Space window. Enter a partial calling search space name in the List items where Name contains field. Click the desired calling search space name in the list of calling search spaces that displays in the Select item to use box and click OK.

Note To set the maximum list box items, choose System > Enterprise Parameters and choose CCMAdmin Parameters.

AAR Calling Search Space

Choose the appropriate calling search space for the device to use when it performs automated alternate routing (AAR). The AAR calling search space specifies the collection of route partitions that are searched to determine how to route a collected (originating) number that is otherwise blocked due to insufficient bandwidth.

Media Resource Group List

This list provides a prioritized grouping of media resource groups. An application chooses the required media resource, such as a Music On Hold server, from among the available media resources according to the priority order that a Media Resource Group List defines.

Network Hold Audio Source

This audio source plays when the network initiates a hold action.

User Hold Audio Source

This audio source plays when a user initiates a hold action.

Port Selection Order

Choose the order in which ports are chosen. If you are not sure which port order to use, choose TOP_DOWN:

TOP_DOWN—Selects ports in descending order, from port 1 to port 8.

BOTTOM_UP—Selects ports in ascending order, from port 8 to port 1.

MLPP Domain (e.g., "0000FF")

Enter a hexadecimal value between 0 and FFFFFF for the MLPP domain that is associated with this device. If you leave this field blank, this device inherits its MLPP domain from the value that is set for the device pool of the device. If the device pool does not have an MLPP Domain setting, this device inherits its MLPP Domain from the value that is set for the MLPP Domain Identifier enterprise parameter.

MLPP Indication

The system does not make this setting available on this device type.

MLPP Preemption

The system does not make this setting available on this device type.

Product-Specific Configuration

Model-specific configuration fields defined by the gateway manufacturer

The gateway manufacturer specifies the model-specific fields under product-specific configuration. Because they are dynamically configured, they can change without notice.

To view field descriptions and help for product-specific configuration items, click the "i" information icon to the right of the Product Specific Configuration heading to display help in a popup dialog box.

If you need more information, refer to the documentation for the specific gateway that you are configuring or contact the manufacturer.


Related Topics

Adding an Analog Access Gateway and Ports

Adding a Cisco VG248 Analog Phone Gateway

Updating Gateways and Ports

Gateway Configuration Settings

Cisco VG248 Gateway Configuration Settings

Table 58-9 lists configuration settings for the Cisco VG248 Gateways.

Table 58-9 Cisco VG248 Gateway Configuration Settings 

Field
Description

MAC Address

Enter the last 10 digits of the Media Access Control (MAC) address for the Cisco VG248.

Only one MAC address exists for the Cisco VG248 Analog Phone Gateway, but Cisco Unified CallManager requires unique MAC addresses for all devices. When only 10 digits of the MAC address are entered, Cisco Unified CallManager can use the MAC address for the gateway and append additional information to it to create the MAC addresses for the VGC phones.

The conversion of the MAC address for each device occurs by adding the two-digit port number to the end of the MAC address (to the right of the number) and adding VGC at the beginning of the MAC address.

EXAMPLE
MAC Address for the Cisco VG248 is
0039A44218
the MAC address for registered port 12 in
Cisco Unified CallManager is
VGC0039A4421812

Description

Cisco Unified CallManager automatically provides this information by adding VGCGW immediately in front of the MAC address.

Load Information

Enter the firmware version for the Cisco VG248 that is being configured; otherwise, leave blank to use the default.

Installed Ports

48 PORTS

From the list of endpoint identifiers, choose one of the ports to configure the VGC_Phone ports.

Product Specific Configuration

For information about product-specific configuration, press the i button for help. Refer to the Cisco VG248 Analog Phone Gateway Software Configuration Guide for more information about the VG248 gateway.


Related Topics

Adding an Analog Access Gateway and Ports

Updating Gateways and Ports

Cisco VG248 Analog Phone Gateway Software Configuration Guide

Cisco IOS SCCP Gateway Configuration Settings

Table 58-10 lists configuration settings for the Cisco IOS SCCP gateways.

Table 58-10 Cisco IOS SCCP Gateway Configuration Settings 

Field
Description

MAC Address (last 10 Characters)

Enter the last 10 digits of the Media Access Control (MAC) address for the gateway. Use the MAC address of the interface that the sccp local IOS command specifies on the gateway. Valid characters include the digits 0 through 9 and the uppercase characters A through F.

The conversion of the MAC address for each device occurs by adding the three-digit mapping of the slot/subunit/port to the end of the MAC address (to the right of the number).

EXAMPLE
MAC Address for the gateway is
0006D7E5C7
The MAC address in Cisco Unified CallManager is
0006D7E5C7281
where 281 is the three-digit mapping of the 
slot/subunit/port.
The values 2,8 and 1 can be hex digits and each do not necessarily 
correspond to slot, subunit and port values.

The system inserts the following two-character strings before the MAC address to indicate the phone device types:

BR—BRI phone

AN—Analog phone

The system also inserts SKIGW for the gateway name.

Description

Cisco Unified CallManager automatically provides this information by adding SKIGW immediately in front of the MAC address. You can override the description.

Cisco Unified CallManager Group

From the drop-down list box, choose a Cisco Unified CallManager redundancy group.

A Cisco Unified CallManager redundancy group includes a prioritized list of up to three Cisco Unified CallManagers. The first Cisco Unified CallManager in the list serves as the primary Cisco Unified CallManager. If the primary Cisco Unified CallManager is not available or fails, the gateway attempts to connect with the next Cisco Unified CallManager in the list, and so on.

Installed Voice Interface Cards

Note You must specify the beginning port number for some VICs. For example, if the VIC in Subunit 0 begins at 0 and has two ports (0 and 1); then, the VIC in Subunit 1 must begin at a port number greater than 1 and have two ports (2 and 3 or 4 and 5).

Note The correct number of slots displays for each model of SCCP gateway.

Module in Slot 0
Module in Slot 1
Module in Slot 2
Module in Slot 3

(and so on)

For each available slot on the chosen SCCP gateway, choose the type of module that is installed. The system supports the following modules:

Network Modules (with VIC slots):

NM-2V—Has two VICs, one in Subunit 0 and one in Subunit 1 for FXS-SCCP.

NM-HD-2V—Has two VIC slots, one in Subunit 0 and one in Subunit 1 for FXS-SCCP or for BRI-NT/TE-SCCP.

NM-HD-2VE—Has two VIC slots, one in Subunit 0 and one in Subunit 1 for FXS-SCCP or for BRI-NT/TE-SCCP

Network Modules (no VIC slots):

NM-HDA-4FXS—has 4 FXS directly without VIC and can be extended by up to two expansion modules EM-HDA-8FXS to support 16 FXS ports.

EM-HDA-8FXS—expansion module for the NM-HDA-4FXS

Voice Interface Cards:

VIC-2FXS

VIC-4FXS

VIC2-2FXS

VIC2-2BRI-NT/TE

 

At the slot level, four options exist:

NM-2V—2 subunits options VIC-2FXS-SCCP

NM-HD-2V— 2 subunits options VIC-4FXS-SCCP, VIC2-2FXS-SCCP, VIC2-2BRI-NT/TE-SCCP

NM-HD-2VE—2 subunits options VIC-4FXS-SCCP, VIC2-2FXS-SCCP, VIC2-2BRI-NT/TE-SCCP

NM-HDA—3 subunits options NM-HDA-4FXS-SCCP, EM-8FXS-EM0-SCCP, EM-8FXS-EM1-SCCP.

In NM-HDA, these are not true VICs, The VIC2-2BRI-NT/TE is the only VIC for BRI SCCP phones. Vg224 GW is different from all others

The following option supports only one slot:

ANALOG—1 subunit option 24FXS-SCCP (supports 24 FXS ports)

The option None means that no network modules are installed.

Product Specific Configuration

Model-specific configuration fields defined by the gateway manufacturer

The gateway manufacturer specifies the model-specific fields under product-specific configuration. Because they are dynamically configured, they can change without notice.

To view field descriptions and help for product-specific configuration items, click the "i" information icon to the right of the Product Specific Configuration heading to display help in a popup dialog box.

If you need more information, refer to the documentation for the specific gateway that you are configuring or contact the manufacturer.


Related Topics

Adding Gateways to Cisco Unified CallManager

Adding a Cisco IOS SCCP Gateway

Updating Gateways and Ports

Port Configuration Settings

See the following sections for tables that list detailed descriptions for all port type configuration fields:

POTS Port Configuration Settings

Loop-Start Port Configuration Settings

Ground-Start Port Configuration Settings

E & M Port Configuration Settings

For detailed information about gateway configuration settings, see the Gateway Configuration Settings.

POTS Port Configuration Settings

Table 58-11 describes the POTS port configuration settings.

Table 58-11 POTS Port Configuration Settings 

Field
Description

Port Type

From the Port Type drop-down list box, choose POTS.

Port Number

End Port Number

Choose whether you want to add and configure all available ports, a single port, or a range of ports by setting values for the Port Number and End Port Number fields:

To specify a range of ports, choose appropriate values for Port Number and End Port Number.

To create a single port, choose the same number in the Port Number and End Port Number fields.

To add all available ports, choose All Ports for both the Port Number and End Port Number fields.

Port Direction

Choose the direction of calls that pass through this port:

Inbound—Use for incoming calls only.

Outbound—Use for outgoing calls.

Bothways—Use for inbound and outbound calls (default).

Audio Signal Adjustment into IP Network

This field specifies the gain or loss that is applied to the received audio signal relative to the port application type.

Note Improper gain setting may cause audio echo. Use caution when you are adjusting this setting.

Audio Signal Adjustment from IP Network

This field specifies the gain or loss that is applied to the transmitted audio signal relative to the port application type.

Note Improper gain setting may cause audio echo. Use caution when you are adjusting this setting.

Prefix DN

Enter the prefix digits that are appended to the digits that this trunk receives on incoming calls.

The Cisco Unified CallManager adds prefix digits after it truncates the number in accordance with the Num Digits setting.

Num Digits

Enter the number of significant digits to collect, from 0 to 32.

Cisco Unified CallManager counts significant digits from the right (last digit) of the number that is called.

Use this field for the processing of incoming calls and to indicate the number of digits starting from the last digit of the called number that are used to route calls that are coming into the PRI span. See Prefix DN.

Expected Digits

Enter the number of digits that are expected on the inbound side of the trunk. For this rarely used field, leave zero as the default value if you are unsure.

Call Restart Timer (1000-5000 ms)

Call Restart Timer (1000-5000 ms); ms indicates time in milliseconds.

Offhook Validation Timer (100-1000 ms)

Offhook Validation Timer (100-1000 ms); ms indicates time in milliseconds.

Onhook Validation Timer (100-1000 ms)

Onhook Validation Timer (100-1000 ms); ms indicates time in milliseconds.

Hookflash Timer (100-1500 ms)

Hookflash Timer (100-1500 ms); ms indicates time in milliseconds.

SMDI Port Number (0-4096)

Use this field for analog access ports that connect to a voice-messaging system.

Set the SMDI Port Number equal to the actual port number on the voice-messaging system to which the analog access port connects.

Note Voice-mail logical ports typically must match physical ports for the voice-messaging system to operate correctly.

Product-Specific Configuration

Model-specific configuration fields defined by the gateway manufacturer

The gateway manufacturer specifies the model-specific fields under product-specific configuration. Because they are dynamically configured, they can change without notice.

To view field descriptions and help for product-specific configuration items, click the "i" information icon to the right of the Product Specific Configuration heading to display help in a popup dialog box.

If you need more information, refer to the documentation for the specific gateway that you are configuring or contact the manufacturer.


Related Topics

Adding T1-CAS Ports to an MGCP Gateway

Adding an Analog Access Gateway and Ports

Gateway Configuration Settings

Adding Gateways to Cisco Unified CallManager

Loop-Start Port Configuration Settings

Table 58-12 describes the loop-start port configuration settings.

Table 58-12 Loop-Start Port Configuration Settings 

Field
Description

Port Type

From the Port Type drop-down list box, choose Loop Start.

Beginning Port Number

Ending Port Number

Choose whether you want to add and configure all available ports, a single port, or a range of ports by setting values for the Port Number and End Port Number fields:

To specify a range of ports, choose appropriate values for Port Number and End Port Number.

To create a single port, choose the same number in the Port Number and End Port Number fields.

To add all available ports, choose All Ports for both the Port Number and End Port Number fields.

Port Direction

Choose the direction of calls that pass through this port:

Inbound—Use for incoming calls only.

Outbound—Use for outgoing calls.

Both Ways—Use for inbound and outbound calls.

Attendant DN

Enter the directory number to which you want incoming calls routed; for example, zero or a directory number for an attendant.

Product-Specific Configurations

Model-specific configuration fields defined by the gateway manufacturer

The gateway manufacturer specifies the model-specific fields under product-specific configuration. Because they are dynamically configured, they can change without notice.

To view field descriptions and help for product-specific configuration items, click the "i" information icon to the right of the Product Specific Configuration heading to display help in a popup dialog box.

If you need more information, refer to the documentation for the specific gateway that you are configuring or contact the manufacturer.


Related Topics

Adding T1-CAS Ports to an MGCP Gateway

Gateway Configuration Settings

Adding Gateways to Cisco Unified CallManager

Ground-Start Port Configuration Settings

Table 58-13 describes the ground start port configuration settings.

Table 58-13 Ground-Start Port Configuration Settings 

Field
Description

Port Type

From the Port Type drop-down list box, choose Ground Start.

Port Number

End Port Number

Choose whether you want to add and configure all available ports, a single port, or a range of ports by setting values for the Port Number and End Port Number fields:

To specify a range of ports, choose appropriate values for Port Number and End Port Number.

To create a single port, choose the same number in the Port Number and End Port Number fields.

To add all available ports, choose All Ports for both the Port Number and End Port Number fields.

Port Direction

Choose the direction of calls that pass through this port:

Inbound—Use for incoming calls only.

Outbound—Use for outgoing calls.

Both Ways—Use for inbound and outbound calls.

Attendant DN

Enter the number to which you want incoming calls routed; for example, zero or a directory number for an attendant.

Product-Specific Configuration

Model-specific configuration fields defined by the gateway manufacturer

The gateway manufacturer specifies the model-specific fields under product-specific configuration. Because they are dynamically configured, they can change without notice.

To view field descriptions and help for product-specific configuration items, click the "i" information icon to the right of the Product Specific Configuration heading to display help in a popup dialog box.

If you need more information, refer to the documentation for the specific gateway that you are configuring or contact the manufacturer.


Related Topics

Adding T1-CAS Ports to an MGCP Gateway

Gateway Configuration Settings

Adding Gateways to Cisco Unified CallManager

E & M Port Configuration Settings

E & M (Ear and Mouth) ports allow connection for PBX trunk lines (tie lines). E & M designates a signaling technique for two-wire, four-wire, and six-wire telephone and trunk interfaces.

Table 58-14 describes the E & M port configuration settings.

Table 58-14 E & M Port Configuration Settings 

Field
Description

Port Type

From the Port Type drop-down list box, choose EANDM.

Port Number

End Port Number

Choose whether you want to add and configure all available ports, a single port, or a range of ports by setting values for the Port Number and End Port Number fields:

To specify a range of ports, choose appropriate values for Port Number and End Port Number.

To create a single port, choose the same number in the Port Number and End Port Number fields.

To add all available ports, choose All Ports for both the Port Number and End Port Number fields.

Port Direction

Choose the direction of calls that pass through this port:

Inbound—Use for incoming calls only.

Outbound—Use for outgoing calls.

Both Ways—Use for inbound and outbound calls.

Digit Sending

Choose one of the following digit sending types for out-dialing:

DTMF—Dual-tone multifrequency. Normal touchtone dialing

MF—Multifrequency

PULSE—Pulse (rotary) dialing

Prefix DN

Enter the prefix digits that are appended to the called party number on incoming calls.

Cisco Unified CallManager adds prefix digits after first truncating the number in accordance with the Num Digits setting.

Num Digits

Choose the number of significant digits to collect, from 0 to 32. Cisco Unified CallManager counts significant digits from the right (last digit) of the number that is called.

Use this field if you check the Sig Digits check box. Use this field for the processing of incoming calls and to indicate the number of digits starting from the last digit of the called number that are used to route calls that are coming into the PRI span. See Prefix DN and Sig Digits.

Expected Digits

Enter the number of digits that are expected on the inbound side of the trunk. If you are unsure, leave zero as the default value for this rarely used field.

Product-Specific Configuration

Model-specific configuration fields defined by the gateway manufacturer

The gateway manufacturer specifies the model-specific fields under product-specific configuration. Because they are dynamically configured, they can change without notice.

To view field descriptions and help for product-specific configuration items, click the "i" information icon to the right of the Product Specific Configuration heading to display help in a popup dialog box.

If you need more information, refer to the documentation for the specific gateway that you are configuring or contact the manufacturer.


Related Topics

Adding T1-CAS Ports to an MGCP Gateway

Gateway Configuration Settings

Adding Gateways to Cisco Unified CallManager

Finding Specific Gateways

Because you might have hundreds of gateways in your network, Cisco Unified CallManager lets you use specific criteria to locate specific gateways. Use these sections to find specific gateways:

Searching by Device Name

Searching by Description

Searching by Directory Number/Route Pattern

Searching by Calling Search Space

Searching by Device Pool

Searching by Route Group

Searching by Device Type


Note During your work in a browser session, Cisco Unified CallManager Administration retains your gateway search preferences. If you navigate to other menu items and return to this menu item, Cisco Unified CallManager Administration retains your gateway search preferences until you modify your search or close the browser.


Searching by Device Name

Use this procedure if you know the device name of a specific gateway or if you want to get a listing of all gateways that are registered with Cisco Unified CallManager.

Procedure


Step 1 Choose Device > Gateway.

The Find and List Gateways window displays.

Step 2 From the drop-down list box, choose Device Name; then, choose one of the following criteria:

begins with

contains

ends with

is exactly

is not empty

is empty

Step 3 Specify the appropriate search text, if applicable. You can also specify how many items per page to display and whether to hide or show endpoints.

Step 4 Click Find.

A list of discovered gateways displays by

Device icon

Device Name

Description (if applicable)

Device Pool (if applicable)

Status

IP Address


Note You can delete or reset multiple gateways from the Find and List Gateways window by checking the check boxes next to the appropriate gateways and clicking Delete Selected to delete the gateways or clicking Reset Selected to reset the gateways. You can choose all the gateways in the window by checking the check box in the matching records title bar.



Related Topics

Searching by Description

Searching by Directory Number/Route Pattern

Searching by Calling Search Space

Searching by Device Pool

Searching by Route Group

Searching by Device Type

Searching by Description

Use this procedure if you know any key words that are used in the Description field of a specific gateway that is registered with Cisco Unified CallManager.

Procedure


Step 1 Choose Device > Gateway.

The Find and List Gateways window displays.

Step 2 From the drop-down list box, choose Description; then, choose one of the following criteria:

begins with

contains

ends with

is exactly

is not empty

is empty

Step 3 Specify the appropriate search text, if applicable. You can also specify how many items per page to display and whether to hide or show endpoints.

Step 4 Click Find.

A list of discovered gateways displays by

Device icon

Description (if applicable)

Device Name

Device Pool

Status

IP Address


Note You can delete or reset multiple gateways from the Find and List Gateways window by checking the check boxes next to the appropriate gateways and clicking Delete Selected to delete the gateways or clicking Reset Selected to reset the gateways. You can choose all the gateways in the window by checking the check box in the matching records title bar.



Related Topics

Searching by Device Name

Searching by Directory Number/Route Pattern

Searching by Calling Search Space

Searching by Device Pool

Searching by Route Group

Searching by Device Type

Searching by Directory Number/Route Pattern

Use this procedure to locate gateways that are assigned to a specific extension or range of extensions and that are registered with Cisco Unified CallManager.

Procedure


Step 1 Choose Device > Gateway.

The Find and List Gateways window displays.

Step 2 From the drop-down list box, choose DN/Route Pattern; then, choose one of the following criteria:

begins with

contains

ends with

is exactly

is not empty

is empty

Step 3 Specify the appropriate search text, if applicable. You can also specify how many items per page to display and whether to hide or show endpoints.

Step 4 Click Find.

A list of discovered gateways displays by

Extension

Partition

Device icon

Device Name

Description (if applicable)

Status

IP Address


Note You can delete or reset multiple gateways from the Find and List Gateways window by checking the check boxes next to the appropriate gateways and clicking Delete Selected to delete the gateways or clicking Reset Selected to reset the gateways. You can choose all the gateways in the window by checking the check box in the matching records title bar.



Related Topics

Searching by Device Name

Searching by Description

Searching by Calling Search Space

Searching by Device Pool

Searching by Route Group

Searching by Device Type

Searching by Calling Search Space

Use this procedure to locate gateways that are assigned to a calling search space and that are registered with Cisco Unified CallManager.

Procedure


Step 1 Choose Device > Gateway.

The Find and List Gateways window displays.

Step 2 From the drop-down list box, choose Calling Search Space; then, choose one of the following criteria:

begins with

contains

ends with

is exactly

is not empty

is empty

Step 3 Specify the appropriate search text, if applicable. You can also specify how many items per page to display and whether to hide or show endpoints.


Tip You can locate an existing calling search space by choosing one from the drop-down list box under the Find button. This action automatically inserts the name of the calling search space that you choose into the Find field.


Step 4 Click Find.

A list of discovered gateways displays by

Calling Search Space

Device icon

Device Name

Description (if applicable)

Status

IP Address


Note You can delete or reset multiple gateways from the Find and List Gateways window by checking the check boxes next to the appropriate gateways and clicking Delete Selected to delete the gateways or clicking Reset Selected to reset the gateways. You can choose all the gateways in the window by checking the check box in the matching records title bar.



Related Topics

Searching by Device Name

Searching by Description

Searching by Directory Number/Route Pattern

Searching by Device Pool

Searching by Route Group

Searching by Device Type

Searching by Device Pool

Use this procedure to locate gateways that are assigned to a specific device pool and that are registered with Cisco Unified CallManager.

Procedure


Step 1 Choose Device > Gateway.

The Find and List Gateways window displays.

Step 2 From the drop-down list box, choose Device Pool; then, choose one of the following criteria:

begins with

contains

ends with

is exactly

is not empty

is empty

Step 3 Specify the appropriate search text, if applicable. You can also specify how many items per page to display and whether to hide or show endpoints.


Tip You can locate an existing device pool by choosing one from the drop-down list box under the Find button. This action automatically inserts the name of the device pool that you choose into the Find field.


Step 4 Click Find.

A list of discovered gateways displays by

Device Pool

Device icon

Device Name

Description (if applicable)

Status

IP Address


Note You can delete or reset multiple gateways from the Find and List Gateways window by checking the check boxes next to the appropriate gateways and clicking Delete Selected to delete the gateways or clicking Reset Selected to reset the gateways. You can choose all the gateways in the window by checking the check box in the matching records title bar.



Related Topics

Searching by Device Name

Searching by Description

Searching by Directory Number/Route Pattern

Searching by Calling Search Space

Searching by Route Group

Searching by Device Type

Searching by Route Group

Use this procedure to locate gateways that are assigned to a specific route group and that are registered with Cisco Unified CallManager.

Procedure


Step 1 Choose Device > Gateway.

The Find and List Gateways window displays.

Step 2 From the drop-down list box, choose Route Group; then, choose one of the following criteria:

begins with

contains

ends with

is exactly

is not empty

is empty

Step 3 Specify the appropriate search text, if applicable. You can also specify how many items per page to display and whether to hide or show endpoints.


Tip You can locate an existing route group by choosing one from the drop-down list box under the Find button. This action automatically inserts the name of the route group that you choose into the Find field.


Step 4 Click Find.

A list of discovered gateways displays by

Route Group (Priority)

Device icon

Device Name (Port)

Description (if applicable)

Status

IP Address


Note You can delete or reset multiple gateways from the Find and List Gateways window by checking the check boxes next to the appropriate gateways. Click Delete Selected to delete the gateways or click Reset Selected to reset the gateways. You can choose all the gateways in the window by checking the check box in the matching records title bar.



Related Topics

Searching by Device Name

Searching by Description

Searching by Directory Number/Route Pattern

Searching by Calling Search Space

Searching by Device Pool

Searching by Device Type

Searching by Device Type

Use this procedure if you know the device type of a specific gateway or if you want to get a listing of all gateways of a particular device type.

Procedure


Step 1 Choose Device > Gateway.

The Find and List Gateways window displays.

Step 2 From the drop-down list box, choose Device Type; then, choose one of the following criteria:

begins with

contains

ends with

is exactly

is not empty

is empty

Step 3 Specify the appropriate search text, if applicable. You can also specify how many items per page to display and whether to hide or show endpoints.


Tip You can locate an existing device type by choosing one from the drop-down list box under the Find button. This action automatically inserts the name of the device type that you choose into the Find field.


Step 4 Click Find.

A list of discovered gateways displays by

Device Type

Device icon

Device Name

Description (if applicable)

Status

IP Address


Note You can delete or reset multiple gateways from the Find and List Gateways window by checking the check boxes next to the appropriate gateways and clicking Delete Selected to delete the gateways or clicking Reset Selected to reset the gateways. You can choose all the gateways in the window by checking the check box in the matching records title bar.



Related Topics

Searching by Device Name

Searching by Description

Searching by Directory Number/Route Pattern

Searching by Calling Search Space

Searching by Device Pool

Searching by Route Group

Modifying Gateways and Ports

Using Cisco Unified CallManager, you perform the following tasks identically regardless of the gateway type:

Using Dependency Records

Deleting Gateways

Resetting and Restarting Gateways

Updating Gateways and Ports

Using Dependency Records

Gateways and ports use a variety of configuration information such as partitions, device pools, and directory numbers. Before updating or deleting gateways or ports, you can find configuration information about that gateway and port by using the Dependency Records link. For more information about this link, see the "Dependency Records" appendix.

Deleting Gateways

Complete the following steps to delete a gateway from Cisco Unified CallManager.

Before You Begin

If you try to delete a gateway that a route group is using, Cisco Unified CallManager displays a message.To find out which route groups are using the gateway, click the Dependency Records link from the Gateway Configuration window. If the dependency records are not enabled for the system, the dependency records summary window displays a message. For more information about dependency records, see the "Accessing Dependency Records" section on page A-3. Before deleting a gateway that is currently in use, you must perform either or both of the following tasks:

Assign a different gateway to any route groups that are using the gateway that you want to delete. See the "Adding Devices to a Route Group" section.

Delete the route groups that are using the gateway that you want to delete. See the "Deleting a Route Group" section.

Procedure


Step 1 Choose Device > Gateway.

The Find and List Gateways window displays.

Step 2 To locate a specific gateway, enter search criteria.

Step 3 Click Find.

A list of discovered gateways that matches your search criteria displays.

Step 4 Check the check box next to the gateway that you want to delete.

Step 5 Click Delete Selected.

A message displays that states that you cannot undo this action.

Step 6 To delete the gateway, click OK or to cancel the operation, click Cancel.


Tip You can delete all the gateways in the window by checking the check box in the matching records title bar and clicking Delete Selected.



Related Topics

Adding Gateways to Cisco Unified CallManager

Finding Specific Gateways

Resetting and Restarting Gateways

Complete the following steps to reset or restart a gateway by using Cisco Unified CallManager.

Procedure


Step 1 Choose Device > Gateway.

The Find and List Gateway window displays.

Step 2 To locate a specific gateway, enter search criteria.

Step 3 Click Find.

A list of discovered gateways that matches your search criteria displays.

Step 4 Check the check box next to the gateway that you want to reset.

Step 5 Click Reset Gateway.

The Reset Gateway(s) window displays.

Step 6 Click one of the following choices:

Restart—Restarts a device without shutting it down.

Reset—Shuts down a device and brings it back up.

Close—Returns to the previous window without performing any action.


Note Restarting or resetting an H323 gateway does not physically restart/reset the gateway; it only reinitializes the configuration that Cisco Unified CallManager loaded. When you reset any other gateway type, Cisco Unified CallManager automatically drops the calls that are using the gateway. When you restart any other gateway type, Cisco Unified CallManager attempts to preserve the calls that are using the gateway.



Related Topics

Finding Specific Gateways

Updating Gateways and Ports

Updating Gateways and Ports

Complete the following steps to update a gateway or reconfigure gateway ports from Cisco Unified CallManager.

Procedure


Step 1 Choose Device > Gateway.

The Find and List Gateways window displays.

Step 2 To locate a specific gateway, enter search criteria.

Step 3 Click Find.

A list of discovered devices displays.

Step 4 Click the Device Name of the gateway that you want to update.

The Gateway Configuration window displays.

Step 5 Update the appropriate gateway or port settings as described in the following sections.

To access gateway ports, click the icon of the gateway port or the MGCP endpoint link on the left side of the configuration window for the chosen gateway.

MGCP Gateway Configuration Settings

FXS/FXO Gateway Configuration Settings

E1/T1 PRI Gateway Configuration Settings

T1-CAS Gateway Configuration Settings

Analog Access Gateway Configuration Settings

Port Configuration Settings

Step 6 Click Update.

Step 7 To apply the changes, reset the gateway.


Related Topics

Adding Gateways to Cisco Unified CallManager

Finding Specific Gateways

Resetting and Restarting Gateways

Deleting Gateways