2011/4/1 Peter Krebs <[email protected]>: > To clarify my question, let's consider that the URI in your > example includes optional values, e. g. > > sip:user:[email protected] > ;transport=udp;user=ip;method=INVITE;ttl=123&header=some%20header > > What value should be used in the calculation of str2 in the <sip uri> part, > the whole URI as string with all optional values in the exact order they are > given above or just the mandatory parts (which would be " > sip:[email protected]" or the one in your example without the user)?
Hi, AFAIK matching request URI and authorization "uri" field is mostly used in HTTP world, but in SIP it makes no so sense. I know about some SIP servers that doesn't require both fields to match. Probably, if SIP protocol would define a custom authentication mechanism (rather than reusing HTTP digest) no "uri" field would exist in the authentication exchange. -- Iñaki Baz Castillo <[email protected]> _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
