> -----Original Message----- > From: Worley, Dale (BL60:9D30) > Sent: Tuesday, November 10, 2009 12:05 AM > > On Mon, 2009-11-09 at 19:55 -0500, Dale Worley wrote: > > If I understand you, the problem is that while the SAA shortens the > > resubscribe interval to 60 seconds so that the application > code gets > > prompt notification if the notifier becomes inaccessible, the > > SipSubscribeClient's "retry" code takes considerably longer than 60 > > seconds to give up attempting to re-SUBSCRIBE and notify the > > application of subscription failure. > > My belief is that the SAA application code shortens the > subscription refresh time to 60 seconds, whereas the > re-SUBSCRIBE retry sequence takes more than 5 minutes. But > it is clear that there is no value to attempting to > re-subscribe after the (known) termination point of the > subscription. So if we modify SipSubscribeClient in this > way, it will start resubscribing at about 2/3 of the > expiration point, 40 seconds, but if it reaches the 60 second > point, it will stop attempting to resubscribe, and will > report the subscription as having terminated. (It will > attempt a new subscription, but the old subscription will be > reported to the application code as having ended.) This > should give the effect you want. > > Dale > Sounds good. The SAA shortens the subscription time to 300 seconds (5 minutes), which is the shortest value recommended in the draft.
Carolyn _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
