Your interpretation basically sounds correct. The 423 is not applicable. The notifier needs to send NOTIFY before Timer N expires.
Using "probation" and retry-after might produce the desired behavior. It would basically allow obtaining approval/rejection during the retry-after intervals. If they try after approval, it could be granted or rejected. > -----Original Message----- > From: Jānis Rukšāns [mailto:janis.ruks...@gmail.com] > Sent: Monday, February 10, 2014 3:51 PM > To: sip-implementors > Subject: [Sip-implementors] SUBSCRIBE state polling and user > authorization > > Hi all, > > Suppose a subscriber is polling a resource, which according to RFC 6665 > is done by sending SUBSCRIBE with Expires set to 0. What is the > notifier > behaviour if it cannot accept the request immediately, eg. it requires > authorization from the user? > > If my understanding of RFC 6665 is correct, such requests will always > fail with Subscription-State: terminated;reason=giveup (or equivalently > reason=timeout) because the subscription has already expired. > > Thanks, > Jānis > > _______________________________________________ > Sip-implementors mailing list > Sip-implementors@lists.cs.columbia.edu > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors -- This email is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. If you are not the intended recipient and have received this email in error, please notify BroadSoft, Inc. immediately by replying to this message, and destroy all copies of this message, along with any attachment, prior to reading, distributing or copying it. _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
