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. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Outbound dialing issues with new prefix

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..                  

Everyone's tags (5)
1 ACCEPTED SOLUTION

Accepted Solutions
VIP Super Bronze

Outbound dialing issues with new prefix

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 "The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
24 REPLIES
Hall of Fame Super Silver

Outbound dialing issues with new prefix

What system? CUCM, CME?

You need to make sure you have matching route pattern if using CUCM and dial-peer on the GW if using H323/SIP or dial-peer if using CME.

Chris

New Member

Outbound dialing issues with new prefix

We're using CUCM 8.6 skinny with VG224 gateway using dial peer.

I apologize if my lingo isnt very accurate.

Thanks for your help.

Ray

VIP Super Bronze

Outbound dialing issues with new prefix

Hi,

I amnot sure you are using Vg224 for outbound calls. You must have a different gateway to use for PSTN calls.

For local calls to work, you will need to create the appriopriate patterns to route out.

Can you give an example of a local number you are trying to dial? and can you send the config on your gateway..What type of gateway? is it MGCP or H323. On cucm, you need to also ensure that you have the proper route pattern configured

Please rate all useful posts "The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
New Member

Outbound dialing issues with new prefix

Your correct...we only use the vg224 for the analog phones in our patient rooms(this is a small hospital) as well as our faxes.

We already have a route pattern for all local calls:

Route Pattern: 9@

Route Partition: PT_MRH_Local

Numbering Plan: NANP

Route Filter: RF_Local10-digit

Discard Digits: PreAT

Why wouldnt I be able to use this pattern?

BTW...the number we are trying to reach is 9402904XXXX....we have multiple other prefixes that work just fine on this pattern. What do I need to change?

Thanks for your help!

Ray

Hall of Fame Super Silver

Outbound dialing issues with new prefix

can you post your Route Filter?

Juding by its name it is only for 10 digit dialing. For 11 digit dialing simply add following route pattern:

9.1[2-9]XX[2-9]XXXXXX

HTH,

Chris

New Member

Outbound dialing issues with new prefix

Hi Chris,

Route Filter: RF_Local10-digit

So I configured the route pattern with what you suggested, however do I need to replace the current route pattern in place for local calls or does that matter?

Hall of Fame Super Silver

Outbound dialing issues with new prefix

It depends if you need it. If 10 digit dialing does not work for any area codes then that would not be needed.

HTH, please rate all useful posts!

Chris

New Member

Outbound dialing issues with new prefix

Just did a debug on our voice router and this is what I just got back....

= 8  callref = 0x17C1

1756724: May 21 2012 15:50:51.348 CDT: ISDN Se0/0/0:23 Q931: RX <- CONNECT pd = 8  callref = 0x97C0

        Progress Ind i = 0x8482 - Destination address is non-ISDN

1756725: May 21 2012 15:50:51.352 CDT: ISDN Se0/0/0:23 Q931: TX -> CONNECT_ACK pd = 8  callref = 0x17C0

1756726: May 21 2012 15:50:53.912 CDT: ISDN Se0/0/0:23 Q931: TX -> SETUP pd = 8  callref = 0x17C3

        Bearer Capability i = 0x8090A2

                Standard = CCITT

                Transfer Capability = Speech

                Transfer Mode = Circuit

               Transfer Rate = 64 kbit/s

        Channel ID i = 0xA9838D

                Exclusive, Channel 13

        Calling Party Number i = 0x0081, '100908'

                Plan:Unknown, Type:Unknown

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

               Plan:ISDN, Type:National

1756727: May 21 2012 15:50:53.940 CDT: ISDN Se0/0/0:23 Q931: RX <- RELEASE_COMP pd = 8  callref = 0x97C3

        Cause i = 0xC28A - Prefix 1 not dialed

I'll be calling our local carrier tomorrow...I'll keep you posted.

Thanks!

Hall of Fame Super Silver

Outbound dialing issues with new prefix

Looks like you are not sendin the 1, make sure you are not stripping it on CUCM or GW if using H323/SIP for GW.

If using H323/SIP can you provide "debug voice dial-peer" and "sh run"?

Chris

New Member

Outbound dialing issues with new prefix

Chris,

We use sccp here, but i did a "debug voice dialpeers" then the show run and here is what we have configured for dial-peers. We shouldnt need to dial a 1 in order to call this prefix as it is a local number. So Im thinking this might be a carrier issue, not with cucm...unless you see something else? This config is off of our voice router.

~Ray

mgcp profile default

!

!

dial-peer voice 999000991 pots

service mgcpapp

!

dial-peer voice 1 pots

incoming called-number .

port 0/0/0:23

!

dial-peer voice 2 pots

incoming called-number .

!

dial-peer voice 9911 pots

trunkgroup Outbound-TG1

description ***** Emergency 911 *****

destination-pattern 9911

forward-digits 3

!

dial-peer voice 9100 pots                       

trunkgroup Outbound-TG1

description ***** Local *****

destination-pattern 9[2-9]..[2-9]......          <<---Wouldnt this configuration allow me to call 9402904XXXX as local?

forward-digits 10

!

dial-peer voice 9110 pots

trunkgroup Outbound-TG1

description ***** LD Dialing *****

destination-pattern 91[2-9].........

forward-digits 11

!

dial-peer voice 9411 pots

trunkgroup Outbound-TG1

description ***** Information *****

destination-pattern 9.11

forward-digits 3

!

dial-peer voice 9011 pots

trunkgroup Outbound-TG1

description ****** International Dialing *****

destination-pattern 9011T

prefix 011

!

dial-peer voice 8911 voip

description ***** Emergency 911 *****

preference 10

destination-pattern 9911

session target ipv4:10.100.4.2

!

dial-peer voice 8100 voip

description ***** Local *****

preference 10

destination-pattern 9[2-9]..[2-9]......

session target ipv4:10.100.4.2

!

dial-peer voice 8110 voip

description ***** LD Dialing *****

preference 10

destination-pattern 91[2-9].........

session target ipv4:10.100.4.2

!

dial-peer voice 8411 voip

description ***** Information *****

preference 10

destination-pattern 9.11

session target ipv4:10.100.4.2

!

dial-peer voice 8011 voip

description ****** International Dialing *****

preference 10

destination-pattern 9011T

session target ipv4:10.100.4.2

!

dial-peer voice 7000 voip

destination-pattern 7...

session target ipv4:10.115.4.2

!

!

VIP Super Bronze

Outbound dialing issues with new prefix

That will allow you. Can you do a test call and post the output of

"debug isdn q931"

so before you do your test call

type.debug isdn q931 on this gateway

after your test call type

undebug all.

If you do it quickly I can have a look and see where the call is failing

Please rate all useful posts "The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
New Member

Outbound dialing issues with new prefix

Do this on one of the gateways and not the router?

~Ray

VIP Super Bronze

Outbound dialing issues with new prefix

Ray,

on the router that connects to the PSTN

Please rate all useful posts "The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
New Member

Outbound dialing issues with new prefix

ok, whats the command for testing a call?

~Ray

VIP Super Bronze

Outbound dialing issues with new prefix

"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 "The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
New Member

Outbound dialing issues with new prefix

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

~Ray

VIP Super Bronze

Outbound dialing issues with new prefix

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 "The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
New Member

Outbound dialing issues with new prefix

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

VIP Super Bronze

Outbound dialing issues with new prefix

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 "The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
New Member

Re: Outbound dialing issues with new prefix

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#

New Member

Re: Outbound dialing issues with new prefix

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

~Ray

VIP Super Bronze

Outbound dialing issues with new prefix

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 "The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
New Member

Re: Outbound dialing issues with new prefix

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

New Member

Re: Outbound dialing issues with new prefix

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

1386
Views
0
Helpful
24
Replies