Basic Configuration

You have two options to get your phone to be provisioned:

  • Set up a DHCP server
  • Tell manually each phone where to get the provisioning informations

You may want to manually configure the phones if you are only trying XiVO or if your network configuration does not allow the phones to access the XiVO DHCP server.

You may want to set up a DHCP server if you have a significant number of phones to connect, as no manual intervention will be required on each phone.

Configuring the DHCP Server

XiVO includes a DHCP server that facilitate the auto-provisioning of telephony devices. It is not activated by default.

There’s a few things to know about the peculiarities of the included DHCP server:

This means that if your phones are on the same broadcast domain than your computers, and you would like the DHCP server on your XiVO to handle both your phones and your computers, that won’t do it.

The DHCP server is configured via the Configuration ‣ Network ‣ DHCP page:


Configuration ‣ Network ‣ DHCP

Activate/desactivate the DHCP server.
Pool start
The lower IP address which will be assigned dynamically. This address should be in the VoIP subnet. Example:
Pool end
The higher IP address which will be assigned dynamically. This address should be in the VoIP subnet. Example:
Extra network interfaces

A list of space-separated network interface name. Example: eth0.

Useful if you have done some custom configuration in the /etc/dhcp/dhcpd_extra.conf file. You need to explicitly specify the additional interfaces the DHCP server should listen on.

After saving your modifications, you need to click on Apply system configuration for them to be applied.

Installing provd Plugins

The installation and management of provd plugins is done via the Configuration ‣ Provisioning ‣ Plugin page:


Configuration ‣ Provisioning ‣ Plugin

The page shows the list of both the installed and installable plugins. You can see if a plugin is installed or not by looking at the Action column.

Here’s the list of other things that can be done from this page:

  • update the list of installable plugins, by clicking on the top right icon. On a fresh XiVO installation, this is the first thing to do.
  • install a new plugin
  • upgrade an installed plugin
  • uninstall an installed plugin
  • edit an installed plugin, i.e. install/uninstall optional files that are specific to each plugin, like firmware or language files

After installing a new plugin, you are automatically redirected to its edit page. You can then download and install optional files specific to the plugin. You are strongly advised to install firmware and language files for the phones you’ll use although it’s often not a strict requirement for the phones to work correctly.


If you uninstall a plugin that is used by some of your devices, they will be left in an unconfigured state and won’t be associated to another plugin automatically.

The search box at the top comes in handy when you want to find which plugin to install for your device. For example, if you have a Cisco SPA508G, enter “508” in the search box and you should see there’s 1 plugin compatible with it.


If your device has a number in its model name, you should use only the number as the search keyword since this is what usually gives the best results.

It’s possible there will be more than 1 plugin compatible with a given device. In these cases, the difference between the two plugins is usually just the firmware version the plugins target. If you are unsure about which version you should install, you should look for more information on the vendor website.

It’s good practice to only install the plugins you need and no more.

Alternative plugins repository

By default, the list of plugins available for installation are the stable plugins for the officially supported devices.

This can be changed in the Configuration ‣ Provisioning ‣ General page, by setting the URL field to one of the following value:

  • supported devices “stable” repository (default)
  • – officially supported devices “testing” repository
  • – officially supported devices “archive” repository
  • supported devices “stable” repository
  • – community supported devices “testing” repository

The difference between the stable and testing repositories is that the latter might contain plugins that are not working properly or are still in developement.

The archive repository contains plugins that were once in the stable repository.

After setting a new URL, you must refresh the list of installable plugins by clicking the update icon of the Configuration ‣ Provisioning ‣ Plugin page.

How to manually tell the phones to get their configuration

If you have set up a DHCP server on XiVO and the phones can access it, you can skip this section.

The according provisioning plugins must be installed.


On the web interface of your phone, go to Advanced settings ‣ Configuration server, and enter the following settings:



On the phone, go to Menu ‣ Settings ‣ Advanced ‣ Admin Settings ‣ Network configuration ‣ Server Menu and enter the following settings:

  • Server type: HTTP
  • Server address: http://<XiVO IP address>:8667/000000000000.cfg

Then save and reboot the phone.


On the web interface of your phone, go to Setup ‣ Advanced ‣ Update and enter the following settings:


Autoprovisioning a Device

Once you have installed the proper provd plugins for your devices and setup correctly your DHCP server, you can then connect your devices to your network.

But first, go to Services ‣ IPBX ‣ Devices page. You will then see that no devices are currently known by your XiVO:


You can then power on your devices on your LAN. For example, after you power on an Aastra 6731i and give it the time to boot and maybe upgrade its firmware, you should then see the phone having its first line configured as ‘autoprov’, and if you refresh the devices page, you should see that your XiVO now knows about your 6731i:


You can then dial from your Aastra 6731i the provisioning code associated to a line of one of your user. You will hear a prompt thanking you and your device should then reboot in the next few seconds. Once the device has rebooted, it will then be properly configured for your user to use it. And also, if you update the device page, you’ll see that the icon next to your device has now passed to green:


Resetting a Device

From the Device List in the Webi

To remove a phone from XiVO or enable a device to be used for another user there are two different possibilities :

  • click on the reset to autoprov button on the web interface

The phone will restarts and display autoprov, ready to be used for another user.

From the User Form in the Webi

Device With one User Only Associated

Edit the user associated to the device and put the device field to null.

  • click on the Save button on the web interface

The phone doesn’t restart and the phone is in autoprov mode in the device list.

You can synchronize the device to reboot it.

Device with Several Users Associated

Edit the primary user associated to the terminal (one with the line 1) and put the device field to null.

  • click on the Save button on the web interface

The primary line of the phone has been removed, so the device will lose its funckeys associated to primary user but there others lines associated to the device will stay provisionned.

The phone doesn’t restart and the phone is in autoprov mode in the device list.

You can synchronize the device for reboot it.

From a Device

  • Dial *guest (*48378) on the phone dialpad followed by xivo (9486) as a password

The phone restarts and display autoprov, ready to be used for another user.