Intel® Collaboration Suite for WebRTC
Community support and discussions on the Intel® Collaboration Suite for WebRTC (Intel® CS for WebRTC).

Error creating superservice

Jorge_D_
Beginner
1,157 Views

Hi,

I am trying to install the MCU Server but I got this error, May you help me with this issue?

I have:

Ubuntu 12 LTS

Node.js 0.10.33

Mongo 2.6.3

SuperService ID: Mon Mar 9 12:02:04.432 TypeError: Cannot read property '_id' of null
SuperService KEY: Mon Mar  9 12:02:04.479 TypeError: Cannot read property 'key' of null
sed: -e expression #1, char 25: unterminated `s' command
sed: -e expression #1, char 26: unterminated `s' command

0 Kudos
1 Solution
Artem_M_
New Contributor I
1,157 Views

Try to create service manually and restart init file:

mongo nuvedb
db.services.insert({name: 'superService', key: '0000', rooms: []})

 

View solution in original post

0 Kudos
7 Replies
Jorge_D_
Beginner
1,157 Views

-

0 Kudos
Artem_M_
New Contributor I
1,158 Views

Try to create service manually and restart init file:

mongo nuvedb
db.services.insert({name: 'superService', key: '0000', rooms: []})

 

0 Kudos
Jorge_D_
Beginner
1,157 Views

Hi Artem,

Thank you, It worked.

I have other problems:

My FW is up, What ports must be opened?

I have in my list 3001, 5672 but service doesn't work if FW is up, Which ones am I missing?.

The other one is about creating a room and token (I am testing the MCU Server):

The api is asking for:

Woogeen.API.init(SERVICEID, SERVICEKEY, SERVICEHOST);

the first two are the same above you wrote me? 'superService' and '0000'

 

Once again thanks for your help and support.

 

0 Kudos
Chunbo_H_Intel1
Employee
1,157 Views

On MCU server, the following default ports have been assigned for MCU usage: 5672 (configurable), 8080 (configurable), 3000. Make sure they are always available for MCU as well as 3001, 3004 if you're using basic sample.

Another thing is WebRTC streaming itself which will use random big port, like 33430, 54578 on MCU.

0 Kudos
Chunbo_H_Intel1
Employee
1,157 Views

As for the super service id and key values, refer to the init.sh script:

  local SERVID=$(mongo ${dbURL} --quiet --eval 'db.services.findOne({"name":"superService"})._id')
  local SERVKEY=$(mongo ${dbURL} --quiet --eval 'db.services.findOne({"name":"superService"}).key')

0 Kudos
Jorge_D_
Beginner
1,157 Views

Hi Chunbo,

It worked so fine, for both, ports and superService.

Thanks for your help and support.

PD: I am testing other things maybe I will come back here :D.

 

0 Kudos
Chunbo_H_Intel1
Employee
1,157 Views

Sure. Really nice of you to say so.

0 Kudos
Reply