PJSIP does not use TLS if Record-Route in 200 OK contains "sips:" scheme

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



2011/9/16 Benny Prijono <bennylp at teluu.com>:
> Hi,
>
> https://trac.pjsip.org/repos/ticket/1319 is still on for 1.12.

Thanks, I didn't know it :)


> I'm not convinced about setting the Contact to SIPS (have we discussed
> this before?).

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.

So, I don't ask for PJSIP to use SIPS in Contact header. I just ask
that, in case PJSIP attempts to send a request with top Route (or RURI
if not) having "sips" schema (and optional ;transport=tcp param) it
must use TLS over TCP.

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.
---------------------

Thanks a lot.

-- 
I?aki Baz Castillo
<ibc at aliax.net>



[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux