[OpenSIPS-Users] Presence: "xmlns" attributes inside <tuple> element not compliant to RFC3863
Saúl Ibarra Corretgé
saul at ag-projects.com
Mon Mar 10 20:45:09 CET 2014
Hi,
On Mar 10, 2014, at 8:15 PM, Martin Stock wrote:
> Hi guys,
>
> I updated my OpenSIPS server from version 1.6.4 to version 1.10. Nearly everything is working. I only have some problems with the presence stuff: IMHO the structure of XML presence object is not correct.
>
> Working presence body (OpenSIPS 1.6.4):
> --- SNIP ---
> <?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:rp="urn:ietf:params:xml:ns:pidf:rpid" entity="sip:10 at domain">
> <tuple id="t48d84e51">
> <status>
> <basic>closed</basic>
> </status>
> <dm:person id="t48d84e51">
> <status>
> <basic>open</basic>
> </status>
> <rp:activities>
> <rp:Away/>
> </rp:activities>
> </dm:person>
> <timestamp>2014-03-07T16:49:30Z</timestamp>
> </tuple>
> </presence>
> --- SNAP ---
>
> Bad presence body (OpenSIPS 1.10):
> --- SNIP ---
> <?xml version="1.0"?>
> <presence xmlns="urn:ietf:params:xml:ns:pidf" entity="sip:10 at domain">
> <tuple xmlns="urn:ietf:params:xml:ns:pidf" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:rp="urn:ietf:params:xml:ns:pidf:rpid" id="t1e8c1196">
> <status>
> <basic>closed</basic>
> </status>
> <dm:person id="t1e8c1196">
> <status>
> <basic>open</basic>
> </status>
> <rp:activities>
> <rp:Away/>
> </rp:activities>
> </dm:person>
> <timestamp>2014-03-07T16:50:21Z</timestamp>
> </tuple>
> </presence>
> --- SNAP ---
>
>
> With OpenSIPS 1.10 the namespace attributes are not defined inside the <presence> element. Referring to RFC3863, Section 4.1.1 (https://tools.ietf.org/html/rfc3863#page-5) IMHO this is not intended.
I'm not sure what you mean. What attributes are not defined?
> Also the encoding Header is missing. This is a bad style.
>
I'm not sure when the encoding went, but yes, it should have been there, that's a bug.
> I don't find any UA that works with this <presence> element.
>
Any client based on SIP SIMPLE Client SDK (such as Blink) works with those documents.
> Is this a bug or are there options to tweak this?
>
What do you need to tweak? (the encoding bug aside)
Regards,
--
Saúl Ibarra Corretgé
AG Projects
More information about the Users
mailing list