Settings

Settings live under Management > Settings, which only users allowed to manage BeePanel see. Each row shows a setting's current value and opens an editor that checks a new value before saving it. Setup asks for every setting here except storage and retention and call transcription, so you rarely change them afterwards. Rows that need the Pro edition carry the Pro mark.

Time zone

History, reports, date ranges, and exports use the organization's time zone, and every user sees call times in it. Setup fills in the server's time zone. Changing it later leaves stored calls as they are: history and reports show their times, and group them by day, in the new zone.

AMI connection

The live panel, call events, and call actions such as transfers run over the connection to Asterisk's management interface (AMI). The installer prepares an AMI identity for BeePanel on the PBX, and setup fills in its address and username. Without the connection, BeePanel still installs, and the live features stay unavailable until it is set up. See AMI connection.

Context classification

Which dialplan contexts count as internal and which as external. Endpoints in an internal context are your extensions, endpoints in an external context are your trunks, and call direction in history follows from the same lists. On FreePBX and Issabel, setup proposes from-internal as internal and from-trunk and from-pstn as external. See Context classification.

Recording directory

The directory that holds the call recordings; BeePanel only reads it. Setup proposes /var/spool/asterisk/monitor, or the monitor directory under the Asterisk spool directory. After a change, BeePanel looks for every call's recording in the new directory. When BeePanel runs on a separate server, the recordings must be reachable there, for example through a mounted directory; see Installing on a server separate from the PBX.

Call history source

A read-only connection to the database where Asterisk writes its call events (CEL), the source of call history and reports. MariaDB or MySQL, PostgreSQL, and SQLite are supported. Setup fills in the connection it finds on the PBX. See Call history source.

Queue log

The source of queue statistics: the queue log table on the call history source's database, or the local Asterisk queue log file. Setup proposes whichever it finds. See Queue log.

Storage and retention

BeePanel never deletes call data on its own, and never deletes anything from the call history source. Here you can rebuild call history from the source: only calls still in the source come back, and transcripts are kept unless you choose to delete them as well. The Status page shows the progress.

Panel address

The address, port, and protocol browsers use to reach BeePanel: HTTP, HTTPS with a self-signed certificate BeePanel generates, or HTTPS with your own certificate. The default is HTTP on port 18080 on every network interface. After a change, you sign in again at the new address; if it is not opened within three minutes, the panel returns to the current one. See Network and ports.

Call transcription

Turns a call recording into text with the BeeSTT service when a permitted user asks for its transcript. It is off by default and needs a BeeSTT API key. Saving the setting sends nothing; only the requested recording leaves the server. See Call transcription.