Questions[coturn](server)

We are using coTurn server to allow our SIP appliance work reliably between client apps and teleconferences. During our test's we have found that one type of calls is not working at all. But at first let me explain test scenarios:

Client A - IPv6 (priority) + IPv4 Client B, D - IPv4 only Client C - IPv6 + IPv4 (priority)

1. Call from A to C - everything ok
2. Call from C to A - everything ok
3. Call from A to B or D - no sound transmitted in both ways
4. Call from B or D to A - everything ok

We understand this results as if call is propagated from IPv6 network the answering site has to be accessible via IPv6 to make successful call but when call is propagated from IPv4 network it does not matter which IP address family is on the aswering call (IPv6 or IPv4)

Listening IP and Relaying IP of CoTurn is set to autodiscovery. We have tested also allocation-default-address-family="keep" but this didn't changed anything in test results.

We use ABTO VoIP SDK for dot.Net and iOS but I do not see if this will be important matter in this case. CoTurn version is 4.5.1.1

Did anyone had similar issue with mixed IPv6/IPv4 networks? How can we resolve this issue?

Thanks in advance for help.

I am trying to add a Nginx UDP LoadBalancer in front of CoTURN.

• Installed ejabberd in a VM
• Installed nginx in a VM
• Installed coturn in a VM

Nginx config:

log_format    basic    '$remote_addr [$time_local] '
                       '$protocol $status $bytes_sent $bytes_received '
                       '$session_time';

# Enable access_log statements for debugging

access_log /var/log/nginx/stream.log basic buffer=32k;

upstream stream_cluster {
#    hash $remote_addr consistent;
    least_conn;
    server 30.40.50.60:3478;
    server 30.40.50.61:3478;
}

server {
    listen 3478 udp reuseport;
    listen 3478;
    #All UDP/TCP traffic will be forwarded to the cluster
    proxy_buffer_size 4096k;
    proxy_responses 0;
    proxy_bind $remote_addr transparent;
    proxy_protocol on;
    proxy_pass stream_cluster;
    allow all;
#    error_log /var/log/nginx/stream.log;
}

coturn is working nicely when directly used along with ejabberd. All required ports are open in the Security Policy. But nginx is not passing the data to the upstream. I have followed the official nginx documentation.

Not sure what I am doing wrong.

I am using React Native WebRTC to develop p2p calling application. It works everywhere except UAE and maybe Middle East.

I am using my own TURN server with port 4211 also tried TURN server with port 443 as mentioned in this answer. But that never works when I call to UAE from other countries. On the other hand incoming calls from UAE to other countries works on few network.

I'm trying to get (as a Docker stack) Matrix Synapse (matrixdotorg/synapse) together with Coturn (coturn/coturn) to work. Matrix is fully working with TLS certs. Also the coturn server works with disabled TLS without any problems. But when I enable TLS then it fails completely.

In the Matrix' homeserver.yaml the following TURN settings are in place:

turn_uris: [ "turns:turn.example.com?transport=udp", "turns:turn.example.com?transport=tcp", "turn:turn.example.com?transport=udp", "turn:turn.example.com?transport=tcp" ]
turn_shared_secret: "secretstuff"
turn_user_lifetime: 1h
turn_allow_guests: true

Tis is the full turnserver.conf file:

listening-port=3478
# tls-listening-port=5349
listening-ip=172.16.1.2
relay-ip=172.16.1.2
external-ip=1.2.3.4
min-port=49152
max-port=65535
verbose
use-auth-secret
static-auth-secret=secretstuff
realm=turn.example.com
user-quota=12
total-quota=1200
no-tcp-relay
stale-nonce=600
cert=/etc/certs/fullchain.pem
pkey=/etc/certs/privkey.pem
no-software-attribute
no-multicast-peers
denied-peer-ip=10.0.0.0-10.255.255.255
denied-peer-ip=172.16.0.0-172.31.255.255
denied-peer-ip=192.168.0.0-192.168.255.255
allowed-peer-ip=172.16.1.2
pidfile="/var/tmp/turnserver.pid"
no-cli
no-tlsv1
no-tlsv1_1

If I disable the TLS listener (commented out line) then everything works perfectly fine. But as soon as I enable the TLS listener no connection is possible (call button creates a call and it rings on the other side but when I pick up it just says "connecting" and stays in that state. In the logs I don't get any useful hint. The TLS certificates on the TURN server are for "turn.example.com" - the realm name of the server.

I have already tried everything I found online - in GitHub and in tutorials. But nothing worked.

As end devices Android smartphones with the Element App are used.

I have coturn running on a server and it runs as usual systemd process as user root.

Can someone tell me how I could make coturn run as user coturn ?

p.s. could someone modify the Tags and add coturn , turn and sturn because I need 300 reputation for this, and I have only 225-