Hello guys,

also kamilio is running on a container with hostNetwork: true so it should use the correct port.

The VIA looks ok (advertised ip and port are there)

Regards,

David Villasmil



On Tue, Sep 10, 2024 at 12:50 PM David Villasmil <david.villasmil.work@gmail.com> wrote:
Hello guys,

maybe i need to add that i'm sending the call out from the internal fs using the outbound_proxy parameter.


Regards,

David Villasmil



On Tue, Sep 10, 2024 at 12:31 PM David Villasmil <david.villasmil.work@gmail.com> wrote:
Hello guys,

i'm seeing something weird, and i'm working if you can let me know.
I have a kamailio in AWS with a private IP listening on several sockets:

Listening on
             udp: 10.1.2.36:5070
             udp: 10.1.2.36:5080
             udp: 10.1.2.36:5160 advertise 4.3.2.1:5160
             udp: 0.0.0.0:5066
             tls: 10.1.2.36:443 advertise sip.something.com:443
             tls: 10.1.2.36:444 advertise sip.something.com:444
             tls: 10.1.2.36:5061 

When forwarding a udp invite received on 10.1.2.36:5080 to a public ip provider say on 8.8.8.8:5060, i'm forcing the outgoing socket with force_socket via 10.1.2.36:5160. But the outgoing invite does NOT use 5160, it uses some random port...

Anybody knows why this might be?

my problem is, that call goes to freeswitch... call is setup properly and connects fine. But 15 minutes later the end provider sends back a reINVITE, which freeswitch then sends TO THE RANDOM PORT kamailio used to send the INVITE... but by this time kamailio doesn't seem to even see the packet...

help is greatly appreciated!

David

Regards,

David Villasmil