tony2001 / rfc5766-turn-server Goto Github PK

I didn't find the command to stop the server in the documentation. How do I do this?

i am using rfc-5766 turn server + jssip

in fedora 19

i am trying to connected

datacard ip :106.208.93.5

  to

private net ip:192.168.2.51

return-server:182.72.101.53

calls are received after attending only black screen on both side
here is my log.

also i need to know what are the ports i need to open.

turnserver -v
1392819495: RFC 3489/5389/5766/5780/6062/6156 STUN/TURN Server
1392819495: version Citrix-2.6.4.1 'Harding Grim'
1392819495: =====================================================
1392819495: Multithreading supported
1392819495: TLS supported
1392819495: DTLS supported
1392819495: Multithreaded relay supported
1392819495: Redis is not supported
1392819495: PostgreSQL supported
1392819495: MySQL supported
1392819495: OpenSSL multithreading supported
1392819495: OpenSSL version: fresh enough
1392819495: =====================================================
1392819495: Config file found: /usr/local/etc/turnserver.conf
1392819495: Config file found: /usr/local/etc/turnserver.conf
1392819495: Config file found: /usr/local/etc/turnuserdb.conf
1392819495:
CONFIGURATION ALERT: you specified long-term user accounts, (-u option)
but you did not specify the long-term credentials option
(-a or --lt-cred-mech option).
I am turning --lt-cred-mech ON for you, but double-check your configuration.
1392819495:
CONFIGURATION ALERT: you did specify the long-term credentials usage
but you did not specify the realm option (-r option).
The TURN Server will be inaccessible.
Check your configuration.
1392819495: WARNING: cannot find certificate file: turn_server_cert.pem (1)
1392819495: WARNING: cannot start TLS and DTLS listeners because certificate file is not set properly
1392819495: WARNING: cannot find private key file: turn_server_pkey.pem (1)
1392819495: WARNING: cannot start TLS and DTLS listeners because private key file is not set properly
1392819495: ===========Discovering listener addresses: =========
1392819495: Listener address to use: 127.0.0.1
1392819495: Listener address to use: 182.72.101.53
1392819495: Listener address to use: ::1
1392819495: =====================================================
1392819495: ===========Discovering relay addresses: =============
1392819495: Relay address to use: 182.72.101.53
1392819495: =====================================================
1392819495: pid file created: /var/run/turnserver.pid
1392819495: IO method (main listener thread): epoll
1392819495: IO method (udp listener/relay thread): epoll
1392819495: IO method (udp listener/relay thread): epoll
1392819495: IO method (udp listener/relay thread): epoll
1392819495: IO method (udp listener/relay thread): epoll
1392819495: IO method (udp listener/relay thread): epoll
1392819495: IO method (udp listener/relay thread): epoll
1392819495: IO method: epoll
1392819495: IPv4. UDP listener opened on : 127.0.0.1:3578
1392819495: IO method: epoll
1392819495: IPv4. UDP listener opened on : 127.0.0.1:3579
1392819495: IPv4. TCP listener opened on : 127.0.0.1:3578
1392819495: IPv4. TCP listener opened on : 127.0.0.1:3579
1392819495: IO method: epoll
1392819495: IPv4. UDP listener opened on : 182.72.101.53:3578
1392819495: IO method: epoll
1392819495: IPv4. UDP listener opened on : 182.72.101.53:3579
1392819495: IPv4. TCP listener opened on : 182.72.101.53:3578
1392819495: IPv4. TCP listener opened on : 182.72.101.53:3579
1392819495: IO method: epoll
1392819495: IPv6. UDP listener opened on : ::1:3578
1392819495: IO method: epoll
1392819495: IPv6. UDP listener opened on : ::1:3579
1392819495: IPv6. TCP listener opened on : ::1:3578
1392819495: IPv6. TCP listener opened on : ::1:3579
1392819495: IO method (auth thread): epoll
1392819495: IO method (nonudp relay thread): epoll
1392819495: IO method (nonudp relay thread): epoll
1392819637: handle_udp_packet: New UDP endpoint: local addr 182.72.101.53:3578, remote addr 192.168.2.51:1262
1392819637: handle_turn_command: user <>: message processed, error 401
1392819637: IPv4. Server relay addr: 182.72.101.53:0
1392819637: IPv4. Local relay addr: 182.72.101.53:45555
1392819637: new Allocation: id=0xecdc3c10, username=, lifetime=3600
1392819637: handle_turn_command: user : request ALLOCATE processed, error 0
1392819637: handle_udp_packet: New UDP endpoint: local addr 182.72.101.53:3578, remote addr 192.168.2.51:1263
1392819637: handle_turn_command: user <>: message processed, error 401
1392819637: IPv4. Server relay addr: 182.72.101.53:0
1392819637: IPv4. Local relay addr: 182.72.101.53:49327
1392819637: new Allocation: id=0xe77c4830, username=, lifetime=3600
1392819637: handle_turn_command: user : request ALLOCATE processed, error 0
1392819637: handle_udp_packet: New UDP endpoint: local addr 182.72.101.53:3578, remote addr 192.168.2.51:1264
1392819637: handle_turn_command: user <>: message processed, error 401
1392819637: IPv4. Server relay addr: 182.72.101.53:0
1392819637: IPv4. Local relay addr: 182.72.101.53:47400
1392819637: new Allocation: id=0xe7a1d380, username=, lifetime=3600
1392819637: handle_turn_command: user : request ALLOCATE processed, error 0
1392819637: handle_udp_packet: New UDP endpoint: local addr 182.72.101.53:3578, remote addr 192.168.2.51:1265
1392819637: handle_turn_command: user <>: message processed, error 401
1392819637: IPv4. Server relay addr: 182.72.101.53:0
1392819637: IPv4. Local relay addr: 182.72.101.53:45675
1392819637: new Allocation: id=0xe7c79f48, username=, lifetime=3600
1392819637: handle_turn_command: user : request ALLOCATE processed, error 0
1392819637: handle_udp_packet: New UDP endpoint: local addr 182.72.101.53:3578, remote addr 192.168.2.51:1266
1392819637: handle_turn_command: user <>: message processed, error 401
1392819637: IPv4. Server relay addr: 182.72.101.53:0
1392819637: IPv4. Local relay addr: 182.72.101.53:44057
1392819637: new Allocation: id=0xe6682ab8, username=, lifetime=3600
1392819637: handle_turn_command: user : request ALLOCATE processed, error 0
1392819637: handle_udp_packet: New UDP endpoint: local addr 182.72.101.53:3578, remote addr 192.168.2.51:1267
1392819637: handle_turn_command: user <>: message processed, error 401
1392819637: IPv4. Server relay addr: 182.72.101.53:0
1392819637: IPv4. Local relay addr: 182.72.101.53:47280
1392819637: new Allocation: id=0xe69235f8, username=, lifetime=3600
1392819637: handle_turn_command: user : request ALLOCATE processed, error 0
1392819642: handle_udp_packet: New UDP endpoint: local addr 182.72.101.53:3578, remote addr 106.208.93.5:9654
1392819642: handle_turn_command: user <>: message processed, error 401
1392819642: handle_udp_packet: New UDP endpoint: local addr 182.72.101.53:3578, remote addr 106.208.93.5:9655
1392819642: handle_turn_command: user <>: message processed, error 401
1392819642: handle_udp_packet: New UDP endpoint: local addr 182.72.101.53:3578, remote addr 106.208.93.5:9656
1392819642: handle_turn_command: user <>: message processed, error 401
1392819642: handle_udp_packet: New UDP endpoint: local addr 182.72.101.53:3578, remote addr 106.208.93.5:9657
1392819642: handle_turn_command: user <>: message processed, error 401
1392819642: handle_udp_packet: New UDP endpoint: local addr 182.72.101.53:3578, remote addr 106.208.93.5:9658
1392819642: handle_turn_command: user <>: message processed, error 401
1392819642: handle_udp_packet: New UDP endpoint: local addr 182.72.101.53:3578, remote addr 106.208.93.5:9659
1392819642: handle_turn_command: user <>: message processed, error 401
1392819642: handle_turn_command: user <>: message processed, error 401
1392819642: handle_turn_command: user <>: message processed, error 401
1392819642: handle_turn_command: user <>: message processed, error 401
1392819642: handle_turn_command: user <>: message processed, error 401
1392819642: IPv4. Server relay addr: 182.72.101.53:0
1392819642: IPv4. Local relay addr: 182.72.101.53:44106
1392819642: new Allocation: id=0xf9328190, username=, lifetime=3600
1392819642: handle_turn_command: user : request ALLOCATE processed, error 0
1392819642: IPv4. Server relay addr: 182.72.101.53:0
1392819642: IPv4. Local relay addr: 182.72.101.53:42127
1392819642: new Allocation: id=0xf9aad298, username=, lifetime=3600
1392819642: handle_turn_command: user : request ALLOCATE processed, error 0
1392819642: IPv4. Server relay addr: 182.72.101.53:0
1392819642: IPv4. Local relay addr: 182.72.101.53:47672
1392819642: new Allocation: id=0xf97189f0, username=, lifetime=3600
1392819642: handle_turn_command: user : request ALLOCATE processed, error 0
1392819642: handle_turn_command: user <>: message processed, error 401
1392819642: handle_turn_command: user <>: message processed, error 401
1392819642: IPv4. Server relay addr: 182.72.101.53:0
1392819642: IPv4. Local relay addr: 182.72.101.53:45919
1392819642: new Allocation: id=0xf9dcdc58, username=, lifetime=3600
1392819642: handle_turn_command: user : request ALLOCATE processed, error 0
1392819642: IPv4. Server relay addr: 182.72.101.53:0
1392819642: IPv4. Local relay addr: 182.72.101.53:49717
1392819642: new Allocation: id=0xf81be4b8, username=, lifetime=3600
1392819642: handle_turn_command: user : request ALLOCATE processed, error 0
1392819642: IPv4. Server relay addr: 182.72.101.53:0
1392819642: IPv4. Local relay addr: 182.72.101.53:42902
1392819642: new Allocation: id=0xf8552d60, username=, lifetime=3600
1392819642: handle_turn_command: user : request ALLOCATE processed, error 0
1392819642: handle_turn_command: user : request ALLOCATE processed, error 0
1392819642: handle_turn_command: user : request ALLOCATE processed, error 0
1392819642: handle_turn_command: user : request ALLOCATE processed, error 0