/etc/amportal.conf

The main configuration file for freePBX (named amportal for historal reasons - this will probably be changed at some point).

See: browser:freepbx/trunk/amportal.conf

Options

AUTHTYPE

Type of authentication to use

  • none (default) No authentication is used, the username is assumed to be AMPDBUSER and always has admin access (rights to everything).
  • database Authentication is done through the ampusers table, managed by the 'Administrators' page in the GUI. Each user can have different access rights.

There is a fallback that if the AMPDBUSER logs in with AMPDBPASS, they are granted admin rights.

  • webserver FreePBX provides access control only, no authentication. A username passed by the webserver is assumed to be logged in successfully, and is given the rights that user has in the ampusers table (managed from the 'Administrators' page in the GUI). If the username is the same as AMPDBUSER, then they are given admin rights.

This method should only be used when the webserver is providing some kind of authentication, for example by .htaccess files, Apache's mod_auth_ldap, etc. Warning: without providing protection, ANY user name passed, regardless of the password, will be accepted! A misconfigured webserver can leave your system unsecure.

"Undocumented" options

AMPDISABLELOG

Disables logging to the freepbx_log database table.

Values: true, false. Defaults to false

DEVEL

Enables extra developer features.

  • Shows a module information tab in module admin
  • Shows page processing time in the main freepbx view

Values: true, false. Defaults to false

DEVELRELOAD

Always keeps reload button active, regardless if it is really "needed" or not

Values: true, false. Defaults to false

AMPBADNUMBER

Defaults to true, if set to false the bad-number context will not be created.

Donate



Support
Download
Develop
Forums
News
Documentation
Paid Support
About

Paid Ads