On Wed, 2009-09-02 at 14:57 -0400, Carolyn Beeton wrote: > Is it acceptible for our stack to deliver NOTIFYs out of sequence? I > can reproduce this sometimes with the SAA feature - unfortunately, the > Polycom sets really don't like it, and between us we drop the > subscription and they do not reestablish it, thus killing the feature. > I have a set of logs which shows two NOTIFYs where the Cseq=25 one is > apparently delivered before the Cseq=24 one. Is this something that > can happen from time to time, and from which we should recover, or > does it indicate a bug in the stack?
In theory it's OK, but it causes problems in practice, as you see. One thing to look at is why two NOTIFYs are being generated so quickly. In theory, that shouldn't happen unless the application above SipSubscribeServer is publishing new content for one URI twice in quick succession. Dale _______________________________________________ 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/
