Wowza Community

RTMP ingest to WebRTC in 4.8

I just tried the suggested RTMP ingest to WebRTC and subscribing fails.

  • Added support for RTMP/RTSP/SRT ingest and WebRTC output

I get this error on the play sample. Exactly like I am experiencing with IOS publishing right now.

"‘setRemoteDescription’ on ‘RTCPeerConnection’: Failed to set remote offer sdp*: Failed to set remote video description send parameters* "

Here is the full offer and error. There is no candidate and the high h264 profile level which is breaking. The same result with IOS publishing I think.

webrtc-subscriber-7.2.7.js:9510 getOffer: v=0

o=WowzaStreamingEngine-next 192590802 2 IN IP4 127.0.0.1

s=-

t=0 0

a=fingerprint:sha-256 01:80:56:E4:BB:8A:F0:96:6C:21:B9:91:98:7E:39:3E:0E:E6:7A:A3:7F:D5:FB:7F:D0:2C:9C:14:9A:15:94:C7

a=group:BUNDLE video

a=ice-options:trickle

a=msid-semantic:WMS *

m=video 9 RTP/SAVPF 97

a=rtpmap:97 H264/90000

a=fmtp:97 packetization-mode=1;profile-level-id=64C01F;sprop-parameter-sets=Z2QAH6zZQFAFuhAAAAMAEAAAAwPI8YMZYA==,aO+8sA==

a=framerate:30.0

a=control:trackID=1

c=IN IP4 0.0.0.0

a=sendrecv

a=ice-pwd:b41a180f0016e1a4fb2ded7a023841d1

a=ice-ufrag:479ac369

a=mid:video

a=msid:{ebd47bfc-8e8a-4024-8603-5822297091c7} {0de5c4c2-1095-407a-acea-fed260e5ac8a}

a=rtcp-fb:97 nack

a=rtcp-fb:97 nack pli

a=rtcp-fb:97 ccm fir

a=rtcp-mux

a=setup:actpass

a=ssrc:661197176 cname:{80b4f15f-90a8-4fc7-a06b-7794f43899b3}

17:34:04.726 webrtc-publisher-7.2.7.js:2144 simple-peer [6955d08] signal() +0ms

17:34:04.729 webrtc-publisher-7.2.7.js:2144 simple-peer [6955d08] destroy (error: InvalidAccessError: Failed to execute ‘setRemoteDescription’ on ‘RTCPeerConnection’: Failed to set remote offer sdp: Failed to set remote video description send parameters.) +4ms

17:34:04.731 webrtc-subscriber-7.2.7.js:9837 Error: InvalidAccessError: Failed to execute ‘setRemoteDescription’ on ‘RTCPeerConnection’: Failed to set remote offer sdp: Failed to set remote video description send parameters.

at makeError (webrtc-publisher-7.2.7.js:8017)

at webrtc-publisher-7.2.7.js:8219

It’s the same error with webrtc publisher if the H264 level isnt filtered to “42e01f”, It does not like 64C028. Wowza refuses to send candidates.

getOffer: v=0

o=WowzaStreamingEngine-next 1209965586 2 IN IP4 127.0.0.1

s=-

t=0 0

a=fingerprint:sha-256 01:80:56:E4:BB:8A:F0:96:6C:21:B9:91:98:7E:39:3E:0E:E6:7A:A3:7F:D5:FB:7F:D0:2C:9C:14:9A:15:94:C7

a=group:BUNDLE video audio

a=ice-options:trickle

a=msid-semantic:WMS *

m=video 9 RTP/SAVPF 97

a=rtpmap:97 H264/90000

a=fmtp:97 packetization-mode=1;profile-level-id=64C028;sprop-parameter-sets=Z2QAKKwrQDwBE/LCAAADAAIAAAMAeBtBEI1A,aM48MA==

a=framerate:30.0

a=control:trackID=2

c=IN IP4 0.0.0.0

a=sendrecv

a=ice-pwd:bc7f56704821b069aef1a0d63a4f85bb

a=ice-ufrag:de4af493

a=mid:video

a=msid:{d08b713c-5af1-4f7a-b920-14fa3ece2e78} {2249dbee-a68a-440f-b17c-7d3d8106a326}

a=rtcp-fb:97 nack

a=rtcp-fb:97 nack pli

a=rtcp-fb:97 ccm fir

a=rtcp-mux

a=setup:actpass

a=ssrc:478676847 cname:{fc9d1ffd-bbb3-4c3a-9db7-784ef765e62a}

m=audio 9 RTP/SAVPF 96

a=rtpmap:96 OPUS/48000/2

a=control:trackID=1

c=IN IP4 0.0.0.0

a=sendrecv

a=ice-pwd:bc7f56704821b069aef1a0d63a4f85bb

a=ice-ufrag:de4af493

a=mid:audio

a=msid:{d08b713c-5af1-4f7a-b920-14fa3ece2e78} {d6e91bcf-44a6-4888-879e-d1c39620b467}

a=rtcp-mux

a=setup:actpass

a=ssrc:745328323 cname:{fc9d1ffd-bbb3-4c3a-9db7-784ef765e62a}

A working SDP that sends candidates

getOffer: v=0

o=WowzaStreamingEngine-next 1190238603 2 IN IP4 127.0.0.1

s=-

t=0 0

a=fingerprint:sha-256 01:80:56:E4:BB:8A:F0:96:6C:21:B9:91:98:7E:39:3E:0E:E6:7A:A3:7F:D5:FB:7F:D0:2C:9C:14:9A:15:94:C7

a=group:BUNDLE video audio

a=ice-options:trickle

a=msid-semantic:WMS *

m=video 9 RTP/SAVPF 97

a=rtpmap:97 H264/90000

a=fmtp:97 packetization-mode=1;profile-level-id=42C01F;sprop-parameter-sets=Z0LAH2MjUBaGrzwDwiEagA==,aGzjyA==

a=control:trackID=2

c=IN IP4 0.0.0.0

a=sendrecv

a=ice-pwd:d2ae4d65f1629734f12f4ab1cfe972f5

a=ice-ufrag:6ea7c8cf

a=mid:video

a=msid:{e06c90e3-d7b8-4b3b-bb7d-6c410a5d0b15} {2936a891-8d75-48a8-acf8-75e272df61d9}

a=rtcp-fb:97 nack

a=rtcp-fb:97 nack pli

a=rtcp-fb:97 ccm fir

a=rtcp-mux

a=setup:actpass

a=ssrc:747857431 cname:{03801209-e571-4c72-a2dd-081aaa0ad8ed}

m=audio 9 RTP/SAVPF 96

a=rtpmap:96 OPUS/48000/2

a=control:trackID=1

c=IN IP4 0.0.0.0

a=sendrecv

a=ice-pwd:d2ae4d65f1629734f12f4ab1cfe972f5

a=ice-ufrag:6ea7c8cf

a=mid:audio

a=msid:{e06c90e3-d7b8-4b3b-bb7d-6c410a5d0b15} {7123c00d-9e68-4140-8ea2-1e7cdba2c6aa}

a=rtcp-mux

a=setup:actpass

a=ssrc:1828352266 cname:{03801209-e571-4c72-a2dd-081aaa0ad8ed}

We just published a new article on this today and maybe this will help:

https://www.wowza.com/docs/ingest-rtsp-srt-or-rtmp-streams-into-wowza-streaming-engine-for-playback-with-webrtc

If not, send us a support ticket and we’ll take a closer look. Tech support doesn’t debug in the forums.

I found this. I have that constraint configured. Still wont subscribe

https://www.wowza.com/community/questions/44054/ingest-via-rtmp-and-play-via-webrtc.html