Paul Kyzivat <[EMAIL PROTECTED]> wrote: ... >> Also, when setting the re-subscription timer you should take into >> account the ammount of time that potentially has passed between when >> the notifier generated the NOTIFY/2xx-to-SUBSCRIBE, and the time >> when you (the subscriber) received it. > > Do you have a proposal for how to do that?
No, not really. When I implemented subscriptions, I tried to do something smart but it turned out to be tricky when the subscription expiration time was short - say 60 (or 10) seconds. Anything under 32s (or 64s as you wrote later on) is probably impossible to handle in a way that never fails. I agree with what you concluded : > ... > make sure that the > expiration times are sufficiently larger than the transport delay so > that the refresh won't be late as a result. This probably means you > always want to send your refresh at least 64s before you think the > subscription will expire. /Fredrik _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
