Re: [SR-Users] Problems with TCP

2012-02-13 Thread Daniel-Constantin Mierla
Hello, for 1) Is the device behind nat? Do you have tcp connection lifetime parameter value long enough? for 2) is the physical IP a public space IP? Do you have mhomed parameter set? It is a warning saying that the interface returned by OS for connecting to the destination is not in the lis

Re: [SR-Users] Problems with TCP

2012-02-16 Thread Mino Haluz
2) I tried to set mhomed=1, but it has become even worse - No out socket. So I tried to disable it again and force kamailio to listen on physical address as well (so simultaneously on virtual and physical). The error disappeared, but the BYE message is not forwarded, it is processed and onsend even

Re: [SR-Users] Problems with TCP

2012-02-16 Thread Marius Zbihlei
On 02/16/2012 05:26 PM, Mino Haluz wrote: 2) I tried to set mhomed=1, but it has become even worse - No out socket. Hello, mhomed only works for UDP connection. It shouldn't have any effect on TCP. There must be something else. For TCP and multihomed, I think you have to use force_send_sock