RI app: In Rich Call contacts not visible

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Setup ekiga account with device's full mobile number
2. Provision the stack with the account information. Login successful
3. Add a contact. This contact is another device logged in to RCS stack using 
+91xxxxxxxxxx@ekiga.net
4. Initiate voice call between the devices. Both the devices are 3G enabled.
5. Open RI app -> Rich call -> Initiate Image sharing

What is the expected output? What do you see instead?
Added contact should be available in the drop down. I see no contact is listed. 
Attaching the screen shot of the issue.

What version of the product are you using? On what operating system?
2.3.4

Please provide any additional information below.
Same observation for Messaging -> Transfer File
But I can see contacts listed in Capabilities -> Request Capabilities

Because of this problem I am not able to initiate any communication between the 
2 RCS devices.

Original issue reported on code.google.com by moondra....@gmail.com on 8 Dec 2011 at 11:04

Attachments:

• Capabilities.png
• RichCall.png

[GoogleCodeExporter]

It's because the supported capabilities are not exchanged between devices.

Capabilities are exchanged:
- The first time,
- When a new phone number is added in the address book
- When a phone number has changed in the address book
- Periodically (see period in stack settings).

You can force a capability exchange via the RI application also.

Original comment by jmauffret@gmail.com on 8 Dec 2011 at 2:44

• Changed state: Done

[GoogleCodeExporter]

I tried force refresh on the capability exchange using RI app. On clicking 
refresh, it says that "Request has been sent in background for the <mobile> 
number"
But nothing happens.

I checked the sip.txt also on the requesting side and could see that OPTION 
message is being sent but on the receiving side there is no message recvd for 
this. 

Attaching sip.txt of the requesting side (+919945403884)

Original comment by moondra....@gmail.com on 9 Dec 2011 at 8:47

Attachments:

• sip_1.txt

[GoogleCodeExporter]

I have tel-URI format disabled for the above logs. But I checked with tel-URI 
enabled also earlier and found the same problem

Original comment by moondra....@gmail.com on 9 Dec 2011 at 8:50

[GoogleCodeExporter]

Any clues ?? What could be wrong here ??

Original comment by moondra....@gmail.com on 13 Dec 2011 at 8:16

[GoogleCodeExporter]

It seems ekiga's proxy is not processing OPTION message and blindly returning 
200 OK for the OPTION messages. That's why capabilities of my devices logged 
into ekiga are not getting exchanged. How can I proceed in this situation ??

Original comment by moondra....@gmail.com on 13 Dec 2011 at 1:56