[OpenSIPS-Users] Managing different route classes (Standard, Premium, Direct)

Nick Cameo symack at gmail.com
Sat Dec 7 00:07:26 CET 2013


Thanks Bogdan,

Correct me if I am wrong, you are suggesting something like:

Standard: 1001011
Premium: 1001012
Direct: 1001013

$var(prefix) = $tU.substr,0,7
     do_routing($var(prefix));


+--------+---------+--------+---------+----------+---------+--------+-------+----------------------------------------+
| ruleid | groupid | prefix | timerec | priority | routeid | gwlist |
attrs | description                 |
+--------+-----------------+--------+---------+----------+---------+--------+-------+---------------------------------+
| 321408 | 1001011 | 91     |         |        1 | 0       | 1,2
  | yes  | Standard India Route    |
+--------+----------------+--------+---------+----------+---------+--------+-------+----------------------------------+
| 321409 | 1001012 | 91     |         |        1 | 0       | 4,5
  | yes | Premium India Route    |
+--------+---------------+--------+---------+----------+---------+--------+-------+-----------------------------------+
| 321410 | 1001013  | 91     |         |        1 | 0       | 6,7    |
yes   | Direct India Route        |
+--------+---------+--------+---------+----------+---------+----+---------+----------------------------------------------+

Makes sense. Just a few issues:

* There will be only one massive dr_rules table for everything (ie,
standard,premium,
and direct prefixes destined to multiple gateways
* Only one dr_gateways table for the three types of routes. Again,
offered by multiple
carriers, failover etc...

Did I misunderstand something. And how manageable,scalable,performance
would this approach be?

Nice to hear from you again Bogdan,

Nick.



More information about the Users mailing list