search

kuldeeplodhi / rcsjta

Automatically exported from code.google.com/p/rcsjta
0 stars 0 forks source link

Bad reason code when group chat reaches the minimum number of active participants #119

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
When group chat reaches the minimum number of active participants, the 
Controlling Function indicates this by including a Reason header field with the 
protocol set to SIP and the protocol-cause set to 410 (e.g.
SIP;cause=410;text=”Gone”) in the SIP BYE request that it sends to the 
remaining participants.
The Core stack abort the GC with a reason code set to ABORTED_BY_INACTIVITY 
instead of ABORTED_BY_REMOTE.
Moreover when a GC is closed for this reason (cause 410), client should not be 
allowed to restart/rejoin the GC.

Initial conditions: A and B are the only participants of an active GC.
Actions: A leaves the GC.

Expected result: 
B receives a SIP Bye with Reason set to cause=410;text=”Gone”
B decodes the SIP Bye reason and aborts the GC with reason code set to 
ABORTED_BY_REMOTE.

Result we got:
B aborts the GC with reason code set to ABORTED_BY_INACTIVITY.

Original issue reported on code.google.com by lemordan...@gmail.com on 26 Jun 2015 at 9:12

Attachments: