Configuring SIP Route Patterns in Cisco Unified Communications Manager

Created by Rami Kandah Introduction

This white paper discusses the Session Initiation Protocol (SIP) Route Pattern feature that is available in Cisco Unified Communications Manager 5.x, 6.x, and 7.x. The SIP Route Pattern feature allows SIP endpoints to initiate calls using SIP Uniform Resource Identifier (URI) dialing. Although SIP route patterns use numeric route patterns conceptually, they are very different from their traditional numeric route pattern counterpart when it comes to routing decisions. Unlike traditional route patterns, SIP route patterns can use only SIP trunks. Another important distinction between SIP route patterns and traditional route patterns is that SIP phones can use SIP route patterns or traditional route patterns, but Skinny phones can use only traditional route patterns. In order to demonstrate SIP interoperability and show how SIP route patterns work, this white paper uses a third-party SIP phone to make international calls to Germany using an Internet telephony service provider (ITSP). The following sections show various working configurations and screen shots that were captured from a lab environment. More information on the SIP Route Pattern feature and other Cisco Unified Communications Manager features can be found on www.cisco.com.

Topology
The following lab topology demonstrates the various components of the network:
Mary Smith (San Jose, USA) +14085552004

Voice Gateway

Cisco Unified Communications Manager Third-Party SIP Softphone

PSTN Internet
DNIS: 331214002

SIP Route Pattern: de.xyz.com

ITSP
Domain: de.xyz.com
John Doe (Munich, Germany) +4989331214002

Configuring SIP Route Patterns in Cisco Unified Communications Manager

2009 Cisco Systems, Inc.

Configuration Steps:
The following configuration steps are required:
Step 1 Step 2 Step 3 Step 4

Configure SIP softphone on Cisco Unified Communications Manager. Configure X-Lite softphone. Configure SIP Trunk on Cisco Unified Communications Manager. Configure clusterwide domain fields in Enterprise parameters on Cisco Unified Communications Manager. Configure SIP Route Pattern on Cisco Unified Communications Manager.

Step 5

Configuring SIP Softphone on Cisco Unified Communications Manager

In order to demonstrate SIP interoperability between Cisco Unified Communications Manager and thirdparty SIP phones, the X-Lite SIP VoIP softphone, a freeware application that can be downloaded from the Internet, will be used. Add the SIP VoIP softphone on Cisco Unified Communications Manager by clicking Device > Phone > Add New, then selecting Third-party SIP Device (Basic).

Configuring SIP Route Patterns in Cisco Unified Communications Manager

2009 Cisco Systems, Inc.

The screen shot below shows the SIP softphone configuration:

Note: The MAC address for the phone can be any dummy MAC address. Also note that the Digest User, sipphone, will also be configured on the X-Lite softphone application as seen below. The rest of the configurations are typical of that of a SIP phone with the exception of the third-party fields: Phone Button Templates and Device Security Profile.

Configuring SIP Route Patterns in Cisco Unified Communications Manager

2009 Cisco Systems, Inc.

Configuring the X-Lite Softphone

Configure the X-Lite softphone Account parameters as follows: Note that the Authorization user name matches the Digest User, sipphone, on the phone configuration page in Cisco Unified Communications Manager. The domain proxy Address used in this case is the IP address of the Cisco Unified Communications Manager, 10.1.5.3. The Dialing plan is left as the default.

Configuring SIP Route Patterns in Cisco Unified Communications Manager

2009 Cisco Systems, Inc.

The X-Lite softphone should register with Cisco Unified Communications Manager as shown below:

Configuring the SIP Trunk

Configure the SIP Trunk in Cisco Unified Communications Manager as follows: Click Device > Trunk > Add New. Note: Only the SIP Information Section will be discussed below. For detailed information on all of the fields used in SIP Trunk configuration, refer to www.cisco.com. SIP Information Section: Destination Address: 10.1.5.1 (IP address of the ITSP router) Destination Port: 5060 (default) SIP Trunk Security Profile: Non Secure SIP Trunk Profile SIP Profile: Standard SIP Profile The remaining fields are left as the defaults.

Configuring SIP Route Patterns in Cisco Unified Communications Manager

2009 Cisco Systems, Inc.

Configuring SIP Route Patterns in Cisco Unified Communications Manager

2009 Cisco Systems, Inc.

Configuring Clusterwide Domain Fields in Enterprise Parameters

Click System > Enterprise Parameters in Cisco Unified Communications Manager. Note: The Top Level Domain name is abc.com, and for this particular cluster, it is sj.abc.com. These fields are important during the call-routing decision; Cisco Unified Communications Manager checks the host portion of the URI against these parameters. If the host portion matches the cluster domain name, the call gets routed internally. On the contrary, if the host portion does not match the cluster domain name, the call gets routed via the SIP Trunk as configured on the SIP Route Pattern.

Configuring the SIP Route Pattern

Configure the SIP Route Pattern in Cisco Unified Communications Manager as follows: Click Call Routing > SIP Route Pattern > Add New.

Configuring SIP Route Patterns in Cisco Unified Communications Manager

2009 Cisco Systems, Inc.

SIP Route Pattern Configuration Parameters:

Pattern Usage: Domain Routing IPv4 Pattern: de.xyz.com (Alternatively, we could use IPAddress routing. In which case, we would point to the ITSP subnet address.) Route Partition: HQ_Intl (In order for the X-Lite softphone to access this partition, its calling search space needs to contain this partition.) SIP Trunk: SIP_Routing (This is the SIP Trunk that we configured previously. It has to be preconfigured for it to be shown as a drop-down option.) The remaining fields are no different than the traditional route pattern fields.

Configuring SIP Route Patterns in Cisco Unified Communications Manager

2009 Cisco Systems, Inc.

Testing and Verification

The address of John Doe in Munich is added to the address book of Mary as: 0114989331214002@de.xyz.com

Configuring SIP Route Patterns in Cisco Unified Communications Manager

2009 Cisco Systems, Inc.

When Mary, who is in San Jose, wants to call John in Munich, she simply clicks on Johns address in her address book as shown below:

When Cisco Unified Communications Manager sees the call, it looks at the host portion of the dialed URI, de.xyz.com, and checks against its list of SIP route patterns. A match is found against de.xyz.com. Cisco Unified Communications Manager then checks the host portion of the URI against its cluster domain name, sj.abc.com. Because there is no match, it forwards the call over the SIP Trunk, SIP_Routing, as configured.

10

Configuring SIP Route Patterns in Cisco Unified Communications Manager

2009 Cisco Systems, Inc.

Now we will examine the call at the ITSP side to see if the call is coming out of Munich as a local call: debug isdn q931 *Dec 5 03:29:13.935: ISDN Se0/0/0:23 Q931: Applying typeplan for sw-type 0x12 is 0x0 0x1, Calling num 2004 *Dec 5 03:29:13.935: ISDN Se0/0/0:23 Q931: Sending SETUP callref = 0x008D callID = 0x800E switch = primary-net5 interface = User *Dec 5 03:29:13.935: ISDN Se0/0/0:23 Q931: TX -> SETUP pd = 8 callref = 0x008D Bearer Capability i = 0x8090A2 Standard = CCITT Transfer Capability = Speech Transfer Mode = Circuit Transfer Rate = 64 kbit/s Channel ID i = 0xA98381 Exclusive, Channel 1 Calling Party Number i = 0x0181, '2004' Plan:ISDN, Type:Unknown Called Party Number i = 0x81, '331214002' Plan:ISDN, Type:Unknown *Dec 5 03:29:13.963: ISDN Se0/0/0:23 Q931: RX <- CALL_PROC pd = 8 callref = 0x808D Channel ID i = 0xA98381 Exclusive, Channel 1 *Dec 5 03:29:14.031: ISDN Se0/0/0:23 Q931: RX <- ALERTING pd = 8 callref = 0x808D Progress Ind i = 0x8188 - In-band info or appropriate now available *Dec 5 03:29:19.151: ISDN Se0/0/0:23 Q931: RX <- CONNECT pd = 8 callref = 0x808D *Dec 5 03:29:19.151: %ISDN-6-CONNECT: Interface Serial0/0/0:0 is now connected to 331214002 N/A *Dec 5 03:29:19.151: %ISDN-6-CONNECT: Interface Serial0/0/0:0 is now connected to 331214002 N/A *Dec 5 03:29:19.151: ISDN Se0/0/0:23 Q931: TX -> CONNECT_ACK pd = 8 callref = 0x008D As shown here, the call breaks out of the ITSP router in Munich as a local public switched telephone network (PSTN) call.

11

Configuring SIP Route Patterns in Cisco Unified Communications Manager

2009 Cisco Systems, Inc.