Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
705
Views
0
Helpful
8
Replies

All outbound LD calls default to "local" dial-peer

jelzein
Level 1
Level 1

‎08-16-2007 10:44 AM - edited ‎03-14-2019 11:06 PM

Hello experts,

This is a new small office VoIP setup utilizing a 2851 Integrated Services router. System is fully configured and working for the most part -- internal and local outbound calls work as well as incoming calls. I have 2 dial-peers for outbound calling that i'm concerned about, one for local, one for long-distance.

All outbound calls are matching the first dial-peer "9.......", even though users specifiy "91..........". I'm not sure why. I have COR's setup, but have double-checked to make sure they're acurate.

Any help would be greately appreciated.

COR's and dial-peer config:

!

!

dial-peer cor custom

name internal

name local

name domestic

name international

!

dial-peer cor list call-internal

member internal

!

dial-peer cor list call-local

member local

!

dial-peer cor list call-domestic

member domestic

!

dial-peer cor list call-international

member international

!

dial-peer cor list user-internal

member internal

!

dial-peer cor list user-local

member internal

member local

!

dial-peer cor list user-domestic

member internal

member local

member domestic

!

dial-peer cor list user-international

member internal

member local

member domestic

member international

!

dial-peer voice 1 pots

description ** T1 PRI pots dial-peer **

destination-pattern 911

port 0/1/0:23

forward-digits all

!

dial-peer voice 2 pots

description ** T1 PRI pots dial-peer **

destination-pattern 9911

port 0/1/0:23

forward-digits 3

!

dial-peer voice 3 pots

description ** T1 PRI pots dial-peer **

destination-pattern 9.......

port 0/1/0:23

forward-digits 7

!

dial-peer voice 4 pots

description ** T1 PRI pots dial-peer **

destination-pattern 91..........

port 0/1/0:23

forward-digits 10

prefix 1

!

dial-peer voice 5 pots

corlist outgoing call-international

description ** T1 PRI pots dial-peer **

destination-pattern 9011T

port 0/1/0:23

forward-digits all

!

dial-peer voice 8 pots

description ** T1 PRI pots dial-peer **

incoming called-number .

direct-inward-dial

port 0/1/0:23

!

dial-peer voice 40 voip

description ** cue voicemail pilot number **

translation-profile outgoing PSTN_CallForwarding

destination-pattern 4240

session protocol sipv2

session target ipv4:10.1.10.1

dtmf-relay sip-notify

codec g711ulaw

no vad

!

dial-peer voice 41 voip

description ** cue auto attendant number **

translation-profile outgoing PSTN_CallForwarding

destination-pattern 4250

session protocol sipv2

session target ipv4:10.1.10.1

dtmf-relay sip-notify

codec g711ulaw

no vad

!

Additionally, running a "show dialplan number" on a long-distance number shows a match with dial-peer 3 (local). I can't figure out why???

Any help would be greatly appreciated.

Thanks,

Jad

Labels:
0 Helpful
8 Replies 8

paolo bevilacqua
Hall of Fame
Hall of Fame

‎08-16-2007 10:47 AM

Hi, try:

dial-peer voice 3 pots

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

Hope this helps, please rate post if it does!

0 Helpful

jelzein
Level 1
Level 1
In response to paolo bevilacqua

‎08-16-2007 10:53 AM

that didn't change much. I'll start dialing a 10-digit long distance number, but the phone stops at 7-digits and starts calling out.

example:

I dial a local number 123-4567 - matches dial-peer 3 and goes through fine.

I dial a long distance number 1-123-456-7890 - it stops at 1123456.

0 Helpful

paolo bevilacqua
Hall of Fame
Hall of Fame
In response to jelzein

‎08-16-2007 11:09 AM

Hi, the example you made should never match DP 3.

Please post output of "show dialplan number 915551234567".

0 Helpful

jelzein
Level 1
Level 1
In response to paolo bevilacqua

‎08-16-2007 11:13 AM

That's what i'm thinking...attached.

Preview file
13 KB
0 Helpful

paolo bevilacqua
Hall of Fame
Hall of Fame
In response to jelzein

‎08-16-2007 11:34 AM

Hi, the output indicates that now you have corlist call-domestic for DP 4, please check that the incoming DP or ephone-dn has also corresponding corlist privileges.

0 Helpful

jelzein
Level 1
Level 1
In response to paolo bevilacqua

‎08-16-2007 11:41 AM

yes, both the incoming DP and the ephone-dn are configured with that corlist...

!

dial-peer voice 3 pots

corlist outgoing call-local

description ** T1 PRI pots dial-peer **

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

port 0/1/0:23

forward-digits 7

!

dial-peer voice 4 pots

corlist outgoing call-domestic

description ** T1 PRI pots dial-peer **

huntstop

destination-pattern 91..........

no digit-strip

port 0/1/0:23

forward-digits 10

prefix 1

ephone-dn 85 dual-line

number 4285

label 4285

description Test Phone

name Visitor 4285

call-forward busy 4240

call-forward noan 4240 timeout 15

corlist incoming user-domestic

hold-alert 30 originator

corlist "user-domestic" and "call-domestic" are members of the same group...

dial-peer cor custom

name internal

name local

name domestic

name international

!

!

dial-peer cor list call-internal

member internal

!

dial-peer cor list call-local

member local

!

dial-peer cor list call-domestic

member domestic

!

dial-peer cor list call-international

member international

!

dial-peer cor list user-internal

member internal

!

dial-peer cor list user-local

member internal

member local

!

dial-peer cor list user-domestic

member internal

member local

member domestic

!

dial-peer cor list user-international

member internal

member local

member domestic

member international

0 Helpful

jelzein
Level 1
Level 1
In response to jelzein

‎08-16-2007 11:51 AM

I found the issue - the FXO dial-peers were taking presedence. I removed them for now and all is working well.

Thanks for you help!!

0 Helpful

mfcornett
Level 1
Level 1
In response to jelzein

‎04-30-2008 05:55 PM

FYI- Might help someone else....

I ran into the same problem during a recent install of CME4.2. Cisco TAC came up with the following solution:

The reason for the problem is due to the way CME accepts dialed digits. As it accepts digits one by one rather than all at once it will match the 7 digit dial-peer first when you want it to match the 10 digit dial-peer.

This can be overcome by adding a T to the end of the 7 digit dial-peer. This makes the dial-peer wait the length of the inter-digit timeout for more digits to come in. If the inter-digit timeout expires then the 7 digit dial-peer is chosen. If more digits are entered then the next best dial-peer will be chosen (the 10 digit dial-peer assuming 10 digits are entered).

Below is a sample configuration

dial-peer voice XX pots

description LOCAL

destination-pattern 91.......T

port x/x/x

dial-peer voice XX pots

description LONG DISTANCE

destination-pattern 91..........

port x/x/x

0 Helpful
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Customers Also Viewed These Support Documents