Can you trace the traffic between the server and the clients in those 10
minutes? Is the TCP connection kept alive by any sort of pinging?
Are you using the keep_alive parameter?
[1] http://www.opensips.org/Documentation/Script-CoreParameters-1-11#toc98
Best regards,
Razvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com
On 04/17/2014 05:51 PM, leo wrote:
Hello Razvan,
/From the logs, for me it is pretty clear that the connection does not
exist, therefore OpenSIPS cannot contact your client behind NAT.
After finally managing to call over TCP (after 10 seconds or so),
placing another call succeeds?
/ Yes, normally is taken between 10 to 30 seconds to get the ringing
The strange thing is when the client (the one i try to call) registers for
the first time, the call is established in 2/3 secs (like with UDP)!!!!.
After +/- 8:30 to 9:30 mins (510 to 570 secs) the problem starts.
At the beginning i thought it could be an expiry problem (600 secs) but i've
tried to change it to 86400 secs and the situation doesn't changed.
One more test i've done is to create a linphone account (i don't know if you
know it) and using their SIP server always work... :( . I can't understand
why i can't achieve that with opensips.
--
View this message in context:
http://opensips-open-sip-server.1449251.n2.nabble.com/UDP-vs-TCP-TLS-tp7590719p7590808.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
