Issue metadata
Sign in to add a comment
|
Failed setting SFU remote answer sdp due to invalid port number
Reported by
leticia....@temasys.com.sg,
May 1 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.29 Safari/537.36 Steps to reproduce the problem: 1. Go to https://getaroom.io/mtest to replicate client connection to SFU. Note that the SFU is targeted as MCU. 2. Open the Web console 3. Notice set remote description answer failure. What is the expected behavior? No DOM errors What went wrong? Errors given in error callback: DOMException: Failed to parse SessionDescription. m=application 66754 DTLS/SCTP 5000 The port number is invalid This is not reproducible in chrome 58. Did this work before? Yes 58 Does this work in other browsers? Yes Chrome version: 59.0.3071.29 Channel: beta OS Version: OS X 10.12.2 Flash Version: SDP answer: v=0 o=- 0 0 IN IP4 127.0.0.1 s=SFUSDP t=0 0 a=group:BUNDLE audio video data a=msid-semantic: WMS 4g7tKW9GzI m=audio 1 UDP/TLS/RTP/SAVPF 111 0 126 c=IN IP4 0.0.0.0 a=rtcp:1 IN IP4 0.0.0.0 a=candidate:1 1 udp 2013266431 xx.xx.xx.xx 25939 typ host generation 0 a=candidate:2 1 udp 1677721855 xx.xx.xx.xx 25939 typ srflx raddr xx.xx.xx.xx rport 25939 generation 0 a=ice-ufrag:BaTU a=ice-pwd:yKrLfQTOrJSz4P/FKcP8ZB a=fingerprint:sha-256 D4:64:0D:FC:CE:A0:23:05:0E:0B:40:1C:3F:5A:FB:CD:94:C3:85:85:4B:AC:72:9B:79:22:E1:6F:3A:BA:72:BA a=recvonly a=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level a=mid:audio a=rtcp-mux a=rtpmap:111 opus/48000/2 a=fmtp:111 minptime=10;useinbandfec=1;stereo=1; a=rtpmap:0 PCMU/8000 a=rtpmap:126 telephone-event/8000 a=maxptime:60 a=ssrc:44444 cname:o/i14u9pJrxRKAsu a=ssrc:44444 msid:4g7tKW9GzI a0 a=ssrc:44444 mslabel:4g7tKW9GzI a=ssrc:44444 label:4g7tKW9GzIa0 m=video 1 UDP/TLS/RTP/SAVPF 96 c=IN IP4 0.0.0.0 a=rtcp:1 IN IP4 0.0.0.0 a=candidate:1 1 udp 2013266431 xx.xx.xx.xx 25939 typ host generation 0 a=candidate:2 1 udp 1677721855 xx.xx.xx.xx 25939 typ srflx raddr xx.xx.xx.xx rport 25939 generation 0 a=ice-ufrag:BaTU a=ice-pwd:yKrLfQTOrJSz4P/FKcP8ZB a=extmap:2 urn:ietf:params:rtp-hdrext:toffset a=extmap:3 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time a=extmap:4 urn:3gpp:video-orientation a=extmap:5 http://www.ietf.org/id/draft-holmer-rmcat-transport-wide-cc-extensions-01 a=extmap:6 http://www.webrtc.org/experiments/rtp-hdrext/playout-delay a=fingerprint:sha-256 D4:64:0D:FC:CE:A0:23:05:0E:0B:40:1C:3F:5A:FB:CD:94:C3:85:85:4B:AC:72:9B:79:22:E1:6F:3A:BA:72:BA a=recvonly a=mid:video a=rtcp-mux a=rtpmap:96 VP8/90000 a=rtcp-fb:96 ccm fir a=rtcp-fb:96 nack a=rtcp-fb:96 nack pli a=rtcp-fb:96 transport-cc a=ssrc:55543 cname:o/i14u9pJrxRKAsu a=ssrc:55543 msid:4g7tKW9GzI v0 a=ssrc:55543 mslabel:4g7tKW9GzI a=ssrc:55543 label:4g7tKW9GzIv0 a=ssrc:55555 cname:o/i14u9pJrxRKAsu a=ssrc:55555 msid:4g7tKW9GzI v0 a=ssrc:55555 mslabel:4g7tKW9GzI a=ssrc:55555 label:4g7tKW9GzIv0 m=application 66754 DTLS/SCTP 5000 c=IN IP4 0.0.0.0 a=ice-ufrag:BaTU a=ice-pwd:yKrLfQTOrJSz4P/FKcP8ZB a=candidate:1 1 udp 2013266431 xx.xx.xx.xx 25939 typ host generation 0 a=candidate:2 1 udp 1677721855 xx.xx.xx.xx 25939 typ srflx raddr xx.xx.xx.xx rport 25939 generation 0 a=fingerprint:sha-256 D4:64:0D:FC:CE:A0:23:05:0E:0B:40:1C:3F:5A:FB:CD:94:C3:85:85:4B:AC:72:9B:79:22:E1:6F:3A:BA:72:BA a=setup:active a=sctpmap:5000 webrtc-datachannel 1024 a=mid:data
,
May 3 2017
Just tested and it seems like something that Chrome 59+ has added strict rules for m= line port number: https://tools.ietf.org/html/draft-ietf-rtcweb-jsep-20#section-5.2.1. Seems like going a port number above 65536 would result in an error. This ticket is closable.
,
May 3 2017
Thanks for looking into it; closing. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by guidou@chromium.org
, May 2 2017