Open
Bug 1095743
Opened 11 years ago
Updated 3 years ago
JsepSessionImpl should not try to use rtcp-mux for payload types that will cause conflicts
Categories
(Core :: WebRTC: Signaling, enhancement, P5)
Core
WebRTC: Signaling
Tracking
()
NEW
| backlog | webrtc/webaudio+ |
People
(Reporter: bwc, Unassigned)
References
Details
| Reporter | ||
Updated•10 years ago
|
backlog: --- → webRTC+
Rank: 50
Priority: -- → P4
Comment 1•8 years ago
|
||
Mass change P4->P5 to align with new Mozilla triage process.
Priority: P4 → P5
Comment 2•8 years ago
|
||
As we only use PTs 0, 8, 9 and 96-127 I don't think that we are ever going to any conflicting PT from the range 64-80.
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•