Peer connection failed

[Dean_Turner]

The latest chrome build Version 127.0.6533.73 (Official Build) (64-bit) has broken WebRTC

Across all servers, our custom code even the https://www.wowza.com/developer/webrtc/dev-view-publish reports the same error.

Error: Failed to execute ‘setLocalDescription’ on ‘RTCPeerConnection’: Failed to parse SessionDescription. Failed to parse codecs correctly.

Currently unable to fix this.

[Dean_Turner]

if anyone comes across this in the meantime, the issue seems to be with the mungeSDPPublish function from the wowza webrtc-examples, commenting that out at least stops the peer connection failed error and creates a stream

[MICHITOSHI_KATAOKA]

Checking
chrome://webrtc-internals/ with Chrome 127 and 128 beta

It seems setLocalDescription created by wowza sample code of mungeSDPPublish, does not have any
a=rtpmap
line in video section.

Also, createOfferOnSuccess at chrome://webrtc-internals shows, H.264 options but profile-level-id is different than Chrome 126.
42001f -> 42002a
42e01f -> 42e02a
4d001f -> 4d002a
64001f -> 64002a

[Bernd_Backhaus1]

@anyone here, thank you for the reports and your valuable input. We are aware of the issue and investigating, please follow

Incident with Wowza Streaming Engine \ Wowza Video - Wowza WebRTC Publish Page...

for updates.

Thank you!

Regards,
Bernd Backhaus
Wowza Support
WOWZA | The solution you start with, the partner you scale with.

Wowza Video is here! Look at all the new features that will help elevate your business.

Manage your Support cases online
Bookmark our FAQ page
Bookmark our Status page