Re: [SR-Users] set_advertised_address() / set_advertised_port() + PVs?

On 03/23/2016 01:51 PM, Alex Balashov wrote:

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.

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?

I'm not sure if it's sane, but I do this as well.

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()?

I have a main listen=udp:192.168.25.31 advertise PUBLIC:5060

and then when needed...

set_advertised_address("192.168.25.31");

as in...

if ($rd=~"192.168.25") { set_advertised_address("192.168.25.31"); }

--fred