Iñaki Baz Castillo schrieb:
El Friday 15 February 2008 11:01:02 Klaus Darilion escribió:
Iñaki Baz Castillo schrieb:
Hi, I register a X-Lite (TCP client) and a Twinkle (UDP client) behind NAT. I dissable STUN, ICE, keepalive, "discover external address", etc... in both.
They send a REGISTER to my OpenSer with public IP so I enable OPTIONS pinging ifor both (I confirm that "location" table has the same cflags for the you entries and so, all is correct.
But I just see a periodical SIP OPTIONS by UDP for Twinkle. Are they exist in case of TCP?
Looks like this is a limitation of the natpinging. I would think it should work with TCP/TLS too (useful to handle clients which close the TCP connection after some time).
Dan-Pascau said in devel maillist:
"NAT pinging only handles UDP. For TCP there is a flag to set connection persistence to the lifetime of the registration."
Yes. This avoids that openser drops the TCP connection. But if the client is buggy (I remember some problems with SNOM phones) and drops the TCP line after inactivity then it does not help. But maybe we should not take care of dump clients ....:-)