Followon to bug 1390202: Investigate using more of simulcast.cc:GetSimulcastConfig() or our own algorithm for number of temporal layers.
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
I think we need to switch over to using cricket::GetSimulcastConfig to avoid more problems with assertions / crashes like in Bug 1432793. I have some patches in progress to do this.
Assignee: nobody → dminor
Depends on: 1432793
Priority: P3 → P2
Unassigning in case someone gets to this before me.
Assignee: dminor → nobody
You need to log in before you can comment on or make changes to this bug.