diff options
author | Sean Bright <sean@malleable.com> | 2009-05-28 14:39:21 +0000 |
---|---|---|
committer | Sean Bright <sean@malleable.com> | 2009-05-28 14:39:21 +0000 |
commit | f22962a0c1973a867893bc144e5bd1bd44053a84 (patch) | |
tree | 2e8e77235c0fb39f0551db5e6012057fc8c580d0 /configs/meetme.conf.sample | |
parent | a7d813cae7568f9c587dc994b0654d9b7384565a (diff) |
Remove a bunch of trailing whitespace in preparation for reformatting/cleanup.
Let's try that again, this time removing trailing whitespace and not leading
whitespace. I can't believe no one noticed.
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@197535 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'configs/meetme.conf.sample')
-rw-r--r-- | configs/meetme.conf.sample | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/configs/meetme.conf.sample b/configs/meetme.conf.sample index 05bcb893f..c40c4606e 100644 --- a/configs/meetme.conf.sample +++ b/configs/meetme.conf.sample @@ -5,13 +5,13 @@ [general] ;audiobuffers=32 ; The number of 20ms audio buffers to be used -; when feeding audio frames from non-DAHDI 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. + ; when feeding audio frames from non-DAHDI 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. ; ; Conferences may be scheduled from realtime? ;schedule=yes @@ -34,12 +34,12 @@ ; [rooms] ; -; Usage is conf => confno[,pin][,adminpin] +; 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 => 1234 ;conf => 2345,9938 |