Matrix server automated install
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

turnserver.conf 27KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750
  1. # Coturn TURN SERVER configuration file
  2. #
  3. # Boolean values note: where a boolean value is supposed to be used,
  4. # you can use '0', 'off', 'no', 'false', or 'f' as 'false,
  5. # and you can use '1', 'on', 'yes', 'true', or 't' as 'true'
  6. # If the value is missing, then it means 'true' by default.
  7. #
  8. # Listener interface device (optional, Linux only).
  9. # NOT RECOMMENDED.
  10. #
  11. #listening-device=eth0
  12. # TURN listener port for UDP and TCP (Default: 3478).
  13. # Note: actually, TLS & DTLS sessions can connect to the
  14. # "plain" TCP & UDP port(s), too - if allowed by configuration.
  15. #
  16. listening-port=3478
  17. # TURN listener port for TLS (Default: 5349).
  18. # Note: actually, "plain" TCP & UDP sessions can connect to the TLS & DTLS
  19. # port(s), too - if allowed by configuration. The TURN server
  20. # "automatically" recognizes the type of traffic. Actually, two listening
  21. # endpoints (the "plain" one and the "tls" one) are equivalent in terms of
  22. # functionality; but Coturn keeps both endpoints to satisfy the RFC 5766 specs.
  23. # For secure TCP connections, Coturn currently supports
  24. # TLS version 1.0, 1.1 and 1.2.
  25. # For secure UDP connections, Coturn supports DTLS version 1.
  26. #
  27. tls-listening-port=5443
  28. # Alternative listening port for UDP and TCP listeners;
  29. # default (or zero) value means "listening port plus one".
  30. # This is needed for RFC 5780 support
  31. # (STUN extension specs, NAT behavior discovery). The TURN Server
  32. # supports RFC 5780 only if it is started with more than one
  33. # listening IP address of the same family (IPv4 or IPv6).
  34. # RFC 5780 is supported only by UDP protocol, other protocols
  35. # are listening to that endpoint only for "symmetry".
  36. #
  37. #alt-listening-port=0
  38. # Alternative listening port for TLS and DTLS protocols.
  39. # Default (or zero) value means "TLS listening port plus one".
  40. #
  41. #alt-tls-listening-port=0
  42. # Some network setups will require using a TCP reverse proxy in front
  43. # of the STUN server. If the proxy port option is set a single listener
  44. # is started on the given port that accepts connections using the
  45. # haproxy proxy protocol v2.
  46. # (https://www.haproxy.org/download/1.8/doc/proxy-protocol.txt)
  47. #
  48. #tcp-proxy-port=5555
  49. # Listener IP address of relay server. Multiple listeners can be specified.
  50. # If no IP(s) specified in the config file or in the command line options,
  51. # then all IPv4 and IPv6 system IPs will be used for listening.
  52. #
  53. listening-ip=0.0.0.0
  54. #listening-ip=10.207.21.238
  55. #listening-ip=2607:f0d0:1002:51::4
  56. # Auxiliary STUN/TURN server listening endpoint.
  57. # Aux servers have almost full TURN and STUN functionality.
  58. # The (minor) limitations are:
  59. #
  60. # 1) Auxiliary servers do not have alternative ports and
  61. # they do not support STUN RFC 5780 functionality (CHANGE REQUEST).
  62. #
  63. # 2) Auxiliary servers also are never returning ALTERNATIVE-SERVER reply.
  64. #
  65. # Valid formats are 1.2.3.4:5555 for IPv4 and [1:2::3:4]:5555 for IPv6.
  66. #
  67. # There may be multiple aux-server options, each will be used for listening
  68. # to client requests.
  69. #
  70. #aux-server=172.17.19.110:33478
  71. #aux-server=[2607:f0d0:1002:51::4]:33478
  72. # (recommended for older Linuxes only)
  73. # Automatically balance UDP traffic over auxiliary servers (if configured).
  74. # The load balancing is using the ALTERNATE-SERVER mechanism.
  75. # The TURN client must support 300 ALTERNATE-SERVER response for this
  76. # functionality.
  77. #
  78. #udp-self-balance
  79. # Relay interface device for relay sockets (optional, Linux only).
  80. # NOT RECOMMENDED.
  81. #
  82. #relay-device=eth1
  83. # Relay address (the local IP address that will be used to relay the
  84. # packets to the peer).
  85. # Multiple relay addresses may be used.
  86. # The same IP(s) can be used as both listening IP(s) and relay IP(s).
  87. #
  88. # If no relay IP(s) specified, then the turnserver will apply the default
  89. # policy: it will decide itself which relay addresses to be used, and it
  90. # will always be using the client socket IP address as the relay IP address
  91. # of the TURN session (if the requested relay address family is the same
  92. # as the family of the client socket).
  93. #
  94. #relay-ip=172.17.19.105
  95. #relay-ip=2607:f0d0:1002:51::5
  96. # For Amazon EC2 users:
  97. #
  98. # TURN Server public/private address mapping, if the server is behind NAT.
  99. # In that situation, if a -X is used in form "-X <ip>" then that ip will be reported
  100. # as relay IP address of all allocations. This scenario works only in a simple case
  101. # when one single relay address is be used, and no RFC5780 functionality is required.
  102. # That single relay address must be mapped by NAT to the 'external' IP.
  103. # The "external-ip" value, if not empty, is returned in XOR-RELAYED-ADDRESS field.
  104. # For that 'external' IP, NAT must forward ports directly (relayed port 12345
  105. # must be always mapped to the same 'external' port 12345).
  106. #
  107. # In more complex case when more than one IP address is involved,
  108. # that option must be used several times, each entry must
  109. # have form "-X <public-ip/private-ip>", to map all involved addresses.
  110. # RFC5780 NAT discovery STUN functionality will work correctly,
  111. # if the addresses are mapped properly, even when the TURN server itself
  112. # is behind A NAT.
  113. #
  114. # By default, this value is empty, and no address mapping is used.
  115. #
  116. external-ip=EXTERNAL_IP
  117. #
  118. #OR:
  119. #
  120. #external-ip=60.70.80.91/172.17.19.101
  121. #external-ip=60.70.80.92/172.17.19.102
  122. # Number of the relay threads to handle the established connections
  123. # (in addition to authentication thread and the listener thread).
  124. # If explicitly set to 0 then application runs relay process in a
  125. # single thread, in the same thread with the listener process
  126. # (the authentication thread will still be a separate thread).
  127. #
  128. # If this parameter is not set, then the default OS-dependent
  129. # thread pattern algorithm will be employed. Usually the default
  130. # algorithm is optimal, so you have to change this option
  131. # if you want to make some fine tweaks.
  132. #
  133. # In the older systems (Linux kernel before 3.9),
  134. # the number of UDP threads is always one thread per network listening
  135. # endpoint - including the auxiliary endpoints - unless 0 (zero) or
  136. # 1 (one) value is set.
  137. #
  138. #relay-threads=0
  139. # Lower and upper bounds of the UDP relay endpoints:
  140. # (default values are 49152 and 65535)
  141. #
  142. min-port=49152
  143. max-port=65535
  144. # Uncomment to run TURN server in 'normal' 'moderate' verbose mode.
  145. # By default the verbose mode is off.
  146. verbose
  147. # Uncomment to run TURN server in 'extra' verbose mode.
  148. # This mode is very annoying and produces lots of output.
  149. # Not recommended under normal circumstances.
  150. #
  151. #Verbose
  152. # Uncomment to use fingerprints in the TURN messages.
  153. # By default the fingerprints are off.
  154. #
  155. fingerprint
  156. # Uncomment to use long-term credential mechanism.
  157. # By default no credentials mechanism is used (any user allowed).
  158. #
  159. lt-cred-mech
  160. # This option is the opposite of lt-cred-mech.
  161. # (TURN Server with no-auth option allows anonymous access).
  162. # If neither option is defined, and no users are defined,
  163. # then no-auth is default. If at least one user is defined,
  164. # in this file, in command line or in usersdb file, then
  165. # lt-cred-mech is default.
  166. #
  167. #no-auth
  168. # Enable prometheus exporter
  169. # If enabled the turnserver will expose an endpoint with stats on a prometheus format
  170. # this endpoint is listening on a different port to not conflict with other configurations.
  171. #
  172. # You can simply run the turnserver and access the port 9641 and path /metrics
  173. #
  174. # For mor info on the prometheus exporter and metrics
  175. # https://prometheus.io/docs/introduction/overview/
  176. # https://prometheus.io/docs/concepts/data_model/
  177. #
  178. #prometheus
  179. # TURN REST API flag.
  180. # (Time Limited Long Term Credential)
  181. # Flag that sets a special authorization option that is based upon authentication secret.
  182. #
  183. # This feature's purpose is to support "TURN Server REST API", see
  184. # "TURN REST API" link in the project's page
  185. # https://github.com/coturn/coturn/
  186. #
  187. # This option is used with timestamp:
  188. #
  189. # usercombo -> "timestamp:userid"
  190. # turn user -> usercombo
  191. # turn password -> base64(hmac(secret key, usercombo))
  192. #
  193. # This allows TURN credentials to be accounted for a specific user id.
  194. # If you don't have a suitable id, then the timestamp alone can be used.
  195. # This option is enabled by turning on secret-based authentication.
  196. # The actual value of the secret is defined either by the option static-auth-secret,
  197. # or can be found in the turn_secret table in the database (see below).
  198. #
  199. # Read more about it:
  200. # - https://tools.ietf.org/html/draft-uberti-behave-turn-rest-00
  201. # - https://www.ietf.org/proceedings/87/slides/slides-87-behave-10.pdf
  202. #
  203. # Be aware that use-auth-secret overrides some parts of lt-cred-mech.
  204. # The use-auth-secret feature depends internally on lt-cred-mech, so if you set
  205. # this option then it automatically enables lt-cred-mech internally
  206. # as if you had enabled both.
  207. #
  208. # Note that you can use only one auth mechanism at the same time! This is because,
  209. # both mechanisms conduct username and password validation in different ways.
  210. #
  211. # Use either lt-cred-mech or use-auth-secret in the conf
  212. # to avoid any confusion.
  213. #
  214. #use-auth-secret
  215. # 'Static' authentication secret value (a string) for TURN REST API only.
  216. # If not set, then the turn server
  217. # will try to use the 'dynamic' value in the turn_secret table
  218. # in the user database (if present). The database-stored value can be changed on-the-fly
  219. # by a separate program, so this is why that mode is considered 'dynamic'.
  220. #
  221. static-auth-secret=STATIC_SECRET
  222. # Server name used for
  223. # the oAuth authentication purposes.
  224. # The default value is the realm name.
  225. #
  226. server-name=DOMAIN
  227. # Flag that allows oAuth authentication.
  228. #
  229. #oauth
  230. # 'Static' user accounts for the long term credentials mechanism, only.
  231. # This option cannot be used with TURN REST API.
  232. # 'Static' user accounts are NOT dynamically checked by the turnserver process,
  233. # so they can NOT be changed while the turnserver is running.
  234. #
  235. user=turn:TURN_PWD
  236. #user=username2:key2
  237. # OR:
  238. #user=username1:password1
  239. #user=username2:password2
  240. #
  241. # Keys must be generated by turnadmin utility. The key value depends
  242. # on user name, realm, and password:
  243. #
  244. # Example:
  245. # $ turnadmin -k -u ninefingers -r north.gov -p youhavetoberealistic
  246. # Output: 0xbc807ee29df3c9ffa736523fb2c4e8ee
  247. # ('0x' in the beginning of the key is what differentiates the key from
  248. # password. If it has 0x then it is a key, otherwise it is a password).
  249. #
  250. # The corresponding user account entry in the config file will be:
  251. #
  252. #user=ninefingers:0xbc807ee29df3c9ffa736523fb2c4e8ee
  253. # Or, equivalently, with open clear password (less secure):
  254. #user=ninefingers:youhavetoberealistic
  255. #
  256. # SQLite database file name.
  257. #
  258. # The default file name is /var/db/turndb or /usr/local/var/db/turndb or
  259. # /var/lib/turn/turndb.
  260. #
  261. #userdb=/var/db/turndb
  262. # PostgreSQL database connection string in the case that you are using PostgreSQL
  263. # as the user database.
  264. # This database can be used for the long-term credential mechanism
  265. # and it can store the secret value for secret-based timed authentication in TURN REST API.
  266. # See http://www.postgresql.org/docs/8.4/static/libpq-connect.html for 8.x PostgreSQL
  267. # versions connection string format, see
  268. # http://www.postgresql.org/docs/9.2/static/libpq-connect.html#LIBPQ-CONNSTRING
  269. # for 9.x and newer connection string formats.
  270. #
  271. #psql-userdb="host=<host> dbname=<database-name> user=<database-user> password=<database-user-password> connect_timeout=30"
  272. # MySQL database connection string in the case that you are using MySQL
  273. # as the user database.
  274. # This database can be used for the long-term credential mechanism
  275. # and it can store the secret value for secret-based timed authentication in TURN REST API.
  276. #
  277. # Optional connection string parameters for the secure communications (SSL):
  278. # ca, capath, cert, key, cipher
  279. # (see http://dev.mysql.com/doc/refman/5.1/en/ssl-options.html for the
  280. # command options description).
  281. #
  282. # Use the string format below (space separated parameters, all optional):
  283. #
  284. #mysql-userdb="host=<host> dbname=<database-name> user=<database-user> password=<database-user-password> port=<port> connect_timeout=<seconds> read_timeout=<seconds>"
  285. # If you want to use an encrypted password in the MySQL connection string,
  286. # then set the MySQL password encryption secret key file with this option.
  287. #
  288. # Warning: If this option is set, then the mysql password must be set in "mysql-userdb" in an encrypted format!
  289. # If you want to use a cleartext password then do not set this option!
  290. #
  291. # This is the file path for the aes encrypted secret key used for password encryption.
  292. #
  293. #secret-key-file=/path/
  294. # MongoDB database connection string in the case that you are using MongoDB
  295. # as the user database.
  296. # This database can be used for long-term credential mechanism
  297. # and it can store the secret value for secret-based timed authentication in TURN REST API.
  298. # Use the string format described at http://hergert.me/docs/mongo-c-driver/mongoc_uri.html
  299. #
  300. #mongo-userdb="mongodb://[username:password@]host1[:port1][,host2[:port2],...[,hostN[:portN]]][/[database][?options]]"
  301. # Redis database connection string in the case that you are using Redis
  302. # as the user database.
  303. # This database can be used for long-term credential mechanism
  304. # and it can store the secret value for secret-based timed authentication in TURN REST API.
  305. # Use the string format below (space separated parameters, all optional):
  306. #
  307. #redis-userdb="ip=<ip-address> dbname=<database-number> password=<database-user-password> port=<port> connect_timeout=<seconds>"
  308. # Redis status and statistics database connection string, if used (default - empty, no Redis stats DB used).
  309. # This database keeps allocations status information, and it can be also used for publishing
  310. # and delivering traffic and allocation event notifications.
  311. # The connection string has the same parameters as redis-userdb connection string.
  312. # Use the string format below (space separated parameters, all optional):
  313. #
  314. #redis-statsdb="ip=<ip-address> dbname=<database-number> password=<database-user-password> port=<port> connect_timeout=<seconds>"
  315. # The default realm to be used for the users when no explicit
  316. # origin/realm relationship is found in the database, or if the TURN
  317. # server is not using any database (just the commands-line settings
  318. # and the userdb file). Must be used with long-term credentials
  319. # mechanism or with TURN REST API.
  320. #
  321. # Note: If the default realm is not specified, then realm falls back to the host domain name.
  322. # If the domain name string is empty, or set to '(None)', then it is initialized as an empty string.
  323. #
  324. realm=DOMAIN
  325. # This flag sets the origin consistency
  326. # check. Across the session, all requests must have the same
  327. # main ORIGIN attribute value (if the ORIGIN was
  328. # initially used by the session).
  329. #
  330. #check-origin-consistency
  331. # Per-user allocation quota.
  332. # default value is 0 (no quota, unlimited number of sessions per user).
  333. # This option can also be set through the database, for a particular realm.
  334. #
  335. #user-quota=0
  336. # Total allocation quota.
  337. # default value is 0 (no quota).
  338. # This option can also be set through the database, for a particular realm.
  339. #
  340. #total-quota=0
  341. # Max bytes-per-second bandwidth a TURN session is allowed to handle
  342. # (input and output network streams are treated separately). Anything above
  343. # that limit will be dropped or temporarily suppressed (within
  344. # the available buffer limits).
  345. # This option can also be set through the database, for a particular realm.
  346. #
  347. #max-bps=0
  348. #
  349. # Maximum server capacity.
  350. # Total bytes-per-second bandwidth the TURN server is allowed to allocate
  351. # for the sessions, combined (input and output network streams are treated separately).
  352. #
  353. # bps-capacity=0
  354. # Uncomment if no UDP client listener is desired.
  355. # By default UDP client listener is always started.
  356. #
  357. #no-udp
  358. # Uncomment if no TCP client listener is desired.
  359. # By default TCP client listener is always started.
  360. #
  361. no-tcp
  362. # Uncomment if no TLS client listener is desired.
  363. # By default TLS client listener is always started.
  364. #
  365. #no-tls
  366. # Uncomment if no DTLS client listener is desired.
  367. # By default DTLS client listener is always started.
  368. #
  369. #no-dtls
  370. # Uncomment if no UDP relay endpoints are allowed.
  371. # By default UDP relay endpoints are enabled (like in RFC 5766).
  372. #
  373. #no-udp-relay
  374. # Uncomment if no TCP relay endpoints are allowed.
  375. # By default TCP relay endpoints are enabled (like in RFC 6062).
  376. #
  377. #no-tcp-relay
  378. # Uncomment if extra security is desired,
  379. # with nonce value having a limited lifetime.
  380. # The nonce value is unique for a session.
  381. # Set this option to limit the nonce lifetime.
  382. # Set it to 0 for unlimited lifetime.
  383. # It defaults to 600 secs (10 min) if no value is provided. After that delay,
  384. # the client will get 438 error and will have to re-authenticate itself.
  385. #
  386. #stale-nonce=600
  387. # Uncomment if you want to set the maximum allocation
  388. # time before it has to be refreshed.
  389. # Default is 3600s.
  390. #
  391. #max-allocate-lifetime=3600
  392. # Uncomment to set the lifetime for the channel.
  393. # Default value is 600 secs (10 minutes).
  394. # This value MUST not be changed for production purposes.
  395. #
  396. #channel-lifetime=600
  397. # Uncomment to set the permission lifetime.
  398. # Default to 300 secs (5 minutes).
  399. # In production this value MUST not be changed,
  400. # however it can be useful for test purposes.
  401. #
  402. #permission-lifetime=300
  403. # Certificate file.
  404. # Use an absolute path or path relative to the
  405. # configuration file.
  406. # Use PEM file format.
  407. #
  408. cert=/etc/letsencrypt/live/DOMAIN/fullchain.pem
  409. # Private key file.
  410. # Use an absolute path or path relative to the
  411. # configuration file.
  412. # Use PEM file format.
  413. #
  414. pkey=/etc/letsencrypt/live/DOMAIN/privkey.pem
  415. # Private key file password, if it is in encoded format.
  416. # This option has no default value.
  417. #
  418. #pkey-pwd=...
  419. # Allowed OpenSSL cipher list for TLS/DTLS connections.
  420. # Default value is "DEFAULT".
  421. #
  422. #cipher-list="DEFAULT"
  423. # CA file in OpenSSL format.
  424. # Forces TURN server to verify the client SSL certificates.
  425. # By default this is not set: there is no default value and the client
  426. # certificate is not checked.
  427. #
  428. # Example:
  429. #CA-file=/etc/ssh/id_rsa.cert
  430. # Curve name for EC ciphers, if supported by OpenSSL
  431. # library (TLS and DTLS). The default value is prime256v1,
  432. # if pre-OpenSSL 1.0.2 is used. With OpenSSL 1.0.2+,
  433. # an optimal curve will be automatically calculated, if not defined
  434. # by this option.
  435. #
  436. #ec-curve-name=prime256v1
  437. # Use 566 bits predefined DH TLS key. Default size of the key is 2066.
  438. #
  439. #dh566
  440. # Use 1066 bits predefined DH TLS key. Default size of the key is 2066.
  441. #
  442. #dh1066
  443. # Use custom DH TLS key, stored in PEM format in the file.
  444. # Flags --dh566 and --dh2066 are ignored when the DH key is taken from a file.
  445. #
  446. #dh-file=<DH-PEM-file-name>
  447. # Flag to prevent stdout log messages.
  448. # By default, all log messages go to both stdout and to
  449. # the configured log file. With this option everything will
  450. # go to the configured log only (unless the log file itself is stdout).
  451. #
  452. #no-stdout-log
  453. # Option to set the log file name.
  454. # By default, the turnserver tries to open a log file in
  455. # /var/log, /var/tmp, /tmp and the current directory
  456. # (Whichever file open operation succeeds first will be used).
  457. # With this option you can set the definite log file name.
  458. # The special names are "stdout" and "-" - they will force everything
  459. # to the stdout. Also, the "syslog" name will force everything to
  460. # the system log (syslog).
  461. # In the runtime, the logfile can be reset with the SIGHUP signal
  462. # to the turnserver process.
  463. #
  464. log-file=/var/tmp/turnserver.log
  465. # Option to redirect all log output into system log (syslog).
  466. #
  467. syslog
  468. # This flag means that no log file rollover will be used, and the log file
  469. # name will be constructed as-is, without PID and date appendage.
  470. # This option can be used, for example, together with the logrotate tool.
  471. #
  472. #simple-log
  473. # Enable full ISO-8601 timestamp in all logs.
  474. #new-log-timestamp
  475. # Set timestamp format (in strftime(1) format)
  476. #new-log-timestamp-format "%FT%T%z"
  477. # Disabled by default binding logging in verbose log mode to avoid DoS attacks.
  478. # Enable binding logging and UDP endpoint logs in verbose log mode.
  479. #log-binding
  480. # Option to set the "redirection" mode. The value of this option
  481. # will be the address of the alternate server for UDP & TCP service in the form of
  482. # <ip>[:<port>]. The server will send this value in the attribute
  483. # ALTERNATE-SERVER, with error 300, on ALLOCATE request, to the client.
  484. # Client will receive only values with the same address family
  485. # as the client network endpoint address family.
  486. # See RFC 5389 and RFC 5766 for the description of ALTERNATE-SERVER functionality.
  487. # The client must use the obtained value for subsequent TURN communications.
  488. # If more than one --alternate-server option is provided, then the functionality
  489. # can be more accurately described as "load-balancing" than a mere "redirection".
  490. # If the port number is omitted, then the default port
  491. # number 3478 for the UDP/TCP protocols will be used.
  492. # Colon (:) characters in IPv6 addresses may conflict with the syntax of
  493. # the option. To alleviate this conflict, literal IPv6 addresses are enclosed
  494. # in square brackets in such resource identifiers, for example:
  495. # [2001:db8:85a3:8d3:1319:8a2e:370:7348]:3478 .
  496. # Multiple alternate servers can be set. They will be used in the
  497. # round-robin manner. All servers in the pool are considered of equal weight and
  498. # the load will be distributed equally. For example, if you have 4 alternate servers,
  499. # then each server will receive 25% of ALLOCATE requests. A alternate TURN server
  500. # address can be used more than one time with the alternate-server option, so this
  501. # can emulate "weighting" of the servers.
  502. #
  503. # Examples:
  504. #alternate-server=1.2.3.4:5678
  505. #alternate-server=11.22.33.44:56789
  506. #alternate-server=5.6.7.8
  507. #alternate-server=[2001:db8:85a3:8d3:1319:8a2e:370:7348]:3478
  508. # Option to set alternative server for TLS & DTLS services in form of
  509. # <ip>:<port>. If the port number is omitted, then the default port
  510. # number 5349 for the TLS/DTLS protocols will be used. See the previous
  511. # option for the functionality description.
  512. #
  513. # Examples:
  514. #tls-alternate-server=1.2.3.4:5678
  515. #tls-alternate-server=11.22.33.44:56789
  516. #tls-alternate-server=[2001:db8:85a3:8d3:1319:8a2e:370:7348]:3478
  517. # Option to suppress TURN functionality, only STUN requests will be processed.
  518. # Run as STUN server only, all TURN requests will be ignored.
  519. # By default, this option is NOT set.
  520. #
  521. #stun-only
  522. # Option to hide software version. Enhance security when used in production.
  523. # Revealing the specific software version of the agent through the
  524. # SOFTWARE attribute might allow them to become more vulnerable to
  525. # attacks against software that is known to contain security holes.
  526. # Implementers SHOULD make usage of the SOFTWARE attribute a
  527. # configurable option (https://tools.ietf.org/html/rfc5389#section-16.1.2)
  528. #
  529. #no-software-attribute
  530. # Option to suppress STUN functionality, only TURN requests will be processed.
  531. # Run as TURN server only, all STUN requests will be ignored.
  532. # By default, this option is NOT set.
  533. #
  534. #no-stun
  535. # This is the timestamp/username separator symbol (character) in TURN REST API.
  536. # The default value is ':'.
  537. # rest-api-separator=:
  538. # Flag that can be used to allow peers on the loopback addresses (127.x.x.x and ::1).
  539. # This is an extra security measure.
  540. #
  541. # (To avoid any security issue that allowing loopback access may raise,
  542. # the no-loopback-peers option is replaced by allow-loopback-peers.)
  543. #
  544. # Allow it only for testing in a development environment!
  545. # In production it adds a possible security vulnerability, so for security reasons
  546. # it is not allowed using it together with empty cli-password.
  547. #
  548. #allow-loopback-peers
  549. # Flag that can be used to disallow peers on well-known broadcast addresses (224.0.0.0 and above, and FFXX:*).
  550. # This is an extra security measure.
  551. #
  552. #no-multicast-peers
  553. # Option to set the max time, in seconds, allowed for full allocation establishment.
  554. # Default is 60 seconds.
  555. #
  556. #max-allocate-timeout=60
  557. # Option to allow or ban specific ip addresses or ranges of ip addresses.
  558. # If an ip address is specified as both allowed and denied, then the ip address is
  559. # considered to be allowed. This is useful when you wish to ban a range of ip
  560. # addresses, except for a few specific ips within that range.
  561. #
  562. # This can be used when you do not want users of the turn server to be able to access
  563. # machines reachable by the turn server, but would otherwise be unreachable from the
  564. # internet (e.g. when the turn server is sitting behind a NAT)
  565. #
  566. # Examples:
  567. # denied-peer-ip=83.166.64.0-83.166.95.255
  568. # allowed-peer-ip=83.166.68.45
  569. # File name to store the pid of the process.
  570. # Default is /var/run/turnserver.pid (if superuser account is used) or
  571. # /var/tmp/turnserver.pid .
  572. #
  573. #pidfile="/var/run/turnserver.pid"
  574. # Require authentication of the STUN Binding request.
  575. # By default, the clients are allowed anonymous access to the STUN Binding functionality.
  576. #
  577. #secure-stun
  578. # Mobility with ICE (MICE) specs support.
  579. #
  580. #mobility
  581. # Allocate Address Family according
  582. # If enabled then TURN server allocates address family according the TURN
  583. # Client <=> Server communication address family.
  584. # (By default Coturn works according RFC 6156.)
  585. # !!Warning: Enabling this option breaks RFC6156 section-4.2 (violates use default IPv4)!!
  586. #
  587. #keep-address-family
  588. # User name to run the process. After the initialization, the turnserver process
  589. # will attempt to change the current user ID to that user.
  590. #
  591. #proc-user=<user-name>
  592. # Group name to run the process. After the initialization, the turnserver process
  593. # will attempt to change the current group ID to that group.
  594. #
  595. #proc-group=<group-name>
  596. # Turn OFF the CLI support.
  597. # By default it is always ON.
  598. # See also options cli-ip and cli-port.
  599. #
  600. #no-cli
  601. #Local system IP address to be used for CLI server endpoint. Default value
  602. # is 127.0.0.1.
  603. #
  604. #cli-ip=127.0.0.1
  605. # CLI server port. Default is 5766.
  606. #
  607. #cli-port=5766
  608. # CLI access password. Default is empty (no password).
  609. # For the security reasons, it is recommended that you use the encrypted
  610. # form of the password (see the -P command in the turnadmin utility).
  611. #
  612. # Secure form for password 'qwerty':
  613. #
  614. #cli-password=$5$79a316b350311570$81df9cfb9af7f5e5a76eada31e7097b663a0670f99a3c07ded3f1c8e59c5658a
  615. #
  616. # Or unsecure form for the same password:
  617. #
  618. #cli-password=qwerty
  619. # Enable Web-admin support on https. By default it is Disabled.
  620. # If it is enabled it also enables a http a simple static banner page
  621. # with a small reminder that the admin page is available only on https.
  622. #
  623. #web-admin
  624. # Local system IP address to be used for Web-admin server endpoint. Default value is 127.0.0.1.
  625. #
  626. #web-admin-ip=127.0.0.1
  627. # Web-admin server port. Default is 8080.
  628. #
  629. #web-admin-port=8080
  630. # Web-admin server listen on STUN/TURN worker threads
  631. # By default it is disabled for security resons! (Not recommended in any production environment!)
  632. #
  633. #web-admin-listen-on-workers
  634. #acme-redirect=http://redirectserver/.well-known/acme-challenge/
  635. # Redirect ACME, i.e. HTTP GET requests matching '^/.well-known/acme-challenge/(.*)' to '<URL>$1'.
  636. # Default is '', i.e. no special handling for such requests.
  637. # Server relay. NON-STANDARD AND DANGEROUS OPTION.
  638. # Only for those applications when you want to run
  639. # server applications on the relay endpoints.
  640. # This option eliminates the IP permissions check on
  641. # the packets incoming to the relay endpoints.
  642. #
  643. #server-relay
  644. # Maximum number of output sessions in ps CLI command.
  645. # This value can be changed on-the-fly in CLI. The default value is 256.
  646. #
  647. #cli-max-output-sessions
  648. # Set network engine type for the process (for internal purposes).
  649. #
  650. #ne=[1|2|3]
  651. # Do not allow an TLS/DTLS version of protocol
  652. #
  653. no-tlsv1
  654. no-tlsv1_1