There are two main voice routing modes in SAARA: Fixed Rriority Routing and Least Cost Routing. Fixed Priority routing lets system administrator assign fixed priority and weight based routes and Least Cost Routing (LCR) lets administrator to choose routes based on their purchase price. All routes selection are made based on the longest matching prefix, i.e. to select the proper routing group the system will try to find a most matching route based on the first digits of the destination number.
The simplest case is where all calls are sent to one carrier. This case does not need any further setup beyond what was explained in Voice Service Quick Start Guide. If you only use one carrier, please follow the mentioned guide. The rest of this document is intended only for those who are setting up more than one voice carrier.
The routing is based on the master list - single centralized list of destinations and codes across the system. Only the codes in the master list are considered when making routing decisions. Therefore, for a destination to have separate routing, its codes should be present in the Master List. There are several ways to set up Master list:
Navigate to Routing > Voice > Master List tab. This is a list of Master Code lists in the system. Note, that they are ordered by time, i.e. it is possible to create a new Master Code list for future use with Activation Time in the future without disrupting current operations. To add a new master List for use in future, click "Add Master Code List" button. A dialog will prompt for Activation Date and option to copy Master List from any of existing versions. It is useful if you want to make some small manual changes in the list and become effective on the future date:
Save the list and click on "View Codes" button of the newly created empty master code list. To start adding destinations manually, click "Add destination" button. Enter destination name and click "Save": When saved, "Add Codes" button will appear. Add code or more codes one by one:
Add all destinations and codes for which you will need separate routing breakouts, including fixed/mobile, area codes and different mobile operators.
It is also possible to import master code list from .csv file. Prepare a file with destination codes and names following this simple example:
|33764||France - Mobile Bouygues|
|336059||France - Mobile Bouygues|
|337525||France - Mobile Bouygues|
|337524||France - Mobile Bouygues|
|337523||France - Mobile Bouygues|
|337522||France - Mobile Bouygues|
|337521||France - Mobile Bouygues|
|337515||France - Mobile Bouygues|
|337514||France - Mobile Bouygues|
|337513||France - Mobile Bouygues|
|337512||France - Mobile Bouygues|
|335091||France - Mobile Bouygues|
|336003||France - Mobile Bouygues|
|337511||France - Mobile Bouygues|
Select the template "Simple 3col" and click "Upload" to start upload. Once finished, click "View Codes" to verify if codes and destinations are uploaded as expected.
You can use Master Code List (CSV) to try the upload. NOTE: the code list is provided as a sample only! The codes change very frequantly and we cannot gauarantee the accuracy of the provided file. Use with caution!
Once master code list is created, we can now crate actual routes. Go to Routing > Voice > Routing Groups and select a routing group which you want to use. (How to assign routing group to client via Product, see Voice Service Quick Start Guide).
Click "Add Routing Destination" button. A dropdown list with destinations will appear with the "AZ Destinations (ALL)" on the top. It is important to add AZ destinations to the routing since it will provide a "catch all" route for those routes which are not configured explicitly.
Select the destination you would like to route, and choose from the routing type dropdown:
After destination is added, add all possible carriers where you would like this destination to be routed:
You can add more than one carrier for each destiantion row.
Here are the settings available for each routing type:
Set as much as separate routes are necessary. Note, that route search is always starting from longest prefix match down to AZ destinations if there are no "Huntstop" checked on the routes in the match list.
Test the route, and observe the call records. Make the corrections if necessary.