[OpenSIPS-Users] mid_registrar in AOR throttling mode and auth

[Andrew]

Hi all
Maybe someone could give me an idea on how to implement additional
authentication in AOR throttling mode.
Current behaviour of mid_registrar in AOR throttling mode:
A device tries to register to OpenSIPs for the first time. Since this is
the first time mid_registrar_save returns 1 and we pass REGISTER to the
asterisk. Auth goes as usual and AOR is saved and contact is added to the
user location table.
Now another device tries to register to the same AOR. mid_registrar_save
returns 2 and adds contact to this AOR without any auth. As a result, an
unknown device can receive calls.
What I would like to achieve: NEW device REGISTER should be passed to main
registrar and contact should be saved after successful auth. Next REGISTER
of this device can be absorbed. I've created the issue on github
https://github.com/OpenSIPS/opensips/issues/3193 but it's not accepted as a
problem.
Big problem: mid_registrar_save immediately saves new contact. New contact
is in the user location table on the next step after mid_registrar_save in
a script! Adding no-reply to the mid_registrar_save flags doesn't help. In
this case OpenSIPS doesn't respond with OK but contact is added anyway.
It's also useless  to pass REGISTER to the main registrar. Contact is added
although the main registrar answers 401 asking for auth and next REGISTER
from the device is just absorbed.
Any ideas how to implement auth for a new device?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20241118/3b028691/attachment.html>