topic Hi Deepa, in Intel® Collaboration Suite for WebRTC

Camera not coming on test page

Deepa_G_ — Sun, 25 Jan 2015 22:44:38 GMT

I have installed all the components as docuemented in CS_WebRTC_Conference_Server_User_Guide.v2.0.pdf

but the sample application is not working.

Where shud i check what is the issue?

In some other posts there

Artem_M_ — Mon, 26 Jan 2015 02:25:23 GMT

In some other posts there were explanations about propblem with node js install. Did you see them?

Can you attach some logs from start directory. Without them, I think, nobody could help you.

Please see below info -- i do

Deepa_G_ — Mon, 26 Jan 2015 06:02:00 GMT

Please see below info -- i do not see any error in log except for room name? can i not give any room name? please direct to correct forum post if this was covered earlier.

# node -v
v0.10.33

cat logs/woogeen-controller.stdout
2015-01-25 21:56:43.065 - INFO: RPC - Exchange rpcExchange is open
2015-01-25 21:56:43.070 - INFO: RPC - ClientQueue amq.gen-QGFCvsbLnSIEK9CDvfUcMX is open
2015-01-25 21:56:43.396 - INFO: RPC - Queue erizoController_1 is open
2015-01-25 21:56:43.399 - INFO: ErizoController - server on

cat logs/woogeen-agent.stdout
Running process
2015-01-25 21:56:44.165 - INFO: RPC - Exchange rpcExchange is open
2015-01-25 21:56:44.184 - INFO: RPC - ClientQueue amq.gen-ArlyaK4h76Sw6y14HzFwn4 is open
2015-01-25 21:56:44.203 - INFO: RPC - Queue ErizoAgent is open

cat logs/woogeen-app.stdout
2 rooms in this service.
MyRoom Id: 54c3b42b4eb96d917a48ec52
P2PRoom Id: 54c3b42b4eb96d917a48ec53
GET /?room=111 304 11.226 ms - -
GET /woogeen.sdk.js 304 4.434 ms - -
GET /woogeen.sdk.ui.js 304 3.672 ms - -
GET /script2.js 304 2.371 ms - -
GET / 304 1.341 ms - -
GET /woogeen.sdk.js 304 0.806 ms - -
GET /woogeen.sdk.ui.js 304 1.275 ms - -
GET /script2.js 304 1.161 ms - -
eyJ0b2tlbklkIjoiNTRjNTY2Y2Q0YTVlZjI1NGUyZmYzOTQ3IiwiaG9zdCI6IjEwLjAuMC43OjgwODAiLCJzZWN1cmUiOmZhbHNlLCJzaWduYXR1cmUiOiJZVFEwTURKak9EQXpObUpqWXpWa1lUVXhOR0ZqWldGbU56RXhZVGcwTldVM01UY3lZekF6WXc9PSJ9
POST /createToken/ 200 175.158 ms - 196
GET /?room=1111 304 1.037 ms - -
GET /woogeen.sdk.js 304 1.486 ms - -
GET /script2.js 304 0.971 ms - -
GET /woogeen.sdk.ui.js 304 0.976 ms - -
POST /createToken/ - - ms - -
POST /createToken/ - - ms - -
POST /createToken/ - - ms - -
POST /createToken/ - - ms - -

cat logs/woogeen-nuve.stdout
2015-01-25 21:56:37.646 - INFO: RPC - Conected to rabbitMQ server
2015-01-25 21:56:37.652 - INFO: RPC - Exchange rpcExchange is open
2015-01-25 21:56:37.676 - INFO: RPC - Queue nuveQueue is open
2015-01-25 21:56:37.678 - INFO: RPC - ClientQueue amq.gen-wUZ-8eOAjkCz4pUmkakMoC is open
2015-01-25 21:56:43.120 - INFO: CloudHandler - New erizocontroller ( 1 ) in: 10.0.0.7
2015-01-25 21:56:46.591 - INFO: RoomsResource - Representing rooms for service 54c26186f0baab1613a7f6a6
2015-01-25 21:56:57.814 - INFO: TokensResource - Room 111 does not exist
2015-01-25 21:57:33.955 - INFO: TokensResource - Created token for room 54c3b42b4eb96d917a48ec52 and service 54c26186f0baab1613a7f6a6
2015-01-25 21:57:36.872 - INFO: TokensResource - Room 1111 does not exist
2015-01-25 21:58:57.786 - INFO: TokensResource - Room 111 does not exist
2015-01-25 21:59:37.332 - INFO: TokensResource - Room 1111 does not exist

Your first problem as I told

Artem_M_ — Mon, 26 Jan 2015 13:44:35 GMT

Your first problem as I told earlier - is node js. Installation instaruction is https://software.intel.com/en-us/forums/topic/538837 At the bottom.

You should install version 0.10.26 vis nvm

The second - in url you should type /?room= 54c3b42b4eb96d917a48ec52 not ?room=1111 because it uses hash of room

Thank you it is working now -

Deepa_G_ — Mon, 26 Jan 2015 14:07:03 GMT

Thank you it is working now -- on LAN with ROOM IDs as below

1. How to use these rooms on WAN

2. How to create more rooms?

Please share if any documentation on this like gettign started

=====
2 rooms in this service.
MyRoom Id: 54c3b42b4eb96d917a48ec52
P2PRoom Id: 54c3b42b4eb96d917a48ec53

Nice to hear that!

Artem_M_ — Mon, 26 Jan 2015 14:31:56 GMT

Nice to hear that!

Previously in version 1.1 there was administrstion panel. May be it will appea in future.

Now - the only way to create room - is vis mongo shell.

mongo has 2 main tables services and rooms.

You should create first in rooms then in services.

in pure mongo shell it will be something like

db.rooms.insert(
        {
                _id: ObjectId("54a9a18e1f0f96f837b7d6d8")
				"name": "Mix Room2"
        });
		
		
db.services.update(
        { _id: ObjectId("54a9a18e1f0f96f837b7d6d8") },
        { $addToSet: { rooms: {
             "_id": ObjectId("54b7d1d1b2a1933287391669"),
             "name": "Mix Room2"
     } } })

In PHP something like:

$serviceId = ""yyyyy;
$roomId = new MongoId();
$name = "xxx";
$insertRoom = array(
            '_id'       =>  $roomId
            ,"name"      =>  $name            
        );
        
        
$servicesParams = array('_id'=>new MongoID($serviceId));
$insertServices = array(
            '$addToSet'=> array(
                "rooms" => $insertRoom
            )
        );
        
        
$rooms->insert($insertRoom);        
$services->update($servicesParams,$insertServices);

The only documentation - is that can be downloaded from main page of project

448063

Thank you very much for your

Deepa_G_ — Mon, 26 Jan 2015 14:51:20 GMT

Thank you very much for your Prompt response and resolution :)

Appreciate it

I have gone through that user guide it shows only Internal IP(LAN)

I have the server on a public ip to connect over WAN - I see the error log where it is connecting to socket.io on an INTERNAL IP

Navigated to http://<Public IP>:3001/?room=54c3b42b4eb96d917a48ec52
woogeen.sdk.js:9 GET http://10.0.0.7:8080/socket.io/1/?t=1422283560215 net::ERR_CONNECTION_TIMED_OUTwoogeen.sdk.js:9 d.handshakewoogeen.sdk.js:9 d.connectwoogeen.sdk.js:9 dwoogeen.sdk.js:9 c.connectwoogeen.sdk.js:8 c.ConferenceClient.joinscript2.js:138 (anonymous function)script2.js:19 req.onreadystatechange
woogeen.sdk.js:8 ERROR: server connection failed: connection_error

Hi guys,

Chunbo_H_Intel1 — Mon, 26 Jan 2015 15:22:28 GMT

Hi guys,

Great to see the hot discussion going on here! Thanks for your sharing.

What's more, the new management panel/UI is on its way. You will have it soon. Stay tuned!

in file woogeen_config.js

Artem_M_ — Mon, 26 Jan 2015 16:04:21 GMT

in file woogeen_config.js you have properties like

// Public erizoController IP for websockets (useful when behind NATs)
// Use '' to automatically get IP from the interface
config.erizoController.publicIP = '136..........'; //default value: ''
// Use '' to use the public IP address instead of a hostname
config.erizoController.hostname = 'xxxxxxx.com'; //default value: ''
config.erizoController.port = 8080; //default value: 8080
// Use true if clients communicate with erizoController over SSL
config.erizoController.ssl = true; //default value: false

I think you should change that values to may it work in WAN too.

Hi Artem,

Deepa_G_ — Mon, 26 Jan 2015 16:36:29 GMT

Hi Artem,

I changed the IP as advised above and I opened port 8080 on the public IP. now when I try to use 2 users I get PEER CONNECTION FAILED and each others video is not visible even on the same computer.

Is there a list of ports I need to open on the Public Interface? Please note I m running the main server and peerserver on the same machines

INFO: stream in conference: 54c3b42b4eb96d917a48ec52
woogeen.sdk.js:8 INFO: subscribing: 54c3b42b4eb96d917a48ec52
woogeen.sdk.js:8 INFO: subscribed: 54c3b42b4eb96d917a48ec52
woogeen.sdk.js:8 INFO: stream published: Ix0sZgifswNU89CIEmOL
woogeen.sdk.js:8 INFO: user left: Object {name: "user", role: "presenter", id: "GUxGEkFTKRqSBluAEmOK", permissions: Object}id: "GUxGEkFTKRqSBluAEmOK"name: "user"permissions: Objectrole: "presenter"__proto__: Object
woogeen.sdk.js:8 INFO: user joined: Object {name: "user", role: "presenter", id: "sedDTpEj1PfnunZPEmOM", permissions: Object}id: "sedDTpEj1PfnunZPEmOM"name: "user"permissions: Objectrole: "presenter"__proto__: Object
woogeen.sdk.js:8 ERROR: 54c3b42b4eb96d917a48ec52 subscribe failed: peer connection failed
woogeen.sdk.js:8 ERROR: publish failed: peer connection failed

Appreciate your help. Thanks

Hi Deepa,

Chunbo_H_Intel1 — Mon, 09 Feb 2015 03:45:12 GMT

Hi Deepa,

Main ports on MCU for client connection:

Woogeen ErizoController: 8080 (configurable)

Woogeen Nuve: 3000

Woogeen Streaming: Random Big Port, like 33430, 54578...

Main ports on Peer Server:

8095 for http, 8096 for https

Please make sure those ports are available. And let me know if you still have connection issues.