-
Cisco IOS XR Session Border Controller Configuration Guide Release 3.6
-
About This Guide
-
About SBC Deployment Models
-
SBC Configuration Prerequisites
-
Implementing SBC Adjacencies
-
Configuring SIP Method Profiles
-
Configuring Header Profiles
-
Restricting Codecs
-
SIP Tel URI Support
-
SIP Timer
-
H.323 Support
-
H.323-SIP Interworking
-
Implementing SBC Policies
-
Tracking Policy Failure Statistics
-
Implementing SBC Firewall Traversal and NAT
-
Implementing SBC Interworking DTMF
-
SIP 3xx Redirect Responses
-
SIP Call Hold
-
SIP Call Transfer
-
Encrypted SIP Signaling
-
SIP Outbound Authentication
-
SIP Inbound Authentication
-
SIP-I Transparency and Profile Support
-
SIP Configuration Flexibility
-
Implementing SBC QoS (Marking)
-
DoS Prevention and Dynamic Blacklisting
-
Unexpected Source Address Alerting
-
Implementing SBC Billing
-
Implementing SBC Redundancy (High Availability)
-
Implementing SBC Multi-VRF
-
Implementing SBC Transcoding
-
Configuring DBE Overload Reporting
-
Media Address Pools
-
Early Media
-
Fax Support
-
Nine-Tier Termination Name Hierarchy
-
Multiple Streams in a H.248.1 v3 Termination
-
DBE Signaling Pinhole Support
-
IPv6 Support on the DBE
-
Extension of H.248 Termination Wildcarding
-
Optional H.248 Ginfo Package
-
H.248.1 v3 Support
-
H.248 Traffic Management (Tman)
-
Context Attribute Descriptor Support
-
H.248 Historical Event Notification
-
H.248 Segmentation Package Support
-
H.248 Configurable T-Max
-
H.248 Configurable VRF
-
Implementing H.248 nt/qualert Events
-
H.248 Gateway Profile Configuration
-
Interim Authentication Header Support
-
IP NAPT Traversal Support
-
MGC-Controlled Gateway-Wide Properties
-
MGC-Specified Local Addresses and Ports
-
Optional Local and Remote Descriptors
-
Provisioned Inactivity Timer
-
Disabling RTP Flows
-
Discarded Packet Statistics
-
IPv4/IPv6 Voice Clipping Avoidance
-
Secure Media Support
-
RADIUS VPN Support
-
Configurable Base Root Package
-
MGC Information Package Support
-
Ia Profile Support
-
Integration of Resource Management and SIP
-
P-CSCF Support
-
IBCF Processing Support
-
End-to-End SBC Configuration Example on a Cisco XR 12000 Series Router
-
Additional Information about Billing Support
-
Index
-
Table Of Contents
Restrictions for SIP Tel URI Support
Information About SIP Tel URI Support
The Carrier Identification Code (CIC) Parameter
SIP Tel URI Support
The SBC supports Tel Uniform Resource Identifier (tel URI) in SIP messages, permitting SIP users to set up calls from a SIP IP-phone or SIP User Agent Application to an endpoint in the Public Switched Telephone Network (PSTN). The addition of tel URI to the SIP URI method of connection greatly increases the functionality of the SBC. SIP can use the tel URI anywhere a URI is allowed, for example, as a Request-URI, along with SIP and SIP URIs.
.Feature History for SIP Tel URI Support
Release 3.4.1
This feature was introduced on the Cisco XR 12000 Series Router.
Release 3.5.0
No modification.
Release 3.6.0
No modification.
Contents
This module contains the following sections:
•
Restrictions for SIP Tel URI Support
•
Restrictions for SIP Tel URI Support
The following is a list of restrictions for SIP tel URI support.
•
sip:1234567@remote.combecomes
sip:1234567@1.2.3.4:5060•
•
•
Information About SIP Tel URI Support
Local and Global Tel URIs
A tel URI can either be global or local. Global tel URIs are globally unique. Local tel URIs are only valid within a specific local context. For this reason, all local tel URIs must contain the phone-context parameter to specify the context in which they are valid.
The following are examples of a global and local tel URIs, respectively.
tel:+358-555-1234567
Note
tel:1234567;phone-context=+358-555This URI locates the endpoint with the directory number 1234567 in the context 358-555.
Note
Tel URI Versus SIP URI
A SIP URI consists of a username and host domain name. A SIP URI uniquely identifies a SIP subscriber but does not necessarily resolve to one particular endpoint on a network. For example,
sip:john@cisco.comIt is also possible to use a directory number as a SIP username and an IP address and port in place of the host domain name. In this case, a SIP URI can uniquely identify an endpoint on a network. For example,
sip:1234567@192.167.1.1:5060Local tel URIs may or may not contain a domain name in the phone-context parameter. For example,
tel: 1234567;phone-context=cisco.comThe Carrier Identification Code (CIC) Parameter
A Carrier Identification Code is a three- or four-digit number used to identify the carrier network in which the destination endpoint of a call is located. It is used by network devices to determine how a call request should be routed between carrier networks. The CIC is often used to specify which carrier network is the current freephone service provider for a freephone number. The current carrier for a given freephone number can be determined by looking up a freephone database.
Tel URIs can include carrier identification codes. For example,
tel: +1-800-234-5678;cic=2345indicates that the carrier that has been assigned the CIC 2345 is currently the service provider for the freephone number, 1-800-234-5678.
When a network device receives a call request with a tel URI containing a CIC parameter, it will try to route the request according to the value of the CIC parameter. If it cannot route the request, it must decide whether to reject it or continue, ignoring the CIC parameter. If the CIC parameter matches the CIC of the carrier network, in which the network device is located, it should route the request based on its local routing policy and strip out the CIC parameter before forwarding the request.
Note
Additional References
The following sections provide references related to SIP tel URI support.
Related Documents
Standards
No new or modified standards are supported by this feature, and support from existing standards has not been modified by this feature.
—
MIBs
—
To locate and download MIBs using Cisco IOS XR software, use the Cisco MIB Locator found at the following URL and choose a platform under the Cisco Access Products menu:
RFCs
Technical Assistance
