Slider 2TryLearn MoreSlash your Phone bills - Slider Image

Use SIP trunks, WebRTC & Apps

Slash your Phone Bill by 80%

Configuring IP Phones

On this topic


Provisioning phones using Plug and Play (Cloud & On premise installs)

Provisioning Phones using RPS (Direct SIP/Stun)

Provisioning Legacy Phones: Cisco, Polycom & Aastra

See also


The “Phones” function enables you to simplify IP phone provisioning for the extensions you have created. Manual configuration of IP phones using their web interface is impractical and leads to many errors, drastically increasing the IP phone deployment time and making their ongoing management almost impossible.

Therefore 3CX requires you to use phone provisioning to instruct the phone to retrieve its configuration from the 3CX Phone System. Once you provision a phone, the phone automatically configures itself correctly and you can manage the phone centrally and remotely, without having to log in each phones web interface. Use the Phones function in the 3CX Management Console to:

  • View all the phones in the network, including their IP and MAC addresses.
  • View all 3CX Apps connected in softphone mode.
  • Check and upgrade the firmware version that the phone is running, see how here.
  • Remotely reboot and re-provision any or all of the phones.
  • Launch the phone’s admin interface.
  • Monitor security of extension password and PIN - weak extension passwords and PINs are the most common cause of security breaches.

3CX can provision phones via:

  • Plug and Play (PnP) - for phones on the local LAN or behind a 3CX SBC.
  • RPS server - for remote extensions using direct SIP/STUN.
  • Manual Provisioning URL - by entering the provisioning URL into the phone's’ web interface (applicable for local, remote and SBC extensions).
  • DHCP Option 66 - for legacy phones (from a previous PBX installation, e.g. Polycom, Cisco or Aastra) can be provisioned via DHCP for use in the local LAN only. Some limitations apply.

Provisioning phones using Plug and Play (Cloud & On premise installs)

Applicable to:

  • 3CX in the Cloud - Phones behind a SBC
  • 3CX on-premise - Phones on local LAN

Connecting a supported phone that is on the same LAN as 3CX or is connected behind a 3CX SBC, you can see the phone appear as an entry in BOLD in the “Phones” function. This means 3CX has detected a new phone on the network that you need to process.

Note: PnP provisioning requires that the 3CX Phone System runs on the default SIP port 5060 and that the IP phones reside on the same local LAN subnet as 3CX or behind an SBC. In these cases you must use DHCP 66 or manually configure the URL in the phones. See how for Snom, Htek, Grandstream, Fanvil and Yealink here.

To auto-provision phones using Plug and Play:

  1. Connecting the phone to the network, the phone sends a LAN multicast message, picked up by the 3CX Phone System. The same applies for phones connected via an SBC through a tunnel connection.
  2. The phone shows up as new in the Phones function in the 3CX Management Console, so you can assign it to an extension with Assign Ext or create a new one using Add Ext:
  • In the extension’s provisioning tab that opens, you can specify other configuration settings for the phone.
  • Leave “Provisioning Method” Mac Address default.
  • Select “Phone Display Language” and “Timezone” for the phone.
  1. Click OK to configure the phone sending a link to the configuration file with the settings you specified.

Provisioning Phones using RPS (Direct SIP/Stun)

Applicable to:

  • 3CX in the Cloud - for sites with 1 or 2 IP phones where a local SBC is overkill.
  • 3CX on-premise - for phones not in the local LAN.

Remote phones that are not behind a 3CX SBC must be configured via the 3CX RPS server with these steps from the Phones function in the 3CX Management Console:

  1. Select Add Phone and select the extension to associate this phone.
  2. Enter the MAC address of the phone - can be found on the underside label of the phone.
  3. Select the appropriate phone model from the drop down menu.

  1. In the Provisioning Method drop-down menu, select Direct SIP (STUN - Remote).
  2. Select “Phone Display Language” and “Timezone” for the phone.

  1. Click OK to create the provisioning files and publish the link to the RPS server. You can check the server Event Log if the RPS was successfully sent.
  2. Connect the phone to the network within 14 days.
  3. The phone boots up and requests a username and password: enter the corresponding extension number as username and the extension’s voicemail pin as password to provision automatically.

If you don’t want to use RPS, you can configure the phone(s) manually with the provisioning link from the Phone Provisioning tab in the extension’s configuration.

Provisioning Legacy Phones: Cisco, Polycom & Aastra

Applicable to:

  • 3CX in the Cloud - phones must be behind an SBC.
  • 3CX on-premise - for phones in the local LAN.

Cisco, Polycom and Aastra phones do not support Plug and Play nor secure HTTPS provisioning with a Let’s Encrypt Root CA. They can only be used on the local LAN or behind an SBC, provisioned as follows:

  1. Download the 3CX-tested firmware for the legacy phones.
  2. Factory reset your phones to ensure that old settings do not conflict with the new configuration. See how for Aastra, Cisco, Cisco SPA and Polycom SoundPoint / SoundStation.

  1. Add the phone to an extension by clicking Add Phone in the “Phones” function or clicking “Add” from the extension’s “Phone Provisioning” tab.
  2. Select your phone model and enter its MAC address to go to the provisioning page.

IMPORTANT: Take note of the Provisioning Link shown below the drop down.

  1. Select Phone Display Language and Timezone for the phone.
  2. Leave Phone Web Page Password to the default.
  3. Click OK to add the phone to the extension.
  4. Setup the phone to retrieve its configuration from the 3CX provisioning folder. Use DHCP option 66 or configure the phone(s) manually via their web interface with the 3CX provisioning link. Learn how to use DHCP option 66 or follow the guides to manually configure Aastra, Cisco SPA and Polycom phones. Cisco 7940/7960 phones must be provisioned using TFTP and DHCP option 66.

Detailed step by step guides for legacy phones:

See also

Free for up to 1 year! Select preferred deployment:


for Linux on a $200 appliance or as a VM

Get the ISO


for Windows as a VM

Download the setup file

On the cloud

In your Google, Amazon, Azure account

Take the PBX Express