Installing on a server separate from the PBX

BeePanel can run on a Linux server of its own and reach the PBX over the network. The installer then cannot prepare anything on the PBX: you create BeePanel's AMI user, its database account, and its access to the recordings yourself. Installing on the PBX server is simpler and more complete; see How BeePanel works.

Limits

BeePanel does not connect to the PBX server over SSH, change its configuration, or create a VPN, a tunnel, or a mount for you.
AMI travels over your network. Keep it on a private network, a VPN, or a tunnel; BeePanel asks you to accept this risk when you enter the connection.
Recordings must be mounted on the BeePanel server, for example over NFS.
Uninstalling BeePanel does not remove what you add on the PBX; remove it yourself.

Before you start

A BeePanel server that meets the system requirements.
Root access to the PBX server and to the BeePanel server.
A network path from the BeePanel server to the PBX's AMI port and, for call history, to its CEL database. See Network and ports.

On the PBX server

Change nothing on the PBX beyond these steps.

Add BeePanel's AMI user. On FreePBX and Issabel add it to /etc/asterisk/manager_custom.conf; otherwise to /etc/asterisk/manager.conf. Use the BeePanel server's address and a long random secret:
```
[beepanel]
secret = <a long random secret>
deny = 0.0.0.0/0.0.0.0
deny = ::/0
permit = <BeePanel server address>/32
read = system,call,agent
write = reporting,system,call,originate,agent
displayconnects = no
```
For an IPv6 address, write /128 instead of /32.
Apply it:
```
asterisk -rx "manager reload"
```
Check that AMI is enabled and listens on an address the BeePanel server can reach, and that the PBX's firewall lets the BeePanel server reach the AMI port, 5038 by default. On FreePBX and Issabel, change these through the PBX's own settings rather than by editing manager.conf.
For call history, with Pro: create a database account that can read the CEL table and connect from the BeePanel server, and let the database accept that connection. A read-only account is recommended. See Call history source.
For call history, add the application events that the installer adds on a PBX server. Create /etc/asterisk/cel_beepanel.conf with these lines:
```
[general](+)
events=APP_START,APP_END
apps=Dial,Queue,Playback,Background,ChanSpy,ExtenSpy,VoiceMail,VoiceMailMain,ConfBridge,MeetMe,Record,MixMonitor,Monitor,StopMixMonitor,Park,ParkedCall
```
Add #include cel_beepanel.conf to cel_general_custom.conf on FreePBX and Issabel, or below the [general] section of cel.conf otherwise, then run asterisk -rx "module reload cel". This step needs CEL to be enabled already.
Share the recording directory, usually /var/spool/asterisk/monitor, with the BeePanel server. Read-only sharing is enough.

On the BeePanel server

Run the install command as root; see Installing BeePanel. The installer reports warning: no supported local PBX detected, which is expected here.
Mount the shared recording directory, and make sure the beepanel account can read it and every file in it. The installer grants no access to it.
Open the setup address and complete the wizard. On Configuration:
- AMI connection: enter the PBX's address and AMI port, for example 192.0.2.10:5038, with the username beepanel and the secret. Accept the transport risk, then choose Verify connection.
- Call history source, with Pro: enter the CEL database's address and the account you created.
- Recording directory: enter the mount's path. It must be a real directory, not a symbolic link.
- Queue log, whose statistics need Pro: choose the queue log table in the CEL database, or the queue log file if you mounted its directory too.

Checking the result

Management > Status shows the PBX connection working, and with Pro the call history source too.
The live panel shows your extensions.
With Pro, a recorded call's recording plays in Reports > Call history.