Hi all,
I need to setup an inbound DID router for 8 proxies and ~300 DID's. Very simple, a call comes in from pstn > kamailio looks up DID for exact match in mysql > returns location > If db result returns noservice redirect to 1.2.3.4 else remain in call-flow and send to destination. Having a failure route capability would be nice.
From what I've read on each of the 4 modules, any could do what I need though each have their own complexities. I'm still new to kamailio and hoping to utilize the group here for some advice. I'd like to keep this as simple as possible then adding/deleting DID's from the db as needed for routing.
In your experience which would be the best module to use in order to achieve my goal?
TIA,
Skyler
Hello,
what I use in such case is a combination between mtree and dispatcher. DIDs are matched against mtree and as a result on successful match is the ID to use with dispatcher to find where to relay/redirect it.
Cheers, Daniel
On 10/3/11 9:23 AM, Skyler wrote:
Hi all,
I need to setup an inbound DID router for 8 proxies and ~300 DID's. Very simple, a call comes in from pstn> kamailio looks up DID for exact match in mysql> returns location> If db result returns noservice redirect to 1.2.3.4 else remain in call-flow and send to destination. Having a failure route capability would be nice.
From what I've read on each of the 4 modules, any could do what I need though each have their own complexities. I'm still new to kamailio and hoping to utilize the group here for some advice. I'd like to keep this as simple as possible then adding/deleting DID's from the db as needed for routing.
In your experience which would be the best module to use in order to achieve my goal?
TIA,
Skyler
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hi Daniel,
Does mt_reload need to be run upon adding/removing entries in db? If so, is there a way to run mt_reload automatically every so often via kamailio.cfg? What would I be searching in docs to find an example of that?
Cheers, Skyler
On Mon, 2011-10-03 at 18:14 +0200, Daniel-Constantin Mierla wrote:
Hello,
what I use in such case is a combination between mtree and dispatcher. DIDs are matched against mtree and as a result on successful match is the ID to use with dispatcher to find where to relay/redirect it.
Cheers, Daniel
On 10/3/11 9:23 AM, Skyler wrote:
Hi all,
I need to setup an inbound DID router for 8 proxies and ~300 DID's. Very simple, a call comes in from pstn> kamailio looks up DID for exact match in mysql> returns location> If db result returns noservice redirect to 1.2.3.4 else remain in call-flow and send to destination. Having a failure route capability would be nice.
From what I've read on each of the 4 modules, any could do what I need though each have their own complexities. I'm still new to kamailio and hoping to utilize the group here for some advice. I'd like to keep this as simple as possible then adding/deleting DID's from the db as needed for routing.
In your experience which would be the best module to use in order to achieve my goal?
TIA,
Skyler
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
You can reload from command line with
kamctl fifo mt_reload <tree name>
/Morten
On Tue, Oct 4, 2011 at 2:07 AM, Skyler skchopperguy@gmail.com wrote:
Hi Daniel,
Does mt_reload need to be run upon adding/removing entries in db? If so, is there a way to run mt_reload automatically every so often via kamailio.cfg? What would I be searching in docs to find an example of that?
Cheers, Skyler
On Mon, 2011-10-03 at 18:14 +0200, Daniel-Constantin Mierla wrote:
Hello,
what I use in such case is a combination between mtree and dispatcher. DIDs are matched against mtree and as a result on successful match is the ID to use with dispatcher to find where to relay/redirect it.
Cheers, Daniel
On 10/3/11 9:23 AM, Skyler wrote:
Hi all,
I need to setup an inbound DID router for 8 proxies and ~300 DID's. Very simple, a call comes in from pstn> kamailio looks up DID for exact match in mysql> returns location> If db result returns noservice redirect to 1.2.3.4 else remain in call-flow and send to destination. Having a failure route capability would be nice.
From what I've read on each of the 4 modules, any could do what I need though each have their own complexities. I'm still new to kamailio and hoping to utilize the group here for some advice. I'd like to keep this as simple as possible then adding/deleting DID's from the db as needed for routing.
In your experience which would be the best module to use in order to achieve my goal?
TIA,
Skyler
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Thanks Morten, that will work nicely from cron :)
On Tue, 2011-10-04 at 08:20 +0200, Morten Isaksen wrote:
You can reload from command line with
kamctl fifo mt_reload <tree name>
/Morten
On Tue, Oct 4, 2011 at 2:07 AM, Skyler skchopperguy@gmail.com wrote:
Hi Daniel,
Does mt_reload need to be run upon adding/removing entries in db? If so, is there a way to run mt_reload automatically every so often via kamailio.cfg? What would I be searching in docs to find an example of that?
Cheers, Skyler
On Mon, 2011-10-03 at 18:14 +0200, Daniel-Constantin Mierla wrote:
Hello,
what I use in such case is a combination between mtree and dispatcher. DIDs are matched against mtree and as a result on successful match is the ID to use with dispatcher to find where to relay/redirect it.
Cheers, Daniel
On 10/3/11 9:23 AM, Skyler wrote:
Hi all,
I need to setup an inbound DID router for 8 proxies and ~300 DID's. Very simple, a call comes in from pstn> kamailio looks up DID for exact match in mysql> returns location> If db result returns noservice redirect to 1.2.3.4 else remain in call-flow and send to destination. Having a failure route capability would be nice.
From what I've read on each of the 4 modules, any could do what I need though each have their own complexities. I'm still new to kamailio and hoping to utilize the group here for some advice. I'd like to keep this as simple as possible then adding/deleting DID's from the db as needed for routing.
In your experience which would be the best module to use in order to achieve my goal?
TIA,
Skyler
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
On Monday 03 October 2011, Skyler wrote:
[..] From what I've read on each of the 4 modules, any could do what I need though each have their own complexities. I'm still new to kamailio and hoping to utilize the group here for some advice. I'd like to keep this as simple as possible then adding/deleting DID's from the db as needed for routing.
Hi Skyler,
maybe this information (from some previous mails) is helpful for you to get an general understanding:
The modules differ mostly in their provided configuration interface, their capabilities and the internal used datastructures IMHO.
lcr
- introduced in 0.9.x times, reworked several times
- provided initially support for a limited number of routes, today it
supports large route sets as well
- provides easy failover functionaly to try sequentially several gateways
- uses internally a hash table
cr
- introduced in 1.3, reworked for 1.5
- support larger route sets
- provides flexible failure routing capabilities with a dedicated table, but
is more complicated to setup and use
- uses a trie (tree) internally
mtree
- introduced in 3.1
- support larger route sets
- provides generic tree matching functionality, but without that much
additional functionality
- uses a tree internally
drouting
- ported from opensips for 3.0
- support larger route sets
- provides failover capabilities and some special matching as time or date
- uses a trie (tree) internally
Best regards,
Henning
-
Daniel-Constantin Mierla -
Henning Westerholt -
Morten Isaksen -
Skyler