Vous êtes sur la page 1sur 8

Cisco − Converting a Cisco 7940/7960 CallManager Phone to a SIP Phone and the Reverse Process

Table of Contents
Converting a Cisco 7940/7960 CallManager Phone to a SIP Phone and the Reverse Process....................1
Introduction.............................................................................................................................................1
Before You Begin...................................................................................................................................2
Conventions......................................................................................................................................2
Prerequisites.....................................................................................................................................2
Components Used.............................................................................................................................2
Steps Required to Enable SIP Functionality...........................................................................................2
Manually Configuring the Phone Network Settings........................................................................4
Configuring the Phone Network Settings via DHCP.......................................................................4
Bootup Process for a Cisco 7940/7960 SIP IP Phone............................................................................5
TFTP Server Log of a Phone Booting Up..............................................................................................5
Reverting Back to a Cisco CallManager SCCP Image...........................................................................6
Common Issues / Troubleshooting Tips.................................................................................................6
TFTP Accessibility and Impact on Network....................................................................................6
Obtaining SCCP Firmware...............................................................................................................6
W210 TFTP Error : buffer full" Error..............................................................................................7
SIP Phone not Accepting SCCP Load..............................................................................................7
Related Information................................................................................................................................7

i
Converting a Cisco 7940/7960 CallManager Phone
to a SIP Phone and the Reverse Process
Introduction
Before You Begin
Conventions
Prerequisites
Components Used
Steps Required to Enable SIP Functionality
Manually Configuring the Phone Network Settings
Configuring the Phone Network Settings via DHCP
Bootup Process for a Cisco 7940/7960 SIP IP Phone
TFTP Server Log of a Phone Booting Up
Reverting Back to a Cisco CallManager SCCP Image
Common Issues / Troubleshooting Tips
TFTP Accessibility and Impact on Network
Obtaining SCCP Firmware
W210 TFTP Error : buffer full" Error
SIP Phone not Accepting SCCP Load
Related Information

Introduction
Cisco 7940/7960 IP phones can support either the Skinny Call Control Protocol (SCCP) to run with Cisco
CallManager, the Session Initiation Protocol RFC2543 (SIP) protocol, or the Media Gateway Control
Protocol (MGCP), but not more than one simultaneously. It does this by loading different firmware versions
on bootup. This functionality is transparent to the end user, and it is enabled by changes to the basic
text−based configuration files that the phones download from a Trivial File Transfer Protocol (TFTP) server.

For more information on Cisco SIP IP phone, refer to Cisco IP Phone 7960/7940 User Guide for SIP.

Cisco − Converting a Cisco 7940/7960 CallManager Phone to a SIP Phone and the Reverse Process
Before You Begin
Conventions
For more information on document conventions, see the Cisco Technical Tips Conventions.

Prerequisites
There are no specific prerequisites for this document.

Components Used
This document is not restricted to specific software and hardware versions.

Steps Required to Enable SIP Functionality


Follow these steps to enable SIP functionality:

1. Download the following files from Cisco.com and place them in the root directory of your TFTP
server (tftpboot on a UNIX machine). To proceed with the download of these files, go to Cisco SIP IP
Phone 7940/7960 Software ( registered customers only) . Download the following:

♦ P0S30100.bin This is the SIP image. Download the file in binary format to prevent it from
getting corrupted.

◊ Note: There are many different variations of this file depending on the version of
software you are loading. Below are some examples.
◊ SIP Release 2.3 or earlier: P0S3xxyy.bin − The xx variable represents the version
number, and yy is the sub−version number.

Cisco − Converting a Cisco 7940/7960 CallManager Phone to a SIP Phone and the Reverse Process
◊ SIP Release 3.0 and later: P0S3−xx−y−zz.bin − The xx variable represents the major
version number, y is the minor version number, and zz is the sub−version number.
◊ SIP Release 5.0 and later: After this version has been installed, you will not be able to
revert back to versions older than 5.0. You may still change from SCCP images to
SIP images, but they both must be version 5.0 and later. For more information on
this, please visit Release Notes for Cisco SIP IP Phone 7940/7960 Release 5.0.
◊ The following table describes the meanings of the first 4 characters in the binary files.

First Digit Second Third Fourth


Digit Digit Digit
"0"
"P" Represents
represents it
represents the phone
is a "3"
a Phone Protocol
combined represents
"0" for
image the ARM
Skinny
(application processor
and "S"
and DSP)
for SIP

Note: To verify which image the phone is using, go to Settings > Status >
Firmware Versions. Different phone models use different processors. This fourth
digit can help distinguish which model phone the file is for.
♦ OS79XX.TXTThis file tells the Cisco 7940/7960 which binary to download from the TFTP
server. This file is case sensitive and must only contain the name of the file you are
attempting to load, without the .bin extension. For example, if you were attempting to load
the SIP version 2.3 software, it must contain only the line "P0S30203". The binary referenced
here must also be present in the TFTP root directory. Without this file, the phone would not
know which file it needs to retrieve to replace its existing software.
♦ SIPDefaultGeneric.cnfThis file is an example of a default configuration file. This file
contains configuration information relevant to all phones.
♦ SIPConfigGeneric.cnfThis file is similar to the previous one, except that it contains
information relevant to a specific phone instead of all phones.
♦ RINGLIST.DATLists audio files that are the custom ring type options for the phones. The
audio files listed in the RINGLIST.DAT file must also be in the root directory of the TFTP
server.
♦ ringer1.pcmThis file is a sample ring tone used by the Cisco 7940/7960.
Note: Creation of the SIP .cnf files is out of the scope of this document. For more information please
visit Getting Started with Your Cisco SIP IP Phone.
2. With a text−editor (vi, NotePad or WordPad), rename the fileSIPDefaultGeneric.cnf to SIPDefault.cnf
(used for global parameters on all phones).
3. Using a text editor rename the file SIPConfigGeneric.cnf to SIP[MAC_Address].cnf for each phone.

For example, SIP002094D245CB.cnf. The MAC address must be specified in capital letters. The
MAC address of the phone can be found on the sticker located on the bottom of the phone or via the
phone LCD screen (Settings > Network Configuration > MAC Address).

Note: Make sure to allow the read and write file permissions for the above files on the TFTP server
(for UNIX TFTP servers, use the UNIX command: #chmod 777 <filename>. For windows based
servers, check the software's documentation).
4. Reset the phones by unplugging the power cord or ethernet cord if inline power is being used. Make
certain that the phones can find the TFTP server by manually configuring the phone's IP address,
gateway address, and TFTP server address or configuring the phone network settings via the Dynamic

Cisco − Converting a Cisco 7940/7960 CallManager Phone to a SIP Phone and the Reverse Process
Host Configuration Protocol (DHCP) server. We recommend not using the TFTP server on the Cisco
CallManager if you have one in your current system.

Note: If you are experiencing failure in the installation of SIP software 3.x or 4.x, try to upgrade to
the SIP image 2.3 first and then move to 3.x. This is common when using a particularly old version of
the Cisco 7940/7960 SCCP Software. Here is the tftp log debug showing what the failure looks like.

Wed Nov 06 11:58:51 2002: Sending 'OS79XX.TXT' file to 10.1.1.1 in binary mode
Wed Nov 06 11:58:51 2002: Successful.
Wed Nov 06 11:58:51 2002: Sending 'P0S30300.bin' file to 10.1.1.1 in binary mode
Wed Nov 06 11:58:52 2002: Failed ( State Error ).
Wed Nov 06 11:59:00 2002: Sending 'P0S30300.bin' file to 10.1.1.1 in binary mode
Wed Nov 06 11:59:02 2002: Failed ( State Error ).
Wed Nov 06 11:59:10 2002: Sending 'P0S30300.bin' file to 10.1.1.1 in binary mode
Wed Nov 06 11:59:13 2002: Failed ( State Error ).

Manually Configuring the Phone Network Settings


Follow these steps to manually configure the phone network settings:

1. Unlock the phone by pressing the **#buttons. (This step either locks or unlocks the options,
depending on the previous state.)
2. Press Settings.
3. Press the down arrow to Network Configuration and press the Select soft key. Look at the
upper−right portion of your LCD, there should be an unlocked padlock icon.
4. Modify any parameters using the toggle button and the arrow keys. When entering IP addresses, the *
key is used for decimal points.
5. Save the changes with Save.

Note: To lock the phone settings press **#.

For more information, refer to Getting Started with Your Cisco SIP IP Phone.

Configuring the Phone Network Settings via DHCP


For SIP phones, make sure that the DHCP server uses Option 66 for the TFTP server. The following DHCP
options are usually configured via the DHCP server:

• IP Address (DHCP Option 50)


• Subnet Mask (DHCP Option 1)
• Default IP Gateway (DHCP Option 3)
• DNS Server Address (DHCP Option 6)
• TFTP Server (DHCP Option 66)
• Domain Name (DHCP Option 15)

Note: Cisco CallManager uses Option 150 for the TFTP server, while SIP Phones expect Option 66 for the
TFTP server.

For more information, refer to Getting Started with Your Cisco SIP IP Phone.

Cisco − Converting a Cisco 7940/7960 CallManager Phone to a SIP Phone and the Reverse Process
Bootup Process for a Cisco 7940/7960 SIP IP Phone
Follow the steps below.

1. Each phone requests the initial setup file OS79XX.TXT

Note: Make certain that you use exactly the same name, because the filenames on the TFTP server
and the SIP image name in OS79XX.TXT are case sensitive.
2. Each phone loads the firmware binary file listed in the OS79XX.TXT file. After downloading the
proper .bin file, it replaces the software it runs with this new image. To switch back to another
software version, the phone must be restarted so that software may be downloaded again.
3. Each phone loads the SIP image indicated in the initial setup file. In this case, the P0S30100.bin file is
loaded.
4. Each phone loads the SIPDefault.cnf file. This file contains basic configuration settings that are
common for all phones.
5. Each phone loads its specific configuration information from the file SIP[MAC_Address].cnf. The
MAC address must be specified in capital letters.

TFTP Server Log of a Phone Booting Up


The following is a sample log file from the TFTP server showing the full boot procedure:

Mon Sep 11 15:24:53 2000: Sending 'OS79XX.TXT' file to 10.1.1.10 in binary mode
#
Mon Sep 11 15:24:53 2000: Successful.
Mon Sep 11 15:24:53 2000: Sending 'P0S30100.bin' file to 10.1.1.10 in binary mode
############################################################################
############################################################################
############################################################################
############################################################################
############################################################################
############################################################################
############################################################################
############################################################################
####################################################################
Mon Sep 11 15:24:55 2000: Successful.
Mon Sep 11 17:15:25 2000: Sending 'OS79XX.TXT' file to 10.1.1.10 in binary mode
#
Mon Sep 11 17:15:25 2000: Successful.
Mon Sep 11 17:15:26 2000: Sending 'SIPDefault.cnf' file to 10.1.1.10 in binary mode
###
Mon Sep 11 17:15:26 2000: Successful.
Mon Sep 11 17:15:26 2000: Sending 'SIP003094C29C71.cnf' file to 10.1.1.10 in
binary mode
##
Mon Sep 11 17:15:26 2000: Successful.
Mon Sep 11 17:15:26 2000: Sending 'RINGLIST.DAT' file to 10.1.1.10 in binary mode
#
Mon Sep 11 17:15:27 2000: Successful.
Mon Sep 11 17:15:37 2000: Sending 'ringer2.pcm' file to 10.1.1.10 in binary mode
################
Mon Sep 11 17:15:37 2000: Successful.

Below is the TFTP log file which shows the failure to download the SIP image to the IP Phone. To resolve
this, try to upgrade the SIP phone load to 2.3 first and then move to 3.x or 4.x .

Wed Nov 06 11:58:51 2002: Sending 'OS79XX.TXT' file to 10.1.1.1 in binary mode

Cisco − Converting a Cisco 7940/7960 CallManager Phone to a SIP Phone and the Reverse Process
Wed Nov 06 11:58:51 2002: Successful.
Wed Nov 06 11:58:51 2002: Sending 'P0S30300.bin' file to 10.1.1.1 in binary mode
Wed Nov 06 11:58:52 2002: Failed ( State Error ).
Wed Nov 06 11:59:00 2002: Sending 'P0S30300.bin' file to 10.1.1.1 in binary mode
Wed Nov 06 11:59:02 2002: Failed ( State Error ).
Wed Nov 06 11:59:10 2002: Sending 'P0S30300.bin' file to 10.1.1.1 in binary mode
Wed Nov 06 11:59:13 2002: Failed ( State Error ).

Reverting Back to a Cisco CallManager SCCP Image


To revert the SIP phone back to the Cisco CallManager Skinny phone, edit the OS79XX.txt file, and change
the filename reference back to the Cisco CallManager load ID. The next time the phone connects to the TFTP
server, it loads the CallManager load file.

Navigate to the Cisco 8940/7960 SCCP software download page in Software Center by clicking Voice
Software, then selecting the SIP IP Phone 7940/7960. Download the latest version of the 7940/7960
software. If you are upgrading from an early version of the 7940/7960 SIP software (3.x or earlier), try
upgrading to the latest version of the SCCP 4.x chain before upgrading to the SCCP 5.x chain. Once you
upgrade to the 5.x chain, you will not be able to revert back to an earlier image. For more information about
the difference between versions, please view the Release Notes for Cisco SIP IP Phone 7940/7960 Release
5.0.

Run the executable file to install the SCCP software. Make sure the new files are in your TFTP main folder.
Change the OS79xx.txt file to reflect the new filename. For example, if you had downloaded version 5.0(1.1),
your .bin file would have been P00305000101.bin. Change the text in the OS79xx.txt file to reflect this
filename without the .bin extension.

Note: Make certain that all of the required Cisco CallManager files are on the TFTP server before rebooting
the phones.

For more information on configuring DHCP, TFTP, or Cisco CallManager, visit the links below:

• Cisco TFTP
• Configuring Windows 2000 DHCP Server for Cisco Call Manager
• Configuring Cisco CallManager 3.x with IOS MGCP Gateways (Analog FXO, FXS Ports)

Common Issues / Troubleshooting Tips


TFTP Accessibility and Impact on Network
If you are trying to update only one phone in a production network, make sure that you use a different TFTP
server than the one listed on the DHCP server. Using that TFTP server can potentially cause all phones on the
network to upgrade to the new firmware. If you are only attempting to upgrade one phone, use a different
TFTP server, and enter the server's IP address manually in the phone's settings (Settings > Network
Configuration > Alternate TFTP Server (Change to Yes) > TFTP Server (Change IP address)). Always
take great care when upgrading phones, as changing these configurations has the potential to bring down the
entire phone system if not implemented properly.

Obtaining SCCP Firmware


The files located in software center for the SCCP image are contained in an executable file. Upon execution of
this file, an installer will be launched to locate the presence of Cisco Call Manager and its TFTP root folder.

Cisco − Converting a Cisco 7940/7960 CallManager Phone to a SIP Phone and the Reverse Process
Once this location has been determined, the installer will copy all necessary files to the TFTP root folder.
After this installation, it is still necessary to make the appropriate changes to the OS79XX.TXT file as
mentioned earlier.

W210 TFTP Error : buffer full" Error


Older versions of the SIP software (2.x releases) have a bug where the phone cannot download the SIPDefault
file if it is larger than a certain size. The phone may display "W210 TFTP error : buffer full". To solve this
problem, make sure the following files have these characteristics:

• OS79XX.TXT should contain only the firmware filename minus the .bin extension. ex: P0S30203 for
P0S30203.bin
• SIPDefault.cnf should contain only "image_version: <filename>", where filename is the firmware
filename minus the .bin.

This will allow the Cisco 7940/7960 to download the newer software. Once you have upgraded, you may
replace SIPDefault.cnf with your configuration information, as the phone will be able to download this larger
file.

SIP Phone not Accepting SCCP Load


For SIP software version 2.1 and earlier: the phone will not accept an SCCP load whose filename is longer
than eight characters. There are two options to workaround 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 (max length =
xxxxxxxx.yyy)

Note: The most common caveats in this upgrade procedure have been listed throughout this document. Most
problems stem from using older software, or not having the correct syntax in the OS79XX.TXT file. Before
opening a case with the TAC, try upgrading to the latest versions of the phone software, as this solves many
problems pertaining to the Cisco 7940/7960 Series phones.

Related Information
• Getting Started with Your Cisco SIP IP Phone
• RFC 2543: Session Initiation Protocol − SIP
• Voice Technologies
• Voice, Telephony and Messaging Devices
• Voice Software
• Voice, Telephony and Messaging TAC eLearning Solutions
• Recommended Reading: Troubleshooting Cisco IP Telephony
• Technical Support − Cisco Systems

All contents are Copyright © 1992−2003 Cisco Systems, Inc. All rights reserved. Important Notices and Privacy Statement.

Cisco − Converting a Cisco 7940/7960 CallManager Phone to a SIP Phone and the Reverse Process