Open Bug 1429571 Opened 6 years ago Updated 2 years ago

only configure MID rtp header extension if we receive MID in SDP

Categories

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

Product:
Core
Component:
WebRTC: Signaling
Version:
58 Branch
Type:
enhancement

Tracking

()

People

(Reporter: mjf, Unassigned)

References

Details

Currently we are using mTransportId to setup the MID rtp header extension in MediaPipelineFactory.  However, mTransportId isn't always the MID.  If we didn't receive an MID in SDP, we create mTransportId synthetically in JsepSessionImpl::InitTransport and should not use it for the rtp header extension.
Rank: 15
Priority: -- → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.