f11d0b3d54
https://origsvn.digium.com/svn/asterisk/branches/1.4 ................ r55006 | russell | 2007-02-16 16:49:42 -0600 (Fri, 16 Feb 2007) | 17 lines Merged revisions 55005 via svnmerge from https://origsvn.digium.com/svn/asterisk/branches/1.2 ........ r55005 | russell | 2007-02-16 16:48:22 -0600 (Fri, 16 Feb 2007) | 9 lines Revert the change I did in revisions 54955, 54969, and 54970, in 1.2, 1.4, and trunk. I decided that once a conference is created from meetme.conf, it is acceptable behavior that the pin can not be changed until the conference goes away. I also added a note in meetme.conf to describe this behavior. We still have another issue in 1.4 and trunk where some conferences with no users don't go away. That is the real bug that needs to be addressed here. ........ ................ git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@55007 65c4cc65-6c06-0410-ace0-fbb531ad65f3
27 lines
926 B
Text
27 lines
926 B
Text
;
|
|
; Configuration file for MeetMe simple conference rooms for Asterisk of course.
|
|
;
|
|
; This configuration file is read every time you call app meetme()
|
|
|
|
[general]
|
|
;audiobuffers=32 ; The number of 20ms audio buffers to be used
|
|
; when feeding audio frames from non-Zap channels
|
|
; into the conference; larger numbers will allow
|
|
; for the conference to 'de-jitter' audio that arrives
|
|
; at different timing than the conference's timing
|
|
; source, but can also allow for latency in hearing
|
|
; the audio from the speaker. Minimum value is 2,
|
|
; maximum value is 32.
|
|
;
|
|
[rooms]
|
|
;
|
|
; Usage is conf => confno[,pin][,adminpin]
|
|
;
|
|
; Note that once a participant has called the conference, a change to the pin
|
|
; number done in this file will not take effect until there are no more users
|
|
; in the conference and it goes away. When it is created again, it will have
|
|
; the new pin number.
|
|
;
|
|
;conf => 1234
|
|
;conf => 2345,9938
|