[sr-dev] TLS: Sip-Routers adds a Record-Route with "sip" scheme rather than "sips"

[Iñaki Baz Castillo]

2011/7/6 Klaus Darilion <klaus.mailinglists at pernau.at>:
> If you do not change the RURI but add a Route header with "sips:" then
> it would influence only the next hop.

Mmmm, imagine this INVITE sent by a UA via TLS:

  INVITE sip:bob at domain.com
  Via: SIP/2.0/TLS
  Route: <sips:myproxy>
  Contact: <sip:alice at 1.2.3.4>

In this case, the UA would send the INVITE via TCP but in-dialog
request from the remote would be delivered by the proxy to alice via
UDP (the Contact header).

AFAIK RFC 5630 states that, in order to send a request via TLS
(without requiring security in all the path) the UAC must use:

  INVITE sip:bob at domain.com
  Via: SIP/2.0/TLS
  Contact: <sips:alice at 1.2.3.4>



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