Intel® Collaboration Suite for WebRTC
Community support and discussions on the Intel® Collaboration Suite for WebRTC (Intel® CS for WebRTC).
Announcements
Welcome to the Intel Community. If you get an answer you like, please mark it as an Accepted Solution to help others. Thank you!
For the latest information on Intel’s response to the Log4j/Log4Shell vulnerability, please see Intel-SA-00646

Issue with forward Stream

Naresh_R_1
New Contributor I
247 Views

Dear Team,

We installed Intel CS MCU 4.1 in AWS cloud and opened all ports, below is the configuration for webrtc_agent. used nginx as reverse proxy webserver and with https SSL Certificates 

network_interfaces = [{name = "eth0", replaced_ip_address = "18.136.148.95"}]

maxport = 49152 #default: 0

minport = 65535 #default: 0

When we try to open basic example app with forward true we are getting below error when it is opened in 3 tabs and we have restart mcu again

but with mixing its working fine with multiple tabs

Kindly help with the issue

https://mcu.domain.com/?forward=true

ics.js:8 Empty candidate.
ics.js:8 ICE connection state changed to checking
ics.js:8 Remote stream added.
ics.js:8 ICE connection state changed to checking
2index.js:32 subscribe failed Error: Source stream loss
    at new t (ics.js:8)
    at t.value (ics.js:8)
    at t.value (ics.js:8)
    at O (ics.js:8)
    at ics.js:8
    at ics.js:8
    at Array.map (<anonymous>)
    at t.dispatchEvent (ics.js:8)
    at Socket.<anonymous> (ics.js:8)
    at Socket.Emitter.emit (socket.io.js:3)
3ics.js:8 ICE connection state changed to failed
ics.js:8 Uncaught (in promise) Error: ICE connection failed or closed.
    at new t (ics.js:8)
    at t.value (ics.js:8)
    at RTCPeerConnection._pc.oniceconnectionstatechange (ics.js:8)

 

Thanks

Naresh

0 Kudos
5 Replies
Qiujiao_W_Intel
Employee
247 Views

Naresh, from your configuration, maxport is smaller than minport, please configure them with valid value

maxport = 49152 #default: 0

minport = 65535 #default: 0

Le__Samuel
Beginner
247 Views

I have the same issue when i try to run webrtc-agent inside of a docker container, this is the log file

2019-01-29 12:45:36.488  - INFO: ErizoJS - pid: 227
2019-01-29 12:45:36.494  - INFO: ErizoJS - Connecting to rabbitMQ server...
2019-01-29 12:45:36.524  - INFO: AmqpClient - Connecting to rabbitMQ server OK, hostPort: { host: '35.247.128.104', port: 5672 }
2019-01-29 12:45:36.616  - INFO: ErizoJS - webrtc-828b95f0907573075d5c@10.148.0.3_0 as rpc server ready
2019-01-29 12:45:36.622  - INFO: ErizoJS - webrtc-828b95f0907573075d5c@10.148.0.3_0 as monitor ready
2019-01-29 12:52:23,246  - WARN: LibNiceConnection -  message: failed and not received all candidates, newComponentState:4
2019-01-29 12:52:23,637  - WARN: LibNiceConnection - ?N message: failed and not received all candidates, newComponentState:4
2019-01-29 12:58:00.938  - WARN: ErizoJS - Exiting on SIGTERM
 

Li_C_Intel
Employee
247 Views

Hi, Le, Samuel

If you start webrtc-agent in a docker container, was your network ok?

Have you tried with docker network=host?

 

Le__Samuel
Beginner
247 Views

Obviously, I have been using network = host and 2 virtual machines:

1, first one runs cluster_managers, nuve, rabbitmq, mongodb

2, second one runs portal, conference agent, webrtc agent, audio, video, streaming agent, all inside of a docker container.

Do i need a Turn server in this case ?

Le__Samuel
Beginner
247 Views

Hi there, I found the solution:

this error is caused by the difference between the default network interface name of different Ubuntu machines.

make sure you run the command "ifconfig" to see your existing network interfaces before specifying : network_interfaces in webrtc-agent/agent.toml

Reply