...
Panel |
---|
...
...
In this section:
|
...
Info |
---|
...
|
...
| |
Related articles: |
...
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:
USER@ADDRESS
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.
Info |
---|
...
Refer to the following pages to configure URIs for a SIP Adaptor Profile: |
Include Page | ||||
---|---|---|---|---|
|
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
...
Spacevars | ||
---|---|---|
|
The
...
Spacevars | ||
---|---|---|
|
Info |
---|
...
Refer to the following pages for configuration details: |
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. The
Spacevars | ||
---|---|---|
|
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:
Publicly accessible telephone number formats are shown below. Any additional publicly accessible telephone number formats are rewritten at the network border.
Code Block | ||
---|---|---|
| ||
TEL:+<ISN>
SIP:+<ISN>@domain.name;user=phone |
Private accessible telephone number formats are shown below. These formats are an allowed identities, but are not publicly accessible telephone numbers.
Code Block | ||
---|---|---|
| ||
sip:<digits>@some.domain
sip:user@domain.com |
A Globalization example is provided below.
Ingress Message:
Code Block | ||
---|---|---|
| ||
SIP:0<NSN>@domain.name;user=phone
|
Egress Message:
Code Block | ||
---|---|---|
| ||
SIP:+<CC><NSN>@domain.name;user=phone |
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:
Code Block | ||
---|---|---|
| ||
SIP:+<ISN>@<IP-address>;user=phone
|
Egress Message:
Code Block |
---|
TEL:+<ISN |
OR
Code Block | ||
---|---|---|
| ||
SIP:+<ISN>@some.domain;user=phone |
For domain name mapping,
...
the
Spacevars | ||
---|---|---|
|
Ingress Message:
Code Block | ||
---|---|---|
| ||
TEL:0<NSN> |
Egress Message:
Code Block | ||
---|---|---|
| ||
SIP:+<CC><NSN>@some.domian;user=phone |
Note |
---|
The PSX Globalize Profile provides globalization information for all originating and terminating identities individually in policy response to |
...
the
|
...
refer to the "Globalize Profile Screen" in PSX documentation. To configure Domain Name Mapping details for all the originating and terminating identities individually, |
...
refer to PSX documentation "DM/PM Rule Screen". |
Pagebreak |
---|