SIP Route Patterns#

Overview#

This section applies to Provider deployments only.

Cisco Unified Communications Manager (CUCM) uses SIP route patterns to route or block both internal and external calls.

The domain name or IP address provides the basis for routing. The administrator can add domains, IP addresses, and IP network (subnet) addresses and associate them to SIP trunks (only). This method allows requests that are destined for these domains to be routed through particular SIP trunk interfaces.

Configure SIP Route Patterns#

This procedure configures a SIP route pattern.

Prerequisites

Configure at least one SIP Profile and SIP trunk before configuring a SIP route pattern.

Perform these steps

Log in as Provider, Reseller, or Customer administrator.
Ensure that the hierarchy path is set to a customer or site level.
If prompted, choose the NDL that contains the CUCM which you are configuring the SIP Route Pattern.
Choose an option, depending on your login:
- Provider or Reseller administrator: Go to (default menus) Apps Management > CUCM > SIP Route Patterns.
- Customer administrator? Go to (default menus) Apps Management > Advanced > SIP Route Patterns.
Click Add.
On the Pattern Definition tab, complete the Pattern Definition Tab.
On the Calling Party Transformations tab, complete the Calling Party Transformations Tab.
On the Connected Party Transformations tab, complete the Connected Party Transformations Tab.
Click Save.

Pattern Definition Tab#

Field	Description
Pattern Usage	From the drop-down list, choose either Domain Routing or IP Address Routing. This field is mandatory.
IPv4 Pattern	Enter the domain, subdomain, IPv4 address, or IP subnetwork address. This field is mandatory. For Domain Routing pattern usage, enter a domain name IPv4 Pattern field that can resolve to an IPv4 address. The domain name can contain the following characters: -, ., 0-9, A-Z, a-z, *, ], and [. For IP Address Routing pattern usage, enter an IPv4 address with the format X.X.X.X, where X represents a number between 0 and 255. For the IP subnetwork address, in classless interdomain routing (CIDR) notation, X.X.X.X/Y; where Y is the network prefix that denotes the number of bits in the network address. Tip: If the SIP trunk supports IPv6 or both IPv4 and IPv6 (dual-stack mode), configure the IPv6 Pattern in addition to the IPv4 pattern.
IPv6 Pattern	Unified CM uses SIP route patterns to route or block both internal and external calls. The IPv6 address in this field provides the basis for routing internal and external calls to SIP trunks that support IPv6. Tip: If the SIP trunk supports IPv6 or both IPv4 and IPv6 (dual-stack mode), configure the IPv4 Pattern in addition to the IPv6 pattern.
Description	Enter a description of the SIP Route Pattern. The description can include up to 50 characters in any language, but it cannot include double-quotes ("), percentage sign (%), ampersand (&), or angle brackets (<>).
Route Partition	If you want to use a partition to restrict access to the SIP route pattern, choose the desired partition from the drop-down list box. If you do not want to restrict access to the SIP route pattern, leave the Route Partition value empty.
SIP Trunk/Route List	Choose the SIP trunk or route list to which the SIP route pattern is associated. This field is mandatory.
Block Pattern	Select this check box if you want this pattern to be used for blocking calls.

Calling Party Transformations Tab#

Field	Description
Use Calling Party’s External Phone Mask	Select On if you want the full, external phone number to be used for calling line identification (CLID) on outgoing calls. Select Default to use the default External Phone Number Mask. This field is mandatory.
Calling Party Transformation Mask	Enter a transformation mask value. Valid entries include the digits 0 to 9 and the wildcard characters X, asterisk (*), and octothorpe (#). If this field is blank and the preceding field is not selected, no calling party transformation takes place.
Prefix Digits (Outgoing Calls)	Enter prefix digits in the Prefix Digits (Outgoing Calls) field. Valid entries include the digits 0 to 9 and the wildcard characters asterisk (*) and octothorpe (#). Note: The appended prefix digit does not affect which directory numbers route to the assigned device.
Calling Line ID Presentation	Calling line ID presentation (CLIP/CLIR) is a supplementary service that allows or restricts the originating caller phone number on a call-by-call basis. Choose whether you want to allow or restrict the display of the calling party phone number on the called party phone display for this SIP route pattern. Choose Default if you do not want to change calling line ID presentation. Choose Allowed if you want to allow the display of the calling number. Choose Restricted if you want to block the display of the calling number.
Calling Line Name Presentation	Calling line name presentation (CNIP/CNIR) is a supplementary service that allows or restricts the originating caller name on a call-by-call basis. Choose whether you want to allow or restrict the display of the calling party name on the called party phone display for this SIP route pattern. Choose Default if you do not want to change calling name presentation. Choose Allowed if you want to allow the display of the caller name. Choose Restricted if you want to block the display of the caller name.

Connected Party Transformations Tab#

Field	Description
Connected Line ID Presentation	Connected line ID presentation (COLP/COLR) is a supplementary service that allows or restricts the called party phone number on a call-by-call basis. Choose whether you want to allow or restrict the display of the connected party phone number on the calling party phone display for this SIP route pattern. Choose Default if you do not want to change the connected line ID presentation. Choose Allowed if you want to display the connected party phone number. Choose Restricted if you want to block the display of the connected party phone number. If a call originating from an IP phone on Unified CM encounters a device, such as a trunk, gateway, or route pattern, that has the Connected Line ID Presentation set to Default, the presentation value is automatically set to Allowed.
Connected Line Name Presentation	Connected name presentation (CONP/CONR) is a supplementary service that allows or restricts the called party name on a call-by-call basis. Choose whether you want to allow or restrict the display of the connected party name on the calling party phone display for this SIP route pattern. Choose Default if you do not want to change the connected name presentation. Choose Allowed if you want to display the connected party name. Choose Restricted if you want to block the display of the connected party name.

Field

Description

Connected Line ID Presentation

Connected line ID presentation (COLP/COLR) is a supplementary service that allows or restricts the called party phone number on a call-by-call basis.

Choose whether you want to allow or restrict the display of the connected party phone number on the calling party phone display for this SIP route pattern.

Choose Default if you do not want to change the connected line ID presentation. Choose Allowed if you want to display the connected party phone number. Choose Restricted if you want to block the display of the connected party phone number.

If a call originating from an IP phone on Unified CM encounters a device, such as a trunk, gateway, or route pattern, that has the Connected Line ID Presentation set to Default, the presentation value is automatically set to Allowed.

Connected Line Name Presentation

Connected name presentation (CONP/CONR) is a supplementary service that allows or restricts the called party name on a call-by-call basis.

Choose whether you want to allow or restrict the display of the connected party name on the calling party phone display for this SIP route pattern.

Choose Default if you do not want to change the connected name presentation. Choose Allowed if you want to display the connected party name. Choose Restricted if you want to block the display of the connected party name.

SIP Route Patterns

On this page