I’ve setup Wowza 4.6.0 and use the latest WebRTC sample code to publish/play from the Chrome browser. I enable save incoming stream on Wowza, as well as transcoding to H264/AAC output.
When I use Chrome browser on laptop and publish to WebRTC, the publish stream works fine and I can playback the stream from another browser instance. The SDP and Wowza logs indicate that the codecs used are VPX(VP8) for Video and Opus for Audio. The log shows decode-video-start & decode-audio-start when publishing start.
However, when I use Chrome browser on my Android phone (Samsung Galaxy S7), the publish video stream freezes after a few seconds. When checking SDP and Wowza logs it look like H264 is picked up for Video instead of VPX (Audio is still Opus though). The log only shows decode-audio-start (no decode-video-start) when publishing start.
If I take out H264 support for WebRTC in Application.xml and only leave VP8 as the supported video codec, then my Android phone publishing works fine.
Is this a known issue? Can you reproduce this on your side? Thanks.