In order to revert the SIP phone back to a Cisco CallManager Skinny phone, edit the OS79XX.TXT file to change the file name reference back to the Cisco CallManager load ID. The next time that the phone connects to the TFTP server, it loads the CallManager load file.
Navigate to the Cisco7940/7960 SCCP software download page at the Cisco Downloads (registered customers only): click Voice Software, and then click SIP IP Phone 7940/7960. Download the latest version of the
7940/7960 software. If you convert from an early version of the 7940/7960 SIP software (3.x or earlier), try to convert to the latest version of the SCCP 4.x chain before you convert to the SCCP 5.x chain. Once you convert to the 5.x chain, you are not able to revert back to an earlier image. For more information about the difference between versions, refer to Release Notes for Cisco SIP IP Phone 7940/7960 Release 5.0.
· SIP Images 4.x/Earlier to SCCP Images 5.x/Earlier
· SIP Images 4.x/Earlier to SCCP Images 6.x/Later
· SIP Images 7.x/Later to SCCP Images 5.x
SIP Images 4.x/Earlier to SCCP Images 5.x/Earlier
If your current SIP image is 4.x or earlier, complete these steps in order to convert to the desired SCCP
images 5.x or earlier:
1. Run the executable file in order to install the SCCP software. Ensure that the new files are in your TFTP main folder.
2. Change the OS79XX.TXT file to reflect the new file name. For example, if you download version 5.0(1.1), your BIN file is P00305000101.bin. Change the text in the OS79XX.TXT file to reflect this file name, without the .bin extension.
3. Reset each phone.
Note: Ensure that all of the required Cisco CallManager files are on the TFTP server before you reboot the phones.
SIP Images 4.x/Earlier to SCCP Images 6.x/Later
If your current SIP images is 4.x or earlier, complete these steps in order to convert to the desired SCCP
images 6.x or later:
1.Complete these steps in order to convert to the 6.3 image first:
a. Copy the desired binary image from Cisco.com to the root directory of the TFTP server.
b. Open the OS79XX.TXT file with a text editor and edit the file to include the desired image.
c. Specify the desired image in the protocol configuration files.
d.Reset each phone.
The phone contacts the TFTP server and requests its configuration files. The phone compares the image that is defined in the configuration file to the image that it has stored in Flash memory. If the phone determines that the image in the configuration file differs from the image in Flash memory, it downloads the image in the configuration file (which is stored in the root directory on the TFTP server). Once the new image downloads, the phone programs that image into Flash memory and reboots.
2. Complete these steps in order to convert to the desired image:
a. Unzip the software_version.zip file to the root (top level) TFTP directory.
b. Reset the phone.
The phone contacts the TFTP server and requests its configuration files. The phone compares the image defined in the OS79XX.TXT and protocol configuration files to the image that it has stored in Flash memory. If the phone determines that the image defined in the files differs from the image in Flash memory, it downloads the image that is defined (which is stored in the root directory on the TFTP server). Once the new image downloads, the phone programs that image into Flash memory and reboots.
SIP Images 7.x/Later to SCCP Images 5.x/Later
If your current SIP image is 7.x or later, complete these steps in order to convert to the desired SCCP images 5.x or later:
In the configuration file for the protocol that the phone currently runs, change the image in the load_information parameter (SCCP) or the image_version parameter (SIP) to represent the protocol that you
want to run. For example, if the image on the phone is SIP and the image desired is SCCP, change the image_version parameter to reflect the SCCP image (P00306000200).
DHCP, TFTP, or Cisco CallManager:
· Cisco TFTP
· Configuring Windows 2000 DHCP Server for Cisco Call Manager
· Configuring Cisco CallManager 3.x with IOS MGCP Gateways (Analog FXO, FXS Ports)
Converting SCCP Phones to SIP and reverse in Cisco Unified Communication Manager 5.x and 6.x
Complete these steps in order to convert the SCCP IP Phones to SIP:
1. Go to Cisco CallManager Administration and choose Bulk Administration > Phones > Migrate Phones > SCCP to SIP.
2. Click Find after you select/enter the appropriate search criteria to list the phones that need to be migrated.
3. Click Next and choose the phone template from the drop?down.
4. Enter the job description in the Job Information area.
5. Click Run Immediately in order to migrate phone records immediately or click Run Later in order to migrate at a later time.
6. Click Submit in order to create a job for migrating the phone records.
Note: After you submit a job for migrating phones from SCCP to SIP, make sure that you reset these phones. In order to reset the phones, choose Bulk Administration > Phones > Reset/Restart Phones > Query.
7. When the Migrate job is submitted, choose Bulk Administration > Job Scheduler in order to schedule and/or activate this job. If it remains in the Pending state, you might need to activate the Bulk Provisioning Service under the Serviceability > Tools > Service Activation page. Refer to Activating Bulk Provisioning Service for
more information.
8. Go to Cisco CallManager Administration, choose System > Enterprise Parameters and change Auto Registration Phone Protocol to SIP (SCCP is the default). Then restart the Cisco CallManager service.
Note: In order to revert back to SCCP, you need to delete the SIP phone, set Auto Registration Phone
Protocol to SCCP and then let the phone re?register as SCCP.
TFTP Accessibility and Impact on Network
If you want to update only one phone in a production network, be sure to use a different TFTP server than the one that is listed on the DHCP server. If you use the listed TFTP server, you can potentially cause all phones on the network to convert to the new firmware. If you only attempt to convert one phone, use a different TFTP
server and enter the IP address of the server manually in the phone settings (Settings > Network Configuration > Alternate TFTP Server [Change to Yes] > TFTP Server [Change IP address]). Always
take great care when you upgrade phones, as changes to these configurations have the potential to bring down the entire phone system, if they are not properly implemented.
SIP Phone not Accepting SCCP Load
For SIP software version 2.1 and earlier, the phone does not accept an SCCP load whose file name is longer than eight characters. There are two options to work around this problem:
· Upgrade the SIP software to a newer version, then revert back to the SCCP software.
. Rename the SCCP load file so that it meets the 8.3 DOS standard naming convention (maximum file
name length is xxxxxxxx.yyy).