Open Bug 1253706 Opened 4 years ago Updated 5 months ago

Implement RTCPeerConnection.setConfiguration

Categories

(Core :: WebRTC: Signaling, enhancement, P3)

enhancement

Tracking

()

Tracking Status
firefox47 --- affected

People

(Reporter: jib, Unassigned)

References

(Blocks 3 open bugs, )

Details

(Keywords: dev-doc-needed, parity-chrome, parity-safari)

Today people set their config in the RTCPeerConnection constructor, so setConfiguration is only needed to reconfigure an existing peer connection.
Rank: 29
Priority: -- → P2
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
We need this feature to update ICE server list. 
See: https://github.com/versatica/mediasoup-client/issues/28

Is there any alternative way howto update ICE server list or the turn server credential?
Blocks: 1533015
Blocks: 1533017

Setting parity keywords.
We got support info for this wrong in our docs and a user reported: "Because of this bug, Firefox does not fit in our new security concept where the WebRTC user gets an generated username and password for a TURN server,"

See https://github.com/mdn/browser-compat-data/pull/4075

Type: defect → enhancement
You need to log in before you can comment on or make changes to this bug.