Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

cisco 3845 doing MGCP dropping int calls after about 2 min help!!

For some reason when we make an outbound international call the call suddendly drops...here is my debugs from the cisco 3845

Aug 13 15:04:37.534: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0

tei=0

Aug 13 15:04:38.534: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0

tei=0

Aug 13 15:04:38.742: //829/ED6ABD4B81A0/CCAPI/ccCallModifyExtended:

Nominator=0x70C83118, Params=0x70C82760, Call Id=829

Aug 13 15:04:38.742: //830/ED6ABD4B81A0/CCAPI/ccCallModify:

Nominator=0x800, Params=0x70C828A8, Call Id=830

Aug 13 15:04:38.742: //829/ED6ABD4B81A0/CCAPI/cc_api_call_modify_done:

Result=0, Interface=0x656D7838, Call Id=829

Aug 13 15:04:38.746: //830/ED6ABD4B81A0/CCAPI/cc_api_call_modify_done:

Result=0, Interface=0x706D7CAC, Call Id=830

Aug 13 15:04:38.750: //829/ED6ABD4B81A0/CCAPI/ccCallModify:

Nominator=0x1000, Params=0x70C830F0, Call Id=829

Aug 13 15:04:38.750: //830/ED6ABD4B81A0/CCAPI/ccGetCallStatistics:

Call Stats=0x656F3D94, Call Id=830

Aug 13 15:04:38.750: //829/ED6ABD4B81A0/CCAPI/ccConferenceDestroy:

Conference Id=0x19F, Tag=0x0

Aug 13 15:04:38.750: //829/xxxxxxxxxxxx/CCAPI/cc_api_bridge_drop_done:

Conference Id=0x19F, Source Interface=0x656D7838, Source Call

Id=829,

Destination Call Id=830, Disposition=0x0, Tag=0x0

Aug 13 15:04:38.750: //830/xxxxxxxxxxxx/CCAPI/cc_api_bridge_drop_done:

Conference Id=0x19F, Source Interface=0x706D7CAC, Source Call

Id=830,

Destination Call Id=829, Disposition=0x0, Tag=0x0

Aug 13 15:04:38.750: //829/ED6ABD4B81A0/CCAPI/cc_generic_bridge_done:

Conference Id=0x19F, Source Interface=0x706D7CAC, Source Call

Id=830,

Destination Call Id=829, Disposition=0x0, Tag=0x0

Aug 13 15:04:38.750: //829/ED6ABD4B81A0/CCAPI/ccCallDisconnect:

Cause Value=16, Tag=0x0, Call Entry(Previous Disconnect Cause=0,

Disconnect Cause=0)

Aug 13 15:04:38.750: //829/ED6ABD4B81A0/CCAPI/ccCallDisconnect:

Cause Value=16, Call Entry(Responsed=TRUE, Cause Value=16)

Aug 13 15:04:38.750: //829/ED6ABD4B81A0/CCAPI/cc_api_get_transfer_info:

Transfer Number Is Null

Aug 13 15:04:38.750: //830/ED6ABD4B81A0/CCAPI/ccCallDisconnect:

Cause Value=16, Tag=0x0, Call Entry(Previous Disconnect Cause=0,

Disconnect Cause=0)

Aug 13 15:04:38.750: //830/ED6ABD4B81A0/CCAPI/ccCallDisconnect:

Cause Value=16, Call Entry(Responsed=TRUE, Cause Value=16)

Aug 13 15:04:38.750: //829/ED6ABD4B81A0/CCAPI/cc_api_call_modify_done:

Result=0, Interface=0x656D7838, Call Id=829

Aug 13 15:04:38.750:

//830/ED6ABD4B81A0/CCAPI/cc_api_call_disconnect_done:

Disposition=0, Interface=0x706D7CAC, Tag=0x0, Call Id=830,

Call Entry(Disconnect Cause=16, Voice Class Cause Code=0, Retry

Count=0)

Aug 13 15:04:38.750:

//830/ED6ABD4B81A0/CCAPI/cc_api_call_disconnect_done:

Call Disconnect Event Sent

Aug 13 15:04:39.154: //829/ED6ABD4B81A0/CCAPI/cc_api_call_feature:

Feature Type=6, Interface=0x656D7838, Call Id=829

Aug 13 15:04:39.158:

//829/ED6ABD4B81A0/CCAPI/cc_api_call_disconnect_done:

Disposition=0, Interface=0x656D7838, Tag=0x0, Call Id=829,

Call Entry(Disconnect Cause=16, Voice Class Cause Code=0, Retry

Count=0)

Aug 13 15:04:39.158:

//829/ED6ABD4B81A0/CCAPI/cc_api_call_disconnect_done:

Call Disconnect Event Sent

8 REPLIES
New Member

Re: cisco 3845 doing MGCP dropping int calls after about 2 min h

I had an almost similar problem with CCM 5.1, SIP Phones, MGCP GW with overlap sending.

I thought it was an ISDN problem, but it was a SIP problem. Regarding the CCM traces, there was problem with SIP signaling.

As I didn't really need SIp, I changed to Skinny.

But maybe it's not your problem at all.

best regards

jp

New Member

Re: cisco 3845 doing MGCP dropping int calls after about 2 min h

well here we are using mgcp and sccp

New Member

Re: cisco 3845 doing MGCP dropping int calls after about 2 min h

The first two lines are the problem. Your gateway has issued a layer 2 reset to your carrier. Most ISDN implementations will kill layer 3 on a layer 2 reset. You made to check your timers. You would be better of debugging ISDN Q921 and ISDN Q931

Hall of Fame Super Gold

Re: cisco 3845 doing MGCP dropping int calls after about 2 min h

Russel is right but we can also suppose that router is reinitializing layer 2 consequently to a problem with layer 1. Would be interesting to see output of "show controllers T1", on the other hand based on the date of posting you have likely solved this by now.

New Member

Re: cisco 3845 doing MGCP dropping int calls after about 2 min h

I am having the same symtom with international dropped calls. After about 2 min the call will drop. It does not do it all the time but it is a problem. I am using a real basic VG-200 GW FXO to a PSTN. The GW is using H323 and a basic VOIP config. Anyone have any idea as well would be helpfull

voice-port 1/1/0

connection plar opx 4110

description FXO Gateway to PSTN Port 0

caller-id enable

dial-peer voice 110 pots

description FXO Gateway to PSTN Port 0

tone ringback alert-no-PI

destination-pattern 9.T

port 1/1/0

!

dial-peer voice 4110 voip

description - VOIP calls to call manager

preference 1

destination-pattern .T

session target ipv4:192.168.10.48

dtmf-relay h245-alphanumeric

codec g711ulaw

New Member

Re: cisco 3845 doing MGCP dropping int calls after about 2 min h

Just to check, do you have any firewalls behind your CCM?

I had a couple of times where the firewalls (like ASA and FWSM) have some H323, H225 and MGCP timers where it dropped my calls after 5 mins.

HTH,

Eugene

New Member

Re: cisco 3845 doing MGCP dropping int calls after about 2 min h

It is a straight shot to the GW. They are on the same switch (3524), VLAN and sbubnet. I though about using a data and a voice vlan but there is not enough traffic to cause this.

New Member

Re: cisco 3845 doing MGCP dropping int calls after about 2 min h

I resolved my issue after reading more post. The proble was actualy the ATA device. I only had port 1 configured and when port 2 would try to do a TFTP pulldown, it would rest the device. after disableing the port 2 on the ata. the problem went away.

382
Views
0
Helpful
8
Replies