Dial Peers, Route Patterns and Translation Rules

[Nightwolf_82]

Hi guys, 

Just several questions related to dial peers and rout patterns.

Q1. Here are my POTS dial peers.

dial-peer voice 10 pots
description **10-DIGITS LOCAL DIALING**
destination-pattern 9[2-9].........
port 0/0/0:15
forward-digits 10
!
dial-peer voice 11 pots
description **LONG DISTANCE DIALING**
destination-pattern 91[2-9]..[2-9]......
port 0/0/0:15
forward-digits 0
prefix 1
!
dial-peer voice 12 pots
description **INTERNATIONAL CALLS**
destination-pattern 9011T
port 0/0/0:15
forward-digits 0
prefix 011
!
dial-peer voice 911 pots
description **EMERGENCY NUMBER**
destination-pattern 9911
no digit-strip
port 0/0/0:15
forward-digits 3 

NY-RTR#sh dialplan number 901161248192480
Macro Exp.: 901161248192480
No match, result=1

Could you please help me to understand why the number 901161248192480 is not matched to destination-pattern 9011T.

Q2. Here are my POTS dial peers from another router. 

dial-peer voice 3 pots
description **INTERNATIONAL DIAL-PEER**
destination-pattern 00011T
port 0/0/0:15
prefix 0011
!
dial-peer voice 4 pots
description **SYDNEY LOCAL 8-DIGITS NUMBERS**
destination-pattern 0........
port 0/0/0:15
forward-digits 8

SYD-RTR#sh dial-peer voice summary
dial-peer hunt 0
AD PRE PASS OUT
TAG TYPE MIN OPER PREFIX DEST-PATTERN FER THRU SESS-TARGET STAT PORT KEEPALIVE
1 voip up up 2... 0 syst ipv4:192.168.10.5
2 pots up up 0 down 0/0/0:15
3 pots up up 0011 00011T 0 up 0/0/0:15
4 pots up up 0........ 0 up 0/0/0:15
5 pots up up 0000 0 up 0/0/0:15
SYD-RTR#show dialplan number 0001112125165510
Macro Exp.: 0001112125165510

VoiceEncapPeer4
peer type = voice, system default peer = FALSE, information type = voice,
description = `**SYDNEY LOCAL 8-DIGIT NUMBERS**',
tag = 4, destination-pattern = `0........',

How can I get the number 0001112125165510 to match dial-peer 3 instead of dial-peer 4 which is intended for 8-digits numbers?

Q3. I have route patterns on CUCM and dial-peers on voice gateway that are duplicate.

0.0011! [Digit Discard – PreDot] – for International calls
0.000! [Digit Discard – PreDot] – for emergency number calls
0.XXXXXXXX – [Digit Discard – PreDot] – 8-digits for local calls

dial-peer voice 3 pots
description **INTERNATIONAL DIAL-PEER**
destination-pattern 00011T
port 0/0/0:15
prefix 0011
!
dial-peer voice 4 pots
description **SYDNEY LOCAL 8-DIGIT NUMBERS**
destination-pattern 0........
port 0/0/0:15
forward-digits 8
!
dial-peer voice 5 pots
description **EMERGENCY NUMBER**
destination-pattern 0000
no digit-strip
port 0/0/0:15
forward-digits 3

Is that correct approach to have both CUCM and voice gateway that works in pair to have absolutely identical route patterns and dial peers? 

Thank you. 

[Mohammed al Baqari]

Hi,

For Q1, make sure that your controller is up. check the command 'show controller e1 0/0/0 br'

For Q2, break dialpeer 4 as below. This will exclude the starting digits '000' from dialpeer 4.

dial-peer voice 40 pots
description **SYDNEY LOCAL 8-DIGIT NUMBERS**
destination-pattern 0[1-9].......
port 0/0/0:15
forward-digits 8

dial-peer voice 41 pots
description **SYDNEY LOCAL 8-DIGIT NUMBERS**
destination-pattern 0.[1-9]......
port 0/0/0:15
forward-digits 8

For Q3, it depends on deployment. In some deployments of SRST this can be used to make sure that the gateway will route calls when CUCM is dead

[Nightwolf_82]

Hi guys,

A little question regarding dial peers. I know that there are dial-peer voice number voice for VoIP calls and dial-peer voice number pots for PSTN call. Today I watched video where I saw just this dial-peer voice number without specifying voip or pots. What is it for? 

Thank you.

[Suresh Hudda · Accepted solution]

Where did you see it ? If you are changing something for already defined POTS/VOIP dial peer then you don't need to mention it's type (pots or voip), it's optional then.

Suresh

[Nightwolf_82]

Yes, I know that, but in that video (by Kevin Wallace) he started to create dial-peer this way dial-peer voice 1 and nothing else. Then I thought maybe I missed something. ;)

[Nightwolf_82]

P.S. Those who worked on CCIE Voice or working on their CCIE Collaboration could you please clarify one little issue. In PSTN config from almost all training vendors there is this translation rule: 

voice translation-rule 1
rule 1 /\(^011\)\(.*\)/ /\2/
rule 2 /\(^1\)\(.*\)/ /\2/
rule 3 /\(^0\)\([^0].*\)/ /\2/ or /\(^00\)\([^0].*\)/ /\2/
rule 4 /\(^001\)\(.*\)/ /\2/

I would highly appreciate if someone could explain what 011, 1, 0 (or 00) and 001 mean.

Thank you.

[Suresh Hudda]

Rule 1: this rule will be applied to those numbers which start from 011

Rule 2: This rule will be applied to those numbers which start from 1

Rule 3: This rule will be applied to those numbers which start from 0 or 00 (these rules should be defined separately)

Rule 4: This rule will be applied to those numbers which start from 001

Note: Caret "^" symbol is to specify that matched digits are starting digits in dialing string.

http://www.cisco.com/c/en/us/support/docs/voice/call-routing-dial-plans/61083-voice-transla-rules.html

[Nightwolf_82]

Hi Suresh,

I know that ^ symbol is used to specify that matched digits are staring digits in dialling string. The question is what does 011, 1, 0 (00) and 001 mean. Are they trunk access (off net) codes or international exit codes. That's what I'm trying to clarify. 

"1" possibly means the USA country code and "011" is international exit code used in the USA which I'm not sure. More than that I can't figure out what could "0 (00)" and "001" mean. Would be grateful if someone could clarify that for me.

Thank you.

[Mohammed al Baqari]

Hi,

011 US international access code

1 US national access code

00 international access code for many country such as UK, Hong Kong, 

001 this is international call destined to US from country using 00 access internal access code (for example dialing US number from UK)

Note: My advice is to spend time understanding concepts before going to prepare for lab

[Nightwolf_82]

Hi Mohammed,

Could you please clarify if these codes that are used in most of CCIE Voice/Collaboration workbooks are used exactly the way you described.

Also, recently I came across the article about translation rules.

What if, for those same inbound calls, we want to modify the caller-id to prefix the access numbers (9, 91 or 9011) so that the calls can be dialed easily from a user’s call history? To accomplish this, we need another set of rules:
voice translation-rule 2
rule 1 /^…….$/ /9&/
rule 2 /^[2-9]..[2-9]……$/   /91&/
rule 3 /^1[2-9]..[2-9]……$/   /9&/
rule 4 /.*/    /9011&/

Imagine that I am in Chicago and someone is calling me from Boston. Does it mean on the screen of my phone display I will see something like 91617XXXXXX? What is the purpose of having 91 being displayed in front of 617XXXXXX instead of just 617XXXXXX?

Thank you.

[Evgeny Izetov]

When people see a calling number starting with "9" they know it's an external caller, as opposed to for example a 4-digit same site caller. 

People in the US are accustomed to see a local caller ID starting with 9 +10 (or 7) digits, a long-distance 91 + 10 digits, and international starting with 9011. Also depending on how the system is set up it is easier for user to dial from Missed Calls list if the number is already in a dialable format.

This is done solely for user habits. With a globalized dial plan it would make it much more simple to set up if people got used to dialing and receiving numbers in only +E.164 format.

[Nightwolf_82]

Hi Evgeny,

Thank you for your reply. There is another little gap with translation rule which I would to clarify. Here is a chunk of text from the same article.

Another action your router can take is to properly format your internal users’ caller-id for calls outbound to the PSTN. We created rules like this in Part 1. Here is a ruleset for our three sites:

voice translation-rule 3

rule 1     /^7…$/            /7035557…/

rule 2    /^3[0-4]..$/     /9725553…/

rule 3    /^5[23]..$/      /4065559…/

And here is the voice translation-profile that has the router use voice translation-rule 3 to modify caller-id:

voice translation-profile PSTN-OUT

translate calling 3

dial-peer voice 9 pots

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

translation-profile outgoing PSTN-OUT

port 0/0/0:23

This I suppose is used when the WAN is down and call flows can't go through WAN circuit. In this example dialed 7XXX/3XXX/5XXX translate into 7035557XXX/9725553XXX/4065559XXX respectively. But what about 9 for access the trunk and 1 for national dialling (if necessary)? Does translation-profile outgoing PSTN-OUT works together with destination-pattern 9[2-9]..[2-9]……? 

[Evgeny Izetov]

In this example dialed 7XXX/3XXX/5XXX won't translate into 7035557XXX/9725553XXX/4065559XXX. This translation profile only changes calling number, not called.

In real life the calling number is usually already in the correct format, taken from External Phone Number Mask field in CUCM, but it can also be manipulated in several other places in CUCM.

I'm not sure what your concern is about 9. Notice it's a pots dial-peer and that 9 is going to be stripped off.

[Nightwolf_82]

Hi guys,

Could you please help me to solve this task. Below is a diagram.

[LONDON 3333XXXX] ----- E1 0/0/0:15 [PSTN simulator] T1 0/1/0:23 ----- [555XXXX NEW YORK]

I configured some dial-peers and translation profiles:

voice translation-rule 1
/\(^00\) \(.*\)/ /\2/

voice translation-profile PSTN
translate called 1

voice port 0/0/0:15
translation-profile incoming PSTN

dial-peer voice 1 pots
incoming called-number .
direct-inward-dial

dial-peer voice 2 pots
destination-pattern 212555....
port 0/1/0:15
forward-digits all

1. In London someone is dialing 0012125555555 that is accepted by PSTN accoding to dial-peer voice 1 pots.
2. The number 0012125555555 is matched to voice translation rule 1 and is changed to 12125555555.
3. In the task, according to dial-peer voice 2 pots the number 2125555555 should come out of voice port 0/1/0:15 and go to router NEW YORK.

The thing is that after translation rule 1 is processed I have 12125555555, but not 2125555555.

The question is what should I do with 1 from the number 12125555555? Of course, I can change dial-peer voice 2 pots and make it like this:

destination-pattern 1212555....
forward-digits all

However, if I add national calls in voice translation rule 1, then the number 12125555555, let's say from Chicago, translated into 2125555555, but it won't match to dial-peer 2 which, after we edited it, sends 1212555....

voice translation-rule 1
/\(^011\) \(.*\)/ /\2/ <= international
/\(^1\) \(.*\)/ /\2/ <= national

1. How this issue can be solved?
2. Imagine, a company buys DID 212555XXXX. In this case telephone provider send 212555XXXX or 555XXXX?

[Nightwolf_82]

Hi guys,

Here are my translation rules and dial peers on PSTN simulator.

voice translation-rule 1 rule 1 /\(^0011\)\(.*\)/ /\2/
rule 2 /\(^0\)\(.*\)/ /\2/
rule 3 /^........$/ /&/
rule 4 /\(^011\)\(.*\)/ /\2/
rule 5 /\(^1\)\(.*\)/ /\2/
rule 6 /^.......$/ /&/
!
voice translation-rule 2
rule 1 /^2\(.*\)/ /\1/ type any subscriber
rule 2 /^8/ /&/ type any national
rule 3 /^61/ /&/ type any international
!
voice translation-rule 3
rule 1 /^212\(.*\)/ /\1/ type any subscriber
rule 2 /^312/ /&/ type any national
rule 3 /^1/ /&/ type any international
!
voice translation-profile NEW-YORK
translate calling 3
!
voice translation-profile PSTN
translate called 1
!
voice translation-profile SYDNEY
translate calling 2
!
voice-port 0/0/0:15
translation-profile incoming PSTN
translation-profile outgoing SYDNEY
!
voice-port 0/1/0:23
translation-profile incoming PSTN
translation-profile outgoing NEW-YORK
!
dial-peer voice 1 pots
incoming called-number .
direct-inward-dial
!
dial-peer voice 2 pots
description **SYDNEY 23333XXXX**
destination-pattern ^6123333....
direct-inward-dial
port 0/0/0:15
forward-digits 9
!
dial-peer voice 3 pots
description **NEW YORK 212555XXXX**
destination-pattern ^1212555....
direct-inward-dial
port 0/1/0:23
forward-digits 10
!
ephone-dn 1
number 000
!
ephone-dn 2
number 911
!
ephone-dn 3 dual-line
number 61211111111 secondary 211111111
!
ephone-dn 5 dual-line
number 12128888888 secondary 2128888888
!
ephone-dn 6 dual-line
number 13129999999 secondary 3129999999

I have one interesting thing with international calls both on CUCM on the one side and CUCME on the other side. The thing is that if international dial-peer on CUCME is configured like this:

dial-peer voice 12 pots description **INTERNATIONAL DIALING**
destination-pattern 9011T
port 0/0/0:23
prefix 011

And Route Pattern for international calls is configured like this:

0.0011!

Then international calls don't go out. However, if I explicitly specify the number of digits that should be forwarded and change prefix 011 for forward-digits 11 on CME and change 0.0011! for 0.0011XXXXXXXXXXX on CUCM then international call flows work perfectly.

Why is it so?