1. What is ZTP ?

ZTP (Zero Touch Provisioning) means that after a CPE device is powered on, it automatically contacts a cloud platform to obtain SIP account configuration information, allowing the device to operate without any local manual configuration.

All Flyingvoice POTS hardware can reach ZTP via VolaCloud in two ways:

  • Using VolaCloud as a redirect to the provisioning server (RPS)
  • Direct use of VolaCloud as a provisioning server

2. Use VolaCloud as RPS

Most popular UC platforms provide a provisioning server. For example, Netsapiens offers NDP (Netsapiens Device Provisioning Platform).

When creating a SIP account on the UC platform, users are usually prompted to select the device model and the MAC address associated with the account. The system then automatically generates the required configuration files for NDP.

When a Flyingvoice CPE powers on for the first time, it first contacts VolaCloud to obtain an initial configuration file. This initial configuration file may simply contain the NDP server URL, instructing the CPE to redirect to NDP to retrieve the SIP configuration.

In VolaCloud, downloading configuration files and assigning configuration files to devices in the Inventory are two separate actions. Therefore, when using VolaCloud as an RPS, it is not necessary to assign a unique initial configuration file to each device in the Inventory. All devices can share the same configuration file, since its sole purpose is to direct the CPE to the NDP URL, identical for all devices.

Customers can also choose to download the initial configuration file via the VolaCloud API and specify this file when adding devices to the inventory.

3. Use VolaCloud as the provisioning server

When ITSPs use open‑source UC platforms such as FreeSWITCH or Asterisk, they may find that no ready‑to‑use provisioning platform is available.

In this case, VolaCloud itself can be used directly as a provisioning server.

The operation method is similar to the previous section. The difference is that, in this scenario, each device requires its own complete configuration file.

If this operation is performed manually, it can be quite tedious. However, VolaCloud supports APIs, allowing SIP account information created in FreeSWITCH or Asterisk to be written directly into VolaCloud via API calls. This makes the provisioning process highly efficient and convenient.

For clients using older versions of Netsapiens NDP that do not yet support Flyingvoice CPE devices, this method can also be used to implement ZTP directly via VolaCloud.