project about route ngn user manoul by alireza navabi teacher: mr ali esmaeili

7/30/2019 project about route NGN user manoul by alireza navabi teacher: Mr Ali Esmaeili

1/47

RouteNGNUser Manual

April 2012

Collection of : Alireza Navabi

Teacher's Guide : Mr Ali Esmaeili

Folad University of Technology


2/47

2012 - IceHook Systems

Page 2

Contents

Overview ................................................................................................................................................... 4Call Flow ............................................................................................................................................... 4Redundancy ........................................................................................................................................... 7SIP Options Ping ................................................................................................................................... 7

Icons .......................................................................................................................................................... 9Edit ........................................................................................................................................................ 9Delete .................................................................................................................................................... 9Undo ...................................................................................................................................................... 9Save ....................................................................................................................................................... 9Add ...................................................................................................................................................... 10Rate ..................................................................................................................................................... 10Apply ................................................................................................................................................... 10

Global Settings ......................................................................................................................................... 11Login .................................................................................................................................................... 11Email .................................................................................................................................................... 11Password.............................................................................................................................................. 11Company .............................................................................................................................................. 11Failure Code ......................................................................................................................................... 11Redirect Code ....................................................................................................................................... 11TG Tag ................................................................................................................................................. 11TG Tag Format ..................................................................................................................................... 11Profit Threshold .................................................................................................................................. 12Inline Contact ...................................................................................................................................... 12

Carrier Setup ........................................................................................................................................... 13Carriers ................................................................................................................................................ 13Groups ................................................................................................................................................. 13

Inbound Group ................................................................................................................................ 14Outbound Group ............................................................................................................................. 16

Time of Day / Day of Week Routing .................................................................................................... 17End Points ........................................................................................................................................... 17


3/47


Page 3

Regions................................................................................................................................................ 17Adding Dial Codes Manually ............................................................................................................. 18Importing Dial Codes .......................................................................................................................... 19

Rates ........................................................................................................................................................ 20Route Tables ........................................................................................................................................ 23Domestic Route Tables ....................................................................................................................... 23Generating LCR .................................................................................................................................. 24Changing Route Priorities ................................................................................................................... 24Block Vendor ....................................................................................................................................... 24Changing Rates ................................................................................................................................... 24Search .................................................................................................................................................. 25Allocation Routing .............................................................................................................................. 25Region Override .................................................................................................................................. 26Route Table Download ........................................................................................................................ 28

Trouble Shooting Call Logs ................................................................................................................. 28Sample Call Log.............................................................................................................................. 30

Trouble Shooting Call Reports ............................................................................................................. 35Appendix A: Genband S3 4.0c3-xx RouteNGNConfiguration Guide ................................................... 37

Introduction ......................................................................................................................................... 37RouteNGN Endpoint Configuration ................................................................................................... 37Appendix B: Genband S3 v4.3m7 RouteNGNConfiguration Guide: ................................................ 43Introduction: ........................................................................................................................................ 43RouteNGN GUI Endpoint Configuration ........................................................................................... 43Global Configure CLI for H.323 End Point ........................................................................................ 47


4/47


Page 4

Overview

The RouteNGNis a high capacity, carrier grade, flexible routing platform. It was designed and built to

augment the routing capabilities of SIP compatible devices (SIP Devices). It is a stateless system and

therefore does not and does not generate CDRs or limit concurrent sessions.

Call Flow

While it can be deployed in a variety of locations in a network, it is recommended that the RouteNGNis located behind an SBC or Soft Switch.

In most cases users configure their SIP Devices with very basic routing. The primary role the SIP

Device plays in routing will be to identify the customer sending the traffic. One method of

accomplishing this is via tech-prefixing (this will be covered in detail in the Carrier Groups section).

The RouteNGNprovides routing instructions to SIP Devices via a 300 Redirect message and is capable

of sending multiple route choices in a single redirect message.


5/47


Page 5

Figure 1 - Sample Call Flow


6/47


Page 6

Figure 2 - Sample Ladder Diagram


7/47


Page 7

Redundancy

The RouteNGNis 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, usersshould 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 toboth the primary and secondary servers after changes are Applied. (see 'Apply' below). Many times the

updates will take effect on the servers within sixty seconds of applying them. On rare occasions, it can

take up to 10 minutes for changes to propagate across the network.

SIP Options Ping

The RouteNGN supports a SIP OPTIONS ping, sometimes referred to as a SIP Heartbeat. If the

RouteNGN receives a SIP OPTIONS from a known device, it will respond with a 200 OK message if itis functioning normally.


8/47


Page 8

Figure 3 - An overview of call flow with both primary and secondary clusters configured


9/47

2012 - IceHook SystemsPage 9

Icons

The RouteNGNweb 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 RouteNGNinterface. It will allow users to change

the properties of an element in the system. The edit icon is always located within the element that itaffects.

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 this

action.

Undo

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

Save

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


10/47


Add

The Add button allows the user to add an additional element to the data window it refers to. It is

clicked 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 orCarrier Group.

Apply

Any changes made to the system will not take effect until you press the apply button. As soon as

users 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 effect 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 changesto take effect. 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.


11/47


Page 11

Global Settings

To view the Global Settings navigate to [HOMEDASHBOARD]. Click EDIT on the right hand sideto modify these settings.

Login

Modify the GUI username here.

Email

Modify users email here.

Password

Modify GUI password here. Note that you will have to also enter the identical information in the

Confirm Password field.

Company

Modify company name here.

Failure Code

Global setting for the call failure code. Default is 503 Not Found. This may be configured to any SIPvalue greater than 4xx. Note you must populate the field with a number followed by any text. For

example: 503 Not Found.

Redirect Code

Global setting for the redirect code. Default is 300 Redirect. This may be modified to a 302 Redirector any other redirect code that may work for the signaling SIP device. Consult your SIP device

manufacturer for proper format. Note you must populate the field with a number followed by any text.

For example: 302 Redirect.

TG Tag

Setting for outbound or destination trunk group tag. Many plat forms support TGRP or DTG. Incertain instance it may be case sensitive. Consult your SIP device manufacturer for proper format.

TG Tag Format

TG tag Formats sets the placement for the trunk group tag in the redirect message contact header. The

two choices are as follows:


12/47


Page 12

DN@IP;dtg=XXXXDN,dtg=XXXX@IP

Where:

DN = Destination Number

IP = IP address or Fully Qualified Domain Namedtg = Destination Trunk Group Indicator Note this will be in the format indicated in

the TG Tag field

XXXX = The Destination Trunk Group Tag as defined in the outbound EndPoint Group

Profit Threshold

Enables or disables Profit Threshold Routing.

Inline ContactThe Contact Header in the redirect message may be formatted in two ways.

Inline:

Contact:

Contact: Contact:

Multi:

Contact: sip:DN@IP1, DN@IP2, DN@IP3

Where:

DN = Destination Number

IPx = IP address or Fully Qualified Domain Name and x = route choice


13/47


Page 13

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 the

Carrier 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]. Carriershave a one-to-many relationship with Groups and all routing is done on the Group level. Groups are

defined 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 and

pressing ENTER or clicking on the Add icon.


14/47


Figure 4 - Configuring an inbound End Point Group

Inbound Group

Inbound Groups are set up for traffic coming to the RouteNGN. 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.

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 which will be automatically stripped by

the RouteNGN before routing the call. Prefixing the DN is one option that can be used to select a LCRor Domestic routing table.

Strip Digits

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


15/47


16/47


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]. InboundGroups will route traffic according to the priorities set in the associated Route Table.

Outbound Group

Outbound Groups are set up for traffic sent out from the RouteNGN. Users can set the properties of aGroup by clicking on the Edit next to the Group name.

NAME

The top field 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 outbound Groups, select OUT.

Figure 5 - Configuring an outbound End Point Group


17/47


Page 17

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.

DN Strip Digits

This field is will strip from the DN the pattern specified. If a the Prefix filed is populated the digitsbeing stripped will be after the prefix.

Trunk Group

Below the Strip Digits field is the Trunk Group field. By populating this field the RouteNGN will

insert a destination trunk group in the 300 redirect message contact header using the following the

defined TG format [see Global Settings section]..

Time of Day / Day of Week Routing

Time of day or day of week routing may be implemented by clicking on the radial button and

indicating the times and/or days when the End Point Group should be taking calls.

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 text box labeled 'New Carrier' at the bottom of the Carrier data window and

press ENTER or click on the Add icon. Add all the IP addresses which are to be included in the carrierGroup.

Dynamic Vendor IP

Using an IP address 0.0.0.0 for the vendor IP will cause the RouteNGN to automatically populate the IP

address as the Inbound Group IP. This is useful if the same vendor is used on two different Inbound

SIP devices.

Multiple Endpoints

All traffic is split evenly between Endpoints. For example if there are two different endpoints

configured for an endpoint group (End Point A and End Point B), 50% of the time End Point A willhave a higher priority and 50% of the time End Point B will have a higher priority. Therefore to split

the traffic in a different manner, users may enter the same End Point multiple times.

Regions

The Carrier setup page can be found by clicking on [TABLES-->REGIONS]. The Regions table is the


18/47


Page 18

master dial code table within the RouteNGN. 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 below

the Dial Code data window.


19/47


Importing Dial Codes

Importing codes is the fastest way to define large amounts of Regions and Locales in the RouteNGN.The file should be in CSV (Comma Separated Value) format and should have the following layout.

Region,Locale,Dial Code

Example:

NY,MANHATTAN,1212

INDIA,MOBILE,9198

Figure 6 - Regions, Locals and Dial Codes


20/47


Page 20

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.

RatesCustomer 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.


21/47


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 successmessage once the operation is complete. Any errors in the upload will output to a file that users have

the option of downloading.

Figure 7 - Importing Rates


22/47


Page 22

Routes

Routes are broken up into two categories, LCR and Domestic Routing. LCR (B-Number Only) routingtakes 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.

Routing is broken out into two categories: Best Match and Best Rate:

Best Match

RouteNGNuses the following order to set route order for Best Match Routing:

1. Best Code Match*} Profit Threshold Met?

2. End Point Group Priority*NOTE: RouteNGN may be configured to return multiple locales for all digit matched not just one.

Best Rate

RouteNGNuses the following order to set route order for Best Rate Routing

1. Best Price for all possible code matches2. Code Match

} Profit Threshold Met?

3. End Point Group Priority


23/47


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.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, ANI, or the RN only.

Figure 8 - Route Tables Main

Domestic Route TablesDomestic 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 are

routed 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


24/47


25/47


Figure 9 - Route Table View

Search

Regions, Locals or Dial Codes may be searched for in a Route Table. The search window is located on

the 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 assomething is typed into the window. There is no need to press [ENTER].

Allocation Routing

To perform Allocation or Percentage Routing, click the allocate link below the Locale you wish to

modify. This will redirect you to a screen to allow you to create multiple LCR and Block choices with

desired weights for the same Locale. Click Add for each new LCR choice you would like to add foreach locale. Next, set the route priorities as you normally would (see Changing Route Priorities section

above). Then, add the relative weight you would like to apply to each choice. Finally, click Save

then Back to return to the routing table. An APPLY is NOT needed to make changes active.


26/47


Figure 10 - Allocation routing configure

To identify a locale as having allocation routing applied to it the system will replace route choices with

the weights and percentage of each allocation choice. To view the complete list, click on the allocate

link.

Figure 11 - Allocation routing view

Region Override

RouteNGN allows users to modify the routing choices for an entire region on a per jurisdiction basis.

In order to perform this action, click on the region name which will redirect you to the region overridescreen. Note that users can override the entire region route priority completely but also have the optionset a percentage of how often the override should occur. This percentage override applies to rerouting

the entire region or, blocking a specific endpoint group for the entire region while leaving the existing

route priorities in place (minus the blocked endpoint group of course).


27/47


Modifying blocks and route priority changes work as normal (see above), but the user now has the

option to set how often this will occur. The numbers next to the Order Chance and Block Chance

stand for percentage. For example, a setting of 100 activates the override on every call while a settingof 50, activates the override on half or 50% of the calls.

Once the settings are in place, click Save to activate and Back to return to the Routes screen.

An APPLY is NOT needed to make changes active.

Figure 12 - Region Override configure

To identify a Region as having override routing applied to it the system will replace route choices with

Region Override and the corresponding Order and Block choice percentages. .


28/47


Figure 13 - Region Override view

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.

Trouble Shooting Call Logs

To search for a Call Log in the system, navigate to [HOME]-->[RECORDS]. To view the most recentrecords, select current day of the month. To perform a search on one or more fields, click the Search

Day # button. Enter the complete or partial value followed by % for the desired field(s). Clicking on

each call record will open a tab (if supported by browser) with more detailed information on thatparticular call.

The system stores calls for 30 days.


29/47


Figure 14 - Call Log Search


30/47


Page 30

Sample Call Log

Field Value

id 413

created_at 2012-04-25 12:29:11 UTC

received

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

Via: SIP/2.0/UDP 192.168.1.52:5060;branch=z9hG4bK-4607-1-0

From: sipp ;tag=4607SIPpTag001

To: sut

Call-ID: [email protected]

CSeq: 1 INVITE

Contact: sip:[email protected]:5060

Max-Forwards: 70

Subject: Performance Test

Content-Type: application/sdp

Content-Length: 133

v=0

o=user1 53655765 2353687637 IN IP4 192.168.1.52

s=-

c=IN IP4 192.168.1.52

t=0 0

m=audio 6000 RTP/AVP 0

a=rtpmap:0 PCMU/8000

detail

Setting account 3 by local and source IP:cp3.routengn.icehook.com

Selecting routing module

Source IP: 50.38.131.98

Dialed Digits: 8176815120

Prefix: 3000#

Creating new routing module

Setting routing algorithm to: stickySet failure code to 503 Service Unavailable

Setting up query

Using source ip and prefix to determine inbound group

Making instance query

Using endpoint group: dialer


31/47


Page 31

Using table USA

strip_digits is: null

Got append digit data null , null , nullrn prefix is: null

rn is: null

margin is:0

Setting module type to: ii

Setting route on type to : dn

Parsed 9162085087 as ANI

Checking for blocked ANI

ANI is Not Blocked.

Parsed 8176815120 as DN

Checking for blocked DN

DN is Not Blocked.Unable to convert RN (null) to long and test for block

Using II

Setting routing algorithm to: sticky

Set failure code to 503 Service Unavailable

Got instance: 1

Routing on DN - digits now: 8176815120

ANI: 9162085087

DN: 8176815120

Making ANI region query

Making DN region query

route table type is: interGot customer rate: 0.04

Setting up routes query

Making routes query

Total routes found:1

longest dialcode match: 817681

gathering routes details for locale_id 13772, routecase 2,3

Setting up custom routes query

Making custom routes query

got customRoutecases: []

Final EndPointGroup order: [2, 3]

Got customer rate: 0.04Using best digit match routing

Matched digits: 817681

Using profit threshold

Margin: 0

Customer rate: 0.04


32/47


Page 32

Supplier rate: 0.02

Trunkgroup: null

Calculated margin: 50.0Margin threshold met - appending route: 1.1.1.1 ( 817681 , 0.02 )

Matched digits: 817681

Using profit threshold

Margin: 0

Customer rate: 0.04

Supplier rate: 0.03

Trunkgroup: null

Calculated margin: 25.000000000000007

Margin threshold met - appending route: 2.2.2.2 ( 817681 , 0.03 )

Sending reply from ip: cp3.routengn.icehook.com

SRS version: 1.9.69-analyticstime: 0.008

sent

SIP/2.0 300 Redirect

To: sut

;tag=1267374834

From: sipp ;tag=4607SIPpTag001

Call-ID: [email protected]

CSeq: 1 INVITE

Via: SIP/2.0/UDP 192.168.1.52:5060;branch=z9hG4bK-4607-1-0

Contact:

Contact:

Server: KETEL Research SRS 1.9.69-analytics

call_date_in_iso8601 2012-04-25 12:29:11 UTC

call_date_in_milliseconds 1335371351776

invite true

server_name ICEHOOK_DEVEL

server_version 1.9.69-analytics

stale false

account_id 3

signaling_ip 50.38.131.98


33/47


Page 33

source_ip

local_ip cp3.routengn.icehook.com

call_id [email protected]

dialed_digits 8176815120

prefix 3000#

ani 9162085087

rn

oli

route_on_digits 8176815120

trunk_group

inbound_end_point_group_id 1

inbound_end_point_group_name dialer

matched_dialcodes

route_on_type dn

returned_contacts 2

lrn_dipped false

lrn_dip_time

response_time 0.008

loop_detected false

contacts (,,1.1.1.1,0.02)|(,,2.2.2.2,0.03)

customer_rate 0.04

response_code 300 Redirect

used_profit_protection true

route_table_name USA

route_table_type inter


34/47


Page 34

internal_response_code 700

total_routes_found 1

total_routes_returned 2

first_place_end_point_group_id 2

longest_dialcode_match 817681

lowest_available_vendor_rate 0.02

highest_available_vendor_rate 0.03

average_available_vendor_rate 0.025

required_profit_margin 0

first_place_vendor_profit_margin 50.0

average_profit_margin 37.5

failed_profit_margin false


35/47


Trouble Shooting Call Reports

To search for a Call Log in the system, navigate to [HOME]-->[REPORTS]. Select the items in the

pull down menu that you would like to report on. Leaving an item blank will default to all.

Figure 15 - Call Reports

The Max Digits pull down will tell the system how many digits it should group the report by. The

image below shows the results for a Max Digit setting of 6.


36/47


Figure 16 - Call Reports results


37/47


Page 37

Appendix A: Genband S3 4.0c3-xx RouteNGNConfigurationGuide

Introduction

This document illustrates the procedures needed to configure the RouteNGN using Full Qualified

Domain Name (FQDN) in conjunction with the Genband Session Border Controller (SBC) running

version 4.0c3-74. The How-To assumes that DNS has been set up and SBC can PING the RouteNGN

via the FQDN address.

RouteNGN Endpoint Configuration

From the tool bar select: EDIT > ADD > Endpoint

Figure 17 - Endpoint Configuration Phone


38/47


Page 38

From the Device Type select SIP Proxy Enter a name for the RouteNGN in the Registration ID: field Port Number will automatically populate with zero Enter the IP Address of the RouteNGN Select a Calling Plan Select the Realm on which the RouteNGN resides Select IEdge Group

Select the Advanced tab.

Figure 18 - Endpoint Configuration Advanced


39/47


Page 39

Uncheck the Domain Match Flag

Select the Protocol tab.

Figure 19 - Endpoint Configuration Protocol

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


40/47


41/47


Page 41

Figure 21 - Endpoint Configuration Calls

CheckUnlimited for all three CAC setting. Confirm that all three the radio buttons are unchecked for Media control


42/47


Page 42

Select the OK button to save the endpoint. The RouteNGN end point is now configured and set-up for

redundancy.


43/47


Page 43

Appendix B: Genband S3 v4.3m7 RouteNGNConfiguration Guide:

Introduction:

This document illustrates the procedures needed to configure the RouteNGN using Full Qualified

Domain Name (FQDN) in conjunction with the Genband Session Border Controller (SBC) running

version 4.3m7. The How-To assumes that DNS has been set up and SBC can PING the RouteNGN viathe FQDN address.

RouteNGN GUI Endpoint Configuration

From the tool bar select: EDIT > ADD > Endpoint

Figure 22 - Endpoint Configuration Phone


44/47


Page 44

From the Device Type select SIP Proxy Enter a name for the RouteNGN in the Registration ID: field Port Number will automatically populate with zero Enter the IP Address of the RouteNGN Select a Calling Plan Select the Realm on which the RouteNGN resides

Select the Protocol tab.

Figure 23 - Endpoint Configuration Protocol

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


45/47


Page 45

Figure 24 - Endpoint Configuration SIP Protocol


46/47


Page 46

Check the FQDN redundancy radio button Enter the FQDN, provided by IceHook, in the Contact: field Select the OK button to go back to the Protocol tab.

Select the Calls tab

Figure 25 - Endpoint Configuration Calls


47/47

CheckUnlimited for all three CAC setting.

Confirm that all three the radio buttons are unchecked for Media control

Select the OK button to save the endpoint.

Global Configure CLI for H.323 End Point

From the CLI of the S3 enter the following global configuration command to enable the S3 not toappend the INGRESS calling plan to the EGRESS end point when routed via a 300 message.

S3-MSX:~ # nxconfig.pl -e nosrcdnisrouteonlcf -v 1

S3-MSX:~ # nxconfig.pl -s nosrcdnisrouteonlcf

----------------------------------------------------------

Attribute Information

----------------------------------------------------------

Process Name : gis

Attr. Category: h323

Attr. Name : nosrcdnisrouteonlcf

Attr. Value : 1

Attr. Default : 0

Attr. Min Val : 0

Attr. Max Val : 1

Attr. Type : bool

Attr. Descr. : Configuration to not apply the ingress DNIS

route when doing a DB lookup for a number returned in theLCF. Valid Values: 1 (Enable) | 0 (Disable)

Needs iServer Restart : no

----------------------------------------------------------

S3-MSX:~ #

The RouteNGN end point is now configured and set-up for redundancy.

project about route ngn user manoul by alireza navabi teacher: mr ali esmaeili

Documents