Hello,
I have a need to deploy Kamailio in AWS in a scenario of this sort:
[Public Internet] <---> Kamailio <---> (Internal AWS servers)
In such a scenario, Kamailio would be multihomed.
Furthermore, in addition to sending out of two distinct network
interfaces, the networking idiosyncrasies of AWS needs to be taken into
account. AWS hosts only have an RFC1918 address homed natively,
front-ended by 1:1 NAT externally. Normally, this is taken care of by
advertised_address, which allows Kamailio to make outward
representations about the network address by which it can be reached
that are different to the IP to which it is bound.
The problem here is that I need to do this conditionally, only on
traffic going out the public interface. It should not be done on
messages going to the "internal AWS servers".
So, the questions that arise are:
1. Is this sane? Any unforeseen effects, e.g. vis-a-vis RR, provided
enable_double_rr is enabled and that two genuinely different network
interfaces are used?
2. Do set_advertised_address()/set_advertised_port() accept PV
arguments, or are they pre-PV "core function folk traditions" in the
same way as rewritehostport() and force_send_socket()?
Thanks!
-- Alex
--
Alex Balashov | Principal | Evariste Systems LLC
1447 Peachtree Street NE, Suite 700
Atlanta, GA 30309
United States
Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
_______________________________________________
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
