[OpenSIPS-Users] ds_select_dst with algorithm 6 is not using the last destination

[Pat Burke]

Hello,


It appears that 2.2.2 ds_select_dst with the parameters that I have below is not using the last destination in the set.  


...
	if (!ds_select_dst("$avp(core_server_group)","6","FuSd")) {
...


Here is the results from ds_list full.


(with 2 destinations in the set)
PARTITION:: default
	SET:: 10005
		URI:: sip:216.147.191.143:5060 state=Active first_hit_counter=16
			weight:: 1
			priority:: 0
			description:: DEV Ingress-DEV Core
		URI:: sip:216.147.191.144:5060 state=Active first_hit_counter=0
			weight:: 1
			priority:: 0
			description:: DEV Ingress-DEV Core
	SET:: 10002




(with 3 destinations in the set)
PARTITION:: default
	SET:: 10005
		URI:: sip:216.147.191.143:5060 state=Active first_hit_counter=13
			weight:: 1
			priority:: 0
			description:: DEV Ingress-DEV Core
		URI:: sip:216.147.191.144:5060 state=Active first_hit_counter=15
			weight:: 1
			priority:: 0
			description:: DEV Ingress-DEV Core
		URI:: sip:216.147.191.142:5060 state=Active first_hit_counter=0
			weight:: 1
			priority:: 0
			description:: DEV Ingress-DEV Core
	SET:: 10002








What I am after is the functionality that I had in 1.11 which was a random use of all destinations in the set.  I had the following setting




modparam("dispatcher", "force_dst", 1)
modparam("dispatcher", "flags", 2)


and called using


...
    if (!ds_select_dst("$avp(core_server_group)","6")) {
...


Regards,
Pat Burke



______________________________________________________________________________________
Direct: (402) 403-5121   |   Cell: (402) 443-8929  |   Email: pat at voxtelesys.com
1801 23rd Avenue North   |  Suite 217    |  Fargo, North Dakota 58102

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20170206/448bda26/attachment.html>