Cisco IP Phone and ATA Setup Guide
SIPSTACK Nova PBX can generate the configuration for Cisco SPA500 desk phones, Cisco Multiplatform (MPP, also called 3PCC) desk phones, and Cisco analogue telephone adapters (ATAs). You register the device in Switchboard, point it at your organization’s provisioning URL, and it downloads its lines, dial plan and keys.
Every Cisco model is marked Beta in the Switchboard model picker and on this page.
Firmware matters. 6800, 7800 and 8800 phones must run Cisco’s Multiplatform (MPP / 3PCC) firmware. The same hardware running Cisco’s enterprise firmware for Unified Communications Manager does not read this configuration. Converting a phone to MPP firmware is done with Cisco, not in Switchboard.
Supported Models
Section titled “Supported Models”| Model | Type | Lines | Line keys | Status |
|---|---|---|---|---|
| SPA501G | Desk phone | 8 | 8 | Beta (discontinued by vendor) |
| SPA502G | Desk phone | 1 | 0 | Beta (discontinued by vendor) |
| SPA504G | Desk phone | 4 | 4 | Beta (discontinued by vendor) |
| SPA508G | Desk phone | 8 | 8 | Beta (discontinued by vendor) |
| SPA509G | Desk phone | 12 | 12 | Beta (discontinued by vendor) |
| SPA512G | Desk phone | 1 | 0 | Beta (discontinued by vendor) |
| SPA514G | Desk phone | 4 | 4 | Beta (discontinued by vendor) |
| SPA525G2 | Desk phone | 5 | 5 | Beta (discontinued by vendor) |
| CP-6821 | Desk phone (MPP) | 2 | 2 | Beta |
| CP-6841 | Desk phone (MPP) | 4 | 4 | Beta |
| CP-6851 | Desk phone (MPP) | 4 | 4 | Beta |
| CP-6861 | Desk phone (MPP) | 4 | 4 | Beta |
| CP-6871 | Desk phone (MPP) | 6 | 6 | Beta |
| CP-7811 | Desk phone (MPP) | 1 | 0 | Beta |
| CP-7821 | Desk phone (MPP) | 2 | 2 | Beta |
| CP-7841 | Desk phone (MPP) | 4 | 4 | Beta |
| CP-7861 | Desk phone (MPP) | 16 | 16 | Beta |
| CP-7832 | Conference phone (MPP) | 1 | — | Beta |
| CP-8811 | Desk phone (MPP) | 10 | 10 | Beta |
| CP-8841 | Desk phone (MPP) | 10 | 10 | Beta |
| CP-8845 | Desk phone (MPP) | 10 | 10 | Beta |
| CP-8851 | Desk phone (MPP) | 10 | 10 | Beta |
| CP-8861 | Desk phone (MPP) | 10 | 10 | Beta |
| CP-8865 | Desk phone (MPP) | 10 | 10 | Beta |
| SPA112 | ATA (2 phone ports) | 2 | — | Beta |
| SPA122 | ATA (2 phone ports) | 2 | — | Beta |
| ATA191 | ATA (2 phone ports) | 2 | — | Beta |
| ATA192 | ATA (2 phone ports) | 2 | — | Beta |
Cisco ended sales and support of the SPA500 phones years ago, and they no longer get firmware or security updates. They can still be provisioned, but plan to replace them.
Models that are not in this table, such as the SPA300 series and the Cisco 9800 series, are not in the Nova PBX catalog. Set them up by hand with the extension’s SIP credentials (see Manual SIP Registration).
Before You Start: Your Provisioning URL and PIN
Section titled “Before You Start: Your Provisioning URL and PIN”Every Nova PBX organization has one provisioning URL and one provisioning PIN that all of its devices share:
https://<slug>:<PIN>@cfg.sipstack.com/<slug>/<slug>is your tenant slug (also the username).<PIN>is your provisioning PIN — 8 digits for organizations set up since September 2026.
Both live in Switchboard → Nova PBX → System → PBX Settings → Provisioning Access. The URL is shown with the PIN masked; the Regenerate PIN button reveals a new PIN, once. The PIN is shown once when generated. Lost it? Rotate it in Provisioning Access — devices keep working on the old PIN for 24 hours.
There is no per-device password and nothing to copy from an individual device’s page: the same URL provisions every device in your organization.
Step 1: Register the Device in Switchboard
Section titled “Step 1: Register the Device in Switchboard”- Log in to Switchboard.
- Go to Nova PBX → Devices → Devices and click Register device. If the page asks you to generate your provisioning PIN first, do that in PBX Settings → Provisioning Access — devices cannot be registered until the PIN has been generated.
- Enter the device’s MAC address from the label on the bottom of the phone or adapter.
- Pick Cisco and the model (it shows a Beta badge), then click Register device.
- Assign an extension to line 1. On an ATA, line 1 is phone port 1 and line 2 is phone port 2. On a phone, add any BLF or speed-dial keys you want in the key editor.
- Click Apply Changes. Applying publishes the device’s configuration to the provisioning server — until you apply, the server has nothing to hand the device.
Step 2: Set the Profile Rule
Section titled “Step 2: Set the Profile Rule”Cisco devices fetch their configuration from the URL in their Profile Rule field. The organization URL above ends at your folder; the Profile Rule also needs the file name, so add $MA.xml to the end. The device replaces $MA with its own MAC address.
https://<slug>:<PIN>@cfg.sipstack.com/<slug>/$MA.xml- Find the device’s IP address. On a phone, open Settings (or Setup on an SPA) → Network / Status. On an ATA, dial
****from an attached analogue phone and choose option110. - Open
http://{device-ip}in a browser and sign in as admin. On SPA phones and SPA1xx adapters, click Admin Login, then Advanced. - Go to Voice → Provisioning.
- Set Profile Rule to the value above, with your slug and PIN filled in.
- Click Submit All Changes. The device restarts, downloads its configuration and registers.
Your DHCP server can also hand the device its provisioning URL (option 160, or option 66 on some devices). The organization URL in DHCP has no file name on the end, so for Cisco devices it is more reliable to set the Profile Rule by hand as above.
SIPSTACK never writes the Profile Rule back into the configuration it sends, so the rule you entered (with your PIN in it) stays on the device.
What SIPSTACK Configures
Section titled “What SIPSTACK Configures”- Lines. Every line the model has: extension credentials, the Nova SIP server, registration. A line with no extension assigned is turned off and its credentials are cleared.
- Dial plan. A local dial plan that lets every Nova star code through, including paging (
*80+ page group), intercom (*81+ extension), park retrieve (*85), directed pickup (*87+ extension), voicemail (*97,*98), 3- and 4-digit extensions, North American numbers,011international, and 911, 988 and 112. Each of 911, 988 and 112 is sent the moment you finish dialling it. - Paging and intercom auto-answer (phones). Pages (
*80) and intercom calls (*81) are answered hands-free. - BLF keys (phones with line keys). A BLF key shows the watched extension’s state, calls it when pressed, and picks up its ringing call (Nova
*87). - Speed-dial and feature keys (phones). Speed dial, voicemail, group pickup (
*88), intercom, paging, Do Not Disturb and call forward keys dial the matching number or Nova code. - Voicemail. The voicemail button dials
*97. MPP phones also subscribe for the message-waiting light. - Codecs from your PBX settings: up to three for phones, G.711 only for ATAs.
- Time zone and NTP server, when your organization or device has a time zone chosen. The North American daylight-saving rule is set for North American zones.
- Web passwords for the admin and user logins, when your organization has them set.
- Resync. The device checks for new configuration every hour. SIPSTACK also sends Cisco devices a “reprovision” signal when you click Reprovision on the device page. Support for this brand is in Beta, so the signal is not yet confirmed on every model: if the device has not picked up your change after a minute, reboot it.
What SIPSTACK Does Not Configure
Section titled “What SIPSTACK Does Not Configure”- The Profile Rule (see above) — it stays as you entered it.
- Park keys. A park key is skipped and Switchboard shows a warning. Park calls by transferring them to the park extension instead.
- Expansion modules (Cisco KEM, SPA500S). Keys on a module are skipped with a warning.
- Fax settings on the ATAs. SIPSTACK writes no fax (T.38) settings to Cisco adapters; the adapter keeps its own.
- Message-waiting and transport settings on the ATAs, wideband codecs on the ATAs, and the ATAs’ web passwords. These are named differently on each adapter model, so the adapter keeps its own values.
- Firmware. SIPSTACK does not update Cisco firmware unless you pin a firmware version for the model in Switchboard, and only where its firmware catalog lists one.
- Anything else in the device’s web UI keeps the value it already has.
Manual SIP Registration (Fallback)
Section titled “Manual SIP Registration (Fallback)”For a Cisco model that is not in the catalog, enter the extension’s SIP credentials by hand. You get registration only — no keys, no dial plan and no updates from Switchboard.
- In Switchboard, open Nova PBX → Extensions → [extension] and copy the values on the SIP Auth tab.
- In the device’s web UI (Admin Login → Advanced), open the Ext 1 tab (or Line 1 on an ATA).
- Set Line Enable to Yes. Under Proxy and Registration, set Proxy to the SIP server and Register to Yes.
- Under Subscriber Information, set Display Name, User ID (the SIP username), Password, and Auth ID (the SIP username again, with Use Auth ID set to Yes).
- Click Submit All Changes.
Factory Reset
Section titled “Factory Reset”Reset a device that was used with another system before you provision it, so old settings don’t linger.
- SPA500 phones: press Setup, dial
73738(RESET) and press1to confirm. - MPP phones: unplug the phone, hold
#while you plug it back in, release#when the line-key lights turn on, then dial123456789*0#. - SPA112 / SPA122 / ATA19x: hold the RESET button on the adapter for at least 10 seconds.
After a reset, enter the Profile Rule again.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Likely cause | Fix |
|---|---|---|
| Line shows unregistered | The device has no configuration yet: MAC not registered, no extension on line 1, or changes not applied | Check the MAC in Nova PBX → Devices, assign an extension to line 1, click Apply Changes, then reboot the device |
Provisioning fails with 404 | The Profile Rule has no file name, or the MAC registered in Switchboard is wrong | End the Profile Rule with $MA.xml; compare the MAC with the label on the device |
Provisioning fails with 401 | Wrong slug or PIN in the Profile Rule | Compare with PBX Settings → Provisioning Access; after a rotation the previous PIN stops working 24 hours later |
| Provisioning fails for every device at once | 100 failed attempts within an hour paused provisioning for your organization | Correct the PIN, wait for the hour to pass, then reboot one device before the rest |
| Registration fails, then the device can’t reach SIPSTACK at all for a while | The device is registering to the wrong SIP server or domain, often a value left over from a previous provider. Repeated failed registrations from your network can trigger a temporary IP block | The SIP server must be your organization’s SIP server exactly as shown on the extension’s SIP Auth tab. Factory reset the device so the provisioned value is used, wait for the block to clear, then try again. Contact support if it continues |
| A star code or page is dialled before you finish | The device is running an old dial plan | Click Apply Changes, then Reprovision (or reboot the device) |
| Calls connect but there is no audio | SIP ALG or NAT on your router | Turn off SIP ALG; see Network & Firewall |
For additional support, contact SIPSTACK at https://www.sipstack.com/contact.