aboutsummaryrefslogtreecommitdiffstats
path: root/configs
diff options
context:
space:
mode:
authorkpfleming <kpfleming@f38db490-d61c-443f-a65b-d21fe96a405b>2008-01-17 16:17:52 +0000
committerkpfleming <kpfleming@f38db490-d61c-443f-a65b-d21fe96a405b>2008-01-17 16:17:52 +0000
commit3b7a68b182210ac85c009ca90e9d6346db16b081 (patch)
treefe2a9e9205d3e73881f042d6e214e48c50239c13 /configs
parentd866061e1dfbc7b484e9adea7af7be2f91f2d87d (diff)
major reliability and performance improvement in VWMI monitoring for FXO ports (code by markster, me and dbailey)
git-svn-id: http://svn.digium.com/svn/asterisk/trunk@98990 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'configs')
-rw-r--r--configs/zapata.conf.sample4
1 files changed, 3 insertions, 1 deletions
diff --git a/configs/zapata.conf.sample b/configs/zapata.conf.sample
index 884d235f6..f369a7947 100644
--- a/configs/zapata.conf.sample
+++ b/configs/zapata.conf.sample
@@ -343,9 +343,11 @@ usecallerid=yes
; the script specified by the mwimonitornotify option is executed. Also, an
; internal Asterisk MWI event will be generated so that any other part of
; Asterisk that cares about MWI state changes will get notified, just as if
-; the state change came from app_voicemail.
+; the state change came from app_voicemail. The energy level that must be seen
+; before starting the MWI detection process can be set with 'mwilevel'.
;
;mwimonitor=no
+;mwilevel=512
;
; This option is used in conjunction with mwimonitor. This will get executed
; when incoming MWI state changes. The script is passed 2 arguments. The