Hi Vali, yeah it's a bug alright (or rather a bug introduced by some other fixes). I just fixed this in http://trac.pjsip.org/repos/ticket/842. Sorry for the late response, and for the few hours of debugging. :) cheers Benny On Sun, Apr 19, 2009 at 9:01 AM, Tom?? Valenta <vali at kamarad.cz> wrote: > Hello, > > I have found a bug in function int_parse_status_line in file sip_parser.c. > I was trying to use attended call transfer and trace status of the transfer > via event subscription (pjsua-lib's on_call_transfer_status). But with each > client I tested I was getting "Warning: received NOTIFY with invalid > message/sipfrag content", even with pjsua. After few hours of debugging I > found out the bug is in int_parse_status_line function. Suppose NOTIFY > message "SIP/2.0 200 OK". On line 1570 > > parse_sip_version(scanner); > > would eat "SIP/2.0" from the scanner buffer. Then > > pj_scan_get( scanner, &pconst.pjsip_DIGIT_SPEC, &token); > > throws an exception because the scanner->currptr points to the whitespace > in front of status code "200". I solved the problem by adding > pj_scan_skip_whitespace: > > parse_sip_version(scanner); > pj_scan_skip_whitespace(scanner); > pj_scan_get( scanner, &pconst.pjsip_DIGIT_SPEC, &token); > > - Vali > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip at lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20090512/c345f56d/attachment.html>
