Volkan Hatem wrote: > How are you planning to handle race conditions where "Subscribe expires:0" > is delivered before the original subscribe?
In that case, you get the one notify, and the earlier subscribe fails with a 500 due to out of order CSeq number. But you get the result you wanted. > -volkan > > 2008/11/24 Evgeniy Khramtsov <[EMAIL PROTECTED]> > >> Naarumanchi Kaushik wrote: >> >>> Hi All, >>> >>> In a Subscribe dialog, can we unsubscribe before receiving 200 OK for the >>> subscribe refresh request? >>> Regards, >>> N.V.S.Kaushik. >>> >> Why not? This is a case flow: >> >> F1 |--Subscribe Expires:3600-->| >> F2 |--Subscribe Expires:0----->| >> F1 |<------------OK------------| >> F1 |<----------NOTIFY----------| >> F2 |<------------OK------------| >> F2 |<---NOTIFY terminated------| >> >> I don't see any weird situation here. >> >> -- >> Regards, >> Evgeniy Khramtsov, ProcessOne. >> xmpp:[EMAIL PROTECTED] <[EMAIL PROTECTED]>. >> >> _______________________________________________ >> 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
