mgcp pri busy tone

[rvincent]

I have call mgr 3.3(3) with a 3745 mgcp gateway with 6 pri's. Can not make a call over 2 of the pri's (controller 3). Always get a reorder tone.

Everything looks fine. ISDN status is good, contr are up. call mgr shows them registered, but will not pass a call over them.

They are the 1st choice in the route list & never get a call on them. Perf mon shows all channels are idle & d channel is in service.

I set up a test route pattern to pick that pri only & that's when I get reorder tone.

Has anyone seen this?

thanks

rob

[rzanett]

Are all of your PRIs the same? That is, are some only for inbound calls and some for outbound or are they setup to handle bothways?

Have you tried running any ISDN debugs on the gateway or traces on callmanager? This will more than likely tell what is up.

Bob

[jmatteo]

I have a 3725 w/ 2 PRI's at a customer site and ran into what sounds like a similar problem. See attached info regarding the ticket that was opened. You might want to look into this with TAC:

May 4 16:09:47.918: send_mgcp_msg, MGCP Packet sent to 10.10.10.3:2427 --->

May 4 16:09:47.918: 400 157181 Voice call setup failed

<---

*** Service Request LOG 2004-05-04 21:13:07.0 GMT, THFERGUS, Action Type: Resolution Summary ***

The above debugs match symptoms for software defect CSCee27950:

Symptoms:

---------

When a call from the PSTN is received on a Cisco 2600 MGCP gateway, the calling

party will receive a fast busy tone and the call will fail if it comes in on

timeslot 2. This has also been observed on random timeslots as well.

The first call on timeslots 1 will work fine. In the CallManager trace you

will

see the following error: 400 12813 Voice call setup failed.

Conditions:

-----------

This symptom is observed on timeslot 2 of a Cisco 2600 gateway configured for

MGCP

protocol. Cisco 3660 router is running IOS Release 12.3(5b).

Workaround:

-----------

Busy out B-Channel from Cisco CallManager service parameters. This is in the

Advance settings of the CM service parameters.

ChangeBChannelMaintenanceStatus1

Or remove the following command from the configs ..

ccm-manager config

*** Service Request LOG 2004-05-04 21:14:21.0 GMT, THFERGUS, Action Type: Resolution Summary ***

The second b-channel for pri connected to controller 2/0 has been busied out.

Incoming calls are no longer hitting this b-channel and are completing

successfully.