Confirm
978
edits
Changes
no edit summary
*Scenario #1: There is no other call on-line (current design)<br>When a remote party dials, a new call is generated with its call index (no. 1), and the call state now is CALL_STATE_INCOMING.<br>When user answers/hangs up the call, the call state is eventually pushed to CALL_STATE_CONNECTED/CALL_STATE_DISCONNECTED according to user's decision.
*Scenario #2: There is already a call on-line<br>When the third party dials, a new call is generated with the state of CALL_STATE_INCOMING. Since there is already a call on-line, the new call's index is no. 2. <br>When user answers the new call (call no. 2), its state is going to be transferred to CALL_STATE_CONNECTED. <br>In the meanwhile, the state of the originally connected call (call no. 1) should be forced to CALL_STATE_HELD. <br> *Scenario #3: User wants to hold a call when there's no waiting call<br>User can |HoldCall()| to change the call state from CALL_STATE_CONNECTED to CALL_STATE_HELD. <br>User can |ResumeCall()| to make a call from CALL_STATE_HELD back to <br>CALL_STATE_CONNECTED.
[[Image:Proposal TelephonyCallStates v2.png|842x936px|Proposal of telephony call states to support call holding]]<br>
=== Proposal: Enhance WebTelephony API to hold a call ===
