2011/9/17 Benny Prijono <bennylp at teluu.com>: >> Yes, but honestly, given the comments I've received in this thread in >> IETF SIP maillist: >> ?http://www.ietf.org/mail-archive/web/sip/current/msg27887.html >> >> I strongly prefer to use the non-standard-but-working ;transport=tls >> and use SIP schema rather than SIPS. >> > > That's basically everybody's conclusion. :) Right, it's sad but that's the true :) > By the way, when you use TLS to send request to next hop peer and you > want inbound request to be sent with TLS too, the only solution seems > to be SIP outbound (RFC 5626), which we support. Ok >> Also I suggest updating the ticket in the tracker by adding this text: >> >> --------------------- >> Also consider that "sips:host;transport=tcp" is equivalent to >> "sips:host", as in the abscense of a ;transport param, SIPS schema >> means TLS transport and port 5061. >> --------------------- >> > > That's basically what the ticket does, see the ticket title. Sorry, that's true. Thanks a lot. -- I?aki Baz Castillo <ibc at aliax.net>
