asterisk/meetme.conf@a6cd892638c1 (annotated)
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"'
| michael@202 | 1 | ; |
| michael@202 | 2 | ; Configuration file for MeetMe simple conference rooms for Asterisk of course. |
| michael@202 | 3 | ; |
| michael@202 | 4 | ; This configuration file is read every time you call app meetme() |
| michael@202 | 5 | |
| michael@202 | 6 | ;[general] |
| michael@202 | 7 | ;audiobuffers=32 ; The number of 20ms audio buffers to be used |
| michael@202 | 8 | ; when feeding audio frames from non-Zap channels |
| michael@202 | 9 | ; into the conference; larger numbers will allow |
| michael@202 | 10 | ; for the conference to 'de-jitter' audio that arrives |
| michael@202 | 11 | ; at different timing than the conference's timing |
| michael@202 | 12 | ; source, but can also allow for latency in hearing |
| michael@202 | 13 | ; the audio from the speaker. Minimum value is 2, |
| michael@202 | 14 | ; maximum value is 32. |
| michael@202 | 15 | ; |
| michael@202 | 16 | ;[rooms] |
| michael@202 | 17 | ; |
| michael@202 | 18 | ; Usage is conf => confno[,pin][,adminpin] |
| michael@202 | 19 | ; |
| michael@202 | 20 | ; Note that once a participant has called the conference, a change to the pin |
| michael@202 | 21 | ; number done in this file will not take effect until there are no more users |
| michael@202 | 22 | ; in the conference and it goes away. When it is created again, it will have |
| michael@202 | 23 | ; the new pin number. |
| michael@202 | 24 | ; |
| michael@202 | 25 | ;conf => 1234 |
| michael@202 | 26 | ;conf => 2345,9938 |
