RFC 3261 section 22 discusses various aspects to consider. The last paragraph of section 22.1 is likely of interest.
> -----Original Message----- > From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip- > implementors-boun...@lists.cs.columbia.edu] On Behalf Of Michael > Hirschbichler > Sent: Thursday, July 09, 2009 10:29 AM > To: Rohit Aggarwal > Cc: sip-implementors@lists.cs.columbia.edu > Subject: Re: [Sip-implementors] Registration - Challenging Question > > IMO too, but in this special case, a third REGISTER-request would have > been the solution (long story). > > Is there anywhere (RFCs?) a definition for the correct behaviour? > > br > Michael > > Rohit Aggarwal wrote: > > IMO, there is no point retrying Registration 3^rd time because it is > > highly likely that would also fail. > > > > > > > > Regards > > > > Rohit Aggarwal > > > > Aricent > > > > > > > > -----Original Message----- > > From: sip-implementors-boun...@lists.cs.columbia.edu > > [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of > > Michael Hirschbichler > > Sent: Thursday, July 09, 2009 5:04 PM > > To: sip-implementors@lists.cs.columbia.edu > > Subject: [Sip-implementors] Registration - Challenging Question > > > > > > > > Hi all, > > > > > > > > I have a problem with the following call-flow > > > > > > > > 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? > > > > > > > > Thx in advance and BR > > > > Michael > > > > _______________________________________________ > > > > Sip-implementors mailing list > > > > Sip-implementors@lists.cs.columbia.edu > > > > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > > > > > > ------------------------------------------------------------------------ > > "DISCLAIMER: This message is proprietary to Aricent and is intended > > solely for the use of the individual to whom it is addressed. It may > > contain privileged or confidential information and should not be > > circulated or used for any purpose other than for what it is intended. > > If you have received this message in error,please notify the originator > > immediately. If you are not the intended recipient, you are notified > > that you are strictly prohibited from using, copying, altering, or > > disclosing the contents of this message. Aricent accepts no > > responsibility for loss or damage arising from the use of the > > information transmitted by this email including damage from virus." > > _______________________________________________ > 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
