Security
Business telephony with a clear boundary between service and administration.
Discuss your deploymentA phone system processes operationally sensitive configuration, history, contacts and potentially recordings. PBXCenter separates roles, limits employee access and guides administrators through network, backup and retention settings.
Identity and roles
Employees do not receive the keys to the entire system
Network and change
Domain, TLS and firewall belong in the product workflow
Data and continuity
Recordings, retention and backups have a controlled lifecycle
Identity and roles
Employees do not receive the keys to the entire system
Administrators and employees use separate product surfaces. Employees access the phone, queue, contacts and notes, but not provider, network, device or maintenance configuration.
- Administrator permissions separate configuration, calls, devices and maintenance.
- WebRTC sessions deliver short-lived data instead of reusable employee SIP passwords.
- Production should contain no default passwords or test accounts.
Network and change
Domain, TLS and firewall belong in the product workflow
PBXCenter guides domain and TLS, trusted networks and firewall policy. Administrators preview risk and track operations instead of editing server configuration manually.
- Outbound rules can restrict prefixes, countries and call concurrency.
- Signed HTTPS webhooks reduce event impersonation risk.
- Diagnostics show service and connectivity health without exposing secrets to staff.
Data and continuity
Recordings, retention and backups have a controlled lifecycle
Recordings play through a protected API and permission governs access. Administrators set retention, create backups, export protected packages and queue a controlled restore.
- The public site never retrieves customer configuration, calls or recordings.
- Backup and restore live in the panel, not in a hidden server command.
- Updates use prepared packages and require a maintenance permission.
FAQ
Direct answers before the conversation.
Does PBXCenter encrypt phone traffic?
TLS and WebRTC readiness are part of environment configuration, but transmission also depends on the provider, devices and network. Those dependencies are verified in deployment scope.
Who can play call recordings?
Only an account with the appropriate administrator permission. Employees do not automatically receive access to the recording library or server storage paths.
Does the public website connect to customer systems?
No. The marketing site is a separate surface and never loads customer configuration, employee accounts, call history or recordings.
Next steps
Move from answers to the right decision.
Deployment for your company
Address security before the first production call.
Deployment analysis defines roles, recording access, network, devices, backups and maintenance before configuration reaches production.