instrumentisto / coturn-docker-image

[Closed] Coturn TURN server Docker image
Other
191 stars 47 forks source link

Test coturn server #15

Closed Sudheerkumar closed 4 years ago

Sudheerkumar commented 4 years ago

Once we pull the docker image and run with the command specified in the readme.md how do we test and check if the turnserver is working as expected?

Any tools available to test the working of turnserver

tyranron commented 4 years ago

@Sudheerkumar we've tested that Coturn works as expected with Trickle ICE and our inner Kurento-based WebRTC tests.

Sudheerkumar commented 4 years ago

Hi @tyranron What i meant was, I run the image using docker run command like this

docker run -d --network=host instrumentisto/coturn \ -n --log-file=stdout \ --min-port=49160 --max-port=49200 \ --lt-cred-mech --fingerprint \ --no-multicast-peers --no-cli \ --no-tlsv1 --no-tlsv1_1 \ --realm=my.realm.org \ it gives me some default code, but dont get any logs to the console and we are unable to connect to the turnserver. At app side it gives ICE connection failed error.

Not very sure if I missed any configs.

Steps followed:

  1. docker pull image
  2. docker run

Help is much apprecaited. Thank you.

tyranron commented 4 years ago

@Sudheerkumar hmmm... at least you should be able to connect to the server's STUN/TURN ports with telnet/nc. Have you tried that? If no logs appears, have you checked if incoming traffic on those ports is not blocked with any firewall rules?

Sudheerkumar commented 4 years ago

I tried to do VNC using the ip and port number. It gives me a "Socket error while reading" message.

CoreyCole commented 4 years ago

When you run the docker container in network=host mode, it is as if the server is running localhost on your host machine. This means the ports on your machine (49160-49200/udp and 3478) need to be open.

What does your test configuration look like. Are you attempting to connect two different web browsers on the same subnet?

Sudheerkumar commented 4 years ago

Hi @CoreyCole , we are able to connect when not in the VPN, we get failure when we move to VPN/ enterprise networks. we havetls-listeningport = 443 and all the certs added, Opened the ports on the machine on which coturn docker image is running. Any inputs @CoreyCole

tsiory commented 4 years ago

Hi @Sudheerkumar have you found a solution to test this docker image with Trickle ICE? If so, can you tell me how you managed to do it? Thanks!

Sudheerkumar commented 4 years ago

Hi,

We have hosted the docker image on an Ubuntu server. Used TURN REST api principals to authorise and just used those in the trickle ICE

turns::port

On Tue, 8 Sep 2020 at 17:18, Tsiory notifications@github.com wrote:

Hi @Sudheerkumar https://github.com/Sudheerkumar have you found a solution to test this docker image with Trickle ICE? If so, can you tell me how you managed to do it? Thanks!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/instrumentisto/coturn-docker-image/issues/15#issuecomment-688815448, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAPQ46LHHZGYEXU66Y4IGGDSEYK2JANCNFSM4JS6PPJQ .

--

Cheers,

Sudheer

tsiory commented 4 years ago

Hi @Sudheerkumar Thanks for your response. But, I ran the docker image on my local machine with this command: docker run -d --network=host --name coturn instrumentisto/coturn and it ran successfully but now I don't know how to test it with Trickle ICE ...

Can I just use my public IP Address ? If so what port I need to test in Trickle ICE?

Thanks!