Closed Bug 746886 Opened 12 years ago Closed 10 years ago

B2G telephony: Error handling for dropped calls

Categories

(Firefox OS Graveyard :: RIL, defect)

Product:
Firefox OS Graveyard
Component:
RIL
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(blocking-b2g:-, blocking-basecamp:-)

Status:
RESOLVED WORKSFORME
Project Flags:
blocking-b2g -
blocking-basecamp -

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.
Blocks: b2g-telephony
Depends on: 712944
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?
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.
No longer blocks: b2g-telephony
blocking-basecamp: --- → -
Component: DOM: Device Interfaces → RIL
Product: Core → Firefox OS
Version: Trunk → unspecified
Whiteboard: [SUMO-b2g]
blocking-b2g: --- → -
This feature has been done.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.