-
```
What steps will reproduce the problem?
1. Establish a TURN allocation, authenticate with long-ter credentials, and
install a permission.
2. Send data to the relay address from the permission addr…
-
```
What steps will reproduce the problem?
I deployed turnserver in one of my machine(192.168.11.53). When I tried with
the buildin tool
turnutils_stunclient 192.168.11.53
I can get the response…
-
```
What steps will reproduce the problem?
1.Currently testing with Counterpath X-Lite Vers. 3.0 build 56125
2.
3.
What is the expected output? What do you see instead?
Is there a way to configure th…
-
```
According to RFC 5389, STUN Transaction IDs SHOULD be cryptographically random;
RFC 5766 similarly says that nonces SHOULD be cryptographically random, and
cites RFC 4086.
However, rfc5766-turn…
-
```
Red Hat Enterprise Linux 6.4 / 64- bit i installed the server package.
Install:
$ cd /var/tmp;
wget
https://github.com/downloads/libevent/libevent/libevent-2.0.21-stable.tar.gz;
tar xvfz libev…
-
```
According to RFC 5389, STUN Transaction IDs SHOULD be cryptographically random;
RFC 5766 similarly says that nonces SHOULD be cryptographically random, and
cites RFC 4086.
However, rfc5766-turn…
-
```
If the server receives an allocate request for a super-session that hasn't
previously sent a nonce, it always returns 401, even if the request contains a
message-integrity attribute.
Following …
-
```
According to RFC 5389, STUN Transaction IDs SHOULD be cryptographically random;
RFC 5766 similarly says that nonces SHOULD be cryptographically random, and
cites RFC 4086.
However, rfc5766-turn…
-
```
What steps will reproduce the problem?
1.Currently testing with Counterpath X-Lite Vers. 3.0 build 56125
2.
3.
What is the expected output? What do you see instead?
Is there a way to configure th…
-
```
What steps will reproduce the problem?
I deployed turnserver in one of my machine(192.168.11.53). When I tried with
the buildin tool
turnutils_stunclient 192.168.11.53
I can get the response…