Follow the workflow to register your phones to a BroadWorks platform.

1

Download the CPE Kit from cisco.com. To download the latest CPE kits, go to this URL: https://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/broadworks/Config/All/Cisco-Multi-Platform-Phones-1203-ver001.zip.

2

Import the most recent DTAF file to the BroadWorks (system level) server.

For the procedures, see the section Configure BroadWorks Device Profile Type in Cisco BroadSoft Partner Configuration Guide Cisco Multi-Platform Phone.

3

Configure Broadworks Device Profile Type.

For the procedures, see the section Cisco Broadworks Device Profile Type Configuration in Cisco BroadSoft Partner Configuration Guide Cisco Multi-Platform Phone.

What to do next

OOB onboarding flowchart

The following Out-Of-Box (OOB) flowchart shows the process for phone onboarding.

OOB: Phone is just taken out of the phone box and turned on for its initial onboarding to the target call control system.

PhoneOS Devices Onboarding Flowchart
PhoneOS device OOB onboarding flowchart

Near Field Communication (NFC) is only available on Cisco Desk Phone 9800 Series.

Provisioning with DHCP options

The phone can automatically locate its configuration server through DHCP options. During a resync, the phone queries the following DHCP options:

  • IPv4: 66, 160, 159, 150
  • IPv6: 17, 160, 159

Based on the DHCP response, the phone behaves as follows:

  • If a valid file is found, the phone will register in MPP mode using that file.

    If the DHCP option does not specify a file name, the phone tries the following default paths in sequence:

    1. /$PSN.xml
    2. /Cisco/$PN/$MA.cfg

    where

    • $PSN = Phone Serial Number
    • $PN = Phone Product Name
    • $MA = Phone MAC Address

  • If DHCP responds but no valid file is available, the phone will attempt CDA

  • If DHCP query times out (no server response), the phone will proceed to query DHCP 150/66 for the default provisioning file to register with CUCM.