Overview
The URI Dialing feature describes the enhancements that are made to Uniform Resource Identifier (URI)-based dialing on Cisco Unified Border Element (CUBE) for Session Initiation Protocol (SIP) calls. The URI-Based Dialing Enhancements feature includes support for call routing on CUBE when the User Part of the incoming Request-URI is non-E164 (for example, INVITE sip:user@abc.com).
Cisco Unified Communications Manager supports dialing using directory Uniform Resource Identifiers (URIs) for call addressing. Directory URIs follow the username@host format where the host portion is an IPv4 address or a fully qualified domain name. Use a directory URI to identify a directory number. Assign that directory number to a phone, so that Unified Communications Manager can route calls to that phone using the directory URI. URI dialing is available for Session Initiation Protocol (SIP) and Signaling Connection Control Part (SCCP) endpoints that support directory URIs.
The URI Dialing feature extends support for CUBE URI routing of calls. With these enhancements CUBE supports:
-
URI routing when the User Part of the incoming Request-URI is non-E164 (for example, INVITE sip:user@abc.com).
-
URI routing when the User Part is not present. The User Part is an optional parameter in the URI (for example, INVITE sip: abc.com).
-
Copying the outgoing Request-URI and To header from the inbound Request-URI and To header respectively.
-
Deriving (optionally) the session target for the outbound dial peer from the host portion of the inbound URI.
-
URI routing for 302, Refer, and Bye Also scenarios.
-
Call hunting where the subsequent dial peer is selected based on URI.
-
Pass through of 302, with the host part of Contact: unmodified.
Note |
The minimum supported release of Cisco IOS required for URI-based call routing on dial-peers is Cisco IOS XE Gibraltar Release 16.12. You must configure the 'call-route-url' on the outgoing dial-peers to properly route the refer-to headers based on the URI matching. |
Feature Information
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Feature Name |
Releases |
Feature Information |
---|---|---|
URI-Based Dialing Enhancements |
The following commands were introduced or modified: contact-passing , requri-passing , session target sip-uri and voice-class sip requri-passing |
Call Flows for URI-Based Dialing Enhancements
Case1: URI dialing with username being E164 or non-E164 number and Request-URI host copied from the inbound leg.
Case 2: Incoming Request-URI does not contain user part. The To: header information is also copied from the peer leg when the requri-passing command is enabled.
Case 3: The old behavior of setting the outbound Request-URI to session target is retained when the requri-passing command is not enabled.
Case 4: The session target derived from the host part of the URI. The outgoing INVITE is sent to resolved IP address of the host part of the URI.
Case 5: Pass through of contact URI to request URI.
Case 6: In 302 pass-through, contact header can be passed through from one leg to another by using the contact-passing command.
Case 7: Pass through of refer-to URI to request URI.
Case 8: URI routing based on BYE Also header.