On Sun, Oct 30, 2022 at 6:19 AM Kevin Kennedy <kennedy4...@gmail.com> wrote:
> I have set the ds_select_dst used in the mid_registrar part of the script > to hash the To URI > > $ru = (ds_select_dst(1, *2*, , "default", 1)); > > but I am not seeing exactly how to do this for the INVITE. If I use > ds_select_dst for the INVITE, it just chooses a random destination, > not performing a match on the Registration destination. > > You cannot use ds_select to send INVITE to where the REGISTER was You can make the kv-store visible to MI, and then ul_dump the AOR complete of kv-store Also, you can simply write in a memory hash or in a db table to which destination was the REGISTER going btw, I believe this architecture is fragile, you don't want INVITEs going to a destination related to the one REGISTER was, a lot of bad things can happen if you have such constraints. If you really really really want that, then just go for sharding based on domains or on users ranges, with some fallback schema -giovanni -- Sincerely, Giovanni Maruzzelli OpenTelecom.IT cell: +39 347 266 56 18
_______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users