Hey Alex, Thanks for the response. This is the AWS scenario where there's a 1:1 NAT from the public to private IP.
I've got as far as figuring out how to advertise the public IP. But, when I forward the request to another node inside the cluster, I assume I want to double-RR that request so that my internal SIP application sees the private IP of the instance. Similarly, for outbound traffic, I want to double-RR so the remote party sees the public IP of the host. That's the part I'm struggling with. Best, Colin On Sat, Jun 25, 2016 at 6:12 PM Alex Balashov <abalas...@evaristesys.com> wrote: > Is this the AWS NAT scenario where the public IP is actually not homed on > the host itself, or are you asking about a genuine two-interface scenario? > > Either way, look up the "advertise" option to the "listen" core > configuration directive. > > -- Alex > > -- > Principal, Evariste Systems LLC (www.evaristesys.com) > > Sent from my Google Nexus. > > > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users@lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users >
_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
