Loading nathelper module comes with some overhead (including an extra timer process for nat pinging), but even we can live with that, I think it is better to do symmetric signaling by default, because this is like 99% of what I could spot out there so far. The asymmetric singaling should be done for trusted/known peers only, otherwise it expose the system to become part to sort of "reflection" attack -- e.g., send OPTIONS to SIP server to make it flood a particular target with replies by setting Via to the target address.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/commit/aebae41bccaec46d086796301d33223…
Sorry for a lack of clarity in my response. What I tried to patch is the bug that it did not delete all rows, or as expressed clearly by @miconda and @henningw, a unfiltered delete of all rows.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/commit/bf2ecd4dec55d5009e0904392d083e1…
Kamailio adds IP addresses in the record route. When one updates the config to use domains from aliases in record route, other changes have to be done. I do not want to have the config an alternative source for documentation.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/commit/aebae41bccaec46d086796301d33223…
Would it be too expensive to check with nat_uac_test before conditionally enabling this? I'm assuming yes, since this route will statelessly handle most OPTIONS requests and several scanning cases, but I thought I'd ask anyway...
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/commit/aebae41bccaec46d086796301d33223…
If this excerpt from the core docs still holds true: "It is necessary to include the port (the port value used in the “port=” or “listen=” defintions) in the alias definition otherwise the loose_route() function will not work as expected for local forwards", it might be a good idea to use # alias="sip.mydomain.com:5060" here to provide a hint to whomever is reading this.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/commit/aebae41bccaec46d086796301d33223…