20 Aug
2010
20 Aug
'10
8:55 p.m.
2010/8/19 Vadim Lebedev <vadim(a)mbdsys.com>om>:
Diniel i think you'll aggree that in NATed
environment this behaviour is
not really locgical.
The most logical thing to dis in such case is to use the
'force_send_socket' IMO.
Hi, I don't agree. A client sending a SUBSCRIBE/INVITE/REGISTER using
TCP and containing a "Contact" without ";transport=tcp" is *not*
logical at all (even if it's valid according to the exotic RFC 3261).
Regards.
--
Iñaki Baz Castillo
<ibc(a)aliax.net>