JsepSessionImpl should not try to use rtcp-mux for payload types that will cause conflicts

NEW
Unassigned

Status

()

P5
enhancement
Rank:
50
4 years ago
a year ago

People

(Reporter: bwc, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Updated

3 years ago
backlog: --- → webRTC+
Rank: 50
Priority: -- → P4
Mass change P4->P5 to align with new Mozilla triage process.
Priority: P4 → P5
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.
You need to log in before you can comment on or make changes to this bug.