Closed
Bug 746886
Opened 13 years ago
Closed 11 years ago
B2G telephony: Error handling for dropped calls
Categories
(Firefox OS Graveyard :: RIL, defect)
Tracking
(blocking-b2g:-, blocking-basecamp:-)
RESOLVED
WORKSFORME
People
(Reporter: ptseng, Unassigned)
References
Details
(Whiteboard: [SUMO-b2g])
If a call is dropped mid-stream, can we also get the fail cause? Should we notify the error? If so, we should make sure we don't notify DISCONNECTED twice.
Reporter | ||
Updated•13 years ago
|
Blocks: b2g-telephony
Depends on: 712944
Reporter | ||
Comment 1•13 years ago
|
||
To test the dropped calls, I take the battery out of the other phone suddenly after the connection is established to simulate the scenario. The state of the call object switches from CONNECTED to DISCONNECTED. |rilRequstError| is 0, which means no error occurs so that the current notification mechanism of error handling doesn't view it as an error and notify the upper layer. The fall cause is CALL_FAIL_ERROR_UNSPECIFIED. Any opinions or suggestions?
Comment 2•13 years ago
|
||
There is a difference from one end of a call going away and the network going away. Hopefully one of our partners has a network simulator we can use to create some of these error cases.
We can test those two cases using qemu.
Updated•12 years ago
|
No longer blocks: b2g-telephony
blocking-basecamp: --- → -
Updated•11 years ago
|
Component: DOM: Device Interfaces → RIL
Product: Core → Firefox OS
Version: Trunk → unspecified
Updated•11 years ago
|
blocking-b2g: --- → -
Comment 4•11 years ago
|
||
This feature has been done.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•