root/config.ini.sample

Revision 399, 9.4 kB (checked in by Dan Pascu <dan@ag-projects.com>, 6 weeks ago)

Added management_passport option to dispatcher

Line 
1
2[Relay]
3; A list of dispatchers to connect to, separated by spaces. The format is
4; "host[:port] [host[:port] ...]". If a port is not specified the default port
5; of 25060 will be used. "host" can be one of the following:
6;  - A domain name that has a SRV record for a SIP proxy, i.e. at
7;    "_sip._udp.<domain>". If the DNS lookup for this succeeds the relay
8;    will connect to the IP address of the SIP proxy on the port specified in
9;    this configuration.
10;  - A hostname. The lookup for this will be performed if the SRV lookup
11;    fails.
12;  - An IP address. The relay will connect directly to this address.
13;  Both the SRV and hostname lookups will be periodically refreshed (see
14;  "dns_check_interval" below).
15;
16;dispatchers = example.com 1.2.3.4:12345
17
18; Specify extra checks to be performed on the dispatcher TLS credentials before
19; considering the connection with the dispatcher succesful. The passport is
20; specified as a list of attribute/value pairs in the form:
21;   AN:value[, AN:value...]
22; where the attribute name (AN) is one of the available attribute names from
23; the X509 certificate subject: O, OU, CN, C, L, ST, EMAIL. The value is a
24; string that has to match with the corresponding attribute value from the
25; dispatcher certificate. A wildcard (*) can be used in the value at the
26; beginning or the end of the string to indicate that the corresponding
27; attribute from the dispatcher certificate must end with respectively to
28; start with the given string (excluding the wildcard).
29; For example using this passport:
30;   passport = O:AG Projects, CN:*dispatcher
31; means that a connection with a dispatcher will only be accepted if the
32; dispatcher certificate subject has organization set to "AG Projects" and
33; the common name ends with "dispatcher". To specify that no additional
34; identity checks need to be performed, use the keyword None. If passport
35; is None, then only the certificate signature is verified agains the
36; certificate authority in tls/ca.pem (signature is always verified even
37; when passport is None).
38;
39; Default value is None.
40;
41;passport = None
42
43; The host IP address used for relaying streams. The default for this value
44; is to use the IP address of the interface that has the default route. This
45; is the most appropriate choice for almost any situation. Unless you need to
46; use a very specific interface, which is not the default one, there is no need
47; to set this option. Leave this option commented to use the default value.
48;relay_ip = <default host IP>
49
50; The port range to use for relaying media streams in the form start:end with
51; start and end being even numbers in the [1024, 65536] range and start < end
52; The default range is 50000:60000. You should allocate 4 times the number of
53; streams you plan for the relay to handle simultaneously. The default range
54; having 10000 ports, is able to handle up to 2500 streams.
55;
56;port_range = 50000:60000
57
58; The amount of time to wait for a stream in a new SDP offer to start sending
59; data before the relay decides that it has timed out. The default value is 90
60; seconds. This only applies to the initial setup stage, before the first
61; packet for a stream is received (from both ends). After the stream is started
62; and the conntrack rule is in place, the idle timeout (how long before the
63; conntrack rule expires when no traffic is received) is controlled by a kernel
64; setting that defaults to 180 seconds and can be adjusted in:
65;     /proc/sys/net/ipv4/netfilter/ip_conntrack_udp_timeout_stream
66;
67;stream_timeout = 90
68
69; Amount of time a call can be on hold before it is declared expired by the
70; relay. The default value is 7200 seconds (2 hours).
71;
72;on_hold_timeout = 7200
73
74; How often to check in DNS if the SRV and A records for the dispatcher have
75; changed. Interval is in seconds and the default value is 60 seconds.
76;
77;dns_check_interval = 60
78
79; If the relay cannot connect to a dispatcher is should retry after this
80; amount of seconds. The default value is 10 seconds.
81;
82;reconnect_delay = 10
83
84; How often to sample the aggregate ammount of data processed by the relay, in
85; order to compute an average of the relayed traffic over that period. The
86; value is expressed in seconds and the default value is 15 seconds.
87; Use 0 to disable it in case you have to many streams processed by the relay
88; and it warns you in syslog that gathering this information takes too long.
89;
90;traffic_sampling_period = 15
91
92
93[Dispatcher]
94; Local socket on which to communicate with OpenSIPS. The OpenSIPS mediaproxy
95; module should be configured to connect to this socket. If a relative path,
96; /var/run/mediaproxy will be prepended. Default value is dispatcher.sock.
97;
98;socket_path = dispatcher.sock
99
100; Listen address for incoming connections from the relays. The format is
101; "ip[:port]". If the ip is "0.0.0.0" or the keyword "any", the dispatcher
102; will listen on all interfaces of this host. If the port is not specified,
103; the dispatcher will listen on the default port of 25060.
104;
105;listen = 0.0.0.0
106
107; Listen address for incoming management interface connections. Clients can
108; connect to this and issue commands to query the status of the relays and
109; their sessions. The format is "ip[:port]". If the ip is "0.0.0.0" or the
110; keyword "any", the dispatcher will listen on all interfaces of this host.
111; If the port is not specified, the dispatcher will listen on the default
112; port of 25061.
113;
114;listen_management = 0.0.0.0
115
116; Whether or not to use TLS on the management interface. Note that the same
117; TLS credentials are used for both the relay and the management interface
118; connections.
119;
120; Default value is yes.
121;
122;management_use_tls = yes
123
124; Specify extra checks to be performed on the relay TLS credentials before
125; considering the connection with the relay succesful. The passport is
126; specified as a list of attribute/value pairs in the form:
127;   AN:value[, AN:value...]
128; where the attribute name (AN) is one of the available attribute names from
129; the X509 certificate subject: O, OU, CN, C, L, ST, EMAIL. The value is a
130; string that has to match with the corresponding attribute value from the
131; relay certificate. A wildcard (*) can be used in the value at the beginning
132; or the end of the string to indicate that the corresponding attribute from
133; the relay certificate must end with respectively to start with the given
134; string (excluding the wildcard).
135; For example using this passport:
136;   passport = O:AG Projects, CN:relay*
137; means that a connection with a relay will only be accepted if the relay
138; certificate subject has organization set to "AG Projects" and the common
139; name starts with "relay". To specify that no additional identity checks
140; need to be performed, use the keyword None. If passport is None, then only
141; the certificate signature is verified agains the certificate authority in
142; tls/ca.pem (signature is always verified even when passport is None).
143;
144; Default value is None.
145;
146;passport = None
147
148; This option is similar to passport above, but applies to the management
149; interface connections instead of relay connections. It specifies extra
150; checks to be performed on the TLS credentials suplied by an entity that
151; connects to the management interface. Please consult passport above for
152; a detailed description of the possible values for this option.
153;
154; If management_use_tls is false, this option is ignored.
155;
156; Default value is None.
157;
158;management_passport = None
159
160; Timeout value in second for individual relays. When a command is sent from
161; the dispatcher to a relay it will wait this amount of seconds for a reply.
162; The default is 5 seconds.
163;
164;relay_timeout = 5
165
166; A comma separated list of accounting backends that will be used to save
167; accounting data with the session information once a session has finished.
168; Currently 2 backends are available: "radius" and "database". If enabled
169; they can be configured below in their respective sections. The default
170; is to use no accounting backend.
171;
172;accounting =
173
174[TLS]
175; Path to the certificates. If relative, it will be looked up in both the
176; application directory (for a standalone installation) and /etc/mediaproxy,
177; the former taking precedence if found.
178;
179;certs_path = tls
180
181; How often (in seconds) to verify the peer certificate for expiration and
182; revocation. Default value is 300 seconds (5 minutes)
183;
184;verify_interval = 300
185
186
187[Database]
188; This section needs to be configured if database accounting is enabled
189
190; Database URI in the form: scheme://user:password@host/database
191;dburi = mysql://mediaproxy:CHANGEME@localhost/mediaproxy
192
193; Name for the table.
194;sessions_table = media_sessions
195
196; Column names. Columns are strings except for info which is a BLOB
197;
198;callid_column = call_id
199;fromtag_column = from_tag
200;totag_column = to_tag
201;info_column = info
202
203[Radius]
204; This section needs to be configured if radius accounting is enabled
205
206; OpenSIPS RADIUS configuration file. All RADIUS cofiguration parameters will
207; be read from this file, including dictionary files.
208;
209;config_file = /etc/opensips/radius/client.conf
210
211; Additional dictionary file with MediaProxy specific attributes.
212;additional_dictionary = radius/dictionary
213
214[OpenSIPS]
215; Configure interaction between the media dispatcher and OpenSIPS
216
217; Path to OpenSIPS' UNIX filesystem socket from the mi_datagram module.
218;socket_path = '/var/run/opensips/socket'
219
220; Maximum number of connections to open with OpenSIPS' mi_datagram socket.
221; Please note that connections will be opened on a need basis depending on
222; load, but never more than the number configured below.
223;
224;max_connections = 10
Note: See TracBrowser for help on using the browser.