I see, since all the connections are TCP, there is no issue with kamailio knowing its public IP? Normally that IP is embedded in VIA headers etc.

I’ve been reading your thread about TCP connection reuse with interest ;)  Will let you know if I find some way around it.

On 10 Nov 2019, at 18:37, Joel Serrano <joel@textplus.com> wrote:

I’m working on something similar, what cloud are you using?

In my case, using GCP, I have a script that queries the metadata API and uses information from there, but for the setup I’m trying out, I use the LB public IP not the VM one. 

I’m curious as to how you plan to get it to work, why would you need the public IP of the VM?

Also, I’m having trouble getting Kamailio to use existing (established) TCP connections when it’s not the initial request... 

I’d love to hear if you get it working!

Cheers,
Joel. 


On Sun, Nov 10, 2019 at 09:23 Mack Hendricks <mack@dopensource.com> wrote:
Each cloud provider acts a little different when it comes to Nat’ing

Sent from my iPhone

> On Nov 10, 2019, at 9:16 AM, Alejandro Recarey <alex@recarey.org> wrote:
>
> Hi, I am trying to get kamailio working cloud provider, autoscaling
> them behind a TCP load balancer.
>
> Is there a way for kamailio to discover its Public IP at startup? Or
> do people generally program their own startup scripts that modify the
> kamailio config file before starting it?
>
> Is there any gotchas you have hit while configuring this setup?
>
> Thank you!
>
> Alex
>
> _______________________________________________
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

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