Nextcloud talk problem

ℹ️ Support 💬 Talk (spreed)
1

Hi everyone. In installed nextcloud 19 from source code. everything is ok and work. but my problem is nextcloud talk. I followed nextcloud manual . I installed coturn and follow all rules. but my problem is we can call others no voice and video transferred.

my coturn version : 4.5.0.7-1ubuntu2.18.04.1

STUN servers : office.xxxxxx.xxx:443
TURN servers : office.xxxxx.x.xxx:3478

turnserver.conf

listening-ip=office.xxxxxx.xxxx
relay-ip=office.xxxxx.xxxxxx

fingerprint
lt-cred-mech
use-auth-secret
static-auth-secret=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
realm=office.xxxxxxxxxx.xxx
total-quota=100
bps-capacity=0
stale-nonce=600
log-file=/var/tmp/turn/turn.log
simple-log
no-loopback-peers
no-multicast-peers

2

hi ehsan,

Did you check by default configuration of using Talk service as I want to know that before configure of Turnserver ? I am facing same problem. Its worked on same Lan but over public network its not working on my case. My configuration as same like you. Is there anybody to help us. :frowning:

3

Hi. I installed nextcloud on the public cloud.

4

I found this eeror in turn.log file

: incoming packet message processed, error 401: Unauthorized
53: IPv4. Local relay addr

5

–listening-ip <ip> Listener IP address of relay server. Multiple listeners can be specified. If no IP (s) specified, then all IPv4 and IPv6 system IPs will be used for listening.

sure that a fqdn is working here?

6

yes I’m sure about it

7

Are users coming from behind firewalls? NAT?
If the latter, start with just the built-in STUN server (i.e. disable coturn server)

Are attendees using mobiles or computers?

EDIT:
Are both servers - NC and coturn - on the same subnet?
IP addresses - public or private?
If public - are they SSLed?

8

Hi. I installed nextcloud on the public cloud . users can have a valid IP address or sit behind NAT . Nextcloud and coturn both on the same server , and have a valid IP address .
I used lets encrypt.

9

the fields are called IP for a reason.
You need to set it to the IP address of the turn server. A FQDN will not help.

10

Hi. I Changed But I’ve same problem .

11

Hi. do you still have a problem ?

13

hi Ehsan,

There was issue on my coturn server configuration. Which is resolved now.
Choose the listening port, e.g. 3478 ( default for non-TLS ) Coturn config as below:

listening-port=3478
fingerprint
lt-cred-mech
use-auth-secret
static-auth-secret= <yourChosen/GeneratedSecret>
realm= your.domain.org
total-quota=100
bps-capacity=0
stale-nonce
no-loopback-peers # Only on coTURN below v4.5.1.0!
no-multicast-peers
#The following settings can be used to adjust the logging behavior.
no-stdout-log
log-file=…
syslog
simple-log

I’m not issue the below two line because It only for specific IP
#listening-ip=office.xxxxxx.xxxx
#relay-ip=office.xxxxx.xxxxxx

14

Hi .thx for your respond . I solved my problem . I changed nextclould talk 9 to 8 and it work .

15

Use: external-ip=your.external.ip in your turnserver.conf
listening-ip I use the internal ip in our network, for external Ip is for wan.
Works for my centos7 and coturn and nextcloud19 talk 9