01-29-2009 06:44 AM - edited 03-13-2019 06:02 PM
My client has cm6.1 and can call all 877xxxxxxx except one get blocked by call manager. I checked with cm and sees all 877 number uses same CS and no resitriction forever. And call trace shows the called # send to MGCP GTW T1. Any idea what's cause this. Thanks for help!
Steve
01-29-2009 07:41 AM
What does 'debug mgcp packet' and 'debug isdn q931' look like from the gateway?
-nick
01-29-2009 06:43 PM
Hi Nick,
see the trace below. All other 877# calling good except this one '8777471200'. If I add POTS line as second choice, this call going thrugh POTS line. Why T1 block this # only. I don't get it. Thanks for your help.
*Apr 11 02:18:55: 200 15605 OK
I: 28F9
v=0
c=IN IP4 192.168.3.1
m=audio 19562 RTP/AVP 0 100
a=rtpmap:100 X-NSE/8000
a=fmtp:100 192-194
<---
*Apr 11 02:18:55: ISDN Se2/0:23 Q931: TX -> SETUP pd = 8 callref = 0x03EC
Bearer Capability i = 0x8090A2
Standard = CCITT
Transer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98397
Exclusive, Channel 23
Calling Party Number i = 0x0081, '7327581500'
Plan:Unknown, Type:Unknown
Called Party Number i = 0x80, '8777471200'
Plan:Unknown, Type:Unknown
*Apr 11 02:18:56: ISDN Se2/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x8
C
Cause i = 0x809C - Invalid number format (incomplete number)
*Apr 11 02:18:56: MGCP Packet received from 172.30.1.11-
01-29-2009 08:27 PM
This looks fine. I would compare it with a working SETUP to see if the numbering plan/type or called number is in a different format.
You can paste a good one here to look at if you like.
hth,
nick
02-02-2009 04:59 PM
Nick,
I post both traces here. It looks same execpt the call manager add error message for the failed call. I don't know what's the different between these two 877 #s and hope to get your opinion on how to trouble shoot this. Thanks!
********** Good call ***********
*Apr 13 00:33:21: ISDN Se2/0:23 Q931: TX -> SETUP pd = 8 callref = 0x0507
Bearer Capability i = 0x8090A2
Standard = CCITT
Transer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98397
Exclusive, Channel 23
Calling Party Number i = 0x0081, '7327581500'
Plan:Unknown, Type:Unknown
Called Party Number i = 0x80, '18775551212'
Plan:Unknown, Type:Unknown
*Apr 13 00:33:22: ISDN Se2/0:23 Q931: RX <- CALL_PROC pd = 8 callref = 0x8507
Channel ID i = 0xA98397
Exclusive, Channel 23
*Apr 13 00:33:23: ISDN Se2/0:23 Q931: RX <- ALERTING pd = 8 callref = 0x8507
Progress Ind i = 0x8088 - In-band info or appropriate now available
*Apr 13 00:33:25: ISDN Se2/0:23 Q931: RX <- CONNECT pd = 8 callref = 0x8507
*Apr 13 00:33:25: ISDN Se2/0:23 Q931: TX -> CONNECT_ACK pd = 8 callref = 0x050
*Apr 13 00:33:28: ISDN Se2/0:23 Q931: TX -> DISCONNECT pd = 8 callref = 0x0507
Cause i = 0x8090 - Normal call clearing
*Apr 13 00:33:28: ISDN Se2/0:23 Q931: RX <- RELEASE pd = 8 callref = 0x8507
*Apr 13 00:33:28: ISDN Se2/0:23 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x05
7
REDBANK_MS_3725#
******** Bad call *******************
*Apr 13 00:34:01: ISDN Se2/0:23 Q931: TX -> SETUP pd = 8 callref = 0x0508
Bearer Capability i = 0x8090A2
Standard = CCITT
Transer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98397
Exclusive, Channel 23
Calling Party Number i = 0x0081, '7327581500'
Plan:Unknown, Type:Unknown
Called Party Number i = 0x80, '18777471200'
Plan:Unknown, Type:Unknown
*Apr 13 00:34:01: ISDN Se2/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x85
8
Cause i = 0x809C - Invalid number format (incomplete number)
02-02-2009 06:07 PM
setup looks fine, have you called your telco to find out why they reply with that message??
HTH
java
if this helps, please rate
02-02-2009 06:47 PM
This is a provider problem. This is a valid SETUP, and it's obvious that they don't have a profile that you're breaking.
It's possible that the end system that receives this setup is passing to the provider because they're picky / in error.
hth,
nick
02-02-2009 06:55 PM
Will call tomorrow and let you know. Thanks!
steve
02-03-2009 07:56 AM
Steve,
From the output, the number in question is missing the first digit â1â. The error states invalid format (incomplete number). The working number is not missing this digit.
Check your route patterns and see that both numbers are using the same route pattern/route list/route group (I would recommend you use the DNA tool). Then look at your gateway and see if there are any translation rules that might be altering the number.
Let me know if this helps.
Regards,
Nathan
02-03-2009 08:19 AM
Hi Nathen,
Where do you see digit "1" is missing? I see both called # are 18775551212 and 18777471200 from output.
Thanks!
Steve
02-03-2009 08:53 AM
Hi Steve,
I based my statement on the output you posted earlier in this topic (and I pasting the relevant output here):
Called Party Number i = 0x80, '8777471200'
Plan:Unknown, Type:Unknown
*Apr 11 02:18:56: ISDN Se2/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x8
C
Cause i = 0x809C - Invalid number format (incomplete number)
Calling Party Number i = 0x0081, '7327581500'
Plan:Unknown, Type:Unknown
Called Party Number i = 0x80, '18775551212'
Am I misreading something? Hope this helps.
Thanks,
Nathan
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide