15 Feb
2008
15 Feb
'08
3:17 p.m.
Bogdan-Andrei Iancu schrieb:
Hi Klaus,
I did some test last year with nathelper sending pings over TCP and it
proofed to be non-functional. If the TCP connection is closed (from
client side), the timer process will actually hang trying to open a TCP
connection via NAT....
This brings me to an INO very useful feature request I mentioned some
time ago: For certain kind of scenarios it would be useful to tell
openser to "not open a new TCP connection if there is no existing TCP
connection" - e.g. by having a flag somewhere.
Use cases: natpinging, requests forwarded to TCP clients behind NAT
(e.g. after lookup), ....
regards
klaus
Regards,
Bogdan
Klaus Darilion wrote:
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).
klaus
_______________________________________________
Users mailing list
Users(a)lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users