Hi Rob,
Thanks for the reply. I was confused as section 13.2.2.3 says:

13.2.2.3 4xx, 5xx and 6xx Responses

   A single non-2xx final response may be received for the INVITE.  4xx,
   5xx and 6xx responses may contain a Contact header field value
   indicating the location where additional information about the error
   can be found.  Subsequent final responses (which would only arrive
   under error conditions) MUST be ignored.

Thanks and Regards,
Peeyush Jain

On Thu, Jun 13, 2013 at 1:09 AM, Rob Day <r...@rkd.me.uk> wrote:
>
> On Tuesday 11 Jun 2013 12:21:58 peeyush jain wrote:
> > Hi all,
> >
> > Should 401 response from uas to Register message contain "contact header".
> > If yes/no , can someone please guide me to the relevant rfc section?
> >
> > Thanks and Regards,
> > Peeyush Jain
>
> I'd say no. Section 19.1.1 of RFC 3261 says:
> "  URIs in Contact header fields have different restrictions depending
>    on the context in which the header field appears.  One set applies to
>    messages that establish and maintain dialogs (INVITE and its 200 (OK)
>    response).  The other applies to registration and redirection
>    messages (REGISTER, its 200 (OK) response, and 3xx class responses to
>    any method)."
>
> which I'd take to imply that Contact headers are only valid on those messages.
>
> I'm not sure what the value of the Contact header would be, if you did have
> one - you wouldn't want to send a list of bindings as you do with the 200
> response, because you shouldn't be providing that information to
> unauthenticated users.
>
> Best,
> Rob
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Sipp-users mailing list
> Sipp-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sipp-users

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users

Reply via email to