asterisk/meetme.conf@a6cd892638c1
asterisk/meetme.conf
Sat, 03 Oct 2009 16:18:52 +0200
- author
- Michael Schloh von Bennewitz <michael@schloh.com>
- date
- Sat, 03 Oct 2009 16:18:52 +0200
- changeset 220
- a6cd892638c1
- permissions
- -rw-r--r--
Update version, adjust corresponding buildconf, and correct logic.
1: Make minor corrections and improvements to scripts patch logic.
2: Upgrade to most recent stable release version 3.0.2.
3: Force selection of a single db backend, as multiple ones never
were supported (changing 'with_db<end>' identifiers accordingly.)
4: Unfortunately add gawk requirement although only partly needed.
5: Add openssl::with_threads requirement to solve strange and hard
to debug problems on Solaris leading to connection failures:
'host-dir JobId 0: Error: openssl.c:86 Connect failure: ERR=error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number'
and
'host-dir JobId 40: Fatal error: TLS negotiation failed with FD at "back1.host.com:9102"'
1 ;
2 ; Configuration file for MeetMe simple conference rooms for Asterisk of course.
3 ;
4 ; This configuration file is read every time you call app meetme()
6 ;[general]
7 ;audiobuffers=32 ; The number of 20ms audio buffers to be used
8 ; when feeding audio frames from non-Zap channels
9 ; into the conference; larger numbers will allow
10 ; for the conference to 'de-jitter' audio that arrives
11 ; at different timing than the conference's timing
12 ; source, but can also allow for latency in hearing
13 ; the audio from the speaker. Minimum value is 2,
14 ; maximum value is 32.
15 ;
16 ;[rooms]
17 ;
18 ; Usage is conf => confno[,pin][,adminpin]
19 ;
20 ; Note that once a participant has called the conference, a change to the pin
21 ; number done in this file will not take effect until there are no more users
22 ; in the conference and it goes away. When it is created again, it will have
23 ; the new pin number.
24 ;
25 ;conf => 1234
26 ;conf => 2345,9938
