Re: [SR-Users] Best practise for limiting concurrent calls across a cluster

2015-09-08 Thread Juha Heinanen
Daniel-Constantin Mierla writes: > Are you referring to the hierarchical architecture I plugged in as > example for usrloc, or about the topic of limiting the concurrent calls > using a backend system? I'm referring to your hierarchical architecture idea. > The hierarchical model is not the only

Re: [SR-Users] Best practise for limiting concurrent calls across a cluster

2015-09-08 Thread Daniel-Constantin Mierla
On 08/09/15 12:00, Juha Heinanen wrote: > Daniel-Constantin Mierla writes: > >> However, even in this case, when the subscriber base is really huge, >> single mysql system can become slow, so there needs to be some >> partitioning of the users, relying on several mysql systems. > In that case parti

Re: [SR-Users] Best practise for limiting concurrent calls across a cluster

2015-09-08 Thread Juha Heinanen
Daniel-Constantin Mierla writes: > However, even in this case, when the subscriber base is really huge, > single mysql system can become slow, so there needs to be some > partitioning of the users, relying on several mysql systems. In that case partitioning could be done also based on userid or p

Re: [SR-Users] Best practise for limiting concurrent calls across a cluster

2015-09-08 Thread Daniel-Constantin Mierla
On 07/09/15 19:36, Juha Heinanen wrote: > Daniel-Constantin Mierla writes: > >> This is one way to go, ans should work fine (maybe a bit more testing >> needed) for few nodes, but I am actually not using this one, because it >> is a matter of what kind of routing architecture you go for. Lately I

Re: [SR-Users] Best practise for limiting concurrent calls across a cluster

2015-09-07 Thread Juha Heinanen
Daniel-Constantin Mierla writes: > This is one way to go, ans should work fine (maybe a bit more testing > needed) for few nodes, but I am actually not using this one, because it > is a matter of what kind of routing architecture you go for. Lately I > found that replication can bring lots of head

Re: [SR-Users] Best practise for limiting concurrent calls across a cluster

2015-09-07 Thread Daniel-Constantin Mierla
Hello, some of my thoughts on the topic, presented as concepts ... There is a function dlg_remote_profile() that can be used to mirror only profiles from one sip server to another: - http://kamailio.org/docs/modules/stable/modules/dialog.html#dialog.f.dlg_remote_profile The idea is that when

Re: [SR-Users] Best practise for limiting concurrent calls across a cluster

2015-09-04 Thread José Seabra
Hi, I'm also using the same mechanism that Carsten is using(htable and DMQ), the only issue about this solution is when one of your kamailio instances goes down and up, this instance looses the number of current calls. Regards José Seabra 2015-09-04 13:53 GMT+01:00 Daniel Tryba : > On Friday

Re: [SR-Users] Best practise for limiting concurrent calls across a cluster

2015-09-04 Thread Daniel Tryba
On Friday 04 September 2015 10:56:21 Carsten Bock wrote: > i did implement such mechanism once using a htable and DMQ, that > worked like a charm. Sound good, my current solution misses concurrent call setup that happen withing the dialog db_update_period timeout. ___

Re: [SR-Users] Best practise for limiting concurrent calls across a cluster

2015-09-04 Thread Carsten Bock
Hi, i did implement such mechanism once using a htable and DMQ, that worked like a charm. Thanks, Carsten 2015-09-04 10:54 GMT+02:00 Daniel Tryba : > On Friday 04 September 2015 10:15:29 Daniel Tryba wrote: >> But isn't the easiest/best solution to just use sqlops to count the number >> of dial

Re: [SR-Users] Best practise for limiting concurrent calls across a cluster

2015-09-04 Thread Daniel Tryba
On Friday 04 September 2015 10:15:29 Daniel Tryba wrote: > But isn't the easiest/best solution to just use sqlops to count the number > of dialogs for the current endpoints? > select count(id) from dialog where xdata like > '"name":"maxchannels","value":"$dlg_var(key)"' > where the dialog var con

Re: [SR-Users] Best practise for limiting concurrent calls across a cluster

2015-09-04 Thread Daniel Tryba
On Friday 04 September 2015 10:19:07 jay binks wrote: > Initially I mis-read the dialog module documentation and assumed that > dialog would provide me this ability, when used with a database. however > it seems that the dialog module does not pull data from the DB after the > initial startup. A

Re: [SR-Users] Best practise for limiting concurrent calls across a cluster

2015-09-03 Thread jay binks
Im currently using cassandra with kamailio I need something thats highly available and partition tolerant, consistency is a secondary requirement for most of the data. Im really not sure that restful web services are the right way here, that seems like a LOT of overhead at high cps. Sorry I forgo

Re: [SR-Users] Best practise for limiting concurrent calls across a cluster

2015-09-03 Thread Brandon Armstead
I would use some kind of RESTFUL service implementation, various transport mediums are avail i.e. RPC etc. What database are you currently using ? Sincerely, Brandon Armstead > On Sep 3, 2015, at 5:19 PM, jay binks wrote: > > Hey all, > > So I have a cluster of Kamailio servers ( 4 servers c

[SR-Users] Best practise for limiting concurrent calls across a cluster

2015-09-03 Thread jay binks
Hey all, So I have a cluster of Kamailio servers ( 4 servers currently, soon to be 8 ), I'm looking for suggestions about the BEST way to achieve concurrent call limiting on a per customer basis, across the whole cluster. Initially I mis-read the dialog module documentation and assumed that dialo