----- Original Message ----- From: "Paul Kyzivat" <[EMAIL PROTECTED]> <snip> > A way that is conformant with 3261 is to use the > ability to embed a sip header in a sip URI. This is > something like: > > Contact: <sip:[EMAIL PROTECTED]:proxy.example.com%3E> >
RFC 3261 actually discourages this sort of thing. Section 19.1.5 says: An implementation SHOULD NOT honor any requested Route header field values in order to not be used as an unwitting agent in malicious attacks. _______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
