Turn Server Configuration, video/voice is not relayed

113 views

Skip to first unread message

Sadia Javed

unread,

Jul 11, 2018, 3:19:32 AM7/11/18

to TURN Server (Open-Source project)

Hi All

I am testing relay on turn server but it is not showing video/voice. I am attaching the server logs and a video call logging (on server) between 2 peers. Does any one knows what is the issue, what i am missing?

Note: I changed public ip with 1.2.3.4 in logs

Following are the server logs:

0: log file opened: /var/log/turn_2615_2018-07-11.log

RFC 3489/5389/5766/5780/6062/6156 STUN/TURN Server

Version Coturn-4.5.0.6 'dan Eider'

Max number of open files/sockets allowed for this process: 1048576

Due to the open files/sockets limitation,

max supported number of TURN Sessions possible is: 524000 (approximately)

==== Show him the instruments, Practical Frost: ====

0: TLS is not supported

0: DTLS supported

0: DTLS 1.2 supported

0: TURN/STUN ALPN supported

0: Third-party authorization (oAuth) supported

0: GCM (AEAD) supported

0: OpenSSL compile-time version: OpenSSL 1.1.0g 2 Nov 2017 (0x1010007f)

0: SQLite is not supported

0: Redis is not supported

0: PostgreSQL is not supported

0: MySQL is not supported

0: MongoDB is not supported

0: Default Net Engine version: 3 (UDP thread per CPU core)

=====================================================

0: Config file found: /root/../etc/turnserver.conf

0: Listener address to use: 192.168.1.34

0: Relay address to use: 192.168.1.34

0: Config file found: /root/../etc/turnserver.conf

0: Domain name:

0: Default realm: company.org

0: DTLS1.2: Certificate file found: /etc/ssl/certificate.pem

0: DTLS1.2: Private key file found: /etc/ssl/privatekey.pem

0: DTLS: Certificate file found: /etc/ssl/certificate.pem

0: DTLS: Private key file found: /etc/ssl/privatekey.pem

0: DTLS cipher suite: DEFAULT

0: pid file created: /var/run/turnserver.pid

0: IO method (main listener thread): epoll (with changelist)

0: WARNING: I cannot support STUN CHANGE_REQUEST functionality because only one IP address is provided

0: Wait for relay ports initialization...

0: relay 192.168.1.34 initialization...

0: relay 192.168.1.34 initialization done

0: Relay ports initialization done

0: IO method (general relay thread): epoll (with changelist)

0: turn server id=0 created

0: IPv4. SCTP listener opened on : 192.168.1.34:3478

0: IPv4. TCP listener opened on : 192.168.1.34:3478

0: IO method (general relay thread): epoll (with changelist)

0: turn server id=1 created

0: IPv4. TCP listener opened on : 192.168.1.34:3478

0: IO method (general relay thread): epoll (with changelist)

0: turn server id=2 created

0: IPv4. TCP listener opened on : 192.168.1.34:3478

0: IO method (general relay thread): epoll (with changelist)

0: turn server id=3 created

0: IPv4. DTLS/UDP listener opened on: 192.168.1.34:3478

0: IPv4. TCP listener opened on : 192.168.1.34:3478

0: IPv4. DTLS/UDP listener opened on: 192.168.1.34:5349

0: Total General servers: 4

0: IO method (auth thread): epoll (with changelist)

0: IO method (admin thread): epoll (with changelist)

0: IPv4. CLI listener opened on : 127.0.0.1:5766

Logs when a call is placed it is receiving packets but not showing video on either end.

188: handle_udp_packet: New UDP endpoint: local addr 192.168.1.34:3478, remote addr 1.2.3.4:27966

188: session 000000000000000002: realm <company.org> user <>: incoming packet BINDING processed, success

188: session 000000000000000002: realm <company.org> user <>: incoming packet message processed, error 401: Unauthorized

188: IPv4. tcp or tls connected to: 1.2.3.4:21126

188: session 003000000000000001: realm <company.org> user <>: incoming packet message processed, error 401: Unauthorized

188: IPv4. Local relay addr: 192.168.1.34:58923

188: session 000000000000000002: new, realm=<company.org>, username=<demo>, lifetime=600

188: session 000000000000000002: realm <company.org> user <demo>: incoming packet ALLOCATE processed, success

188: IPv4. Local relay addr: 192.168.1.34:59933

188: session 003000000000000001: new, realm=<company.org>, username=<demo>, lifetime=600

188: session 003000000000000001: realm <company.org> user <demo>: incoming packet ALLOCATE processed, success

198: session 000000000000000002: realm <company.org> user <demo>: incoming packet BINDING processed, success

208: session 000000000000000002: realm <company.org> user <demo>: incoming packet BINDING processed, success

218: session 000000000000000002: realm <company.org> user <demo>: incoming packet BINDING processed, success

229: session 000000000000000002: realm <company.org> user <demo>: incoming packet BINDING processed, success

Reply all

Reply to author

Forward

0 new messages