Closed
Bug 1052850
Opened 10 years ago
Closed 10 years ago
Firefox uses remote PT instead of local PT for received RTP
Categories
(Core :: WebRTC: Signaling, defect)
Core
WebRTC: Signaling
Tracking
()
RESOLVED
FIXED
mozilla34
People
(Reporter: abr, Assigned: abr)
Details
Attachments
(1 file)
|
2.77 KB,
patch
|
jesup
:
review+
|
Details | Diff | Splinter Review |
If Firefox sends an offer, and then receives an answer that uses a different RTP payload type than the one that it sent (for the same codec), then it expects to receive RTP with a PT matching the PT in the answer rather than the one it sent in the offer. This is at odds with RFC 3264: "For sendrecv RTP streams, the payload type numbers indicate the value of the payload type field the offerer expects to receive, and would prefer to send."
|
Assignee | |
Comment 1•10 years ago
|
||
|
|
Assignee | |
Updated•10 years ago
|
Attachment #8471895 -
Flags: review?(rjesup)
|
||
Updated•10 years ago
|
Attachment #8471895 -
Flags: review?(rjesup) → review+
|
|
Assignee | |
Comment 2•10 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/a3f7eb906770
|
||
Comment 3•10 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/a3f7eb906770
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla34
You need to log in
before you can comment on or make changes to this bug.
Description
•