Open Bug 1017886 Opened 11 years ago Updated 3 years ago

config & troubleshooting if we change conduits when active - renegotiation & negotiation needed events in the Peer Connection handshake

Categories

(Core :: WebRTC: Networking, defect, P3)

Product:
Core
Component:
WebRTC: Networking
Type:
defect

Tracking

()

Milestone:
mozilla35
Blocking Flags:
backlog webrtc/webaudio+

People

(Reporter: shell, Unassigned)

References

Details

(Whiteboard: [investigation])

config and troubleshooting if we change conduits when active - currently it blows apart
Summary: configuration and troubleshooting if we change conduits when active → config & troubleshooting if we change conduits when active - renegotiation & negotiation needed events in the Peer Connection handshake
I believe this isn't needed for switching cameras
Priority: P1 → P2
Target Milestone: mozilla33 → mozilla35
backlog: --- → webRTC+
Rank: 25
Whiteboard: [investigation, p=2] → [investigation]
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.