Thanks Benny for the prompt reply. I see what you mean, but the thing is I had tried the same exact setup with the XLITE client and it worked fine (i.e. it accepted the Notify messages' CSeq even though it was less than the previous CSeqs of Notifies. I think that maybe in the case of XLITE the program accepts NOTIFY messages with CSeq larger than the last CSeq of last "Subscribe" sent and so hence it would in this case accept the 8945 since it is larger than the 8944 of the refresh subscribe. (somehow the counter resets back to that of the last subscribe CSeq I guess). And by the way, you're saying that the NOTIFY and SUBSCRIBE are two different direction dialogues, which is true, but how do you explain the fact that the NOTIFY msgs that result from SUBSCRIBE messages always have a NOTIFY CSeq = SUBSCRIBE's CSeq + 1 ? . So my point here is: shouldn't PJSIP reconfigure its CSeq counter with that of every SUBSCRIBE sent at every subscription refresh so that it wouldn't reject the CSeq as what happened in my diagram? Anyway I would really appreciate if you could guide me as to where I could find the control code for that behavior in the source. I am thinking of changing the behavior so that it would accept such CSeqs. I looked in the pjsip_simple and pjsua_pres.c but still no luck :S Any help would be greatly appreciated J Thanks again, 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/20080330/fda4a21a/attachment.html
