When BeePanel is installed on the PBX server, the installer adds a few things so that BeePanel can connect to Asterisk and read its data. It never replaces or rewrites the configuration your PBX manages. Every file change is in BeePanel's own files or between marker lines, so it can be found and removed again. The read permissions described below are the exception: they carry no marker and stay after uninstall. On a separate server, the installer changes nothing on the PBX.
Files BeePanel owns
The installer creates these files in /etc/asterisk:
| File | Contents |
|---|---|
manager_beepanel.conf |
BeePanel's AMI user, beepanel. See AMI connection. |
extensions_beepanel.conf |
No dialplan; only comments. |
cel_beepanel.conf |
The application start and end events call history needs, when CEL is enabled. See Call history source. |
Include lines in your files
Asterisk loads each file through one marked include block, the only text BeePanel writes into files it does not own:
| Block | Added to |
|---|---|
manager_beepanel.conf |
manager_custom.conf when that file exists and manager.conf includes it; otherwise manager.conf |
extensions_beepanel.conf |
extensions_custom.conf on FreePBX and Issabel; extensions.conf otherwise |
cel_beepanel.conf |
cel_general_custom.conf on FreePBX and Issabel; cel.conf otherwise |
Each block looks like this one:
; BEGIN BEEPANEL MANAGED MANAGER INCLUDE
#include manager_beepanel.conf
; END BEEPANEL MANAGED MANAGER INCLUDERunning the installer again does not add a second block.
Reloads
The installer then reloads the manager and the dialplan, and the CEL module
when it added or changed cel_beepanel.conf or its include block:
asterisk -rx "manager reload"
asterisk -rx "dialplan reload"
asterisk -rx "module reload cel"It never restarts Asterisk, so calls in progress are not affected.
Read access to recordings and the queue log
BeePanel runs as the beepanel system account. When that account cannot
read the recording directory or the queue log, the installer gives it
read-only access with file access control lists (ACLs): read access to the
recordings, the queue log and its rotated files, and passage through the
directories above them. Files created later in those directories can be
read too. For the queue log this covers its whole directory, usually
/var/log/asterisk: other logs Asterisk creates there later become readable
as well. The installer prints every path it granted. A recording directory
or queue log you choose after setup gets no permission from the installer;
give it yourself.
The installer adds no write access, changes no owner or group, and adds the account to no group. These read permissions stay after BeePanel is uninstalled; remove them yourself when you no longer need them.
What BeePanel never changes
- Configuration generated or managed by FreePBX or Issabel, and its database.
- CEL itself: the installer never turns CEL on, changes where CEL is written, or installs Asterisk modules.
manager_custom.confis never created; the installer adds to it only when it already exists.- Firewall and SELinux settings.
Removing the changes
Uninstalling BeePanel removes its files and include blocks and reloads the same parts of Asterisk. It removes only content that still carries BeePanel's markers; text you added around it stays. See Uninstalling BeePanel.