Re: [Sip-implementors] 401 Unauthorized with Require Header?

2018-08-16 Thread Sreekanth
I just thought about it a bit more and Dale is right. I believe the *Require *header should be enough. The REGISTER can be sent to the Registrar server from UAC with the Require header containing the feature name. If the Registrar server supports this, it will respond with a 401. Otherwise the

Re: [Sip-implementors] 401 Unauthorized with Require Header?

2018-08-16 Thread Olle E. Johansson
> On 16 Aug 2018, at 16:44, Paul Kyzivat wrote: > > On 8/16/18 1:21 AM, Sreekanth wrote: >> On Thu, 16 Aug 2018 at 08:31, Dale R. Worley wrote: >>> Sreekanth writes: I am going through the SIP RFC (3261) and couldn't find anything >>> specified regarding the 401 Unauthorized

Re: [Sip-implementors] 401 Unauthorized with Require Header?

2018-08-16 Thread Paul Kyzivat
On 8/16/18 1:21 AM, Sreekanth wrote: On Thu, 16 Aug 2018 at 08:31, Dale R. Worley wrote: Sreekanth writes: I am going through the SIP RFC (3261) and couldn't find anything specified regarding the 401 Unauthorized challenge response from the UAS side during a registration. I wanted to