After update WCS - turn server problem

cheinan

Member
Hello
I did update to the latest available version
In order to solve Edge webRTC error c0044003 problem.
I ran: service webcallserver update
From WCS version: v. 0.5.25.2455 - 5.0.2596
I update to: v. 0.5.28.2747 - 5.0.2971
And since then my coturn turnserver (which is installed on the same Linux server) is not working with WCS
And i cold not use webRTC in cellular networks.
I call the turn server:
connectionOptions = {
urlServer: urlMediaServer,
mediaOptions: {
"iceServers": [{ 'url': 'turn:urlTurnServer:443?transport=tcp', 'username': 'theUserName', 'credential': 'thePass' }]
}
};

Any idea Way?
 

Max

Administrator
Staff member
Hello
It looks like Edge does not support TCP based TURN servers.
Here you can find the Microsoft ORTC guide and it does not mention TCP ICE support.
https://docs.microsoft.com/en-us/microsoft-edge/dev-guide/realtime-communication/object-rtc-api
Here another github issue related TCP ICE support in Edge browsers.
https://github.com/webrtc/adapter/issues/573
So the issue should be resolved by Microsoft Edge developers.

As a workaround you may try MSE (Media Source Extension).
Try our default sample Embed Player and apply MSE as media provider.
https://wcs5-eu.flashphoner.com/client2/examples/demo/streaming/embed_player/sample.html
 

Attachments

cheinan

Member
Tested my turn server on your demo: Firewall Streaming
with v. 0.5.28.2747 - 5.0.2966
It is working fine.
So i guess i will try to update my server again...
 

cheinan

Member
After doing update again:
From my server demo
i cold not connect to either my turn server, or your demo turn server.
And from your WCS example demo i can connect to both...
My server is behind net
So what cold be blocking my WCS from connect to turn server?
Do i need to install HAproxy as well on my Linux server?

Thanks
Cheinan
 
Last edited:

Max

Administrator
Staff member
Hello
We have two servers:
wcs5-eu.flashphoner.com:443 (websocket).
turn.flashphoner.com:443 (TURN TCP relay).
So if you have only 443 port open, it should work.
Therefore to get this working you need two different servers.
Do i need to install HAproxy as well on my Linux server?
HAproxy will not help to recognize and separate between Websocket and TURN traffic.
It will rather help to separate https 443 and websocket 443 traffic.
In our installation:
HAproxy is bound on wcs5-eu.flashphoner.com:443
- forwards to Websocket
- forwards
TURN is bound on turn.flashphoner.com:443
It is two different servers.
 

cheinan

Member
Hi Max
Thanks for your replays.

I will try to put focus on my problem:
In my old Linux server which was not behind net
I cold connect with WCS to any turn server.
In my new Linux server which is behind net
I cold not connect with WCS to any turn server.

When i try with your demo in your server:
https://wcs5-eu.flashphoner.com:8888/login.xhtml
In Firewall Streaming example i can connect with your WCS to
Both my old and new turn servers.
But when i try with my WCS Firewall Streaming example, i cold not connect to any turn server.

What can block my WCS from connecting to any turn server?

Thanks
Cheinan
 

Max

Administrator
Staff member
Maybe it is a firewall.
Make sure your WCS UDP ports are open for TURN server. Try to disable firewall on WCS server.
Default UDP port range is [31000-32000] in flashphoner.properties
 
Top