> In such a case UAC and NOTIFIER would destroy then SUBSCRIBE > dialog quietly.
NOTIFIER will destroy the dialog as per RFC3265. But how/why did the UAC destroy subscribe dialog? I think it has to wait for the NOTIFY. > Now my questions are - > 1. Does the proxy server have to start a timer for receipt of NOTIFY? > 2. What should be the value of such a timer, if any? NOTIFY can come after quite a long time (authorization may take a long time, if interacting with user, a primary reason that subscription-state is *finally* conveyed in a NOTIFY message, a separate transaction) > 3. Won't this timer be, if there's any, similar to session-expires timer? Anyway, subscribe dialog lifetime is bound (even at proxy, if dialog stateful) based on expires header 2xx response for subscribe. So I don't think any other timer is required. On Mon, Dec 14, 2009 at 5:43 PM, Dushyant Dhalia <[email protected]> wrote: > The scenario is as follows - > > 1. UAC sends SUBSCRIBE. > 2. Proxy forwards SUBSCRIBE to the NOTIFIER. > 3. NOTIFIER sends 200 (OK) which is received by the UAC. > 4. NOTIFIER sends NOTIFY which is lost, retransmissions are also lost. > > As per RFCs 3265 and 5057 subscribe usage should be destroyed in such a > scenario. See sec. 4.2 of RFC 5057 (NOTIFY or refresh-SUBSCRIBE request > timeout). In such a case UAC and NOTIFIER would destroy then SUBSCRIBE > dialog quietly. > > Now my questions are - > 1. Does the proxy server have to start a timer for receipt of NOTIFY? > 2. What should be the value of such a timer, if any? > 3. Won't this timer be, if there's any, similar to session-expires timer? > > Regards, > Dushyant P S Dhalia, > Rancore Technologies, INDIA > > -- > "When work is a pleasure, life is a joy! When work is duty, life is > slavery." > > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
