The issue here is that your carrier is detecting you as a NATed client
and this breaks your ACK routing.
I overloaded the meaning of interfaces. Two sockets (same IP,
different ports) works fine in a multihomed setting.
One socket for internal traffic and one socket (with external
advertised IP)
Hi Ovidiu,
On 18/10/14 00:37, Ovidiu Sas wrote:
Which is bad, it should be the IP of the FS server.
I investigated and I'm not sure this is the issue.
Unfortunately when I named the various addresses it obscured the fact
that the ip address kamailio.int is the IP address of the freeswitch
se
It seems that you SIP provider detects your NAT settings and it is
trying to fix it, which breaks your setup.
See the Contact in the 200OK: Contact:
Which is bad, it should be the IP of the FS server.
See the RURI in ACK: sip:0390156...@kamailio.ext:5061;transport=udp
The IP was switched from int
