Discovery 11: Implement Endpoint Addressing and Call Routing
Discovery 11: Implement Endpoint Addressing and Call Routing
Introduction
In Cisco Unified Communications Manager, you can configure phones with two types of endpoint addresses:
directory numbers and directory URIs.
The configuration of these two types of addresses is similar but there are some differences. Each type has some
unique characteristics of which you should be aware.
There is a Cisco Unified Communications Manager (HQ-UCM) in this topology with three preconfigured phones:
CIPC-1 running on PC-1, CIPC-2 running on PC-2, and CIPC-3 running on PC-3.
You will configure directory numbers on these phones and identify how a directory number differs from a line
appearance. Then you will apply directory number-based URIs and user-based directory URIs to the phones.
Finally, you will configure overlapping directory numbers and then analyze the related problems and the role of
urgent priority.
Topology
Job Aid
Device Information
HQ-CUCM Cisco Unified Communications Manager serving the US and the UK sites 10.1.5.5 Administrator, C0ll@B
HQ-WIN-SERVER-1 Microsoft Windows Server providing NTP and DNS services 10.1.5.100
Task 1: Register Endpoints
Activity
Step 1
On PC-1, open Google Chrome and navigate to Cisco Unified Communications Manager Administration
(https://10.1.5.5/ccmadmin). Log in using Administrator for the username and C0ll@B for the password.
Step 2
Select Device > Phone, click Find and observe if Cisco IP Communicator phones are displayed. If phones are
not displayed wait a while for the automation system to finish configuring Cisco Unified Communicacitons
Manager and then click Find again. Continue only when phones are displayed.
Step 3
On PC-1, start Cisco IP Communicator and configure it with the following settings:
Step 4
On PC-2, start Cisco IP Communicator and configure it with the following settings:
It is important that you understand the difference between a directory number which is not associated with a
device, and a directory number which is associated with a device.
Activity
Directory Numbers, Shared Lines, and Line Appearances
A single directory number can be associated with zero or more devices. If a directory number is used with multiple
devices, it is called a shared line.
The directory number configuration consists of the following two types of parameters:
Directory number parameters that are shared with all associated devices. Examples of these parameters are
Calling Search Space and Call Forward settings.
Directory number parameters that are associated with a specific device. Examples of these parameters are the
Line Text Label and the External Phone Number Mask.
You can view and edit the directory number configuration in different ways:
To view and edit only shared directory number parameters, open the Call Routing > Directory Number menu.
Any changes that are made to these parameters apply to all associated devices.
To view and edit both the shared and the device-associated parameters, choose the line configuration link at the
phone configuration page or click the Edit Line Appearance button from the Directory Number Configuration
page. Depending on the parameter that is being changed, the parameter might apply to all associated devices
or is specific to only one associated device.
Step 1
On PC-1, open Chrome or Firefox and navigate to https://10.1.5.5/ccmadmin. Log in with username
Administrator and password C0ll@B.
Step 2
Select Device > Phone. Then click find to see a list of all phones.
Step 3
Click on the CIPC-2 phone; then Click the link Line [2] – Add a new DN.
Step 4
Before entering any data, scroll down the directory configuration page and note that no device-specific
parameters are set.
You can find the device-specific configuration parameters under the heading Line 2 on Device CIPC-2.
Step 5
Scroll back to the top of the page and enter 11009 for the Directory Number. Then click in another field.
After you click in another field, you see a message on top of the page that indicates that the page has
refreshed and that you have to click the Save button to save the configuration.
Step 6
Click Save.
Step 7
Note that after you save the changes, the configuration page looks different. It shows CIPC-2 as an associated
device. You are at the directory number line appearance of CIPC-2.
Step 8
Set the Forward Busy External destination to 11001.
Step 9
Set the Display (Caller ID) parameter to CIPC-2, Line 2.
Step 10
Save the configuration.
Directory number 11009 is now configured to forward external calls to directory number 11001 when the
called line (11009) is busy. This directory number setting applies to all associated devices (if more than
one). In addition, the line appearance of directory number 11009 on CIPC-2 is configured with a display
caller ID of CIPC-2, Line 2.
Step 11
Go to the phone configuration page of CIPC-3.
Step 12
Click the link Line [2] – Add a new DN.
Step 13
Enter 11009 for the Directory Number and then click in another field.
After you leave the Directory Number field, one currently associated device (CIPC-2) is shown.
Step 14
Click Save.
After you save the changes, you can see two associated devices (CIPC-2 and CIPC-3).
If you want to quickly change from the line appearance of one device to the line appearance of another
device, you can choose the desired device in the list of associated devices and then click Edit Line
Appearance.
Step 15
Verify that the Forward Busy External destination for the shared directory number is already set to 11001.
The Call Forward configuration is part of the shared directory number and therefore applies to all
associated devices.
Step 16
Verify that the Display (Caller ID) parameter at the device-specific line area is not configured. Configure this
parameter for CIPC-3 by entering CIPC-3, Line 2.
Step 17
Save the configuration. On PC-3, have a look at CIPC-3. You see that the phone restarts. Wait until it shows both
directory numbers.
Step 18
On PC-1, in CIPC-1, place a call to 11009. Check that the call is delivered to both phones: CIPC-2 (running on
PC-2) and CIPC-3 (running on PC-3). Accept the call on CIPC-3 and keep the call open.
Step 19
On PC-1, in CIPC-1, check the shown caller ID. You see CIPC-3, Line 2.
Step 20
In CIPC-1, drop the call and then call 11009 again. Accept the call on CIPC-2 and keep the call open. In CIPC-1,
check the shown caller ID. You should see CIPC-2, Line 2.
Step 21
In CIPC-1, drop the call.
Summary
You placed two calls to the same directory number, which is configured as a shared line (on CIPC-2 and CIPC-3).
When you accept the call on different phones, you see different display caller IDs. These different numbers are
displayed because you are connected to the same directory number, but on different devices. The display caller ID
is a device-specific directory number setting and you configured it differently on the two phones.
There are two ways to assign directory URIs to a phone line: you can configure one or more directory URIs at a
directory number, or you can assign a directory URI to a directory number via an end user.
Activity
Assign a Directory URI at the Directory Number Configuration Page
You will assign a directory URI to CIPC-3 by adding the URI to directory number 11003.
Step 1
On PC-1, in Cisco Unified Communications Manager Administration, select Call Routing > Directory Numbers
and click Find to see a list of all directory number.
Step 2
Click directory number 11003 and configure dgrey@cll-collab.internal as the primary directory URI. Then click
Save.
Assign a Directory URI via an End User
You can assign a directory URI via an end user if the phone is associated with the user and the directory number is
configured as the primary extension of the user. The directory URI that you configure at the end user is then
applied to the specified primary extension.
You will apply a directory URI to directory number 11001 at CIPC-1 via the end-user configuration page.
Step 3
Choose User Management > End Users and open the configuration page of user jdoe.
This user is imported from Microsoft Active Directory via LDAP. The directory URI is a field that is
synchronized with the LDAP directory and you cannot modify it in Cisco Unified Communications
Manager.
When you add a local user to Cisco Unified Communications Manager (a user that is not imported from
LDAP), you can set the directory URI locally in Cisco Unified Communications Manager.
Step 4
Verify that the directory URI is already set to jdoe@cll-collab.internal.
You can see that the directory URI is a field that cannot be edited, which indicates that it is synchronized
via LDAP.
Step 5
To associate the end user with CIPC-1, you have to perform the following procedure:
Step 7
Save the changes at the end-user configuration page.
Step 8
Go to directory number 11001 (select Call Routing > Directory Numbers) and verify that the directory URI was
applied to the directory number:
The directory URI is not a line appearance parameter. Therefore, you can check either the directory
number or the line appearance.
You can see that the user-assigned directory URI cannot be deleted on the directory number
configuration page. If you add more directory URIs to the directory number, then the user-assigned
directory URI is always the primary directory URI. The primary directory URI is the one that is sent as
the calling-directory URI (in addition to the calling-party number) on calls that are placed from the phone
line that has the directory number assigned.
Note that the user-assigned directory has the partition Directory URI applied and that you cannot change
the partition of a user-assigned directory URI.
To allow calls to end-user-based directory URIs, the CSS of the calling device must include the Directory URI
partition.
You do not configure partitions and CSSs in this exercise. Therefore, you cannot place calls to the directory URI of
CIPC-1. Other than the directory URI of CIPC-1, the directory URI of CIPC-3 is not in a partition, so you can reach
this URI without configuring a CSS.
Now you will verify URI call routing by placing a call to the directory URI of CIPC-3.
Speed dials allow users to place calls to popular destinations with a single keystroke. Speed dials support DNs and
URIs.
Dialing a URI from the keypad of a phone is not supported on all phone models.
Here, you are using Cisco IP Communicator. Cisco IP Communicator does not support dialing a URI from
the keypad, but it does support speed dials in URI format.
Step 9
Go to the phone configuration page of CIPC-2 and configure a speed dial for destination dgrey@cll-
collab.internal with a label dgrey.
Step 10
On PC-2, in CIPC-2, press the speed dial labeled dgrey to place a call to URI dgrey@cll-collab.internal. On
PC-3, in CIPC-3, verify that you see the incoming call.
Task 4: Configure Overlapping Directory Numbers and Urgent Priority
Cisco Unified Communications Manager interprets dialed digits one-by-one as the digits are entered at the calling
phone. If overlapping, longer patterns exist in the call-routing table, the interdigit timeout must expire before a call is
sent to the shorter matching pattern.
Typically, you do not want end users have to wait for a timeout when they enter the number that they want to call.
They should only have to wait if it is absolutely necessary; for example, when dialing international numbers that are
of variable length.
You must be aware of how Cisco Unified Communications Manager performs digit analysis. Then you can design
your dial plan so that users do not have to wait for interdigit timeouts if timeouts can be avoided.
Activity
Configure a Longer, Overlapping Pattern
You will change the directory number of the line on CIPC-3 from 11009 to 110019. The first four digits of this new
directory number overlap the existing directory number of CIPC-1 (11001) and the new number has the extra fifth
digit.
When you dial 11001, Cisco Unified Communications Manager does not know immediately if you want to reach
11001 or if you will dial an extra 9 to call 110019. Cisco Unified Communications Manager has to wait for a fifth digit
until the interdigit timeout expires to determine that you finished dialing.
Step 1
On PC-1, in Cisco Unified Communications Manager Administration, go to the configuration page of CIPC-3 and
change the directory number of Line 2 from 11009 to 110019.
Verify Digit-by-Digit Analysis
Now you will place a call from CIPC-2 to 11001 using the digit-by-digit addressing method.
Step 2
On PC-2, in CIPC-2, press the New Call softkey and then dial 11001. Check how long it takes until the call is
routed to CIPC-1. You can see if Cisco Unified Communications Manager is still waiting for digits by looking at
the display of the calling phone:
CIPC-1 rings 10 seconds after you enter the last digit. A longer, overlapping pattern exists, and due to
the digit-by-digit addressing method, Cisco Unified Communications Manager has to wait to see if you
dial an extra digit.
By default, the interdigit timeout is 15 seconds, but in this lab it is set to 10 seconds.
Step 3
Drop the call setup attempt by pressing the EndCall softkey.
Support for sending the called number en bloc differs per endpoint and may depend on the Cisco Unified
Communications Manager version, the phone model, the phone firmware, or in softphones, the softphone software
version. In addition, different endpoints may use either the en bloc or digit-by-digit addressing method, depending
on how you dial the number on the endpoint. Here are some options for dialing a number that may result in
different addressing methods:
You go off-hook first (or press the New Call softkey) and then enter the digits on the keypad.
You first enter the digits on the keypad and then go off-hook (or press the Dial softkey).
You choose a call list entry instead of entering the digits.
You use a speed dial instead of entering the digits.
In this exercise, Cisco IP Communicator does not use the en bloc addressing method, regardless of how you place
the call. You can, however, generate an en bloc call to 11001 by calling a translation pattern that changes the
number that you dialed (for example, 11000) to 11001. Internally, in Cisco Unified Communications Manager, a
translation pattern generates a new call setup request after it modifies the called number. When the translation
pattern is configured with the Do Not Wait For Interdigit Timeout On Subsequent Hops option, the translation
pattern generates the new call setup request using the en bloc addressing method.
Now you will configure such a translation pattern so that you can generate an en bloc call to 11001. Then you will
place the test call and analyze the result.
Step 4
On PC-1, in Cisco Unified Communications Manager Administration, configure a new translation pattern (select
Call Routing > Translation patterns) with the following settings:
Step 5
On PC-2, in CIPC-2, generate an en bloc test call to CIPC-1 (11001) by pressing the New Call softkey and then
dialing 11000. Check how long it takes until the call is routed to CIPC-1.
The call is routed to CIPC-1 immediately after you dial the last digit. The call setup request for 11001 is
en bloc. Therefore, Cisco Unified Communications Manager knows that the dialed string (11001) is
complete and does not have to wait for additional digits, even though an overlapping longer pattern
exists.
Step 6
Drop the call setup attempt by pressing the EndCall softkey.
Step 7
Go to the directory number configuration page of directory number 11001 and configure the directory number to
be urgent.
Step 8
On PC-2, in CIPC-2, press the New Call softkey and then dial 11001. Check how long it takes until the call is
routed to CIPC-1.
This time, CIPC-1 rings immediately after you enter the fourth digit, even though your input is interpreted
digit-by-digit and a longer overlapping pattern exists.
Urgent patterns or numbers instruct Cisco Unified Communications Manager to stop waiting for
additional digits if a shorter match is found in the urgent pattern.
Step 9
Drop the call setup attempt by pressing the EndCall softkey.