2002-04-09 00:49:07 +00:00
|
|
|
;
|
2005-10-04 22:51:59 +00:00
|
|
|
; Configuration file for MeetMe simple conference rooms for Asterisk of course.
|
2002-04-09 00:49:07 +00:00
|
|
|
;
|
2005-03-17 15:56:55 +00:00
|
|
|
; This configuration file is read every time you call app meetme()
|
2005-11-08 23:19:30 +00:00
|
|
|
|
|
|
|
[general]
|
2006-04-06 15:41:37 +00:00
|
|
|
;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.
|
2005-03-17 15:56:55 +00:00
|
|
|
;
|
2007-10-17 20:42:20 +00:00
|
|
|
; Conferences may be scheduled from realtime?
|
|
|
|
;schedule=yes
|
|
|
|
;
|
|
|
|
; Update realtime when members login/out of the conference
|
|
|
|
;logmembercount=no
|
|
|
|
;
|
|
|
|
; How much earlier than the start time should we allow participants to
|
|
|
|
; join the conference (in seconds)?
|
|
|
|
;fuzzystart=300
|
|
|
|
;
|
|
|
|
; If the participants join too early, how much time should we allow
|
|
|
|
; to tell them that they've joined too early, rather than telling them
|
|
|
|
; the conference simply doesn't exist (in seconds)?
|
|
|
|
;earlyalert=3600
|
|
|
|
;
|
|
|
|
; How many seconds before the scheduled end of the conference should
|
|
|
|
; the participants be warned?
|
|
|
|
;endalert=120
|
|
|
|
;
|
2002-04-09 00:49:07 +00:00
|
|
|
[rooms]
|
|
|
|
;
|
2005-02-22 15:42:41 +00:00
|
|
|
; Usage is conf => confno[,pin][,adminpin]
|
2002-04-09 00:49:07 +00:00
|
|
|
;
|
2007-02-16 22:50:22 +00:00
|
|
|
; 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.
|
|
|
|
;
|
2002-04-09 00:49:07 +00:00
|
|
|
;conf => 1234
|
2004-01-14 06:38:29 +00:00
|
|
|
;conf => 2345,9938
|