#170: Qutecom should use <rpid:activities><rpid:busy/></rpid:activities> rather
than <note>busy</note>
--------------------+-------------------------------------------------------
Reporter: ibc | Owner: vadim
Type: defect | Status: new
Priority: major | Milestone: QuteCom 2.2-RC4
Component: phapi | Version: 2.2-RC3
Keywords: |
--------------------+-------------------------------------------------------
Qutecom doesn't interoperate well with other softphones as EyeBeam since
Qutecom doesn't implement the RFC 4480 (RPID: Rich Presence Extensions).
For example, Qutecom sends the following PUBLISH body when setting "busy"
status:
{{{
<?xml version="1.0" encoding="UTF-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf"
entity="sip:[email protected]">
<tuple id="azersdqre">
<status><basic>open</basic></status>
<note>busy</note>
<contact priority="1">sip:[email protected]</contact>
</tuple>
</presence>
}}}
The element "<note>busy</note>" is just a text note to be read by the
human, nothing else, it won't be interpreted by the softpone as a specific
status (Qutecom does it but it's wrong).
The real specification to indicate the "advanced" presence status is the
RFC 4480 (which also requires RFC 4479). Eyebeam, which implements it,
sends the following PUBLISH body when setting "busy" status:
{{{
<?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'
xmlns:c='urn:ietf:params:xml:ns:pidf:cipid'
entity='sip:[email protected]'>
<tuple id='t2267e46e'>
<status>
<basic>open</basic>
</status>
</tuple>
<dm:person id='pdc5ba422'>
<rpid:activities>
<rpid:busy/>
</rpid:activities>
<dm:note>working at the office</dm:note>
</dm:person></presence>
}}}
As you can see, RFC's 4479 and 4480 statesthat the advances presence
status and the user custom text note must be contained into a <dm:person>
node (xmlns:dm='urn:ietf:params:xml:ns:pidf:data-model') rather than be
contained into the <tuple> node.
RFC 4479 (A Data Model for Presence) explains that <tuple> node must just
be used to indicate '''service''' status. In Qutecom, as SIP softphone, it
means:
* <basic>open</basic>: My voice/IM is open, you can try it.
* <basic>closed</basic>: My voice/IM is closed, don't try it.
RFC 4479 also explains that <person> node must be used to indicate
'''human''' status and custom note (as explained above).
--
Ticket URL: <http://trac.qutecom.org/ticket/170>
QuteCom <http://trac.qutecom.org>
_______________________________________________
QuteCom-dev mailing list
[email protected]
http://lists.qutecom.org/mailman/listinfo/qutecom-dev
