Hello,

I have only relevant experience with the carrierroute module. This module has 
support for different prefix/suffix per carrier for example. About the 
different headers, this might be maybe easier to be implemented with the lcr 
module flags support.

Table reload with RPC commands support both modules. About the alarming, you 
probably need to setup something here on your own.

Another idea is to combine one of the module with a database or htable lookup, 
or even go only with a database query in a custom table, performance wise is 
the in-memory storage that the mentioned modules provide in many cases not 
necessary anymore.

Cheers,

Henning

--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://gilawa.com<https://gilawa.com/>

From: sr-users <[email protected]> On Behalf Of Edward 
Romanenco
Sent: Sunday, April 19, 2020 2:25 PM
To: [email protected]
Subject: [SR-Users] LCR and fallback

Hi!

I would like to implement LCR and fallback capabilities for my Kamailio 
installation. I'm currently using the dispatcher module with a simple 
configuration file.
As I understood, there are multiple modules (carrier route, dynamic routing) 
that can be used to achieve that, what I'm aiming for is -
*         Country-based (or prefix-based) routing with up to 4 different 
carriers (could be expanded in the future, but I won't have more than a dozen), 
while also maintaining a fallback route if the 1st priority is not available.
*         Each of my carriers have his own requirements for headers and 
formatting, for instance, for one of our carriers, having a '+' prefix before 
dialing to a non-US number is mandatory, while on the others - it is not, or 
another example - one of my carriers doesn't allow having a P-Asserted-Identity 
header in my invite, while others do. I would love to have the option to 
manipulate headers based on the route that I have chosen, both on the default 
and fallback routes.
*         It would be nice to receive SMTP or SNMP alerts if a fallback does 
occur.
*         Easy management, having the ability to load and reload the routing 
table on a monthly basis, once the pricing list is changed.
What would be your suggestion?

Edward
_______________________________________________
Kamailio (SER) - Users Mailing List
[email protected]
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Reply via email to