Open
Bug 901629
Opened 12 years ago
Updated 3 years ago
improve/document how to detect and handle network failure (including IP address changes)
Categories
(Core :: WebRTC: Networking, defect, P4)
Tracking
()
NEW
| backlog | webrtc/webaudio+ |
People
(Reporter: jesup, Unassigned)
Details
Lost of connectivity, IP address changes, NAT resets, etc
We need to provide tools to detect these situations as best we can, and advice/tools for apps to deal with these situations (and also suggestions, like watching incoming video frames, keeping a datachannel up as a verification path to check connectivity, etc.)
We may discuss error report/ handling on Bug 884196.
|
Reporter | |
Updated•10 years ago
|
backlog: --- → webRTC+
Rank: 35
Priority: -- → P3
|
||
Comment 2•8 years ago
|
||
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4
|
||
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•