bettybop68 / android-rcs-ims-stack

Automatically exported from code.google.com/p/android-rcs-ims-stack
0 stars 1 forks source link

OPTIONS doesn't appear to contain fthttp capability #115

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Enable the File transfer HTTP option on the Profile tab of the Provisioning 
tool
2. Start a file transfer
3.

What is the expected output? What do you see instead?
I expect the transfer to be initiated over HTTP. Instead it is done using MSRP. 
The specific issue that I'm seeing is that the OPTIONS sent to the other 
contact in advance of the exchange doesn't appear to contain the tag for file 
transfers via HTTP (...application.ims.iari.rcs.fthttp). It is contained in the 
REGISTER though.

What version of the product are you using? On what operating system?
2.5.6 running on Android 2.3.5.

Please provide any additional information below.

Original issue reported on code.google.com by iiaGa...@gmail.com on 23 Jul 2013 at 2:22

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
Some clarification on this. I was expecting the capabilities exchange to take 
place when I choose the File Transfer option. However it appears that this 
isn't the case. If I go back to the Capabilities->Request capabilities function 
and request capabilities for my contact, I do see the fthttp capability.

However even after the capability exchange reports the other party supports 
fthttp, the transfer still appears to be happening over MSRP.

Original comment by iiaGa...@gmail.com on 23 Jul 2013 at 2:36

GoogleCodeExporter commented 8 years ago
With the RI (rest tool) all the RCS features are well separated: capabilities 
discovery and services.

FToHTTP is used if remote and local supports the capabilities AND the stack 
settings "Default FT protocol" is set to "HTTP".

Original comment by jmauffret@gmail.com on 23 Jul 2013 at 8:00