Hi I do not thing 403 Forbidden can have Retry-After. 403 usually means the UE is either blocked or not allowed. Retry-After makes sense in 503 Service unavailable.
Regards Ranjit -----Original Message----- From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Shanbhag, Somesh (NSN - IN/Bangalore) Sent: Tuesday, July 14, 2009 9:48 AM To: Pavesi, Valdemar (NSN - US/Boca Raton); ext Dale Worley; Michael Hirschbichler Cc: sip-implementors@lists.cs.columbia.edu Subject: Re: [Sip-implementors] Registration - Challenging Question In such cases 403 Forbidden shall have Retry-After header field giving the number of seconds client has to wait before sending the next REGISTER request. Somesh -----Original Message----- From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of ext Pavesi, Valdemar (NSN - US/Boca Raton) Sent: Monday, July 13, 2009 7:49 PM To: ext Dale Worley; Michael Hirschbichler Cc: sip-implementors@lists.cs.columbia.edu Subject: Re: [Sip-implementors] Registration - Challenging Question If there is 401 back is because the Credentials are not correct: username ,password , realm, nonce... You do need a trace in our system. Normally after some retries ( nounce counter) then there is a final 403 response to stop the loop. Register/401. Valdemar -----Original Message----- From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of ext Dale Worley Sent: Friday, July 10, 2009 4:31 PM To: Michael Hirschbichler Cc: sip-implementors@lists.cs.columbia.edu Subject: Re: [Sip-implementors] Registration - Challenging Question On Thu, 2009-07-09 at 13:33 +0200, Michael Hirschbichler wrote: > UAC Proxy > ------------REGISTER----------------> > <----401 Unauthorized (w challenge)-- > ---REGISTER (w correct Credentials)-> > <----401 Unauthorized (w challenge)-- > > (The credentials are correct and the 401 are no retransmissions) > > How should the client now behave? Should he retry to register using the > Digest from the last "401"? How often should the client retry until he > stops trying to register? The expectation is that an immediate re-REGISTER will not succeed, and that the UA has to wait for some "external" change. So it should send re-REGISTERS at a slow pace, waiting to detect the "external" change. Dale _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors