Hi Stanisław, OpenSER it is not ignoring the weights - the received records are ordered by weight. The tricky question is about records with the same weight - which to be used? openser is right now using the first returned by the DNS server.
Regards, Bogdan Stanisław Pitucha wrote: > ----- "Sajith T S" <[EMAIL PROTECTED]> wrote: > >> [EMAIL PROTECTED] wrote: >> >> >>> and got 6 calls on asterisk-2 and none on asterisk-1. If I change >>> the order, all calls go to the first host on the list. Shouldn't >>> openser do load-balancing in this scenario? I don't use any options >>> in t_relay(). >>> >> You should use openser dispatcher module for this. >> > > Yes... I've just noticed in > http://www.openser.org/pipermail/users/2007-October/013660.html that openser > basically decided to go against SRV RFC and ignores weights. (RFC says that > clients should sort and select from list of servers, not servers as B.A.I. > suggested if I understood that correctly) > > Anyways - about dispatcher: I couldn't find any description about it's > behavior with call transfers / taking over. I understand that while I'm using > callid-based hash there will be no problems with REFER, because call-id stays > the same and each leg will go to the same server. > But what about INVITE + Replaces: ? I don't really see a way for it to work > just with hashing. Has anyone tested this / has solution? > > PS. sorry Sajith, I replied to you before by mistake > > Thanks, > Stan > > _______________________________________________ > Users mailing list > Users@lists.openser.org > http://lists.openser.org/cgi-bin/mailman/listinfo/users > > _______________________________________________ Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users
