Dialogic ControlSwitch LSG User guide

Brand: Dialogic

Model: ControlSwitch LSG

Type: User guide

Dialogic® ControlSwitch™ SIP

Local Number Portability (LNP)

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

July 2009

Initial Release

June 2009

Comments Incorporated

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) SIP Local Number Portability

 Dialogic Inc. Proprietary Page 3

Table of Contents

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

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

1.2 System Architecture .................................................................................................................................... 4

SIP LNP SERVER INTERACTION ...................................................................................................................... 6 2.

2.1 Request to LNP Server ................................................................................................................................. 6

2.2 Possible response formats .......................................................................................................................... 6

Format 1.................................................................................................................................................. 6 2.2.1

Format 2.................................................................................................................................................. 7 2.2.2

Format 3.................................................................................................................................................. 7 2.2.3

Format 4.................................................................................................................................................. 7 2.2.4

2.3 No Response from the LNP Server .............................................................................................................. 8

2.4 Possible Response Formats ......................................................................................................................... 8

LSG CALL FLOW ............................................................................................................................................ 10 3.

CDR INFORMATION ..................................................................................................................................... 11 4.

4.1 Call Tracing and Routing Dips .................................................................................................................... 11

ALARMS AND REPORTS ............................................................................................................................... 12 5.

5.1 Alarms ....................................................................................................................................................... 12

5.2 Reports ...................................................................................................................................................... 12

ControlSwitch (v.5.10.2) SIP Local Number Portability

 Dialogic Inc. Proprietary Page 4

Introduction 1.

1.1 Overview

Local Number Portability (LNP) is deployed world-wide, allowing the end-users to keep their existing

phone number if they either move or switch carriers. This involves storing of the Network Routing

Number (NRN) that is a different number from the user’s directory number (DN) in the SCP. When a

switch (this could be an originating, transit, or a terminating switch) determines that a number is

ported, it attempts to retrieve the NRN for the DN. NRN is used to route the call towards the correct

destination. One way of doing this is to query an SCP (SN) by using the SIP protocol – a simple

transaction with an INVITE to the SN results in a 3xx redirection with the LNP information. The LSG (CS

element) provides a SIP transaction-based interface, for querying the SIP service nodes (SN), in IP

network.

For SIP LNP configuration, refer to ControlSwitch Advanced Elements and Services User's Manual,

section SIP LNP Configuration.

1.2 System Architecture

The LNP Signaling Gateway (LSG) is an integral component of the CS, used when an external SIP SN

needs to be queried.

The SIP LNP solution involves the following elements:

 Call Processing Element (CCE). IP/TDM Call Processing element.

 Service Execution Element (SEE). After dipping with the Policy Engine (PE), the SEE interacts

with the LSG that queries the SCP.

 Policy Engine (PE). Provides the service trigger information for identifying whether or not there

is a need for SIP-based SCP interaction.

 LNP SIP Gateway (LSG): Communicates the transaction messages between the CS and SCP.

 SIP LNP Server: External SCP which provides SIP interface to access LNP database.

 EMS: EMS manages all the elements of the CS. It provisions the PE with routing information

and other necessary mappings required within the system and allows the dynamic provisioning

of the service nodes.

LSG interacts with SEE for providing the LNP information and with EMS for management purposes.

When an incoming call is forwarded to the PE for route determination, if the PE finds that the called

party belongs to a ported number range and that is being served by a SIP SN, it instructs the SEE to

make the LNP dip. SEE sends the request to the LSG which interacts with the SN and obtains the LNP

information. The call processing continues with the new information.

The following figure depicts the system architecture.

ControlSwitch (v.5.10.2) SIP Local Number Portability

 Dialogic Inc. Proprietary Page 5

Figure 1: System Architecture

ControlSwitch (v.5.10.2) SIP Local Number Portability

 Dialogic Inc. Proprietary Page 6

SIP LNP Server Interaction 2.

Figure 2: SIP Communication between CS and the SIP Server

2.1 Request to LNP Server

INVITE sip:[email protected]:5061;user=phone SIP/2.0

Call-ID: [email protected]

From: <sip:[email protected]:3560;user=phone>;tag=30705

To: <sip:[email protected]:5061;user=phone>

CSeq: 1 INVITE

Via: SIP/2.0/UDP 10.5.30.239:3560;branch=z9hG4bK-600000006-a051eef-7

Contact: sip:54321001@10.5.30.239:3560

Supported: timer,100rel

Max-Forwards: 70

2.2 Possible response formats

CS supports the following formats of ‘301/302’ response messages.

Format 1 2.2.1

Case: ‘sip:’ url SCP Dip done and Number ported:

SIP/2.0 301 Moved Permanently /302 Moved Temporarily

Via: SIP/2.0/UDP 10.5.30.239:3560;branch=z9hG4bK-600000006-a051eef-7

From: <sip:[email protected]:3560;user=phone>;tag=30705

To: <sip:[email protected]:5061;user=phone>;tag=583330932

Call-ID: 25769803782-1[email protected]

CSeq: 1 INVITE

Contact: <sip: 54321001;rn=1408987654;[email protected]:9090;user=phone>

Content-Length: 0

 Ported number should be presented in “rn=” parameter.

 CS Supports both formats for npdi ie. “npdi=yes” or npdi

 For ‘sip:’ url rn and npdi should be present in User part

ControlSwitch (v.5.10.2) SIP Local Number Portability

 Dialogic Inc. Proprietary Page 7

Format 2

2.2.2

Case: ‘tel url’ SCP Dip done and Number ported:

SIP/2.0 301 Moved Permanently/302 Moved Temporarily

Via: SIP/2.0/UDP 10.5.20.87:3020;branch=z9hG4bK-400000004-a051457-5

From: <sip:[email protected]:3020;user=phone>;tag=8684

To: <sip:[email protected]:9090;user=phone>;tag=4

Call-ID: 17179869188-[email protected]

CSeq: 1 INVITE

Contact: <tel:+14088888888;rn=14089876543; npdi>

Content-Length: 0

The following flow shows SEE interaction where the service node does not have ported information for

the ported called number.

Figure 3: SIP Communication between CS and the SIP Server (number not ported)

Format 3 2.2.3

Case: SCP Dip done and Number not ported: (npdi, no rn)

SIP/2.0 301 Moved Permanently /302 Moved Temporarily

Via: SIP/2.0/UDP 10.5.30.239:3560;branch=z9hG4bK-600000006-a051eef-7

From: <sip:[email protected]:3560;user=phone>;tag=30705

To: <sip:[email protected]:5061;user=phone>;tag=583330932

Call-ID: [email protected]

CSeq: 1 INVITE

Contact: <sip: 54321001;[email protected]:9090;user=phone>

Content-Length: 0

Format 4 2.2.4

Case: SCP Dip done and Number not found

SIP/2.0 404 Not Found

Via: SIP/2.0/UDP 10.5.20.87:3020;branch=z9hG4bK-500000005-a051457-6

From: <sip:[email protected]:3020;user=phone>;tag=8550

To: <sip:[email protected]:9090;user=phone>;tag=1

Call-ID: 21474836485-[email protected]

CSeq: 1 INVITE

Content-Length: 0

ControlSwitch (v.5.10.2) SIP Local Number Portability

 Dialogic Inc. Proprietary Page 8

2.3 No Response from the LNP Server

The following shows the SEE interaction when SEE terminates the transaction early/SCP

unreachable/SCP response not received.

Figure 4: SIP Communication between the CS and the SIP Sever (no response)

2.4 Possible Response Formats

RSIP Response

npdi

Use Case

Msg to SEE

Destination Routing Addr

3xx

present

Number ported

Connect

“rn” as received in contact hdr

of 3xx (Format 1/ Format 2

present

absent

Number not ported

Connect/Release

(Note1)

“user” field of UserPart from the

contact header (Format 3)

absent

present

Other services (such

as free phone)

Connect

“rn” as received in contact hdr

of 3xx

absent

Other services as

(such as free phone)

Connect

“user” field of UserPart from the

contact header

404

Number not ported

Connect/

Release

(Note1)

Set it to same number as

received in the InitialDP request

(Called Party Number) (Format

4xx, 5xx, 2xx

Error

Abort

None

6xx

Error

Connect

Set it to same number as

received in the InitialDP request

(Called Party Number)

Internal Error

Error

Abort

None

Basic Call Flow:

ControlSwitch (v.5.10.2) SIP Local Number Portability

 Dialogic Inc. Proprietary Page 9

Figure 5: Message Flow

1. Call Ingress in CS through IP/TDM network

2. CCE sends Call Info to SEE

3. SEE dips to PE to find out Services associated with Incoming Call

4. PE based on Trunk Group (TG) Service Trigger plan executes policies associated with Incoming call,

identifies whether or not there is need of SIP based SCP Interaction and send response back with

LSG details to SEE.

5. SEE applies DA rule to called number if applicable and sends Incoming call Info to LNP.

6. LNP sends SIP INVITE message with Incoming call information to SCP

7. If number is ported then SCP sends ‘301/302’ response with rn and npdi parameters.

8. LSG passes routing number to SEE.

9. SEE sends Routing number, Original Called Party Number to PE.

10. PE does Post processing, applies policies based on New routing number sends back final Egress TG

list to SEE. Original Called Party Number is copied into GAP parameter.

11. SEE updates Forward Indicator based on SCP response and sends call to outgoing CCE

12. CCE sends call out on IP/TDM network.

ControlSwitch (v.5.10.2) SIP Local Number Portability

 Dialogic Inc. Proprietary Page 10

LSG Call Flow 3.

Figure 6: Call Flow

ControlSwitch (v.5.10.2) SIP Local Number Portability

 Dialogic Inc. Proprietary Page 11

CDR Information 4.

CS records the LNP events in CDR. If the dip succeeds, CS receives ‘301/302’ message with RN and NPDI,

and records following information:

<SVC ID="32" SUCC="1" ServiceNodeId="5" ServiceCategory="LNP"

TcapGatewayId="691"><Time>2010-10-19+01:23:38.023</Time>

If the operation fails the following information is recorded:

<SVC ID="32" SUCC="0" ServiceNodeId="5" ServiceCategory="LNP"

TcapGatewayId="691"><Time>2010-10-19+01:23:38.023</Time>

The following scenarios list the unsuccessful dip caes:

 If Veraz CS receives 4xx/5xx/6xx message for INVITE

 INVITE request time out

 Veraz CS could not reach to SCP

4.1 Call Tracing and Routing Dips

When a call has been triggered for tracing and it involves routing dips, all messages that are required

are viewable by the operator. The following messages are traced:

 The routing dip request sent by SEE

 The SIP request sent out by LNP SIP Gateway

 The SIP responses or timeout in the LNP SIP Gateway

 The routing dip response received by SEE

LSG sends the following messages/information in the trace messages:

 The Service Node ID to which the SIP request is being sent to

 The content of SIP requests and responses

ControlSwitch (v.5.10.2) SIP Local Number Portability

 Dialogic Inc. Proprietary Page 12

Alarms and Reports 5.

5.1 Alarms

LSG supports the following alarms:

 General Life cycle (Stat up, Shutdown, Disable) alarms related to CS element

 CPU overload alarm

 Process related alarms: Queue delay

5.2 Reports

The reports are available on daily or hourly basis for the SIP LNP service.

 Number of Calls Requiring LNP dips

 Number of Ported Calls. SCP returned a positive response with the new RN.

 Total Dips. Total number of attempts made (some attempts may be failures, some calls may

have done multiple dips).

END of DOCUMENT

Dialogic ControlSwitch LSG User guide

Dialogic ControlSwitch LSG User guide

Dialogic ControlSwitch LSG User guide

Related papers

Other documents