Hi Nir, The problem is because the RX buffer is not large enough to receive the whole message. On other platforms, this would cause the whole datagram to be dropped by the OS, but it seems that on Symbian (or due to our code), part of the datagram still goes through to application, causing parsing syntax error. The workaround is to enlarge your RX buffer (PJSIP_MAX_PKT_LEN). While doing this you should enlarge PJ_LOG_MAX_SIZE as well so that large messages can be logged. I've heard few complaints on these, so I think I will enlarge the default value to something like 4000 in the next release. I believe the reason for the large XML message body is because the other (pjsip) user agent didn't un-PUBLISH properly. This has been fixed in the SVN trunk by http://trac.pjsip.org/repos/ticket/364. So I hope we won't get this problem anymore after 1.5. :) Cheers Benny On Fri, Oct 23, 2009 at 5:21 PM, nir elkayam <nir.elkayam at gmail.com> wrote: > hi, > > I am using the presence on symbian, > > In general it work great, but sometimes I don't get the notification, > > attached the log for the wrong norify: > > > > 11:58:37.486?? pjsua_core.c? RX 2000 bytes Request msg NOTIFY/cseq=1 > (rdata0x73be14) from UDP X.X.X.X:30101: > NOTIFY sip:1234 at 82.102.146.171:1025;transport=UDP SIP/2.0 > Via: SIP/2.0/UDP X.X.X.X:30101;branch=z9hG4bK5001.a32805d1.0 > To: <sip:1234 at X.X.X.X>;tag=1JXtkF8YxwvsjXGt.vplyLh2JKS-kSYj > From: <sip:5678@X.X.X.X>;tag=ac8e3903c5f7631bc3ade9c02ee1f772-68d4 > CSeq: 1 NOTIFY > Call-ID: jNILpfGYqVRNlR00TxusIlRzh4j78I5u > Content-Length: 2883 > User-Agent: OpenSIPS (1.5.3-tls (i386/linux)) > Max-Forwards: 70 > Event: presence > Contact: <sip:X.X.X.X:30100> > Subscription-State: active;expires=600 > Content-Type: application/pidf+xml > > <?xml version="1.0" encoding="UTF-8"?> > <presence xmlns="urn:ietf:params:xml:ns:pidf" > xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" > xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" > entity="sip:5678 at X.X.X.X:30101"> > ?<tuple id="pjsfkUq1b7aF6yXAa7WWXROsgvHvSqFHtA"> > ? <status> > ?? <basic>open</basic> > ? </status> > ? <timestamp>2009-09-23T12:00:12.074Z</timestamp> > ? <note>NirBusy</note> > ?</tuple> > ?<dm:person id="pjzNWXa6iUCm-KYW5udQXTF.CL16XOe51J"> > ? <rpid:activities> > ?? <rpid:busy/> > ? </rpid:activities> > ? <dm:note>NirBusy</dm:note> > ?</dm:person> > > ?<tuple xmlns="urn:ietf:params:xml:ns:pidf" > id="pjrmqZAVbMZ6R80tiIfNeIeqKhlt-u7ZNi"> > ? <status> > ?? <basic>open</basic> > ? </status> > ? <timestamp>2009-09-23T11:58:26.535Z</timestamp> > ? <note>NirBusy</note> > ?</tuple> > ?<dm:person xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" > xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" > id="pjrX9pjoryJ5qZaXnc7MvgpELBOZ15vD9U"> > ? <rpid:activities> > ?? <rpid:busy/> > ? </rpid:activities> > ? <dm:note>NirBusy</dm:note> > ?</dm:person> > > ?<tuple xmlns="urn:ietf:params:xml:ns:pidf" > id="pjvN2XvV07DwYPL0BiokNanatuTUvTSpJK"> > ? <status> > ?? <basic>open</basic> > ? </status> > ? <timestamp>2009-09-23T11:57:40.468Z</timestamp> > ? <note>NirBusy</note> > ?</tuple> > ?<dm:person xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" > xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" > id="pjZGk092MxWF-sF7k2SR76qKCffQ8UzLOx"> > ? <rpid:activities> > ?? <rpid:busy/> > ? </rpid:activities> > ? <dm:note>NirBusy< > > > --end msg-- > > 11:58:37.494????????? xml.c? Syntax error parsing XML in line 42 column 19 > > 11:58:37.495?? pjsua_core.c? TX 446 bytes Response msg 488/NOTIFY/cseq=1 > (tdta0x757938) to UDP X.X.X.X:30101: > > SIP/2.0 488 Not Acceptable Here > Via: SIP/2.0/UDP > X.X.X.X:30101;received=X.X.X.X;branch=z9hG4bK5001.a32805d1.0 > Call-ID: jNILpfGYqVRNlR00TxusIlRzh4j78I5u > From: <sip:5678@X.X.X.X>;tag=ac8e3903c5f7631bc3ade9c02ee1f772-68d4 > To: <sip:1234 at X.X.X.X>;tag=1JXtkF8YxwvsjXGt.vplyLh2JKS-kSYj > CSeq: 1 NOTIFY > Accept: application/pidf+xml, application/xpidf+xml > Warning: 399? "Bad PIDF content for presence" > Content-Length:? 0 > > It seems that the XML has some redundency.. > is it a problem of the server? > > > thanks, > nir > > > _______________________________________________ > 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 > >
