Connect - TURN server

Interested in talking about Mash-up's? This is the place.
marko
Posts: 4
Joined: Fri Jul 26, 2019 8:32 am

Connect - TURN server

Postby marko » Mon Mar 23, 2020 12:46 pm

If I configure 2 accounts on this way:
zxsuite connect iceServer add turn:[IP]:443?transport=tcp username user credential pass account user1@domain.com
zxsuite connect iceServer add turn:[IP]:443?transport=tcp username user credential pass account user2@domain.com

I can establish connection if user1 is on VPN, and user2 is on public internet. But I thinks that this is not a good idea (because of number of users), so I try to configure TURN based on COS or DEFAULT, but without any success. Is there some problem in commands:

Based on COS:
zxsuite connect iceServer add turn:[IP]:443?transport=tcp username user credential pass cos cosName

Based on DEFAULT:
zxsuite connect iceServer add turn:[IP]:443?transport=tcp username user credential pass

Many thanks!


juanrossi
Posts: 3
Joined: Sat Apr 04, 2020 1:42 pm

Re: Connect - TURN server

Postby juanrossi » Sat Apr 04, 2020 1:44 pm

I have the same problems. My internet provider has blocked me from accessing any VPN. Do you solve your problems? I would advise you to figure out with this article about How to Watch Popcorn Time on Chromecast - webguidevpn
User avatar
rleiker
Advanced member
Advanced member
Posts: 56
Joined: Tue Jan 07, 2020 8:23 pm
Location: Kansas City
Contact:

Re: Connect - TURN server

Postby rleiker » Mon Apr 13, 2020 8:38 pm

marko wrote:If I configure 2 accounts on this way:
zxsuite connect iceServer add turn:[IP]:443?transport=tcp username user credential pass account user1@domain.com
zxsuite connect iceServer add turn:[IP]:443?transport=tcp username user credential pass account user2@domain.com


Marko,

If you have not already, take a look at my guide for setting up a STUN/TURN server: viewtopic.php?f=45&t=67960 . This will help ensure you have all of the settings on your TURN server correct. While the "zxsuite connect iceServer add" command does allow defining a TURN server globally, by COS, or by account, you may find it difficult to scale up by specifying a TURN server per account. I would suggest this command instead to specify a single global TURN server to start:

zxsuite connect iceServer add turn:[IP]:443?transport=tcp credential pass username user

In speaking with somone a few weeks ago who does support at Zextras, he explained that while the "zxsuite connect iceServer add" command will allow multiple TURN server user accounts to be used, Zimbra Connect is designed to only use the first user account that is configured. So, for example, if you used:

zxsuite connect iceServer add turn:[IP]:443?transport=tcp credential pass1 username user1
zxsuite connect iceServer add turn:[IP]:443?transport=tcp credential pass2 username user2

The "user2" TURN account would never be used by Zimbra Connect. I am guessing Zextras built it this way with the intent to introduce some kind of load balancing in the future, but that capability apparently does not yet exist in Zimbra Connect. My understanding is that the majority of Zimbra Connect users will use WebRTC peer-to-peer connections, with an estimated 20% of Zimbra Connect users needing to fall back to a TURN server for connectivity.

Return to “Zimlets”

Who is online

Users browsing this forum: No registered users and 2 guests