search

capt-jk / android-rcs-ims-stack

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

RI send and INVITE RESTART instead of a REJOIN #205

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
A establishes a conference  with B.
The conference ends because of time out (A and B receive a BYE)
A goes to chat history and click to the conference
RI send and INVITE RESTART instead of a REJOIN 

The Client should only restart a conference if the respond of the REJOIN is 404.

RI 2.5.15

ps : it seem to be a regression VS 2.5.14
ps2 : the atach file is the same as issue 204

Original issue reported on code.google.com by rcs.capg...@gmail.com on 24 Jan 2014 at 3:09

GoogleCodeExporter commented 9 years ago 
If the session is terminated on the server, the rejoin will always receive a 
404, so you can directly do the restart procedure.

Original comment by jmauffret@gmail.com on 5 Feb 2014 at 1:29

GoogleCodeExporter commented 9 years ago 
If a BYE is sent by the server, why should the device try to rejoin (a 
terminated session) and not perform directly a restart ?
Please give us some feedback to justify a code change ?

Original comment by lemordan...@gmail.com on 10 Feb 2014 at 4:07

GoogleCodeExporter commented 9 years ago 
As describe at chatper 6.3.5.6 Group Chat re-start (Clarification) in document 
: Blackbird-Product-Descrption-Document-v2.0 :

6.3.5.6 Group Chat re-start (Clarification)
When a Group Chat has been closed due to inactivity, it may be restarted at any 
time by any of the participants. In order to do so, *the joyn client will as 
described in [RCC.07 RCS 5.1] try to re-join using the focus Session Identity 
and same Contribution-ID of the previous Group Chat session.* Depending on 
Service Provider policies, the Group Chat may (e.g. in later RCS releases) be 
*automatically restarted* as explained below or a *404 error response will be 
returned*. If a 404 error response is returned the RCS-e client shall initiate 
a new Group Chat re-using the same Contribution-ID and with latest participant 
list it has available for the Group Chat to build the URI-list in the SIP 
INVITE request. If the client is not authorized to (re-) create a group it will 
receive a 403 Forbidden error from the Messaging server including the warning 
text set to '127 Service not authorised' as specified in OMA SIMPLE IM. In that 
case the RCS-e client shall not create a new group chat with the same 
Contribution-ID.

Original comment by rcs.capg...@gmail.com on 14 Feb 2014 at 9:26