Closed
Bug 1037626
Opened 10 years ago
Closed 10 years ago
H.264 SDP code doesn't find the correct fmtp value when negotiating if only mode 1 is supported
Categories
(Core :: WebRTC: Signaling, defect)
Tracking
()
People
(Reporter: jesup, Assigned: jesup)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
5.94 KB,
patch
|
ehugg
:
review+
|
Details | Diff | Splinter Review |
This patch both turns off mode 0 (since we don't actually support it yet), and fixes a bug when an offer you're making an answer to only has mode 1 (it was failing to find the right fmtp entry when checking the packetization-mode value).
We'll want to uplift this to Aurora/32/2.0 so it can respond correctly to offers with mode 1 only (which is what we will generate).
Attachment #8454651 -
Flags: review?(ethanhugg)
Comment 1•10 years ago
|
||
Comment on attachment 8454651 [details] [diff] [review]
H.264 mode 1-only support
Review of attachment 8454651 [details] [diff] [review]:
-----------------------------------------------------------------
lgtm
Attachment #8454651 -
Flags: review?(ethanhugg) → review+
Assignee | ||
Comment 2•10 years ago
|
||
Blocks: WebRTC-OpenH264, 1003040
Target Milestone: --- → mozilla33
Assignee | ||
Comment 3•10 years ago
|
||
We need this for 2.0 - first, we're offering mode 0 and don't actually support it. Second, if offered h.264 mode-1 only, it would fail to connect video at all (and with this on inbound, we will only offer mode 1 from desktop).
It can be tested with http://mozilla.github.com/webrtc-landing/pc_test_h264.html
Updated•10 years ago
|
blocking-b2g: 2.0? → 2.0+
Comment 4•10 years ago
|
||
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 5•10 years ago
|
||
status-b2g-v2.0:
--- → fixed
status-b2g-v2.1:
--- → fixed
status-firefox31:
--- → wontfix
status-firefox32:
--- → fixed
status-firefox33:
--- → fixed
Assignee | ||
Updated•10 years ago
|
Whiteboard: [webrtc-uplift]
You need to log in
before you can comment on or make changes to this bug.
Description
•