panjinya / coturn Goto Github PK

The server operation may become erratic when the clients are using native SCTP 
connections. That is especially true for the FreeBSD server platform.

What steps will reproduce the problem?
1. install turnserver v4.1.1.1 on CentOS 6.5
2. install kamailio-4.1.5
3. install imsdroid on android endpoint

What is the expected output? What do you see instead?
After several necessary configuration, turnserver work only in relay mode with 
two imsdroid UAs

What version of the product are you using? On what operating system?
turnserver v4.1.1.1 on CentOS 6.5
kamailio-4.1.5
imsdroid v2.569.1089

Please provide any additional information below.

Coturn and Turnserver cannot be installed side by side.

Currently both projects share a few similar files which means they cannot be 
installed side by side. So far I can see that /etc/init.d/rfc5766-turn-server 
is the same, I propose to change this to: /etc/init.d/coturn

Secondly the config files, (userdb.conf & turnserver.conf) these should be 
changed to be coturn specific to prevent conflicts.

When I set a DSCP tag (by using googDscp constraint : true when setting up a 
peer connection), packets from client to TURN server are marked.

Differentiated Services Field: 0x88 (DSCP 0x22: Assured Forwarding 41; (...)
1000 10 .. = Differentiated Services Codepoint: Assured Forwarding 41 (0x22)

DSCP in packets after going through the server are set back to zero:
Differentiated Services Field: 0x00 (DSCP 0x00: Default; (...)
0000 00 .. = Differentiated Services Codepoint: Default (0x00)

On linux preferred behaviour is used mleaning that the outgoing value is set to 
the incoming value. But given my tests, this value is set to zero.

I have checked it on coturn 4.3.1.2 (Ubuntu server 14.04) and on turn-5766 
3.2.2.4 (Ubuntu server 12.04).


What version of the product are you using? On what operating system?


Please provide any additional information below.

What steps will reproduce the problem?
1. Start a redis-server in localhost, as turn-server's user-statsdb:
./redis-server &

2. Start turn-server with statsdb enabled:
./turnserver -p 10001 -L 10.10.10.15 -a -f -v --no-cli -r localhost -O 
port=6379 

3. Kill or restart the redis-server started in "step 1":
kill

4. run top command, watch the cpu usage of turn-server:
top

What is the expected output? What do you see instead?
Expected output:
Turn server runs normally, and cpu usage is low.

Real output: 
The cpu usage is over 99% per thread:

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND                                                                                                                         
30877 xxxxxxxx  20   0  696m  18m 2424 R 99.4  0.5   0:22.79 turnserver         


30876 xxxxxxxx  20   0  696m  18m 2424 R 99.1  0.5   0:22.80 turnserver         


30878 xxxxxxxx  20   0  696m  18m 2424 R 99.1  0.5   0:22.72 turnserver 


What version of the product are you using? On what operating system?
Version: 
Version Coturn-4.4.5.1 'Ardee West'

Operating system:
Linux tmpserver 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 
x86_64 x86_64 x86_64 GNU/Linux

Please provide any additional information below.

When trying to set a mongodb uri in the turnserver.conf configuration I get the 
following error:
"Bad configuration format: mongo-userdb"

My configuration looks like this
mongo-userdb="mongodb://user:pass@host/db"

Any ideas on what the correct format should be? I checked out this page (side 
note the docs point to an invalid webpage, this is the correct):
http://hergert.me/docs/mongo-c-driver-docs-0.94.2/mongoc_uri.html

My configuration directive looks to be right! I can connect using the shell 
script for schema population.

In Ubuntu the firewall is managed by UFW. The rules can be manually added or an 
application configuration file can be added to simplify the process.

I've attached a file with the default ports to simplify firewall setup on 
Ubuntu.

To use run these commands
cp turnserver /etc/ufw/applications.d/turnserver
ufw add turnserver

This file should probably be automatically copied as part of the Ubuntu package 
install (not quite sure how to do this but it's a standard practise).

Hello currently i would like to use turnserver with peerjs. One think that 
bothers me is how to set users for turn.
I would like to store users in file turnuserdb.conf. My problem is when I use 
deafult user: ninefingers:youhavetoberealistic everything is fine(I can make 
video chat), but when I specify for example myuser:passw and then appy it  to 
the example 1) as: 

 var peer = new Peer({host: peerJsServerHost, port: peerJsServerPort, path: peerJsServerPath, debug:3, 
       config: {'iceServers': [
        {   url: 'turn:'+stunTurnServerHost+':3478',        credential: 'passw',        username: 'myuser'      },
        {   url: 'stun:'+stunTurnServerHost+':3478',        credential: 'passw',        username: 'myuser'      }
        ]}
    });  
there is no connection between those two peerjs. Can anybody give me hint or 
solution to this problem.
I'm starting turnserver with command:  turnserver -o -c 
/etc/turnserver/turnserver.conf -a 

1) https://github.com/peers/peerjs/blob/master/examples/videochat/index.html

Hi,

The attached patch allows the listening-ip and relay-ip configuration fields to 
contain a hostname, which is then resolved with getaddrinfo(). Tested under 
Linux and OSX.

Rationale:

In some environments (for example, Google Cloud Servers) the host gets a 
dynamic private IPv4 upon restart which may change at any time. Fortunately an 
alias for the private IP is automatically added into /etc/hosts. For some 
reasons one may need to make Coturn to just listen into the private address and 
avoid IP autodiscovery. The patch makes this scenario easier to live with.

What steps will reproduce the problem?
1. Setup coturn in AWS Amazon instances, lt-cred-mech, use-auth-secret, 
static-auth-secret=Veureka123, without database, just generic username 
(timestamp:userx), credential base64(hmac(Veureka123, username)).
2. Use SimpleWebRTC in client side.
3. Create crdentials like:

self.webrtc.config.peerConnectionConfig.iceServers = [{"url" : 
"stun:myStunIP:3478"},
            { 
            "url" : "turn:myTurnIP:3478?transport=udp",
            "username": username,
            "credential":hashEncoded
            }];

What is the expected output? What do you see instead?

In Firefox it works fine, but in Chrome it isn't.


What version of the product are you using? On what operating system?
I test coTurn 4.2.3.1, 4.0.0.0 and 4.1.1.1, all fails.


Is there any reason of structure in ice servers config?? I tried use adapterjs 
but simplewebrtc don't supports it.

Regards,

What steps will reproduce the problem?

The call flow is : 

SIP PHONE APP (with ICE) ==> ASTERISK (with ICE) 


What is the expected output? What do you see instead?

ICE failed : I receiveid the following error : 
Received invalid STUN packet from 176.182.63.143:7076: MESSAGE_INTEGRITY 
attribute missing

176.182.63.143 is the IP address from SIP PHONE APP. 

What version of the product are you using? On what operating system?

Androïd and iOS Linphone APP. 


Please provide any additional information below.

May be, coturn provide a parameter to disable control message integrity ?




Regards.

AfriCallShop

I currently have a database with some collection names that follow a 
convention. I want to share this DB with Turnserver but unfortunately a couple 
of the collection names used are the same.

I would like the option in the conf file to set the string collection name used 
for each function.

e.g. in the config we would have the following

mongodb-collection-allowed-peer-ip="allowed_peer_ip"
mongodb-collection-denied-peer-ip="denied_peer_ip"
mongodb-collection-realms="realms"
mongodb-collection-turn-secret="turn_secret"
mongodb-collection-turnusers-lt="turnusers_lt"
mongodb-collection-turnusers-st="turnusers-st"

What steps will reproduce the problem?
1. run this command to start turn server, "10.0.0.12" is turn server's local ip 
address:
./turnserver -E 10.0.0.12 -E 127.0.0.1 -E 10.0.0.12
2. Watch command output, about "Relay address to use".


What is the expected output? What do you see instead?
Expected output:
... ...
0: Relay address to use: 10.0.0.12
0: Relay address to use: 127.0.0.1
... ...

Real output:
... ...
0: Relay address to use: 10.0.0.12
0: Relay address to use: 127.0.0.1
0: Relay address to use: 10.0.0.12
... ...


What version of the product are you using? On what operating system?
Version Coturn-4.4.5.1 'Ardee West'


Please provide any additional information below.
Patch file in attached.

What steps will reproduce the problem?
1. start coturn with default configuration
2. call turnutils_uclient -T -n 50 -l 10000 host
3.

What is the expected output? What do you see instead?
I see Total lost packets 100 (100.000000%)

What version of the product are you using? On what operating system?
Linux32, Version Coturn-4.2.1.2

Please provide any additional information below.