[SR-Users] Monitoring Dispatcher

[Tim Bowyer]

Hi Daniel,

Wow that was fast!  Really appreciate your efforts.
I'm using a docker package at the moment so will need to jump through some hoops to get the master build packaged for docker.

I'll keep you posted how I go.

Cheers once again and have a great weekend.

Tim Bowyer

-----Original Message-----
From: Daniel-Constantin Mierla <miconda at gmail.com> 
Sent: Thursday, 7 June 2018 7:10 PM
To: Kamailio (SER) - Users Mailing List <sr-users at lists.kamailio.org>; Tim Bowyer <timbo at timbo.net.au>
Subject: Re: [SR-Users] Monitoring Dispatcher

Hello,


On 07.06.18 10:04, Daniel-Constantin Mierla wrote:
> Hello,
>
> [...]
>
> For the future, I can add an rpc command to dump those numbers 
> directly from dispatcher module when using with algorithm 10.

just implemented the feature in master branch -- the active dialogs load should be printed in the rpc output for each destination (RUNTIME => DLGLOAD field).

Can you test and report back if it gives what you expect? If you want to test with older versions and backport the patch locally, the commit adding it is:

  -
https://github.com/kamailio/kamailio/commit/513a176394247a3378ee218bf9df611da7296061

Cheers,
Daniel
>
> Cheers,
> Daniel
>
> On 07.06.18 09:04, Tim Bowyer wrote:
>> Thanks for the prompt reply Alex!
>>
>> Trying to get my head around the best way to use the module.
>> By the looks I need to statically create profiles which will be used as counting groups.  
>> Since each destination is dynamically created thus named with a fairly random ID, I can't see how this could work.
>>
>> Have tried using variables but I get a heap of errors.  The process will only start if I use static profile names.
>>
>> Is there another sneaky way to get around this?  When a new container is spun up, a new entry is added to the dispatcher table and the dispatcher reloaded.
>> Likewise to trigger a container to start draining calls we remove from dispatcher then reload before waiting for all calls to finish and stop the container.
>>
>> Cheers,
>>
>> Tim Bowyer
>>
>>
>> -----Original Message-----
>> From: sr-users <sr-users-bounces at lists.kamailio.org> On Behalf Of 
>> Alex Balashov
>> Sent: Thursday, 7 June 2018 10:42 AM
>> To: Kamailio (SER) - Users Mailing List <sr-users at lists.kamailio.org>
>> Subject: Re: [SR-Users] Monitoring Dispatcher
>>
>> It sounds like the dialog module might be your best bet. 
>>
>> On June 6, 2018 10:40:38 PM EDT, Tim Bowyer <timbo at timbo.net.au> wrote:
>>> Hi All,
>>>
>>> Currently trying to work out the best way to keep track of how many 
>>> calls are being sent to any given dispatcher destination.
>>> I remember being able to do this years ago with the load balancer 
>>> module in OpenSIPS: opensipsctl fifo lb_list.
>>>
>>> Dispatching algorithm '10' seems to be the best fit for my 
>>> requirements, as I'm essentially wanting to send calls to a large 
>>> quantity of FreeSwitch docker containers acting as fax receiving nodes.
>>> Equal weight, just filling them in some balanced fashion.
>>>
>>> Any hints or ideas would be much appreciated!
>>>
>>> Kind regards,
>>>
>>> Tim Bowyer
>> -- Alex
>>
>> --
>> Sent via mobile, please forgive typos and brevity. 
>>
>> _______________________________________________
>> Kamailio (SER) - Users Mailing List
>> sr-users at lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>> _______________________________________________
>> Kamailio (SER) - Users Mailing List
>> sr-users at lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

--
Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference -- www.kamailioworld.com