#89 closed defect (fixed)
MESSAGE "Content-Type: typingstate/typing" ??? (non standard => RFC 3994)
| Reported by: | ibc | Owned by: | vadim |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | phapi | Version: | 2.2-RC3 |
| Keywords: | Cc: |
Description
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:
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.
Attachments (1)
Change History (5)
Changed 4 years ago by laurent
comment:1 Changed 4 years ago by laurent
comment:2 Changed 4 years ago by vadim
Seems to be ok...
Please commit it
comment:3 Changed 4 years ago by laurent
- Resolution set to fixed
- Status changed from new to closed
aplied
comment:4 Changed 4 years ago by ibc
It works great now and interoperates perfectly with other clients as Twinkle :)
Thanks.

Is this path correct ?