Hi Benny, Well it really turned out to be a problem with the openser server. I was using version 1.2.0. An upgrade to version 1.2.2 solved the issue of invalid CSequence numbers after a subscription renewal. What made me wonder and puzzle out in the first place was why did Xlite accept NOTIFY packets with lower CSeqs than expected. The server (prior to 1.2.2) was binding NOTIFY CSeqs to every new subscription CSeq issued by the client and incrementing that until a new subscription arrives; Xlite somehow handled that. Well thanks to PJSIP for complying with RFC 3261 :) Openser 1.2.2 now creates a separated CSeq for NOTIFY msgs (starting with a first CSeq = 1) and increments that on every new NOTIFY issued by it for that very dialogue. PJSIP presence now works perfectly fine :) Regards, Ramzi T. Touma Electrical and Computer Engineering American University of Beirut P.O. Box 11-0236/ 5555 Riad el Solh Square 1107 - 2020 Email: <http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org> rtt00 at aub.edu.lb -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20080402/b9cbcd27/attachment.html
