Here's where we try to take some of the agony out of loading a 7940/7960
I think that a lot of folks will agree that loading a Cisco phone can be
either a piece of cake or a total pain in the butt!!! - No in betweens! - But
we'll do what we can to make it a little less agonizing for you.
We'll do this by showing you a couple of lists.
From the first list, you'll tell us what firmware's currently loaded in your
Based on what your phone has loaded, we'll then show you a choice of
possible firmware(s) you can load into your phone.
After you choose what you want to load, we'll then (try to) explain a little
about the loading process and what you need to do.
Gosh! What do I do here?
Here's where we need to know what firmware image you have installed in
your phone now.
To determine what firmware you have on your 7940 or 7960, just do the
Press the 'Settings' button on the phone.
Scroll down to 'Status' and press the 'Select' soft
Scroll down to 'Firmware Versions' and press the
Look for 'App Load ID:' - That shows the firmware version
loaded in your phone. It should match up to one of the choices in the table
on your left.
All you have to do is chose your installed
firmware from the table and we'll take you to the next screen.
When you get there, you may have to scroll up to the top.
Please double-check & make sure the above matches with your phone's installed
firmware before continuing.
If you wish to bail out and re-select your installed firmware, here's your
Based on the firmware version that's currently in the phone, the list on the left
shows you all the possible firmware versions you can load.
Just like the previous menu, all you need to do is select which version you want
to load and we'll tell you about what procedure you need to use and
a little about it.
Cisco specifies what they call 'Procedure A' for this load
Here is Cisco's description for this procedure:
The SEP<mac-address>.cnf.xml file is downloaded when the phone is
reset. This file contains the load_information tag that tells the phone
which image it should be running. If this image load differs from the one
currently loaded on the phone, the phone contacts the TFTP server to upgrade
to the new image.
There's not much else to this except that this procedure is only associated with
SCCP (skinny) loads and we don't use SCCP on any of our phones.
Cisco specifies what they call 'Procedure B' for this load.
Cisco specifies what they call 'Procedure C' for this load.
Specify the image in the configuration file image parameter for the protocol
that is being upgraded to (load_information for SCCP or image_version for
SIP and MGCP). - Remove any protocol configuration files that are not used
for the specified protocol.
Note: For a single step upgrade from an SCCP image to a SIP or MGCP
image (manufacturing images, for example) the load information tag in the
XML Default.cnf.xml file must reflect the Universal Application Loader Image
(P003-xx-y-zz). This step is in addition to the steps listed above for SIP
and MGCP. - For example:
model="IP Phone 7940">P003-07-4-00</loadInformation8>
model="IP Phone 7960">P003-07-4-00</loadInformation7>
Cisco specifies what they call 'Procedure D' for this load.
Here's Cisco's description of this load:
Cisco specifies what they call 'Procedure D2' for this load.
This almost identical to the normal Procedure 'D'. - See my note below.
Note: - If you want to upgrade from SIP 5.x or 6.x to 7.x use
Procedure 'F'. - Upgrading from SIP 5.x directly to SIP 7.x is not
possible. - First upgrade to SIP 6.3 and then go to SIP 7.x.
FYI - 'Procedure F' specifies to further use Procedures 'B' & 'D'. - If you
like, we can show you 'Procedure F' and those procedures it specifies:
Here's Cisco's description for procedure 'F':
1. Upgrade to the 6.3 image using Procedure 'B'.
Then (if necessary)
2. Upgrade to the desired image using Procedure 'D'.
Here is Cisco's description for procedure 'B':
Here's Cisco's description for procedure 'D':
Cisco specifies what they call 'Procedure E' for this load.
Here is Cisco's description of this procedure:
There are two possible ways to accomplish this upgrade.
Cisco specifies what they call 'Procedure F' for this load.
Here's Cisco's description for this procedure:
If you like, we can show you these other procedures:
For some reason I can't find any procedure for your installed firmware and you
'target' firmware. - But one surely exists.
This can only mean we have a bug in our program. - While we extensively check
all scenarios, it's still possible one may 'leak through'.
Here we'll try to pass on some usefull Hints, Tips, & Gotcha's we learned
along the way. - Hope you find at least some of them helpfull.
Early SIP versions:
SIP versions 1 & 2 are not recommended due to their age (In fact, we haven't
been able to find SIP ver. 1 anywhere.). - However you may need to load an early SIP
version as an 'intermediate' load to access the later versions (see next item).
If you have SIP 2.1 or earlier installed:
1 - These versions will not allow upgrading to a version if the number of
characters is greater than 8 (it uses old 8.3 DOS filenames). - Cisco recommends
re-naming the binary to 8 characters.
1A - Even after re-naming the file, it still won't work if it's larger than
384K in size. - Thanks to a kind soul on the Internet for this info (of
course, we can't find anything in Cisco's docs regarding this).
Our recommendation is to first load either SIP version 2.2 or 2.3
which allows longer filenames and larger size loads. - Then you'll be
'good-to-go' for the bigger stuff.
Unlocking a Phone:
On your phone, if you press 'Settings', scroll to the bottom and do
not see 'Unlock Config', this means that you have a very early firmware
To 'unlock' this type of a configuration is to press
'**#. - This uses the same method as the 7905/7912
If you DO see 'Unlock Config',
'**#' will NOT work and you'll have to enter
the phone's password. - The default password from the factory is: cisco
Reseting a Phone.
You can do this by a 'power reset' or by pressing:
'asterisk'-'6'-'Settings' all at the same time. - Cisco's version of a
PC's: 'alt'-'ctrl'-'del' (three-finger salute).
Loading a ver. 5 or later onto a Pre-ver. 5 Phone
Please be aware that after loding a ver. 5.x or later onto a pre-ver. 5 phone,
you can NEVER revert the phone back to a pre-5.x image (regardless
of the protocol).
This is because beginning with version 5.0 (all protocols), Cisco introduced
'signed images' and part of your 'load' will replace the phone's application
loader. - This new loader will only accept 'signed' images for any subsequent
Here's a link to the Cisco's Firmware Upgrade page that includes a lot of usefull
information if you can just wade through it:
Cisco's Firmware Guide