#76: QuteCom sends too much PUBLISH
---------------------+------------------------------------------------------
Reporter: ibc | Owner: vadim
Type: defect | Status: new
Priority: major | Milestone: QuteCom 2.2-RC4
Component: phapi | Version: 2.2-RC3
Resolution: | Keywords:
---------------------+------------------------------------------------------
Comment(by ibc):
Replying to [comment:12 laurent]:
> Replying to [comment:11 Preeteesh]:
> > In config.xml changing
<sip.p2p.presence><bool>false</bool></sip.p2p.presence> flag to true will
not send publish twice.
> Be carefull : in this way you will not send your mood ...
Vadim, could you please explain with an example what you mean with "send
your mood"? According to [http://tools.ietf.org/html/rfc4480#section-3.5
RFC 4480 section 3.5 (Mood Element)] <mood> element looks like:
{{{
<mood>
<note>I'm ready for the bar BOF!</note>
<sleepy/>
<thirsty/>
</mood>
}}}
AFAIK Qutecom *doesn't* send a <mood> element. Example of PUBLISH body
sent by Qutecom:
{{{
<?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>do not disturb</note>
<contact priority="1">sip:[email protected]</contact>
</tuple>
</presence>
}}}
Also I insist on what I already suggested some time ago: sending two
PUBLISH'es is wrong and makes no sense. Basically when a presence server
receives a second PUBLISH with same <tuple id="azersdqre"> it should
discard the previous one. If "id" was different then the presence server
would aggregate both XML presentities and send both in each NOTIFY for
watchers. For sure this is not the behavior desired.
Please, sending two PUBLISH'es is wrong.
--
Ticket URL: <http://trac.qutecom.org/ticket/76#comment:13>
QuteCom <http://trac.qutecom.org>
_______________________________________________
QuteCom-dev mailing list
[email protected]
http://lists.qutecom.org/mailman/listinfo/qutecom-dev
