Closed Bug 1052850 Opened 6 years ago Closed 6 years ago
Firefox uses remote PT instead of local PT for received RTP
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."
Attachment #8471895 - Flags: review?(rjesup) → review+
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla34
You need to log in before you can comment on or make changes to this bug.