1225795 - consider allowing slightly incompatible profile-level-ids

Status: NEW

(Core :: WebRTC: Audio/Video, defect, P5)

Description

[Maire Reavy [:mreavy]]

+++ This bug was initially created as a clone of Bug #1170924 +++

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.73 Safari/537.36

Steps to reproduce:

Firefox calls a legacy device with H264 support(with profile-level-id:42E01F).
Legacy device answers the call(with profile-level-id:42801F).
Firefox fails to setRemoteDescription and gives webrtc error.


Actual results:

When Firefox has an incompatible profile-level-id as mentioned above, simply webrtc engine throws an error.


Expected results:

I am aware that profile-level-id '42E0xx' and '4280xx' incompatible by the H264 RFC, but Firefox should consider allowing profile-level-ids that are only slightly incompatible.

Comment 1

[FredLuart]

Hello,

Is there a solution to force the usage of '4280xx' in Firefox ?
For example, if we modify the SDP before using setLocalDescription, will it be considered by Firefox ?

Comment 2

[Bulk Bug Changes for mreavy's org]

Mass change P4->P5 to align with new Mozilla triage process.