HI Brett, Thanks for the response .. Have a nice day ..
*Best Regards* *Rakesh Kumar Mohanty* On Fri, Jan 6, 2017 at 8:44 PM, Brett Tate <br...@broadsoft.com> wrote: > As mentioned based upon what you provided, the server returning 401 is > okay. The client just goes through the normal authentication process by > sending REGISTER with higher cseq and new Authorization based upon the > received 401. If the REGISTER continues to fail authentication (causing > 403 or another 401), it could be because of bad auth credentials or a bug > somewhere. > > > > *From:* Rakesh [mailto:rak...@gmail.com] > *Sent:* Friday, January 06, 2017 9:59 AM > > *To:* Brett Tate > *Subject:* Re: [Sip-implementors] SIP REGISTRTION INFO > > > > Hi Brett, > > > > Thanks for the response. So here the UAS should handle it instead > rejecting. > > My case the UE deregister is due to rebooted automatically and after that > UE not able to register . > > > > > *Best Regards* > > *Rakesh Kumar Mohanty* > > > > > > On Fri, Jan 6, 2017 at 7:46 PM, Brett Tate <br...@broadsoft.com> wrote: > > Hi, > > > > Yes; it can change Call-ID. If I recall correctly, much of the Call-ID > reuse stuff mentioned within RFC 3261 section 10 indicates “SHOULD” instead > of “MUST”. See RFC 3261 section 3 for where to look for meaning of > “SHOULD” and “MUST”. > > > > Since deregister removes the binding, I don’t recall if the working group > actually intended Call-ID to remain the same if deregister and then > register within the same boot cycle. > > > > RFC 3261 section 10.2: > > > > “Call-ID: All registrations from a UAC SHOULD use the same Call-ID > > header field value for registrations sent to a particular > > registrar. > > > > If the same client were to use different Call-ID values, a > > registrar could not detect whether a delayed REGISTER request > > might have arrived out of order.” > > > > RFC 3261 section 10.2.4: > > > > “A UA SHOULD use the same Call-ID for all registrations during a > > single boot cycle. Registration refreshes SHOULD be sent to the same > > network address as the original registration, unless redirected.” > > > > *From:* Rakesh [mailto:rak...@gmail.com] > *Sent:* Friday, January 06, 2017 8:48 AM > *To:* Brett Tate > *Subject:* Re: [Sip-implementors] SIP REGISTRTION INFO > > > > Hi Brett, > > > > Thanks for the confirmation .. My question is that can same UE change the > call ID for a new Register request? > > > > BR///Rakesh > > > *Best Regards* > > *Rakesh Kumar Mohanty* > > > > > > On Fri, Jan 6, 2017 at 6:33 PM, Brett Tate <br...@broadsoft.com> wrote: > > > In our case the Call-ID: ee74e9624ebe1844 value us > > differ from the previous one so the UAS should update > > the binding and accept the REGISTER request instead > > rejecting it with 401. > > 401 is associated with authentication. They have the right to generate > 401 if they want. For instance, they might want to change nonce. > > > > > _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
