Web Interface for user

Asterisk Asterisk Support
1

hi,

There is quite a few gui/web interfaces to configure/manage asterisk.
But is there a web interface or client for a user i.e., for purpose of viewing my last dialed nos, scheduling a conf call, checking my line’s status…

Thanks

2

Are you still looking for a GUI? Take a look at my project.

3

You are assuming that Asterisk is a PABX, when it is actually a toolkit that can, amongst other things, be used to implement a PABX.

4

Absolutely fair point!
You’re right — Asterisk itself is not a PBX, but a telephony toolkit/framework that can be used to build PBX systems (among many other things).
GonoPBX doesn’t try to replace that flexibility — it builds a structured management and multi-tenant layer around Asterisk, while keeping the underlying telephony engine intact.
So the goal is more about architecture, orchestration and operational clarity — not redefining what Asterisk fundamentally is.
Appreciate the clarification!

5

pjsip_config.py

PJSIP_CONFIG_PATH = “/etc/asterisk/custom/pjsip.conf”
EXTERNAL_IP = os.getenv(“EXTERNAL_IP”, “127.0.0.1”)

it’s a facepalm

this tool need’s root?

6

Good catch, thank you! You’re right - requiring root access for the tool and having
127.0.0.1 as a fallback for EXTERNAL_IP is definitely a facepalm moment.

I’ll fix this by:

  • Moving the config to a user-writable location (e.g., /var/lib/gonopbx/)
  • Making EXTERNAL_IP a required env variable without a meaningless default
  • Having Asterisk include the generated config instead of writing directly to /etc/asterisk/

Appreciate the feedback - this will make the deployment much cleaner and more secure.

7

Both points have been fixed:

EXTERNAL_IP: The 127.0.0.1 default was indeed a facepalm. The external IP is now auto-detected (ipify/ifconfig.me/icanhazip, fallback to default route). The env variable can optionally be set to override, but is no longer required.

Root privileges: No, root is not strictly required. Docker group membership is sufficient (sudo usermod -aG docker $USER). The installer now checks this upfront and provides a clear hint. The backend needs access to the Docker socket
for docker exec into the Asterisk container, long-term this will be replaced with pure AMI communication.

8

don’t use docker for critical services.

you project is a pet project, sorry

9

Thanks for your input. While GonoPBX started as a passion project, it’s already running in production environments. The Docker architecture was a deliberate choice to simplify deployment and updates - especially valuable for smaller teams without dedicated IT departments.

Whether Docker is suitable for “critical services” depends on the use case. We’re talking about telephony for small to mid-sized businesses, not carrier-grade infrastructure. Docker is perfectly appropriate here and is used by commercial VoIP solutions as well.

If you have specific architectural concerns, I’m open to constructive discussion. The project is open source - contributions are welcome!