Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

ENUM is a protocol that uses DNS on internet to translate E.164 numbers (E.164=public enum directory of telephone numbers using ITU-T standard). Enum maps a telephone number to an e-mail address, website, VoIP address, etc. The IMG 2020 supports ENUM E2U+sip to resolve an ENUM telephone number into a SIP URI. The IMG 2020 enum is follows the procedures in the following RFC's:

RFC 3764  - enumservice registration for Session Initiation Protocol (SIP) Addresses-of-Record

RFC 3761- The E.164 to URI DDDS Application (ENUM)

RFC 3824- Using E.164 numbers with SIP

RFC 3263- Locating SIP Servers

RFC 3401- Dynamic Delegation Discovery System (DDDS) - Part 1

Some of the benefits of Enum on IMG 2020

  • A user is calling from the PSTN through a PSTN-SIP gateway and the gateway is expected to map routing information from the PSTN directly on to SIP signaling.  

  • A native SIP user intentionally initiates a call addressed to an E.164 number.

  • Add the ENUM behavior in the IMG 2020 as a way to minimize the proxy’s activities and centralize the number translation functions in the User Agent.

  • Application servers may initiate SIP calls destined to end users and transiting through the IMG 2020.  

Follow the procedures below to configure ENUM service.

ENUM Diagram

Diagram below displays the IMG 2020 which accepts a E.164 telephone number. The IMG 2020 converts the number and adds .e164.arpa to it as displayed below. The Database does a lookup and converts the query to E2U+SIP format (sip:info@example.com) and sends back to IMG 2020 where it is added to a SIP INVITE message. See diagram below.

 

Call Trace

Refer to Call Trace - ENUM  link.

Configuration

The procedure below explains how to configure the IMG 2020 for a SIP enum query. Before configuring SIP ENUM, the IMG 2020 must have an initial configuration created on it. Follow the Basic Configurations procedure before proceeding onto configuring SIP enum feature.

Create a SIP Profile (SGP)

  1. Right click on the Profiles object and select New SIP Profiles. The SIP Profiles object is a parent or container object. No configuration is needed here. Refer to the SIP Profiles  topic for more information on this object.

  2. Right click on the SIP Profiles object and select New SIP Profile. The first profile that gets created is a Default SIP Profile and cannot be modified. Disregard this profile.

  3. Right click on the SIP Profiles object and select New SIP Profile again. In the SIP Profile object that appears, either enter a name that identifies this SIP Profile or accept the default name already entered. In this example the SIP Profile was labeled SIP Default. For information on configuring the individual fields in the SIP Profile object, refer to the SIP Profile - SGP topic.

Create a SIP ENUM Server Set

  1. Right click on the Dialogic object and select New External Network Elements. The External Network Elements object is a parent or container object and no configuration is needed here. Refer to External Network Elements topic for more information.

  2. Right click on External Network Elements object and select New ENUM Server Set. Either enter a name that identifies the ENUM Server Set being configured or accept the default entry.

  3. In the SIP Profile field, select the SIP Profile created above. Refer to the ENUM Server Set topic for information on configuring the remaining fields.

  4. Right click on ENUM Server Set and select New ENUM Server. Either enter a name that identifies the ENUM Server being configured or accept the default entry.

  5. Enter the IP address of the ENUM Server in the IP address field. This will be the IP address the IMG 2020 uses to communicate with the ENUM server.

Create a DNS Client

Configure the DNS server that the IMG 2020 will communicate with in order to translate the E.164 number into SIP URI.

  1. Configure DNS Server

  2. Configure DNS Client Server Association

  3. Configure DNS Client

These are the same steps as configuring a DNS server for Host Name resolution. Refer to Configure DNS topic for more information.

Configure SIP Channel Group

  1. Right click on the Dialogic object and select New Routing Configuration. The Routing Configuration object is a parent or container object and no configuration is needed here. Refer to the Routing Configuration topic for more information.

  2. Right click on the Routing Configuration object and select New Channel Groups. The Channel Groups object is a container object also and no configuration is needed. Refer to the Channel Groups topic for more information.

  3. Right click on the Channel Groups object and select New Channel Group. Either enter a name that identifies this channel group or accept the default entry. In this example the Channel Group was labeled ENUM_CG.

  4. Select SIP from the drop down menu of the Signaling Type field. Refer to Channel Group  topic for more information on configuring the remaining fields.

Insert SIP External Network Element into SIP Channel Group

Right Click on the SIP Channel group created and select New IP Network Element. Within the IP Network Element field, select from drop down menu, the ENUM Server Set created. See screen capture below.

Click on the Channel Groups object again. The Channel Groups object will have a yellow exclamation point in place of the icon indicating the configuration has not been sent to the IMG 2020. Click on the Download Resource Tables button and the new configuration will be sent to the IMG 2020.

Create the Node Association

The Node Association object is created under the IP Network Element object. The IP Network Element object binds an IP Channel Group such as a SIP Channel group to an external remote gateway in the network. The Node Association object associates the IP address that was configured as a SIP IP Address to an individual Packet Facility.

In the ENUM Client field, select the DNS Client that will be used to translate E.164 numbers into SIP URI.

Activate the Resource Table Download

Click on the Channel Groups object again. The Channel Groups object will have a yellow exclamation point in place of the icon indicating the configuration has not been sent to the IMG 2020. Click on the Download Resource Tables button and the new configuration will be sent to the IMG 2020.

Configure SIP Signaling (Cont)

The configuration above displays how to create and configure the SIP Profile object, the SIP Channel Group, the SIP ENUM Server and how to associate the ENUM Server to the channel group. If not already configured, the SIP signaling stack and associated objects need to be configured. Refer to the Configure SIP (Single SIP IP) topic for a procedure that describes how to configure the SIP signaling functionality. This procedure can be used to finish the SIP configuration for this feature.

Additional Information

  • ENUM resolution is to be accomplished on outbound SIP INVITE when L4 provides an Outseize Control with an external gateway of type enum.

  • ENUM resolution is to be accomplished on outbound SIP requests when a previously provided target has an E.164 format. A "previously provided" target is either a contact or a route that contained a URI user part with an E.164 format, received in a SIP message.

  • If the IMG 2020 is unable to create or translate an E.164 number into an ENUM query, SIP L3 is to reply to L4 with an Outseize Nack.

  • The maximum number of ENUM queries for any given call leg is 10.

  • If an ENUM query returns multiple AOR, the IMG 2020 is to send a single SIP request, and is not to fork the request to multiple AOR. Therefore if the NAPTR record all hold the same weight, the first one is to be used

  • The maximum number of configurable ENUM Server Sets is four. Each ENUM Server Set is to allow up to three DNS servers.

  • No security consideration is implemented. The information provided within an ENUM record set, just as in a DNS record, must be considered to be open to the public.

  • No labels