Discovery 8: Create a Basic Dial Plan

Introduction
In this lab, you will create a basic dial plan and utilize Cisco DNA (Dialed Number Analyzer) to explore call flow.

This lab will take approximately 50 minutes to complete.

Topology

Credentials
Usernames and Passwords

Device IP address Username Password

Cisco UCM 10.1.5.5 Administrator C0ll@B

PC-1 10.1.5.200 Student C0ll@B

PC-2 10.1.5.201 Student C0ll@B

PC-3 10.1.99.101 Student C0ll@B

Task 1: Use DNA to Analyze an Internal Call Flow

Activity
The Cisco DNA (Dialed Number Analyzer) is a powerful tool to help troubleshoot and identify call routing issues. To
use the DNA, services need to be activated.

Step 1
From PC-1, open Chrome and navigate to https://10.1.5.5/ccmservice and log in with username Administrator
and password C0ll@B accepting any security warnings.

Step 2
Select Tools > Service Activation.
Step 3
Select the Publisher server from the dropdown menu and click Go.

Step 4
Check the Cisco Dialed Number Analyzer service box.

A popup window will notify you that to activate the Cisco Dialed Number Analyzer service, the Cisco Dialed
Number Analyzer Server service is also required.

Click OK for both services to be activated and Save.

Step 5
Once the services have been activated, open a new tab in your browser and navigate to https://10.1.5.5/dna.
You can also navigate to the Cisco Dialed Number Analyzer from Cisco Unified Serviceability Tools menu.

Step 6
Select Analysis > Analyzer.

Step 7
Enter 11001 in the Calling Party field.
Step 8
Enter 11002 in the Dialed Digits.

Step 9
Leave all the other values as default and click Do Analysis.
The popup window will display the Results Summary.

Step 10
Notice that the Match Result is “RouteThisPattern” which indicates there are no failures and this call would work.
Step 11
Expand Call Flow > Directory Number: DN = 11002 > Device: Type = Cisco IP Communicator.

Step 12
Take some time to identify some of the information that is available, including the Device Status, Device Name,
and Alerting Name.

The Device Status is “UnKnown” because the PC hosting the CIPC is not booted or configured at this
stage. It is not needed for this lab, so this status message can be ignored for now.

Step 13
Close the popup window.

Step 14
Change the Dialed Digits from 11002 to 9911 and click Do Analysis.
Step 15
Notice that the Match Result is now indicating “BlockThisPattern”. The Route Block Cause is “Unallocated
Number”, which indicates that the Cisco UCM does not have any knowledge of this number or how to route the
call.

Task 2: Create a Route Pattern

Activity
Step 1
Navigate to https://10.1.5.5/ccmadmin.

Step 2
Select Call Routing > Route/Hunt > Route Pattern.
Step 3
Click Find and notice that there are 5 Route Patterns that have already been configured, however the Route
Pattern 9.911 is missing.

Click Add New.

Step 4
Enter 9.911 in the Route Pattern field.
The reason for adding “9.” In front of 911 is to allow for a corporate policy of dialing “9” to get an outside line before
dialing the actual number as required. The period is used to separate the outside dial tone number from the
number to be sent to the PSTN.

Step 5
In the description field, enter “911 Emergency HQ Route Pattern”.

Step 6
Select the HQ SIP ROUTE LIST from the Gateway/Route List dropdown menu. You will analyze this Route List
in more detail later in this lab.

Step 7
Confirm that Route this pattern is selected.
Step 8
Confirm that the Call Classification is OffNet.

Step 9
Confirm that Provide Outside Dial Tone is checked.

Step 10
Check the Urgent Priority checkbox.

When Urgent Priority is enabled on Directory Number Configuration Page, the call is routed at once to
the fully qualified DN without any necessity to wait for inter-digit-timeout. If the Urgent Priority checkbox
is disabled and you have overlap patterns configured, then CUCM waits for the user to dial further digits.
Step 11
In the Calling Party Transformations section, check the Use Calling Party’s External Phone Number Mask
checkbox.

Step 12
In the Called Party Transformations section, select PreDot from the Discard Digits dropdown menu.

The PreDot DDI (Discard Digit Instruction) configures the Cisco UCM to not forward any digits before
the “dot” (period) in the pattern. Since the PSTN is not expecting the “9.” to get an outside line, you don’t
want to forward it to the PSTN.

Step 13
Leave all other fields as default, and click Save.

Step 14
Click OK on the following two popup notifications.
Task 3: Configure the External Phone Number Mask
Activity
Step 1
Select Device > Phone.

Step 2
Click Find, then click HQ-CIPC-1.

Step 3
Click Line [1] – 11001.

Step 4
Scroll down to the “Line 1 on Device HQ-CIPC-1” section and enter the following information:

Display (Caller ID): John Doe

Line Text Label: John – 11001
External Phone Number Mask: 408555XXXX
Display (Caller ID) is the caller ID that will be shown on the receiver’s screen instead of just showing the number
that is calling, it can show the name of the person as entered in this field.

Line Text Label is a friendly name on screen of the owner’s phone. In this case, the phone belonging to John Doe
will now show “John -11001” on screen next to line 1, instead of the default which in this case would be 11001.

External Phone Number Mask is to modify the calling number before sending the call to the PSTN. Without this
field, the calling number would be 11001 which is not a valid PSTN number. With this external phone number mask,
the four “X’s” at the end of the mask will keep the last 4 digits of the calling number, in this case 1001. The number
408555 will be added to the front of the “X’s”, so the result will be 4085551001 for John Doe.

Step 5
Click Save.

Step 6
Repeat the previous steps on the HQ-CIPC-2 phone with the following information:

Display (Caller ID): Jane White

Line Text Label: Jane – 11002
External Phone Number Mask: 408555XXXX

Task 4: Use DNA to Analyze an External Call Flow

Activity
Step 1
Navigate to https://10.1.5.5/dna or from Cisco Unified Communications Manager Serviceability and choose
Tools > Dial Number Analyzer

Step 2
From the Cisco DNA, select Analysis > Phones. Click Find button, then select HQ-CIPC-1 phone from the
list.
Step 3
In Association Information select 1Line [1] - 1001 (no partition). Enter 9911 in Dialed Digits option, then
click Do Analysis.

Step 4
Notice that the Match Result now shows “RouteThisPattern” as you have created the Route Pattern that matches
this dial string.
Step 5
Notice the Called Party Number shows as “911”, indicating 911 is the number that would be sent after the PreDot
DDI has taken place.

Step 6
Expand Call Flow > Route Pattern > Called Party Transformations.
Step 7
Notice the Discard Digits Instruction (DDI) is "PreDot". PreDot will drop the first 9 in the route pattern and the
final called number will be 911 as seen in the Called Number field.
Step 8
Notice the Route List Name used to route this call is “HQ SIP ROUTE LIST”.

Expand the ROUTE LIST menu.

Step 9
Notice that the Route Group used is the Standard Local Route Group, which has been configured as “HQ SIP to
PSTN Route Group”.

Expand the Route Group menu.

Step 10
Notice that the Device Type is "SIPTrunk".

Expand the Device Type menu to identify the device name of 10.1.99.5.

Task 5: Explore the Dial Plan Elements

Activity
Step 1
From the Cisco Unified CM Administration page, select Call Routing > Route/Hunt > Route List and click Find.
Step 2
Notice the route list named “HQ SIP ROUTE LIST” that you selected when creating the Route Pattern for 9.911
calls.

Step 3
Click the route list named HQ SIP ROUTE LIST.

Step 4
Notice the following information that is displayed:

the route list description

the Cisco UCM Group that is responsible for the route list (HQ-CUCM-GROUP-1)
indication the route list is enabled
indication the route list is configured to run on all active Unified CM nodes in the cluster

Also notice in the Route List Member Information section, that the “Standard Local Route Group (Local Route
Group) is listed in the Selected Groups section. This information indicates that rather than selecting a specific
Route Group to route this call, the Route Group that has been defined in the device pool will be used.

Step 5
Select System > Device Pool.
Step 6
Click Find, then select the HQ device pool.

Step 7
Scroll down to the Local Route Group Settings section and notice the “HQ SIP to PSTN Route Group” has been
selected from the dropdown menu.

Step 8
Select Call Routing > Route/Hunt > Route Group.
Step 9
Click Find, then click the route group named HQ SIP to PSTN Route Group.

Step 10
Notice that the Distribution Algorithm has been set to “Top Down”. (A second option is “Circular”)

In a Top Down algorithm, the first device listed will always be used for each call unless it is unavailable, at
which point the second device listed will be used and so on. This option is the preferred method when wishing
to forward calls via the WAN and using a PSTN connection as a backup.
In a Circular algorithm, each device will be used on a rotation bases.

Step 11
 Notice in the Route Group Member Information section that there is a list of all available devices, which currently
contains one device, the SIP Trunk.

Step 12
Notice that the SIP Trunk is also listed in the Selected Devices list under the Current Route Group Members
section.

The order of the devices is unimportant in a Circular algorithm, but in a Top Down configuration, the order is of
paramount importance. You will notice that there are arrows on the right of the selected devices list to allow the
order to be changed.

Step 13
Select Device > Trunk.
Step 14
Click Find, and then notice the SIP Trunk that was referred to in the DNA Analysis. Click the name of the SIP
Trunk (10.1.99.5).

Step 15
Notice the following settings for the trunk:

Device Name: 10.1.99.5 (This entry does not need to be an IP Address as used in the LAB, but often
administrators find it easier when troubleshooting if the name of the trunk is the IP address of the destination.)
Description: HQ SIP Trunk Direct to PSTN
Device Pool: HQ
Call Classification: OffNet
Location: HQ

Step 16
Scroll down to the Inbound Calls section. Notice that the Significant Digits is set to "All".

This setting allows you to define how many of the digits that this trunk presents to Cisco Unified CM when receiving
a call. This is the number of digits that are needed to route the call internally. The PSTN will often present more
digits than what the organization is using internally.

Step 17
Scroll down to the SIP Information section and notice the Status, Status Reason, and Duration values listed here.
This section is where the destination for the SIP trunk is defined, in this case, IP Address 10.1.99.5. Also, the
status values you see are only visible if “SIP OPTIONS Ping” under the SIP Profile have been configured, as you
will see further in this lab.

Step 18
Notice that the SIP Trunk Security Profile has been set to a custom profile named “HQ SIP TRUNK FOR PSTN”.

The Security Profile defines the protocols (TCP / UDP), the port numbers, and the security mode used by the trunk.

Step 19
Notice that the SIP Profile is set to a custom profile named “HQ SIP Profile”.

SIP Profiles contain information including Timer values, QoS settings for packet marking, and SIP OPTIONS Ping
used to monitor the connectivity to the destination. Take some time to view some of the other settings on the SIP
profile by selecting Device > Device Settings > SIP Profile, and selecting the HQ SIP Profile from the list.

Step 20
Select Call Routing > Translation Pattern.
Step 21
Click Find, and click the 408555XXXX translation pattern.

The translation pattern in this lab is used to allow inbound calls from the PSTN. When a caller from outside dials
408-555-XXXX (The Direct Inward Dial number range), the PSTN will present the full 10 digits to the SIP Trunk. As
the internal number in this lab is 1XXXX, it does not match the DID range as seen from the outside and translation
is required.

If you use John’s extension number as an example, from inside the company, a user would dial 11001, while a user
on the PSTN would dial 408-555-1001. Only the last 4 digits are the same. The 408-555 needs to be removed and
a 1 needs to be prepended to the number to reach John’s internal directory number.

A Translation pattern is one way to allow the translation to take place. For example, a translation pattern of
408-555-XXXX, with a transformation mask of 1XXXX would solve the problem. The “X’s” are maintained while the
“408-555” is removed and a “1” is added to the front of the “X’s”.

Step 22
Notice that the Translation pattern is 408555XXXX.
Step 23
Scroll down to the Called Party Transformations section and notice that the Called Party Transform Mask has
been set at 1XXXX.