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?
It's a bug. The only sure way to avoid this is to not have two NOTIFY messages outstanding at once... wait until the previous NOTIFY has returned a final status before sending another one. _______________________________________________ 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/
