TURN Error: user <>: incoming packet ALLOCATE processed, error 437

[Sourabh Das]

Hi All,

We are trying to setup a demo project on AWS which can be used for peer-to-peer WebRTC video calls (using EasyRTC).

The setup seems to run fine with our organization's wireless network but fails with some mobile data carriers.

We are receiving the following error in the turn server log file:

user <>: incoming packet ALLOCATE processed, error 437

We are using the TURN AWS package from and configuration instructions from:

https://storage.googleapis.com/google-code-archive-downloads/v2/code.google.com/rfc5766-turn-server/turnserver-3.2.2.1-debian-wheezy-ubuntu-mint-x86-64bits.tar.gz

http://blog.knoldus.com/2013/10/24/configure-turn-server-for-webrtc-on-amazon-ec2/

None of us here is a server expert and we don't have any infrastructure team to support us on this. But we managed to meet the dependencies for installing the turn server deb package and it is binding to the ports it does.

Further, we are using this command to start the turn server in testing mode:

turnserver -syslog -a -L A.A.A.A -X B.B.B.B -E A.A.A.A -f -min-port=32355 -max-port=65355 -user='qwerty':'qwerty' -r mycompany.org -log-file=stdout -v

where, A.A.A.A is the internal IP of the AWS instance and B.B.B.B is the public IP of our AWS instance.

Without authentication or not, we are getting the above error in our log file and even when connecting through wireless network in our organization (when the call gets successfully connected), the same error is present in the logs.

On the client end, we get EasyRTC error message as 'undefined' at the initiator side and 'No usable TURN/STUN path found' at the receiver's side.

Can someone provide insight about this and if possible guide us to some setup guide for TURN?

Thanks a lot in advance!