From cc42229f26c66864913302572f034f19d571d71a Mon Sep 17 00:00:00 2001 From: Walter Doekes Date: Mon, 27 Jan 2014 08:17:22 +0000 Subject: manager: The eventfilter= option now takes an extended regex. In pre-trunk versions (...12) it accepts a basic regex, which is confusing because all other regexes in asterisk are of the extended kind. Review: https://reviewboard.asterisk.org/r/3147/ git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@406618 65c4cc65-6c06-0410-ace0-fbb531ad65f3 --- configs/manager.conf.sample | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) (limited to 'configs') diff --git a/configs/manager.conf.sample b/configs/manager.conf.sample index fd54b81b9..f31c6d397 100644 --- a/configs/manager.conf.sample +++ b/configs/manager.conf.sample @@ -94,13 +94,14 @@ bindaddr = 0.0.0.0 ; user. ; ;eventfilter=Event: Newchannel -;eventfilter=!Channel: DAHDI.* +;eventfilter=Channel: (PJ)?SIP/(james|jim|john)- +;eventfilter=!Channel: DAHDI/ ; The eventfilter option is used to whitelist or blacklist events per user. -; A filter consists of a (basic/old-style and unanchored) regular expression -; that is run on the entire event data. If the first character of the filter -; is an exclamation mark (!), the filter is appended to the blacklist instead -; of the whitelist. After first checking the read access below, the regular -; expression filters are processed as follows: +; A filter consists of an (unanchored) regular expression that is run on the +; entire event data. If the first character of the filter is an exclamation +; mark (!), the filter is appended to the blacklist instead of the whitelist. +; After first checking the read access below, the regular expression filters +; are processed as follows: ; - If no filters are configured all events are reported as normal. ; - If there are white filters only: implied black all filter processed first, ; then white filters. -- cgit v1.2.3