Opened 4 years ago
Closed 4 years ago
#162 closed defect (fixed)
Contacts display name get corrupted when using SIP presence
| Reported by: | ibc | Owned by: | laurent |
|---|---|---|---|
| Priority: | critical | Milestone: | QuteCom 2.2-RC4 |
| Component: | GUI | Version: | 2.2-RC3 |
| Keywords: | Cc: |
Description
Hi, using the last trunk version of Qutecom 2.2 the display name (alias) of the contacts get corrupted when receiving a presence NOTIFY. The fact is that the alias is changed to "away" or "online".
For example:
- I create a contact with name "ibc Twinkle" and SIP ID "30001".
- It receives the first NOTIFY (with status "away").
- Now I edit the contact and see SIP ID = "away".
Also the contactlist.xml file contains the following data:
<wgcard version="1.0" xmlns="http://www.openwengo.org/wgcard/1.0"> <name> <first><![CDATA[ibc Twinkle]]></first> </name> <birthday> <date> <day>29</day> <month>10</month> <year>2009</year> </date> </birthday> <address type="home"> </address> <im protocol="SIP"> <id>30001@mydomain.org</id> <alias><![CDATA[away]]></alias> <account>57228e34-b033-4a24-a24f-79317f942209</account> </im> <group><![CDATA[Amigos]]></group> <UUID>5b9b4aa1-0ed2-4886-9625-5713cef14b06</UUID> </wgcard> </contactlist>
The worst is that, after this issue, when Qutecom receives a new NOTIFY for this contact it doesn't update its status. For example, the following XML arrives in a NOTIFY for subscription to user 30001 presence:
<?xml version="1.0" encoding="UTF-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf" entity="sip:30001@mydomain.org">
<tuple id="zonyor">
<status>
<basic>open</basic>
</status>
</tuple>
</presence>
but Qutecom displays the contact as offline with the following visible name: "ibc Twinkle - (away)".
The *same* occurs with other presence status (online and so). So in other cases I see other contacts (as 30005) with modified SIP ID = "online" (or sometimes "30005;online), the status is *always* offline and the display name shown in the contact list is "_USER_ALIAS_ - (online)" but he always appears as offline in fact (so MESSAGE is not possible and so).
This is a terrible issue IMHO. Really nobody has detected it? I've confirmed this bug with latest Qutecom 2.2 version (changeset: 441:32faa7d90a06 - date: Sun Sep 27 16:24:36 2009 +0200) and also with versions ~one month old.
Attachments (1)
Change History (5)
Changed 4 years ago by ibc
comment:1 Changed 4 years ago by ibc
Unfortunatelly it doesn not always occur, but it does occurs randomly, for sure.
comment:2 Changed 4 years ago by vadim
Is there some reliable way to reproduce this?
comment:3 Changed 4 years ago by ibc
I didn't find a reliable way to repdoruce it, in fact it occurs to me in 30% of times. Of course, it's required a SIP presence server.
I'll try to determine a way ot reproduce it.
comment:4 Changed 4 years ago by laurent
- Resolution set to fixed
- Status changed from new to closed

I added a user "SIP ID = 30001" and this is how it looks after receiving a presence NOTIFY