Add a Manager / Admin User¶
UnifiedBX has two distinct admin-user concepts that often get confused:
- Administrators (the
ampusersmodule under System Admin → Administrators) — login accounts for the UnifiedBX GUI. - UnifiedBX Manager Users (the
managermodule under System Admin → UnifiedBX Manager Users) — Asterisk Manager Interface (AMI) accounts used by integrations (CRM popups, dialer apps, custom dashboards). NOT for human GUI logins.
This page covers both.
Add a UnifiedBX GUI Administrator¶
For human admins who log into the dashboard.
Steps¶
- Go to System Admin → Administrators.
- Click + Add User.
- Fill in:
- Username — e.g.
jane.admin. - Password — strong, 12+ chars.
- Admin Access —
Fullfor unrestricted, orLimitedto restrict by section. - Section Access (if Limited) — check only the modules they should see.
- Allowed Extensions / Allowed DIDs — leave blank for all, or restrict for tenant-style isolation.
- Username — e.g.
- Click Submit.
- Click Apply Config.
Verify¶
Log out and log back in as the new user. Confirm the section restrictions match what you set.
Add a UnifiedBX Manager User (AMI)¶
For programmatic AMI access — used by Sangoma Connect, dialer integrations, custom CRM popups.
Steps¶
- Go to System Admin → UnifiedBX Manager Users.
- Click + Add Manager.
- Fill in:
- Manager name — e.g.
crmpro_ami. - Manager secret — strong random string.
- Deny / Permit — restrict by source IP.
Permit: 10.0.0.0/8is common for LAN-only. - Read / Write — privilege classes:
system— server commandscall— call origination/controloriginate— only originating new callsagent— queue agent operationscdr— CDR accessdialplan— dialplan readsuser— user events
- For a CRM "click-to-call":
Read: call,user,Write: call,originateis typical. - DisplayConnects —
Yesshows the manager inmanager show users.
- Manager name — e.g.
- Click Submit.
- Click Apply Config.
Verify¶
asterisk -rx "manager show users"
The new manager should appear. Test the credentials from another box:
nc <unifiedbx-ip> 5038
# Then send:
# Action: Login
# Username: crmpro_ami
# Secret: <secret>
You should get Response: Success.
Common Issues¶
- Mixed up the two. Don't use a Manager User to log into the GUI — it won't work. Don't use an Administrator account in CRM AMI configs — also won't work.
- AMI port 5038 unreachable. Check System Admin → Firewall — AMI must be allowed from the integration's source IP. By default it's blocked from external.
- GUI login locked out. If you delete the only Full Admin, you're locked out. Recovery: SSH to the host and run
fwconsole userman addUser. - Permissions too narrow. AMI integrations often need both
callANDoriginateto dial out —originatealone won't let them control existing calls.