Best Sip-cube Lab

Cisco Unified CM 10.0 SIP Trunking, Session Management, Intercluster Lookup Service (ILS) and URI Dialing Cisco Live San Francisco 2014

Paul Giralt ([email protected]) Rafael Muller ([email protected])

POD10

LTRUCC-2150

2014 Cisco Systems, Inc. All rights reserved Document for POD10. Page 2 of 140

Table of Contents

Introduction to Lab ............................................................................ 7

Prerequisites .................................................................................... 9

Lab Diagram ................................................................................... 10

Lab Overview ................................................................................. 11

Before You Begin ............................................................................ 12

ILS/GDPR Overview ......................................................................... 13 Hub or Spoke ....................................................................................................................... 14 Advertisements .................................................................................................................... 15

Configure ILS on Unif ied CM SME Edit ion .......................................... 17 Task 1: Configure Cluster ID ........................................................................................... 17 Task 2: Configure ILS on Unified CM SME ...................................................................... 17

Configure ILS on Unif ied Communications Manager Leaf 1 .................. 19 Task 3: Configure Cluster ID ........................................................................................... 19 Task 4: Configure ILS on Unified Communications Manager Leaf 1 ................................ 19

Configure ILS on Unif ied Communications Manager Leaf 2 .................. 21 Task 5: Configure Cluster ID ........................................................................................... 21 Task 6: Configure ILS on Unified Communications Manager Leaf 2 ................................ 21 Task 7: View ILS Mesh topology ..................................................................................... 22

Dial Plan for Unif ied CM Leaf Cluster 1 ............................................. 23 Task 8: Configure partitions on Leaf Cluster 1 ................................................................ 25 Task 9: Configure CoS Calling Search Space for Leaf Cluster 1 ..................................... 26 Task 10: Configure CoR CiscoLive_National CSS ........................................................... 27 Task 11: Configure CoR CiscoLive_International CSS ..................................................... 27 Task 12: Configure CSS_Inbound_ILS CSS .................................................................... 28

Configure Translation Patterns for Leaf Cluster 1 ............................... 29 Task 13: Configure National Translation Pattern .............................................................. 29 Task 14: Configure International Translation Pattern with # ............................................. 30 Task 15: Configure International Translation Pattern without # ........................................ 31

Configure SIP trunk and Route List to SME in Leaf Cluster 1 ............... 32 Task 16: Configure SIP trunk to Unified CM SME ............................................................ 32 Task 17: Configure Route Group ..................................................................................... 33 Task 18: Configure Route List ......................................................................................... 34

Dial Plan for Unif ied CM Leaf Cluster 2 ............................................. 36 Task 19: Configure partitions on Leaf Cluster 2 ............................................................... 37 Task 20: Configure CoS Calling Search Space for Leaf Cluster 2 ................................... 38


Task 21: Configure CoR CiscoLive_National CSS ........................................................... 39 Task 22: Configure CoR CiscoLive_International CSS ..................................................... 39 Task 23: Configure CSS_Inbound_ILS CSS .................................................................... 40

Configure Translation Patterns for Leaf Cluster 2 ............................... 41 Task 24: Configure National Translation Pattern .............................................................. 41 Task 25: Configure International Translation Pattern with # ............................................. 42 Task 26: Configure International Translation Pattern without # ........................................ 43

Configure SIP trunk and Route List to SME in Leaf Cluster 2 ............... 44 Task 27: Configure SIP trunk to Unified CM SME ............................................................ 44 Task 28: Configure Route Group ..................................................................................... 45 Task 29: Configure Route List ......................................................................................... 46

ILS/GDPR with Central ized Unif ied CM SME ....................................... 47

Configure SIP Route String for Unif ied CM Leaf 1 .............................. 49 Task 30: Configure SIP route string ................................................................................. 49

Configure SIP Route String for Unif ied CM Leaf 2 .............................. 50 Task 31: Configure SIP route string ................................................................................. 50

Configure Unif ied CM SME Dial Plan ................................................. 51 Task 32: Configure Partitions in Unified CM SME ............................................................ 52 Task 33: Configure Calling Search Space in Unified CM SME ......................................... 53

Configure SIP Trunks on Unif ied CM SME .......................................... 54 Task 34: Configure SIP Trunk to Unified CM Leaf 1 ......................................................... 54 Task 35: Configure SIP Trunk to Unified CM Leaf 2 ......................................................... 54 Task 36: Configure SIP Trunk to Unified Border Element ................................................. 55

Configure Route Groups and Route Lists in Unif ied CM SME ............... 57 Task 37: Configure Route Group for Unified CM Leaf 1 ................................................... 57 Task 38: Configure Route Group for Unified CM Leaf 2 ................................................... 58 Task 39: Configure Route Group for Unified Border Element ........................................... 58 Task 40: Configure Route List for Unified CM Leaf 1 ....................................................... 59 Task 41: Configure Route List for Unified CM Leaf 2 ....................................................... 59 Task 42: Configure Route List for Unified Border Element ............................................... 60

Configure SIP Route Pattern in Unif ied CM SME ................................. 61 Task 43: Configure SIP Route Pattern for Unified CM Leaf 1 ........................................... 61 Task 44: Configure SIP Route Pattern for Unified CM Leaf 2 ........................................... 62

Configure Phone Line in Unif ied CM Leaf 1 ....................................... 63 Task 45: Configure Global Dial Plan Replication for Phone #1 ......................................... 63 Task 46: Configure advertisement for Enterprise Alternate Number ................................ 64 Task 47: Configure advertisement for +E.164 Alternate Number ..................................... 64


Configure Phone Line in Unif ied CM Leaf 2 ....................................... 65 Task 48: Configure Global Dial Plan Replication for Phone #1 ......................................... 65 Task 49: Configure advertisement for Alternate Number ................................................. 66 Task 50: Configure advertisement for +E.164 Number .................................................... 66

Validate learned patterns via ILS/GDPR ............................................. 67 Task 51: Validate learned patterns on Leaf Cluster 2 ...................................................... 67 Task 52: Place calls with Cisco Jabber Client .................................................................. 68

Configure PSTN Route Patterns Leaf Cluster 1 .................................. 70 Task 53: Add US NANP static route pattern on Leaf Cluster 1 ........................................ 70 Task 54: Add International static route pattern on Leaf Cluster 1 .................................... 71

Configure PSTN Route Patterns Leaf Cluster 2 .................................. 72 Task 55: Add US NANP static route pattern on Leaf Cluster 2 ........................................ 72 Task 56: Add International static route pattern on Leaf Cluster 2 .................................... 73

Configure PSTN Route Patterns Unif ied CM SME ................................ 74 Task 57: Add US NANP static route pattern on Unified CM SME ..................................... 74 Task 58: Add International static route pattern on Unified CM SME ................................. 75

CUBE General Configuration ............................................................ 76 Task 59: CUBE General Configuration ............................................................................. 76 Task 60: Configure media inactivity ................................................................................. 78

CUBE Box to Box Redundancy .......................................................... 79 Task 61: Configure redundancy between CUBEs ............................................................ 79 Task 62: Configure IPC between CUBEs ......................................................................... 79 Task 63: Configure track interface objects ...................................................................... 80 Task 64: Configure HSRP on Inside Interfaces ................................................................ 81 Task 65: HSRP Tracking and Priorities ............................................................................. 81 Task 66: Configure HSRP delay timers ............................................................................ 82 Task 67: Configure HSRP group name ............................................................................ 82 Task 68: Verify configuration of HSRP on Internal Interfaces ........................................... 83 Task 69: Configure Service Provider HSRP Interface ...................................................... 83 Task 70: Configure Redundancy Inter-device ................................................................. 84

CUBE Server Groups ....................................................................... 86 Task 71: Define internal server groups ............................................................................ 86 Task 72: Define external ( service provider ) server groups ............................................. 86

E164 Dial Maps ............................................................................... 87 Task 73: Configure internal E164 Dial Map ...................................................................... 87 Task 74: Configure service provider E164 Dial Map ........................................................ 87

CUBE Dial Peers ............................................................................. 88 Task 75: Configure Dial Peers between CUBE and Unified CM SME ............................... 88


Task 76: Configure redundancy bind ............................................................................... 90 Task 77: Configure Dial Peer between CUBE and the Service Provider ........................... 91 Task 78: Enable CCSIP debugs on Active Cube .............................................................. 92

Configure CUBE Dial Plan Normalization ............................................ 94 Task 79: Convert from +E.164 to NANP for Called Numbers to the PSTN ....................... 94 Task 80: Convert from +E.164 to NANP for Calling Numbers to the PSTN ...................... 94 Task 81: Convert Called Number from NANP to +E.164 for Inbound Calls from PSTN .... 95 Task 82: Convert calling number from NANP to +E.164 for inbound calls from PSTN ..... 95 Task 83: Configure Translation profile for inbound dial-peers ......................................... 96 Task 84: Add translation profiles to dial-peers ................................................................ 96 Task 85: Place PSTN call from CUCM ............................................................................. 97

CUBE DO to EO configuration ........................................................... 98 Task 86: Enable DO-EO on Outbound Dial Peers ............................................................ 99 Task 87: Verify EO-DO Configuration .............................................................................. 99

Enhanced Event Tracing ................................................................ 101 Task 88: Enable monitor event trace ............................................................................. 101 Task 89: Disable event-trace automatic file dump ......................................................... 101 Task 90: Configure event-trace memory footprint ......................................................... 101 Task 91: Place calls for event-monitor .......................................................................... 102 Task 92: Configure dump file destination path ............................................................... 103 Task 93: Event-trace file dump ..................................................................................... 103

CUBE / SME OPTIONS Ping Configuration ........................................ 105 Task 94: Configure OPTIONS ping on CUBE dial-peers ................................................ 106 Task 95: Configure OPTIONS pings on Unified CM SME ............................................... 107 Task 96: Add OPTIONS Ping Profile to the SIP Trunk .................................................... 107

Enabling URI Dial ing ...................................................................... 108 Task 97: Create a new End User and associate Primary Extension ................................ 109 Task 98: Verify Directory URI Mapping .......................................................................... 109 Task 99: Check URI replication ...................................................................................... 110

SME Normalization Script (Modify Diversion Header) ........................ 111 Task 100: Add a new normalization script to SME ......................................................... 111 Task 101: Apply Normalization Script to CUBE SIP Trunk .............................................. 112

Translate Inbound DID to Lab Number ............................................. 114 Task 102: Create a new Partition in SME for inbound translations ................................. 114 Task 103: Create a new CSS to restrict access to Inbound Translations ....................... 114 Task 104: Add Inbound Translations partition to the Inbound PSTN CSS ...................... 115 Task 105: Create Translation Pattern to Translate PSTN number .................................. 116 Task 106: Add number to e164 Pattern Map ................................................................. 116


Use Session Trace feature to view SIP call f low ............................... 120

Debug SIP call on CUBE ................................................................ 124 Task 107: Initiate debugs on Unified Border Element .................................................... 124 Task 108: Copy log file from CUBE to your Cisco Live Workstation ............................... 125 Task 109: Read the log file in Translator X ..................................................................... 126

Detailed tracing on Unif ied Communications Manager ....................... 129 Task 110: Navigate to Cisco Unified Serviceablity ......................................................... 129 Task 111: Enable detailed tracing for Call Manager Service .......................................... 130

Unified Communications Manager trace collection ............................ 132 Task 112: Trace collection with RTMT ........................................................................... 132 Task 113: Read UCM trace files with TranslatorX .......................................................... 134 Task 114: Tracing a call end to end ............................................................................... 137

Notes ........................................................................................... 138

Notes ........................................................................................... 139

Notes ........................................................................................... 140


Introduction to Lab

Enterprises and service providers are increasingly moving from traditional TDM-based telephony to IP-based networks. While enterprises have been deploying IP telephony within their networks for many years now, it is only recently that service providers have started to provide IP-based trunking services. These trunking services are based on the Session Initiation Protocol (SIP). SIP trunking services typically terminate on a session border controller (SBC) that serves as a demarcation point between the enterprise and the service provider much in the same way that a firewall separates two data networks. The Cisco Unified Border Element (CUBE) is Ciscos SBC product.

SIP is also becoming increasingly important within the enterprise. Most enterprise telephony vendors leverage SIP to communicate with each other and there are numerous applications that use SIP as their interface to other devices, for example, Unified Messaging, Voicemail, and Audio or Video Conferencing applications. One challenge that SIP brings to the table is that, although it is referred to as a standard, it really is just a large collection of RFCs that vendors can interpret in different ways or can implement only the pieces they require. As a result, there is an increasing need to be able to interconnect these disparate systems as well as adapt to the various SIP implementations. Most companies also have a large installed based of legacy TDM and H.323-based telephony systems. Cisco Unified Communications Manager Session Management Edition (SME) offers session management capabilities for the enterprise. SME provides a rich feature set that allows an enterprise to centrally manage various aspects of their real-time communications such as voice and video and interconnect disparate systems from multiple vendors and service providers.

The world of telephony has traditionally been based on static dial plans. If one system needs to send calls to another system, a static pattern is configured (potentially with wildcards) that indicates the trunk to use to send the call. If that route is unavailable, there may be redundant routes that are, again, statically configured. Some routes may even require manipulation of the digits, for example in the case of rerouting a call to the public switched telephone network (PSTN) in the case of a failure. This manipulation has also traditionally been statically configured on each system that requires that functionality.

As communications migrate from segregated communications that put Voice, Video, Instant Messaging and Email in separate realms of responsibility, the industry is moving towards an environment of true unified communications and


collaboration. The traditional concept of a phone number has slowly started moving to internet-style addressing that looks a lot like an email address.

This identification mechanism is known as a SIP URI (uniform resource identifier). As it looks like an email address, SIP URIs within an enterprise generally cannot be summarized. For example, if [email protected] and [email protected] are both on different Unified CM clusters within the enterprise, how do you summarize those routes? There is really no way to summarize which means that every cluster needs to know how to get to URIs individually as opposed to through a summary. Routes to other domains (e.g. @webex.com, @apple.com) can be summarized by their domain or leverage DNS to look up the domain.

Cisco Unified Communications Manager 9.0 introduced the Inter-cluster Lookup Service (ILS) feature to address this very problem. This feature made it possible for multiple Unified CM clusters to share URI reachability information.

While ILS was a great innovation allowing all clusters to easily share URI dial plan information, this left a hole where traditional numeric dial plans still required static configurations. Also, URIs could not be dialed over the traditional PSTN, so any kind of failover to the PSTN in the event of a network outage or CAC limit was impossible.

Unified CM 10.0 addresses these issues by extending the capabilities of ILS into a new feature called Global Dial Plan Replication (GDPR). GDPR improves how ILS works for URIs and also adds the ability to advertise traditional numeric routes between clusters. With GDPR, every cluster knows how to reach directory numbers anywhere in the network without the need to configure any numeric routes between clusters.

In this lab, you will learn how to create an environment that uses ILS and GDPR to establish a global dial plan. In this multiple cluster environment, you will configure these features to establish calls between different endpoints in the network including calls to and from the PSTN. A centralized Unified CM SME will be utilized to aggregate the dial plan and provide access towards the PSTN via a centralized SIP trunk that uses a Cisco Unified Border Element (CUBE) as the Session Border Controller towards a service provider.


Prerequisites

A basic understanding of Cisco Unified Communications Manager Administration is highly recommended in order to complete this exercise in time. Even though we will provide step-by-step instructions, you should have a basic understanding of:

Cisco IOS configuration

Cisco Unified Communications Manager Dial Plan Management (Calling Search Spaces, Partitions, Translation Patterns)

Understanding of SIP

If you are unfamiliar with configuring Cisco IOS devices, here are a few basic commands to get you started. If you are already familiar with IOS, you can skip to the next page.

To access an IOS device, use the telnet/SSH client provided and authenticate with the provided username and password. In this lab, the provided username and password will automatically log you into the enable mode, so it is not necessary to enter the command enable.

To configure the router, enter the command config t. To exit configuration mode, type end or type control-Z. IOS has various levels of hierarchical configuration. For example, if you enter interface g0/0 while in configuration mode, you are moved to the interface configuration mode. To back-out one level, use the command exit. To save your configuration, exit configuration mode and enter the command wr (or you can use the command copy running-configuration startup-configuration.


Lab Diagram

Your lab network contains the following products: Cisco Unified Communications Manager (x2) Cisco Unified Communications Manager Session Management Edition (SME) Cisco Unified Border Element (CUBE) (x2) Cisco Jabber for Windows 9.6 client (x2)

Each pod of this lab accommodates up to two students. Every pod is identical with the exception of the IP addresses and phone numbers. This manual is customized for your assigned pod number, but you may also refer to the online documentation at http://siplab.ciscolive.com for details.

All these devices are located in a Cisco lab and the connection back to the lab is via a VPN connection. To connect to the lab, click on the link to the VPN connection on the siplab.ciscolive.com site if the connection has not already been established for you.

The following diagram is a high-level topology of the devices you will be configuring in the lab. Your CUBE routers will also connect to a simulated PSTN network as well. You will be configuring all the components shown in the diagram below.

10.0.110.11 10.0.110.12 10.0.110.10

10.0.110.40

10.0.110.50

10.0.110.60


Lab Overview

There are several high-level tasks you will complete in this lab: 1. Configure ILS/GDPR 2. Configure Dial Plan and Session Management Edition 3. Configure Trunks and Route String routing 4. Configure static PSTN routes 5. Configure CUBE and High Availability 6. Enable URI Dialing 7. Bonus Troubleshooting section

You can find access information to your pod on http://siplab.ciscolive.com


Before You Begin

Several pieces of the lab have already been pre-configured for you so that you can spend your time focused on learning about ILS, GDPR, Session Management, and CUBE. The following has already been configured for you:

IP Addresses IP Routing Unified CM and Unified CM SME are installed Services are activated Jabber endpoints have been added and registered to Unified CM (some configuration

changes will be necessary) Users have been added to Unified CM

Additionally, there is a simulated service provider network to which you will connect to route calls out to the PSTN.

Without further ado, lets get on with the lab.


ILS/GDPR Overview

ILS provides a mechanism by which Cisco Unified Communications Manager clusters can distribute information amongst each other. URIs and directory numbers are two of the things that ILS can distribute, but ILS also distributes the list of all clusters that are part of the ILS network.

This makes configuration of ILS very simple. If you already have an existing ILS network and want to add another cluster to the topology, you just point the new cluster to any existing cluster in the topology and the new node will automatically learn about all the other clusters in the network and establish replication links to the other clusters as needed.

In the following diagram we can see clusters 1 and 2 are already peered with each other using ILS.

When Cluster 3 is introduced into the network, you just need to peer to one of the clusters participating in the ILS network. For example, in the diagram above we peer Cluster 3 with Cluster 1. This is what happens:

1. ILS is enabled on Cluster 3 to point towards Cluster 1. 2. Cluster 1 sends the ILS topology to Cluster 3. 3. Cluster 3 then can establish connectivity to the other ILS peers in the network to begin

replicating data with them.

This is a very high level view of the communications between the clusters. Some important things to keep in mind:

1. The ILS process only runs in the publisher node of Unified Communications Manager cluster. This has changed from Unified CM 9.x where ILS ran on multiple nodes in the cluster. In Unified CM 10.0, advertisements are stored in the local database, so database replication within the cluster takes care of getting advertised data to the subscribers.

2. Clusters can be configured to take one of two roles: SPOKE or HUB as described next.


Hub or Spoke In an ILS network a cluster can be configured to be a spoke or as a hub. A hub shares information across the network with all other hubs and as well as spokes that are peered to that hub. A spoke only shares the information with its configured hub. All hub clusters form a full mesh for replication.

This provides a mechanism for creating structure across an ILS network. Depending on the size of the ILS network the use of a spoke might play a role in your network to reduce the size of the full mesh across Unified Communication Manager clusters.

In a scenario where a customer has a Unified CM SME cluster centrally located in the network and various Unified Communications Manager Leaf clusters, the network could be configured as follows:

In a hub and spoke topology, the central hub clusters are in charge of relaying the advertisements of the topology to all the spokes. While this topology seems clean it can delay the advertisement of patterns across the network. As a rule a cluster can never be more than 3 hops away from any other cluster. This is because a spoke can only peer with a hub and all hubs are fully meshed. With the default 10 minutes synchronization timer, a new pattern can take up to 30 minutes to propagate across the network in the worst-case scenario, however those timers can be tuned to speed up the replication process. The diagram below shows the time it takes an advertisement to get from one spoke to another in the case where the two spokes are peered with different hub clusters.


When we look at fully meshed environment where each cluster is a hub, each cluster establishes a full mesh with the other hub members of the ILS network so advertisements only ever take at most one replication cycle to get to other clusters as shown below.

From an administrators point of view, Unified Communications Manager establishes the full mesh automatically. The administrator only needs to establish a connection to one of the hub clusters in the network and it will establish a connection to all known hub clusters configured in the ILS network.

Advertisements ILS/GDPR provides 4 separate buckets containing patterns that are shared across the network.

1. Enterprise Alternate Numbers 2. E164 Alternate Numbers 3. Enterprise Patterns 4. E164 Patterns

Included with each of these are: 1. Advertised by cluster identifier 2. Route string 3. Updated Sequence Number

Each of these plays a key role in how calls are routed across the network. The most important information is the route string. The route string provides the routing information that Unified CM uses to get the call to the correct cluster.

ILS/GDPR maps a given URI or Directory Number to a route string. A route string is nothing more than a domain to route the call to. For example, John Chambers phone might be registered to the San Jose, CA Unified CM cluster represented by the route string sjc.cisco.com, so the URI [email protected] will be associated with the route string sjc.cisco.com.


A cluster still needs to know how to route calls for a given route string. As we will see later, there are different approaches to this.

Once a cluster has received and stored information about remote patterns, it is stored locally in the Unified CM database. Database replication takes care of making sure all the subscribers know about the learned advertisement. The distinction between a statically configured Route Pattern and learned Directory Number is that each learned pattern is associated with a route string instead of a device or route list.

The diagram below shows what happens when a user dials a pattern that has been learned via GDPR/ILS.

The user dials 82103001 which matches route string leaf2-POD10.ciscolive.com. Unified CM then does a look up for leaf2-POD10.ciscolive.com which points to a SIP trunk that then routes the call to the cluster with the destination phone.

+13912102001

leaf1-POD10-ciscolive

leaf1-POD10.ciscolive.com

82103001

Dials:82103001

Match:82103001

leaf2-POD10.ciscolive.com 10.0.110.60


Configure ILS on Unified CM SME Edition

Log into your Unified CM SME cluster (10.0.110.40) using a web browser and log in to Unified CM Administration. You can also click on the link from the siplab.ciscolive.com site.

SME CM IP Username Password

POD10 10.0.110.40 Administrator c1sco123!

Task 1: Configure Cluster ID The first step in configuring ILS is to configure the Cluster ID. The Cluster ID is defined under Enterprise Parameters. This step is critical because every cluster in an ILS network must have a unique cluster ID. Follow these steps to configure the cluster ID:

1. Go to System > Enterprise Parameters 2. Enter sme-POD10-ciscolive in the Cluster ID field. 3. Click Save.

The ILS configuration section is found in the Advanced Features menu on Unified CM:

Task 2: Configure ILS on Unified CM SME Next you will enable ILS to start a new ILS network. In Unified CM SME, perform the following steps:

1. Go to Advanced Features > ILS Configuration 2. Change the Role from Standalone Cluster to Hub Cluster 3. Click the checkbox Exchange Global Dial Plan Replication Data with Remote Clusters

sme-POD10-ciscolive


4. In the box named Advertised Route String change the configuration that is created by default based on DNS to sme-POD10.ciscolive.com

5. Change the Synchronize Clusters Every to 1. This will speed up the process of advertising patterns in the lab. Changing the value to 1 in a large production environment should be analyzed more carefully.

6. ILS can use two different forms of authentication for the replication network - either TLS certificates or a password. You must choose one method and use it throughout the entire network. To use TLS certificates, you must manually copy certificates between all the clusters so that they will trust each other. With a password you just need to configure the same password on all the clusters. For this lab we will use a password. Under ILS Authentication configure the password c1sco123.

7. Click Save

Once you click Save, ILS will display a popup window that asks for you to enter a registration server. Because this is the first cluster in the ILS network there is no registration server, so just click OK with the value empty. This will start the ILS process.

Once configured, the ILS service will start on the publisher node of the Unified CM Cluster. The bottom of the ILS configuration page should contain a table of established ILS peers. A peer to itself should be on the list.

sme-POD10.ciscolive.com

POD 10 POD 1

0


Configure ILS on Unified Communications Manager Leaf 1

Next you will enable ILS on the other clusters to create the replication network.

Following very similar steps that you used to configure ILS on the Unified CM SME cluster, you will configure ILS on the first Leaf Cluster.

Use a web browser to connect to the IP address listed below and log in to Unified CM Administration on your first leaf cluster:

CUCM Leaf 1 Username Password


Task 3: Configure Cluster ID Just as before, the first step in setting up ILS is to configure the Cluster ID. This is configured under Enterprise Parameters. Follow these instructions:

1. Go to System > Enterprise Parameters 2. Enter leaf1-POD10-ciscolive in the Cluster ID field. 3. Click Save.

Task 4: Configure ILS on Unified Communications Manager Leaf 1 Next enable ILS on the cluster and add it to the existing network you configured on the Unified CM SME cluster.

1. Go to Advanced Features > ILS Configuration 2. Change the Role from Standalone Cluster to Hub Cluster 3. Click the checkbox Exchange Global Dial Plan Replication Data with Remote Clusters 4. In the box named Advertised Route String configure leaf1-POD10.ciscolive.com 5. Change Synchronize Clusters Every to 1 6. Under ILS Authentication, select Use Password and configure c1sco123 as the password. 7. Click Save.



For this cluster, you want to peer it with the Unified CM SME cluster you previously configured. Instead of leaving the field blank to register to itself, provide the IP address of the Unified CM SME cluster publisher IP address. For your pod the IP address is 10.0.110.40. Enter this as the Registration Server and click OK.

Immediately after activating ILS, you will only see the local cluster on the list. If you refresh the page, you should see the Unified CM SME cluster show up on the list of ILS clusters as well.

10.0.110.40



Configure ILS on Unified Communications Manager Leaf 2

Now configure ILS on your second Unified CM cluster just as you did for the first. Log into your second Unified CM cluster (10.0.110.60). Use a Web Browser to connect to the IP address listed below and log in to Unified CM Administration:

CUCM Leaf1 Username Password


Task 5: Configure Cluster ID The first step we will do when configuring ILS is to configure the Cluster ID. Configure the cluster ID under Enterprise Parameters.

1. Go to System > Enterprise Parameters 2. Enter leaf2-POD10-ciscolive for the Cluster ID 3. Click Save

Task 6: Configure ILS on Unified Communications Manager Leaf 2 Now enable ILS on the second cluster by following these steps:

1. Go to Advanced Features > ILS Configuration 2. Change the Role from Standalone Cluster to Hub Cluster 3. Click the checkbox Exchange Global Dial Plan Replication Data with Remote Clusters 4. In the box named Advertised Route String configure leaf2-POD10.ciscolive.com 5. Change Synchronize Clusters Every to 1 6. Under ILS Authentication, select Use Password and configure c1sco123 as the password. 7. Click Save

For this cluster, you want to peer it with the Unified CM SME cluster you previously




configured. Instead of leaving the field blank to register to itself, provide the IP address of the Unified CM SME cluster publisher IP address. For your POD the IP address is 10.0.110.40. Enter this as the Registration Server and click OK.

Once completed this task, you can see the full mesh configuration of the ILS clusters for this POD. Each node will show the peers across the network.

Task 7: View ILS Mesh topology To observe the topology established across the ILS peers

1. Go to Advanced > ILS Configuration on any or all of your Unified CM clusters. If you are already on this page, click the Refresh button at the top of the page.

2. At the bottom of the page you will see a table containing the peer status.

You should see 3 separate Unified Communications Clusters in the topology. These show the role for each of these clusters, the cluster ID and the advertised route string that each cluster is providing.

10.0.110.40

POD 10

POD10

POD10

POD10

POD10 POD10


Dial Plan for Unified CM Leaf Cluster 1

Before you configure the dial plan components we will spend a few moments going over the dial plan design for this lab to highlight some of the advantages that Unified CM 10.0 and ILS/GDPR provides.

Lets start with one of the leaf clusters. This diagram shows the structure of the calling search spaces, partitions, translation patterns, and domain patterns that will be used to route calls between clusters. The areas highlighted in yellow are the portions related to GDPR.

In this simple dial plan, we will only have a single class of service that permits all national and international calls, but the design could be expanded to include various classes of service. We are also using a globalized +E.164 dial plan whereby all patterns are first globalized to +E.164 format before being routed. This allows us to


look through the advertised GDPR patterns for a match before attempting to send a call out to the PSTN, thereby facilitating the ability to keep calls on-net if you are dialing an enterprise destination.

As mentioned earlier, GDPR routes are placed into one of four buckets Enterprise Alternate Numbers, +E.164 Alternate Numbers, Enterprise Patterns, and +E.164 Patterns. The distinction between a Number and a Pattern is that a Number is a single DN whereas a Pattern may contain wildcards. As you will see later, the two are configured differently. Upon learning patterns from the GDPR network, the patterns/numbers learned from each bucket are placed into a user-configurable partition. By default, four partitions are already created for you, however you may change them. To view the configuration of the partitions, navigate to Call Routing > Global Dial Plan Replication > Partitions for Learned Numbers and Patterns. You should see a screen like this:

You can see the partitions that are configured by default. Also notice that you can configure whether learned numbers or patterns should be marked as urgent priority or not. This is helpful to avoid inter digit timeout when dialing on-net patterns when you have variable length patterns in your dial plan as well. For example, if you have a pattern for +44! to reach the United Kingdom and are also learning an on-net number of +44234567890, you would want the call to route immediately to that number without having to wait for inter digit timeout. By marking learned numbers as Urgent, you can make this happen.

In addition to the four pre-configured partitions, you will be adding the following partitions in the next section:

Partition Name Description PT_DN164 All Phone Lines will be in this partition in +E.164 format

PT_LocalFeatures Would normally contain things like Call Park Numbers

PT_Abbreviated_Dial Patterns for abbreviated 8+7 digit dialing

PT_GDPR SIP Domain Patterns to reach Route Strings

PT_Local_Translation Would normally contain any local cluster translations


PT_Global_Translation Translation Patterns to globalize PSTN calls by stripping off the access code (9) and converting to +E.164

PT_Local_Route_Patterns +E.164 Route Patterns for reaching Local numbers

PT_National_Route_Patterns +E.164 Route Patterns for reaching National numbers

PT_Intl_Route_Patterns +E.164 Route Patterns for reaching International numbers

Lets configure the partitions for both leaf clusters.

Task 8: Configure partitions on Leaf Cluster 1 Use a Web Browser to connect to the IP address listed below and log in to Unified CM Administration:



1. Go to Call Routing > Class of Control > Partition 2. Click on Add New 3. Now add the following partitions to Leaf Cluster 1

Partitions PT_DN164

PT_LocalFeatures

PT_Abbreviated_Dial

PT_GDPR

PT_Local_Translation

PT_Global_Translation

PT_Local_Route_Patterns

PT_National_Route_Patterns

PT_Intl_Route_Patterns

4. Click Save.


Task 9: Configure CoS Calling Search Space for Leaf Cluster 1 Next configure the calling search spaces on the leaf clusters. You will configure 4 different calling search spaces on this cluster. The following table describes the calling search spaces:

CSS Name Description CSS_COS_CiscoLive_International Contains all patterns a phone can reach. These patterns include local

patterns to other phones as well as GDPR-learned patterns/numbers and patterns to globalize PSTN-dialed numbers.

CSS_COR_CiscoLive_National Contains +E.164 routes for both on-net and off-net patterns to reach national numbers. Used after using translation patterns to globalize numbers to +E.164 format.

CSS_COR_CiscoLive_International Contains +E.164 routes for both on-net and off-net patterns to reach international numbers. Used after using translation patterns to globalize numbers to +E.164 format.

CSS_Inbound_ILS Only has access to local patterns on the cluster. This will be used as the inbound CSS for SIP trunks from other clusters.

To configure the first calling search space on cluster 1, do the following: 1. Go to Call Routing > Class of Control > Calling Search Space 2. Click Add New 3. Under Name enter CSS_COS_CiscoLive_International 4. For the partitions select in the following partitions in this order:

CSS_COS_CiscoLive_International

PT_DN164

Directory URI

PT_LocalFeatures

PT_Abbreviated_Dial

Global Learned E164 Numbers

Global Learned E164 Patterns

Global Learned Enterprise Numbers

Global Learned Enterprise Patterns

PT_GDPR



5. Click Save


Task 10: Configure CoR CiscoLive_National CSS 1. Go to Call Routing > Class of Control > Calling Search Space 2. Click Add New. 3. Under Name enter CSS_COR_CiscoLive_National

Select the following partitions in this order:

CSS_COR_CiscoLive_National

PT_DN164





PT_GDPR


4. Click Save

Task 11: Configure CoR CiscoLive_International CSS 1. Go to Call Routing > Class of Control > Calling Search Space 2. Click Add New. 3. Under Name enter CSS_COR_CiscoLive_International 4. Select the following partitions in this order:

CSS_COR_CiscoLive_International

PT_DN164





PT_GDPR


5. Click Save


Task 12: Configure CSS_Inbound_ILS CSS Finally, configure a CSS for the SIP trunks that will be receiving calls from other clusters.

1. Go to Call Routing > Class of Control > Calling Search Space 2. Click Add New. 3. Under Name enter CSS_Inbound_ILS

Select the following partitions in this order:

CSS_Inbound_ILS PT_DN164

PT_Abbreviated_Dial

Directory URI

4. Click Save


Configure Translation Patterns for Leaf Cluster 1

Use a Web Browser to connect to the IP address listed below and log in to Unified CM Administration:



Task 13: Configure National Translation Pattern All outbound calls will use an access code of 9 followed by standard North American numbering plan dialing. These calls will be globalized to +E.164 format. For national calls, this means stripping the 9 and prefixing a plus (+). After translating, the pattern uses a CSS that looks for the globalized number amongst the local +E.164 patterns, the GDPR-learned patterns as well as route patterns to the PSTN in case there is no on-net match.

1. Go to Call Routing > Translation Pattern in Unified CM Administration on Unified CM #1 2. Click Add New 3. Enter 9.1[2-9]XX[2-9]XXXXXX in the Translation Pattern text box 4. Change the Partition to PT_Global_Translation 5. Change the Calling Search Space to CSS_COR_CiscoLive_National 6. Select the checkbox for Provide Outside Dialtone 7. Select the checkbox Urgent Priority 8. Select the checkbox Do Not Wait for Interdigit Timeout On Subsequent Hops 9. Change Discard Digits to PreDot under Called Party Transformations 10. Enter a + for Prefix Digits (Outgoing Calls) 11. Click Save

Field Value

Translation Pattern 9.1[2-9]XX[2-9]XXXXXX

Partition PT_Global_Translation

Calling Search Space CSS_COR_CiscoLive_National

Discard Digits PreDot

Prefix Digits (outgoing) +


Task 14: Configure International Translation Pattern with # Now do the same for international calls. The outside access code is 9 followed by the international access code of 011. You will configure a pattern to strip the 9011 and append a plus (+). We also want to allow users to indicate end of dialing with a trailing # sign, so you must configure two patterns one with a # and one without. Lets start with the one that has a #:

1. Go to Call Routing > Translation Pattern in Unified CM Administration on Unified CM #1 2. Click Add New 3. Enter 9011.!# in the Translation Pattern text box 4. Change the Partition to PT_Global_Translation 5. Change the Calling Search Space to CSS_COR_CiscoLive_International 6. Select the checkbox for Provide Outside Dialtone 7. Select the checkbox Urgent Priority 8. Select the checkbox Do Not Wait for Interdigit Timeout On Subsequent Hops 9. Change Discard Digits to PreDot Trailing-# under Called Party Transformations. 10. Enter a + for Prefix Digits (Outgoing Calls) 11. Click Save

Field Value

Translation Pattern 9011.!#


Calling Search Space CSS_COR_CiscoLive_International

Discard Digits PreDot Trailing #


!


Task 15: Configure International Translation Pattern without # The last translation pattern is to allow for international dialing without the # to indicate end of dialing. If the pattern doesnt match an internal pattern via ILS/GDPR, inter digit timeout will occur on this translation and the caller will have to wait due to variable length patterns that exist globally.

1. Go to Call Routing > Translation Pattern in Unified CM Administration on Unified CM #1 2. Click Add New 3. Enter 9011.! in the Translation Pattern text box 4. Change the Partition to PT_Global_Translation 5. Change the Calling Search Space to CSS_COR_CiscoLive_International 6. Select the checkbox for Provide Outside Dialtone 7. De-Select the checkbox Urgent Priority 8. De-Select the checkbox Do Not Wait for Interdigit Timeout On Subsequent Hops 9. Change Discard Digits to PreDot under Called Party Transformations. 10. Enter a + for Prefix Digits (Outgoing Calls) 11. Click Save

Field Value

Translation Pattern 9011.!





!


Configure SIP trunk and Route List to SME in Leaf Cluster 1

There are different ways of routing calls when using GDPR/ILS. Because GDPR simply provides a route string that maps to a dialed number or URI, you can choose how calls to those route strings are actually routed. One approach is to configure trunks directly between clusters so that calls to a specific route string are routed directly to the cluster. This requires forming a full-mesh of SIP trunks between clusters. At this time, ILS does not replicate the SIP trunk information for automatic formation of this mesh.

Another approach is to use a generic SIP route pattern to send calls to any route string up to the Unified CM SME cluster and have the specific route strings configured only on Unified CM SME. For this lab, we will use this second approach. Each leaf cluster will be configured with a SIP trunk pointing to the Unified CM SME cluster.




Task 16: Configure SIP trunk to Unified CM SME Perform the following steps to add the SIP trunk pointing to the Unified CM SME cluster:

1. Go to Device > Trunk 2. Click Add new 3. Select SIP Trunk

4. Select SIP for Device Protocol 5. Select None(Default) for Trunk Service Type 6. Click Next


7. Configure the following parameters:

Parameter Configuration Device Name POD10-SME-SIP-TRUNK

Device Pool Default

Calling Search Space CSS_Inbound_ILS

Destination 10.0.110.40

SIP Trunk Security Profile Non Secure SIP Trunk Profile

SIP Profile Standard SIP Profile

8. Click Save 9. Click OK on the popup 10. Click Reset. 11. On the Reset popup click Reset 12. Click Close

Make sure you reset the trunk as listed in the last two steps, otherwise the SIP trunk will not come up and calls will fail.

Task 17: Configure Route Group Now you must configure a route group that contains the SIP trunk pointing to Unified CM SME:

1. Go to Call Routing > Route/Hunt > Route Group 2. Click Add New 3. Enter POD10-RG-SME for the Route Group Name 4. Select POD10-SME-SIP-TRUNK from the Available Devices list 5. Click Add to Route Group 6. Click Save


The screen should be similar to the following:

Task 18: Configure Route List Next, associate the route group containing the SIP trunk to a route list.

1. Go to Call Routing > Route/Hunt > Route List 2. Click Add New 3. Configure the following parameters

Configuration Parameter Name POD10-RL-SME

Cisco Unified Communications Manager Group Default

4. Click Save 5. Click on Add Route Group 6. Select the route group POD10-RG-SME-[NON-QSIG] 7. Click Save 8. Click OK

POD10-RG-SME

POD10-SME-SIP-TRUNK

POD10-SME-SIP-TRUNK ( All Ports )


The screen for the Route List should look like this:

POD10-RG-SME

POD10-RL-SME

POD10-RG-SME


Dial Plan for Unified CM Leaf Cluster 2

Now you must repeat the same steps for the second leaf cluster. The dial plan is identical on the second cluster.

As mentioned earlier, GDPR routes are placed into one of four buckets Enterprise Alternate Numbers, +E.164 Alternate Numbers, Enterprise Patterns, and +E.164 Patterns. The distinction between a Number and a Pattern is that a Number is a single DN whereas a Pattern may contain wildcards. As you will see later, the two are configured differently. Upon learning patterns from the GDPR network, the patterns/numbers learned from each bucket are placed into a user-configurable partition. By default, four partitions are already created for you, however you may change them. To view the configuration of the partitions, navigate to Call Routing > Global Dial Plan Replication > Partit ions for Learned Numbers and Patterns. You should see a screen like this:

You can see the partitions that have already been created for you. Also notice that you can configure whether learned numbers or patterns should be marked as urgent priority or not. This is helpful to avoid inter digit timeout when dialing on-net patterns when you have variable length patterns in your dial plan as well. For example, if you have a pattern for +44! to reach the United Kingdom and are also learning an on-net number of +44234567890, you would want the call to route immediately to that number without having to wait for inter digit timeout. By marking learned numbers as Urgent, you can make this happen.

In addition to the four pre-configured partitions, you will be adding the following partitions:

Part it ion Name Description

PT_DN164 All Phone Lines will be in this partition in +E.164 format

PT_LocalFeatures Would normally contain things like Call Park Numbers

PT_Abbreviated_Dial Patterns for abbreviated 8+7 digit dialing


PT_GDPR SIP Domain Patterns to reach Route Strings

PT_Local_Translation Would normally contain any local cluster translations

PT_Global_Translation Translation Patterns to globalize PSTN calls by stripping off the access code (9) and converting to +E.164

PT_Local_Route_Patterns +E.164 Route Patterns for reaching Local numbers

PT_National_Route_Patterns +E.164 Route Patterns for reaching National numbers

PT_Intl_Route_Patterns +E.164 Route Patterns for reaching International numbers

Follow these steps to add the partitions to the second leaf cluster:

Task 19: Configure partitions on Leaf Cluster 2 Use a Web Browser to connect to the IP address listed below and log in to Unified CM Administration:



1. Go to Call Routing > Class of Control > Partition 2. Click on Add New 3. Now add the following partitions to Leaf Cluster 2

Partit ions PT_DN164

PT_LocalFeatures

PT_Abbreviated_Dial

PT_GDPR



PT_Local_Route_Patterns



4. Click Save.


Task 20: Configure CoS Calling Search Space for Leaf Cluster 2 Next configure the calling search spaces on the leaf clusters. You will configure 4 different calling search spaces on this cluster. The following table describes the calling search spaces:

CSS Name Description

CSS_COS_CiscoLive_International Contains all patterns a phone can reach. These patterns include local patterns to other phones as well as GDPR-learned patterns/numbers and patterns to globalize PSTN-dialed numbers.

CSS_COR_CiscoLive_National Contains +E.164 routes for both on-net and off-net patterns to reach national numbers. Used after using translation patterns to globalize numbers to +E.164 format.

CSS_COR_CiscoLive_International Contains +E.164 routes for both on-net and off-net patterns to reach international numbers. Used after using translation patterns to globalize numbers to +E.164 format.

CSS_Inbound_ILS Only has access to local patterns on the cluster. This will be used as the inbound CSS for SIP trunks from other clusters.

To configure the first calling search space on cluster 2, do the following: 1. Go to Call Routing > Class of Control > Calling Search Space 2. Click Add New 3. Under Name enter CSS_COS_CiscoLive_International 4. For the partitions select in the following partitions in this order:

CSS_COS_CiscoLive_International PT_DN164

Directory URI

PT_LocalFeatures

PT_Abbreviated_Dial






PT_GDPR



5. Click Save

Task 21: Configure CoR CiscoLive_National CSS 1. Go to Call Routing > Class of Control > Calling Search Space 2. Click Add New. 3. Under Name enter CSS_COR_CiscoLive_National 4. Select the following partitions in this order:

CSS_COR_CiscoLive_National PT_DN164





PT_GDPR


5. Click Save

Task 22: Configure CoR CiscoLive_International CSS 1. Go to Call Routing > Class of Control > Calling Search Space 2. Click Add New. 3. Under Name enter CSS_COR_CiscoLive_International 4. Select the following partitions in this order:

CSS_COR_CiscoLive_Local Global Learned E164 Numbers




PT_GDPR


6. Click Save


Task 23: Configure CSS_Inbound_ILS CSS Finally, configure a CSS for the SIP trunks that will be receiving calls from other clusters.

1. Go to Call Routing > Class of Control > Calling Search Space 2. Click Add New. 3. Under Name enter CSS_Inbound_ILS 4. Select the following partitions in this order:

CSS_Inbound_ILS PT_DN164

PT_Abbreviated_Dial

Directory URI


Configure Translation Patterns for Leaf Cluster 2




Task 24: Configure National Translation Pattern All outbound calls will use an access code of 9 followed by standard North American numbering plan dialing. These calls will be globalized to +E.164 format. For national calls, this means stripping the 9 and prefixing a plus (+). After translating, the pattern uses a CSS that looks for the globalized number amongst the GDPR-learned patterns as well as route patterns to the PSTN in case there is no on-net match.

1. Go to Call Routing > Translation Pattern in Unified CM Administration on Unified CM #2 2. Click Add New 3. Enter 9.1[2-9]XX[2-9]XXXXXX in the Translation Pattern text box 4. Change the Partition to PT_Global_Translation 5. Change the Calling Search Space to CSS_COR_CiscoLive_National 6. Select the checkbox for Provide Outside Dialtone 7. Select the checkbox Urgent Priority 8. Select the checkbox Do Not Wait for Interdigit Timeout On Subsequent Hops 9. Change Discard Digits to PreDot under Called Party Transformations. 10. Enter a + for Prefix Digits (Outgoing Calls) 11. Click Save

Field Value

Translation Pattern 9.1[2-9]XX[2-9]XXXXXX


Calling Search Space CSS_COR_CiscoLive_National



!


Task 25: Configure International Translation Pattern with # Now do the same for international calls. The outside access code is 9 followed by the international access code of 011. You will configure a pattern to strip the 9011 and append a plus (+). We also want to allow users to indicate end of dialing with a trailing # sign, so you must configure two patterns one with a # and one without. Lets start with the one that has a #:

1. Go to Call Routing > Translation Pattern in Unified CM Administration on Unified CM #2 2. Click Add New 3. Enter 9011.!# in the Translation Pattern text box 4. Change the Partition to PT_Global_Translation 5. Change the Calling Search Space to CSS_COR_CiscoLive_International 6. Select the checkbox for Provide Outside Dialtone 7. Select the checkbox Urgent Priority 8. Select the checkbox Do Not Wait for Interdigit Timeout On Subsequent Hops 9. Change Discard Digits to PreDot Trailing-# under Called Party Transformations. 10. Enter a + for Prefix Digits (Outgoing Calls) 11. Click Save

Field Value

Translation Pattern 9011.!#



Discard Digits PreDot Trailing #


!


Task 26: Configure International Translation Pattern without # The last translation pattern is to allow for international dialing without the # to indicate end of dialing. If the pattern doesnt match an internal pattern via ILS/GDPR, inter digit timeout will occur on this translation and the caller will have to wait due to variable length patterns that exist globally.

1. Go to Call Routing > Translation Pattern in Unified CM Administration on Unified CM #2 2. Click Add New 3. Enter 9011.! in the Translation Pattern text box 4. Change the Partition to PT_Global_Translation 5. Change the Calling Search Space to CSS_COR_CiscoLive_International 6. Select the checkbox for Provide Outside Dialtone 7. De-Select the checkbox Urgent Priority 8. De-Select the checkbox Do Not Wait for Interdigit Timeout On Subsequent Hops 9. Change Discard Digits to PreDot under Called Party Transformations. 10. Enter a + for Prefix Digits (Outgoing Calls) 11. Click Save

Field Value

Translation Pattern 9011.!





!


Configure SIP trunk and Route List to SME in Leaf Cluster 2

There are different ways of routing calls when using GDPR/ILS. Because GDPR simply provides a route string that maps to a dialed number or URI, you can choose how calls to those route strings are actually routed. One approach is to configure trunks directly between clusters so that calls to a specific route string are routed directly to the cluster. This requires forming a full-mesh of SIP trunks between clusters. At this time, ILS does not replicate the SIP trunk information for automatic formation of this mesh.

Another approach is to use a generic SIP route pattern to send calls to any route string up to the Unified CM SME cluster and have the specific route strings configured only on Unified CM SME. For this lab, we will use this second approach. Each leaf cluster will be configured with a SIP trunk pointing to the Unified CM SME cluster.




Task 27: Configure SIP trunk to Unified CM SME Perform the following steps to add the SIP trunk pointing to the Unified CM SME cluster:

1. Go to Device > Trunk 2. Click Add new 3. Select SIP Trunk

4. Device Protocol will be SIP 5. Trunk Service Type will be None(Default) 6. Click Next 7. Configure the following parameters

Parameter Configuration Device Name POD10-SME-SIP-TRUNK

Device Pool Default


Calling Search Space CSS_Inbound_ILS




8. Click OK on the popup 9. Click Reset. 10. On the Reset popup click Reset.

Make sure you reset the trunk as listed in the last two steps, otherwise the SIP trunk will not come up and calls will fail.

Task 28: Configure Route Group Now you must configure a route group that contains the SIP trunk pointing to Unified CM SME:

1. Go to Call Routing > Route/Hunt > Route Group 2. Click Add New 3. Enter POD10-RG-SME for the Route Group Name 4. Select POD10-SME-SIP-TRUNK from the Available Devices list 5. Click Add to Route Group 6. Click Save

The screen should be similar to the following:

POD10-RG-SME

POD10-SME-SIP-TRUNK ( All Ports )

POD10-SME-SIP-TRUNK


Task 29: Configure Route List Next, associate the route group containing the SIP trunk to a route list.

1. Go to Call Routing > Route/Hunt > Route List 2. Click Add New 3. Configure the following parameters

Configuration Parameter Name POD10-RL-SME

Cisco Unified Communications Manager Group Default

4. Click Save 5. Click on Add Route Group 6. Select the route group POD10-RG-SME-[NON-QSIG] 7. Click Save

The screen for the Route List should look like this:

POD10-RG-SME

POD10-RL-SME

POD10-RG-SME


ILS/GDPR with Centralized Unified CM SME

As mentioned earlier, ILS/GDPR takes care of replicating number and URI mappings to a route string, but each cluster must be configured to route those route strings. This provides deployment flexibility. ILS/GDPR can be configured such that clusters can route calls from leaf nodes to leaf nodes. While this will work, the configuration can become laborious when a significant number of clusters are in the network because it would require a full mesh of trunks as shown below. With this design, the number of SIP trunks scales exponentially as you add clusters.

Another approach is to send all calls to Unified CM SME and let it route calls by route string to each node. The following figure shows the trunk configuration with Unified CM SME.

With this design, when a new cluster is introduced into the network, the administrator only needs to add the route string for the new cluster in Unified CM SME. The number of SIP trunks scales linearly as you add clusters.

With this configuration, all the leaf clusters are configured to send all calls to the organizations top-level domain to Unified CM SME. Unified CM SME is then


configured with the specific sub-domains matching to the route strings for each cluster.

For example, if Cluster 1 learns a pattern or URI from Cluster 2 and that pattern has an associated route string of leaf2-POD10.ciscolive.com, Cluster 1 is configured with a generic pattern of *.ciscolive.com that sends calls to Unified CM SME. Unified CM SME is then configured with a SIP route pattern of leaf2-POD10.ciscolive.com pointing to Cluster 2. The following diagram shows this call flow:

Note that the request URI for the SIP call to Unified CM SME contains the originally dialed number or URI, not the route string. This means that Unified CM SME needs to look in its GDPR table to find the route string for the pattern again. It performs the same ILS/GDPR search and routes the call to the destination because it will contain a specific match for that SIP Route Pattern. Every leaf cluster will contain a single SIP Route Pattern with the wild card *.ciscolive.com pointing to Unified CM SME.

In the next section you will configure the SIP route patterns needed to route the calls via the route strings.

*.cisc

olive

.com

leaf2-

POD10.ciscolive.com


Configure SIP Route String for Unified CM Leaf 1




Task 30: Configure SIP route string 1. Go to Call Routing > SIP Route Pattern 2. Click Add New 3. Configure the following parameters

Parameter Configuration IPV4 Pattern *.ciscolive.com

Route Partition PT_GDPR

SIP Trunk/Route List POD10-RL-SME

4. Click Save

You should have a screen similar to the following:

POD10-RL-SME


Configure SIP Route String for Unified CM Leaf 2




Task 31: Configure SIP route string 1. Go to Call Routing > SIP Route Pattern 2. Click Add New 3. Configure the following parameters

Parameter Configuration IPV4 Pattern *.ciscolive.com


SIP Trunk/Route List POD10-RL-SME

4. Click Save

You should have a screen similar to the following:

POD10-RL-SME


Configure Unified CM SME Dial Plan

Now that you have configured the Unified CM Leaf clusters to route calls to the Unified CM SME, you need to configure the dial plan on Unified CM SME. This dial plan is simplified because it does not have a Class of Service and Class of Restriction structure. That is left for the Unified CM leaf clusters to manage.

As you may have noticed, Unified CM SME is also participating in the ILS/GDPR network. It is also learning patterns from the network just as the Unified CM Leaf clusters are in this network. Calls that are received from the Unified CM Leaf nodes are routed based on pattern matching to a SIP route string from the advertisements learned across the ILS network.

For this lab we are also leveraging Unified CM SME for centralized trunking for PSTN calls. For this reason you will also configure SIP trunks toward the Unified Border element in this network for all Off-Net patterns. Here is the dial plan structure for the Unified CM SME clusters calling search space coming from the leaf clusters:

For the trunks that we will be defining towards the Unified Border Element, we need to configure the following Calling Search Space. This allows inbound calls from the PSTN to be routed to a leaf cluster by looking up the pattern in GDPR/ILS.


Task 32: Configure Partitions in Unified CM SME Use a Web Browser to connect to the IP address listed below and log in to Unified CM Administration on your Unified CM SME cluster:

Unified CM SME Username Password


1. Go to Call Routing > Class of Control > Partitions 2. Click Add New 3. Add the following partitions

Partit ions PT_GDPR



The screen should look as follows:

4. Click Save.

PT_GDPR PT_National_Route_Patterns PT_Intl_Route_Patterns


Task 33: Configure Calling Search Space in Unified CM SME You must configure two calling search spaces in Unified CM SME

1. Go to Call Routing > Class of Control > Calling Search Space 2. Click Add New 3. Configure this Calling Search Space with the following parameters

Parameter Configuration Name CSS_Inbound_Leaf

Selected Partitions Directory URI Global Learned E164 Numbers Global Learned E164 Patterns Global Learned Enterprise Numbers Global Learned Enterprise Patterns PT_GDPR PT_National_Route_Patterns PT_Intl_Route_Patterns

4. Click Save 5. Click Add New 6. Configure the second Calling Search Space with the following parameters

Parameter Configuration Name CSS_Inbound_CUBE

Selected Partitions Global Learned E164 Numbers Global Learned E164 Patterns Global Learned Enterprise Numbers Global Learned Enterprise Patterns PT_GDPR

7. Click Save

Now both calling search spaces should be configured on Unified CM SME.


Configure SIP Trunks on Unified CM SME

You will configure 3 total trunks on Unified CM SME - one for each of the Unified CM Leaf Clusters and one for the Unified Border Element.




Task 34: Configure SIP Trunk to Unified CM Leaf 1 1. Go to Device > Trunk 2. Click Add New 3. Select SIP Trunk 4. Device Protocol SIP 5. Trunk Service Type None (Default)

6. Click Next 7. Configure the SIP Trunk with the following parameters

Parameter Configuration Device Name POD10-LEAF1-SIP-TRUNK

Device Pool Default

Calling Search Space CSS_Inbound_Leaf




8. Click Save 9. Click OK on the popup 10. Click Reset 11. On the Reset popup click Reset 12. Click Close

Task 35: Configure SIP Trunk to Unified CM Leaf 2 1. Go to Device > Trunk 2. Click Add New 3. Select SIP Trunk


4. Device Protocol SIP 5. Trunk Service Type None (Default)

6. Click Next 7. Configure the SIP Trunk with the following parameters

Parameter Configuration Device Name POD10-LEAF2-SIP-TRUNK

Device Pool Default

Calling Search Space CSS_Inbound_Leaf





Task 36: Configure SIP Trunk to Unified Border Element 1. Go to Device > Trunk 2. Click Add New 3. Select SIP Trunk 4. Device Protocol SIP 5. Trunk Service Type None (Default)

6. Click Next


7. Configure the SIP Trunk with the following parameters

Parameter Configuration Device Name POD10-CUBE-SIP-TRUNK

Device Pool Default

Calling Search Space CSS_Inbound_CUBE






Configure Route Groups and Route Lists in Unified CM SME

In Unified CM SME we will need to configure 3 separate Route Groups and Route Lists to point to each individual SIP trunk you just configured. Although the SIP Route Pattern can be associated to a trunk directly, it is best practice to use route lists and route groups.




Task 37: Configure Route Group for Unified CM Leaf 1 1. Go to Call Routing > Route/Hunt > Route

Group 2. Click Add New 3. Configure the Route Group with the

following parameters

Configuration Parameter

Route Group Name POD10-Leaf1-RG

Selected Devices POD10-LEAF1-SIP-TRUNK

4. Click Save.

POD10-Leaf1-RG

POD10-LEAF1-SIP-TRUNK

POD10-CUBE-SIP-TRUNK POD10-LEAF1-SIP-TRUNK POD10-LEAF2-SIP-TRUNK



Task 38: Configure Route Group for Unified CM Leaf 2 1. Go to Call Routing > Route/Hunt > Route



Configuration Parameter Route Group Name POD10-Leaf2-RG

Selected Devices POD10-LEAF2-SIP-TRUNK

4. Click Save.

Task 39: Configure Route Group for Unified Border Element 1. Go to Call Routing > Route/Hunt > Route




Route Group Name POD10-CUBE-RG

Selected Devices POD10-CUBE-SIP-TRUNK

4. Click Save.

POD10-Leaf2-RG




POD10-CUBE-RG

POD10-CUBE-SIP-TRUNK


POD10-CUBE-SIP-TRUNK


Task 40: Configure Route List for Unified CM Leaf 1 1. Go to Call Routing > Route/Hunt > Route

List 2. Click Add New 3. Configure the Route List Information with

the following parameters


Name POD10-Leaf1-RL

Unified CM Group Default

4. Click Save 5. Click Add Route Group. 6. Once in Route List Member Information

select the Route Group POD10-Leaf1-RL 7. Click Save 8. Click Apply Config 9. Click OK on the popup.

Task 41: Configure Route List for Unified CM Leaf 2 1. Go to Call Routing > Route/Hunt > Route




Name POD10-Leaf2-RL



select the Route Group POD1-Leaf2-RG 7. Click Save 8. Click Apply Config 9. Click OK on the popup.

POD10-Leaf2-RL

POD10-Leaf2-RG

POD10-Leaf2-RG

POD10-Leaf1-RL

POD10-Leaf1-RG

POD10-Leaf1-RG


Task 42: Configure Route List for Unified Border Element 1. Go to Call Routing > Route/Hunt > Route




Name POD10-CUBE-RL



select the Route Group POD10-CUBE-RG 7. Click Save 8. Click Apply Config 9. Click OK on the popup.

POD10-CUBE-RL

POD10-CUBE-RG

POD10-CUBE-RG


Configure SIP Route Pattern in Unified CM SME

As we have mentioned in various parts of the document, we have to configure specific routing for the route string that is advertised by the leaf clusters. You have already configured a SIP Route Pattern of *.ciscolive.com on the leaf clusters that point to the Unified CM SME.

Now you have to configure Unified CM SME with two unique SIP Route Patterns. Because ILS is already configured in the network, we can check the ILS peer configuration page to see the different advertised route strings in the network.

In Unified CM SME if you go to Advanced Features > ILS Configuration on the bottom of the screen is the peering process. You should see the following:

To reach each of the clusters you need to configure each advertised route string. SIP Route Patterns



Task 43: Configure SIP Route Pattern for Unified CM Leaf 1 1. Go to Call Routing > SIP Route Pattern 2. Click Add New 3. Configure the SIP Route Pattern with the



IPv4 Pattern leaf1-POD10.ciscolive.com


SIP Trunk/Route List POD10-Leaf1-RL



sme-POD10.ciscolive.com

Leaf1-POD10-ciscolive

Leaf2-POD10-ciscolive

sme-POD10-ciscolive


POD10-Leaf1-RL

PT_GDPR


Task 44: Configure SIP Route Pattern for Unified CM Leaf 2 1. Go to Call Routing > SIP Route Pattern 2. Click Add New 3. Configure the SIP Route Pattern with the



IPv4 Pattern leaf2-POD10.ciscolive.com


SIP Trunk/Route List POD10-Leaf2-RL


POD10-Leaf2-RL

PT_GDPR


Configure Phone Line in Unified CM Leaf 1

Now that the dial plan is setup between the three clusters, you must configure the line of the phones such that each cluster can advertise the directory numbers into the network. We will be utilizing soft phones for this lab by enabling Phone Mode Jabber client.

For each directory number in Unified CM, GDPR/ILS allows you to advertise two different kinds of advertisements: Enterprise Alternate Numbers and +E.164 Alternate Numbers. Although technically speaking you can use these two categories to carry whatever kind of advertisement you want, the intention is that the Enterprise Alternate Number will contain some form of global private dial plan numbering (e.g. site-code based dialing) while the +E.164 Alternate Number will contain the true globally reachable +E.164 number.




Task 45: Configure Global Dial Plan Replication for Phone #1 In Unified Communications Manager 10.x, the administrator is presented with new options when configuring the line. Perform the following steps to configure the line parameters:

1. Go to Device > Phone 2. Click Find 3. You should see the list of phones. 4. Click on the device CSFPOD10USER1 5. Once in the Phone Configuration, click on

Line [1] 6. The line DN has been pre-configured with

the +E.164 value for this device. 7. Select PT_DN164 for the Route Partition of

this line. 8. Change the Calling Search Space to

CSS_COS_CiscoLive_International 9. Click Save 10. Scroll down until you can see two fields;

Enterprise Alternate Number and +E.164 Alternate Number

11. Click on Add Enterprise Al

Documents

Best Sip-cube Lab