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

index.js:107 subscribe failed Error: connection failed. (v.4.3) - High priority

Chandramouli_P
Beginner
2,587 Views

Hello Team,

We are currently using Intel CS for WebRTC frame work v.4.2.1 and successfully rinning. Now, We installed v.4.3 on both CentOS 7.x and Ubuntu 18.04 (AWS environment) and facing issues. When we are trying to run the sample application in mixed mode and as well as in forward mode also, sample application is not running properly. Some participants are not joining in the call, some participants are disconnecting from the call suddenly, unable to see the participants even though they joined and subscribed, etc.

Please note that our STUN/TURN server is working fine. But, we tried with other STUN/TURN servers also. Also, v.4.2.1 is successfully running in our environment.

We are getting the below messages in Browser's console:

ICE connection state changed to closed
index.js:129 914228465648075000 is ended.
owt.js:9 MCU returns negative ack for unsubscribing, Subscription does NOT exist
(anonymous) @ owt.js:9
index.js:124 A new stream is added  277758274357334370
rest-sample.js:39 Result: Object
owt.js:9 Empty candidate.
owt.js:9 ICE connection state changed to checking
2owt.js:9 Remote stream added.
owt.js:9 ICE connection state changed to connected
owt.js:9 ICE connection state changed to disconnected
index.js:107 subscribe failed Error: connection failed.
   at t.value (owt.js:9)
   at t.value (owt.js:9)
   at RTCPeerConnection._pc.onconnectionstatechange (owt.js:9)

index.js:124 A new stream is added  938158615098228200

As this is a blocking issue to start working with v.4.3, request you to help us to resolve the issue.

Thank you.

Best Regards,
Chandramouli.

0 Kudos
10 Replies
Chandramouli_P
Beginner
2,587 Views

Hello Team,

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

Thank you.

Best Regards,
Chandramouli.

0 Kudos
YanbinZ_Intel
Employee
2,587 Views

Hello Chandramouli.

Do you means same environment with STUN/TURN server  4.2.x works fine while 4.3 don't work ?

 Could you please provide more information e.g your configuration at server side  and your detail test steps ?

 

Thanks

Yanbin

 

0 Kudos
YanbinZ_Intel
Employee
2,587 Views

And , Could you upload your server side log information ?

0 Kudos
Chandramouli_P
Beginner
2,587 Views

Hello Yanbin,

Good evening and thank you for your reply. We are following same installation process only to 4.3 version, like 4.2 and 4.2.1 versions. The same environment is successfully working in 4.2.1 version. Also, same environment with STUN/TURN server, 4.2.x works fine while 4.3 is not working. As I noticed, there are no error messages in logs. Anyway, please find the below information as you asked:

Environment:
Server (MCU) Operating System: Ubuntu 18.04 Server (Minimal version - command line only) and CentOS 7.x (Minimal version - command line only)
Linux Kernel Version: 4.15.0-69-generic (Default) and 5.3.6 (Low latency - Updated)
Browser: Google Chrome Version 77.0.3865.90 (Official Build) (64-bit) and Firefox on Windows 10 Pro
Intel CS for WebRTC Version: 4.3
Firewall: No firewall and all ports are opened
Cloud Environment: AWS

Installation Steps:
1) Installed updates and essential common development libraries
2) Removed firewalld and iptables
3) Installed RabbitMQ, and MongoDB in the same server only
4) Installed NodeJS 8.x
5) Download and unzip CS_WebRTC_Conference_Server_MCU.v4.3.Ubuntu.tgz
6) Installed dependencies in video_agent folder (./install_deps.sh)
7) Installed openh264 library in video_agent folder (./install_openh264.sh)
8) ./compile_ffmpeg_with_libfdkaac.sh in audio_agent folder
9) cp ffmpeg_libfdkaac_lib/* lib/
10) Installed dependencies (./install_deps.sh) in conference_agent, streaming_agent, recording_agent, and sip_agent folders individually to avoid "Connection to rabbitMQ server error Error: libavformat.so.58: cannot open shared object file" error.
11) Changed private IP address and public IP address in the respective .toml files (as same as v.4.2.1)
12) sudo bin/init-all.sh [--deps]
13) sudo bin/start-all.sh
14) Run the sample application from the browser

Please find the logs that you asked in the below link:

https://pastebin.com/be7MSVKU

These are the steps that I followed. Please correct me, If there is anything wrong. If you need any other information, please let me know. I look forward to hearing from you.

Thank you

Best Regards,
Chandramouli.

0 Kudos
Li_C_Intel
Employee
2,587 Views

Hi,

If 4.2.1 works well. You can replace the folder Release-v4.3/extras with Release-v4.2.1/extras and have a try.

I think STUN/TURN needs modification to js sample and your previous 4.2.1 may contain that change.

Don't forget to run bin/init-all.sh after you replace the folder.

0 Kudos
Ravi_Prakash
New Contributor I
2,386 Views

can u give me a sample configuration file for webrtc_agent/agent.toml ?

 

0 Kudos
Chandramouli_P
Beginner
2,587 Views

Hello Li,

Good evening and thank you for your reply. As you suggested, I replaced the "extras" folder with v.4.2.1. But, still getting the same issue. Also, I added ICE STUN/TURN servers information in example application (Release-v4.3/extras/basic_example/public/scripts/index.js). But, getting the same issue. For your convenience, I setup the whole thing in a server and shared the server details with "Wang Yan". Could you please test it once directly? So, you can see the things directly.

We look forward to your help.

Thank you.

Best Regards,
Chandramouli.

0 Kudos
Chandramouli_P
Beginner
2,587 Views

Hello Li,

Good evening and any help would be appreciated.

Thank you.

Best Regards,
Chandramouli.

0 Kudos
Ravi_Prakash
New Contributor I
2,381 Views

Hi Chandra,

I am also stuck in same situation, the browser console log is as follows:

 

Streams in conference: 1
index.js:202 Participants in conference: 1
2owt.js:9 Empty candidate.
owt.js:9 ICE connection state changed to checking
2owt.js:9 Remote stream added.
owt.js:9 ICE connection state changed to checking
owt.js:9 ICE connection state changed to disconnected
index.js:107 subscribe failed Error: connection failed.
at t.value (owt.js:9)
at t.value (owt.js:9)
at RTCPeerConnection._pc.onconnectionstatechange (owt.js:9)
owt.js:9 ICE connection state changed to disconnected
owt.js:9 Uncaught (in promise) Error: connection failed.
at t.value (owt.js:9)
at t.value (owt.js:9)
at RTCPeerConnection._pc.onconnectionstatechange (owt.js:9)

 

 

How did you solve it?

 

Thanks 

0 Kudos
afei
Beginner
2,142 Views

it may be not a ice problem, see this issue :https://github.com/open-webrtc-toolkit/owt-server/pull/599

use new chrome version and the 4.3.1 release package may happen this problem.

I use 4.3.x branch,and compile it,resolve this problem

eg:4.3.x use node 10.21.0

 

0 Kudos
Reply