[SR-Users] Dispatcher round-robin problems in 5.2

Daniel-Constantin Mierla miconda at gmail.com
Mon Aug 12 17:24:45 CEST 2019


could you observe similar behavior on other dispatchers that don't use
an external system tomanage activation and deactivation of the gateways?
Or you haven't checked such one so far?


On 12.08.19 15:23, Alex Balashov wrote:
> Hi,
> I've got a proxy that does very basic round-robin distribution of calls
> to an elastic pool of servers, defined in a simple SQLite database with
> equal priorities. Nothing too complicated, just a vanilla
> `ds_select_domain("1", "4")`. 
> The only complication is that seldom are most of the gateways enabled.
> Probing stuff was turned on, but didn't do quite what was desired, so it
> was replaced with a system that manages activation and deactivation of
> the gateways externally. Nevertheless, these are the left-over probing
> settings:
>    modparam("dispatcher", "ds_ping_method", "OPTIONS")
>    modparam("dispatcher", "ds_ping_from", "sip:pinger at domain")
>    modparam("dispatcher", "ds_ping_interval", 15)
>    modparam("dispatcher", "ds_probing_threshold", 256)
>    modparam("dispatcher", "ds_inactive_threshold", 1)
>    modparam("dispatcher", "ds_probing_mode", 0)
> After an upgrade from 5.1 to 5.2.3 (009f62), the round-robin has become
> extremely "sticky" and tendentious. That is to say, it directs _almost_
> all calls to a single gateway -- the first gateway in the table --
> though not 100%. There is also a marked tendency to send lots of
> consecutive calls to the same gateway, even if it's not the first one,
> though most of the time it is.
> Has anyone experienced similar upon upgrading to 5.2? 
> Thanks much!
> -- Alex
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda

More information about the sr-users mailing list