Posted by: Mudassir Ali | June 11, 2010

Outgoing calls to a PSTN or PBX network through a MGCP gateway fail with symptoms like dead air or re-order tone

Outgoing calls to a PSTN or PBX network through a MGCP gateway fail with symptoms like dead air or re-order tone

VERSION 3

Core Issue

Calls to a Public Switched Telephone Network (PSTN) or PBX network through a Media Gateway Control Protocol (MGCP) gateway could fail with these symptoms:

* Silence or dead air. This could be caused by one-way voice audio. Refer to Troubleshooting One Way Voice Issues

* Re-order tone. If the re-order tone is heard before the complete number is dialed, refer the document Outgoing calls to PSTN or PBX network through a Cisco IOS gateway fail with a re-order tone before the complete number is dialed

The resolution discusses a case where the the re-order tone is heard after all the digits are dialed.

Note: For call connection issues through an H.323 gateway, refer the document Outgoing calls to PSTN/PBX network through an H.323 gateway fail with a reorder tone after all the digits are dialed

Resolution

If the re-order tone is heard after the complete number is dialed, digit manipulation could occur at the route pattern, route list or by use of translation patterns.

To address the issue, perform these steps:

1. When using translation patterns for digit manipulation, ensure that the called party is reachable by the calling party. To address calling search space partition issues, refer to Understanding and Using Partitions and Calling Search Spaces With Cisco CallManager, and ensure the transformation masks match valid Distinguished Names (DNs) or route patterns. Refer to Translation Pattern to understand how translation patterns work in Cisco CallManager.

2. If any digit manipulation is done on the route pattern, route list, or translation patterns, verify that the final result is a valid number. Adjust the digits being discarded or prepended to present a valid called party number to the PSTN. Issue the debug mgcp command on the gateway to verify the digits being sent to it. The observed event O: D/xxxxx (where x is the digit string) will show the digits collected by the gateway packet

3. Verify the registration status of the MGCP gateway with the Cisco CallManager. In Cisco CallManager 3.1 and later, the gateway configuration screen indicates whether the device is registered. With Cisco CallManager 3.0, you must look at the performance monitor or the Cisco CallManager traces to show the status of the gateway.

4. If the exit port to PSTN or PBX is an Foreign Exchange Office (FXO) port, ensure that the port direction is set to either Outbound or Both ways

5. If the gateway is Cisco IOS -based, refer to Sample of Debug MGCP Packets. If the gateway is not Cisco IOS-based, the Signaling Connection Control Part (SCCP) controlled gateways utilize Primary Rate Interface (PRI) back haul. Use the Q.931 translator that ships with the Cisco CallManager to address the failed call. The Q931 translator is found at C:Program FilesCiscoBin.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Categories

%d bloggers like this: