Hello Jasen,
just a quick guess – but have you already tried with a larger value suggested from the
documentation?
1 sip:10.0.0.1:5060<http://10.0.0.1:5060>
weight=75
1 sip:10.0.0.2:5060<http://10.0.0.2:5060> weight=25
Cheers,
Henning
--
Henning Westerholt -
https://skalatan.de/blog/
Kamailio services -
https://skalatan.de/services
From: sr-users <sr-users-bounces(a)lists.kamailio.org> On Behalf Of Jasen Hall
Sent: Tuesday, October 15, 2019 6:56 PM
To: sr-users(a)lists.kamailio.org
Subject: [SR-Users] Kamailio weighted dispatch problems
I am trying to change our request dispatching from round-robin to a weight-based method
(ds_select_dst() algorithm 9 vs. algorithm 4) and am having a hard time getting an
asymmetrical dispatch pattern enabled. In testing, I'm dispatching to two Ringswitch
servers and trying to send three times the traffic to one instance.
My destinations list file previously set both endpoints in the same group and simply
provided the SIP URI for each. My new list file adds the attribute `weight` to each
endpoint and looks like this:
1 sip:10.0.0.1:5060<http://10.0.0.1:5060>
weight=3
1 sip:10.0.0.2:5060<http://10.0.0.2:5060> weight=1
However, when I throw a couple thousand calls at Kamailio, I always end up with an almost
perfect split of calls to both ringswitches. Regardless of the weights I choose, I never
see variation in the dispatched load.
Does anyone have experience with this issue and have some guidance?
Thanks in advance.
--
Jasen Hall | Invoca
Site Reliability Engineer
www.invoca.com<http://www.invoca.com>
[See the
list]<https://invoca.sigstr.net/uc/5cba111d3527a200469b9afd>