Dialogic ControlSwitch ENUM User guide

Brand: Dialogic

Model: ControlSwitch ENUM

Type: User guide

Dialogic® ControlSwitch™

ENUM Service

Revision 02

Release 5.10.2

June 2015

www.dialogic.com

in writing from Dialogic Corporation at the address provided below.

All contents of this document are furnished for informational use only and are subject to change without notice and do not represent

a commitment on the part of Dialogic Corporation and its affiliates or subsidiaries (“Dialogic”). Reasonable effort is made to ensure

the accuracy of the information contained in the document. However, Dialogic does not warrant the accuracy of this information and

cannot accept responsibility for errors, inaccuracies or omissions that may be contained in this document.

INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH DIALOGIC® PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY

ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN A SIGNED

AGREEMENT BETWEEN YOU AND DIALOGIC, DIALOGIC ASSUMES NO LIABILITY WHATSOEVER, AND DIALOGIC DISCLAIMS ANY EXPRESS OR

IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF DIALOGIC PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS

FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY INTELLECTUAL PROPERTY RIGHT OF A THIRD PARTY.

Dialogic products are not intended for use in certain safety-affecting situations. Please see http://www.dialogic.com/company/terms-of-

use.aspx for more details.

Due to differing national regulations and approval requirements, certain Dialogic products may be suitable for use only in specific countries,

and thus may not function properly in other countries. You are responsible for ensuring that your use of such products occurs only in the

countries where such use is suitable. For information on specific products, contact Dialogic Corporation at the address indicated below or on

the web at www.dialogic.com.

It is possible that the use or implementation of any one of the concepts, applications, or ideas described in this document, in marketing

collateral produced by or on web pages maintained by Dialogic may infringe one or more patents or other intellectual property rights owned by

third parties. Dialogic does not provide any intellectual property licenses with the sale of Dialogic products other than a license to use such

product in accordance with intellectual property owned or validly licensed by Dialogic and no such licenses are provided except pursuant to a

signed agreement with Dialogic. More detailed information about such intellectual property is available from Dialogic’s legal department at

6700 de la Cote-de-Liesse Road, Suite 100, Borough of Saint-Laurent, Montreal, Quebec, Canada H4T 2B5. Dialogic encourages all users of its

products to procure all necessary intellectual property licenses required to implement any concepts or applications and does not condone or

encourage any intellectual property infringement and disclaims any responsibility related thereto. These intellectual property licenses may

differ from country to country and it is the responsibility of those who develop the concepts or applications to be aware of and comply with

different national license requirements.

Dialogic, Dialogic Pro, Dialogic Blue, Veraz, Brooktrout, Diva, BorderNet, PowerMedia, ControlSwitch, I-Gate, Network Fuel, Mobile Experience

Matters, Video is the New Voice, Making Innovation Thrive, Diastar, Cantata, TruFax, SwitchKit, Eiconcard, NMS Communications, SIPcontrol,

Exnet, EXS, Vision, inCloud9, NaturalAccess and Shiva, among others as well as related logos, are either registered trademarks or trademarks of

Dialogic Corporation and its affiliates or subsidiaries. Dialogic's trademarks may be used publicly only with permission from Dialogic. Such

permission may only be granted by Dialogic’s legal department at 6700 de la Cote-de-Liesse Road, Suite 100, Borough of Saint-Laurent,

Montreal, Quebec, Canada H4T 2B5. Any authorized use of Dialogic's trademarks will be subject to full respect of the trademark guidelines

published by Dialogic from time to time and any use of Dialogic’s trademarks requires proper acknowledgement.

The names of actual companies and products mentioned herein are the trademarks of their respective owners.

This document discusses one or more open source products, systems and/or releases. Dialogic is not responsible for your decision to use open

source in connection with Dialogic products (including without limitation those referred to herein), nor is Dialogic responsible for any present

or future effects such usage might have, including without limitation effects on your products, your business, or your intellectual property

rights..

Document History

Revision#

Version Date

Comments

April 2012

Initial Release

June 2015

Updated for release 5.10.2

Refer to www.dialogic.com for product updates and for information about support policies, warranty

information, and service offerings.

ControlSwitch (v.5.10.2) ENUM

 Dialogic Inc. Proprietary Page 3

Table of Contents

INTRODUCTION ............................................................................................................................................ 4 1.

1.1 Overview ..................................................................................................................................................... 4

ENUM OVERVIEW ......................................................................................................................................... 5 2.

ARCHITECTURE ............................................................................................................................................. 7 3.

CONFIGURATION .......................................................................................................................................... 8 4.

CALL FLOWS ................................................................................................................................................. 9 5.

5.1 Normal LNP ................................................................................................................................................. 9

5.2 LNP Timeout ................................................................................................................................................ 9

5.3 Normal LNP and Routing ........................................................................................................................... 10

5.4 LNP and Routing Timeout ......................................................................................................................... 11

ENUM TOOLS IN THE CS ............................................................................................................................... 13 6.

6.1 CDRs .......................................................................................................................................................... 13

6.2 Call Trace ................................................................................................................................................... 14

6.3 Reports ...................................................................................................................................................... 15

6.4 Alarms ....................................................................................................................................................... 15

ControlSwitch (v.5.10.2) ENUM

 Dialogic Inc. Proprietary Page 4

Introduction 1.

1.1 Overview

CS supports ENUM services by using the LSG element. The supported ENUM services are as following:

 LNP

 Routing

 LNP and routing – provided by using ENUM in one transaction

The services are applied on all ingress calls/trunk groups.

The LSG element queries a selected external ENUM server, maps between the received and the system

trunk groups, and populates the relevant parameters in SIP messages, based on the server's response. If

the server returns more than maximum allowed trunk groups in the trunk group list (configurable,

default=10), the LSG removes the trunk group with lowest priority.

This document describes the CS's ENUM services.

ControlSwitch (v.5.10.2) ENUM

 Dialogic Inc. Proprietary Page 5

ENUM Overview 2.

ENUM is a client-server protocol, created to resolve the E.164 numbers, based on DNS:

 The client sends an ENUM request (query):

Figure 1: Sample ENUM Query Format

 The server responses: The ENUM answer contains one or more NAPTR records. In the example blow

the record contains the ’rn’ and ’npdi’ parameters. The ’rn’ parameter represents the ported

number for an LNP service implementation.

Figure 2: Sample ENUM Answer Format

Note:

Only NAPTR records with the record type “u” are supported by the ControlSwitch System. Refer to the appropriate RFC for

additional information on ENUM response formats.

ENUM query format

To convert a number to the ENUM format, follow the below steps:

1. Remove all the visual characters [such as '-' or '+']

2. Put '.' [dot] between all the digits

3. Reverse the order of digits

4. Append .e164.arpa at the end (arpa or whatever is configured in service node)

ControlSwitch (v.5.10.2) ENUM

 Dialogic Inc. Proprietary Page 6

Example: Number +44-116-496-0348 get converted to 8.4.1.0.6.4.9.7.0.2.4.4.e164.arpa for sending DNS

query.

Examples:

The ENUM DNS server responses in different formats:

 LNP only:

$ORIGIN 1.0.0.0.3.7.5.8.0.4.1.e164.arpa.

IN NAPTR 10 100 "U" "e2u+pstn:SIP"

"!(^.*)$!SIP:14085730000;rn=25555555555;npdi=yes@10.20.230.52:7004;user=phone!"

 Routing only:

$ORIGIN 1.0.0.0.3.7.5.8.0.4.1.e164.arpa.

IN NAPTR 10 100 "U" "e2u+pstn:SIP"

"!(^.*)$!SIP:14085730000;tgrp=101@10.20.230.52:7004;user=phone!"

 Both LNP & routing:

$ORIGIN 1.0.0.0.3.7.5.8.0.4.1.e164.arpa.

IN NAPTR 10 100 "U" "e2u+pstn:SIP"

"!(^.*)$!SIP:14085730000;rn=25555555555;npdi=yes;tgrp=101@10.20.230.52:7004;user=phon

e!"

 Multiple trunk groups:

$ORIGIN 1.0.0.0.3.7.5.8.0.4.1.e164.arpa.

IN NAPTR 10 100 "U" "e2u+pstn:SIP"

"!(^.*)$!SIP:14085730000;tgrp=101@10.20.230.52:7004;user=phone!"

IN NAPTR 10 101 "U" "e2u+pstn:SIP"

"!(^.*)$!SIP:14085730000;tgrp=201@10.20.230.52:7004;user=phone!"

ControlSwitch (v.5.10.2) ENUM

 Dialogic Inc. Proprietary Page 7

Architecture 3.

The following diagram shows the architecture of the ENUM service working with the CS LSG element:.

The call flow of an ENUM service proceeds as follows:

1. CS receives an incoming call that requires an ENUM query.

2. The CS LSG element submits an ENUM query to an external ENUM server.

3. The ENUM server responds with one or more NAPTR records that contain the appropriate

information, for example the portability information for an ENUM LNP service.

4. Based on the received information, the CS handles the call.

ControlSwitch (v.5.10.2) ENUM

 Dialogic Inc. Proprietary Page 8

Configuration 4.

For ENUM configuration, refer to ControlSwitch Advanced Elements and Services User's Manual, section

ENUM Configuration.

ControlSwitch (v.5.10.2) ENUM

 Dialogic Inc. Proprietary Page 9

Call Flows 5.

5.1 Normal LNP

The following diagram shows a normal ENUM LNP service.

Figure 3: Normal LNP Flow

The call flow proceeds as follows:

1. CCP/ICE receives a call from the network.

2. SEE determines that an LNP query is required for the call.

3. SEE submits a query request to LSG.

4. LSG returns a dialog ID indication that contains a unique dialog ID created for this transaction.

5. LSG sends an ENUM/DNS request to the LNP server.

6. The LNP server returns the ENUM/DNS response that contains one or more NAPTR records.

7. LSG sends the query response containing data from the LNP server to SEE.

8. SEE sends a TcEndRequest to close the transaction with LSG.

9. SEE completes the LNP service and obtains the new ported number.

10. The call is sent to the network.

5.2 LNP Timeout

The following diagram depicts an ENUM LNP times out scenario.

ControlSwitch (v.5.10.2) ENUM

 Dialogic Inc. Proprietary Page 10

Figure 4: ENUM LNP Timeout Scenario

The call flow proceeds as follows:

1. CCP/ICE receives a call from the network.

2. SEE determines that an LNP query is required for the call.

3. SEE submits a query request to LSG.

4. LSG returns a dialog ID indication that contains a unique dialog ID created for this transaction.

5. LSG sends an ENUM/DNS request to the LNP server.

6. The LNP server does not respond within the configured time limit, and the query times out at LSG.

7. LSG retransmits the ENUM/DNS query to the LNP server.

8. The LNP server does not respond within the configured time limit, and the query times out at LSG.

9. LSG considers the transaction as failed (depending on the service node setting).

10. LSG sends an Abort Indication to SEE.

11. SEE sends TcEndRequest to close the pending transaction.

12. SEE considers the LNP query as failed.

13. The call may proceed without a ported number.

5.3 Normal LNP and Routing

The following diagram depicts a normal ENUM LNP and Routing service.

ControlSwitch (v.5.10.2) ENUM

 Dialogic Inc. Proprietary Page 11

Figure 5: Normal LNP and Routing Service

5.4 LNP and Routing Timeout

If the ENUM server does not respond, after a predefined time interval, LSG tries to retransmit N times

(according to the retransmit parameter) and upon not receiving an answer, it returns a failure message

to the SEE.

The following diagram depicts an ENUM LNP and Routing service timeout scenario.

ControlSwitch (v.5.10.2) ENUM

 Dialogic Inc. Proprietary Page 12

Figure 6: LNP and Routing Service Timeout

The table below shows all the combinations of answers from the ENUM server

Service trigger

npdi exist

rn and/or TG list exist

Comments

LNP

OK (the number was not ported)

Error

Routing

OK (no external routing decision)

Routing and LNP

OK (no external routing decision)

Error

ControlSwitch (v.5.10.2) ENUM

 Dialogic Inc. Proprietary Page 13

ENUM Tools in the CS 6.

6.1 CDRs

Calls that require an ENUM/DNS query will produce extra information in the CDRs that helps to identify

the query. To view this information, go to the CDR UI and open CDR.

1. Select CDR > General Tab to view the Event Order. In the sample below, the Event Order above

contains “Svc”, which indicates a service execution.

2. Select CDR > Location Tab to view the Called Party Number of the call.

3. Select CDR > Redirection Tab to view the ported number (shown in the Terminating LRN field).

4. Select CDR > Service Tab to view ingress information.

The Ingress SEE ID indicates the SEE that processed the service. The Ingress Service Field provided

details of the service that was executed:

 SVC ID indicates the service identification.

 ServiceNodeId identifies the service node used in the query.

 ServiceCategory indicates the type of service (in this case, LNP).

 TcapGatewayId identifies the LSG used for the query.

ControlSwitch (v.5.10.2) ENUM

 Dialogic Inc. Proprietary Page 14

6.2 Call Trace

The standard ControlSwitch System call trace feature has been expanded to display the ENUM/DNS

interactions with the ENUM LNP server.

The following screenshot shows an example of a standard call trace:

The next screenshot shows an example of a call trace from a DNS query. The DNS query trace shows the

query ID and query number.

The next screenshot shows an example of a DNS answer trace. The DNS answer trace shows the query

ID, queried number, and the answer section. The answer section contains the NAPTR record(s) with the

regular expression containing the ported number (rn=).

ControlSwitch (v.5.10.2) ENUM

 Dialogic Inc. Proprietary Page 15

6.3 Reports

The current LNP statistics reports now also show statistics for the ENUM LSG. There are two options for

LNP statistics reports:

 Standard Reports > Network Elements > LNP Statistics, which provides a report for all Service

Execution Elements (SEEs).

 Standard Reports > Network Elements > LNP Statistics per SEE, which provides a report for a

specific SEE.

Note:

LNP reports are cumulative. LNP queries are shown per SEE for all service node types the SEE maintains.

6.4 Alarms

The ENUM LSG raises the standard CPU overload alarm if the system becomes overloaded.

END of DOCUMENT

Dialogic ControlSwitch ENUM User guide

Dialogic ControlSwitch ENUM User guide

Dialogic ControlSwitch ENUM User guide

Related papers

Other documents