Skip to end of metadata
Go to start of metadata



A SIP URI is the SIP addressing scheme used to contact other SIP users on other SIP networks. The standard format for a SIP URI is:


A SIP URI must not contain special characters, such as "(), [], {}, *, #, $, !, ^". Using these characters may cause problems as these are special characters and may provide an unintended result.

See following pages to configure URIs for a SIP Adaptor Profile:

SBC supports SIP URI messages containing up to 20 parameters in any SIP header. However, increasing the number of URI parameters impacts memory usage. For example, increasing the number of parameters from 10 to 20 will increase memory usage by approximately 10%.


SIP URI scheme allows resources to require a secure connection using TLS for each hop over which a request is forwarded to the target domain. SIPS scheme enables protection against attackers trying to listen in on the signaling link.

The SBC currently does not carry the URI scheme received in the ingress leg forward to the egress leg, and does not provide an option to enforce TLS as a secured transport when the SIP URI scheme is “sips”. This feature provides the requisite options to achieve the following using new Trunk Group configuration:

  • Enforce SIPS if egress transport is TLS.
  • Enforce TLSIfSipsUriScheme if ingress URI has SIPS.

The SBC rejects a request received in following scenarios:

  1. In non-TLS transport if the Request URI scheme is SIPS if “EnforceTlsIfSipsUriScheme” is enabled at the trunk group on which request is received.
  2. With SIPS scheme in contact, but SIP scheme in Request-Uri, if “EnforceSipsIfEgressIsTls” is enabled at the trunk group on which request is received.

See the following pages for configuration details:

SIP URI Transparency

In a mixed FQDN and IP environment when a message is outbound, SIP URIs or TEL URIs may contain identities/usernames that are not global and may also contain private IP addresses.This makes the message meaningless when the call is forwarded to another IP-domain. SBC Core overcomes this obstacle by providing the following SIP URI transparency capabilities.

  • Standardizing telephone numbers representations in the network by globalizing the user part of URIs in various headers of outgoing SIP PDUs.
  • Supporting mixed FQDN and IP environments by defining domain mapping rules to rewrite host part of URIs in various headers of outgoing SIP PDUs.

These capabilities ensure that SIP-URIs and TEL-URLs in a network always describe an unambiguous valid global user identity.

SIP headers considered for user name globalization and domain mapping rules are categorized as:

  • Originating Identities: FROM, PAI and DIVERSION
  • Terminating Identities: TO and RURI

User Name Globalization

Publicly accessible telephone number formats are shown below. Any additional publicly accessible telephone number formats are rewritten at the network border.


Private accessible telephone number formats are shown below. These formats are an allowed identities, but are not publicly accessible telephone numbers.


A Globalization example is provided below.

Ingress Message:


Egress Message:


Domain Name Mapping Rules

Some networks allow mixed ingress traffic supporting both FQDN and IP addresses requiring manipulation to preserve the FQDNs or replace IP addresses. This is achieved by defining domain mapping rules to rewrite the host part of URIs in various headers of outgoing SIP PDUs.The domain names used for originating identities are based on inbound trunk group. The domain names used for terminating identities are related to the outbound trunk group or to the routing label.

Example of domain name mapping for SIP URIs:

Ingress Message:


Egress Message:




SIP URI Preference Over TEL URI

For domain name mapping, SBC gives preference to SIP URI over TEL URL for a given originating/terminating identity when URI preference is set to SIP.

Ingress Message:


Egress Message:


PSX Globalize Profile provides globalization information for all originating and terminating identities individually in policy response to SBC. For more information, see "Globalize Profile Screen" in PSX documentation.

To configure Domain Name Mapping details for all the originating and terminating identities individually, see PSX documentation "DM/PM Rule Screen".

  • No labels