Hi Yuriy
Sounds great. I am glad to hear you got a good working solution.
I hope you have a great weekend.
All the best.
Will
On Thu, Jan 29, 2015 at 2:52 AM, Yuriy Gorlichenko ovoshl...@gmail.com
wrote:
Will, thanks for your answer. I already implemented my own lgorithm
without using
Will, thanks for your answer. I already implemented my own lgorithm without
using dispatcher module. It works better for me. Now I try to implement it
with REDIS for faster results.
2015-01-29 1:35 GMT+03:00 Will Ferrer will.fer...@switchsoft.com:
Hi Yuri
I shared your issue with my business
Hi Yuri
I shared your issue with my business partner who works on the configs with
me. I had remembered he had some similar issue he pinged me about some time
back.
His response to your issue follows:
Looks like he is missing flags 8 and the trailing ; after weight in attrs.
CREATE TABLE
Hello I use dipatcher algorithm 8 that works with weight. I added 2
Asterisks and try to call its with my kam.We use 4.3 version.
Tthis config select needed dst from database with my scenario.
if(!ds_select_dst($var(setid), 8))
$var(setid)- is variable for setting setid that i get from
Hello,
what version are you using? Can you paste here the records you have for
the destination set (you can replace the ip addresses, I am interested
in attributes) and the ds_select_dst() or ds_select_domain() lines from
your config?
Cheers,
Daniel
On 08/01/15 04:07, Yuriy Gorlichenko wrote:
We use 4.3 version.
if(!ds_select_dst($var(setid), 9))
$var(setid)- is variable for setting setid that i get from database with my
own scenario. IT does not matter. You may change it to something like 1,2,
or anthing else.
So as you see setid 2 have 2 servers. I have an issue with this config
I see that you have setid 2 with two addresses, one with weight 10 and
one with weight 50. In total you give the weight 60. The module is
filling up to weight 100 using the last address returned from database,
so you can end up having first address with weight 10 and the second
with weight 90.
