Hi Sa?l,
Thanks for the reply.
Yes I was testing our server with SIPSIMPLE client.
Now I know where to look, thanks again.
Cheers
Allen
________________________________________
From: pjsip [pjsip-bounces@xxxxxxxxxxxxxxx] on behalf of Sa?l Ibarra Corretg? [saul at ag-projects.com]
Sent: Thursday, April 11, 2013 7:57 PM
To: pjsip list
Subject: Re: pidf parser problem
On Apr 11, 2013, at 6:40 AM, Allen Zhang wrote:
> Hi,
>
> I got this error:
> '{urn:ietf:params:xml:ns:pidf}tuple': This element is not expected
>
> when parsing this xml document:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:fl="com.imgtec.flow" entity="sip:testuser at domain.com">
> <fl:device-list>
> <fl:url sequence="1" type="application/vnd.imgtec.com.devices+xml">uri</fl:url>
> </fl:device-list>
> <tuple xmlns="urn:ietf:params:xml:ns:pidf" xmlns:agp-pidf="urn:ag-projects:xml:ns:pidf" id="ID-668234b9-eaf1-447a-830b-4cb1374010e5">
> <status>
> <basic>open</basic>
> <agp-pidf:extended>available</agp-pidf:extended>
> </status>
> <agp-pidf:device-info id="urn:uuid:668234b9-eaf1-447a-830b-4cb1374010e5"/>
> <contact priority="0.0">sip%3Atestuser1%40domai.com%3Bgr%3Durn%3Auuid%3A668234b9-eaf1-447a-830b-4cb1374010e5</contact>
> <timestamp>2013-04-11T13:41:27.687658+12:00</timestamp>
> </tuple>
> <dm:person xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" id="ID-40e23d03258ee4c62670c5c1dc373ba3">
> <rpid:time-offset>720</rpid:time-offset>
> <dm:timestamp>2013-04-11T13:41:27.687891+12:00</dm:timestamp>
> </dm:person>
> <dm:device xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" id="ldarzifq">
> <dm:deviceID>urn:uuid:668234b9-eaf1-447a-830b-4cb1374010e5</dm:deviceID>
> <dm:note xml:lang="en">Powered by sipsimple 0.34.0</dm:note>
> <dm:timestamp>2013-04-11T13:41:27.688134+12:00</dm:timestamp>
> </dm:device>
> </presence>
>
> The above document seems to conform to RFC3863. Is this a parser error?
>
The first element in the sequence is the tuple element, but you have that device-list, so tuple is indeed unexpected as a next element. That document looks like generated by our SIP SIMPLE SDK, how did you add the device-list element, manually modifying the etree?
--
Sa?l Ibarra Corretg?
AG Projects
_______________________________________________
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
