[SIPForum-discussion] Query about 407 proxy authentication Required in SIP response

[Stephen James]

Generally I have seen 401, but if it is a proxy that is provide authentication, 407 could be received.
 
Stephen James 
sjames_1958 at yahoo.com
 
We are not princes of the earth, we are the descendants of worms, and any nobility must be earned.



________________________________
 From: Durgesh kumar singh <durgeshk1990 at gmail.com>
To: discussion at sipforum.org 
Sent: Monday, September 8, 2014 1:08 AM
Subject: [SIPForum-discussion] Query about 407 proxy authentication Required	in SIP response
 


Hello,


I have been reading about SIP register flow and most of the place i found that whenever any SIP client try to Register then server response with 401 unauthorized and then http-digest authentication field added in our next Register message headers by which our client get register successfully.

In our project when our SIP client try to register then it first passes with a proxy server then to IntraSwitch SIP server.

In our case Registration flow is look like this.


SIP Client                                         SIP Server 

    REGISTER with no authentication
A --------------------------------------------->

    407 Proxy Authentication required

A <--------------------------------------------

     REGISTER with Authentication
A --------------------------------------------->

               200 OK 1 binding

A <--------------------------------------------

So here my question is that is 407 proxy Authentication required SIP response is correct response for SIP registration or it should be 401 Unauthorized ?

Please clear my concept.

Regards,
Durgesh Kumar Singh

_______________________________________________
This is the SIP Forum discussion mailing list
TO UNSUBSCRIBE, or edit your delivery options, please visit http://sipforum.org/mailman/listinfo/discussion
Post to the list at discussion at sipforum.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20140908/26f5552b/attachment-0002.html>