Guest

Cisco Unified Communications Manager (CallManager)

Configure MGCP Gateway and FXO/FXS Ports on a Cisco CallManager Server

Document ID: 42101

Updated: Jan 11, 2007

   Print

Introduction

This document explains how to:

  • Add a Media Gateway Control Protocol (MGCP) gateway.

  • Add and configure the Foreign Exchange Station (FXS) and Foreign Exchange Office (FXO) ports of the added gateway on Cisco CallManager 3.x and 4.x servers.

Symptoms:

You can potentially encounter this list of symptoms when you configure Cisco CallManager with Cisco IOS MGCP gateways with analog FXO and FXS ports:

  • The MGCP gateway does not register with Cisco CallManager. Refer to MGCP Gateway Registration Failure with Cisco CallManager.

  • Caller ID does not work on FXO ports. This is because caller ID is not supported with FXO ports when configured for MGCP. Configure the gateway in H.323 mode instead.

  • Overhead paging locks up FXO ports during hookflash unless users go completely off-hook. Shut followed by No shut resets the port. This is related to Cisco bug ID CSCef62275 (registered customers only) when fixed in Cisco IOS Software Release 12.3(14)T and later.

This document is part three of a six-document set.

  1. Configuring Cisco CallManager with IOS MGCP Gateways (Analog FXO, FXS Ports)

  2. Configuring the Cisco IOS® Media Gateway Control Protocol (MGCP) Gateway

  3. Configure MGCP Gateway and FXO/FXS Ports on a Cisco CallManager Server

  4. Verify and Troubleshoot the Cisco IOS MGCP Gateway

  5. Sample of Debug MGCP Packets

  6. Monitor, Reset, and Delete MGCP Gateways for Cisco CallManager

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

The information in this document is based on these software and hardware versions:

  • 1 * Cisco VG200 / 2 X FXS / 2 X FXO / 1 FastEthernet 10/100 port. Cisco IOS Software Release 12.1(5)T

  • 1 * Cisco CallManager 3.0(5a) that runs on a MCS7835

  • 1 * Cisco CallManager 3.1(2) that runs on a MCS7835

  • 1 * Cisco CallManager 3.2(2c) that runs on a MCS7835

  • 1 * Cisco CallManager 3.3(3) that runs on a MCS7835

  • 1 * Cisco CallManager 4.0(0.359) that runs on a MCS7835

  • 2 * Analog handsets

  • 2 * Cisco 7960 IP phones

This configuration was tested with Cisco CallManager 3.0, 3.1, 3.2, 3.3 and 4.0 and various versions of Cisco IOS Software Release 12.2 images.

Refer to the Cisco CallManager Compatibility Matrix for recommended compatibility software releases between Cisco CallManager and the Cisco IOS gateway.

Note: Cisco IOS Software Release 12.2(11)T and later is recommended based on the ccm-manager mgcp command enhancements. The ccm-manager mgcp command requires Cisco IOS Software Release 12.2(2)XA and later on Cisco 2600 and 3600 series and Cisco VG200 routers.

Cisco 2600, 3600, and VG200 routers support MGCP if they run Cisco IOS Software Release 12.1(3)T and later. The software release and version that you require is based on the features that you need to enable. For MGCP voice gateway interoperability with Cisco CallManager, use Cisco IOS Software Release 12.1(3)T and later for VG200 and Cisco IOS Software Release 12.2(2)XA for Cisco 2600 and 3600 series routers. The Cisco CallManager server must run 3.0(5)a or later. The Cisco CallManager and router configuration is the same for all types of routers.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

Refer to Cisco Technical Tips Conventions for more information on document conventions.

Tasks to Perform for Cisco CallManager 3.0

These configurations use the default device pool. All locations, calling search spaces, and partitions are set to None. You must understand the implications of these features before you proceed if your configuration uses non-default device pools, locations, calling search spaces, or partitions.

Task 1: Create an MGCP Gateway

A VG200-based MGCP gateway is created in this task. The material in this section also applies to other Cisco IOS MGCP routers. The only difference is the platform that you select in step 3.

  1. Use the Device Wizard to create an MGCP gateway. Select Device > Gateway.

    cm_cfg-1.gif

  2. Click Add a New Gateway when this window appears.

    cm_cfg-2.gif

  3. Select the Gateway type, in this case Cisco VG200. This changes in later software releases to reflect that platforms other than the VG200 support MGCP.

    cm_cfg-3.gif

    Note: Notice that the only option in the Device Protocol field is "Not Required for MGCP". This means that you do not need to select a protocol if the gateway is an MGCP gateway.

    Note: Select the appropriate Gateway type (such as 26xx or 36xx) if you use another Cisco IOS router. This is the only step that is different. The tasks that remain apply to the VG200 as well as the 2600 and 3600 series routers.

    Click Next.

  4. Use the actual host name you have assigned to the VG200 for the MGCP Domain Name, in this case VG200A.

    Specify the carrier module that the VG200 has installed. In this case it is an NM-2V.

    Note:  The MGCP Domain Name parameter is case-sensitive.

    Note: The voice carrier modules for the IAD2400 are different than those of the VG200, 2600, and 3600 routers.

    cm_cfg-4.gif

    Click Insert.

    Note: If the Cisco IOS router or gateway is configured with a domain name (router[config]#ip domain-name word ), the MGCP Domain Name field needs to include it. For example, VG200A.company.com.

    You have now completed the basic tasks required to create the MGCP gateway. Proceed to Task 2: Configure the FXO Ports.

Task 2: Configure the FXO Ports

The FXO ports are configured in this task. These are the ports that connect to the PSTN. The port type is determined and the attendant directory number (DN) is assigned in this procedure.

  1. Identify the Voice Interface Card (VIC) modules installed in slot 1 positions 0 and 1. There is an FXO and FXS module in this case.

    cm_cfg-5.gif

    Click Update to activate the changes.

  2. The FXO and FXS ports appear at the bottom right of this window. These are also referred to as endpoint identifiers.

    cm_cfg-6.gif

    Select the FXO port labeled 1/0/0 or the appropriate FXO port according to your configuration.

  3. Select the correct FXO Port Type.

    cm_cfg-7.gif

    Note: Loop Start is a very common configuration.

    You can safely experiment if you are not certain which option to use. You can create a new MGCP member with the Ground Start option if you cannot make or receive calls over the FXO port after you complete these VG200 and Cisco CallManager configuration tasks. You must first delete the original port configuration (MGCP member). This step is required because it is not possible to change the port type of an MGCP member once it has been created. The first window in the Task 3: Configure the FXS ports section shows the Delete option for an MGCP member.

  4. Configure your parameters on this MGCP Member Configuration window as required.

    Note: Configure an attendant DN to indicate where incoming calls need to be forwarded since the VIC-FXO card is not a direct inward dial (DID) card.

    cm_cfg-8.gif

    Note: Look for the name AALN/S1/SU0/0@VG200A in this image. This is how you can tell which MGCP device you configure (VG200A) as well as the port S1/SU0/0 = Slot 1/VIC0/Port0.

    Click Insert.

    You have now completed the basic tasks required to configure the FXO ports. Proceed to Task 3: Configure the FXS Ports.

Task 3: Configure the FXS Ports

The FXS ports are configured in this task. These are the ports that connect to the analog telephony devices (handsets in this case). The port type is determined and the DN is assigned. The MGCP gateway is reset to activate the changes at the end of this task.

  1. The left side of this window has a section that shows the ports in the VG200. Port number 1/0/0 is in bold to indicate that it is the MGCP member for the current configuration window.

    cm_cfg-9.gif

    Note: The second FXO port (1/0/1) is not used in this configuration.

    Click the text 1/1/0 to start the FXS configuration process.

  2. This window displays (Port Type—POTS [only option]) in Cisco CallManager 3.0. This window does not display in the newer Cisco CallManager software releases.

    cm_cfg-10.gif

    POTS was the only option available when this document was written. You see a window similar to the one in step 3 when you select POTS.

  3. Accept the defaults or configure your parameters on this MGCP Member Configuration window as required.

    cm_cfg-11.gif

    Click Insert when you finish.

  4. You see the Add DN option to create a DN for the port that you configure in step 3.

    cm_cfg-12.gif

    Click the Add DN text.

  5. Configure the parameters for this window as required. A DN of 6001 is used in this example.

    cm_cfg-13.gif

    Click Insert and Close to proceed to step 6.

  6. Select the Back To MGCP Configuration option.

    Repeat steps 1-5 for the FXS port that remains. The DN for the FXS port 1/1/1 is 6002 in this example.

    Note: Select Device > Gateway from the main Cisco CallManager menu at the top of the window if you lose your place in the menu system. Then select the Find option. All configured gateways appear on the window.

  7. You have now finished the FXS port configuration for the analog handsets. The gateway is reset to activate the changes in this step. Select the Back To MGCP Configuration option and click Reset Gateway.

    cm_cfg-14.gif

  8. cm_cfg-15.gif

    Click Reset.

    You have now completed the basic tasks required to configure the FXS ports and activate the MGCP gateway. Proceed to Task 4: Test the Phones for Local Connectivity.

Task 4: Test the Phones for Local Connectivity

If you have completed the tasks to configure the VG200, the VG200 now sends MGCP messages to the Cisco CallManager server in attempts to establish an MGCP relationship. The Cisco CallManager server and the VG200 are now ready to route local calls between any IP phones registered to the Cisco CallManager server and the analog phones connected to the FXS ports that were configured in Task 3.

  1. You now have dial tone on the analog phones connected to the FXS ports. Try to dial from FXS 1/1/0 to 1/1/1 (in this case DN 6001 and DN 6002). You can make and receive calls between these ports.

  2. You can also dial the IP phones that you already configured from the analog phones that you configure in Task 3. You can call the analog phones from the IP phones. Try to make calls to and from all the phones in your configuration.

    Note: Look at your partition, calling search space, device pool, and location configurations if some of your phones cannot place or receive calls. You might have a configuration that does not allow all local phones to call each other. Temporarily place one IP phone and one analog phone (FXS port) in the same partition, device pool, location, and calling search space and try the test again if this is the case.

    Note: Try to reset the gateway voice ports if you encounter issues with the Cisco IOS gateway registration or operation, as this example shows:

    router(config)#voice-port 1/0/0
    router(config-voiceport)#shutdown
    Both ports are out of service
    router(config-voiceport)#no shutdown
    

    Note: Refer to Monitor, Reset, and Delete MGCP Gateways for Cisco CallManager and Verify and Troubleshoot the Cisco IOS MGCP Gateway for more troubleshooting tasks if you still have problems.

    Proceed to Task 5: Configure a Route Pattern once you have successfully completed this task.

Task 5: Configure a Route Pattern

A simple route pattern is created to enable the phones to make calls via the PSTN in this task. The standard North American Numbering Plan (NANP) pattern of "9.@" is used.

  1. Select Route Plan > Route Pattern from the main Cisco CallManager menu.

    cm_cfg-16.gif

  2. These parameters are configured in the Route Pattern Configuration window in addition to the defaults:

    Field Name Value Meaning
    Route Pattern 9.@ Standard route pattern for dial plans that use the NANP. This route pattern is configured to provide dial tone by default.
    Gateway/ Route List AALN/S1/SU0/0@VG200A FXO 1/0/0 on VG200A
    Discard Digits PreDot Drop everything up to and including the "." in the route pattern.

    Note: The route pattern "9.@" is often used for installations outside the United States that cannot use the NANP.

    cm_cfg-17.gif

    Click Insert.

    You have now completed the entire Cisco CallManager configuration. Proceed to Verify: Test Calls Over The PSTN.

Tasks to Perform for Cisco CallManager 3.1 and 3.2

These configurations use the default device pool. All locations, calling search spaces, and partitions are set to None. You must understand the implications of these features before you proceed if your configuration uses non-default device pools, locations, calling search spaces, or partitions.

Note: The screen shots in these sections are from from the Cisco CallManager 3.2 Administration Page but still apply to Cisco CallManager 3.1.

Task 1: Create an MGCP Gateway

A VG200-based MGCP gateway is created in this task. The material in this section also applies to other Cisco IOS MGCP routers. The only difference is the platform that you select in step 3.

  1. Use the Device Wizard to create an MGCP gateway. Select Device > Gateway.

    cm_cfg-v3-1.gif

  2. Click Add a New Gateway when this window appears.

    cm_cfg-v3-2.gif

  3. Select the Gateway type, in this case Cisco VG200.

    cm_cfg-v3-3.gif

    Note: Notice that the only option in the Device Protocol field is "Not Required for MGCP". This means you do not need to select a protocol if the gateway is an MGCP gateway.

    Note: Select the appropriate Gateway type (such as 26xx or 36xx) if you use another Cisco IOS router. This is the only step that is different. The tasks that remain apply to the VG200 as well as the 2600 and 3600 series routers.

    Click Next.

  4. Use the actual host name you have assigned to the VG200 for the MGCP Domain Name, in this case VG200c.

    Specify the carrier module that the VG200 has installed. In this case it is an NM-2V. Please observe the new Cisco CallManager Group field in the configuration. Each group has an ordered list of Cisco CallManagers (maximum of three per group) to use.

    Note:  The MGCP Domain Name parameter is case-sensitive.

    Note: The voice carrier modules for the IAD2400 are different than those of the VG200, 2600, and 3600 routers.

    cm_cfg-v3-4.gif

    Click Insert.

    Note: If the Cisco IOS router or gateway is configured with a domain name (router[config]#ip domain-name word ), the MGCP Domain Name field needs to include it. For example, VG200c.company.com.

    You have now completed the basic tasks required to create the MGCP gateway. Proceed to Task 2: Configure the FXO Ports.

Task 2: Configure the FXO Ports

The FXO ports are configured in this task. These are the ports that connect to the PSTN. The port type is determined and the attendant DN is assigned in this procedure.

  1. Identify the VIC modules installed in slot 1 positions 0 and 1. There is an FXO and FXS module in this case.

    cm_cfg-v3-5.gif

    Click Update to activate the changes.

  2. The FXO and FXS ports appear at the bottom right of this window. These are also referred to as endpoint identifiers.

    cm_cfg-v3-6.gif

    Select the FXO port labeled 1/0/0 or the appropriate port according to your configuration.

  3. Select the correct FXO Port Type.

    cm_cfg-v3-7.gif

    Note: Loop Start is a very common configuration.

    You can safely experiment if you are not certain which option to use. Try the Ground Start option if you cannot make or receive calls over the FXO port after you complete these VG200 and Cisco CallManager configuration tasks. You must first delete the original port configuration. This step is required because it is not possible to change the port type of an FXO port once it has been created. The first window in the Task 3: Configure FXS ports section shows the Delete option for the FXO port.

  4. Configure your parameters for the FXO port on this Gateway Configuration window as required.

    Note: Configure an attendant DN to indicate where incoming calls need to be forwarded since the VIC-FXO card is not a DID card.

    cm_cfg-v3-8.gif

    Note: Look for the name AALN/S1/SU0/0@VG200A in this image. This is how you can tell which MGCP device you configure (VG200A) as well as the port S1/SU0/0 = Slot 1/VIC0/Port0.

    Click Insert.

    You have now completed the basic tasks required to configure the FXO ports. Proceed to Task 3: Configure the FXS Ports.

Task 3: Configure the FXS Ports

The FXS ports are configured in this task. These are the ports that connect to the analog telephony devices (handsets in this case). The port type is determined and the DN is assigned.

  1. Click the Insert button for the FXO port after configuration and this window appears. The left side has a section that shows the ports in the VG200. Port number 1/0/0 is in bold to indicate that it is the selected voice port for the current configuration.

    cm_cfg-v3-9.gif

    Note: The second FXO port (1/0/1) is not used in this configuration.

    Click the text 1/1/0 to start the FXS configuration process.

  2. Accept the defaults or configure your parameters on this Gateway Configuration window as required.

    cm_cfg-v3-10.gif

    Click Insert when you finish.

  3. This window shows the Add DN option to create a DN for the port that you configure in step 2.

    cm_cfg-v3-11.gif

    Click the Add DN text.

  4. Configure the parameters for this window as required. A DN of 2001 is used in this example.

    cm_cfg-v3-12.gif

    Click Insert to proceed to the next step.

  5. Repeat steps 1-4 for the FXS port that remains. The DN for the FXS port 1/1/1 is 2002 in this example.

    Note: Select Device > Gateway from the main Cisco CallManager menu at the top of the window if you lose your place in the menu system. Then select the Find option. All configured gateways appear on the window.

  6. This window appears when you have finished configuration of the FXS ports for the analog handsets.

    cm_cfg-v3-13.gif

  7. The gateway needs to be reset to activate the changes in this step. Select the Back To MGCP Configuration option, then click Reset Gateway. Click Reset when this window appears.

    cm_cfg-v3-14.gif

    You have now completed the basic tasks required to configure the FXS ports and activate the MGCP gateway. Proceed to Task 4: Test The Phones for Local Connectivity.

Task 4: Test the Phones for Local Connectivity

If you have completed the tasks to configure the VG200, the VG200 now sends MGCP messages to the Cisco CallManager server in attempts to establish an MGCP relationship. The Cisco CallManager server and the VG200 are now ready to route local calls between any IP phones registered to the Cisco CallManager server and the analog phones connected to the FXS ports that you configure in Task 3.

  1. You now have dial tone on the analog phones connected to the FXS ports. Try to dial from FXS 1/1/0 to 1/1/1 (in this case DN 2001 and DN 2002). You can make and receive calls between these ports.

  2. You can also dial the IP phones that you already configured from the analog phones that you configure in Task 3. You can call the analog phones from the IP phones. Try to make calls to and from all the phones in your configuration.

    Note: Look at your partition, calling search space, device pool, and location configurations if some of your phones cannot place or receive calls. You might have a configuration that does not allow all local phones to call each other. Temporarily place one IP phone and one analog phone (FXS port) in the same partition, device pool, location, and calling search space and try the test again if this is the case.

    Note: Try to reset the gateway voice ports if you encounter issues with the Cisco IOS gateway registration or operation, as this example shows:

    router(config)#voice-port 1/0/0
    router(config-voiceport)#shutdown
    Both ports are out of service
    router(config-voiceport)#no shutdown
    

    Note: Refer to Monitor, Reset, and Delete MGCP Gateways for Cisco CallManager and Verify and Troubleshoot the Cisco IOS MGCP Gateway for more troubleshooting tasks if you still have problems.

    Proceed to Task 5: Configure a Route Pattern once you have successfully completed this task.

Task 5: Configure a Route Pattern

A simple route pattern is created to enable the phones to make calls via the PSTN in this task. The standard North American Numbering Plan (NANP) pattern of "9.@" is used.

  1. Select Route Plan > Route Pattern from the main Cisco CallManager menu.

    cm_cfg-v3-15.gif

  2. These parameters are configured in the Route Pattern Configuration window in addition to the defaults:

    Field Name Value Meaning
    Route Pattern 9.@ Standard route pattern for dial plans that use the NANP. This route pattern is configured to provide dial tone by default.
    Gateway/ Route List AALN/S1/SU0/0@VG200c FXO 1/0/0 on VG200c
    Discard Digits PreDot Drop everything up to and including the "." in the route pattern.

    Note: The route pattern "9.@" is often used for installations outside the United States that cannot use the NANP.

    cm_cfg-v3-16.gif

    Click Insert.

    You have now completed the entire Cisco CallManager configuration. Proceed to Verify: Test Calls Over The PSTN.

Tasks to Perform for Cisco CallManager 3.3 and 4.0

These configurations use the default device pool. All locations, calling search spaces, and partitions are set to None. You must understand the implications of these features before you proceed if your configuration uses non-default device pools, locations, calling search spaces, or partitions.

Note: The screen shots in these sections are from the Cisco CallManager 4.0 Administration Page but still apply to Cisco CallManager 3.3.

Task 1: Create an MGCP Gateway

A VG200-based MGCP gateway is created in this task. The material in this section also applies to other Cisco IOS MGCP routers. The only difference is the platform that you select in step 3.

  1. Use the Device Wizard to create an MGCP gateway. Select Device > Gateway.

    cm_cfg-1-v4.gif

  2. Click Add a New Gateway when this window appears.

    cm_cfg-2-v4.gif

  3. Select the Gateway type, in this case Cisco VG200.

    cm_cfg-3-v4.gif

    Note: Notice that the only option in the Device Protocol field is "Not Required for MGCP". This means that you do not need to select a protocol if the gateway is an MGCP gateway.

    Note: Select the appropriate Gateway type (such as 26xx or 36xx) if you use another Cisco IOS router. This is the only step that is different. The tasks that remain apply to the VG200 as well as the 2600 and 3600 series routers.

    Click Next.

  4. Use the actual host name you have assigned to the VG200 for the Domain Name, in this case VG200c.

    Specify the carrier module that the VG200 has installed. In this case it is an NM-2V. Observe the new Cisco CallManager Group field in the configuration. Each group has an ordered list of Cisco CallManagers (maximum of three per group) to use.

    Note:  The Domain Name parameter is case-sensitive.

    Note: The voice carrier modules for the IAD2400 are different than those of the VG200, 2600, and 3600 routers.

    cm_cfg-v4-4.gif

    Click Insert.

    Note: If the Cisco IOS router or gateway is configured with a domain name (router[config]#ip domain-name word ), the MGCP Domain Name field needs to include it. For example, VG200c.company.com.

    You have now completed the basic tasks required to create the MGCP gateway. Proceed to Task 2: Configure the FXO Ports.

Task 2: Configure the FXO Ports

The FXO ports are configured in this task. These are the ports that connect to the PSTN. The port type is determined and the attendant DN is assigned in this procedure.

  1. Identify the VIC modules installed in slot 1 positions 0 and 1. There is an FXO and FXS module in this case.

    cm_cfg-5-v4.gif

    Click Update to activate the changes.

  2. The FXO and FXS ports appear at the bottom right of this window. These are also referred to as endpoint identifiers.

    cm_cfg-v4-6.gif

    Select the FXO port labeled 1/0/0 or the appropriate port according to your configuration.

  3. Select the correct FXO Port Type.

    cm_cfg-v4-7.gif

    Note: Loop Start is a very common configuration.

    You can safely experiment if you are not certain which option to use. You can use the Ground Start option to create a new MGCP member if you are not able to make or receive calls over the FXO port after you complete these VG200 and Cisco CallManager configuration tasks. You must first delete the original port configuration (MGCP member). This step is required because it is not possible to change the port type of an MGCP member once it has been created. The first window in the Task 3: Configure FXS ports section shows the Delete option for the FXO port.

  4. Configure your parameters for FXO ports on this Gateway Configuration window as required.

    Note: Configure an attendant DN to indicate where incoming calls need to be forwarded since the VIC-FXO card is not a DID card.

    cm_cfg-v4-8.gif

    Note: Look for the name AALN/S1/SU0/0@VG200c in this image. This is how you can tell which MGCP device you configure (VG200c) as well as the port S1/SU0/0 = Slot 1/VIC0/Port0.

    Click Insert.

    You have now completed the basic tasks required to configure the FXO ports. Proceed to Task 3: Configure the FXS Ports.

Task 3: Configure the FXS Ports

The FXS ports are configured in this task. These are the ports that connect to the analog telephony devices (handsets in this case). The type of port is determined and the DN is assigned.

  1. Click the Insert button for the FXO port after configuration and a window similar to this appears. The left side has a section that shows the ports in the VG200. Port number 1/0/0 is in bold to indicate that it is the selected voice port for the current configuration.

    cm_cfg-v4-9.gif

    Note: The second FXO port (1/0/1) is not used in this configuration.

    Click the text 1/1/0 to start the FXS port configuration process.

  2. Accept the defaults or configure your parameters on this Gateway Configuration window as required.

    cm_cfg-v4-10.gif

    Click Insert when you finish.

  3. This window shows the Add DN option to create a DN for the port that you configure in step 2.

    cm_cfg-v4-11.gif

    Click the Add DN text.

  4. Configure the parameters for this window as required. A DN of 2001 is used in this example.

    cm_cfg-v4-12.gif

    Note: If you want to enable call tranfer, scroll down to the Multiple Call/Call Waiting Settings section and set the Maximum Number of Calls field to 2. If this field is set to the default value of 1, the VG200 Gateway is not able to transfer calls or initiate a conference. Refer to Configuring Call Waiting and Multiple Calls Using Cisco CallManager 4.0 for more information.

    Click Add to proceed to the next step.

  5. Repeat steps 1-4 for the FXS port that remains. The DN for the FXS port 1/1/1 is 2002 in this example.

    Note: Select Device > Gateway from the main Cisco CallManager menu at the top of the window if you lose your place in the menu system. Then select the Find option. All configured gateways appear on the window.

  6. This window appears when you have finished configuration of the FXS ports for the analog handsets.

    cm_cfg-v4-13.gif

  7. The gateway needs to be reset to activate the changes in this step. Select the Back To Main Gateway Configuration option, then click Reset Gateway. Click Reset when this window appears.

    cm_cfg-v4-14.gif

    You have now completed the basic tasks required to configure the FXS ports and activate the MGCP gateway. Proceed to Task 4: Test The Phones for Local Connectivity.

Task 4: Test the Phones for Local Connectivity

If you have completed the tasks to configure the VG200, the VG200 now sends MGCP messages to the Cisco CallManager server in attempts to establish an MGCP relationship. The Cisco CallManager server and the VG200 are now ready to route local calls between any IP phones registered to the Cisco CallManager server and the analog phones connected to the FXS ports that you configure in Task 3.

  1. You now have dial tone on the analog phones connected to the FXS ports. Try to dial from FXS 1/1/0 to 1/1/1 (in this case DN 2001 and DN 2002). You can make and receive calls between these ports.

  2. You can also dial the IP phones that you already configured from the analog phones that you configure in Task 3. You can call the analog phones from the IP phones. Try to make calls to and from all the phones in your configuration.

    Note: Look at your partition, calling search space, device pool, and location configurations if some of your phones cannot place or receive calls. You might have a configuration that does not allow all local phones to call each other. Temporarily place one IP phone and one analog phone (FXS port) in the same partition, device pool, location, and calling search space and try the test again if this is the case.

    Note: Try to reset the gateway voice ports if you encounter issues with the Cisco IOS gateway registration or operation, as this example shows:

    router(config)#voice-port 1/0/0
    router(config-voiceport)#shutdown
    Both ports are out of service
    router(config-voiceport)#no shutdown
    

    Note: Refer to Monitor, Reset, and Delete MGCP Gateways for Cisco CallManager and Verify and Troubleshoot the Cisco IOS MGCP Gateway for more troubleshooting tasks if you still have problems.

    Proceed to Task 5: Configure a Route Pattern once you have successfully completed this task.

Task 5: Configure a Route Pattern

A simple route pattern is created to enable the phones to make calls via the PSTN in this task. The standard North American Numbering Plan (NANP) pattern of "9.@" is used.

  1. Select Route Plan > Route Patter/Hunt Pilot from the main Cisco CallManager menu.

    cm_cfg-16-v4.gif

  2. These parameters are configured in addition to the defaults:

    Field Name Value Meaning
    Route Pattern 9.@ Standard route pattern for dial plans that use NANP. This route pattern is configured to provide dial tone by default.
    Gateway or Route/Hunt List AALN/S1/SU0/0@VG200c FXO 1/0/0 on VG200c
    Discard Digits PreDot Drop everything up to and including the "." in the route pattern.

    Note: The route pattern "9.@" is often used for installations outside the United States that cannot use the NANP.

    cm_cfg-v4-17.gif

    Click Insert.

    You have now completed the entire Cisco CallManager configuration. Proceed to Verify: Test Calls Over The PSTN.

Verify: Test Calls Over the PSTN

You can now route calls over the PSTN from any phone on the system by dialing 9 and then the called number after the dial tone returns.

  1. Try to make a call from an analog phone.

  2. Try to make a call from an IP phone.

    Note: Refer to Monitor, Reset, and Delete MGCP Gateways for Cisco CallManager and Verify and Troubleshoot the Cisco IOS MGCP Gateway for more troubleshooting tasks if you still have problems.

Related Information

Updated: Jan 11, 2007
Document ID: 42101