Closed Bug 1249319 Opened 10 years ago Closed 10 years ago

SDP does not offer H.264

Categories

(Core :: WebRTC: Networking, defect)

47 Branch
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: robertk54, Unassigned)

Details

Attachments

(1 file)

Attached image firefox_h264.jpg
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.109 Safari/537.36 Steps to reproduce: Tried using our WebRTC web application to make an audio / video call into our WebRTC server. Even though I enabled H.264, Firefox (and Nightly) does not offer H.264. It only offers VP8 which is what gets used. Actual results: Since it does not offer H264 we only negotiate VP8. Expected results: There should be an 'a=rtpmap:126 H264/90000' or 'a=rtpmap:97 H264/90000' entry in the SDP. I have tried media.navigator.video.preferred_codec set to 126 and 97, no change. I have 'OpenH264 Video Codec provided by Cisco Systems, Inc. 1.5.3' installed and active.
SDP Local SDP v=0 o=mozilla...THIS_IS_SDPARTA-47.0a1 4017297639870531877 0 IN IP4 0.0.0.0 s=- t=0 0 a=sendrecv a=fingerprint:sha-256 90:3A:3B:89:84:9D:AF:25:7C:D9:2E:39:89:1D:D1:15:BB:DB:2F:26:32:B7:6F:60:BC:49:35:E2:03:27:B9:A8 a=group:BUNDLE sdparta_0 sdparta_1 a=ice-options:trickle a=msid-semantic:WMS * m=audio 55947 UDP/TLS/RTP/SAVPF 109 9 0 8 c=IN IP4 10.20.129.16 a=candidate:0 1 UDP 2122187007 10.20.137.158 55946 typ host a=candidate:1 1 UDP 2122252543 10.20.129.16 55947 typ host a=candidate:0 2 UDP 2122187006 10.20.137.158 55948 typ host a=candidate:1 2 UDP 2122252542 10.20.129.16 55949 typ host a=sendrecv a=end-of-candidates a=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level a=ice-pwd:ba3e0b41aadd4fe14bd3e703be5ed2c9 a=ice-ufrag:48a75e62 a=mid:sdparta_0 a=msid:{e3d83d0b-1285-43bf-9976-c2d95e920f1b} {7f37c849-d386-4b51-8e4c-81d554216147} a=rtcp:55949 IN IP4 10.20.129.16 a=rtcp-mux a=rtpmap:109 opus/48000/2 a=rtpmap:9 G722/8000/1 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=setup:actpass a=ssrc:2866823359 cname:{b1289048-824b-4b48-ae2a-276e2851b2ed} m=video 55951 UDP/TLS/RTP/SAVPF 120 c=IN IP4 10.20.129.16 a=candidate:0 1 UDP 2122187007 10.20.137.158 55950 typ host a=candidate:1 1 UDP 2122252543 10.20.129.16 55951 typ host a=candidate:0 2 UDP 2122187006 10.20.137.158 55952 typ host a=candidate:1 2 UDP 2122252542 10.20.129.16 55953 typ host a=sendrecv a=end-of-candidates a=fmtp:120 max-fs=12288;max-fr=60 a=ice-pwd:ba3e0b41aadd4fe14bd3e703be5ed2c9 a=ice-ufrag:48a75e62 a=mid:sdparta_1 a=msid:{e3d83d0b-1285-43bf-9976-c2d95e920f1b} {d6822602-7d46-44a0-b353-d940ad258360} a=rtcp:55953 IN IP4 10.20.129.16 a=rtcp-fb:97 nack a=rtcp-fb:97 nack pli a=rtcp-fb:97 ccm fir a=rtcp-fb:120 nack a=rtcp-fb:120 nack pli a=rtcp-fb:120 ccm fir a=rtcp-fb:126 nack a=rtcp-fb:126 nack pli a=rtcp-fb:126 ccm fir a=rtcp-mux a=rtpmap:120 VP8/90000 a=setup:actpass a=ssrc:253500584 cname:{b1289048-824b-4b48-ae2a-276e2851b2ed}
Are you able to reproduce the issue with a clean profile? https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles
Component: Untriaged → WebRTC: Networking
Product: Firefox → Core
Actually, a clean profile is the most likely way to repro this, since you need to wait for the H264 plugin to download/install. Does about:plugins have "OpenH264 Video Codec provided by Cisco Systems, Inc." in it when you see this behavior?
Flags: needinfo?(robertk54)
Ok, I found that this is not a Firefox issue. My problem is in our demo JS code which is pre-processing the SDP before sending it to our server. I was unaware of this code and surprised to find that we would be doing such pre-processing. Thanks for the prompt replies and sorry for the wasted bandwidth.
Flags: needinfo?(robertk54)
No problem, always feel free to let us know if something looks amiss.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: