Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Beginner
8 Views

Room.conect() fail when called from client side in a Web App deployed with https

Hi, i'm working in a Web Application coded in Node.js + Express v4.11. I use Intel CS MCU WebRTC Server v1.5 for offer Video Conference capabilities in my app. In the server side, I use your's custom Node.js module woogeenserver.js for create a ROOM in the Ubuntu server in behalf of the user that Log In in my Web App, and for get a TOKEN to connect to a specific existing ROOM in the Ubuntu Server. In the client side of the Web App, I use the JavaScript file woogeen.js that is part of the IntelCS WebRTC ClientSDK for with the TOKEN obtained in the Server side, connect to the Intel CS MCU Server for streaming the Web Cam's captured video to the corresponding ROOM.

Mi problem is:
Because I require in my Web App that a user log-in in a custom form, I must deploy my web app trough https(now during develop phase, with a self-signed certificate) for secure user's credentials transmission to the server. Now, when I deploy the Web App without use https, the app works OK. BUT, when I deploy it through https, in the client side, when I try to connect to the Intel's MCU Server with the token generated by the Server side of the Web App, the connection fails. I know it because i'm subscribing an event handler to the Room's "room-connected" event that is dispatchet when the user's attempt to connect to a ROOM sucess, and the handler doesn't get called.

Remark: When my Web App is deployed without use https, the client side connect to the ROOM successfully, because the event handler that i subscribe to the "room-connected" event is getting called.

I try to solve the problem by copy the key.pem and cert.pem that I generate for my Web App to the folder Release-v1.5\conf\cert also, with the intent of suppose that maybe, if I use the same certificate that I'm using in my Web App in the Intel MCU Server, it will work,  but nothing change, it continue to fail.

I know that in the CS_WebRTC_Conference_Server_User_Guide.v.1.5.pdf guide, there are something talked about publish the Intel CS MCU Server through https, but this section of the guide is somewhat lean.

There is some additional configuration change required for this to work in the Intel CS MCU's configuration files? I doesn't have modify any of the configuration files yet.

I have the Intel CS MCU Server v1.5 running in a Ubuntu 12.04 Desktop VMWare virtual machine guest and the Web App coded in Node.js that  I'm talking about is running in the Win7 host operating system. The Ubuntu virtual machine's network adapter is configured to use VMnet1(Host-only) network for communicate with the Win 7 box.

Regards,
I appreciate your hep!!!

Tags (2)
0 Kudos
16 Replies
Highlighted
New Contributor I
8 Views

And can you attach you woogen

And can you attach you woogen_config file and log directory in zip. It can give more information to help you.

I recommend you to start using version 1.5 because it have much differences from 1.5 and works better. And in some time you have to move to 2.0. It's better to do it earlier.

0 Kudos
Highlighted
8 Views

Hi Reynier,

Hi Reynier,

We've release 2.0 which has some major changes regarding server infrastructure and SDK. I'd recommend you to move onto 2.0 like Artem said, which might have some typo in his post above.

Regarding the specific issue you met, can you upload the server log files? You web app log info would be better as well.

0 Kudos
Highlighted
Beginner
8 Views

Hi,first of all, thanks for

Hi,first of all, thanks for these fast responses. Here I send the logs of the Intel CS MCU Server v1.5, and images with print screen of the web application's logs in chrome browser. In the Web Application, I have a web page for the publisher, and another for the subscriber to the Video Conference, that is why there is a group of images files whose file name begin with Publisher, and another group whose file name begin with Subscriber.

I hope that this info help to detect the problem,
Regards

 

0 Kudos
Highlighted
New Contributor I
8 Views

Sorry,  but in that logs no

Sorry,  but in that logs no any information.

Can you  send

1) the full logs directory after sever start.

2) woogen_config.js

3) listing of your start comangs( do you use sudo or work by root - you should'n use it - start by another user)

0 Kudos
Highlighted
8 Views

According to the log you

According to the log you provided, it seems the signaling between MCU and your Chrome client goes wrong.

As you may know, the signaling implementation on Chrome client is part of the browser itself now. What's your Chrome version?

If you're with MCU v1.5, please use Chrome client with version 37 or 38.

0 Kudos
Highlighted
Beginner
8 Views

Hi,

Hi,

Thank you for replying

I am working in Intel CS Webrtc application,

1.Achived to run the IntelCS media server in localhost with Woogeen functions(startRecorder,publish ,subscribe,join,send).

2.when i converted localhost to ssl server (trying to run in https server) cannot able to run and am getting an error("socket not ready"),have used  woogeen functions  like(startRecorder,publish ,subscribe,join,send) these functions where working perfectly in localhost,can't able to run in https server,

3.Is it  necessary to generate my own  new .keystore file and change in basicServer js and also let me know is there any way to customize the basicServer js to create rooms.

4.how to call Woogeen functions  from java. is woogeen provided with api model .i have seen and customized aws deployment.other than that is it possible to call woogeen functions from java.

please help me what mistake i have done to run IntelMedia in  HTTPS server..In hurry please reply soon

 

0 Kudos
Highlighted
8 Views

Hi Saravanan,

Hi Saravanan,

Regarding HTTPS, have you generated your own cert for SSL connections? The default cert in our package is a just self-signed sample.

Regarding Java API, we provide the Android SDK to call those Woogeen functions. Otherwise, you will need to do your own encapsulation.

Thanks!

 

0 Kudos
Highlighted
Beginner
8 Views

Hello Chunbo,

Hello Chunbo,

Thank you for quick response,

First i share my environment details:

1.OS:ubuntu (14.04)Lts

2.Chrome:Version 48.0.2564.82 (64-bit)

3.Intel cs media sdk :Release v2.8.1

I generated ssl certificate and i applied to my local code I have attached ScreenShots (attched in xls and ods formats)in excel please go through n correct me.

(i)But still I cant able to invoke Woogeen Functions, when i tried connecting to the server got error like socket not ready in chrome console.If it is a (client and server connection establishment problem).let me know how to rectify it.

(ii)please Explain me, what is the function of MCU cluster,and how to use it

(iii)Give me an example for how to use the mangement console (3000) 

 

 

0 Kudos
Highlighted
8 Views

Hi Saravanan,

Hi Saravanan,

We've fixed some issues on our server solution with Chrome 48 and above in v3.0. Please upgrade to 3.0.

Regarding the MCU cluster and Management console guide, please refer to our released user guide and documentation.

Thanks!

0 Kudos
Highlighted
Beginner
8 Views

Hi Chunbo,

Hi Chunbo,

Video recording work perfectly with  localhost .n am able record  the video in localstream.

how to record remote video stream,

whether i need to synchronize  both the localStream and remoteStream after recording or it will be  a output of synchronized one.

and a small request could u please reply as soon as earlier,

Thank you

0 Kudos
Highlighted
8 Views

Please refer to the JS client

Please refer to the JS client SDK user guide for the details of media recording.

Thanks!

0 Kudos
Highlighted
Beginner
8 Views

Hi Chunbo,

Hi Chunbo,

switched to version 3.1 and now its working with  secured server

when i started to run woogeen example am not able to establish Ice connection and publish streamed data and also getting error in console mentioned below

(ERROR: publish failed: Failed to get accessing agent.,       INFO: ICE Connection Failed)

am not able to find the Woogeen_config.js file which Intel provided in v2.8 &v3.0,

wen i applied my own certificate am getting the same error tat (Error:Mac verify Failure) 

and also please explain the purpose of Folders (controller audio_agent, video_agent)

 

 

 

 

0 Kudos
Highlighted
8 Views

Please refer to section

Please refer to section "Table 2-5. Distributed MCU components" in our Intel® Collaboration Suite for WebRTC Conference Server Guide for the details of each component.

Regarding the configuration, now each component has its own configuration. For example, controller component has its "controller.toml".

Thanks!

0 Kudos
Highlighted
Beginner
8 Views

Hi,

Hi,

Server Machine: 
1.os:ubuntu (14.04)
2.Memory:8gb,
3.server Version: MCU
4.Network Bandwidth :21mbps

Network Status:wired


I have installed Release v3.2 intel webrtc Mcu
-->followed steps provided Mcu Installation Server,and configured Mcu machine 
-->Have generated my ssl certificate and configured it properly
-->after starting Intel Mcu server with the following command (start-all.sh)
Mcu server has been started properly can able to run both in http ans https

on view got the following Error:
ERROR: server connection failed: invalid token

2.For refrence pupose I attached my log file.please go through and help me to fix the issue.

Thank You.

 

521740

0 Kudos
Highlighted
Employee
8 Views

Please check whether you have

Please check whether you have run the init-all.sh script before start-all.sh.

0 Kudos
Highlighted
Beginner
8 Views

I have the same issue and I

I have the same issue and I have run the init-all.sh file. Yet I am having the error.

0 Kudos