Statistics
| Branch: | Revision:

janus-gateway / conf / janus.cfg.sample.in @ 1d31e31f

History | View | Annotate | Download (8.3 KB)

1
; General configuration: folders where the configuration and the plugins
2
; can be found, how output should be logged, whether Janus should run as
3
; a daemon or in foreground, default interface to use, debug/logging level
4
; and, if needed, shared apisecret and/or token authentication mechanism
5
; between application(s) and Janus.
6
[general]
7
configs_folder = @confdir@		; Configuration files folder
8
plugins_folder = @plugindir@		; Plugins folder
9
transports_folder = @transportdir@	; Transports folder
10
;log_to_stdout = false			; Whether the Janus output should be written
11
								; to stdout or not (default=true)
12
;log_to_file = /tmp/janus.log	; Whether to use a log file or not
13
;daemonize = true				; Whether Janus should run as a daemon
14
								; or not (default=run in foreground)
15
;pid_file = /tmp/janus.pid		; PID file to create when Janus has been
16
								; started, and to destroy at shutdown
17
;interface = 1.2.3.4		; Interface to use (will be used in SDP)
18
debug_level = 4				; Debug/logging level, valid values are 0-7
19
;debug_timestamps = yes		; Whether to show a timestamp for each log line
20
;debug_colors = no			; Whether colors should be disabled in the log
21
;api_secret = janusrocks		; String that all Janus requests must contain
22
;							to be accepted/authorized by the Janus core.
23
;							Useful if you're wrapping all Janus API requests
24
;							in your servers (that is, not in the browser,
25
;							where you do the things your way) and you
26
;							don't want other application to mess with
27
;							this Janus instance.
28
;token_auth = yes			; Enable a token based authentication
29
;							mechanism to force users to always provide
30
;							a valid token in all requests. Useful if
31
;							you want to authenticate requests from web
32
;							users. For this to work, the Admin API MUST
33
;							be enabled, as tokens are added and removed
34
;							through messages sent there.
35
admin_secret = janusoverlord	; String that all Janus requests must contain
36
;								  to be accepted/authorized by the admin/monitor.
37
;								  only needed if you enabled the admin API
38
;								  in any of the available transports.
39
;server_name = MyJanusInstance	; Public name of this Janus instance
40
;								  as it will appear in an info request
41

    
42

    
43
; Certificate and key to use for DTLS.
44
[certificates]
45
cert_pem = @certdir@/mycert.pem
46
cert_key = @certdir@/mycert.key
47

    
48

    
49
; Media-related stuff: you can configure whether if you want
50
; to enable IPv6 support (still WIP, so handle with care), the maximum size
51
; of the NACK queue for retransmissions per handle the range of ports to
52
; use for RTP and RTCP (by default, no range is envisaged), the
53
; starting MTU for DTLS (1472 by default, it adapts automatically),
54
; if BUNDLE should be forced (defaults to false) and if RTCP muxing should
55
; be forced (defaults to false).
56
[media]
57
;ipv6 = true
58
;max_nack_queue = 300
59
;rtp_port_range = 20000-40000
60
;dtls_mtu = 1200
61
;force-bundle = true
62
;force-rtcp-mux = true
63

    
64

    
65
; NAT-related stuff: specifically, you can configure the STUN/TURN
66
; servers to use to gather candidates if the gateway is behind a NAT,
67
; and srflx/relay candidates are needed. In case STUN is not enough and
68
; this is needed (it shouldn't), you can also configure Janus to use a
69
; TURN server; please notice that this does NOT refer to TURN usage in
70
; browsers, but in the gathering of relay candidates by Janus itself,
71
; e.g., if you want to limit the ports used by a Janus instance on a
72
; private machine. Furthermore, you can choose whether Janus should be
73
; configured to work in ICE-Lite mode (by default it doesn't). Finally,
74
; you can also enable ICE-TCP support (beware that it currently *only*
75
; works if you enable ICE Lite as well), choose which interfaces should
76
; be used for gathering candidates, and enable or disable the
77
; internal libnice debugging, if needed. 
78
[nat]
79
;stun_server = stun.voip.eutelia.it
80
;stun_port = 3478
81
nice_debug = false
82
;ice_lite = true
83
;ice_tcp = true
84

    
85
; In case you're deploying Janus on a server which is configured with
86
; a 1:1 NAT (e.g., Amazon EC2), you might want to also specify the public
87
; address of the machine using the setting below. This will result in
88
; all host candidates (which normally have a private IP address) to
89
; be rewritten with the public address provided in the settings. As
90
; such, use the option with caution and only if you know what you're doing.
91
; Besides, it's still recommended to also enable STUN in those cases,
92
; and keep ICE Lite disabled as it's not strictly speaking a public server.
93
;nat_1_1_mapping = 1.2.3.4
94

    
95
; You can configure a TURN server in two different ways: specifying a
96
; statically configured TURN server, and thus provide the address of the
97
; TURN server, the transport (udp/tcp/tls) to use, and a set of valid
98
; credentials to authenticate...
99
;turn_server = myturnserver.com
100
;turn_port = 3478
101
;turn_type = udp
102
;turn_user = myuser
103
;turn_pwd = mypassword
104

    
105
; ... or you can make use of the TURN REST API to get info on one or more
106
; TURN services dynamically. This makes use of the proposed standard of
107
; such an API (https://tools.ietf.org/html/draft-uberti-behave-turn-rest-00)
108
; which is currently available in both rfc5766-turn-server and coturn.
109
; You enable this by specifying the address of your TURN REST API backend,
110
; the HTTP method to use (GET or POST) and, if required, the API key Janus
111
; must provide.
112
;turn_rest_api = http://yourbackend.com/path/to/api
113
;turn_rest_api_key = anyapikeyyoumayhaveset
114
;turn_rest_api_method = GET
115

    
116
; You can also choose which interfaces should be explicitly used by the
117
; gateway for the purpose of ICE candidates gathering, thus excluding
118
; others that may be available. To do so, use the 'ice_enforce_list'
119
; setting and pass it a comma-separated list of interfaces or IP addresses
120
; to enforce. This is especially useful if the server hosting the gateway
121
; has several interfaces, and you only want a subset to be used. Any of
122
; the following examples are valid:
123
;     ice_enforce_list = eth0
124
;     ice_enforce_list = eth0,eth1
125
;     ice_enforce_list = eth0,192.168.
126
;     ice_enforce_list = eth0,192.168.0.1
127
; By default, no interface is enforced, meaning Janus will try to use them all.
128
;ice_enforce_list = eth0
129

    
130
; In case you don't want to specify specific interfaces to use, but would
131
; rather tell Janus to use all the available interfaces except some that
132
; you don't want to involve, you can also choose which interfaces or IP
133
; addresses should be excluded and ignored by the gateway for the purpose
134
; of ICE candidates gathering. To do so, use the 'ice_ignore_list' setting
135
; and pass it a comma-separated list of interfaces or IP addresses to
136
; ignore. This is especially useful if the server hosting the gateway
137
; has several interfaces you already know will not be used or will simply
138
; always slow down ICE (e.g., virtual interfaces created by VMware).
139
; Partial strings are supported, which means that any of the following
140
; examples are valid:
141
;     ice_ignore_list = vmnet8,192.168.0.1,10.0.0.1
142
;     ice_ignore_list = vmnet,192.168.
143
; Just beware that the ICE ignore list is not used if an enforce list
144
; has been configured. By default, Janus ignores all interfaces whose
145
; name starts with 'vmnet', to skip VMware interfaces:
146
ice_ignore_list = vmnet
147

    
148
; You can choose which of the available plugins should be
149
; enabled or not. Use the 'disable' directive to prevent Janus from
150
; loading one or more plugins: use a comma separated list of plugin file
151
; names to identify the plugins to disable. By default all available
152
; plugins are enabled and loaded at startup.
153
[plugins]
154
; disable = libjanus_voicemail.so,libjanus_recordplay.so
155

    
156
; You can choose which of the available transports should be enabled or
157
; not. Use the 'disable' directive to prevent Janus from loading one
158
; or more transport: use a comma separated list of transport file names
159
; to identify the transports to disable. By default all available
160
; transports are enabled and loaded at startup.
161
[transports]
162
; disable = libjanus_rabbitmq.so
163

    
164
; You can choose which of the available event handlers should be loaded or
165
; not. Use the 'disable' directive to prevent Janus from loading one
166
; or more event handlers: use a comma separated list of file names
167
; to identify the event handlers to disable. By default all available
168
; event handlers are enabled and loaded at startup. If you want to
169
; completely disable the broadcasting of events to any event handler,
170
; set broadcast to no.
171
[events]
172
; broadcast = no
173
; disable = libjanus_sampleevh.so