Add_docset_workflow | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Panel |
---|
...
...
...
In this section:
|
Info |
---|
...
|
...
| |
Related articles: |
...
...
...
Include Page Transparency_Profile_Note Transparency_Profile_Note
Telephone Number Mapping (ENUM) transforms the telephone number into a universal identifier recognized across different devices and applications (voice, fax, mobile, e-mail, text messaging, location-based services and the Internet). ENUM can also be used to implement a variety of services like number portability, call forwarding etc. It uses a DNS NAPTR record to translate a telephone number into a Uniform Resource Identifier or IP address that can be used in Internet communications.
Since a call may span multiple network elements, to avoid redundant ENUM queries, the
...
supports (when configured) processing the Spacevars 0 series4 enumdi
parameter received on ingress INVITE. Similarly, if ERE/PSX performs an ENUM dip, the
...
sends this parameter in egress INVITE to the next network element identifying that an ENUM query has already been made for the TEL URI, thus preventing redundant queries further down the network. Spacevars 0 product
The
also supports sending ENUM queries and receive responses, using the Signaling Interface. The user can configure the Signaling Interface for sending ENUM queries and receive responses, using the packet interface port 988. The packets from the Signaling Interface are prioritized over the packets from the Management Interface. Spacevars 0 product
Info | ||||
---|---|---|---|---|
The default behavior of the
|
The Feature Control Profile flag to enable processing of the enumdi
parameter is processEnumdi
. For example,
Code Block |
---|
% set profiles featureControlProfile <profile name> processEnumdi enable |
Note |
---|
If R-URI transparency flag ( |
...
|
The
...
Spacevars | ||
---|---|---|
|
The result of a successful ENUM NAPTR query is a SIP URI telephone number received in the Request-URI resolved to a SIP URI. To perform an ENUM NAPTR query, the
...
Spacevars | ||
---|---|---|
|
By default,
...
the
Spacevars | ||
---|---|---|
|
For example, an ENUM query to an external DNS for the ENUM NAPTR record for the SIP URI sip:+1-212-555-5678@1.2.3.4 is sent using the format 8.7.6.5.5.5.5.2.1.2.1.e164.arpa. The
...
Spacevars | ||
---|---|---|
|
...
Spacevars | ||
---|---|---|
|
...
Spacevars | ||
---|---|---|
|
...
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
When
...
the
Spacevars | ||
---|---|---|
|
...
Spacevars | ||
---|---|---|
|
...
Spacevars | ||
---|---|---|
|
In a NAPTR response to ENUM query, any one of the following strings are recognized as indicating that a SIP address-of-record appears in the URI field:
In the following example, five records were received; the record with the rrk2 address is used because it has the highest order (100) and highest preference (10).
Provisioned records for (44) 1793601415:
5.1.4.1.0.6.3.9.7.1.4.4.e164.arpa. IN NAPTR 300 10 "u" "E2U+sip" "!^.*$!sip:rrk1@sonusnet.com!"
5.1.4.1.0.6.3.9.7.1.4.4.e164.arpa. IN NAPTR 100 10 "u" "E2U+sip" "!^.*$!sip:rrk2@sonusnet.com!"
5.1.4.1.0.6.3.9.7.1.4.4.e164.arpa. IN NAPTR 200 10 "u" "E2U+sip" "!^.*$!sip:rrk3@sonusnet.com!"
5.1.4.1.0.6.3.9.7.1.4.4.e164.arpa. IN NAPTR 100 20 "u" "E2U+sip" "!^.*$!sip:rrk4@sonusnet.com!"
5.1.4.1.0.6.3.9.7.1.4.4.e164.arpa. IN NAPTR 400 10 "u" "E2U+sip" "!^.*$!sip:rrk5@sonusnet.com!"
The NAPTR Resource Record (RR) uses the following format:
Domain TTL Class Type Order Preference Flags Service Regexp Replacement
"Flags" is a <character-string> containing flags to control aspects of the rewriting and interpretation of the fields in the record. Flags are single characters from the set [A-Z0-9]. The case of the alphabetic characters is not significant.
At this time only four flags, "S", "A", "U", and "P", are defined.
The "S", "A" and "U" flags denote a terminal lookup. This means that this NAPTR record is the last one and that the flag determines what the next stage should be.
Flag | Description |
---|---|
S | The next lookup should be for SRV records. |
A | The next lookup should be for either an A, AAAA, or A6 record. |
U | The next step is not a DNS lookup but that the output of the Regexp field is an URI that adheres to the 'absoluteURI' production found in the ABNF of RFC 2396 [9]. Since there may be applications that use NAPTR to also lookup aspects of URIs, implementors should be aware that this may cause loop conditions and should act accordingly. |
P | The remainder of the application side algorithm shall be carried out in a Protocol-specific fashion. The new set of rules is identified by the Protocol specified in the Services field. The record that contains the 'P' flag is the last record that is interpreted by the rules specified in this document. |
For details refer to the IETF RFC at https://tools.ietf.org/html/rfc2915.
ENUM LNP enables number portability lookups in the IP network without the need to consult an external element in the SS7 network, thus simplifying call routing and networking operations.
The Routing Number must use one of the following formats:
To provision ENUM LNP, enter ported numbers into the
...
Spacevars | ||
---|---|---|
|
When a Routing Request triggers an ENUM LNP lookup,
...
the
Spacevars | ||
---|---|---|
|
...
Spacevars | ||
---|---|---|
|
...
Spacevars | ||
---|---|---|
|
ENUM CNAM enables calling name lookups on the IP network without having to consult an external element in the SS7 network, thus simplifying call routing and network operations.
To provision ENUM CNAM, specify the trigger criteria in the Number Translation Criteria entity and specify the ENUM CNAM as the lookup type. ENUM CNAM, provisioned through the DNS-ENUM Service Definition screen, uses the same triggering and escape criteria as SCP-based CNAM. When a Routing Request triggers an ENUM CNAM lookup, the
...
Spacevars | ||
---|---|---|
|
...
Spacevars | ||
---|---|---|
|
The ERE platform
...
supports number translations based on the host part (contains a fully-qualified domain name) of the SIP headers. As the IP address format is not supported for host part lookup, it is recommended to use the fully-qualified domain name.
...
The
Spacevars | ||
---|---|---|
|
The supported destination domain SIP headers are:
R-URI Header
TO Header
Contact Header
CalledUri
and toHeader
element types are used to support call processing. Configure any of these element types to trigger number translations. The domain names configured in number translations are converted to upper case and stored in ERE as uppercase.
The following are configured based on service priority:
The ERE after executing the SIP AoR service, receives the domain name from the NAPTR RR SIP-URI and the system continues to trigger the next service ENUM CNAM in the priority list. In general, ERE uses the domain name received from SIP AoR service for routing. The ERE updates the CalledUri
with the information received from SIP AoR and then performs any other number translations as required.
To facilitate this service interaction ENUM SIP AoR service must be provisioned with a higher priority than ENUM CNAM service. ENUM CNAM service must be provisioned with element type as calledUri.
The mandatory parameter priority
is used to set the priority of this ENUM service. The ENUM service cannot be created if priority
is not set. This parameter is used to prioritize the order of the ENUM service execution. Priority of the ENUM server hold the values in range (
...
0..
...
255).
...
Multiple ENUM services can be created with the same service type, such as sipAor, lnp, and cnam.
The ENUM service is triggered based on the trigger criteria created. The flag skipFurtherNumberTranslations
skips further ENUM service execution and goes directly to routing. The default value is disable
.
Info |
---|
For configuration details, refer to:
|
...
Spacevars | ||
---|---|---|
|
...
The
transparently sends custom and standard userinfo parameters such as tgrp, trunk-context, cic and rn received in ENUM response. Spacevars 0 product
...
The
sends these parameters in the R-URI of the egress INVITE. Spacevars 0 product
This behavior is controlled by enabling the IP Signaling Profile flag “includeEnumParameters”. The default value is "disable". When enabled,
...
the
either adds ENUM response parameters to the R-URI or overwrites egress INVITE R-URI parameter value with the ENUM response parameter value (egress INVITE parameters are determined based on the existing Spacevars 0 product
...
process logic and transparency mechanism). Spacevars 0 product
Code Block | ||||
---|---|---|---|---|
| ||||
% set profiles signaling ipSignalingProfile <profile name> egressIpAttributes flags includeEnumParameters < enable | disable > |
Info |
---|
For configuration details, see:
|
...
...
...
...
The
Spacevars | ||
---|---|---|
|
...
Spacevars | ||
---|---|---|
|
...
Spacevars | ||
---|---|---|
|
...
Spacevars | ||
---|---|---|
|
...
Spacevars | ||
---|---|---|
|
...
Spacevars | ||
---|---|---|
|
...
Spacevars | ||
---|---|---|
|
This feature supports a new process slwresd in SBC ERE and replaces the existing lwresd. The new process takes care of initializing the bind stack according to the load distribution type configured for a particular domain. The new enumDomainName entity in SBC is added to support new configurations required for supporting different load distribution strategy. The new entities enumDomainName, lwresdProfile, and enumDomainNameLabel are added by the new slwresd process for initializing the bind stack.
...
Note | ||||
---|---|---|---|---|
The enumDomain parameter is deprecated in the
|
Note |
---|
For an |
Info |
---|
For configuration details, |
...
...
Pagebreak |
---|