The guide below outlines the provisioning methods which shall be used for Supported IP Phones only. For legacy phones follow the instructions defined with the provisioning guide itself.

Supported IP phones have a vast amount of possible provisioning methods which are depended on the phone’s locality and the configuration on which 3CX is running. Choose the matching setup of your installation and see which provisioning method should be used:

Setup 1: 3CX on SIP Port 5060

All below defined phone’s localities are in relation to a 3CX Phone System running on SIP port equal 5060.

Phone Locality: Same Subnet as PBX

In this setup combination the phone shall be provisioned via P’n’P method as the multicast messages can be intercepted by the 3CX Phone System.

Phone Locality: Other Subnet as PBX

In this setup combination the phone must be provisioned via the manual provisioning method as multicast messages will not traverse via router boards making it for 3CX impossible to intercept those announcements.

Phone Locality: On VPNed Network (Lan2Lan)

Refer to “Phone Locality: Other Subnet as PBX” as same rules apply.

Phone Locality: Connected via the Internet

In this setup the phone will make use of RPS provisioning given the bare minimum firmware (as defined in the main provisioning guides) is installed and the phone is in factory default!

Phone Locality: Connected via a 3CX SBC

In this setup the SBC acts as multicast forwarder to the 3CX and enables the provisioning via P’n’P method for all the remote phones behind this SBC.

Setup 2: 3CX on alternated SIP Port

All below defined phone’s localities are in relation to a 3CX Phone System running NOT on SIP port equal 5060.

Phone Locality: Same Subnet as PBX

In this setup combination the phone must be provisioned via the manual provisioning method as multicast messages are directed by the IP phone, always against the port 5060, where in this case the 3CX is not listening anymore on, making it for the PBX impossible to intercept those announcements by the phone.

Phone Locality: Other Subnet as PBX

In this setup combination the phone must be provisioned via the manual provisioning method as multicast messages will not traverse via router boards plus the same rules of “Phone Locality: Same Subnet as PBX” apply on top of it.

Phone Locality: On VPNed Network (Lan2Lan)

Refer to “Phone Locality: Other Subnet as PBX” as same rules apply.

Phone Locality: Connected via the Internet

In this setup the phone will make use of RPS provisioning given the bare minimum firmware, as defined in the main provisioning guides, is installed and the phone is in factory default!

Phone Locality: Connected via a 3CX SBC

In this setup the SBC acts as multicast forwarder to the 3CX and enabled the provisioning via P’n’P method for all the remote phones behind this SBC. The SBC is also able to redirect the multicast messages to the alternated SIP port of the pbx which is known to the SBC due to it’s configuration.