[cisco-voip] MGCP ISDN call failing due to calling party plan being wrong

[Erick Bergquist]

FYI, Figured this out and got it fixed. There was an Adtran device muxing and rewriting the call information that no one had mentioned and took awhile to discover it and where it was. Thanks all. 

----- Original Message ----
From: Wes Sisk <wsisk at cisco.com>
To: Erick Bergquist <erickbe at yahoo.com>
Cc: ciscovoip <cisco-voip at puck.nether.net>
Sent: Monday, November 27, 2006 7:28:58 PM
Subject: Re: [cisco-voip] MGCP ISDN call failing due to calling party plan being wrong

It shouldn't make any difference but,

with MGCP BH, you're using CM's ISDN stack - trust what's in the CCM  
traces more than the gw debugs.
take one T1 gw port and flip it to an h323 config to see if the  
router ISDN stack offers any difference.

Next consider that you going be going out of the GW into another T1  
Mux or some other interim device that is re-writing what is sent out  
of the router.  Set the calling plan to something else obviously  
wrong/different and send a call.  verify in the CM traces you see  
different bits.  If the carrier says the same problem, then look for  
an interim device.

/Wes

On Nov 27, 2006, at 4:27 PM, Erick Bergquist wrote:

Hi,

I have a strange issue, where the telco is refusing a 411 call on 1  
out of 3 PRIs. All 3 are set up the same on the CCM side. The called  
party plan and type is set to unknown and unknown.  411 calls work on  
the other 2 PRIs fine but not the one. On the one, the carrier is  
seeing the calling party plan as being private_numbering_plan with an  
abrreviated number.  The router Q931 and CCM Detailed traces show  
Unknown and Unknown for both of those on all the calls. If we swap  
just the T1 PRI cables between router interfaces, the problem follows  
the PRI circuit - not the ports on gateway.

Another odd thing is, on a working LD call carrier saw that with a  
calling party plan of National. The gateway configuration pages in  
CCM are set for unknown for called party number.  MGCP has been reset  
a few times, and config download to refreshed from the router as  
well. The CCM servers were rebooted as well

I have been to telco on this a couple times, and escalated, and they  
keep seeing the same thing where the call fails because of private  
numbering plan. We changed the called number plan to all the other  
settings also and nothing seems to help, and the CCM Detailed and  
q931 debugs show the information correct as it is configured at time.

Has anyone seen anything like this before?


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip






 
____________________________________________________________________________________
Cheap talk?
Check out Yahoo! Messenger's low PC-to-Phone call rates.
http://voice.yahoo.com