Show
Ignore:
Timestamp:
05/16/11 20:29:39 (1 year ago)
Author:
p_lindheimer
Message:

Merged revisions 11124-11125,11128-11133,11135,11137,11145-11147,11149,11166,11168,11216,11228-11229,11240-11241,11243-11244,11255,11263-11264,11272,11278,11280,11282,11285,11291-11293,11300,11302,11321,11334,11339-11343,11352,11363-11364,11366,11368,11382-11384,11388-11390,11399,11405-11406,11421,11449,11453-11460,11462-11464,11471,11482,11485-11487,11493-11494,11498,11502,11504,11528,11530,11535,11543,11555,11558,11574-11576,11579,11581,11583,11585-11587,11589,11591-11592,11599,11622,11629,11631,11633,11637-11639,11641,11652,11662-11663,11666,11668,11671-11672,11675-11676,11704,11711,11714,11719,11721,11723,11725-11726,11732,11755,11760,11762-11764,11767,11769-11770,11772-11774,11796,11799-11800,11805,11807,11810,11812,11818,11822,11826,11828,11830,11841-11842,11853-11855,11891-11892,11900,11928,11931,11937-11940,11944,11954,11960,11968,11971-11974,11986-11987,12016,12021-12022,12024,12036-12037,12044-12046,12056,12061,12066,12068,12073,12076,12154-12156 via svnmerge from

Merged 2.9 branch to trunk.

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved

  • freepbx/trunk

    • Property svnmerge-integrated changed from /freepbx/branches/2.9:1-11117 to /freepbx/branches/2.9:1-12166

  • freepbx/trunk/amportal.conf

    r10579 r12167  
    1414#    along with FreePBX.  If not, see <http://www.gnu.org/licenses/>. 
    1515# 
    16 # This file contains settings for components of the Asterisk Management Portal 
    17 # Spaces are not allowed! 
    18 # Run /usr/src/AMP/apply_conf.sh after making changes to this file 
     16# This file contains settings for components of FreePBX 
     17# This file will be used to define the initial configuration installed 
     18# by the install_amp installation program, which can also obtain some 
     19# of this interactively. 
     20# 
     21# Ths file should be writeable by the httpd user (usually asterisk for 
     22# FreePBX installations). Once running, FreePBX will maintain these settings 
     23# in a database and this file will be overwritten. It will also generate 
     24# a based freepbx.conf configuration file, usually in /etc, that will 
     25# be used to bootstrap FreePBX and any associated programs. The content 
     26# of that file will include the core database credentials and path 
     27# information needed to bootstrap FreePBX. 
     28# 
     29# Once installed and running properly out of the database, this file 
     30# will be overwritten to include all the configuration settings specified 
     31# in the Advanced Settings page of FreePBX and made available here for 
     32# potential outside applications that may require access to some of these 
     33# parameters. This will be maintained for a transitionary period to give 
     34# the eco system time to conform to the new mode of setting configurations. 
     35# 
     36# The freepbx.conf file can also be specified in an evnironment variable: 
     37# 
     38#   FREEPBX_CONF 
     39# 
     40# A full path should be specified. This configuration file is formatted as 
     41# a very short snippet of PHP, here is an example of what it should look 
     42# like: 
     43# 
     44#----------------------------------------------------------------- 
     45# <?php 
     46# $amp_conf['AMPDBUSER']  = 'my_db_user'; 
     47# $amp_conf['AMPDBPASS']  = 'my_db_password'; 
     48# $amp_conf['AMPDBHOST']  = 'localhost'; 
     49# $amp_conf['AMPDBNAME']  = 'asterisk'; 
     50# $amp_conf['AMPDBENGINE'] = 'mysql'; 
     51# $amp_conf['datasource'] = ''; //for sqlite3 
     52# require_once('/var/www/html/admin/bootstrap.php'); 
     53#----------------------------------------------------------------- 
     54# 
     55# Where the paths and credentials match up with your system. This file 
     56# will be created by install_amp for you if not present, or will be 
     57# create by the amportal script that is used to start and stop Asterisk 
     58# and FOP for FreePBX. 
     59 
     60# Run /usr/src/AMP/apply_conf.sh after making changes to Asterisk 
     61# manager credentials or MySQL CDR credentials to apply the changes to 
     62# the corresponding manager.conf and cdr_mysql.conf files. 
     63 
    1964 
    2065# FreePBX Database configuration 
    …… 
    2570# AMPDBPASS: Password for AMPDBUSER (above) 
    2671# AMPENGINE: Telephony backend engine (e.g. asterisk) 
     72# 
    2773# AMPMGRUSER: Username to access the Asterisk Manager Interface 
    2874# AMPMGRPASS: Password for AMPMGRUSER 
    …… 
    3076AMPDBHOST=localhost 
    3177AMPDBENGINE=mysql 
    32 # AMPDBNAME=asterisk 
    33 # AMPDBUSER=asteriskuser 
    34 # AMPDBPASS=amp109 
    3578AMPENGINE=asterisk 
    3679AMPMGRUSER=admin 
    …… 
    5194# AMPWEBADDRESS=x.x.x.x|hostname 
    5295 
    53 # FOPWEBROOT: Path to the Flash Operator Panel webroot (leave off trailing slash) 
    54 # FOPPASSWORD: Password for performing transfers and hangups in the Flash Operator Panel 
    55 # FOPRUN: Set to true if you want FOP started by freepbx_engine (amportal_start), false otherwise 
    56 # FOPDISABLE: Set to true to disable FOP in interface and retrieve_conf.  Useful for sqlite3  
    57 # or if you don't want FOP. 
    58 # 
    59 FOPRUN=true 
    6096FOPWEBROOT=/var/www/html/panel 
    6197FOPPASSWORD=passw0rd 
    62  
    63 # FOPSORT=extension|lastname 
    64 # DEFAULT VALUE: extension 
    65 # FOP should sort extensions by Last Name [lastname] or by Extension [extension] 
    6698 
    6799# This is the default admin name used to allow an administrator to login to ARI bypassing all security. 
    …… 
    79111AUTHTYPE=database 
    80112 
    81 # AMPADMINLOGO=filename 
    82 # Defines the logo that is to be displayed at the TOP RIGHT of the admin screen. This enables 
    83 # you to customize the look of the administration screen. 
    84 # NOTE: images need to be saved in the ..../admin/images directory of your AMP install 
    85 # This image should be 55px in height 
    86 AMPADMINLOGO=logo.png 
    87  
    88 # USECATEGORIES=true|false 
    89 # DEFAULT VALUE: true 
    90 # Controls if the menu items in the admin interface are sorted by category (true), or sorted  
    91 # alphabetically with no categories shown (false). 
    92  
    93113# AMPEXTENSIONS=extensions|deviceanduser 
    94114# Sets the extension behavior in FreePBX.  If set to 'extensions', Devices and Users are 
    …… 
    100120AMPEXTENSIONS=extensions 
    101121 
    102 # ENABLECW=true|false 
    103 # DEFAULT VALUE: true 
    104 # Enable call waiting by default when an extension is created. Set to 'no' to if you don't want  
    105 # phones to be commissioned with call waiting already enabled. The user would then be required 
    106 # to dial the CW feature code (*70 default) to enable their phone. Most installations should leave 
    107 # this alone. It allows multi-line phones to receive multiple calls on their line appearances. 
    108  
    109 # CWINUSEBUSY=true|false 
    110 # DEFAULT VALUE: true 
    111 # For extensions that have CW enabled, report unanswered CW calls as 'busy' (resulting in busy  
    112 # voicemail greeting). If set to no, unanswered CW calls simply report as 'no-answer'. 
    113  
    114 # AMPBADNUMBER=true|false 
    115 # DEFAULT VALUE: true 
    116 # Generate the bad-number context which traps any bogus number or feature code and plays a 
    117 # message to the effect. If you use the Early Dial feature on some Grandstream phones, you 
    118 # will want to set this to false. 
    119  
    120 # AMPBACKUPSUDO=true|false 
    121 # DEFAULT VALUE: false 
    122 # This option allows you to use sudo when backing up files. Useful ONLY when using AMPPROVROOT 
    123 # Allows backup and restore of files specified in AMPPROVROOT, based on permissions in /etc/sudoers 
    124 # for example, adding the following to sudoers would allow the user asterisk to run tar on ANY file 
    125 # on the system: 
    126 # asterisk localhost=(root)NOPASSWD: /bin/tar 
    127 # Defaults:asterisk !requiretty 
    128 # PLEASE KEEP IN MIND THE SECURITY RISKS INVOLVED IN ALLOWING THE ASTERISK USER TO TAR/UNTAR ANY FILE 
    129  
    130 # CUSTOMASERROR=true|false 
    131 # DEFAULT VALUE: true 
    132 # If false, then the Destination Registry will not report unknown destinations as errors. This should be 
    133 # left to the default true and custom destinations should be moved into the new custom apps registry. 
    134  
    135 # DYNAMICHINTS=true|false 
    136 # DEFAULT VALUE: false 
    137 # If true, Core will not statically generate hints, but instead make a call to the AMPBIN php script,  
    138 # and generate_hints.php through an Asterisk's #exec call. This requires Asterisk.conf to be configured  
    139 # with "execincludes=yes" set in the [options] section. 
    140  
    141 # XTNCONFLICTABORT=true|false 
    142 # BADDESTABORT=true|false 
    143 # DEFAULT VALUE: false 
    144 # Setting either of these to true will result in retrieve_conf aborting during a reload if an extension 
    145 # conflict is detected or a destination is detected. It is usually better to allow the reload to go 
    146 # through and then correct the problem but these can be set if a more strict behavior is desired. 
    147  
    148 # SERVERINTITLE=true|false 
    149 # DEFAULT VALUE: false 
    150 # Precede browser title with the server name. 
    151  
    152 # USEDEVSTATE = true|false 
    153 # DEFAULT VALUE: false 
    154 # If this is set, it assumes that you are running Asterisk 1.4 or higher and want to take advantage of the 
    155 # func_devstate.c backport available from Asterisk 1.6. This allows custom hints to be created to support 
    156 # BLF for server side feature codes such as daynight, followme, etc. 
    157  
    158 # MODULEADMINWGET=true|false 
    159 # DEFAULT VALUE: false 
    160 # Module Admin normally tries to get its online information through direct file open type calls to URLs that 
    161 # go back to the freepbx.org server. If it fails, typically because of content filters in firewalls that 
    162 # don't like the way PHP formats the requests, the code will fall back and try a wget to pull the information. 
    163 # This will often solve the problem. However, in such environment there can be a significant timeout before 
    164 # the failed file open calls to the URLs return and there are often 2-3 of these that occur. Setting this 
    165 # value will force FreePBX to avoid the attempt to open the URL and go straight to the wget calls. 
    166  
    167 # AMPDISABLELOG=true|false 
    168 # DEFAULT VALUE: true 
    169 # Whether or not to invoke the FreePBX log facility 
    170  
    171 # AMPSYSLOGLEVEL=LOG_EMERG|LOG_ALERT|LOG_CRIT|LOG_ERR|LOG_WARNING|LOG_NOTICE|LOG_INFO|LOG_DEBUG|LOG_SQL|SQL 
    172 # DEFAULT VALUE: LOG_ERR 
    173 # Where to log if enabled, SQL, LOG_SQL logs to old MySQL table, others are passed to syslog system to 
    174 # determine where to log 
    175  
    176 # AMPENABLEDEVELDEBUG=true|false 
    177 # DEFAULT VALUE: false 
    178 # Whether or not to include log messages marked as 'devel-debug' in the log system 
    179  
    180 # AMPMPG123=true|false  
    181 # DEFAULT VALUE: true 
    182 # When set to false, the old MoH behavior is adopted where MP3 files can be loaded and WAV files converted 
    183 # to MP3. The new default behavior assumes you have mpg123 loaded as well as sox and will convert MP3 files 
    184 # to WAV. This is highly recommended as MP3 files heavily tax the system and can cause instability on a busy 
    185 # phone system. 
    186  
    187 # CDR DB Settings: Only used if you don't use the default values provided by FreePBX. 
    188 # CDRDBHOST: hostname of db server if not the same as AMPDBHOST 
    189 # CDRDBPORT: Port number for db host  
    190 # CDRDBUSER: username to connect to db with if it's not the same as AMPDBUSER 
    191 # CDRDBPASS: password for connecting to db if it's not the same as AMPDBPASS 
    192 # CDRDBNAME: name of database used for cdr records 
    193 # CDRDBTYPE: mysql or postgres mysql is default 
    194 # CDRDBTABLENAME: Name of the table in the db where the cdr is stored cdr is default  
    195  
    196 # AMPVMUMASK=mask  
    197 # DEFAULT VALUE: 077  
    198 # Defaults to 077 allowing only the asterisk user to have any permission on VM files. If set to something 
    199 # like 007, it would allow the group to have permissions. This can be used if setting apache to a different 
    200 # user then asterisk, so that the apache user (and thus ARI) can have access to read/write/delete the 
    201 # voicemail files. If changed, some of the voicemail directory structures may have to be manually changed. 
    202  
    203 # DASHBOARD_STATS_UPDATE_TIME=integer_seconds 
    204 # DEFAULT VALUE: 6 
    205 # DASHBOARD_INFO_UPDATE_TIME=integer_seconds 
    206 # DEFAULT VALUE: 20 
    207 # These can be used to change the refresh rate of the System Status Panel. Most of 
    208 # the stats are updated based on the STATS interval but a few items are checked 
    209 # less frequently (such as Asterisk Uptime) based on the INFO value 
    210  
    211 # ZAP2DAHDICOMPAT=true|false 
    212 # DEFAULT VALUE: false 
    213 # If set to true, FreePBX will check if you have chan_dadhi installed. If so, it will 
    214 # automatically use all your ZAP configuration settings (devices and trunks) and 
    215 # silently convert them, under the covers, to DAHDI so no changes are needed. The 
    216 # GUI will continue to refer to these as ZAP but it will use the proper DAHDI channels. 
    217 # This will also keep Zap Channel DIDs working. 
    218  
    219 # CHECKREFERER=true|false 
    220 # DEFAULT VALUE: true 
    221 # When set to the default value of true, all requests into FreePBX that might possibly add/edit/delete 
    222 # settings will be validated to assure the request is coming from the server. This will protect the system 
    223 # from CSRF (cross site request forgery) attacks. It will have the effect of preventing legitimately entering 
    224 # URLs that could modify settings which can be allowed by changing this field to false. 
    225  
    226 # USEQUEUESTATE=true|false 
    227 # DEFAULT VALUE: false 
    228 # Setting this flag will generate the required dialplan to integrate with the following Asterisk patch: 
    229 # https://issues.asterisk.org/view.php?id=15168 
    230 # This feature is planned for a future 1.6 release but given the existence of the patch can be used prior. Once 
    231 # the release version is known, code will be added to automatically enable this format in versions of Asterisk 
    232 # that support it. 
    233  
    234 # USEGOOGLEDNSFORENUM=true|false 
    235 # DEFAULT VALUE: false 
    236 # Setting this flag will generate the required global variable so that enumlookup.agi will use Google DNS 
    237 # 8.8.8.8 when performing an ENUM lookup. Not all DNS deals with NAPTR record, but Google does. There is a 
    238 # drawback to this as Google tracks every lookup. If you are not comfortable with this, do not enable this 
    239 # setting. Please read Google FAQ about this: http://code.google.com/speed/public-dns/faq.html#privacy 
    240  
    241 # MOHDIR=subdirectory_name 
    242 # This is the subdirectory for the MoH files/directories which is located in ASTVARLIBDIR 
    243 # if not specified it will default to mohmp3 for backward compatibility. 
    244 # Enter directory without leading or trailing slash 
    245  
    246 # RELOADCONFIRM=true|false 
    247 # DEFAULT VALUE: true 
    248 # When set to false, will bypass the confirm on Reload Box 
    249  
    250 # FCBEEPONLY=true|false 
    251 # DEFAULT VALUE: false 
    252 # When set to true, a beep is played instead of confirmation message when activating/de-activating: 
    253 # CallForward, CallWaiting, DayNight, DoNotDisturb and FindMeFollow 
    254  
    255 # DISABLECUSTOMCONTEXTS=true|false 
    256 # DEFAULT VALUE: false 
    257 # Normally FreePBX auto-generates a custom context that may be usable for adding custom dialplan to modify the 
    258 # normal behavior of FreePBX. It takes a good understanding of how Asterisk processes these includes to use 
    259 # this and in many of the cases, there is no useful application. All includes will result in a WARNING in the 
    260 # Asterisk log if there is no context found to include though it results in no errors. If you know that you 
    261 # want the includes, you can set this to true. If you comment it out FreePBX will revert to legacy behavior 
    262 # and include the contexts. 
    263  
    264 # TCINTERVAL=integer_seconds 
    265 # DEFAULT VALUE: 60 
    266 # The polling interval used by the Time Conditions manintenace task, launched by an Asterisk call file 
    267 # used to update Time Conditions override states as well as keep custom device state hint values up-to-date 
    268 # when being used with BLF. This interval should be shorter than the shortest time condition true (open) or 
    269 # false (closed) interval to assure that an override is reset after the current time period has expired that 
    270 # it was set in. 
    271  
    272 # TCMAINT=true|false 
    273 # DEFAULT VALUE: true 
    274 # If set to false, this will override the execution of the Time Conditons maintenace task launched by call 
    275 # files. If all the feature codes for time conditions are disabled, the maintenance task will not be launched 
    276 # so this is not needed for that condition. Setting this to false would be fairly un-common. On an extremely 
    277 # active system that has constant calls flowing throught all time conditions of interest that might be overriden 
    278 # one might set this to avoid the additional polling that would otherwise occur since calls traversing the 
    279 # time conditions contexts will also maintain all the necessary state information. You may also set this 
    280 # temporarily if debugging a system to avoid the periodic dialplan running through the CLI that the maintenance 
    281 # task otherwise creates. 
    282  
    283 # DAYNIGHTTCHOOK true|false 
    284 # DEFAULT VALUE: false 
    285 # By default, the Day/Night module will not hook Time Conditions allowing one to associate a daynight manual 
    286 # override with a time condition since now time conditions have their own feature code. If there is already 
    287 # an associaiton configured (on an upgraded system), this will have no affect for the Time Conditions that 
    288 # are effected. Setting this to true reverts the previous behavior by allowing for the continued use of a 
    289 # daynight toggle to be associated with a time conditon. This can be useful for two scenarios. First, to override 
    290 # a Time Condition without the automatic resetting that occurs with the built in Time Condition overrides. 
    291 # The second use is the ability to associate a single daynight toggle with multiple time conditions thus creating 
    292 # a "master switch" that can be used to override several possible call flows through different time conditions. 
    293