For the first patch -- the behaviour is like that on purpose, because one can
have replicated location records via database and the case can be that register
was processed by one server and records are loaded by another server, there
being different IPs for each servers. Another situation is changing the ip
address and restarting kamailio. If there is no NAT involved, the location
records work fine when that socket field is ignored.
If you want to restrict this behaviour and not allow loading those records,
then add a module parameter to control it.
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/306#issuecomment-135316447
_______________________________________________
sr-dev mailing list
[email protected]
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
