Table Of Contents
Gateway Configuration
Adding Gateways to Cisco 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 Port to an MGCP Gateway
Adding a Non-IOS MGCP Gateway
Adding a Cisco IOS H.323 Gateway or Intercluster Trunk
Adding an Analog Access Gateway and Ports
Gateway Configuration Settings
MGCP Gateway Configuration Settings
FXS/FXO Gateway Configuration Settings
E1/T1 PRI Gateway Configuration Settings
T1-CAS Gateway Configuration Settings
H.323 Gateway and Intercluster Trunk Configuration Settings
Analog Access 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
Searching by Calling Search Space
Searching by Device Pool
Searching by Route Group
Modifying Gateways and Ports
Deleting Gateways
Resetting and Restarting Gateways
Updating Gateways and Ports
Gateway Configuration
Cisco IP telephony gateways enable Cisco CallManager to communicate with non-IP telecommunications devices. Cisco CallManager supports several types of gateways as described in the Cisco CallManager System Guide.
These sections provide information about using Cisco CallManager for working with and configuring Cisco gateways.
•
Adding Gateways to Cisco CallManager
•Gateway Configuration Settings
•Port Configuration Settings
•Modifying Gateways and Ports
•Finding Specific Gateways
•Understanding Voice Gateways, Cisco CallManager System Guide
Adding Gateways to Cisco CallManager
To enable Cisco CallManager to manage IP telephony gateways in your network, you must first add each gateway to the Cisco CallManager configuration database. The procedures, web panes, and configuration settings for adding a gateway vary according to the model of gateway that you are adding.
The following procedure describes how to add a new gateway in Cisco CallManager.
Procedure
Step 1 Choose Device > Gateway to display the Find/List Gateways pane.
Step 2 Click the Add a New Gateway link. The Add a New Gateway pane displays.
Step 3 Choose the type of gateway you want to add from the Gateway type drop-down list box. The Device Protocol field may be automatically populated depending on which gateway type you choose.
Step 4 Click Next.
Step 5 In the following table, click the specific procedure for the type of gateway you are configuring. Once you are in the correct procedure, start with the step in which you enter the appropriate settings for that particular gateway type.
Adding a Cisco IOS MGCP Gateway
Use the following procedure to add and configure a Cisco IOS MGCP gateway to Cisco CallManager. The following Cisco IOS gateways support MGCP:
•CiscoVG200 Cisco IP Telephony Voice Gateway
•Cisco IOS 362x, 364x, 366x gateways
•Cisco IOS 26xx gateways
•Cisco Catalyst 4000 Access Gateway Module
•Cisco Catalyst 4224 Voice Gateway Switch
•Cisco IAD2400 gateways
Before You Begin
Before configuring a Cisco IOS MGCP gateway for use with Cisco CallManager, you must configure the gateway using the Cisco IOS command-line interface (CLI). For procedures and commands required to perform this configuration, refer to the configuration documentation supplied with the gateway.
Procedure
Step 1 Choose Device > Add a New Device.
The Add a New Device pane appears.
Step 2 From the Device type drop-down list box, choose Gateway and click Next.
The Add a New Gateway pane appears.
Step 3 From the Gateway Type drop-down list box, choose one of the following gateways:
•Cisco Voice Gateway 200 (VG200)
•Cisco IOS 362x, 364x, 366x gateways
•Cisco IOS 26xx gateways
•Cisco Catalyst 4000 Access Gateway Module
•Cisco Catalyst 4224 Voice Gateway Switch
•Cisco IAD2400 gateway
Note The Cisco Catalyst 6000 gateways also support MGCP, but are configured differently.
When you choose one of the preceding gateways, the Device Protocol drop-down list displays "Not Required for MGCP."
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 pane provides configuration for these interfaces.
Step 4 Click Next. The MGCP Configuration pane displays.
Step 5 Enter the appropriate settings and choose the type of network modules installed in each slot, as described in the "MGCP Gateway Configuration Settings" section, including any product-specific configuration settings.
Step 6 Click Insert.
The MGCP Gateway Configuration pane updates and displays drop-down list boxes with options for configuring the type of voice interface cards (VICs) in each sub-unit of each network module.
The available choices depend on the type of network modules configured in the MGCP Configuration pane.
Step 7 From the drop-down list boxes, choose the type of VICs installed in each subunit and click Update.
Available VIC types include VIC-2FXS, VIC-2FXO, VWIC-1MFT-T1, VWIC-2MFT-T1, VWIC-1MFT-E1, VWIC-2MFT-E1, and WS-U4604-8FXS.
The pane updates to add links for configuring endpoint information and ports for the type of VICs chosen.
Step 8 Click an endpoint identifier (for example, 1/0/0) to configure device protocol information and add ports for the types of VICs installed.
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 Port to an MGCP Gateway
Step 9 Reset the gateway to apply the changes.
Step 10 Continue configuring endpoint information and ports as needed.
Step 11 After you finish configuring 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 for calls to be routed to the gateway.
Note You only need to add the MGCP gateway to a route pattern for outbound trunk 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 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 Choose Device > Gateway to display the Find/List Gateways pane, 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 pane, click the endpoint identifier for the FXS VIC you want to configure.
The pane refreshes and displays the Gateway Configuration pane.
Step 5 Enter the appropriate Gateway Configuration and Port Information settings. Refer to the following sections for details about these fields:
•FXS/FXO Gateway Configuration Settings
•POTS Port Configuration Settings
Step 6 Click Insert.
Note Once you insert a POTS port, the pane refreshes and displays the POTS port in the list on the left side of the pane. 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 8.
Note Refer to the "Adding a Directory Number" section and Directory Number Configuration Settings for information about adding and configuring DNs.
Step 8 Reset the gateway to apply the changes.
Step 9 To return to the main MGCP gateway configuration pane for the gateway to which you just added the ports, click Back to MGCP Configuration.
Step 10 Repeat Step 4 through Step 9 to add additional FXS ports.
Related Topics
•Adding Gateways to Cisco 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 CallManager assumes all loop-start trunks lack positive disconnect supervision. Configure trunks with positive disconnect supervision as ground start, so that active calls can be maintained during a Cisco 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 Choose Device > Gateway to display the Find/List Gateways pane, 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 pane displays.
Step 3 Click on the name of the desired gateway to display its MGCP configuration settings and endpoint identifiers.
Step 4 From the MGCP Configuration pane, click the endpoint identifiers of the FXO port you want to configure.
Step 5 From the Port Type drop-down list box, choose either Ground Start or Loop Start.
Step 6 Enter the appropriate Gateway Configuration and Port Information settings as described in the following sections:
•"FXS/FXO Gateway Configuration Settings" section
•"Ground Start Port Configuration Settings" section.
•"Loop Start Port Configuration Settings" section
Step 7 Click Insert.
Step 8 To return to the main MGCP gateway configuration pane for the gateway to which you just added the ports, click Back to MGCP Configuration.
Step 9 Repeat Step 4 though Step 7 to add more FXO ports.
Step 10 Reset the gateway to apply the changes.
Related Topics
•Adding Gateways to Cisco CallManager
•Port Configuration Settings
Adding T1-CAS Ports to an MGCP Gateway
Step 1 Choose Device > Gateway to display the Find/List Gateways pane, or skip to
Step 2 Enter the appropriate search criteria to locate the MGCP gateway to which you want to add a T1-CAS port.
Step 3 Click the name of the desired gateway to display its MGCP configuration settings and endpoint identifiers.
Step 4 From the MGCP Configuration pane, click the endpoint identifier of the T1-CAS port 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 opens in a separate pane.
Step 9 Choose a port type from the Port Type drop-down list box. See the "Port Configuration Settings" section for the appropriate settings for the port type you choose.
Step 10 Click Insert or Insert and Close.
Step 11 Reset the gateway to apply the changes.
Related Topics
•Adding Gateways to Cisco CallManager
•Port Configuration Settings
Adding a T1 PRI or E1 PRI Port to an MGCP Gateway
Step 1 Choose Device > Gateway to display the Find/List Gateways pane, or skip to Step 4 if you have already located the MGCP gateway to which you want to add a port.
Step 2 Enter the appropriate search criteria to locate the MGCP gateway to which you want to add a T1 PRI or E1 PRI port.
Step 3 Click the name of the desired gateway in the list to display the configuration information for the selected gateway.
Step 4 From the MGCP Configuration pane, click the endpoint identifier of the T1 or E1 PRI port 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 Reset the gateway to apply the changes.
Related Topics
•Adding a Cisco IOS MGCP Gateway
•Adding Gateways to Cisco CallManager
•E1/T1 PRI Gateway Configuration Settings
Adding a Non-IOS MGCP Gateway
Use the following procedure to add the following non-IOS Cisco MGCP gateways to Cisco 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 pane appears.
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 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 pane 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" section.
•"T1-CAS Gateway Configuration Settings" section
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 Reset the gateway to apply the changes.
Related Topics
•Adding Gateways to Cisco CallManager
•E1/T1 PRI Gateway Configuration Settings
•T1-CAS Gateway Configuration Settings
Adding a Cisco IOS H.323 Gateway or Intercluster Trunk
Follow these procedures to add a Cisco IOS H.323 gateway or intercluster trunk to Cisco CallManager.
Before You Begin
Before configuring a Cisco IOS H.323 gateway for use with Cisco CallManager, you must configure the gateway 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 required to perform this configuration, refer to the configuration documentation supplied with the gateway.
For information about configuring intercluster trunks, refer to the Cisco IP Telephone Network Design Guide.
Procedure
Step 1 Choose Device > Add a New Device.
The Add a New Device pane appears.
Step 2 From the Device type drop-down list box, choose Gateway.
Step 3 Click Next.
The Add a New Gateway pane appears.
Step 4 From the Gateway Type drop-down list box, choose H.323 Gateway.
Step 5 From the Device Protocol drop-down list box, choose one of the two available device protocols:
•H.225 (default)—Choose H.323 if you are configuring a Cisco IOS gateway in H.323 mode.
•Intercluster Trunk—An intercluster trunk provides a virtual H.323 gateway that is used to interlink Cisco CallManagers in different clusters.
Step 6 Click Next.
Step 7 Enter the appropriate settings as described in "H.323 Gateway and Intercluster Trunk Configuration Settings" section.
Step 8 Click Insert.
Step 9 Reset the gateway to apply the changes.
Related Topics
•Adding Gateways to Cisco CallManager
•H.323 Gateway and Intercluster Trunk Configuration Settings
Adding an Analog Access Gateway and Ports
Use the procedure in this section to add and configure ports for the following 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 pane appears.
Step 2 From the Device type drop-down list box, choose Gateway.
Step 3 Click Next.
The Add a New Gateway pane appears.
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 CallManager automatically chooses the appropriate device protocol for the gateway (in this case, Analog Access).
Step 5 Click Next.
The Gateway Configuration pane appears.
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 pane.
Step 9 From the drop-down list box, choose POTS or Loop Start as the port type depending on the gateway model 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 pane refreshes and displays the POTS port in the list on the left side of the pane. An Add DN link displays to the right of the new port.
Step 12 Click Add DN to add a directory numbers to an FXS port.
See the "Adding a Directory Number" section and "Phone Configuration Settings" section for information about adding and configuring directory numbers.
Step 13 Reset the gateway to apply the changes.
Related Topics
•Adding Gateways to Cisco CallManager
•Analog Access Gateway Configuration Settings
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
•T1-CAS Gateway Configuration Settings
•H.323 Gateway and Intercluster Trunk Configuration Settings
•Analog Access Gateway Configuration Settings
For detailed information about port configuration settings, see the "Port Configuration Settings" section.
MGCP Gateway Configuration Settings
Table 41-2 provides detailed descriptions for MGCP gateway configuration settings.
Table 41-2 MGCP Gateway Configuration Settings
Field
|
Description
|
MGCP Domain Name
|
Enter a name 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 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 CallManager Group
|
From the drop-down list box, choose a Cisco CallManager redundancy group.
A Cisco CallManager redundancy group includes a prioritized list of up to three Cisco CallManagers. The first Cisco CallManager in the list serves as the primary Cisco CallManager. If the primary Cisco CallManager is not available or fails, the gateway attempts to connect with the next Cisco CallManager in the list, and so on.
|
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 selected MGCP gateway, choose the type of network module installed; for example:
•NM-1V—Has one voice interface card (VIC) in Sub-Unit 0 for FXS or FXO.
•NM-2V—Has two VICs, one in Sub-Unit 0 and one in Sub-Unit 1 for either FXS or FXO.
•NM-HDV—Has one VIC in Sub-Unit 0 for either T1-CAS or T1-PRI, or E1-PRI.
•None—No network modules installed.
The correct number of slots displays for each model of MGCP gateway.
Note The VG200 gateway has only one slot.
|
Product-Specific Configuration
|
Model-specific configuration fields 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 pane.
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 CallManager
•Adding a Cisco IOS MGCP Gateway
•Adding a Non-IOS MGCP Gateway
•Updating Gateways and Ports
FXS/FXO Gateway Configuration Settings
Table 41-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 41-3 FXS/FXO Gateway Configuration Settings
Field
|
Description
|
Description
|
This display-only field contains a string generated by Cisco CallManager that uniquely identifies the analog MGCP description.
For example:
AALN/S0/SUI/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.
|
Calling Search Space
|
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.
|
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, among the available media resources according to the priority order defined in a Media Resource List.
|
Network Audio Hold Source
|
This audio source plays when the network initiates a hold action.
|
User Audio Hold Source
|
This field specifies an audio source played when a user initiates a hold action.
|
Location
|
Choose the appropriate location for this device. The location specifies the total bandwidth 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 consumed by this device.
|
Prefix DN
|
Enter the prefix digits that are appended to the digits this trunk receives on incoming calls.
The Cisco CallManager adds prefix digits after first truncating the number in accordance with the Num Digits setting.
|
Num Digits
|
Enter the number of significant digits to collect, from 0 to 32.
Cisco 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 used to route calls coming into the PRI span. See Prefix DN.
|
Expected Digits
|
Enter the number of digits expected on the inbound side of the trunk. Leave zero as the default value if you are unsure for this rarely-used field.
|
Port Direction
|
Choose the direction of calls 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
|
Enter the directory number to which you want incoming calls routed; for example, zero or a directory number for an attendant.
|
Related Topics
•Adding FXS Ports to an MGCP Gateway
•Adding FXO Ports to an MGCP Gateway
•Adding Gateways to Cisco CallManager
•Adding a Cisco IOS MGCP Gateway
•Adding a Non-IOS MGCP Gateway
•Updating Gateways and Ports
E1/T1 PRI Gateway Configuration Settings
Table 41-4 provides detailed descriptions for E1/T1 PRI configuration settings.
Table 41-4 E1/T1 PRI Configuration Settings
Field
|
Description
|
MAC Address (non-IOS gateway)
|
Enter the appropriate MAC address. The MAC address identifies hardware-based telephones and device name.
You must enter a 12-hexadecimal character value.
|
Domain Name (MGCP gateways)
|
For MGCP gateways, this display-only field contains a string generated by Cisco CallManager 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.
|
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.
|
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, among the available media resources according to the priority order defined in a Media Resource List.
|
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.
|
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.
|
Location
|
Choose the appropriate location for this device. The location specifies the total bandwidth 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 consumed by this device.
|
Load Information
|
Enter the appropriate firmware load information for the gateway.
The value you enter here overrides the default firmware load for this type of gateway.
|
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.
|
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 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.
|
Caller ID DN
|
Enter the pattern 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.
|
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.
|
Channel IE Type
|
Choose one of the following values to specify whether channel selection is presented as a channel map or a slot map.
•Number—B-channel usage is always a channel map format.
•Slotmap—B-channel usage is always a slotmap format
•Use Number When 1B—Channel usage is a channel map for one B-channel but is a slot map if more than one B-channel exists.
|
Interface Identifier Present
|
Check the check box to indicate that an interface identifier is present. By default, the Cisco CallManager leaves the check box unchecked.
This setting only applies to the DMS100 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 obtained from the PBX provider.
This field applies to the DMS100 protocol only. Valid values range from 0 to 255.
|
Display IE Delivery
|
Check the check box to enable delivery of the display information element (IE) in SETUP and CONNECT messages for the calling and called party name delivery service.
Default leaves the check box unchecked.
|
Redirecting Number IE Delivery
|
Check the check box to include the Redirecting Number IE in the SETUP message to indicate the first redirecting number and the redirecting reason of the call when Call Forward happens.
Default leaves this check box unchecked.
This setting applies to the SETUP message only on all protocols for digital access gateways.
|
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 is sent if the Inhibit Restarts check box is unchecked.
|
Num Digits
|
Choose the number of significant digits to collect, from 0 to 32. Cisco CallManager counts significant digits from the right (last digit) of the number called.
Use this field if you check the Sig Digits check box. Use for the processing of incoming calls and to indicate the number of digits starting from the last digit of the called number used to route calls coming into the PRI span. See Prefix DN and Sig Digits.
|
Sig Digits
|
This field represents the number of final digits a PRI span should retain on inbound calls. A trunk with significant digits enabled truncates all but the final few digits of the address provided by an inbound call.
Enable or disable this box depending on whether you want to collect significant digits.
If the check box is unchecked, the Cisco CallManager does not truncate the inbound number. If the check box is checked, you also need to choose the number of significant digits to collect.
|
Prefix DN
|
Enter the prefix digits that are appended to the digits that this trunk receives on incoming calls.
The Cisco CallManager adds prefix digits after first truncating the number in accordance with the Num Digits setting.
|
Presentation Bit
|
Choose whether you want the central office to transmit or block caller ID.
Choose Allowed if you want the central office to send caller ID. Choose Restricted if you do not want the central office to send caller ID.
|
Called party IE number type unknown
|
Choose the format for the type of number in called party directory numbers. Cisco 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 CallManager does not recognize European national dialing patterns. You can also change this setting when connecting to PBXs using routing as a non-national type number.
Choose one of the following options:
•CallManager—The Cisco 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 type of number in calling party directory numbers.
Cisco 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 CallManager does not recognize European national dialing patterns. You can also change this setting when connecting to PBXs using routing as a non-national type number.
Choose one of the following options:
•CallManager—The Cisco 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 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 CallManager does not recognize European national dialing patterns. You can also change this setting when connecting to PBXs using routing as a non-national type number.
Choose one of the following options:
•CallManager—The Cisco 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 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 CallManager does not recognize European national dialing patterns. You can also change this setting when connecting to PBXs using routing as a non-national type number.
Choose one of the following options:
•CallManager—The Cisco 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.
|
PRI Protocol Type
|
Choose the communications protocol for the span:
For E1 PRI spans, two options exist:
•PRI AUSTRALIAN—Australian ISDN
•PRI EURO—European ISDN
T1 PRI spans have several options, depending on the carrier or switch:
•4E—AT&T InterExchange carrier
•5E8 Custom—Cisco IP Phone
•5E9 and NI2—AT&T family local exchange switch or carrier
•DMS—MCI family local exchange switch or carrier
•ETSI SC—European local exchange carrier on T1; also, Japanese local exchange.
Determine the switch to which you are connecting and the preferred protocol, as follows:
•Nortel Meridian—5E8 Custom
•Lucent Definity—4ESS or 5E8
•Madge (Teleos) box—5E8 Teleos
•Intecom PBX—5E8 Intecom
Alternatively, choose the protocol based on the carrier:
•MCI—DMS-250
•Sprint—DMS-250 or DMS-100
•AT&T—4ESS
|
Inhibit restarts at PRI initialization
|
A RESTART message confirms the status of the ports on a PRI span. If RESTARTs are not sent, Cisco CallManager assumes the ports are in service.
When the D-Channel successfully connects with another PRI D-Channel, it sends restarts when this check box is unchecked.
|
Enable status poll
|
Check the check box to view the B-channel status in the debug pane.
|
Number of digits to strip
|
Choose the number of digits to strip on outbound calls, from 0 to 32.
For example, 8889725551234 is dialed, and the number of digits to strip is 3. In this example, Cisco CallManager strips 888 from the outbound number.
|
Country Code
|
Choose the country in which the gateway is located.
|
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, the Cisco 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 CallManager gateway is non-ISDN and that the destination device should play in-band ringback.
This problem usually associates with Cisco CallManagers that connect to PBXs through digital gateways.
|
Product-Specific Configuration
|
Model-specific configuration fields 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 pane.
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 CallManager
•Updating Gateways and Ports
•Gateway Configuration
T1-CAS Gateway Configuration Settings
Table 41-5 provides detailed descriptions for T1-CAS configuration settings.
Table 41-5 T1-CAS Configuration Settings
Field
|
Description
|
MAC Address
(non-IOS gateway)
|
Enter the MAC address as a 12-digit hexadecimal number that uniquely identifies a hardware device.
Make sure that you enter a 12-hexadecimal character value.
|
Domain Name
|
For MGCP gateways, this display-only field contains a string generated by Cisco CallManager 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.
|
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, among the available media resources according to the priority order defined in a Media Resource List.
|
Network Audio Hold Source
|
This audio source plays when the network initiates a hold action.
|
User Audio Hold Source
|
This audio source plays when a user initiates a hold action.
|
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.
|
Load Information
|
Enter the appropriate firmware load information for the gateway.
The values you enter here override the default values for this gateway.
|
Location
|
Choose the appropriate location for this device. The location specifies the total bandwidth 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 consumed by this device.
|
Port 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 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.
|
Country Code
|
Choose the country in which the gateway is located.
|
Related Topics
•Adding a Non-IOS MGCP Gateway
•Adding Gateways to Cisco CallManager
•Updating Gateways and Ports
•Gateway Configuration
H.323 Gateway and Intercluster Trunk Configuration Settings
Table 41-6 lists configuration settings for H.323 gateways and intercluster trunks.
Table 41-6 H.323 Gateway/Intercluster Trunk Configuration Settings
Field
|
Description
|
Device Name
|
Enter a unique name that is used by Cisco CallManager to identify the 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.
|
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, among the available media resources according to the priority order defined in a Media Resource Group List.
|
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.
|
Calling Search Space
|
Choose the appropriate calling search space. A calling search space specifies the collection of Route Partitions searched to determine how a collected (originating) number should be routed.
|
Location
|
Choose the appropriate location for this device. The location specifies the total bandwidth 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 consumed by this device.
|
Caller ID DN
|
Enter the pattern you want to use for caller ID, from 0 to 24 digits.
For example, in North America:
•555XXXX = Variable caller ID, where X is equal to an extension number. The CO appends the number with the area code if you do not specify it.
•5555000 = Fixed caller 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.
|
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.
|
Presentation Bit
|
Choose whether the central office transmits or blocks caller ID.
Choose Allowed if you want the central office to send caller ID.
Choose Restricted if you do not want the central office to send caller ID.
|
Display IE Delivery
|
Check the check box to enable delivery of the display IE in SETUP and CONNECT messages for the calling and called party name delivery service.
Default leaves Display IE Delivery check box unchecked.
|
Gatekeeper Name
|
Choose the Domain Name Service (DNS) name or IP address of the H.323 gatekeeper.
A gatekeeper H.323 entity on the LAN supports the H.225 RAS message set used for admission control, bandwidth allocation, and dial pattern resolution. It controls access to the LAN for connections between H.323-compliant devices such as terminals and gateways.
Use only for H.323-compliant gateways. All other devices do not use this box:
•If your device is not gatekeeper controlled, choose None.
•If a remote gatekeeper controls the H.225 device, choose the name of the gatekeeper from the drop-down list.
|
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.
|
Num Digits
|
Choose the number of significant digits to collect, from 0 to 32.
Cisco CallManager counts significant digits from the right (last digit) of the number called.
Use this field if you enable Sig Digits. Use for the processing of incoming calls and to indicate the number of digits starting from the last digit of the called number used to route calls coming into the H.323 device. See Prefix DN and Sig Digits.
|
Sig Digits
|
Significant digits represent the number of final digits retained on inbound calls. A trunk with significant digits enabled truncates all but the final few digits of the address provided by an inbound call.
Check or uncheck this box depending on whether you want to collect significant digits.
If check box is unchecked, the Cisco CallManager does not truncate the inbound number.
If check box is checked, you also need to choose the number of significant digits to collect (see Num Digits).
|
Prefix DN
|
Enter the prefix digits that are appended to the called party number on incoming calls.
The Cisco CallManager adds prefix digits after first truncating the number in accordance with the Num Digits setting.
|
Run H225D On Every Node
|
This option determines which Cisco CallManager in the cluster establishes the H.225 session. The default setting (checked) establishes the H.225 session on the Cisco CallManager where the calling device has registered. For most systems, the default setting works best.
Caution Unchecking this check box establishes the H.255 session on the controlling Cisco CallManager in the same Cisco CallManager group and device pool as the H.225 gateway. Do not uncheck this box unless advised to do so by Cisco Technical Assistance (TAC).
|
Called party IE number type unknown
|
Choose the format for the type of number in called party directory numbers. Cisco 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 CallManager does not recognize European national dialing patterns. You can also change this setting when connecting to PBXs using routing as a non-national type number.
Choose one of the following options:
•CallManager—The Cisco 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 type of number in calling party directory numbers.
Cisco 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 CallManager does not recognize European national dialing patterns. You can also change this setting when connecting to PBXs using routing as a non-national type number.
Choose one of the following options:
•CallManager—The Cisco 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 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 CallManager does not recognize European national dialing patterns. You can also change this setting when connecting to PBXs using routing as a non-national type number.
Choose one of the following options:
•CallManager—The Cisco 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 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 CallManager does not recognize European national dialing patterns. You can also change this setting when connecting to PBXs using routing as a non-national type number.
Choose one of the following options:
•CallManager—The Cisco 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.
|
Related Topics
•Adding a Cisco IOS H.323 Gateway or Intercluster Trunk
•Updating Gateways and Ports
•Gateway Configuration
Analog Access Gateway Configuration Settings
Table 41-6 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 41-7 Access Analog Gateway Configuration Settings
Field
|
Description
|
MAC Address
|
Enter the media access control address. Make sure that you enter a 12-hexadecimal character value. The MAC address uniquely identifies hardware-based devices.
|
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.
|
Load Information
|
Enter the appropriate load information for the custom software for gateway.
The values you enter here override the default values for this gateway.
|
Country Code
|
Choose the country in which the gateway is located.
|
Location
|
Choose the appropriate location for this device. The location specifies the total bandwidth 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 consumed by this device.
|
Calling Search Space
|
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.
|
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, among the available media resources according to the priority order defined in a Media Resource Group List.
|
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.
|
Related Topics
•Adding an Analog Access Gateway and Ports, page 41-13
•Updating Gateways and Ports
•Gateway Configuration
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" section.
POTS Port Configuration Settings
Table 41-8 POTS Port Configuration Settings
Field
|
Description
|
Port Type
|
Choose POTS from the Port Type drop-down list box.
|
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 passing 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 specifies the gain or loss applied to the received audio signal relative to the port application type.
|
Audio Signal Adjustment from IP Network
|
This specifies the gain or loss applied to the transmitted audio signal relative to the port application type.
|
Prefix DN
|
Enter the prefix digits that are appended to the digits this trunk receives on incoming calls.
The Cisco CallManager adds prefix digits after truncating the number in accordance with the Num Digits setting.
|
Num Digits
|
Enter the number of significant digits to collect, from 0 to 32.
Cisco 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 used to route calls coming into the PRI span. See Prefix DN.
|
Expected Digits
|
Enter the number of digits 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-5000ms)
|
Call Restart Timer (1000-5000ms); ms indicates time in milliseconds.
|
Offhook Validation Timer (100-1000ms)
|
Offhook Validation Timer (100-1000ms); ms indicates time in milliseconds.
|
Onhook Validation Timer (100-1000ms)
|
Onhook Validation Timer (100-1000ms); ms indicates time in milliseconds.
|
Hookflash Timer (100-1500ms)
|
Hookflash Timer (100-1500ms); ms indicates time in milliseconds.
|
SMDI Port Number (0-4096)
|
Use this field for analog access ports that connect to a voice-mail system.
Set the SMDI Port Number equal to the actual port number on the voice-mail system to which the analog access port connects.
|
Product-Specific Configuration
|
Model-specific configuration fields 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 pane.
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, page 41-13
•Gateway Configuration
•Adding Gateways to Cisco CallManager
Loop Start Port Configuration Settings
Table 41-9 Loop Start Port Configuration Settings
Field
|
Description
|
Port Type
|
Choose Loop Start from the Port Type drop-down list box.
|
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 passing through this port:
•Inbound—Use for incoming calls only.
•Outbound—Use for outgoing calls.
•Both Ways—Use for inbound and outbound calls.
|
Audio Signal Adjustment into IP Network
|
This specifies the gain or loss applied to the received audio signal relative to the port application type.
|
Audio Signal Adjustment from IP Network
|
This specifies the gain or loss applied to the transmitted audio signal relative to the port application type.
|
Caller ID Enable
|
Check this check box to enable Caller ID.
|
Attendant DN
|
Enter the directory number to which you want incoming calls routed; for example, zero or a directory number for an attendant.
|
Delay Before Dialing Timer (100-5000ms)
|
Delay Before Dialing Timer (100-5000ms); ms indicates time in milliseconds.
|
Release Guard Timer (100-5000ms)
|
Release Guard Timer (100-5000ms); ms indicates time in milliseconds
|
Incoming Ring Halt Timer (1000-8000ms)
|
Incoming Ring Halt Timer (1000-8000ms); ms indicates time in milliseconds.
|
Incoming Ring Validation Timer (100-2000ms)
|
Incoming Ring Validation Timer (100-2000ms); ms indicates time in milliseconds.
|
Product-Specific Configurations
|
Model-specific configuration fields 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 pane.
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
•Adding Gateways to Cisco CallManager
Ground Start Port Configuration Settings
Table 41-10 Ground Start Port Configuration Settings
Field
|
Description
|
Port Type
|
Choose Ground Start from the Port Type drop-down list box.
|
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 passing 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 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 pane.
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
•Adding Gateways to Cisco CallManager
E & M Port Configuration Settings
E & M (Ear and Mouth or receive and transit) ports allow connection for PBX trunk lines (tie lines). E & M designates a signaling technique for two-wire and four-wire telephone and trunk intefaces.
E & M port configuration values must match those of the PBX to which the port connects. Refer to the documentation that came with your specific PBX for the appropriate E & M voice-port configuration values.
Table 41-11 E & M Port Configuration Settings
Field
|
Description
|
Port Type
|
Choose EANDM from the Port Type drop-down list box.
|
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 passing through this port:
•Inbound—Use for incoming calls only.
•Outbound—Use for outgoing calls.
•Both Ways—Use for inbound and outbound calls.
|
Calling Party Selection
|
Because any outbound call on a gateway can send directory number information, choose which directory number to send:
•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.
|
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
|
Caller ID Type
|
Choose the type of caller ID that displays to the called party:
•ANI—Automatic number identification displays the number of the calling party.
•DNIS—Dialed number identification service displays the number that the caller dialed.
|
Caller ID DN
|
Enter the pattern 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, for 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.
|
Prefix DN
|
Enter the prefix digits that are appended to the called party number on incoming calls.
The Cisco 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 CallManager counts significant digits from the right (last digit) of the number 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 used to route calls coming into the PRI span. See Prefix DN and Sig Digits.
|
Expected Digits
|
Enter the number of digits 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 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 pane.
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
•Adding Gateways to Cisco CallManager
Finding Specific Gateways
Because you might have hundreds of gateways in your network, Cisco CallManager lets you locate specific gateways based on specific criteria. Use these sections to find specific gateways:
•Searching by Device Name
•Searching by Description
•Searching by Directory Number
•Searching by Calling Search Space
•Searching by Device Pool
•Searching by Route Group
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 registered with Cisco CallManager.
Procedure
Step 1 Choose Device > Gateway.
The Find and List Gateways pane appears.
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 pane 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 of the gateways on the pane by checking the check box in the matching records title bar.
Related Topics
•Searching by Description
•Searching by Directory Number
•Searching by Calling Search Space
•Searching by Device Pool
•Searching by Route Group
Searching by Description
Use this procedure if you know any of the key words used in the Description field of a specific gateway registered with Cisco CallManager.
Procedure
Step 1 Choose Device > Gateway.
The Find and List Gateways pane appears.
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 ResetYou can delete or reset multiple gateways from the Find and List Gateways pane 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 of the gateways on the pane by checking the check box in the matching records title bar.
Related Topics
•Searching by Device Name
•Searching by Directory Number
•Searching by Calling Search Space
•Searching by Device Pool
•Searching by Route Group
Searching by Directory Number
Use this procedure to locate gateways assigned to a specific extension or range of extensions and registered with Cisco CallManager.
Procedure
Step 1 Choose Device > Gateway.
The Find and List Gateways pane appears.
Step 2 From the drop-down list box, choose Directory Number; 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 name
•Description (if applicable)
•Status
•IP address
Note You can delete or reset multiple gateways from the Find and List Gateways pane 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 of the gateways on the pane 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 Calling Search Space
Use this procedure to locate gateways assigned to a calling search space and registered with Cisco CallManager.
Procedure
Step 1 Choose Device > Gateway.
The Find and List Gateways pane appears.
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.
Tips You can locate an existing calling search space by choosing one from the drop-down list box under the Find button. This automatically inserts the name of the calling search space you choose into the Find field.
Step 4 Click Find.
A list of discovered gateways displays by:
•Calling search space
•Device name
•Description (if applicable)
•Status
•IP address
Note You can delete or reset multiple gateways from the Find and List Gateways pane 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 of the gateways on the pane by checking the check box in the matching records title bar.
Related Topics
•Searching by Device Name
•Searching by Description
•Searching by Directory Number
•Searching by Device Pool
•Searching by Route Group
Searching by Device Pool
Use this procedure to locate gateways assigned to a specific device pool and registered with Cisco CallManager.
Procedure
Step 1 Choose Device > Gateway.
The Find and List Gateways pane appears.
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.
Tips You can locate an existing device pool by choosing one from the drop-down list box under the Find button. This automatically inserts the name of the device pool you choose into the Find field.
Step 4 Click Find.
A list of discovered gateways displays by:
•Device pool
•Device name
•Description (if applicable)
•Status
•IP address
Note You can delete or reset multiple gateways from the Find and List Gateways pane 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 of the gateways on the pane by checking the check box in the matching records title bar.
Related Topics
•Searching by Device Name
•Searching by Description
•Searching by Directory Number
•Searching by Calling Search Space
•Searching by Route Group
Searching by Route Group
Use this procedure to locate gateways assigned to a specific route group and registered with Cisco CallManager.
Procedure
Step 1 Choose Device > Gateway.
The Find and List Gateways pane appears.
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.
Tips You can locate an existing route group by choosing one from the drop-down list box under the Find button. This automatically inserts the name of the route group you choose into the Find field.
Step 4 Click Find.
A list of discovered gateways displays by:
•Route group priority)
•Device name (port)
•Description (if applicable)
•Status
•IP address
Note You can delete or reset multiple gateways from the Find and List Gateways pane 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 of the gateways on the pane by checking the check box in the matching records title bar.
Related Topics
•Searching by Device Name
•Searching by Description
•Searching by Directory Number
•Searching by Calling Search Space
•Searching by Device Pool
Modifying Gateways and Ports
Using Cisco CallManager, you perform the following tasks identically regardless of the gateway type:
•Deleting Gateways
•Resetting and Restarting Gateways
•Updating Gateways and Ports
Deleting Gateways
Complete the following steps to delete a gateway from Cisco CallManager.
Procedure
Step 1 Choose Device > Gateway.
The Find and List Gateways pane appears.
Step 2 Enter search criteria to locate a specific gateway.
Step 3 Click Find.
A list of discovered gateways matching your search criteria displays.
Step 4 Check the check box next to the gateway you want to delete.
Step 5 Click Delete Selected.
A message displays stating that you cannot undo this action.
Step 6 Click OK to delete the gateway, or Cancel to cancel the operation.
Tips You can delete all of the gateways on the pane by checking the check box in the matching records title bar and clicking Delete Selected.
Related Topics
•Adding Gateways to Cisco CallManager
•Finding Specific Gateways
Resetting and Restarting Gateways
Complete the following steps to reset or restart a gateway using Cisco CallManager.
Procedure
Step 1 Choose Device > Gateway.
The Find and List Gateway pane appears.
Step 2 Enter search criteria to locate a specific gateway.
Step 3 Click Find.
A list of discovered gateways matching your search criteria displays.
Step 4 Check the check box next to the gateway you want to reset.
Step 5 Click Reset Selected.
The Reset Gateway(s) pane appears.
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.
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 CallManager.
Procedure
Step 1 Choose Device > Gateway.
The Find and List Gateways pane appears.
Step 2 Enter search criteria to locate a specific gateway.
Step 3 Click Find.
A list of discovered devices displays.
Step 4 Click the Device Name of the gateway you want to update.
The Gateway Configuration pane appears.
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 pane for the selected 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 Reset the gateway to apply the changes.
Related Topics
•Adding Gateways to Cisco CallManager
•Finding Specific Gateways
•Resetting and Restarting Gateways
•Deleting Gateways
Feedback
