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 achieve ZTP through VolaCloud in two ways:

• Using VolaCloud as a Redirection to Provision Server (RPS)
• Using VolaCloud directly as the Provision Server

2.Using VolaCloud as an RPS

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

When creating a SIP account on the UC platform, users are typically prompted to select the device model and 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 can simply contain the URL of the NDP server, instructing the CPE to redirect to NDP to retrieve the SIP configuration.

In VolaCloud, uploading configuration files and assigning configuration files to devices in the Inventory are two separate actions. Therefore, when using VolaCloud as an RPS, there is no need to assign a unique initial configuration file to every device in the Inventory. All devices can share the same configuration file, since its only purpose is to direct the CPE to the NDP URL, which is identical for all devices.

Customers can also choose to upload the initial configuration file through the VolaCloud API and specify this configuration file when adding devices into the Inventory.

3.Using VolaCloud as the Provision Server

When ITSPs use open-source UC platforms such as FreeSWITCH or Asterisk, they may find that there is no ready-made Provision platform available.

In this case, VolaCloud itself can be used directly as the Provision 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 done manually, this process can be quite cumbersome. However, VolaCloud supports APIs, allowing SIP account information created in FreeSWITCH or Asterisk to be written directly into VolaCloud through API calls. This makes the provisioning process highly efficient and convenient.

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