CCIE Voice Lab 1.6 – Call Routing

This lab focuses on developing the Call Routing and dial plan for Ballplayers, LLC. Please note, depending on your PSTN simulation, some task may require digit manipulation not explicitly defined in the tasks. For example, my Adtran does not accept the London international dial plan. Therefore, I will need to strip the 011+44 from the international dialing from New York and Los Angeles. Your solution may vary, depending on what you are using to simulate the PSTN, and what digits that device will accept.

CCIE Voice Lab 1.6 Tasks

1. Ari Gold (1001) and Arliss Michaels (2001) are allowed full dialing privileges, including international. David Wright (1002) and Kobe Bryant (2002) are not allowed international dialing. Finally, Eli Manning can only call on-net calls.

2. New York should be configured with the following call routing options and parameters:

Calls to London: 7+4 digits
Emergency: 911 and 9911
Local: 9+10 digits
Long Distance: 9+1+10 digits
International: 9+011+any number of digits

In addition:

2a. Local calls from New York should user the local VGWY, followed by the Los Angeles VGWY.

2b. Long Distance calls from New York should user the local VGWY, followed by the LA VGWY.

2c. Calls from NY to the LA area code (213) should route via the LA VGWY, followed by the NY VGWY.

2d. International calls to London from NY should use the 7+4 digit pattern via the gatekeeper, followed by the local NY VGWY. Users should not receive secondary dial-tone when calling London extensions.

2e. All other International calls should route via the NY VGWY, followed by the LA VGWY. Eli should be able to call London an on-net call.

3. Los Angeles should be configured with the following call routing options and parameters:

Calls to London: 7+4 digits
Emergency: 911 and 9911
Local: 9+10 digits
Long Distance: 9+1+10 digits
International: 9+011+any number of digits

In addition:

3a. Local calls from LA should user the local VGWY, followed by the NY VGWY.

3b. Long Distance calls from LA should user the local VGWY, followed by the NY VGWY.

3c. Calls from LA to the NY area code (212) should route via the NY VGWY, followed by the LA VGWY.

3d. International calls to London from LA should use the 7+4 digit pattern via the gatekeeper, followed by the local LA VGWY. Users should not receive secondary dial-tone when calling London extensions.

3e. All other International calls should route via the LA VGWY, followed by the NY VGWY. Eli should be able to call London an on-net call.

4. The London dial plan should be configured as follows:

Calls to New York and Los Angeles: 7+4 digits
Emergency: 999 and 9999
Local London: 9+8 digits
Long Distance UK: 9+0+8 digits
International to US: 9+001+any number of digits


5. You may not use any call blocking mechanisms or local routing to accomplish the task in this lab.

6. You may not use the 9.@ NANP wildcard.

7. All external callers should receive the proper E.164 Call ID from the Calling Party.


CCIE Voice Lab 1.6 Solutions
There are three ways to design a dial plan:

• The Traditional Partition/Calling Search Space approach
• The Line/Device CSS approach
• The New Local Route Groups approach

The wording of this lab, in particular task 5 disallowing the use of blocking mechanism and local routing is an attempt to force the user to configure the dial plan using the Traditional Partition/Calling Search Space approach. The dial plan configuration for both New York and Los Angeles is very similar, so the steps below apply to both.

1. First, begin by creating the appropriate partitions for each location.

2. Next, create the Calling Search Spaces (CSS) and assign the Partitions accordingly



3. Route groups are configured next. For each respective route group, only assign the local gateway. For example, for “RG_LA_MGCP_VGWY” only assign the LA VGWY; for RG_NY_H323_VGWY only assign the NY VGWY; and for RG_GKPR only assign gatekeeper trunk configured in the previous lab.

One note about this lab…. During my testing and staging, I ended up removing the Technology Prefix that was required in Lab 1.5. Therefore, you will need to remove this configuration from the trunk as well as the Gatekeeper.

4. The Route Groups are then added to Route Lists. Pay attention to the ordering of the Route Lists in the Route Groups, so that the task requirements are met. For example, below is the ordering for the LA to NY Tail End Hop Off (TEHO) described in the tasks.

5. The Route Patterns are created next, and assigned to the appropriate Route Lists. Here, your configuration may vary slightly from mine, based on your particular PSTN simulator.



For example, in my Adtran only accepts 10-digit dialing (or, at least that is all I could figure it out to accept). Therefore, I apply a “XXXXXXXXXX” mask so that only the trailing ten digits of a call to London is sent. In this example, if a user in NY dials 9-011-44-20-7654-3001, only “20-7654-3001”, which my Adtran then routes to the London PRI. Don’t forget thing such as “Urgent Priority” for 911 and selecting Discard Digits options where appropriate.


6. Lastly, assign the phones and lines to their appropriate partitions in order to honor the Class of Service described in the task.

7. Networking between CUCM and CUCME can be tricky, especially given the tasks as described. For the 7+4-digit dialing, you need to create a translation rule. A rule is also required to add the appropriate prefix to route calls out the PSTN. Finally, for my testing purpose, I create a rule to translate “999” to “911” so that I could test 911 emergency call to my Adtran.

Another helpful hint during testing is to change the preferences of the dial-peer and observe the behavior of the phone class using the “sh voice call summary” command.

!
voice service voip
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
supplementary-service h450.12
h323
!
!
!
voice class codec 1
codec preference 1 g729r8
codec preference 2 g722-64
codec preference 3 g711ulaw
codec preference 4 g711alaw
!
!
translation-rule 1
Rule 1 71 1
Rule 2 72 2
!
!
translation-rule 2
Rule 0 ^999 911
!
!
translation-rule 3
Rule 1 71 2124321
Rule 2 72 2135432
!
!
dial-peer voice 1 pots
description inbound PRI dial-peer
incoming called-number .
direct-inward-dial
port 0/0/0:23
!
dial-peer voice 999 pots
destination-pattern 999
translate-outgoing called 2
port 0/0/0:23
forward-digits 3
!
dial-peer voice 2 pots
description International
destination-pattern 9001T
port 0/0/0:23
!
dial-peer voice 3 pots
description London Local
destination-pattern 9[2-9].......
port 0/0/0:23
!
dial-peer voice 4 pots
description UK Long Distance
destination-pattern 90[2-9].......
port 0/0/0:23
!
dial-peer voice 1000 voip
preference 2
destination-pattern 71...
translate-outgoing called 1
voice-class codec 1
session target ras
dtmf-relay h245-alphanumeric
!
dial-peer voice 2000 voip
preference 2
destination-pattern 72...
translate-outgoing called 1
voice-class codec 1
session target ras
dtmf-relay h245-alphanumeric
!
dial-peer voice 1001 pots
preference 1
destination-pattern 71...
translate-outgoing called 3
port 0/0/0:23
!
dial-peer voice 2001 pots
preference 1
destination-pattern 72...
translate-outgoing called 3
port 0/0/0:23
!