General info


By default Sippy Softswitch allows you to apply only one tariff per Account.  The tariff is called "Default" in the examples below. From time to time, the tech team receives questions of how to configure and use different prices and different routing rules based on CLI (i.e. ANI based routing) or CLD (prefix based routing).  A configuration of these two solutions is shown below.


How to setup ANI/CLI based routing:


Task:

  • if ANI starts with 123, then apply Premium prices and route the call to a carrier with Premium quality
  • if ANI starts with 456, then apply Gold prices and route the call to a carrier with Gold quality
  • in other cases, use default prices and routes.


The setup assumes that you already have an Account which has been assigned a:

  1. Default Tariff (i.e. default service plan) with default prices;
  2. Default Routing Group with default routes

(if you don't, please refer to the Basic setup checklist)


First of all, you need to open Authentication Rules for the Account in question using the popup menu:


Next, click the Add button and define the options for the new authentication rule as below:


Then, add another authentication rule with a different ANI prefix, tariff and routing group (see below):


You can see every authentication rule has its own Tariff and Routing Group (Premium and Gold respectively).  A CLI translation rule may be required if you need to remove the prefix from the CLI.


Once it's done, you can check your setup using the Test Dial Plan tool.  Here are two examples:


If ANI starts with 123:


If ANI starts with 456:


How to setup CLD prefix based routing:


Task:

  • if CLD starts with 444, then apply Premium prices and route the call to a carrier with Premium quality
  • if CLD starts with 555, then apply Gold prices and route the call to a carrier with Gold quality
  • in other cases, use default prices and routes


The setup assumes that you already have an Account which has been assigned a:

  1. Default Tariff (i.e. default service plan) with default prices
  2. Default Routing Group with default routes

(if you don't, please refer to the Basic setup checklist)


Next, you need to create authentication rules.  Add one authentication rule as below:


Then, add another authentication rule as below:


You can see every authentication rule has its own Tariff and Routing Group (Premium and Gold respectively).  A CLD translation rule may be required if you need to remove the prefix from CLD.


Once it's done, you can check your setup using the Test Dial Plan tool.  Here are two examples:


If CLD starts with 444:


If CLD starts with 555:


How to block calls based on either CLI (ANI) or CLD:


Task:

  • if ANI is "Anonymous", then block the call
  • if CLD has less than 10 digits, then block the call
  • in other cases, allow calls using default pricing and routing


The setup assumes that you already have an account which has been assigned a:

  1. Default Tariff (i.e. default service plan) with default prices
  2. Default Routing Group with default routes

(if you don't, please refer to the Basic setup checklist)


First of all, you need to create an authentication rule which will filter all calls that have a CLD shorter or longer than 10 digits:


The translation rule is:

s/^(\d{,9}|\d{11,})$/BLOCK/


Next, you need to add an authentication rule that will match all anonymous calls:


Once the rules are added, check how your setup works. 


He is an example of a call to a CLD that contains 11 digits:


Here is an example of a call from Anonymous CLI:



Summary


The examples provided above cover very simple use-cases in order to show you how to split traffic with prefixes.  Your requirements may be more complicated.  For example, in cases where more than two prefixes are required or where a verification of CLI/CLD length is needed, you can add as many authentication rules as are needed.


Useful links

  1. Understanding authentication
  2. Understanding routing
  3. Understanding number translation
  4. Video tutorial: Authentication rules part 1
  5. Video tutorial: Authentication rules part 2
  6. All video tutorials