routengn by general telecom managed lcr routing user manual

8/14/2019 RouteNGN by General Telecom Managed LCR Routing User Manual

1/33

Managed LCR Routing User Manual

May 2009


2/33

Table of Contents

Overview....................................................................................................................................................4

Call Flow...............................................................................................................................................4

Redundancy...........................................................................................................................................7

Icons...........................................................................................................................................................9

Edit........................................................................................................................................................9Delete.....................................................................................................................................................9

Undo......................................................................................................................................................9Save.......................................................................................................................................................9

Add......................................................................................................................................................10

Rate .....................................................................................................................................................10Apply...................................................................................................................................................10

Carrier Setup............................................................................................................................................11

Carriers................................................................................................................................................11

Groups.................................................................................................................................................11Inbound Group................................................................................................................................11

NAME........................................................................................................................................11In/Out.........................................................................................................................................11Prefix..........................................................................................................................................12

Strip Digits.................................................................................................................................12

Margin........................................................................................................................................12Route Table Selection................................................................................................................12

Outbound Group.............................................................................................................................13

NAME........................................................................................................................................13In/Out.........................................................................................................................................13

Prefix..........................................................................................................................................14

Strip Digits.................................................................................................................................14

Margin........................................................................................................................................14Route Table Selection................................................................................................................14

End Points............................................................................................................................................14

Regions.....................................................................................................................................................15Adding Dial Codes Manually..............................................................................................................15

Importing Dial Codes .........................................................................................................................16

Rates.........................................................................................................................................................18..................................................................................................................................................................19

Routes.......................................................................................................................................................20

Route Tables........................................................................................................................................21

.............................................................................................................................................................21

LCR Route Tables...............................................................................................................................22Domestic Route Tables........................................................................................................................22

Generating LCR..................................................................................................................................22Changing Route Priorities...................................................................................................................22

Changing Rates....................................................................................................................................22

Search..................................................................................................................................................23Route Table Download........................................................................................................................23

Trouble Shooting......................................................................................................................................24

Call Logs.............................................................................................................................................25


3/33

Sample Call Log.............................................................................................................................25

Appendix A: S3 Managed LCR Routing Configuration Guide...............................................................28

Introduction:.............................................................................................................................................28

Managed LCR Routing Endpoint Configuration....................................................................................28


4/33


5/33

A sample call flow:

CONFIDENTIALSourceComm

Page 5


6/33

A sample ladder diagram:


Page 6

Managed LCRRoutingSBC

TerminationEndpointOrigination


7/33

Redundancy

The Managed LCR Routingis configured in a 1+1 configuration. Upon the initiation of the service,

users are provided with a DNS address as well as a primary and secondary signaling IP addresses.Ideally, users should configure their SIP Device(s) to signal to the DNS address. If users SIP Device(s)

are not capable of routing to a DNS address, use the IP addresses. All updates to the system will

propagate to both the primary and secondary servers after changes are Applied. (see 'Apply' below).

Many times the updates will take effect on both servers within sixty seconds of applying them. On rareoccasions, it can take up to 10 minutes for changes to propagate across the network.


Page 7


8/33

An overview of call flow with both primary and secondary clusters configured:


Page 8


9/33

Icons

The Managed LCR Routingweb interface was designed to be as streamlined as possible. Our designers

have taken great care to minimize superfluous buttons and keep a consistent look and feel throughout

the system. There are a few icons that users should become familiar with.

Edit

The edit icon appears in almost all the screens in the Managed LCR Routinginterface. It will allowusers to change the properties of an element in the system. The edit icon is always located within the

element that it affects.

Delete

The Delete icon will permanently remove elements in the system. It will also remove all associations

to that element. For example if a user deletes a Region it will also delete the Locale and all associatedDial Codes. The Delete feature will always ask the user if he or she is certain they wish to perform thisaction.

Undo

The Undo icon allows the user to exit the edit window without saving changes.

Save


Page 9


10/33

The Save icon saves any changes the user has made in the edit window.

Add

The Add button allows the user to add an additional element to the data window it refers to. It isclicked after the information is added into the text box located next to it.

Rate

The Rate button allows the user to check how many of each rate type is associated with a Carrier or

Carrier Group.

Apply

Any changes made to the system will not take affect until you press the apply button. As soon asusers add, remove or make a change to an element or change routing, the Apply button will begin

to slowly blink as a reminder that changes have yet to take affect on the active servers. Users not

need to press the Apply button after every change but only once he or she is ready for the changes

to take affect. Please note that changes will be stored in the system and can be applied at a later

time even if the user logs out and/or closes his or her browser.


Page 10


11/33

Carrier Setup

Carriers

The Carrier setup page can be found by navigating to [TABLES-->CARRIERS]. Carriers are definedas the customers and vendors that the end user is peered with. Carriers can be broken out to Groups

and Groups can have within them multiple End Points (SIP Peers). Each of these items is broken out

into individual data windows. The data windows should always be reference from left to right.

Start by entering a Carrier name in the text box labeled 'New Carrier' at the bottom of the Carrier data

window and pressing ENTER or clicking on the Add icon. When clicking on the Carrier listed in theCarrier data window, the user will see a text box labeled 'New Group' below the Groups data window.

Groups

Groups are found in center data window on the Carrier setup page [TABLES-->CARRIERS]. Carriers

have a one to many relationship with Groups and all routing is done on the Group level. Groups aredefined as the features associated with an End Point or End Points (SIP Peers).

Enter a Group name in the text box labeled 'New Group' at the bottom of the Group data window andpressing ENTER or clicking on the Add icon.

Inbound Group

Inbound Groups are set up for traffic coming to the Managed LCR Routing. Users can set the

properties of a Group by clicking on the Edit next to the Group name.

NAME

The top field in in an inbound group is for Carrier Group Name

In/Out

To the right of the name, users have the option to define a Group as inbound (traffic FROM customers)

or outbound (traffic TO vendors). For inbound Groups, select IN.


Page 11


12/33

Prefix

The field below the name field is for any inbound Prefix the user may be expecting. Prefixes may be

up to 10 digits long and ALWAYS end with a pound (#) sign. The system will automatically strip thesedigits before routing the call.

Strip Digits

Below the prefix field is the Strip Digits field. It will strip the pattern specified in this field.

Example, for the call 91-11-4365211:

Strip Digits field is set to 9111 the call will get routed as '4365211'.

Margin

Below the strip digits field is the Margin field. This represents the minimum margin required for aGroup. It is defaulted at 0, which implies that the user will not route any calls for a loss. If the marginfield is set at '10' the minimum margin for any route returned will be 10%. Setting this field to -100

disables any margin calculation.

Route Table Selection

Below the Margin field is the Route Table menu. This pull-down list will contain all configured Route

Tables [see the Route Table Section below on how to create and configure Route Tables]. Inbound

Groups will route traffic according to the priorities set in the associated Route Table.


Page 12


13/33

Outbound Group

Outbound Groups are set up for traffic sent out from the Managed LCR Routing. Users can set the

properties of a Group by clicking on the Edit next to the Group name.

NAME

The top field in in an outbound group is for Carrier Group Name

In/Out

To the right of the name, users have the option to define a Group as inbound (traffic FROM customers)

or outbound (traffic TO vendors). For inbound Groups, select OUT.


Page 13


14/33

Prefix

Users may add an outbound Prefix of up to 10 digits in this field. The Prefix will be pre-pended to the

beginning of the dialed number before it is sent out to the Group it is associated with.

Strip Digits

This field is not used for outbound groups

Margin

This field is not used for outbound groups.

Route Table Selection

This field is not used for outbound groups.

End Points

End Points are found in right-most data window on the Carrier setup page [TABLES-->CARRIERS].Groups have a one to many relationship with End Points. End Points are SIP Peers.

Enter an IP address in the the text box labeled 'New Carrier' at the bottom of the Carrier data window

and pressing ENTER or clicking on the Add icon. Add all the IP addresses which are to be included in

the carrier Group. Note Some Soft Switches also allow TDM Trunk Group names to be defined here.


Page 14


15/33

Regions

The Carrier setup page can be found by clicking on [TABLES-->REGIONS]. The Regions table is themaster dial code table within the Managed LCR Routing. Regions have a one to many relationship

with Locales, and Locales have a one to many relationship with Dial Codes. All routing is controlled

on the Locale level.

Regions, Locales and Dial Codes may be added manually or via the Import function.

Adding Dial Codes Manually

Start by entering a Region name in the text box labeled 'New Region' at the bottom of the Regions data

window and pressing ENTER or clicking on the Add icon. When the region listed in the Region datawindow, click on it and you should see a text box labeled 'New Locale' below the Groups data window.

To add a Dial Code for a Locale, click on the Locale and populate the New Dial Code text box belowthe Dial Code data window.


Page 15


16/33

Importing Dial Codes

Importing codes is the fastest way to define large amounts of Regions and Locales in the Managed

LCR Routing. The file should be in CSV (Comma Separated Value) format and should have thefollowing layout.

Region,Locale,Dial Code

Example:

NY,MANHATTAN,1212

INDIA,MOBILE,9198


Page 16


17/33

INDIA,,91

Please note that header rows should not be included in the import format.

To import a file, click on the UPLOAD link [TABLES-->UPLOAD] from anywhere in the TABLES

menu. A modal will drop down. Click on the REGIONS button. Then click Browse to search theusers computer or network drives for the Regions file you wish to upload. Once the user has selected

the proper file, click upload. Users will see a success message once the operation is complete. Any

errors in the upload will output to a file that users have the option of downloading.


Page 17


18/33

Rates

Customer and supplier rates are uploaded into the system in the same manner. The uploaded file

should be in CSV (Comma Separated Value) format and should have the following layout.

Dial Code,Rate

Example:

1212,0.0125

9198,0.10

91,0.065

Please note that header rows should not be included in the import format. The database can import and

store rates to the 1/10,000th of a cent though the interface will only give detail of up to 1/100th of a cent.


Page 18


19/33

To import a file, click on the UPLOAD link [TABLES-->UPLOAD] from anywhere in the TABLES

menu. A modal will drop down. Click on the RATES button. Click on the Carrier and then select theGroup or Groups you wish to apply the rates to. Next, click on the type of rate to be uploaded (LCR,Inter-State, Intra-State, or Undefined). Then click Browse to search your computer or network drives

for the Rates file to be upload. Select the proper file, click upload. Users will receive a success

message once the operation is complete. Any errors in the upload will output to a file that users havethe option of downloading.


Page 19


20/33

Routes

Routes are broken up into two categories, LCR and Domestic Routing. LCR (B-Number Only) routing

takes does not take the Region into consideration when determining how to route a call. Domestic

Routing (Jurisdictional) takes both the Region and Locale into consideration when routing.

Managed LCR Routinguses the following order to set route order:


Page 20


21/33

Route Tables

The system allows users to add multiple Route Tables. To add a Route Table, enter the name of thetable to be added in the text box directly beneath the type of table you wish to add. The top row is for

LCR tables and the bottom row is for Domestic tables. When finished press [ENTER] and it will

automatically open that table.


Page 21


22/33

LCR Route Tables

LCR routes are typically used for international call routing or flat rate domestic routes. Calls that useLCR tables will be routed using the dialed number only. Dial Codes will always be matched on the

most discreet breakout within a Route Table.

Domestic Route Tables

Domestic Route tables are typically used for Jurisdictional or Inter/Intra state routing. Domestic Route

Tables are broken out into three sub-tables. Inter-State, Intra-State, and Undefined. Calls that arerouted using Domestic Routing will first seek to determine if the ANI (A-Number) and the DNIS (B-

Number) are in the same Region. If they are it is considered Intra-State. If they are not it is considered

Inter-State. If it cannot be determined, as in internationally originated traffic for example, it is

considered Undefined.

Generating LCR

New tables are created without any routing built. The system will generate routing using the carriersspecified by the user and will automatically sort route choices in ascending rate order. Routing is

generated by clicking on the Update LCR button located on the tool bar on the upper right-hand corner

of the interface which will cause a modal to drop down. Select the Outbound Groups to be included in

this table. Click Apply. When the success message appears, exit out of the modal. To view thechanges go to the main Routes menu and back into the table. Any time the Generate LCR function is

used it will update routing priorities for the entire table or sub-table.

Changing Route Priorities

In the Route Table Screen, route priorities are listed in descending order from left to right. The route

closest to the Region/Locale has the highest priority for those set of codes on that Route Table. Tochange the priority order of a route, click on a route and drag it to the right or left and drop it in the

location desired.

Changing Rates

To change a rate manually, click on the edit icon in the routes page of the rate to be modified. This will

open a call out box where uses can edit the rate of the destination. Editing a rate in the routes screen

will modify the rate wherever it is used in the system.


Page 22


23/33

Search

Regions, Locals or Dial Codes may be searched for in a Route Table. The search window is located onthe left hand side of the tool bar. Select Region, Locale or Dial Code in the pull down list and type

what is being searched for in the search window. The system will begin searching as soon as

something is typed into the window. There is no need to press [ENTER].

Route Table Download

To download a copy of the route table, click on the downward facing arrow located to the left of the

Update LCR button in the tool bar.


Page 23


24/33

Trouble Shooting

To search for a Call Log in the system, navigate to [HOME]-->[RECORDS]. Enter the complete dialed

number of the call to search. The system stores calls for six hours.


Page 24


25/33

Call Logs

Sample Call Log

received:

INVITE sip:3000#[email protected] SIP/2.0

Max-Forwards: 69

Session-Expires: 3600;refresher=uacSupported: timer

To:

From: "TEST" ;tag=as3d95add9Contact:

Call-ID: [email protected]

CSeq: 1 INVITEVia: SIP/2.0/UDP 69.24.128.244:5060;branch=z9hG4bK121cdf9872e58ed9a88b5bac81fb8fa4

Content-Type: application/sdp

Content-Length: 273v=0

o=Nextone-MSW 19458 19458 IN IP4 69.24.128.244

s=sip call

c=IN IP4 69.24.128.247t=0 0

m=audio 33854 RTP/AVP 18 101

a=sendrecva=ptime:20

a=silenceSupp:off - - - -

a=fmtp:101 0-16a=rtpmap:101 telephone-event/8000

a=fmtp:18 annexb=no

a=rtpmap:18 G729/8000

detail:

Setting account by source IP:69.24.128.244

Selecting routing module

Source IP: 69.24.128.244

Dialed Digits: 19565463646Prefix: 3000#

Creating new routing module

Setting up queryUsing prefix and source IP to determine instance

Making instance query


Page 25


26/33

strip_digits is: 1

src epg: 35

strip_digits is not nullGot strip_digits:1

start of dialed number 19565463646 matches strip digits 1

dialed number is now: 9565463646Got append digit data null , null , null

Using II

Got instance: 1ANI: 8665160115

DN: 9565463646

Making route query

type is: undefGot customer rate: 0.0059

Setting up query

Making route queryUsing best digit match routing

Matched digits: 956546

Using profit thresholdMargin: 5

Customer rate: 0.0059

Supplier rate: 0.0051

Calculated margin: 13.559322033898297Margin threshold met - appending route: 208.80.156.52


Using profit thresholdMargin: 5


Supplier rate: 0.0054Calculated margin: 8.474576271186434

Margin threshold met - appending route: 208.85.248.40

Matched digits: 956546Using profit threshold

Margin: 5


Supplier rate: 0.0062Calculated margin: -5.084745762711863

Margin threshold failed - route: 66.234.182.43

Matched digits: 956546Using profit threshold

Margin: 5



Page 26


27/33


Calculated margin: -10.169491525423727

Margin threshold failed - route: 208.79.53.200Matched digits: 956546

Using profit threshold

Margin: 5Customer rate: 0.0059


Calculated margin: -16.949152542372882Margin threshold failed - route: 216.193.203.110


Using profit threshold

Margin: 5Sending reply from ip: cpxx. sourcecomm.net

sent:

SIP/2.0 300 Redirect

To: ;tag=1994752474From: "TEST" ;tag=as3d95add9

Call-ID: [email protected]

CSeq: 1 INVITEVia: SIP/2.0/UDP 69.24.128.244:5060;branch=z9hG4bK121cdf9872e58ed9a88b5bac81fb8fa4

Contact: sip:[email protected], sip:[email protected]


Page 27


28/33

Appendix A: S3 Managed LCR Routing Configuration Guide

Introduction:

This document illustrates the procedures needed to configure the SourceComm Managed LCR Routing

using Full Qualified Domain Name (FQDN) in conjunction with the NexTone Session Border

Controller (SBC). The How-To assumes that DNS has been set up and SBC can PING the Managed

LCR Routing via the FQDN address.

Managed LCR Routing Endpoint Configuration

From the tool bar select: EDIT > ADD > Endpoint


Page 28


29/33

From the Device Type select Softswitch

Enter a name for the Managed LCR Routingin the Registration ID: field

Port Number will automatically populate with zero

Enter the IP Address of the Managed LCR Routing

Select a Calling Plan

Select the Realm on which the Managed LCR Routingresides

Select IEdge Group

Select the Advanced tab.

Check the Domain Match Flag


Page 29


30/33

Select the Protocol tab.

In the Protocol tab confirm that only the SIP radio button is checked. Then click on the SIP Configurebutton.


Page 30


31/33

Enter the FQDN, given to by SourceComm, in the Contact: field

Check the FQDN redundancy radio button

Select the OKbutton to go back to the Protocol tab.

Select the Calls tab


Page 31


32/33

CheckUnlimited for all three CAC setting.

Confirm that all three the radio buttons are unchecked forMedia control


Page 32


33/33

Select the OKbutton to save the endpoint. The Managed LCR Routingend point is now configured for

redundancy.

routengn by general telecom managed lcr routing user manual

Documents