BTW, my quarrel with add_contact_alias() vs fix_nated_register() comes from the fact that when forwarding registration onward, Asterisk for example chooses to display the peer's host address as Kamailio's address instead of the device's NATed address or even worse the Private address, which isn't that convenient for a few reasons.

Perhaps somebody knows of a workaround.

On Mon, May 7, 2018 at 9:29 AM, Sergiu Pojoga <pojogas@gmail.com> wrote:
On a second thought, SIP Outbound is client-side oriented, so never mind, I guess.

On Mon, May 7, 2018 at 8:49 AM, Sergiu Pojoga <pojogas@gmail.com> wrote:
Hi Alex,

Very thorough write up, as always. If only this article was available some time ago when I was putting up an edge proxy, would have saved me weeks of frustration in figuring out all these NAT-related aspects and RFC readings (although such an exercise helps understand the problem to its core).

What you may consider adding to your article is the option of the yet not so popular, but in my opinion the "future of NAT-traveral" practice in IPv4 networks, which is the SIP Outbound mechanism.

Best regards,
--Sergiu



On Mon, May 7, 2018 at 7:24 AM, Alex Balashov <abalashov@evaristesys.com> wrote:
Recent repeated questions on this topic have inspired a blog post:

http://blog.csrpswitch.com/server-side-nat-traversal-with-kamailio-the-definitive-guide/

This is a rough cut, and may be edited or expanded later.

--
Alex Balashov | Principal | Evariste Systems LLC

Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users