Why am I getting fast busy when dialing to one area code?

[gramanand31]

Dial analyzer:  Shows blocking pattern from gateway, and phone shows allow pattern.  All other area codes in the US work fine, just blocking (516) area code?

Results Summary 

Calling Party Information 

Calling Party = 3564729 

Partition = 

Device CSS = 450W-33rd_CSS 

Line CSS = 

AAR Group Name = 

AAR CSS = 

Dialed Digits = 915162220228 

Match Result = BlockThisPattern 

Called Party Number = 

Matched Pattern Information 

Pattern = 

Partition = 

Pattern Type = 

Time Zone = 

Outside Dial Tone = NO 

Call Flow 

Note: Information Not Available 

Alternate Matches 

Note: Information Not Available 

[Francisco Granados]

Run the number through the route plan report, it may belong to a block partition, then make sure that partition is not on the gws Css.

[gramanand31]

I am not blocking the dial string on the route plan report.  I am allowing 9.@ on that pattern and in that PT/CSS

[Francisco Granados]

How are you connecting to the PSTN? SIP or ISDN? Do you see the call attempting to establish? Please debug on the gateway "debug ccsip mess" or "debug isdn q931"

Thanks,

Frank

[gramanand31]

Frank we are connecting to the PSTN via ISDN.  I do see the call hit the gateway when i do a debug isdn q931.  Then get call rejected.  Below is the debug.  This only occurs when dialing 516 area code which is weird.  When i do dial analyzer from the phone it routes the pattern

    Bearer Capability i = 0x8090A2
                Standard = CCITT
                Transfer Capability = Speech
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA98392
                Exclusive, Channel 18
        Display i = 'Ryan Pirchio'
        Calling Party Number i = 0x0081, '2123564985'
                Plan:Unknown, Type:Unknown
        Called Party Number i = 0xA1, '15162220228'
                Plan:ISDN, Type:National
011008: *Nov 17 03:33:42.411: ISDN Se0/0/0:23 Q931: RX <- CALL_PROC pd = 8  callref = 0x81A5
        Channel ID i = 0xA98392
                Exclusive, Channel 18
SVC-MACEN-VGW1#
011009: *Nov 17 03:33:42.623: ISDN Se0/0/0:23 Q931: RX <- DISCONNECT pd = 8  callref = 0x81A5
        Cause i = 0x8095 - Call rejected
011010: *Nov 17 03:33:42.671: ISDN Se0/0/0:23 Q931: TX -> RELEASE pd = 8  callref = 0x01A5
011011: *Nov 17 03:33:42.695: ISDN Se0/0/0:23 Q931: RX <- RELEASE_COMP pd = 8  callref = 0x81A5
011012: *Nov 17 03:33:44.524: ISDN Se0/0/0:23 Q931: RX <- SETUP pd = 8  callref = 0x792E

[Francisco Granados · Accepted solution]

Ok, good news, I guess. The call is being rejected outside your network, the message is coming from the SP. 

RX = received message

ISDN Se0/0/0:23 Q931: RX <- DISCONNECT pd = 8  callref = 0x81A5
        Cause i = 0x8095 - Call rejected

Your calling/called numbers look good. Assuming this is happening on ANY number you call with that area code, open a ticket with your provider. 

Because your gateway is establishing the call, it rules out any issues with your CSS/partitions.

Thanks,

Frank

[gramanand31]

Yes it is all calls to that area code...That is what i suspected too.  I opened a ticket with telco and they said their end was fine.  Following up with them again!

Thank you for your help Frank!

[Francisco Granados]

You are welcome, good luck!

[gramanand31]

Update - issue is not on telco side.  We are able to dial other numbers in the 516 area code.  We can reach the number in question via cell phones but are unable to dial from Cisco to the destination.

[Amit Kumar]

Have we tried, setting PLAN and type for calling number as well. ISDN & National respectively,

Does that makes any difference.

Thanks,

Amit

[gramanand31]

I have changed it and no luck there.  Went back to original config Here is a recent debug on from the VGW.

g isdn q931 is              ON.
SVC-MACEN-VGW1#
040873: *Nov 20 06:03:36.600: ISDN Se0/0/0:23 Q931: TX -> SETUP pd = 8  callref = 0x0363
        Bearer Capability i = 0x8090A2
                Standard = CCITT
                Transfer Capability = Speech
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA98393
                Exclusive, Channel 19
        Display i = 'Ryan Pirchio'
        Calling Party Number i = 0x0081, '2123564985'
                Plan:Unknown, Type:Unknown
        Called Party Number i = 0xA1, '15162220228'
                Plan:ISDN, Type:National
040874: *Nov 20 06:03:36.648: ISDN Se0/0/0:23 Q931: RX <- CALL_PROC pd = 8  callref = 0x8363
        Channel ID i = 0xA98393
                Exclusive, Channel 19
SVC-MACEN-VGW1#
040875: *Nov 20 06:03:36.860: ISDN Se0/0/0:23 Q931: RX <- DISCONNECT pd = 8  callref = 0x8363
        Cause i = 0x809B - Destination out of order
040876: *Nov 20 06:03:36.904: ISDN Se0/0/0:23 Q931: TX -> RELEASE pd = 8  callref = 0x0363
040877: *Nov 20 06:03:36.936: ISDN Se0/0/0:23 Q931: RX <- RELEASE_COMP pd = 8  callref = 0x8363
040878: *Nov 20 06:03:37.516: ISDN Se0/0/0:23 Q931: TX -> DISCONNECT pd = 8  callref = 0x035F
        Cause i = 0x8090 - Normal call clearing
SVC-MACEN-VGW1#
040879: *Nov 20 06:03:38.052: ISDN Se0/0/0:23 Q931: RX <- RELEASE pd = 8  callref = 0x835F
040880: *Nov 20 06:03:38.080: ISDN 

[Francisco Granados]

Ok, no panic. It's still very unlikely that the issue is on what you are sending, for several reasons. 

#1. You can call other numbers.

#2. The debug shows the far end disconnecting and says it's out of order:

040875: *Nov 20 06:03:36.860: ISDN Se0/0/0:23 Q931: RX <- DISCONNECT pd = 8  callref = 0x8363
        Cause i = 0x809B - Destination out of order

It is clear that they are not supporting something we are trying to negotiate during the call. Have you tried to speak with someone from their IT staff? I have had this issue before, I end up calling the other side and most of the times they've heard from other customers. SIP migrations are a big reason why this happens, it could be the case on their end.

-Frank

[gramanand31]

It is one our remote sites, they have an older PBX on the other end.  All other calls generating from cell phones or other landlines go through.  Calls from Cisco are the only ones that fail and it is only to this number.

[Francisco Granados]

Gotcha... I recommend troubleshooting from the far end, I'm not sure what PBX you have or if you can obtain any debugs. What ever the equivalent to "debug ccapi inout" is what we need to do on that end, it will tell you why they're sending the disconnect message.

[gramanand31]

we do not have access to their old PBX, when I say old I mean early 90's.  Calls always worked there nothing changed on either end.  Very stumped at this one.  Checked my CSS dial plans, patterns, dial peers, and translation patterns.  I feel like i am banging my head against the wall on this one.