Hi Benny, You are right. Sorry for my previous post. In fact "+g.poc.talkburst;+g.poc.groupad" are not SIP URI parameters but Header parameters of the 'Contact header'. It seems that when receiving an incoming call the stack tries to parse the full content of the header parameter (i.e. <sip:PoC-ClientA at networkA.net>; +g.poc.talkburst;+g.poc.groupad) but should only try to parse the SIP URI (without header parameters) (i.e. <sip:PoC-ClientA at networkA.net>). Thanks a lot in any case. --javier Benny Prijono wrote: > On Mon, Sep 15, 2008 at 4:52 PM, "Javier Rodr?guez (Genaker)" > <javier.rodriguez at genaker.net <mailto:javier.rodriguez at genaker.net>> > wrote: > > Hi, > > It seems that the pjsip_parse_uri fails to parse an URI if it contains > 'unknown' parameters. > Here is an example of valid SIP URI not parsable (from > OMA-TS-PoC-ControlPlane-V1_0_1-20061128-A): > <sip:PoC-ClientA at networkA.net>; +g.poc.talkburst;+g.poc.groupad > > It seems that (pj_scan_is_eof(&scanner) || > IS_NEWLINE(*scanner.curptr)) returns false. > > > It works fine here! > > Cheers > Benny > > > > Kind regards, > javier > > > ------------------------------------------------------------------------ > > _______________________________________________ > 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 >
