For some reason, screen share doesn’t works on chrome 57 version.
Note: It works on chrome till 56 version. And it works on Firefox.
And what I notice is stream with video is not working.
Is there any specific reasons for this failure?
Thanks & Regards,
Hemanth
On chrome 57 version:
But what i notice is … content is not coming from licode during subscription.
NOTE: All events are proper, problem is with the stream content.
I added a “poster” for the video tag, where it is shown forever, which means there is no enough content to display the video.
Any guidance to fix this issue?
What OS are you running the Chrome in?
Do normal streams (not screensharing) work?
When did you last update Licode?
You can take a look at chrome://webrtc-internals and see if the connection is actually established and data is coming through.
We use screensharing every day and we’ve found no issues with Chrome 56 and 57. Admittedly, we use Mac and Ubuntu most of the time.
Please find my responses inline.
What OS are you running the Chrome in?
OS : windows 7 64-bit
Do normal streams (not screensharing) work?
Yes … All audio streams are working fine.
When did you last update Licode?
About a week back
You can take a look at chrome://webrtc-internals and see if the connection is actually established and data is coming through.
seems like data is not coming
SDP
Local SDP
v=0
o=mozilla…THIS_IS_SDPARTA-52.0.2 6164186116009841572 0 IN IP4 0.0.0.0
s=-
t=0 0
a=sendrecv
a=fingerprint:sha-256 17:5A:4E:81:02:0F:BA:E1:A3:6D:2B:E1:B2:C3:2A:4A:1F:63:69:66:CF:B8:9B:FB:83:64:AE:49:BA:60:B9:9D
a=ice-options:trickle
**a=msid-semantic:WMS ***
m=video 27374 UDP/TLS/RTP/SAVPF 120 121 126 97
c=IN IP4 182.72.141.194
a=candidate:0 1 UDP 2122252543 172.16.7.38 50803 typ host
a=candidate:0 2 UDP 2122252542 172.16.7.38 50804 typ host
a=candidate:1 1 UDP 1686052863 182.72.141.194 27374 typ srflx raddr 172.16.7.38 rport 50803
a=candidate:1 2 UDP 1686052862 182.72.141.194 45030 typ srflx raddr 172.16.7.38 rport 50804
a=recvonly
a=end-of-candidates
a=fmtp:120 max-fs=12288;max-fr=60
a=fmtp:121 max-fs=12288;max-fr=60
a=fmtp:126 profile-level-id=42e01f;level-asymmetry-allowed=1;packetization-mode=1
a=fmtp:97 profile-level-id=42e01f;level-asymmetry-allowed=1
a=ice-pwd:ad3487da3289fbbf89359c5be540510d
a=ice-ufrag:92646982
a=mid:sdparta_0
a=rtcp-fb:120 nack
a=rtcp-fb:120 nack pli
a=rtcp-fb:120 ccm fir
a=rtcp-fb:120 goog-remb
a=rtcp-fb:121 nack
a=rtcp-fb:121 nack pli
a=rtcp-fb:121 ccm fir
a=rtcp-fb:121 goog-remb
a=rtcp-fb:126 nack
a=rtcp-fb:126 nack pli
a=rtcp-fb:126 ccm fir
a=rtcp-fb:126 goog-remb
a=rtcp-fb:97 nack
a=rtcp-fb:97 nack pli
a=rtcp-fb:97 ccm fir
a=rtcp-fb:97 goog-remb
a=rtcp-mux
a=rtpmap:120 VP8/90000
a=rtpmap:121 VP9/90000
a=rtpmap:126 H264/90000
a=rtpmap:97 H264/90000
a=setup:actpass
a=ssrc:3772648283 cname:{5219eb9a-6eb4-4ad2-b247-87f155b237dd}
Remote SDP
v=0
o=- 0 0 IN IP4 127.0.0.1
s=-
t=0 0
a=sendrecv
m=video 1 UDP/TLS/RTP/SAVPF 120
c=IN IP4 0.0.0.0
a=candidate:1 1 udp 2013266431 172.16.4.100 42903 typ host generation 0
a=sendonly
a=fingerprint:sha-256 B3:71:58:BB:BA:33:57:5C:CF:1B:11:B0:E4:78:24:52:E1:16:07:80:10:90:C6:11:EF:31:ED:CB:90:4D:82:46
a=ice-pwd:pAvQ32bSmdx4/xyPpT/dF6
a=ice-ufrag:AYR5
a=rtcp:1 IN IP4 0.0.0.0
a=rtcp-fb:120 nack
a=rtcp-fb:120 nack pli
a=rtcp-fb:120 ccm fir
a=rtcp-fb:120 goog-remb
a=rtcp-mux
a=rtpmap:120 VP8/90000
a=ssrc:2357700714 cname:o/i14u9pJrxRKAsu
a=ssrc:2357700714 msid:Jz4U1p6Nmw v0
a=ssrc:2357700714 mslabel:Jz4U1p6Nmw
a=ssrc:2357700714 label:Jz4U1p6Nmwv0
RTP Stats
inbound_rtp_video_0
Local: 16:35:02 GMT+0530 (India Standard Time) inboundrtp SSRC: 0
NOTE:
Till Chrome 56 version, everything is absolutely fine.
It git broke from 57 version.
(Same issue for both video and screenshare streams)
And in firefox, everything is working fine.
RTP Stats
inbound_rtp_video_0
Local: 16:55:10 GMT+0530 (India Standard Time) inboundrtp SSRC: 0 Received: 4474 packets (3588.60 Kb) Lost: undefined Jitter: undefined
That’s a Firefox SDP.
Are you subscribing to the screensharing stream with Firefox? Does it work with Chrome?
Case1 - Not working
Attendee 1 - Chrome 57 version - I am publishing the video/screenshare stream.
Attendee 2 - Chrome (or) firefox any version subscribing to it … we cannot see the data successfully on stream.
==========================================================================
Case 2 - Working
Attendee 1 - Chrome (Apart from 57 version) (or) firefox any version … publish video/screenshare stream.
Attendee 2 - Chrome (or) firefox any version subscribing to it … it works like charm.
====================================================
Conclusion
Video/Screen share published from chrome 57 version has a problem at subscriber side.
I hope information is clear.
In case of any further information needed, please ask.
ssrc_1548528521_recv (ssrc)
Statistics ssrc_1548528521_recv
cname:o/i14u9pJrxRKAsu
msid:NiWoM2ssrH v0
mslabel:NiWoM2ssrH
label:NiWoM2ssrHv0
timestamp 4/7/2017, 7:22:44 PM
bytesReceived 14877030
codecImplementationName libvpx
framesDecoded 2949
mediaType video
packetsLost 0
packetsReceived 14173
ssrc 1548528521
transportId Channel-video-1
googCaptureStartNtpTimeMs 0
googCodecName VP8
googCurrentDelayMs 73
googDecodeMs 2
googFirsSent 0
googFrameHeightReceived 480
googFrameRateDecoded 30
googFrameRateOutput 30
googFrameRateReceived 30
googFrameWidthReceived 640
googJitterBufferMs 59
googMaxDecodeMs 4
googMinPlayoutDelayMs 0
googNacksSent 0
googPlisSent 1
googRenderDelayMs 10
googTargetDelayMs 73
googTrackId v0
ssrc_3468354236_recv (ssrc)
Statistics ssrc_3468354236_recv
cname:o/i14u9pJrxRKAsu
msid:ipTWT6bZE2 v0
mslabel:ipTWT6bZE2
label:ipTWT6bZE2v0
timestamp 4/7/2017, 7:26:34 PM
bytesReceived 0
codecImplementationName unknown
framesDecoded 0
mediaType video
packetsLost 0
packetsReceived 0
ssrc 3468354236
transportId Channel-video-1
googCaptureStartNtpTimeMs 0
googCodecName
googCurrentDelayMs 0
googDecodeMs 0
googFirsSent 0
googFrameHeightReceived 0
googFrameRateDecoded 0
googFrameRateOutput 0
googFrameRateReceived 0
googFrameWidthReceived 0
googJitterBufferMs 0
googMaxDecodeMs 0
googMinPlayoutDelayMs 0
googNacksSent 0
googPlisSent 0
googRenderDelayMs 10
googTargetDelayMs 0
googTrackId v0
“codecImplementationName” is unknown in non working and almost rest all parameters are with 0.
It rarely happens to me but not only with screenshare.
codecImplementationName unknown and nor video or audio played
ok … but it is consistent for me.
Hi Pedro,
Can you please provide the SDP’s at both publishing and subscribing side on chrome 57 version?
Will compare and check for some clues.
Thanks,
Hemanth
Hi Pedro,
I tested screen share on different licode instances with following commit hash codes, where I am seeing the stated issue.
Instance 1 : 8a059671c5caade5f80918e29a6a7a12c76fac63 (Tue Jul 26 16:08:46 2016 +0200)
Instance 2 : de95e07637140ac199b1fc086b592350a47b5226 (Wed Mar 8 09:33:14 2017 +0100)
Can you test on these 2 commit hash codes and confirm the working status?
Thanks,
Hemanth
Hi Pedro,
With latest licode, we are able to do screen share and video calls over local instance.
It is working fine.
But over amazon cloud instance, we are seeing below issue:
ERROR: RoomController - message: ErizoJS timed out will be removed, erizoId: af220848-88f0-18d3-8d17-367082c63bf2, publishersAffected: 1
Thanks,
Hemanth
This is initial log.
INFO: EcCloudHandler - message: deleting erizoJS, erizoId: 70f63350-7ced-e36c-b837-7e294c2efc67
I have never used ‘amazon cloud’, so I can’t give you any suggestion in detail 
Working with below hash code.
commit 0a0ebb1fbf2441427a7aea5fce5a29452f14eff0
Date: Wed Apr 19 11:28:22 2017 +0200
Thanks,
Hemanth