Problem connecting Android Chrome browsers

162 views
Skip to first unread message

ryk...@gmail.com

unread,
Dec 7, 2021, 11:28:16 AM12/7/21
to discuss-webrtc
All of a sudden (probably linked with Android Chrome 96)

We can't connect any Android devices.

User A Chrome 96, Mac
User B Chrome 96, Android

User B sends offer to User A.

When User A sets setRemoteDescription from the offer we get the following error:

DOMException: Failed to execute 'setRemoteDescription' on 'RTCPeerConnection': Failed to set remote offer sdp: Failed to set remote video description send parameters for m-section with mid='1'.

Any thoughts on what might have happened? Our code hasn't changed at all!
I've seen some similar posts relating to codec issues. But these were mainly focused on Java. So any thoughts on browser based WebRTC would be great,

Thanks

The full SDP is:
v=0
o=- 4415806538502343826 2 IN IP4 127.0.0.1
s=-
t=0 0
a=group:BUNDLE 0 1 2
a=extmap-allow-mixed
a=msid-semantic: WMS OGEhd3v3plBF99MDf3ez2a0hxkjcE7OewFxN
m=audio 9 UDP/TLS/RTP/SAVPF 111 63 103 104 9 0 8 106 105 13 110 112 113 126
c=IN IP4 0.0.0.0
a=rtcp:9 IN IP4 0.0.0.0
a=ice-ufrag:gm9U
a=ice-pwd:EF/2U3kzqXgo2T1PR/FobYvC
a=ice-options:trickle
a=fingerprint:sha-256 2F:29:AD:23:7B:7E:C4:CA:AA:02:0C:4B:E2:CA:64:37:FE:B3:55:FB:C1:B1:D0:DF:9A:1B:39:1F:96:6F:55:67
a=setup:actpass
a=mid:0
a=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level
a=extmap:2 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time
a=extmap:3 http://www.ietf.org/id/draft-holmer-rmcat-transport-wide-cc-extensions-01
a=extmap:4 urn:ietf:params:rtp-hdrext:sdes:mid
a=extmap:5 urn:ietf:params:rtp-hdrext:sdes:rtp-stream-id
a=extmap:6 urn:ietf:params:rtp-hdrext:sdes:repaired-rtp-stream-id
a=sendrecv
a=msid:OGEhd3v3plBF99MDf3ez2a0hxkjcE7OewFxN 0e875b9e-6909-496b-be40-6792e34be174
a=rtcp-mux
a=rtpmap:111 opus/48000/2
a=rtcp-fb:111 transport-cc
a=fmtp:111 minptime=10;useinbandfec=1
a=rtpmap:63 red/48000/2
a=fmtp:63 111/111
a=rtpmap:103 ISAC/16000
a=rtpmap:104 ISAC/32000
a=rtpmap:9 G722/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:106 CN/32000
a=rtpmap:105 CN/16000
a=rtpmap:13 CN/8000
a=rtpmap:110 telephone-event/48000
a=rtpmap:112 telephone-event/32000
a=rtpmap:113 telephone-event/16000
a=rtpmap:126 telephone-event/8000
a=ssrc:1936809199 cname:EvTSUeypcYaFdm8M
a=ssrc:1936809199 msid:OGEhd3v3plBF99MDf3ez2a0hxkjcE7OewFxN 0e875b9e-6909-496b-be40-6792e34be174
a=ssrc:1936809199 mslabel:OGEhd3v3plBF99MDf3ez2a0hxkjcE7OewFxN
a=ssrc:1936809199 label:0e875b9e-6909-496b-be40-6792e34be174
m=video 9 UDP/TLS/RTP/SAVPF 96 98 100 122 127 97 99 101 121 120
c=IN IP4 0.0.0.0
a=rtcp:9 IN IP4 0.0.0.0
a=ice-ufrag:gm9U
a=ice-pwd:EF/2U3kzqXgo2T1PR/FobYvC
a=ice-options:trickle
a=fingerprint:sha-256 2F:29:AD:23:7B:7E:C4:CA:AA:02:0C:4B:E2:CA:64:37:FE:B3:55:FB:C1:B1:D0:DF:9A:1B:39:1F:96:6F:55:67
a=setup:actpass
a=mid:1
a=extmap:14 urn:ietf:params:rtp-hdrext:toffset
a=extmap:2 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time
a=extmap:13 urn:3gpp:video-orientation
a=extmap:3 http://www.ietf.org/id/draft-holmer-rmcat-transport-wide-cc-extensions-01
a=extmap:12 http://www.webrtc.org/experiments/rtp-hdrext/playout-delay
a=extmap:11 http://www.webrtc.org/experiments/rtp-hdrext/video-content-type
a=extmap:7 http://www.webrtc.org/experiments/rtp-hdrext/video-timing
a=extmap:8 http://www.webrtc.org/experiments/rtp-hdrext/color-space
a=extmap:4 urn:ietf:params:rtp-hdrext:sdes:mid
a=extmap:5 urn:ietf:params:rtp-hdrext:sdes:rtp-stream-id
a=extmap:6 urn:ietf:params:rtp-hdrext:sdes:repaired-rtp-stream-id
a=sendrecv
a=msid:OGEhd3v3plBF99MDf3ez2a0hxkjcE7OewFxN e7f3c454-9747-4fa5-ab7f-5e1b3a98ea46
a=rtcp-mux
a=rtcp-rsize
a=rtpmap:96 VP8/90000
a=rtcp-fb:96 goog-remb
a=rtcp-fb:96 transport-cc
a=rtcp-fb:96 ccm fir
a=rtcp-fb:96 nack
a=rtcp-fb:96 nack pli
a=rtpmap:98 VP9/90000
a=rtcp-fb:98 goog-remb
a=rtcp-fb:98 transport-cc
a=rtcp-fb:98 ccm fir
a=rtcp-fb:98 nack
a=rtcp-fb:98 nack pli
a=fmtp:98 profile-id=0
a=rtpmap:100 H264/90000
a=rtcp-fb:100 goog-remb
a=rtcp-fb:100 transport-cc
a=rtcp-fb:100 ccm fir
a=rtcp-fb:100 nack
a=rtcp-fb:100 nack pli
a=fmtp:100 level-asymmetry-allowed=1;packetization-mode=1;profile-level-id=42e01f
a=rtpmap:122 red/90000
a=rtpmap:127 ulpfec/90000
a=rtpmap:97 rtx/90000
a=fmtp:97 apt=96
a=rtpmap:99 rtx/90000
a=fmtp:99 apt=98
a=rtpmap:101 rtx/90000
a=fmtp:101 apt=100
a=rtpmap:121 rtx/90000
a=fmtp:121 apt=122
a=rtpmap:120 rtx/90000
a=fmtp:120 apt=127
a=ssrc-group:FID 3382608992 4179724220
a=ssrc:3382608992 cname:EvTSUeypcYaFdm8M
a=ssrc:3382608992 msid:OGEhd3v3plBF99MDf3ez2a0hxkjcE7OewFxN e7f3c454-9747-4fa5-ab7f-5e1b3a98ea46
a=ssrc:3382608992 mslabel:OGEhd3v3plBF99MDf3ez2a0hxkjcE7OewFxN
a=ssrc:3382608992 label:e7f3c454-9747-4fa5-ab7f-5e1b3a98ea46
a=ssrc:4179724220 cname:EvTSUeypcYaFdm8M
a=ssrc:4179724220 msid:OGEhd3v3plBF99MDf3ez2a0hxkjcE7OewFxN e7f3c454-9747-4fa5-ab7f-5e1b3a98ea46
a=ssrc:4179724220 mslabel:OGEhd3v3plBF99MDf3ez2a0hxkjcE7OewFxN
a=ssrc:4179724220 label:e7f3c454-9747-4fa5-ab7f-5e1b3a98ea46
m=application 9 UDP/DTLS/SCTP webrtc-datachannel
c=IN IP4 0.0.0.0
a=ice-ufrag:gm9U
a=ice-pwd:EF/2U3kzqXgo2T1PR/FobYvC
a=ice-options:trickle
a=fingerprint:sha-256 2F:29:AD:23:7B:7E:C4:CA:AA:02:0C:4B:E2:CA:64:37:FE:B3:55:FB:C1:B1:D0:DF:9A:1B:39:1F:96:6F:55:67
a=setup:actpass
a=mid:2
a=sctp-port:5000
a=max-message-size:262144

Philipp Hancke

unread,
Dec 7, 2021, 1:01:00 PM12/7/21
to discuss...@googlegroups.com
known bug by now:
even though the root cause is not yet known.

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/823c568e-f3fa-43f1-af36-7c2404df3f16n%40googlegroups.com.

ryk...@gmail.com

unread,
Dec 7, 2021, 4:42:41 PM12/7/21
to discuss-webrtc
Thanks for the link to the issue.

Yep, it's 100% this. I'd actually commented out the only part of our code that deals with codecs and this fixed the issue.

So guess i'm waiting on this bug to close before i can bring that functionality back into our code.

Love this group

Thanks
Reply all
Reply to author
Forward
0 new messages