使用WebRTC、Wowza 4.7.3与FFmpeg实现浏览器摄像头推流的问题

Hey Diego, let's walk through troubleshooting your WebRTC streaming setup with Wowza and FFmpeg—this is a common workflow but has a few gotchas, especially with the versions you're using. Here's what I'd check step by step:

1. Validate Your FFmpeg Command (Critical First Step) #

Since you didn't share your exact FFmpeg command, let's start with a reliable baseline that aligns with your setup, and highlight the non-negotiable flags for VP8/OPUS transcoding to Wowza:

# Example: If capturing directly from a camera (adjust input sources to match your setup)
ffmpeg -f v4l2 -i /dev/video0 -f alsa -i hw:0 \
  -c:v libvpx -b:v 1000k -crf 10 -g 30 -pix_fmt yuv420p \
  -c:a libopus -ar 48000 -b:a 128k -ac 2 \
  -f rtp rtp://[your-wowza-ip]:1935/[your-app-name]/[stream-name]

Key notes here:

• libvpx is the only codec for VP8 in FFmpeg, and yuv420p is required for broad browser compatibility
• OPUS needs a 48kHz sample rate (WebRTC standard) — don't skip ar=48000
• If you're ingesting a pre-captured H.264/AAC stream instead of direct camera input, swap the -i flags to point to that source (e.g., a RTMP input or local file)
• Add -v debug to your command to get detailed logs—look for codec initialization errors or stream dropouts

2. Lock Down Wowza 4.7.3 Configuration #

Wowza 4.7.3 has specific WebRTC-related settings you need to double-check:

• Ensure the WebRTC module is enabled in your application's Application.xml: Look for <Module><Name>ModuleWebRTC</Name><Class>com.wowza.wms.webrtc.module.ModuleWebRTC</Class></Module> in the Modules section
• Confirm your application accepts VP8/OPUS: In Application.xml, under MediaTypes, make sure <MediaType>vp8</MediaType> and <MediaType>opus</MediaType> are listed
• Firewall checks: Wowza uses UDP ports 8000-8001 by default for WebRTC—make sure these are open for both ingest and playback
• For playback, verify your test page's JavaScript uses the correct WebSocket URL: It should look like wss://[your-wowza-ip]:443/[your-app-name]/[stream-name]

3. Rule Out Chrome 66 Canary Issues #

Chrome 66 is an older canary build, and WebRTC implementations have come a long way since then:

• Check chrome://webrtc-internals/—this is your best friend for debugging WebRTC playback issues. Look for ICE connection failures, codec negotiation errors, or packet loss metrics
• Ensure Chrome has camera/microphone permissions for your playback page (check the lock icon in the address bar)
• Try testing with a stable Chrome version (even a newer one) to eliminate canary-specific bugs

4. Debug Transcoding and Stream Integrity #

• First, confirm your FFmpeg build supports VP8/OPUS: Run ffmpeg -codecs | grep vp8 and ffmpeg -codecs | grep opus—you should see DEVI.S (decoding, encoding, video/audio, supported) next to each codec
• Test with a pre-recorded VP8/OPUS file to isolate the issue: Push a known-good .webm file to Wowza with ffmpeg -i test-file.webm -c:v copy -c:a copy -f rtp rtp://[your-wowza-ip]:1935/[your-app-name]/test-stream. If this plays, the problem is with your camera input or transcoding parameters, not Wowza/Chrome

5. Check for Wowza WebRTC Ingest Limitations #

Wowza 4.7.3 has some limitations with WebRTC ingest:

• It doesn't support DTLS 1.3, so make sure Chrome is using DTLS 1.2 (you can check this in chrome://webrtc-internals/)
• If you're having trouble with WebRTC ingest directly, try pushing via RTMP to Wowza first, then let Wowza transcode to VP8/OPUS for WebRTC playback—sometimes this is more reliable with older Wowza versions

内容的提问来源于stack exchange，提问作者Diego T