SIP to SCCP for 7912 Issue

Unanswered Question
Aug 18th, 2007

Hello,


I have the following field in the gkdefault.cfg file


#txt


upgradecode:3,0x601,0x0400,0x0100,192.168.10.250,0x060817A, 0x030829a,CP7912080003SCCP070409A


I then have the gkdefault.cfg in flash and have the tftp-server flash:gkdefault.cfg

i also have tftp-server flash:CP7912080003SCCP070409A.sbin and also have the FW in flash


Then i have load CP7912080003SCCP070409A


I cannot get the 7912 to change FW from SIP to SCCP. Running CME4.1 IOS 12.4(11)XJ3.


Thanks


Thanks

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
G_Dimitrov Sat, 08/18/2007 - 23:02

Hi . Edit your gkdefault.cfg in notepad


upgradecode:3,0x601,0x0400,0x0100,192.168.10.250,0x060817A, 0x070409a,CP7912080003SCCP070409A.bin


Then upload the new gkdefault.cfg in flash .


Mount CP7912080003SCCP070409A.bin in TFTP .


Restart telephony system


Restart tel.7912


good luck !!


p.holley Sun, 08/19/2007 - 04:05

In the upgradecode field i don't have a .bin FW for the 7912 but a .sbin FW.


CP7912080003SCCP070409A.sbin.


so i used this in my gkdefault.cfg file and still not working. 0x070409a is the only change i made to my previous file

Paolo Bevilacqua Sun, 08/19/2007 - 04:10

Correct, it's .sbin not .bin. Apologize for the confusion.


Are you doing the conversion with cfgfmt.exe ?

Can you post output of "term mon" and "debug tftp event" when you turn on the 7912 ?

p.holley Sun, 08/19/2007 - 04:15

Thanks for your response:


When 7912 is loading, this is what i see on my console:


TFTP: Looking for gk0015c69dfbbb

TFTP: lOOKING FOR GKDEFAULT.CFG

TFTP: Opened Flash:GKDEFAULT.CFG, FD 0, SIZE 62 FOR PROCESS 125

TFTP: Finished flash:gkdefault.cfg, time 00:00:00 for process 125

TFTP: Looking for gk0015c69dfbbb

TFTP: lOOKING FOR GKDEFAULT.CFG

TFTP: Opened Flash:GKDEFAULT.CFG, FD 0, SIZE 62 FOR PROCESS 125

TFTP: Finished flash:gkdefault.cfg, time 00:00:00 for process 125



p.holley Sun, 08/19/2007 - 04:19

I also tried creating a new gkdefault.cfg file with just one field and yes I am using the cfgfmt to convert the .txt to .cfg


this is all I have in my updated gkdefault.cfg file


#txt

upgradecode:3,0x601,0x400,0x0100,192.168.10.250,0x060817a,0x070409a,CP7912080003SCCP070409A.sbin


Thanks

p.holley Sun, 08/19/2007 - 04:10

Also when the 7912 is booting up, it looks for two files


gkdefault.cfg and gk0015c69dfbbb. The second is also the phone MAC address

Paolo Bevilacqua Sun, 08/19/2007 - 04:24

Hi, The only thing that can prevent the upgrade is an ID (field before the FW filename) that is lower of whatever has been used previously. Try 0x170409a.


p.holley Sun, 08/19/2007 - 04:34

ok, will give it a try. The FW for this phone was a SIP FW. I don't think it ever ran SCCP

Paolo Bevilacqua Sun, 08/19/2007 - 04:37

EDIT FOR CORRECT FORMAT:


Ok, I was reviewing your file above, you still have an extra field to changed to 69, that is, after the IP address, there is 69, the numeric ID, and then as last field, the filename.


Once you format the line right, phone will upgrade, promised :)


To provide upgrade instructions to a phone, add the following line to the Cisco Unified IP Phone profile file:


upgradecode:3,type,0x0400,0x0100,tftp_server_ip,69,image_id,image_file_name


where:

* type is 0x401 for the Cisco Unified IP Phone 7902G, 0x501 for the Cisco Unified IP Phone 7905G, or 0x601 for the Cisco Unified IP Phone 7912G.


* tftp_server_ip is the IP address of the TFTP server on which the firmware upgrade image is stored. Enter 0 to use the TFTP server specified by the TFTPServer1 parameter or by DHCP.


* image_id is a unique 32-bit integer value. This value must be different for each upgrade. For this value, it is convenient to use 0x followed by the build date on the image file name. (For example, if the image file name is

CP79050101SCCP030323A.ZUP, then the build date is 30323A, and image_id would be 0x30323A.)


* image_file_name is the file name of the firmware upgrade image.

p.holley Sun, 08/19/2007 - 05:14

ah:-) Thank you. I would have been better off asking for the link on the cisco web site, cause i was a bit mislead.


Can you please post the link for this procedure. Thank you very much for your time.

Actions

This Discussion