Changeset 10549

Timestamp:

11/12/10 16:41:58 (3 years ago)

Author:

p_lindheimer

Message:

add amportal.conf configuration variables for now Time Conditions overrides re #4636

Files:

• freepbx/trunk/amp_conf/htdocs/admin/libraries/config.functions.php (modified) (2 diffs)
• freepbx/trunk/amportal.conf (modified) (1 diff)

freepbx/trunk/amp_conf/htdocs/admin/libraries/config.functions.php

@@ -16 +16 @@
-  'AMPSYSLOGLEVEL '=> array('std' , 'LOG_ERR'),
-  'ARI_ADMIN_PASSWORD' => array('std' , 'ari_password'),
+  'TCINTERVAL      '=> array('std' , '60'),
-
-  'ASTETCDIR'      => array('dir' , '/etc/asterisk'),
@@ -56 +57 @@
-  'DISABLECUSTOMCONTEXTS'   => array('bool' , false),
-  'DIVERSIONHEADER' => array('bool' , false),
+  'TCMAINT'         => array('bool' , true),
+  'DAYNIGHTTCHOOK'  => array('bool' , false),
-);
-

freepbx/trunk/amportal.conf

@@ -261 +261 @@
-# and include the contexts.
-
+# TCINTERVAL=integer_seconds
+# DEFAULT VALUE: 60
+# The polling interval used by the Time Conditions manintenace task, launched by an Asterisk call file
+# used to update Time Conditions override states as well as keep custom device state hint values up-to-date
+# when being used with BLF. This interval should be shorter than the shortest time condition true (open) or
+# false (closed) interval to assure that an override is reset after the current time period has expired that
+# it was set in.
+
+# TCMAINT=true|false
+# DEFAULT VALUE: true
+# If set to false, this will override the execution of the Time Conditons maintenace task launched by call
+# files. If all the feature codes for time conditions are disabled, the maintenance task will not be launched
+# so this is not needed for that condition. Setting this to false would be fairly un-common. On an extremely
+# active system that has constant calls flowing throught all time conditions of interest that might be overriden
+# one might set this to avoid the additional polling that would otherwise occur since calls traversing the
+# time conditions contexts will also maintain all the necessary state information. You may also set this
+# temporarily if debugging a system to avoid the periodic dialplan running through the CLI that the maintenance
+# task otherwise creates.
+
+# DAYNIGHTTCHOOK true|false
+# DEFAULT VALUE: false
+# By default, the Day/Night module will not hook Time Conditions allowing one to associate a daynight manual
+# override with a time condition since now time conditions have their own feature code. If there is already
+# an associaiton configured (on an upgraded system), this will have no affect for the Time Conditions that
+# are effected. Setting this to true reverts the previous behavior by allowing for the continued use of a
+# daynight toggle to be associated with a time conditon. This can be useful for two scenarios. First, to override
+# a Time Condition without the automatic resetting that occurs with the built in Time Condition overrides.
+# The second use is the ability to associate a single daynight toggle with multiple time conditions thus creating
+# a "master switch" that can be used to override several possible call flows through different time conditions.
+