Using the `stun' client utility from the `stun' package in Debian, I
notice that turnserver doesn't respond at all, it just logs the following:
22:08:42.576473 [turnserver.c:4506] Received UDP on listening address
22:08:42.576580 [turnserver.c:3231] Bad magic cookie
22:08:42.576607 [turnserver.c:4528] Bad STUN/TURN message or permission
I also test from ice4j (using test/Ice.java), specifically, I modify
Ice.java to only add one harvester:
new TransportAddress("22.214.171.124", 3478, Transport.UDP)));
and I delete all the other harvester setup code for TURN and STUN.
Using just the StunCandidateHarvester, the Ice.java test seems to work
22:17:57.900456 [turnserver.c:4506] Received UDP on listening address
22:17:57.900530 [turnserver.c:3580] OK basic validation are done,
process the TURN message
22:17:57.900545 [turnserver.c:2941] Process a TURN message
22:17:57.900557 [turnserver.c:1144] Binding request received!
Why does it say `Process a TURN message' when only using
By comparison, if I use reTurnServer from reSIProcate, it is able to
pass the tests with ice4j, but it also accepts the STUN packets from the
Is this a sign of some bug, or is turnserver deliberately not compatible
with older STUN clients?