On Fri, 2009-08-14 at 11:17 -0400, Dale Worley wrote: > > > 2: although the SipPersistentSubscriptionMgr persists the CSEQ of > the > > NOTIFYs it sends, there appears to be a timer involved, such that if > a > > service is restarted soon after sending a NOTIFY, it will use a CSEQ > > which is too small. This causes Polycom sets to reject the new > NOTIFY, > > which in turn causes problem #1. > > My guess is that this is due to the 20 second delay in persisting -- > the > IMDB table is written 20 seconds after the first change is made. What > would be a good solution?
If I recall correctly (and if I'm not remembering something that I meant to do and never got around to), we solved this in the registrar by having it always persist the registration data during the server shutdown. _______________________________________________ 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/
