search

vinayseasia / android-rcs-ims-stack

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

SIP BYE exception after an unsucessful file transfer #171

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Description: 
1. User A selects a contact from his/her address book
2. User A selects file transfer option
3. User A selects two files from the internal memory, and two file from the 
external memory list, and select share option
4. User B accepts the invitation
5. User A looses coverage while third file is being transferred.
Funtional steps
3a. User B receives files invitation
4a. User B receives first and second file
5a. User B receives error message, User A has interrupted file transference
5b. User B receives updated capabilities for User A
5c. User B can open received files properly (1st and 2nd)

What do you see instead?
User B does not release the sip session when the file transfer is not performed 
successfully. In fact when the Receiver detects that there is no data sent from 
the Sender, client sends the TCP_FIN in orderto release the MRSP connection but 
it does not sent the BYE request as specified in RCS-e – Advanced 
Communications: Services and Client Specification § 3.4.4 File share error 
cases.

Original issue reported on code.google.com by benoit.j...@gmail.com on 22 Oct 2013 at 9:32