Skip to content

How BeePanel works

Last updated:

Browse articles
On this page

BeePanel is one program that you install on a Linux server, ideally the server your PBX runs on. It runs as a background service, reads what it needs from Asterisk, and serves the panel to your users' browsers. Your call data stays on your own servers.

What BeePanel reads

  • Live calls and queues: through the Asterisk Manager Interface (AMI). BeePanel follows calls, extensions, and queue agents as they change and carries out the call actions your users are allowed to take, such as a transfer or a pickup. See AMI connection.
  • Call history: from the Channel Event Logging (CEL) database Asterisk writes. BeePanel only reads it. See Call history source.
  • Queue statistics: from the Asterisk queue log, as a file or a database table. See Queue log.
  • Recordings: from the directory Asterisk records calls into. BeePanel only reads it.

Call history, queue statistics, and recordings need the Pro edition. The Standard edition is the live product: the live panel, call and queue actions, users and permissions, and status.

What BeePanel stores

BeePanel keeps its own database on the server it runs on: users and permissions, settings, license state, and with Pro the call history it builds from CEL and its copy of the queue log events. It never writes to the CEL database, the queue log, or the recordings.

How users reach it

Users open BeePanel in a web browser. The panel is served by BeePanel itself, over HTTP on port 18080 by default or over HTTPS, and live changes reach the browser as they happen. No separate web server is needed. See Network and ports.

What leaves your server

BeePanel sends no usage statistics, error reports, or logs anywhere. It connects to BeePanel services only for these:

  • Licensing: starting a trial, activating a license, and checking its status.
  • Updates: downloading a new version when an administrator runs the update command.
  • Call transcription: sending one recording when a permitted user asks for its transcript, if an administrator has set transcription up, with Pro. See Call transcription.

Where to install it

On the PBX server, the installer prepares the AMI connection, the call history events, and read access to the recordings and the queue log for you. This is the recommended and most complete setup. BeePanel can also run on a separate Linux server; you then prepare these yourself. See Installing on a server separate from the PBX.

Installation changes your PBX only in small, marked places that BeePanel can remove again, apart from read permissions on the recordings and the queue log, which stay after uninstall. See What BeePanel changes on your PBX.

Can’t find what you need? Write to support@beepanel.io.