We help IT Professionals succeed at work.

7940G Convert SIP to SCCP

I received 12 7940G phones that were configured as SIP.  I need to convert SIP to SCCP to work on our CM7.4 in the Home Office.

Here's my lab setup (not connected to the Internet):
Cisco 1700 router ---> connected to 3560 switch (The router don't have CM configuration)
Desktop with SolarWinds TFTP Server ---> connected to 3560 switch
7940G phone ---> connected to the switch

The current version of the SIP firmware in the phone is P0S3-07-5-00.
I was able to download already SCCP firmware, cmterm-7940-7960-sccp.8-0-10.zip
The SCCP zip file is composed of P00308001000 .bin, .sbn, .sb2, .loads
I changed already the content of OS79XX.TXT to P00308001000
The following are in the root directory of my SolarWinds TFTP Server:

I managed to factory reset the phone and changed the IP on the same subnet as the desktop.  I also changed the TFTP setting of the phone to the IP address of the desktop which has my SolarWinds.

I tried to restart the phone and nothing happens.  I need guidance in making the SCCP upgrade succesful first on one phone, then to the remaining eleven.  Please help. Thank you.
Watch Question

Hi exp exch1,
Cisco Unified IP Phone 7940Gs and Cisco Unified IP Phone 7960Gs—If these IP phones are already configured in Cisco Unified CME to use the SIP protocol, the SIP phone firmware must be version 7.x.

Removing a SIP Configuration Profile
To remove the SIP configuration profile before downloading the SCCP phone firmware to convert a phone from SIP to SCCP, perform the steps in this task.

1 enable

2 configure terminal

3 no voice register pool pool-tag

4 end
Generating an SCCP XML Configuration File for Upgrading from SIP to SCCP
To create an ephone entry and generate a new SCCP XML configuration file for upgrading a particular
Cisco Unified IP phone in Cisco Unified CME from SIP to SCCP, perform the steps in this task.

1 enable

2 configure terminal

3 ephone-dn dn-tag

4 exit

5 tftp-server flash firmware-file

6 telephony service

7 load phone-type firmware-file

8 create cnf-files

9 end

For further information, please have a look at a friends website.
Have a nice day.


I am only doing the initial task of this upgrade which is converting the firmware from SIP to SCCP using my lab setup mentioned. Configuring these phones to work with our CM will be the next step. The router does not recognized the above suggested commands.

I need to know how I can make this upgrade successful with my given scenario.  
What are the files that I need to add with what I currently have in the root directory of my WindSolar TFTP Server?
Is my lab setup appropriate for this upgrade process?
What are the steps that I need to do to make this succesful?

I'm new in VOIP and I really need your help.  Thanks.
The following example shows the configuration steps for upgrading firmware for a Cisco Unified IP Phone 7960G from SIP to SCCP. First the SIP firmware is upgraded to SIP 6.3 and from SIP 6.3 to SIP 7.4; then, the phone firmware is upgraded from SIP 7.4 to SCCP 7.2(3). The SIP configuration profile is deleted and a new ephone configuration profile is created for the Cisco Unified IP phone.

Router(config)# voice register global
Router(config-register-global)# mode cme
Router(config-register-global)# load 7960 P0S3-06-0-00
Router(config-register-global)# upgrade
Router(config-register-global)# load 7960 P0S3-07-4-00
Router(config-register-global)# exit
Router(config)# no voice register pool 1
Router(config-register-pool)# exit
Router(config)# voice register global
Router(config-register-global)# no upgrade
Router(config-register-global)# exit
Router(config)# ephone-dn 1
Router(config-ephone-dn)# exit
Router(config)# tftp-server flash:P00307020300.loads
Router(config)# tftp-server flash:P00307020300.sb2
Router(config)# tftp-server flash:P00307020300.sbn
Router(config)# tftp-server flash:P00307020300.bin
Router(config)# telephony service
Router(config-telephony)# load 7960-7940 P00307000100
Router(config-telephony)# create cnf-files
Just trying to find a how to manual I recieved from a friend a little while ago.
As I an in Australia, I may have to get back to you in 8 hours, as it is nearly midnight now.

This may be of use also.
Looking at your hardware specs, you are fine.

no your lab setup doesn't seem right you will need a CUCME or CUCM to give a config to the phone so that it knows which image to download. A router and tftp server isn't enough Pete's configs assume CUCME but full CUCM is easier if you have it


Thanks... I'm sure this would be great if I have CUCM, but I don't.  

-- Is there a way to uprade this SIP to SCCP without CUCM, just my setup with the phone, switch, desktop with SolarWinds TFTP, and a router which is not connected to the Internet?
-- The current SIP is version 7.5.  Can I jump to load SCCP 8.10 right away?

Here's the thing, these 12 7940G phones arrived here with me in a remote location (other side of the world) with SIP installed from the previous setup (not related to us).  I was advised by our Head Office to upgrade first the SIP to SCCP in order for these phones to work with our Call Manager version 7.4 which is run from the States.  I don't have any CM running in my location.  Therefore, I come up with my setup.  

Option 1 -- I need guidance on how to accomplish the upgrade using my setup (if it's workable at all with it).
Option 2 -- I need advice if ever possible, to just connect the phone to the Internet and let our Technicians in the US Office upgrade the phones using their CUCM.  If so, what are the things that I need to make sure for the phones to have (like TFTP, IP, and other configuration)  prior to this process.  Again, I'm in the other side of the world.

I prefer option 1, but the bottom line is to make these phones work either way as soon as possible.  Thank you.
You will need a version of Call Manager to do this. Can you install the voice IOS on your router and use that?

to use the remote CUCM then the phones will need IP connectivity to that server either using an Internet reachable address or via a NAT router. The DHCP scope for the phones will need to give them an ip address, default gateway and option 150 for the tftp server to get their config from ( usually CUCM).

The guys running CUCM will need the MAC addresses of the phones and will need to manually add them as sccp phones.  The phone will then get this information in their configuration file and download the image they need.



1)  Ok, I'll upgrade the IOS of my 1760 router to 12.3(4)XQ to accommodate voice.  Does upgrading to this IOS enough for me to perform the phones upgrade independently from my end?

2)  Given the capability of voice in my router, what are the steps to successfully install SCCP 8.10 from SIP 7.5.

3)  Is it possible to install SCCP firmware 8.10 straight from SIP 7.5?

4)  Which procedure do you recommend best to make this phones work as soon as possible:  
          a. Performing my upgrade using my 1760 router here (where I'm at)?
          b. Let our Techs in the US do the upgrade remotely using their Call Manager?

5) I was told that we are using Call Manager 7.4 in the US.  Is upgrading my phones to SCCP 8.10 works with such CM version with no problem at all?  What version of SCCP firmware would you recommend to work well with CM 7.4?

If you could please answer each question above, I would really appreciate it.  

Thank you.
Lot of questions which I'm afraid I cannot answer without considerable research which I don't ahve time for at the moment.

However given that the phones when upgraded to SCCP will have to be under the control of a Call Manager and will therefore need to connect to that Call Manager surely the quickest way is to connect them and use the Call Manager to do the upgrade.

You will have to connect them in the end and if the phone load on the Call Manager  doesn't match your offline one they will be overwritten anyway. I cannot see how setting up anything else will be quicker.


I apologize for asking lots of questions here.  Again, I'm new to VOIP.  

We have other VOIP phones connected to our network, like a couple of 7945Gs.  Will they be affected too with the upgrade when it happens?  I don't want to solve the issue in upgrading the 7940 phones, at the same time create problem with the other phones that are currently working.  This is one of the main reason why I want this upgrade to happen offline with my own independent lab setup.

Thank you.
No worries  ask away - we may not be able to answer them all but we will try.  The 7945Gs will be untouched.  Each phone is defined in the Call Manager and can be set to use SCCP or SIP.  I presume the 7945s are already working so they must be

under control of a Call Manager
able to send IP traffic to and from the Call Manager

if you still want to try offline then use the 1760 and put the Call Manager Express IOS on it.


I understand that with my 1760 router upgraded to its new IOS with Call Manager, I should be able to successfully upgrade SIP to SCCP offline using the same suggested commands above, right?



Thanks for your help everyone.  We're able to succesfully upgrade one phone to SCCP last night through our remote Call Manager in the States.  We hope to upgrade the remaining 8 phones which I already reset to factory settings.

I still have 3 phones left that would not allow me to reset to factory settings.  Is there another way to reset these phones?  We don't know the password, so we cannot change the IP, TFTP Server and other network settings relevant to the upgrade.

Is it still possible to convert these remaining phones to SCCP despite the issue, and how?

Thank you...
Yes.If you make factory reset, your problem may be solved.I think all cisco phone's factory loaded image is sccp.
To reset to factory setting...
Remove the power from the phone.
While connecting the power to phones, press and hold '#'  button on the phone around 1 minute.then release the button and dial 123456789*0#  in the order..
It will initiate a factory reset process.



Two of my phones are in SIP ver. 6.3.  
Could I possibly install SCCP 8.10 right away without converting it first to SIP 7.5?

Thank you.