[OpenSIPS-Users] Presence pidf accumulating

Mihai Richard mihai.richard at softvision.ro
Thu Feb 2 17:50:42 CET 2012


Hello,

I¹m having  a bit of a problem with the presence mechanism provided by the
OpenSIPS server. From one device I send information with a PUBLISH and the
pidf xml looks like this:
<?xml version='1.0' encoding='UTF-8'?>
<presence xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid"
xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
xmlns="urn:ietf:params:xml:ns:pidf" entity="test">
    <dm:person id="me">
        <rpid:activities>
            <rpid:note>my status</rpid:note>
            <rpid:other>available</rpid:other>
        </rpid:activities>
    </dm:person>
</presence>
And if I send more statuses, with a different note in activities, the remote
client receives through the NOTIFY a set of statuses instead of the last
one, something like this:
<?xml version="1.0" encoding="UTF-8"?>
<presence xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid"
xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
xmlns="urn:ietf:params:xml:ns:pidf" entity="test">
    <dm:person id="me">
        <rpid:activities>
            <rpid:note>my status</rpid:note>
            <rpid:other>available</rpid:other>
        </rpid:activities>
    </dm:person>
    <dm:person xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" id="me">
        <rpid:activities>
            <rpid:note>older status</rpid:note>
            <rpid:other>available</rpid:other>
        </rpid:activities>
    </dm:person>
    <dm:person xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" id="me">
        <rpid:activities>
            <rpid:note>even older status</rpid:note>
            <rpid:other>available</rpid:other>
        </rpid:activities>
    </dm:person>
</presence>

Does anyone know why the server keeps track of my older statuses?

Thank you,
--
Mihai
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20120202/10841fa5/attachment.htm>


More information about the Users mailing list