Version 2.8 , screen sharing

[Li__Guangming]

Hi，

   I had this issue for weeks and was able to do a workaround.  As a workaround, you get your own chrome extension id from the sample "screen-sharing-chrome-extension" example they gave in the files. Change woogeen.sdk.js under basic_example with your own extension id. 

I think the error is in below code. When it goes through the try { chrome.runtime.sendMessage...} it exits the whole if statement because of the error "Error in event handler for (unknown): TypeError: Cannot read property 'streamId' of undefined". It should tell me that I don't have extension installed or something reasonable" Please help. Thank you

if (b.video && "screen" === b.video.device) {
                    var o = b.video.extensionId || "ndnodmfimngipdamcjglclkbaofcajaa";             
                    i.audio = !1;
                    try {
                        chrome.runtime.sendMessage(o, {
                            getStream: !0
                        }, function(a) {
                            return void 0 === a ? void("function" == typeof d && d({
                                code: 1103,
                                msg: "screen sharing plugin inaccessible"
                            })) : (i.video.mandatory.chromeMediaSource = "desktop", i.video.mandatory.chromeMediaSourceId = a.streamId, void l.apply(navigator, [i, m, n]))
                        })
                    } catch (p)

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I ran it in chrome console:

INFO: stream in conference: 562dd8feed0dcfe60aa426bf
INFO: subscribing: 562dd8feed0dcfe60aa426bf
INFO: user in conference: Object {name: "user", role: "presenter", id: "x3FkZvaCy-97VFF9AAAB", permissions: Object}
ERROR: share screen failed: Object {code: 1103, msg: "screen sharing plugin inaccessible"}
INFO: subscribed: 562dd8feed0dcfe60aa426bf

regards

[donna_l_]

I am same with Li Guangming. After set SSL=true, server return "Service Unavailable".

[donna_l_]

Hi Chunbo:

        Can i use the default certificate to test screen sharing? 

        When i produce my own certificate, i meet the problem, see https://software.intel.com/en-us/forums/intel-collaboration-suite-for-webrtc/topic/606519#comment-1855671, please help me, thank you!

[Chunbo_H_Intel1]

Please look at the source code of basic example, basicServer.js. If you want to use SSL in Nuve, you will have to update the URL of N.API.init API to be with SSL URL.

Thanks!

[Li__Guangming]

Start the server, the MCU startup failure needs to be updated N.API.init() and SSL url?Could you tell me which file is N.API.init?

[Chunbo_H_Intel1]

Please go to extras/basic_example/basicServer.js.

Thanks!

[view_d_]

Hi all: 

I am same with Li Guangming on 3.0, the problem has been solved?

[Chunbo_H_Intel1]

Yes, it has been solved. Thanks!

[yongtao_x_]

大家好：

屏幕共享我也遇到相同的问题，安装了插件一样不行。 我看文档是支持 网络相机输入流的，但是使用rtsp流 返回错误信息如下：

"External stream must have video or audio" rtsp 格式 H264（1080p） AAC(4800hz) 。

我该通过哪些日志是分析错误原因呢。

sdk 里面已经添加了aac编码方式。push rtmp 流是正常的

[Lei_Z_Intel1]

关于RTSP流接入，请参考这个topic https://software.intel.com/en-us/forums/intel-collaboration-suite-for-we...。

[yongtao_x_]

大家好：

   我的版本是 v3.3  屏幕共享问题是需要修改 nuve.toml的 ssl开关吗？修改后也同样启动失败了，同时也修改了basicServer.js  API.init("xxx","xxx","http://xxx:3000/") 仍然无法正常启动。还需修改哪里呢，谢谢。

[yongtao_x_]

basicServer.js  API.init("xxx","xxx","https://xxx:3000/")  修改成了

[Lei_Z_Intel1]

根据Chrome的屏幕共享要求，web app必须是https，所以无需修改basicServer.js，只需要用https://x.x.x.x:3004访问web app页面。但是前提是配置好Chrome screen sharing环境。