search

shadowsnap / doubango

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

Call session state issue #363

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Reproduction steps
1. Place a call from Device A to Device B.
2. End the call from Device A.
3. Answer the call in Device B at the same time.

Result
- The call is still established, but Device A has requested that the library 
end the session.
- The session state is INVITE_EVENT_TERMWAIT instead of INVITE_EVENT_CONNECTED, 
when the call is established in this fashion.
- -[NgnInviteSession isActive] returns NO, despite the fact that the call 
session is established (and you can hear sound from the call session).
- As a result, the logic of our UI is incorrect.

Expected Behaviour
- -[NgnInviteSession isActive] should return correct session information.
- The session state should reflect correct value.
- Call session should not be established if one side hangs up the call.

Original issue reported on code.google.com by boss...@yahoo.fr on 26 Mar 2014 at 6:53

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago

Original comment by boss...@yahoo.fr on 26 Mar 2014 at 6:56

Attachments: