You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to meetecho-janus
Hi Lorenzo,
I am getting "Skipping disabled/unsupported media line..." from the Janus logs (which is 2-3 weeks old). It only happens when negotiating H264, which is rejected by Janus. Do you know why? Below is the relevant part of the log.
[1186331523] Remote SDP: v=0 o=- 8276813410072767804 2 IN IP4 127.0.0.1 s=- t=0 0 a=group:BUNDLE video a=msid-semantic: WMS stream_label m=video 9 UDP/TLS/RTP/SAVPF 120 c=IN IP4 0.0.0.0 a=rtcp:9 IN IP4 0.0.0.0 a=ice-ufrag:AeRn a=ice-pwd:WVIetVyhcCZ4nSpwNfSRRKkl a=fingerprint:sha-256 4A:E6:D3:90:1E:E4:A9:A1:2B:B3:82:96:B6:DC:17:9C:77:E1:E0:81:9D:29:AC:47:0C:1F:8D:56:A5:7A:EE:4B a=setup:actpass a=mid:video 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:6 http://www.webrtc.org/experiments/rtp-hdrext/playout-delay a=sendonly a=rtcp-mux a=rtcp-rsize a=rtpmap:120 H264/90000 a=rtcp-fb:120 ccm fir a=rtcp-fb:120 nack a=rtcp-fb:120 nack pli a=rtcp-fb:120 goog-remb a=rtcp-fb:120 transport-cc a=fmtp:120 packetization-mode=1;profile-level-id=42c028 a=ssrc-group:FID 1933807933 1574388880 a=ssrc:1933807933 cname:3DSbxA84ncX+tysO a=ssrc:1933807933 msid:stream_label video_label a=ssrc:1933807933 mslabel:stream_label a=ssrc:1933807933 label:video_label a=ssrc:1574388880 cname:3DSbxA84ncX+tysO a=ssrc:1574388880 msid:stream_label video_label a=ssrc:1574388880 mslabel:stream_label a=ssrc:1574388880 label:video_label [1186331523] Audio has NOT been negotiated, Video has been negotiated, SCTP/DataChannels have NOT been negotiated [1186331523] The browser: supports BUNDLE, supports rtcp-mux, is doing Trickle ICE [1186331523] Setting ICE locally: got OFFER (0 audios, 1 videos) [1186331523] Creating ICE agent (ICE Full mode, controlled) [1186331523] ICE thread started [1186331523] Adding 192.168.1.11 to the addresses to gather candidates for [1186331523] Gathering done for stream 1 [1186331523] Parsing video candidates (stream=1)... [1186331523] ICE ufrag (local): AeRn [1186331523] ICE pwd (local): WVIetVyhcCZ4nSpwNfSRRKkl [1186331523] Fingerprint (local) : sha-256 4A:E6:D3:90:1E:E4:A9:A1:2B:B3:82:96:B6:DC:17:9C:77:E1:E0:81:9D:29:AC:47:0C:1F:8D:56:A5:7A:EE:4B [1186331523] DTLS setup (local): actpass [1186331523] Video mid: video [1186331523] Peer video SSRC: 1933807933 [1186331523] Peer video SSRC (rtx): 1574388880 [1186331523] Peer video SSRC (rtx): 1574388880 [1186331523] Peer video SSRC (rtx): 1574388880 [1186331523] Peer video SSRC (rtx): 1574388880 ------------------------------------------- >> Anonymized (1241 --> 326 bytes) ------------------------------------------- v=0 o=- 8276813410072767804 2 IN IP4 127.0.0.1 s=- t=0 0 m=video 1 UDP/TLS/RTP/SAVPF 120 c=IN IP4 1.1.1.1 a=sendonly a=rtpmap:120 H264/90000 a=rtcp-fb:120 ccm fir a=rtcp-fb:120 nack a=rtcp-fb:120 nack pli a=rtcp-fb:120 goog-remb a=rtcp-fb:120 transport-cc a=fmtp:120 packetization-mode=1;profile-level-id=42c028
Handling message: { "audio": true, "bitrate": 4000000, "data": false, "request": "configure", "video": true } Setting audio property: true (room 1234, user 2670713210) Setting video property: true (room 1234, user 2670713210) Setting video bitrate: 4000000 (room 1234, user 2670713210) [REMB] bitrate=4000000 (24 bytes) Preparing JSON event as a reply This is involving a negotiation (offer) as well: v=0 o=- 8276813410072767804 2 IN IP4 127.0.0.1 s=- t=0 0 m=video 1 UDP/TLS/RTP/SAVPF 120 c=IN IP4 1.1.1.1 a=sendonly a=rtpmap:120 H264/90000 a=rtcp-fb:120 ccm fir a=rtcp-fb:120 nack a=rtcp-fb:120 nack pli a=rtcp-fb:120 goog-remb a=rtcp-fb:120 transport-cc a=fmtp:120 packetization-mode=1;profile-level-id=42c028
The publisher is NOT going to send an audio stream The publisher is going to send a video stream -- Will answer with media direction 'recvonly' -- -- H264 payload type is 120 The publisher is NOT going to open a data channel Handling publisher: turned this into an 'answer': v=0 o=- 1467332029871740 1467332029871744 IN IP4 127.0.0.1 s=Demo Room t=0 0 m=video 0 RTP/SAVPF 0
[1186331523] Video disabled via SDP [1186331523] -- Marking video stream as disabled [1186331523] Done! Ready to setup remote candidates and send connectivity checks... [1186331523] -- bundle is supported by the browser, getting rid of one of the RTP/RTCP components, if any... [1186331523] -- rtcp-mux is supported by the browser, getting rid of RTCP components, if any...
Webmaster Webmaster
unread,
Jun 30, 2016, 8:56:59 PM6/30/16
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to meetecho-janus
I wonder if this has been fixed by the following. I'll try.
Author: Lorenzo Miniero Date: Mon Jun 20 16:56:51 2016 +0200
Merge pull request #567 from jswirl/master
Fix VideoRoom SDP compose error
Lorenzo Miniero
unread,
Jul 1, 2016, 3:40:02 AM7/1/16
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to meetecho-janus
Yes, if I remember correctly there was a bug that prevented H.264 rooms to work correctly, which is what you seem to be experiencing.