Re: [SR-Users] dispatcher.reload

Hello, you can use the rpc command hash to see what destination is selected. The hash id value does not change, for a user/uri is always the same value. Then the 'hashid % number_of_destination' (modulo operation) is used to pick up the destination from a dispatcher group. If after the reload is

Re: [SR-Users] dispatcher.reload

Hello and thanks for your reply, all. Actually I WANT that behavior :) switching users to other boxes. Thanks! On Thu, 24 Feb 2022 at 07:45, Paolo Visintin wrote: > Hello David, > In my experience yes, the hash policy will be reset after reload but you > can use htable to cache results and avoi

Re: [SR-Users] dispatcher.reload

Hello David, In my experience yes, the hash policy will be reset after reload but you can use htable to cache results and avoid this behavior. Regards Paolo Il giorno mer 23 feb 2022 alle 23:38 David Villasmil < david.villasmil.w...@gmail.com> ha scritto: > Hello guys, > > We're dispatching wi

Re: [SR-Users] dispatcher.reload

Hello, if the dispatcher list stays identical, a dispatcher reload should not affect the hash calculation and distribution to the respective destinations in this algorithm. Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com