Static Route Configuration on IM and Presence Service
If you configure a static route for SIP proxy server traffic, consider the following:
-
A dynamic route represents a path through the network that is automatically calculated according to routing protocols and routing update messages.
-
A static route represents a fixed path that you explicitly configure through the network.
-
Static routes take precedence over dynamic routes.
Route Embed Templates
You must define a route embed template for any static route pattern that contains embedded wildcards. The route embed template contains information about the leading digits, the digit length, and location of the embedded wildcards. Before you define a route embed template, consider the sample templates we provide below.
When you define a route embed template, the characters that follow the "." must match actual telephony digits in the static route. In the sample route embed templates below, we represent these characters with "x".
Sample Route Embed Template A
Route embed template: 74..78xxxxx*
With this template, IM and Presence Service will enable this set of static routes with embedded wildcards:
Destination Pattern |
Next Hop Destination |
---|---|
74..7812345* |
1.2.3.4:5060 |
74..7867890* |
5.6.7.8.9:5060 |
74..7811993* |
10.10.11.37:5060 |
With this template, IM and Presence Service will not enable these static route entries:
-
73..7812345* (The initial string is not ‘74’ as the template defines)
-
74..781* (The destination pattern digit length does not match the template)
-
74…7812345* (The number of wildcards does not match the template)
Sample Route Embed Template B
Route embed template: 471….xx*
With this template, IM and Presence Service will enable this set of static routes with embedded wildcards:
Destination Pattern |
Next Hop Destination |
---|---|
471….34* |
20.20.21.22 |
471…55* |
21.21.55.79 |
With this template, IM and Presence Service will not enable these static route entries:
-
47…344* (The initial string is not ‘471’ as the template defines)
-
471…4* (The string length does not match template)
-
471.450* (The number of wildcards does not match template)
Configure Route Embed Templates on IM and Presence Service
You can define up to five route embed templates. However, there is no limit to the number of static routes that you can define for any route embed template.
A static route that contains an embedded wildcard must match at least one of the route embed templates.
Procedure
Step 1 |
Choose . |
Step 2 |
Choose an IM and Presence Service node. |
Step 3 |
Choose the Cisco SIP Proxy service. |
Step 4 |
Define a route embed templates in the RouteEmbedTemplate field in the Routing Parameters (Clusterwide) section. You can define up to five route embed templates. |
Step 5 |
Choose Save. |
What to do next
Proceed to configure static routes on IM and Presence Service.
Configure Static Routes on IM and Presence Service
The following table lists the static route parameter settings that you can configure for IM and Presence Service.
Field |
Description |
---|---|
Destination Pattern |
This field specifies the pattern of the incoming number, up to a maximum of 255 characters. The SIP proxy allows only 100 static routes to have an identical route pattern. If you exceed this limit, IM and Presence Service logs an error. Wildcard Usage You can use "." as a wildcard for a single character and "*" as a wildcard for multiple characters. IM and Presence Service supports embedded '.' wildcard characters in static routes. However, you must define route embed templates for static routes that contain embedded wildcards. Any static route that contains an embedded wildcard must match at least one route embed template. See the route embed template topic (referenced in the Related Topics section below) for information about defining route embed templates. For phones:
For IP addresses and host names:
An escaped asterisk sequence, \*, matches a literal * and can exist anywhere. |
Description |
Specifies the description of a particular static route, up to a maximum of 255 characters. |
Next Hop |
Specifies the domain name or IP address of the destination (next hop) and can be either a Fully Qualified Domain Name (FQDN) or dotted IP address. IM and Presence Service supports DNS SRV-based call routing. To specify DNS SRV as the next hop for a static route, set this parameter to the DNS SRV name. |
Next Hop Port |
Specifies the port number of the destination (next hop). The default port is 5060. IM and Presence Service supports DNS SRV-based call routing. To specify DNS SRV as the next hop for a static route, set the next hop port parameter to 0. |
Route Type |
Specifies the route type: User or Domain. The default value is user. For example, in the SIP URI "sip:19194762030@myhost.com" request, the user part is "19194762030", and the host part is "myhost.com". If you choose User as the route type, IM and Presence Service uses the user-part value "19194762030" for routing SIP traffic. If you choose the Domain as the route type, IM and Presence Service uses "myhost.com" for routing SIP traffic. |
Protocol Type |
Specifies the protocol type for this route, TCP, UDP, or TLS. The default value is TCP. |
Priority |
Specifies the route priority level. Lower values indicate higher priority. The default value is 1. Value range: 1-65535 |
Weight |
Specifies the route weight. Use this parameter only if two or more routes have the same priority. Higher values indicate which route has the higher priority. Value range: 1-65535 Example: Consider these three routes with associated priorities and weights:
In this example, the static routes are listed in the correct order. The priority route is based on the lowest value priority, that is 1. Given that two routes share the same priority, the weight parameter with the highest value decides the priority route. In this example, IM and Presence Service directs SIP traffic to both routes configured with a priority value of 1, and distributes the traffic according to weight; The route with a weight of 20 receives twice as much traffic as the route with a weight of 10. Note that in this example, IM and Presence Service will only attempt to use the route with priority 2, if it has tried both priority 1 routes and both failed. |
Allow Less-Specific Route |
Specifies that the route can be less specific. The default setting is On. |
In Service |
Specifies whether this route has been taken out of service. This parameter allows the administrator to effectively take a route out of service (versus removing it completely and re-adding it). |
Block Route Check Box |
Check to block the static route. The default setting is Unblocked. |
Procedure
Step 1 |
Choose . |
Step 2 |
Click Add New. |
Step 3 |
Configure the static route settings. |
Step 4 |
Click Save. |