The user is unable to configure fractional or partial T1 PRI with MGCP and Cisco CallManager

Document

Wed, 11/18/2009 - 18:28
Jun 18th, 2009

Core Issue

Currently, Cisco CallManager does not support the configuration or use of a  fractional PRI when using Media Gateway Control Protocol (MGCP) PRI backhaul.

This issue is documented in Cisco bug IDs CSCed41207 and CSCdw29259.

For more information, refer to the Requirements section of How to Configure MGCP with Digital PRI and Cisco CallManager.

Resolution

For a workaround, use H.323 instead of MGCP if a fractional PRI is necessary.

As an alternative, busy-out the B-Channels that you are not using in Cisco CallManager by performing these steps:

Note: This procedure is not TAC-supported.

  1. Open Service Parameters by choosing Services > Service Parameter. Choose a server and Cisco CallManager service on the Cisco CallManager Admin page.        
  2. The device name must exactly match the gateway name on the top of the gateway configuration web page. For example, [email protected] = 0000 1111 0000 0000 0000 0001 (24 bits for T1. Channel number begins with 1 to 24 from left to right. The last one specifies the D-Channel, which is not affected. In this example, 5th-8th B-Channels are out of service).     

    Copy and paste that field into this service parameter to avoid any manual inputting mistake.  =  is mandatory and unique to distinguish the Device Name and B-Channel Maintenance Status fields. B-Channel Maintenance Status = xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx, where x can be one of these:

       
    • In service               
    • Graceful out of service. Change channel status until the active call ends if an active call exists on that channel.           
    • Forceful out of service. Tear down the active call first. Then, change channel status immediately if an active call exists on that channel.    

The system treats any other value as invalid, and the value does not take effect. Make sure that the total number of  x  is either 24 for T1 or 32 for E1. Any other invalid length or mismatch (24 for E1) gets treated as an error, and no action gets taken for that device.

Make sure to check Enable Status Poll on the GW configuration page through Cisco CallManager Admin.

For related information, refer to How to busy-out B-channels on a Catalyst 6608 module in Cisco CallManager for troubleshooting

Loading.
Kris Thompson Fri, 11/06/2009 - 08:07

This is a rather critical feature latency. When does Cisco Product Marketing intend to address this?

Actions

This Document