Is there any tool/client/method to check whether the stun/turn server is working fine, and the performance of it?

[Prinbit]

I am a newbie to turn/stun server, and I am developing a WebRTC-based application.

As usual, we use google turn server by default. 

Some clients reported that they can not connect with each other. so we want ask them to help test the stun/turn server.

Any suggestion? Thanks in advance.

[Oleg Moskalenko]

You have to use your network tools to find out your network situation. The simplest is wire shark. Also the turn server has cli client to check the status.

Sent from my iPhone

--
You received this message because you are subscribed to the Google Groups "TURN Server project rfc5766-turn-server" group.
To unsubscribe from this group and stop receiving emails from it, send an email to turn-server-project-rfc57...@googlegroups.com.
To post to this group, send email to turn-server-project...@googlegroups.com.
Visit this group at http://groups.google.com/group/turn-server-project-rfc5766-turn-server.
For more options, visit https://groups.google.com/groups/opt_out.

[Alexandre GOUAILLARD]

just in case, to state the obvious:

If you *only* use google *stun* server, it is expected that you will fail between 8 and 15% of the case in general. Google turn servers are not usable by third party (as the credential are created on the fly), i.e. even though you can see the IP of their server, you cannot connect to them. Do you mean to say that you are using their STUN servers (which ARE open), or that you installed the same turn server as the one they are using?

Before you check the network, you could check the candidate gathered and see if you have any of type "relay".

If you have installed a TURN server (like the one this list is about), you should fail only in a very few cases.

It also depends on your client capacity to generate ICE candidates. Firefox does not support as much as Chrome for the time being which means, you're more likely to fail to connect with firefox.

[Prinbit]

Thanks, will have a try.

On Monday, December 16, 2013 3:01:18 PM UTC+8, Oleg Moskalenko wrote:

You have to use your network tools to find out your network situation. The simplest is wire shark. Also the turn server has cli client to check the status.

Sent from my iPhone

On Dec 16, 2013, at 8:39 AM, Prinbit <pri...@gmail.com> wrote:

I am a newbie to turn/stun server, and I am developing a WebRTC-based application.

As usual, we use google turn server by default. 

Some clients reported that they can not connect with each other. so we want ask them to help test the stun/turn server.

Any suggestion? Thanks in advance.

--
You received this message because you are subscribed to the Google Groups "TURN Server project rfc5766-turn-server" group.

To unsubscribe from this group and stop receiving emails from it, send an email to turn-server-project-rfc5766-turn-server+unsubscribe@googlegroups.com.
To post to this group, send email to turn-server-project-rfc5766-turn-...@googlegroups.com.

[Prinbit]

There is one situation not included. Due to the bandwidth/limitation of the network, some clients cannot reach the relay server (google turn server).

Next step, I will setup the stun/turn server. From your suggestion, I saw that the installation our own stun/turn server is a better way for performance.

BTW, due to the limitation of resource, if I install the turn/stun server in the same machine of our http server, will the performance be affect? Is there any hardware requirements on stun/turn server? 

Thanks in advance.

On Monday, December 16, 2013 6:17:43 PM UTC+8, Alexandre GOUAILLARD wrote:

just in case, to state the obvious:

If you *only* use google *stun* server, it is expected that you will fail between 8 and 15% of the case in general. Google turn servers are not usable by third party (as the credential are created on the fly), i.e. even though you can see the IP of their server, you cannot connect to them. Do you mean to say that you are using their STUN servers (which ARE open), or that you installed the same turn server as the one they are using?

Before you check the network, you could check the candidate gathered and see if you have any of type "relay".

If you have installed a TURN server (like the one this list is about), you should fail only in a very few cases.

It also depends on your client capacity to generate ICE candidates. Firefox does not support as much as Chrome for the time being which means, you're more likely to fail to connect with firefox.

On Mon, Dec 16, 2013 at 3:01 PM, Oleg Moskalenko <mom0...@gmail.com> wrote:

You have to use your network tools to find out your network situation. The simplest is wire shark. Also the turn server has cli client to check the status.

Sent from my iPhone

On Dec 16, 2013, at 8:39 AM, Prinbit <pri...@gmail.com> wrote:

I am a newbie to turn/stun server, and I am developing a WebRTC-based application.

As usual, we use google turn server by default. 

Some clients reported that they can not connect with each other. so we want ask them to help test the stun/turn server.

Any suggestion? Thanks in advance.

--
You received this message because you are subscribed to the Google Groups "TURN Server project rfc5766-turn-server" group.

To unsubscribe from this group and stop receiving emails from it, send an email to turn-server-project-rfc5766-turn-server+unsubscribe@googlegroups.com.
To post to this group, send email to turn-server-project-rfc5766-turn-...@googlegroups.com.

Visit this group at http://groups.google.com/group/turn-server-project-rfc5766-turn-server.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "TURN Server project rfc5766-turn-server" group.

To unsubscribe from this group and stop receiving emails from it, send an email to turn-server-project-rfc5766-turn-server+unsubscribe@googlegroups.com.
To post to this group, send email to turn-server-project-rfc5766-turn-...@googlegroups.com.

[Prinbit]

There is one situation not included. Due to the bandwidth/limitation of the network, some clients cannot reach the relay server (google turn server).

Next step, I will setup the stun/turn server. From your suggestion, I saw that the installation our own stun/turn server is a better way for performance.

BTW, due to the limitation of resource, if I install the turn/stun server in the same machine of our http server, will the performance be affect? Is there any hardware requirements on stun/turn server? 

Thanks in advance.

On Monday, December 16, 2013 6:17:43 PM UTC+8, Alexandre GOUAILLARD wrote:

just in case, to state the obvious:

If you *only* use google *stun* server, it is expected that you will fail between 8 and 15% of the case in general. Google turn servers are not usable by third party (as the credential are created on the fly), i.e. even though you can see the IP of their server, you cannot connect to them. Do you mean to say that you are using their STUN servers (which ARE open), or that you installed the same turn server as the one they are using?

Before you check the network, you could check the candidate gathered and see if you have any of type "relay".

If you have installed a TURN server (like the one this list is about), you should fail only in a very few cases.

It also depends on your client capacity to generate ICE candidates. Firefox does not support as much as Chrome for the time being which means, you're more likely to fail to connect with firefox.

On Mon, Dec 16, 2013 at 3:01 PM, Oleg Moskalenko <mom0...@gmail.com> wrote:

You have to use your network tools to find out your network situation. The simplest is wire shark. Also the turn server has cli client to check the status.

Sent from my iPhone

On Dec 16, 2013, at 8:39 AM, Prinbit <pri...@gmail.com> wrote:

I am a newbie to turn/stun server, and I am developing a WebRTC-based application.

As usual, we use google turn server by default. 

Some clients reported that they can not connect with each other. so we want ask them to help test the stun/turn server.

Any suggestion? Thanks in advance.

--
You received this message because you are subscribed to the Google Groups "TURN Server project rfc5766-turn-server" group.

To unsubscribe from this group and stop receiving emails from it, send an email to turn-server-project-rfc5766-turn-server+unsubscribe@googlegroups.com.
To post to this group, send email to turn-server-project-rfc5766-turn-...@googlegroups.com.

Visit this group at http://groups.google.com/group/turn-server-project-rfc5766-turn-server.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "TURN Server project rfc5766-turn-server" group.

To unsubscribe from this group and stop receiving emails from it, send an email to turn-server-project-rfc5766-turn-server+unsubscribe@googlegroups.com.
To post to this group, send email to turn-server-project-rfc5766-turn-...@googlegroups.com.

[Oleg Moskalenko]

On Mon, Dec 16, 2013 at 4:22 AM, Prinbit <pri...@gmail.com> wrote:

There is one situation not included. Due to the bandwidth/limitation of the network, some clients cannot reach the relay server (google turn server).

Next step, I will setup the stun/turn server. From your suggestion, I saw that the installation our own stun/turn server is a better way for performance.

BTW, due to the limitation of resource, if I install the turn/stun server in the same machine of our http server, will the performance be affect?

Yes of course. Big time.

 

Is there any hardware requirements on stun/turn server? 

No special requirements - but the better system, your are getting the better performance.

 

[Fabian Bernhard]

 

Is there any hardware requirements on stun/turn server? 

No special requirements - but the better system, your are getting the better performance.

 

Oleg, can you give a suggestion for the hardware requirements or an example for a server setup that you run? For instance X GB RAM and Y CPU allow my to have Z concurrent sessions? We would like to order servers now and are not sure about the requirements. 

Thanks a lot!

[Oleg Moskalenko]

Hi Fabian

I can give you a suggested hardware configuration, but nobody will tell you how many sessions it can support. If somebody would suggest a definite figure, do not trust him - that's virtually impossible to determine. You can find it out only in practice.

The things that affect the number of concurrent sessions:

1) Media group:
   - Codec to be used (payload size).
   - Packet interval.

2) Network topology and protocols group:
  - ISP performance.
  - In each peer-to-peer session, how many TURN sessions are involved - two (when both peers connect to the TURN server) or one (when one peer is talking to the relay endpoint).
  - Which protocols are involved (TCP, UDP or TLS).
  - If TLS is involved, then the parameters of the TLS sessions (how heavy they are) are important.
  - Can your client use alternate-server 300 error for balancing ? (WebRTC client cannot, as of now).
  - Can you use round-robin DNS for balancing ?

3) Hardware & OS group:
  - Number of NICs.
  - How advanced are the NICs.
  - System memory and bus performance (lots of traffic is going thru).
  - Number of CPUs and CPU performance (cache etc).
  - OS type and version.
  - How well NICs are integrated with your OS (whether your drivers are using full NIC capabilities).

All this makes big difference.

Read the wiki performance page on the project site. A few Gbs of RAM and high-end CPUs and NIC(s) will give you the best performance. There are also OS recommendations. But how many sessions - you will determine that by yourself.

We are trying to optimize the TURN server for the wide range of the loads to make it usable for everyone on any platform.

Regards,
Oleg