CoTURN on Amazon EC2 didn't response

[Jeffrey]

Hi,

I installed coturn "turnserver-4.5.0.6" on Amazon EC2 (CentOS 6.8), and I added some inbound rules in security group on aws ec2.

 

Then, I used Trickle ICE (https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/) to test STUN and TURN.

The result i got as follow:There are no srflx and relay candidates in the ICE candidate list. 

So I use Wireshark on EC2(private ip=172.31.2.100) to capture Binding Request packets:

We can see that port 3478 have received Binding Requests from Trickle ICE, but co-turn server didn't response anything.

And there is my turnserver.conf:

external-ip= PUBLIC_IP_on_EC2

user=test:test1

realm=domain.org

Can you please help me what could be wrong?

[shakeeb]

Hi Jeffrey,

As you can see the incoming packets in the tshark or wireshark, your EC2's firewall rule should be ok.

To response STUN binding request, co-turn server needs no configuration at all. Just need to ensure that server is running on desired port. 

`netstat -nap | grep 3478`  command will show co-turn's process name if it is already listening on that port.

If you find that con-turn is listening on desired port then the issue may be related to local firewall settings.

`iptables -F` will clear firewall rules then you can test again.

It is good to test using some test client ( like test client provided with co-turn or libnice ) running on the same instance first then using trickle ICE 

If first works but not the second then the issue is related to firewall settings of EC2.

If all these don't work then you may be running the corrupt or wrong binary. (  probability is very low. )   Try to install from latest stable source code on latest OS.

Thanks,

Shakeeb         

[Jeffrey]

I clear local firewall rules as your suggestion, and it works!

Thank your for all your help.

shakeeb於 2017年7月15日星期六 UTC+8上午10時32分25秒寫道：