Intel® Collaboration Suite for WebRTC
Community support and discussions on the Intel® Collaboration Suite for WebRTC (Intel® CS for WebRTC).
Announcements
The Intel sign-in experience is changing in February to support enhanced security controls. If you sign in, click here for more information.

https://XXXXX:3004 is not working.

Juhee_K_
Beginner
205 Views

To verify whether the server installed successfully, I ran https://XXXXX:3004 on Chrome Browser.
but console log was shown "INFO: ICE Connection Failed" and "ERROR: 57e9f8bce1209XXXXXXXX subscribe failed: peer connection failed" at client 
and web rtc log was shown "ERROR: NiceConnection - video - NICE Component 1 FAILED" and "ERROR: NiceConnection - Nice Failed, stopping ICE" at Server .
What is the problem?.

I atteched client log and server WebRTC log.
Because Our Server is on Amason Web service. private ip is 172.31.XX.XX and public ip is 52.78.XX.XX.

Please give me everything you have about this question?
Thinks a lot for you in advance

0 Kudos
5 Replies
Juhee_K_
Beginner
205 Views

current Server version is 3.2....

Lei_Z_Intel1
Employee
205 Views

Have you open all required ports in AWS security policy, including all UDP ports?

Juhee_K_
Beginner
205 Views

443(UDP),3000(TCP),3001(TCP/UDP),3004(TCP/UDP),4478(TCP/UDP),8080(TCP/UDP),8095(TCP/UDP),8096(TCP/UDP),8124(TCP/UDP),8125(TCP/UDP) ports opened.

Lei_Z_Intel1
Employee
205 Views

The peer connection relies on wider UDP ports, usually > 10000 and < 65535, which is also configurable in MCU access agent configuration.

Juhee_K_
Beginner
205 Views

Hi Lei,

it's good work. 

Thank you for your help.

Reply