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. And see here for current known issues.

New Member

Default dial peer not matching, very strange.

Hello there,

for some reason my default dial-peer is not matching, here is what i got:

cisco(config-dial-peer)#do sh run | sec dial-peer voice 50 pots

dial-peer voice 50 pots

trunkgroup 40

trunkgroup 50

corlist outgoing listNoANI

description Outgoing International to Qwest

destination-pattern 011T

prefix 011

cisco(config-dial-peer)#

and here is what i get when i look to match a number:

cisco(config-dial-peer)#do sh dialplan number 01197234

Macro Exp.: 01197234

No match, result=1

cisco(config-dial-peer)#

am i missing something here??

Thanks in advance,

J.

10 REPLIES

Re: Default dial peer not matching, very strange.

Hi J,

I'm not sure if the show dialplan number command will work with the corlist applied. You can try taking the corlist off and trying the command again.

As well, you can do a 'show dial peer voice summary' and see if the outgoing status of that dial peer is "UP". If the trunkgroups aren't up, it won't let you dial out.

-nick

New Member

Re: Default dial peer not matching, very strange.

Hey Nick,

i removed the corlist but still the same result, as far as the dial peer its up and up :(.

have a look:

cisco#sh run | sec dial-peer voice 50 pots

dial-peer voice 50 pots

trunkgroup 40

trunkgroup 50

description Outgoing International to Qwest

destination-pattern 011T

prefix 011

cisco#sh dialpl

cisco#sh dialplan num

cisco#sh dialplan number 011345

Macro Exp.: 011345

No match, result=1

wtild3#

..

50 pots up up 011 011T 0 up trunkgroup 40

I am starting to think it may be something else in the config, as i have the same behavior on 2 other devices, what else may have an effect on such a think?

J.

Re: Default dial peer not matching, very strange.

Hi J,

There must be something wrong with the trunk groups then - I would try removing 40 and testing, and then try removing 50 and testing.

If you try removing the port from the trunk group, do you get the same result?

-nick

New Member

Re: Default dial peer not matching, very strange.

hey nick,

once again no luck boss:

wtild3(config-dial-peer)#do sh run | sec dial-peer voice 50 pots

dial-peer voice 50 pots

description Outgoing International to Qwest

destination-pattern 011T

port 7/0:D

prefix 011

wtild3(config-dial-peer)#do sh dialplan number 011234

Macro Exp.: 011234

No match, result=1

wtild3(config-dial-peer)#

its a little crazy here, would you like to jump in the device and have a look?

J.

Re: Default dial peer not matching, very strange.

what does 'show isdn status' show for 7/0:D?

-nick

New Member

Re: Default dial peer not matching, very strange.

Hey,

here we go:

ISDN Serial7/0:23 interface

dsl 8, interface ISDN Switchtype = primary-dms100

Layer 1 Status:

ACTIVE

Layer 2 Status:

TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED

Layer 3 Status:

0 Active Layer 3 Call(s)

Active dsl 8 CCBs = 0

The Free Channel Mask: 0x807FFFFF

Number of L2 Discards = 0, L2 Session ID = 1

50 pots up up 011 011T 0 up 7/0:D

cisco#

cisco#sh run | sec dial-peer voice 50 pots

dial-peer voice 50 pots

description Outgoing International to Qwest

destination-pattern 011T

port 7/0:D

prefix 011

cisco#

J.

Re: Default dial peer not matching, very strange.

If you try dialing out, does it work? Or is it a problem with the 'show dialplan' command?

There doesn't appear to be any reason for that not to route the call, unless you've got some other configuration not shown that is conflicting.

-nick

New Member

Re: Default dial peer not matching, very strange.

Hey Nick,

I have just tested it by making a call and it worked.....which is great...

should have though about testing it before but it was hard to find a down time on the device.

from these i would assume as you said that it may be a problem with the show dialplan command working with the T , as when i changed it to 011234 and tried the command it worked.

i guess that gateway dont like T's for some off reason.

thanks for all the help, it looks like we found the problem.

Regards,

Jonathan

New Member

Hi J.Use the timeout keyword

Hi J.

Use the timeout keyword to enable matching variable-length destination patters associated with dial peers

show dialplan number 01197234 timeout

Hope it helps.

Fei

New Member

It was right, I had the same

It was right, I had the same problem with a dial-peer ".T" and a "no match" on the "show dialplan number XXX" command.

Then I added the timeout argument and the dial-peer matched

Thanks fei.he

2099
Views
5
Helpful
10
Replies
CreatePlease to create content