Thanks for your replies, It is actually that our UA needs to be able to correctly respond to either situation and I was hoping there would be something in SIP that would do this. It's not a problem though. Just a bit more logic.
Thanks again Steve -----Original Message----- From: Brett Tate [mailto:[EMAIL PROTECTED] Sent: 25 May 2006 14:21 To: 'Stephen Paterson'; [email protected] Subject: RE: [Sip-implementors] WWW-Authenticate and REGISTER > When registering with a registrar many servers will require > that the username provided in Authorization header matches > the username in the To header of the REGISTER. This, although > entirely understandable, is not a mandatory requirement in > SIP or digest authentication in general. My question is this: > > Is there any means by which a registrar can inform the UAC > that this behaviour is required? No parameter has been defined to indicate this. If such a thing is required, it is more of configuration requirement within the registrar and user agent. If you are just trying to indicate the requirement to the user, the requirement text can be placed within the Reason-Phrase of the Status-Line; however not all devices actually expose such text to the user. > I guess it would be either as a parameter in > the WWW-Authenticate header or possibly > another header. If there is, is it mandatory? If you want to define a new parameter, rfc3261 and rfc2617 allow new parameters to be contained within the auth related headers. If you want to make support mandatory, it requires a new option-tag to be defined so it could be included within Require and Supported. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
