To be able to provision SCCP phones you should :
Then install a plugin for SCCP Phone
At this point you should have a fully functional DHCP server that provides IP address to your phones. Depending on what type of CISCO phone you have, you need to install the plugin sccp-legacy, sccp-9.4 or both.
Please refer to the Provisioning page for more information on how to install CISCO firmwares.
Once your plugin is installed, you’ll be able to edit which firmwares and locales you need. If you are unsure, you can choose all without any problem.
Now if you connect your first SCCP phone, you should be able to see it with
When connecting a second SCCP phone, the device will be automatically detected as well.
Starting from Wazo 18.07, an SCCP device can be associated to a user by entering the user’s provisioning code directly from the SCCP device while in autoprov mode.
There’s two settings in
GET /asterisk/sccp/general influencing the auto-provisioning behaviour:
guestoption must be enabled to allow SCCP devices to connect to the server and allow a provisioning code from being dialed from them. Disabling this option can provide some additional security if your Wazo is in an hostile environment, at the cost of making auto-provisioning support unavailable for SCCP devices.
max_guestsoption limits the number of SCCP devices that can simultaneously connect to the server in autoprov mode. You should set this value to the maximum number of SCCP devices you expect to be in autoprov mode at any moment, unless your Wazo is in an hostile environment, where you should probably set it to a fairly low value.
SCCP General Settings¶
Review SCCP general settings:
The last step is to create a user with a SCCP line.
Creating a user with a SCCP line:
Congratulations ! Your SCCP phone is now ready to be called !
With SCCP phones, the only destination type of function keys that can be configured is
SCCP Phones support directmedia (direct RTP).
|Autoanswer (custom dialplan)||Yes|
|Multi-instance per line||Yes|
|Message waiting indication||Yes|
|Music on hold||Yes|
|Context per line||Yes|
|Resync device configuration||Yes|
|Do not disturb (DND)||Yes|
|Connected line ID||Yes|
|Multi line||Not yet|
|NAT traversal||Not yet|
|Type of Service (TOS)||Manual|
|Device type||Supported||Firmware version||Timezone aware|
Models not listed in the table above won’t be able to connect to Asterisk at all. Models listed as “Testing” are not yet officially supported in Wazo: use them at your own risk.
The “Timezone aware” column indicates if the device supports the timezone tag in its configuration file, i.e. in the file that the device request to the provisioning server when it boots. If you have devices that don’t support the timezone tag and these devices are in a different timezone than the one of the Wazo, you can look at the issue #5161 for a potential solution.