Mike's PBX Cookbook

Editing the NRS

The Network Routing Service (NRS) is responsible for directing calls to the appropriate end point. Remember this is a virtual world: IP trunking does not exist in the traditional sense where a route has physical known end points. Traditional point-to-point 'trunk-routes' don't exist; it's all a nice fluffy cloud.

End points are defined in the NRS database, and associated with their local DN's (or DN range). NRS will define a virtual path (route, to the dialed DN at the appropriate endpoint using this database. If an entry does not exist, the call will fail; in which case it will be necessary to edit the NRS end point data to add it.

NRS is comparable to the internets DNS. A user dials a DN: if the DN is 'off-switch', the NRS is queried for an end-point PBX. The call is then routed to this PBX where it can hopefully be connected.

The following screen shots are from a 5.5 NRS. With 7.5 (and above), log into the Primary NRS server from the UCM Elements list, the principle is the same.

NOTE: Click image to zoom!

To view (or edit) the NRS entries, enter the NRS server IP address into a web browser window, hit enter, and wait for a similar page to load.

Login to the NRS server, the default login is: admin / admin

nrs1sm.gif
Click the <CONFIGURATION> tab
nrs2sm.gif
Click on the left menu <Gateway Endpoints>, or table heading <# of gateway endpoints>
nrs3sm.gif
Click on the table heading <# of routing entries> to display the dial plan for that endpoint (or site name in this example).

Here you can see the entries for Bordeaux:

nrs4sm.gif
Note: You cannot edit or add to the active database. You can ONLY make changes to the Standby Database.

To make changes, you must first switch to the standby database by clicking on <set Standby DB view>

nrs5sm.gif
Here, you can again see the Routing Entries for Bordeaux, this time in Standby DB View. NRS will direct network calls to 436X and 59XX to Bordeaux.

When you edit, think about these entries! Don't waste DN's, or duplicate entries for other endpoints, otherwise confusion will reign (well, lots of errors)!

If the routing entry is not there, or incorrect, NRS will not be able to route the call.

Route Cost: a call will always be sent to the endpoint with the lowest Route Cost if there are multiple endpoints with the same digits.

nrs6sm.gif
Having made changes, they need to be saved, committed, and made active.

To commit the changes, click on the top menu item <Tools>

nrs6sm.gif
And click the left menu item <Database Actions>

Choose <Cutover and Commit> from the drop down menu.

And click submit.

nrs6sm.gif
Your changes will be saved, and the database made active.

Make some test calls, and determine if the changes have worked.

The database is instantly committed, and there is practically no delay in implementing the changes.

Logout of the NRS server, and close the browser window.

nrs6sm.gif