Glossary / Deployment and Administration
⚙️ Deployment and Administration covers everything involved in setting up, configuring, and managing a PBX system on a day-to-day basis. From auto-provisioning phones to planning for disaster recovery, this section contains 22 terms that help you understand how a Cloud PBX is installed, maintained, and kept running.
On this page: Provisioning · Auto-Provisioning/Zero-Touch Provisioning · Provisioning Server · DHCP · TFTP/HTTP/HTTPS Provisioning · Firmware · SIP Profile · Dial Plan (Configuration) · Call Flow · Extension Mapping · Trunk Configuration · Inbound Route · Outbound Route · Multi-Site PBX · Hot Desking · Failover/Redundancy · High Availability · Disaster Recovery · Backup and Restore · Web Admin Portal · User Portal · Tenant
Provisioning
The process of setting up and configuring a phone or PBX device so it is ready to make and receive calls. Provisioning includes assigning an extension number, setting the SIP server address, configuring codecs, and loading any custom settings. It can be done manually (typing settings into the phone's web interface) or automatically through a provisioning server.
Related: Auto-Provisioning/Zero-Touch Provisioning · SIP Profile · SIP Protocol
Auto-Provisioning / Zero-Touch Provisioning
A method that configures phones automatically without human intervention. When a new phone is plugged into the network, it contacts a provisioning server, downloads its configuration file, and is ready to use within minutes. This saves IT teams significant time, especially when deploying dozens or hundreds of phones across multiple offices.
Related: Provisioning Server · DHCP · Firmware
Provisioning Server
A central server that stores configuration files for all phones in a PBX deployment. When a phone boots up or is reset, it connects to this server to download its settings. The server can push updates to phones remotely, such as changing a dial plan or updating firmware. Cloud PBX providers typically host the provisioning server for you.
Related: Provisioning · TFTP/HTTP/HTTPS Provisioning
DHCP (Dynamic Host Configuration Protocol)
A network protocol that automatically assigns IP addresses and other network settings to devices when they connect. In PBX deployments, DHCP can also tell a phone where to find the provisioning server. A special DHCP option (often Option 66) provides the server URL so the phone knows where to download its configuration.
Related: Auto-Provisioning/Zero-Touch Provisioning · QoS
TFTP/HTTP/HTTPS Provisioning
The transport protocols used to deliver configuration files from a provisioning server to phones. TFTP (Trivial File Transfer Protocol) is the oldest and simplest method but has no encryption. HTTP is faster and more flexible. HTTPS adds encryption, protecting configuration data (including passwords) during transfer. Most modern deployments use HTTPS.
Related: Provisioning Server · Firmware
Firmware
The built-in software that runs on a phone or PBX appliance. Firmware controls everything from the screen display to how the device processes calls. Manufacturers release firmware updates to fix bugs, patch security vulnerabilities, and add new features. A provisioning server can push firmware updates to all phones automatically.
Related: Auto-Provisioning/Zero-Touch Provisioning · Provisioning Server
SIP Profile
A set of SIP account settings stored on a phone or PBX. A SIP profile typically includes the SIP server address, username, password, display name, and codec preferences. Most desk phones support multiple SIP profiles, allowing one phone to register with more than one PBX or provider at the same time.
Related: Provisioning · SIP Registration · Codec
Dial Plan (Configuration)
A set of rules that tells the PBX how to interpret and route dialled numbers. The dial plan defines patterns: for example, numbers starting with 0 go out through the SIP trunk, numbers starting with 1 reach internal extensions, and 112 always routes to emergency services. A well-designed dial plan prevents misdialled calls and enforces calling policies.
Related: Call Flow · Inbound Route · Outbound Route
Call Flow
The path a call takes from the moment it arrives at the PBX until it reaches its destination. A call flow might include steps like: ring the reception, if no answer after 15 seconds forward to a queue, if the queue is full play a voicemail greeting. Administrators design call flows using visual editors or configuration files.
Related: Dial Plan (Configuration) · IVR · Call Queue
Extension Mapping
The assignment of internal extension numbers to users, devices, or services within the PBX. For example, extension 100 might be the reception desk, 200-299 could be the sales team, and 900 could be the main IVR menu. A clear extension mapping plan makes it easier for staff to transfer calls and for IT to manage the system.
Related: DID / DDI · Dial Plan (Configuration)
Trunk Configuration
The settings that connect your PBX to an external SIP trunk provider. Trunk configuration includes the provider's SIP server address, authentication method (IP or credentials), codec preferences, and the number of allowed concurrent calls. Incorrect trunk configuration is one of the most common causes of failed outbound calls.
Related: SIP Trunk · IP Authentication
Inbound Route
A rule that tells the PBX what to do with an incoming call based on the dialled number (DID). For example, calls to +352 2634 0100 might go to the sales queue, while calls to +352 2634 0101 go directly to the CEO's extension. Inbound routes are the first decision point for every external call arriving at your PBX.
Related: Dial Plan (Configuration) · Call Flow · DID / DDI
Outbound Route
A rule that determines which SIP trunk the PBX uses for an outgoing call. You might route local calls through a cheap local trunk and international calls through a specialised international provider. Outbound routes can also block certain number patterns (such as premium-rate numbers) to control costs.
Related: Trunk Configuration · Dial Plan (Configuration) · SIP Trunk
Multi-Site PBX
A single PBX system that serves multiple office locations. With a Cloud PBX, all sites connect to the same central system over the internet. Staff at different offices can call each other using short extension numbers, transfer calls between sites, and share a single reception number. This eliminates the need for separate phone systems at each location.
Related: Cloud PBX · Fixed Mobile Convergence
Hot Desking
A feature that allows any user to log into any phone in the office and use it as their own. The phone loads that user's extension, voicemail, speed dials, and settings from the PBX. When they log out, the phone reverts to its default state. Hot desking is common in shared workspaces, call centres, and offices where employees move between desks.
Related: Provisioning · User Portal · Softphone
Failover / Redundancy
A backup mechanism that keeps your phone system running if the primary system fails. If the main PBX server goes down, calls are automatically redirected to a secondary server, a mobile number, or a voicemail system. Failover can also apply to internet connections: if your primary link fails, calls switch to a backup connection.
Related: High Availability · Disaster Recovery · Trunk Group
High Availability (HA)
A system design that minimises downtime by running two or more PBX servers in parallel. If one server fails, the other takes over instantly with no interruption to calls. High availability setups are common in Cloud PBX platforms where the provider manages the redundant infrastructure. The goal is to achieve 99.99% uptime or better.
Related: Failover/Redundancy · Geo-Redundancy · Disaster Recovery
Disaster Recovery
A plan and set of tools for restoring your phone system after a major failure, such as a data centre outage, fire, or cyberattack. Disaster recovery includes regular backups, off-site backup storage, documented restoration procedures, and defined recovery time objectives (how quickly the system must be back online).
Related: Backup and Restore · High Availability · Failover/Redundancy
Backup and Restore
The process of saving your PBX configuration, call data, voicemails, and recordings so they can be recovered if something goes wrong. Backups should be automated, stored off-site, and tested regularly. A good backup includes the dial plan, extension mappings, user settings, IVR menus, and call recordings.
Related: Disaster Recovery · Web Admin Portal
Web Admin Portal
A browser-based interface that administrators use to manage the PBX. From the portal, admins can add or remove users, configure call flows, set up trunks, view call logs, and monitor system health. Cloud PBX platforms always include a web admin portal because there is no physical hardware to access.
Related: User Portal · Tenant
User Portal
A simplified web interface for individual users (not administrators). Through the user portal, employees can check their voicemail, update their presence status, configure call forwarding rules, view their own call history, and manage personal speed dials. The user portal gives staff control over their own phone settings without needing to contact IT.
Related: Web Admin Portal · Hot Desking · Presence
Tenant
An isolated instance within a multi-tenant PBX platform. Each tenant (typically a separate company or department) has its own users, extensions, dial plans, and settings. Tenants cannot see or interact with each other's data. Cloud PBX providers use multi-tenant architecture to serve many customers from the same infrastructure while keeping each customer's data private.
Related: Web Admin Portal · Cloud PBX · Data Residency
Related Sections
🔗 SIP Protocol — How SIP messages control calls and registration
📡 SIP Trunking — Connecting your PBX to the outside phone network
📞 Core Concepts — PSTN, ISDN, DID, and other foundational terms
🎧 Devices and Hardware — Desk phones, softphones, headsets, and hardware
📅 Ready to explore Cloud PBX for your business?
Start with the provider comparisons or feature guides. If you want expert help, book a short call with a consultant.
Made with Bullet