#89: MESSAGE "Content-Type: typingstate/typing" ??? (non standard => RFC 3994)
--------------------+-------------------------------------------------------
Reporter: ibc | Owner: vadim
Type: defect | Status: new
Priority: minor | Milestone:
Component: phapi | Version: 2.2-RC3
Keywords: |
--------------------+-------------------------------------------------------
Hi, I've enabled in "advanced configuration" message typing option, but
Qutecom does it in a non standar way. When typing a message, Qutecom sends
a MESSAGE with:
-----------------
MESSAGE [...]
Content-Type: typingstate/typing
is typing
-----------------
This is really annoying since there is a RFC for this, implemented in most
of the SIP softphones supporting IM:
http://tools.ietf.org/html/rfc3994
For example, the above should be (according to RFC 3994):
------------------
MESSAGE [...]
Content-Type: application/im-iscomposing+xml
<?xml version="1.0" encoding="UTF-8"?>
<isComposing xmlns="urn:ietf:params:xml:ns:im-iscomposing">
<state>active</state>
<refresh>90</refresh>
</isComposing>
------------------
But I've realized that Qutecom *does* support this RFC for *incoming*
MESSAGE's (so if Twinkle or X-Lite is writting a MESSAGE and sends the RFC
3994 typing notification to Qutecom, Qutecom detects it correctly and
shows "Remote user is typing...", that is good.
--
Ticket URL: <http://trac.qutecom.org/ticket/89>
QuteCom <http://trac.qutecom.org>
_______________________________________________
QuteCom-dev mailing list
QuteCom-dev@lists.qutecom.org
http://lists.qutecom.org/mailman/listinfo/qutecom-dev
