Solved: Re: Outbound dialing issues with new prefix - Page 2

Ray Morehead · ‎05-21-2012

We are having an issue with a new prefix when dialing out....

Its supposed to be a local number but when my customer tries to dial the outside digit 9 plus the local number they get a busy signal.

If they dial it 9+1 then they are able to get out but it charges them long distance even though its a local call.

Has anyone dealt with this? or does anyone know how to fix this?

FYI....im 6 months new at dealing with cucm so my knowledge of the system is still limited...

Thanks in advance for your help..

Ayodeji Okanlawon · ‎05-22-2012

"debug isdn q931"

so before you do your test call

type.debug isdn q931 on this gateway

after your test call type

undebug all

Please rate all useful posts

Ray Morehead · ‎05-22-2012

It only tells me that debugging is on, when I make a test call nothing happens...am i missing a command?

~Ray

Ayodeji Okanlawon · ‎05-22-2012

did you telnet to the router? then you need have terminal monitor enabled..How big is the site? If its a very large site with hundreds of calls then we need to configure debugging to be logged into a buffer. If its a small site, then on the router (not the config mode)

type" term mon" and do the test again.

Please rate all useful posts

Ray Morehead · ‎05-22-2012

I believe this is what your looking for....I feel dumb lol...I just did this yesterday.

Bearer Capability i = 0x8090A2

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98397

Exclusive, Channel 23

Calling Party Number i = 0x0081, '402486XXXX'

Plan:Unknown, Type:Unknown

Called Party Number i = 0xA1, '402904XXXX'

Plan:ISDN, Type:National

1757224: May 22 2012 09:37:15.235 CDT: ISDN Se0/0/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x9ADB

Cause i = 0xC28A - Prefix 1 not dialed

Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98397
Exclusive, Channel 23
Calling Party Number i = 0x0081, '402486XXXX'
Plan:Unknown, Type:Unknown
Called Party Number i = 0xA1, '402904XXXX'
Plan:ISDN, Type:National
1757224: May 22 2012 09:37:15.235 CDT: ISDN Se0/0/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x9ADB
Cause i = 0xC28A - Prefix 1 not dialed

Ayodeji Okanlawon · ‎05-22-2012

I believe you have edited this trace. Can you pleae put an arbitrary number in the calling and called number and then send the full trace. I need to see the full trace with the disconnecting message

Please rate all useful posts

Ray Morehead · ‎05-22-2012

Heres the full trace....the only thing edited are the actual numbers called.

MRH-VOICE-RTR2#debug isdn q931

debug isdn q931 is ON.

MRH-VOICE-RTR2#term mon

MRH-VOICE-RTR2#

1757357: May 22 2012 10:21:50.088 CDT: ISDN Se0/0/0:23 Q931: TX -> SETUP pd = 8 callref = 0x1B7C

Bearer Capability i = 0x8090A2

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98393

Exclusive, Channel 19

Calling Party Number i = 0x0081, '402483XXXX'

Plan:Unknown, Type:Unknown

Called Party Number i = 0xA1, '402484XXXX'

Plan:ISDN, Type:National

1757358: May 22 2012 10:21:50.120 CDT: ISDN Se0/0/0:23 Q931: RX <- CALL_PROC pd = 8 callref = 0x9B7C

Channel ID i = 0xA98393

Exclusive, Channel 19

1757359: May 22 2012 10:21:50.816 CDT: ISDN Se0/0/0:23 Q931: RX <- PROGRESS pd = 8 callref = 0x9B7C

Progress Ind i = 0x8481 - Call not end-to-end ISDN, may have in-band info

1757360: May 22 2012 10:21:52.216 CDT: ISDN Se0/0/0:23 Q931: TX -> SETUP pd = 8 callref = 0x1B7D

Bearer Capability i = 0x8090A2

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98392

Exclusive, Channel 18

Calling Party Number i = 0x0081, '402483XXXX'

Plan:Unknown, Type:Unknown

Called Party Number i = 0xA1, '402465XXXX'

Plan:ISDN, Type:National

1757361: May 22 2012 10:21:52.252 CDT: ISDN Se0/0/0:23 Q931: RX <- CALL_PROC pd = 8 callref = 0x9B7D

Channel ID i = 0xA98392

Exclusive, Channel 18

1757362: May 22 2012 10:21:52.680 CDT: ISDN Se0/0/0:23 Q931: RX <- DISCONNECT pd = 8 callref = 0x9B7D

Cause i = 0x8491 - User busy

1757363: May 22 2012 10:21:52.708 CDT: ISDN Se0/0/0:23 Q931: TX -> RELEASE pd = 8 callref = 0x1B7D

1757364: May 22 2012 10:21:52.724 CDT: ISDN Se0/0/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x9B7D

1757365: May 22 2012 10:21:53.100 CDT: ISDN Se0/0/0:23 Q931: TX -> SETUP pd = 8 callref = 0x1B7E

Bearer Capability i = 0x8090A2

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98392

Exclusive, Channel 18

Calling Party Number i = 0x0081, '402486XXXX'

Plan:Unknown, Type:Unknown

Called Party Number i = 0xA1, '402904XXXX'

Plan:ISDN, Type:National

1757366: May 22 2012 10:21:53.132 CDT: ISDN Se0/0/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x9B7E

Cause i = 0xC28A - Prefix 1 not dialed

1757367: May 22 2012 10:21:55.100 CDT: ISDN Se0/0/0:23 Q931: RX <- CONNECT pd = 8 callref = 0x9B7C

Progress Ind i = 0x8A81 - Call not end-to-end ISDN, may have in-band info

1757368: May 22 2012 10:21:55.104 CDT: ISDN Se0/0/0:23 Q931: TX -> CONNECT_ACK pd = 8 callref = 0x1B7C

MRH-VOICE-RTR2#

Ray Morehead · ‎05-22-2012

We also have a call in to Windstream but have yet to hear back from them.

~Ray

Ayodeji Okanlawon · ‎05-22-2012

SO the first call gets a user busy message from the Telco.

Calling Party Number i = 0x0081, '402483XXXX'

Plan:Unknown, Type:Unknown

Called Party Number i = 0xA1, '402465XXXX'

1757362: May 22 2012 10:21:52.680 CDT: ISDN Se0/0/0:23 Q931: RX <- DISCONNECT pd = 8 callref = 0x9B7D

Cause i = 0x8491 - User busy

I belive this call should be fine if the other phone is not on a call or faulty. This looks ok.

The second call does not even get setup. Once the gateway sends a setup request your telco disconnects the call.

Cause i = 0xC28A - Prefix 1 not dialed

I think you need to speak with your telco. Not much you can do and its not a cucm problem.

HTH, please rate useful posts

Please rate all useful posts

Ray Morehead · ‎05-22-2012

Yep, thats what I was wondering....

Thanks for helping me confirm this. I have a call into windstream so I will update this post after I find out what they say.

~Ray

Ray Morehead · ‎05-25-2012

Update on this....

We contacted windstream and it turns out that they had this particular prefix blocked for some reason.

Now it works....

Thanks so much for your help!!

~Ray