DialPlan External Long Distance fails with Busy Tone

[TODD BERGMAN]

Dialing 1XXX XXX XXXX fails with busy tone.

Local 7 digit works fine.

Have route pattern

1. 9.@ with filter area code does not exist

DDi predot

2. 9.1[2-9]XX[2-9]XXXXXX with filter.

area code exists

DDI predot

Running Callmanager 4.1.2 MGCP gateway to 1760 with 2port FXO.

Anyone know why I am getting a busy tone on long distance calls?

Thanks

[milay]

What is the cause code in the disconnect message? Cna you post the Q.931 for the call, from the CCM traces?

Mike

[brian-henry]

Also Route-Filters only work with the @ symbol like 9.@ or 9@. I would use DNA to see which pattern it is hitting.

Also are you stripping the digit in the route pattern or in the route-list? I have seen it give a reorder tone if stripping it on the RL and if you put it in the route pattern it works fine.

[TODD BERGMAN]

Which trace do I enable? Do you want detail or error?

This is a regular analog POTS line I am dialing out on.

[TODD BERGMAN]

This is weird. When I make an 11-digit call this error populates the windows event log in the callmanager. Looks like the gateway unregisters.

Eventid:3

Source:CiscoCallManager

Error: DeviceUnregistered - Device unregistered.

Device name.: AALN/S0/SU0/0@CMEROUTER.bergmantech.com

Device IP address.: 10.90.124.10

Device type. [Optional]: 121

Device description [Optional].: AALN/S0/SU0/0@CMEROUTER.bergmantech.com

Reason Code [Optional].: 9

App ID: Cisco CallManager

Cluster ID: CISCOCM-Cluster

Node ID: CISCOCM

Explanation: A device that has previously registered with Cisco CallManager has unregistered. This event may be issued as part of normal unregistration event or due to some other reason such as loss of keepalives.

Recommended Action: No action is required if unregistration of this device was expected..

Why would this happen and only on long distance calls?

[TODD BERGMAN]

Debug MGCP events and errors on Gateway display.

CMEROUTER#

.Feb 25 18:12:15.123: mgcp_endpt_get_call_record: null pointer specified for end

point.

.Feb 25 18:12:15.139: mgcp_call_set_error_state: callp(0x81CA5A18)

.Feb 25 18:12:15.139: -Traceback= 81606BD4 816488B8 8160A614 8160A53C 8167FF90 8

162401C 81623F30 815FD648 8021AEF8 8021F510

.Feb 25 18:12:15.139: mgcp_endpt_get_call_record: null pointer specified for end

point.

.Feb 25 18:12:15.147: mgcp_search_trans_id_rec: trans id not found. rc = 3.

[milay]

Can you set the CCM traces to detailed on the CCM the GW & the phone are registred to?

MIke

[TODD BERGMAN]

Attached is a trace with CCM All Gateway, Phone, and analog trunk set to detailed. I have so far deleted all route patterns, gateways, and upgraded IOS code on router to 123-8.T6. Wiped the router config and reprogramed the Callmanager and router.

Also, the voice gateway 1760 router config is attached.

Changed route patterns to:

9.[2-9]XXXXXX local 7 digit predot

9.1[2-9]XX[2-9]XXXXXX longdistance 11 digit predot

Local calls work fine.

Longdistance causes the gateway to imediately unregister from call manager. I can't figure it out. It makes no sense. The windows event in the previous reply takes place right after the call gets routed to the gateway.

Thank you all for helping me out.

[TODD BERGMAN]

Here is a better trace showing the gateway losing communication and unregistering. Cause code 34. Reorder Tone issued. Why is this only for Long distance calls.

[Erick Bergquist]

The router cfg looks good, and IOS is newer (12.3(8)T6) but the traceback message is indicator of bug/IOS issue usually.

And port 0/0 has pulse dialing; I haven't seen pulse used in awhile myself and not w/voip yet. The other port isn't pulse dialing. Is this the way it really is? Maybe there is something going on here funky.

Can you dial 11 digits out the 0/1 voice-port without issue or do 11 digits out either port cause mgcp reset?

You can try going in route detail/group in CCM and flipping order of ports if they are in same group or just removing 0/0 from the list for a test.

[TODD BERGMAN]

This is a using a residential POTS line with pulse dialing. Only 1 line in use in port 0/0. I can test on port 0/1. Currently only port0/0 is in the route group.

So wierd that 7 digit dialing works fine. But 11 digit doesn't. Long distance works fine with analog phone so its not the phone company.

I used to have CCME 3.2 on this router and it dialed fine for long distance. It has to be something with MGCP and Callmanager 4.1.2.

[Erick Bergquist]

Does that traceback message occur everytime you try a 11 digit dial and MGCP resets?

Can you post a 'show stack' and a 'show align' from this router?

[TODD BERGMAN]

I do not know if I get a traceback message but I can tell you that every 11 digit dial causes an MGCP reset.

Here are the show commands you requested. Should I try a different version of IOS?

voicegw#show stack

Minimum process stacks:

Free/Size Name

5608/6000 Clock Update Proc

2724/3000 allegro libretto init

5696/6000 CPE MMI SNMP

5796/12000 Init

5576/6000 RADIUS INITCONFIG

2568/3000 Rom Random Update Process

4920/6000 TFTP Read Process

6656/12000 Exec

35284/36000 TCP Command

6656/12000 Virtual Exec

6064/12000 MGCP Application

5128/6000 MGCP App STW Tick

5672/6000 MGCP App DNS

11672/12000 MGCP App TFTP

Interrupt level stacks:

Level Called Unused/Size Name

3 0 9000/9000 PA Management Int Handler

4 5716805 7944/9000 Network interfaces

5 0 9000/9000 Timebase Reference Interrupt

6 591757 8880/9000 16552 Con/Aux Interrupt

Interrupt level stacks:

Level Called Unused/Size Name

7 40224998 8920/9000 MPC860 TIMER INTERRUPT

voicegw#show align

No spurious memory references have been recorded.

[TODD BERGMAN]

Here is another Trace from CCM 11 digit call.

[Erick Bergquist]

I am not finding any specific bugs in bug toolkit or release notes from newer versions. It won't hurt if you want to try upgrading though to latest 12.3T.

Most residental lines these days are tone and not pulse dialing. I can't find reference to pulse dialing being supported or not supported with MGCP. It is not a option in the CCM web page gateway configuration pages though.

You could also configure the gateway as a H323 gateway and see how that goes.

Since this worked with CME, and MGCP resets everytime with a 11 digit call it smells like a MGCP bug/issue.

I have plenty of customers with 1760s and FXO and MGCP and haven't seen this type of problem yet, but this is also the first I've seen pulse dialing used w/MGCP so that may be a factor.