Thomas Froment writes: > --> Multiple questions need clarifications here, because people want > to be able to switch from one transport to another, use numeric ip > addresses, and still make the RR work. So, that's why I explained a > typical "workaround" is to put a transport parameter on the RR. (if > the proxy decides to make RR rewriting, it will put just one RR with > the transport used to reach the next element, and when seeing the 200 > OK response, change that transport to the transport used with the > previous element. > It explains you why I said that the "Route set seen by the callee > will be different than the Route Set seen by the callee" when > rewriting. > Double Record-Routing does not solve that problem at all, this is > still a topic to be discussed, and I am open to any suggestion about > this issue.
thanks for the explanation. today at least openser (which is a VERY popular sip proxy), does double rr if transport protocol changes, for example: Record-Route:<sip:192.98.101.10;transport=TCP;r2=on>,<sip:192.98.101.10;r2=on> is also uses transport=tls no matter if it is deprecated or not. but isn't this a local matter within a proxy, i.e., why should anybody else care? -- juha _______________________________________________ Sip mailing list https://www1.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
