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

Can't connect to the conference in a public network. Joining room failed.

Hi, everyone.

I've encountered two issues. I deployed the server on a computer with Ubuntu 18.04 and I tested the availability of conference in local network. However, after I configured the sip server and tested sip calls in conference with several sip devices, I can't connect to the server with any other devices like phones or browsers. I got the wrong message "Joining room failed." in Chrome console. Before that message, there were "TypeError: publicationGlobal is undefined" and "Error: Portal is not connected." errors as well. But these two errors seem trivial because it still worked on another computer with these two errors. Some logs are shown below:

In portal.stdout:

2019-11-12 16:15:07.276  - INFO: Main - start socket.io server ok.
2019-11-12 16:15:33.964  - INFO: SocketIOServer - Login failed: Joining room failed

In conference-XX.log:

2019-11-12 16:14:57.268  - DEBUG: WorkingNode - No native logger for reconfiguration
2019-11-12 16:14:57.294  - INFO: WorkingNode - pid: 9433
2019-11-12 16:14:57.294  - INFO: WorkingNode - Connecting to rabbitMQ server...
2019-11-12 16:14:57.302  - INFO: AmqpClient - Connecting to rabbitMQ server OK, options: { host: 'localhost', port: 5672 }
2019-11-12 16:14:57.445  - INFO: WorkingNode - conference-7efe4511a6475463d81e@192.168.100.52_1 as rpc server ready
2019-11-12 16:14:57.447  - INFO: WorkingNode - conference-7efe4511a6475463d81e@192.168.100.52_1 as monitor ready
2019-11-12 16:16:48.082  - ERROR: RoomController - new mix terminal failed. room_id: 5dc9fbcaf2ff5857d53a21a8 reason: Failed in scheduling video worker, reason: No worker matches the preference.
2019-11-12 16:16:48.082  - ERROR: RoomController - init fail. view: common reason: Failed in scheduling video worker, reason: No worker matches the preference.
2019-11-12 16:16:48.083  - ERROR: Conference - roomController init failed. Failed in scheduling video worker, reason: No worker matches the preference.
2019-11-12 16:16:48.083  - ERROR: Conference - Init room failed, reason: roomController init failed. reason: Failed in scheduling video worker, reason: No worker matches the preference.
2019-11-12 16:16:48.083  - WARN: Conference - Participant U85_ZmXNwHrbs7KpAAAB join room 5dc9fbcaf2ff5857d53a21a8 failed, err: roomController init failed. reason: Failed in scheduling video worker, reason: No worker matches the preference.

 

Then I tried to deploy the server on another computer and worked well in local network. But after I set the IP to a public IP, I couldn't connect to the conference via 4G or Wifi with mobile phones or browsers. I've set the IP in portal/portal.toml and network_interfaces in webrtc_agent/agent.toml, set the port of socket.io to 3456 and mapped the ports 3000, 3004, 3300, 3456 and 5672. I could still visit https://ip:3004 and https:ip:3300/console. But only the camera was on and it couldn't neither publish nor subscribe streams from the server. Here are the logs in Chrome console:

Remote stream added.

ICE connection state changed to checking

Empty candidate.

ICE connection state changed to failed.

subscribe failed Error: connection failed. at t.value (owt.js:9) at t.value (owt.js:9) at RTCPeerConnection._pc.oniceconnectionstatechange (owt.js:9)

Neither publication nor subscription is available

Uncaught (in promise) Error: connecttion failed. at t.value (owt.js:9) at t.value (owt.js:9) at RTCPeerConnection._pc.oniceconnectionstatechange (owt.js:9)

 

I've followed the instructions in OWT Server User Guide and from other blogs. But I don't know if I missed some important steps to run the server properly.

Any help will be appreciated. Thanks.

Tags (2)
0 Kudos
2 Replies
Highlighted
Beginner
14 Views

我也遇到了相同的问题,请问在新版本中解决了吗  

我也遇到了相同的问题,请问在新版本中解决了吗

 

0 Kudos
Highlighted
14 Views

2019-11-12 16:16:48.082  -

2019-11-12 16:16:48.082  - ERROR: RoomController - new mix terminal failed. room_id: 5dc9fbcaf2ff5857d53a21a8 reason: Failed in scheduling video worker, reason: No worker matches the preference.
2019-11-12 16:16:48.082  - ERROR: RoomController - init fail. view: common reason: Failed in scheduling video worker, reason: No worker matches the preference.
2019-11-12 16:16:48.083  - ERROR: Conference - roomController init failed. Failed in scheduling video worker, reason: No worker matches the preference.
2019-11-12 16:16:48.083  - ERROR: Conference - Init room failed, reason: roomController init failed. reason: Failed in scheduling video worker, reason: No worker matches the preference.

 

These error logs indicate the video codec capability does not match the room setting. H264 is default configured, but openH264 library need be manually installed. Please follow below document. If HEVC was configured, SVT_HEVC need be manually install by " video_agent.compile_svtHevcEncoder.sh".

 

https://github.com/open-webrtc-toolkit/owt-server#quick-start

 

Quick Start

In the repository root, run following commands to start media server on single machine:

1. ./bin/init-all.sh --deps

2. ./bin/start-all.sh

3. Open https://localhost:3004 to visit the web sample page. Due to the test certificate, you may need confirm this unsafe access.

 

 

0 Kudos