Know the Device Provisioning Flow

Module: Deskphone

Let's learn the device provisioning flow in VoiceStack.

1. Device Requests Provisioning Link

Initiated By: Device

Sent To: Remote Provisioning Server (RPS)

Explanation: When the device is turned on for the first time or reset to factory settings, it needs to know where to get its configuration.
So, it automatically contacts the Remote Provisioning Server (RPS) and sends its unique identifiers, such as its MAC address and serial number.
The RPS acts as a central server that helps devices locate their correct provisioning servers.
The main goal here is to ask: “Where can I find my setup files?”

2. RPS Responds with Provisioning Server Link

Initiated By: Remote Provisioning Server
Sent To: Device

Explanation: The RPS checks the device's identity (MAC/serial number) and determines which provisioning server it should talk to; this could vary based on client, region, or device model. It sends back a URL (web link) to the appropriate Provisioning Server, where the device can continue the setup process.

3. Device Requests Boot File

Initiated By: Device
Sent To: Provisioning Server

Explanation: Now that the device has the provisioning server’s URL, it connects to that server and requests a BootFile. The BootFile is a basic configuration file that helps the device understand its role and how to proceed with the full setup.

It may include:

• Device model information

• Initial settings

• Links to more detailed configuration files

4. Provisioning Server Sends Boot File

Initiated By: Provisioning Server
Sent To: Device

Explanation: The provisioning server responds by sending the requested BootFile.
This file may include:

• User type (standard or hot-desking)

• References to more detailed config files like ACC.cfg (account) and BTN.cfg (buttons). The BootFile lays the foundation for full configuration.

5. Device Requests Full Configuration Files

Initiated By: Device
Sent To: Provisioning Server

Explanation: Based on the instructions in the BootFile, the device now asks for the detailed configuration files:

• ACC.cfg – Contains SIP account credentials and call server settings

• BTN.cfg – Defines how phone buttons are mapped (e.g., line keys, transfer, voicemail)

These files are essential for user-specific setup and call behavior.

6. Provisioning Server Sends Configuration Files

Initiated By: Provisioning Server
Sent To: Device

Explanation: The server sends all the requested configuration files.
The device reads and applies the settings, which may include:

• SIP account info (username, password, server IP).

• Button layout and user preferences.

• Call routing rules and display settings. This completes the provisioning setup on the device.

7. Device Registers with Asterisk PBX

Initiated By: Device
Sent To: Asterisk PBX

Explanation: After configuration, the device reaches out to the Asterisk PBX system using the SIP credentials it received. The goal is to register as an active endpoint in the VoIP network. Once registered successfully, the device is fully ready to make and receive calls using the configured SIP account.

Support / Contact

Need further help? Contact [e-mail]  or call 407-833-6436.