Error: Joining room failed (v.4.3), when enabling hardware acceleration

[Chandramouli_P]

Hello,

Please find the environment:

Operating System: Ubuntu 18.04 Server and CentOS 7.x
Linux Kernel Version: 4.15.0-69-generic
Browser: Google Chrome Version 77.0.3865.90 (Official Build) (64-bit)
Intel CS for WebRTC Version: 4.3
Firewall: No firewall and all ports are opened

We successfully deployed previous versions of Intel CS for WebRTC framework earlier in various environments. When we are trying to install v.4.3, we are getting "Joining room failed" error. We tried with default certificate, SSL certificated which is generated with OpenSSL, and also with purchased certificate. I also tried with AWS environment and in our LAN server also. But, getting the same error, when I am executing the https://1.2.3.4:3004 URL in the browser. I am not getting any errors in the log files also, except the below error.

Please find the below error:
Failed to load resource: net::ERR_CONNECTION_CLOSED
Failed to load resource: the server responded with a status of 404 ()
WebSocket connection to 'wss://1.2.3.4:8080/socket.io/?EIO=3&transport=websocket&sid=cw4bbpFEaMcrKI4UAAAA' failed: WebSocket is closed before the connection is established.
server connection failed: Error: Joining room failed

Any help would be really appreciated.

Thank you.

Best Regards,
Chandramouli.
 

[Chandramouli_P]

Hello Li,

Good afternoon and thank you for your reply. I am just trying to run the sample application and haven't changed anything including codecs, etc.

Please find the below logs that you asked:

video-8f41df4b1b107dc2e1a3@192.168.73.182_0.log:
2019-11-21 15:40:08.834  - INFO: WorkingNode - pid: 4835
2019-11-21 15:40:08.835  - INFO: WorkingNode - Connecting to rabbitMQ server...
2019-11-21 15:40:08.844  - INFO: AmqpClient - Connecting to rabbitMQ server OK, options: { host: 'localhost', port: 5672 }
2019-11-21 15:40:08.897  - INFO: InternalConnectionFactory - QUIC is not enabled for internal IO
2019-11-21 15:40:09.148  - INFO: WorkingNode - video-8f41df4b1b107dc2e1a3@192.168.73.182_0 as rpc server ready
2019-11-21 15:40:09.157  - INFO: WorkingNode - video-8f41df4b1b107dc2e1a3@192.168.73.182_0 as monitor ready
2019-11-21 16:02:46.001  - WARN: WorkingNode - Exiting on SIGTERM

video-8f41df4b1b107dc2e1a3@192.168.73.182_1.log:
2019-11-21 15:40:08.833  - INFO: WorkingNode - pid: 4836
2019-11-21 15:40:08.835  - INFO: WorkingNode - Connecting to rabbitMQ server...
2019-11-21 15:40:08.843  - INFO: AmqpClient - Connecting to rabbitMQ server OK, options: { host: 'localhost', port: 5672 }
2019-11-21 15:40:08.897  - INFO: InternalConnectionFactory - QUIC is not enabled for internal IO
2019-11-21 15:40:09.148  - INFO: WorkingNode - video-8f41df4b1b107dc2e1a3@192.168.73.182_1 as rpc server ready
2019-11-21 15:40:09.157  - INFO: WorkingNode - video-8f41df4b1b107dc2e1a3@192.168.73.182_1 as monitor ready
2019-11-21 16:02:46.002  - WARN: WorkingNode - Exiting on SIGTERM

video-agent.stdout:
2019-11-21 15:40:08.744  - INFO: AmqpClient - Connecting to rabbitMQ server OK, options: { host: 'localhost', port: 5672 }
2019-11-21 15:40:08.755  - INFO: WorkingAgent - video agent join cluster ok.
2019-11-21 15:40:08.758  - INFO: ClusterWorker - Join cluster owt-cluster OK.
2019-11-21 15:40:08.762  - INFO: WorkingAgent - as rpc server ok.
2019-11-21 15:40:08.763  - INFO: WorkingAgent - as monitoring target ok.
2019-11-21 16:02:46.000  - WARN: WorkingAgent - Exiting on SIGTERM
2019-11-21 16:02:46.002  - INFO: LoadCollector - To stop load collector.

If you need any other information, please let me know.

Thank you.

Best Regards,
Chandramouli.

[Chandramouli_P]

Hello Li,

Good morning and hope you had a great weekend. Any help would be appreciated.

Thank you.

Best Regards,
Chandramouli.

[Chandramouli_P]

Hello Li,

Any help would be appreciated.

Thank you.

Best Regards,
Chandramouli.

[Chandramouli_P]

Hello Li,

Any help would be appreciated.

Thank you.

Best Regards,
Chandramouli.

[Chandramouli_P]

Hello Li,

Good morning and hope you had a great weekend. Any help would be appreciated.

Thank you.

Best Regards,
Chandramouli.

[Chandramouli_P]

Hello Li,

Any help would be appreciated.

Thank you.

Best Regards,
Chandramouli.

[Li_C_Intel]

Hi, have you run "./video_agent/install_openh264.sh" before start h264 video?

[Chandramouli_P]

Hello Li,

Good evening and thank you very much for your reply. As you suggested, I executed "./video_agent/install_openh264.sh" and installed Cisco h264 library. Now, it is working fine. But, in this scenario, I have below queries:

1) After executing "./video_agent/install_deps.sh --hardware", it is installing Cisco h264 library also. But, I got the problem to join in a room.
2) After executing aboe Step(1), As you suggested, I executed "./video_agent/install_openh264.sh" separately. It is working fine now and able to join in the room. If I understand correctly, Step(1) script is also calling "install_openh264.sh" to install Cisco h264 library. Could you please explain the difference?
3) Most importantly, we are using the MCU server with Intel integrated graphics card (UHD 630) and enabled the hardware acceleration. In this case, why should I depend on Cisco h264 software library?

Thank you very much, once again.

Best Regards,
Chandramouli.

[Chandramouli_P]

Hello Team,

Good evening and any help would be appreciated.

Thank you.

Best Regards,
Chandramouli.

[Chandramouli_P]

Hello Team,

Good evening and wish you a very happy new year. Any help would be appreciated.

Thank you.

Best Regards,
Chandramouli.

[Li_C_Intel]

Hi,

If you use hardware h264, then openh264 is unnecessary.

So your server may not enable hardware mode.

[Li_C_Intel · Accepted solution]

Hi,

Have you run `video_agent/init.sh --hardware` after `install_deps.sh --hardware`?

[Chandramouli_P]

Hello Li,

Thank you for your reply and I understand.

Thank you.

Best Regards,
Chandramouli.