Need help to convert a 7960 Phone with SIP to SCCP!

[Advanced_Programs]

I need some help to convert a 7960 Phone with SIP back to SCCP.

I've been researching this for several days now.

I've made some progress, but I'm stuck in a Loop now (please see below for details)

The Cisco website and many other sites have some conflicting versions about how to do this.

But the most clear guide can be found in this Thread:

https://supportforums.cisco.com/document/62701/how-convert-phones-sip-sccp

So I've followed the steps suggested here.

I'm using the TFTPD32 TFTP Server as suggested in the above Link.

My TFTP Server Directory has all the needed Files for the SCCP Loads:

P00308010200.sbn
P00308010200.loads
P00308010200.bin
P00308010200.sb2

It also has these files:

OS79XX.TXT
SIPDefault.cnf
SIP<mac_address>.cnf
SEP<mac_address>.cnf.xml

All the files has been updated accordingly.  That is:

- OS79XX.TXT has single line with this text: P00308010200

- SIPDefault.cnf was modified, so that the Image Version also points to P00308010200

# Image Version
image_version: "P00308010200"

Finally, SEP<mac_address>.cnf.xml  also includes the proper loadInformation Parameter (P00308010200 in this case)

<device>
<deviceProtocol>SIP</deviceProtocol>
<loadInformation model="IP Phone 7960">P00308010200</loadInformation>
</device>

But it still doesn't work and I'm VERY frustrated now!

First of all, the TFTP never gets a Request for OS79XX.TXT  (I don't really know why; perhaps it's because of the version)

But it does get a Request for the other files:

SIPDefault.cnf
SIP<mac_address>.cnf
SEP<mac_address>.cnf.xml

All 3 files are found and fetched and after that it tries to load P00308010200.loads

So the TFTP Server Log shows the following:

Connection received from 172.30.2.81 on port 50209 [20/04 17:26:39.973]
Read request for file <P00308010200.loads>. Mode octet [20/04 17:26:39.973]
Using local port 3055 [20/04 17:26:39.973]
<P00308010200.loads>: sent 1 blk, 461 bytes in 0 s. 0 blk resent [20/04 17:26:39.989]

But after that it doesn't go any further!  It just repeats the same process over and over!

That is, the Phone simply resets and then it loads all 4 files again.

So it gets the CNF files again and then it tries again to to load P00308010200.loads and so on!

What am I missing?

Any help would be greatly appreciated.

Thanks!

[mohamed helmy]

Hello,

why don't you try to remove and add the phone again as SCCP ?

if this is a CME, make sure you Uploaded the Firmware files to the flash and use these commands:

tftp-server flash:<file name>

tftp-server flash:<file name>

repeat this command to all the firmware files. then under telephony-services use the "load" command

load 7960 <filename.loads>

and if this is a CUCM, simply make sure that the device default points to the firmware version you want, if not, use free FTPd to upload and install this firmware.

Regards,

Mohamed Helmy

[Advanced_Programs]

Thank you for your reply.

I really appreciate the fact that you are trying to help.

But I can tell you that, although this should not be too complicated, it is not as simple as you think either.

If I plug other Phones that already have SCCP in them, they have no problems registering with CME.  The problem is with Phones that have SIP Firmware.

The known procedures for this problem (like the Link given in my original posting) are not working in my case and that is why I seeking some advice.  Perhaps somebody has experienced this issue before.

Thank you anyway!

[Leo Laohoo]

If your phone is plugged into a Cisco switch, then post the "debug tftp events".

[Advanced_Programs]

Thank you for your reply.

Sure, I'm posting them now (please see below the entire sequence)

As I stated in the original posting, you can see that it looks and finds these 3 files:

Looking for SIPDefault.cnf
Looking for SIP001BD4C6C021.cnf
Looking for SEP001BD4C6C021.cnf.xml

Both, the SIPDefault.cnf file and the SEP001BD4C6C021.cnf.xml have entries that point to P00308010200

I guess they are read correctly, because the next file fetched is P00308010200.loads

Looking for P00308010200.loads

It does find it and the transfer starts:

Opened flash:P00308010200.loads, fd 10, size 461

461 is the correct file size.  Then it appears to finish:

Finished flash:P00308010200.loads

I guess that the transfer is completed, but I'm not sure about that because right after that it requests the same file again, so the previous sequence is repeated:

Mar 29 22:13:10.723: TFTP: Looking for P00308010200.loads
Mar 29 22:13:10.727: TFTP: Opened flash:P00308010200.loads, fd 10, size 461 for
process 260
Mar 29 22:13:10.727: TFTP: Sending block 1 (retry 0), socket_id 0x4AC98BE4
Mar 29 22:13:10.727: TFTP: Received ACK for block 1, socket_id 0x4AC98BE4
Mar 29 22:13:10.727: TFTP: Finished flash:P00308010200.loads, time 00:00:00 for process 260
C2811#

At this point the Phone reboots and it starts all over again!

That is, it looks for SIPDefault.cnf and the entire sequence repeats itself in an endless loop!

Looking for SIPDefault.cnf

..............................................

C2811#
C2811#debug tftp events
TFTP Event debugging is on
C2811#debug tftp packets
TFTP Packet debugging is on
C2811#
Mar 29 22:12:47.355: TFTP: Server request for port 51456, socket_id 0x4AC98BE4 f
or process 260
Mar 29 22:12:47.355: TFTP: read request from host 172.35.140.12(51456) via FastEthernet0/0.35
Mar 29 22:12:47.355: TFTP: Looking for SIPDefault.cnf
Mar 29 22:12:47.371: TFTP: Opened flash:SIPDefault.cnf, fd 10, size 6203 for pro
cess 260
Mar 29 22:12:47.375: TFTP: Sending block 1 (retry 0), socket_id 0x4AC98BE4
Mar 29 22:12:47.379: TFTP: Received ACK for block 1, socket_id 0x4AC98BE4
Mar 29 22:12:47.379: TFTP: Sending block 2 (retry 0), socket_id 0x4AC98BE4
Mar 29 22:12:47.379: TFTP: Received ACK for block 2, socket_id 0x4AC98BE4
Mar 29 22:12:47.379: TFTP: Sending block 3 (retry 0), socket_id 0x4AC98BE4
Mar 29 22:12:47.383: TFTP: Received ACK for block 3, socket_id 0x4AC98BE4
Mar 29 22:12:47.383: TFTP: Sending block 4 (retry 0), socket_id 0x4AC98BE4
Mar 29 22:12:47.383: TFTP: Received ACK for block 4, socket_id 0x4AC98BE4
Mar 29 22:12:47.383: TFTP: Sending block 5 (retry 0),
C2811#socket_id 0x4AC98BE4
Mar 29 22:12:47.387: TFTP: Received ACK for block 5, socket_id 0x4AC98BE4
Mar 29 22:12:47.387: TFTP: Sending block 6 (retry 0), socket_id 0x4AC98BE4
Mar 29 22:12:47.391: TFTP: Received ACK for block 6, socket_id 0x4AC98BE4
Mar 29 22:12:47.391: TFTP: Sending block 7 (retry 0), socket_id 0x4AC98BE4
Mar 29 22:12:47.391: TFTP: Received ACK for block 7, socket_id 0x4AC98BE4
Mar 29 22:12:47.391: TFTP: Sending block 8 (retry 0), socket_id 0x4AC98BE4
Mar 29 22:12:47.395: TFTP: Received ACK for block 8, socket_id 0x4AC98BE4
Mar 29 22:12:47.395: TFTP: Sending block 9 (retry 0), socket_id 0x4AC98BE4
Mar 29 22:12:47.395: TFTP: Received ACK for block 9, socket_id 0x4AC98BE4
Mar 29 22:12:47.395: TFTP: Sending block 10 (retry 0), socket_id 0x4AC98BE4
Mar 29 22:12:47.399: TFTP: Received ACK for block 10, socket_id 0x4AC98BE4
Mar 29 22:12:47.399: TFTP: Sending block 11 (retry 0), socket_id 0x4AC98BE4
Mar 29 22:12:47.403: TFTP: Received ACK for block 11, socket_id 0x4AC98BE4
Mar 29 22:12:47.403: TFTP: Sending block 12 (retry 0), socket_id 0x4AC98BE4
Mar 29 22:12:47.403: TFTP: Received ACK for block 12, socket_id 0x4AC98BE4
Mar 29 22:12:47.403: TFTP: Sending block 13 (retry 0), socket_id 0x4AC98BE4
Mar 29 22:12:47.407: TFTP: Received ACK for block 13, socket_id 0x4AC98BE4
Mar 29 22:12:47.407: TFTP: Finished flash:SIPDefault.cnf, time 00:00:00 for proc
ess 260
Mar 29 22:12:47.555: TFTP: Server request for port 51457, socket_id 0x4C9BAB88 f
or process 260
Mar 29 22:12:47.555: TFTP: read request from host 172.35.140.12(51457) via FastEthernet0/0.35
Mar 29 22:12:47.555: TFTP: Looking for SIP001BD4C6C021.cnf
Mar 29 22:12:47.559: TFTP: Opened flash:SIP001BD4C6C021.cnf, fd 10, size 1166 fo
r process 260
Mar 29 22:12:47.563: TFTP: Sending block 1 (retry 0), socket_id 0x4C9BAB88
Mar 29 22:12:47.563: TFTP: Received ACK for block 1, socket_id 0x4C9BAB88
Mar 29 22:12:47.567: TFTP: Sending block 2 (retry 0), socket_id 0x4C9BAB88
Mar 29 22:12:47.567: TFTP: Received ACK for block 2, socket_id 0x4C9BAB88
Mar 29 22:12:47.567: TFTP: Sending block 3 (retry 0), socket_id 0x4C9BAB88
Mar 29 22:12:47.571: TFTP: Received ACK for block 3, socket_id 0x4C9BAB88
Mar 29 22:12:47.571: TFTP: Finished flash:SIP001BD4C6C021.cnf, time 00:00:00 for
 process 260
C2811#
C2811#
Mar 29 22:13:04.783: TFTP: Server request for port 50226, socket_id 0x4C9BAB88 f
or process 260
Mar 29 22:13:04.783: TFTP: read request from host 172.35.140.12(50226) via FastEthernet0/0.35
Mar 29 22:13:04.783: TFTP: Looking for CTLSEP001BD4C6C021.tlv
Mar 29 22:13:04.783: TFTP: Sending error 1 No such file
Mar 29 22:13:04.807: TFTP: Server request for port 50227, socket_id 0x4AC98BE4 f
or process 260
Mar 29 22:13:04.807: TFTP: read request from host 172.35.140.12(50227) via FastEthernet0/0.35
Mar 29 22:13:04.807: TFTP: Looking for SEP001BD4C6C021.cnf.xml
Mar 29 22:13:04.827: TFTP: Opened flash:SEP001BD4C6C021.cnf.xml, fd 10, size 130
 for process 260
Mar 29 22:13:04.831: TFTP: Sending block 1 (retry 0), socket_id 0x4AC98BE4
Mar 29 22:13:04.831: TFTP: Received ACK for block 1, socket_id 0x4AC98BE4
Mar 29 22:13:04.831: TFTP: Finished flash:SEP001BD4C6C021.cnf.xml, time 00:00:00
 for process 260
Mar 29 22:13:04.875: TFTP: Server request for port 50228, socket_id 0x4C9BAB88
C2811# for process 260
Mar 29 22:13:04.875: TFTP: read request from host 172.35.140.12(50228) via FastEthernet0/0.35
Mar 29 22:13:04.875: TFTP: Looking for P00308010200.loads
Mar 29 22:13:04.879: TFTP: Opened flash:P00308010200.loads, fd 10, size 461 for process 260
Mar 29 22:13:04.883: TFTP: Sending block 1 (retry 0), socket_id 0x4C9BAB88
Mar 29 22:13:04.883: TFTP: Received ACK for block 1, socket_id 0x4C9BAB88
Mar 29 22:13:04.883: TFTP: Finished flash:P00308010200.loads, time 00:00:00 for process 260
C2811#
Mar 29 22:13:10.723: TFTP: Server request for port 50229, socket_id 0x4AC98BE4 for process 260
Mar 29 22:13:10.723: TFTP: read request from host 172.35.140.12(50229) via FastEthernet0/0.35
Mar 29 22:13:10.723: TFTP: Looking for P00308010200.loads
Mar 29 22:13:10.727: TFTP: Opened flash:P00308010200.loads, fd 10, size 461 for
process 260
Mar 29 22:13:10.727: TFTP: Sending block 1 (retry 0), socket_id 0x4AC98BE4
Mar 29 22:13:10.727: TFTP: Received ACK for block 1, socket_id 0x4AC98BE4
Mar 29 22:13:10.727: TFTP: Finished flash:P00308010200.loads, time 00:00:00 for process 260
C2811#
Mar 29 22:13:23.503: TFTP: Server request for port 50213, socket_id 0x4C9BAB88 for process 260
Mar 29 22:13:23.503: TFTP: read request from host 172.35.140.12(50213) via FastEthernet0/0.35
Mar 29 22:13:23.503: TFTP: Looking for SIPDefault.cnf
Mar 29 22:13:23.519: TFTP: Opened flash:SIPDefault.cnf, fd 10, size 6203 for process 260
Mar 29 22:13:23.523: TFTP: Sending block 1 (retry 0), socket_id 0x4C9BAB88
Mar 29 22:13:23.527: TFTP: Received ACK for block 1, socket_id 0x4C9BAB88
Mar 29 22:13:23.527: TFTP: Sending block 2 (retry 0), socket_id 0x4C9BAB88
Mar 29 22:13:23.531: TFTP: Received ACK for block 2, socket_id 0x4C9BAB88
Mar 29 22:13:23.531: TFTP: Sending block 3 (retry 0), socket_id 0x4C9BAB88
Mar 29 22:13:23.531: TFTP: Received ACK for block 3, socket_id 0x4C9BAB88
Mar 29 22:13:23.531: TFTP: Sending block 4 (retry 0), socket_id 0x4C9BAB88
Mar 29 22:13:23.535: TFTP: Received ACK for block 4, socket_id 0x4C9BAB88
Mar 29 22:13:23.535: TFTP: Sending block 5 (retry 0),
 

[Advanced_Programs]

Forgot to mention that this endless sequence is basically the same either with an External TFTPD32 TFTP Server   or when using the Router as a TFTP Server.

Cisco does NOT recommend using the same CME Router as a TFTP Server for the purposes of loading the SCCP Firmware files in a Phone with SIP F/Ware.  I don't know why, but they recommend using an External TFTP Server.

So I tried with TFTPD32 TFTP Server, but the Syslog in the TFTPD32 TFTP Server shows basically the same sequence as the one I get when using the CME Router directly.

[Leo Laohoo]

SIP Images 5.x,6.x to SCCP Images 5.x/Later

http://www.cisco.com/c/en/us/support/docs/collaboration-endpoints/unified-ip-phone-7900-series/5455-handset-to-sip.html#siptosccp4

Cisco SIP IP Phone 7940/7960 Release 5.0 is functionally equivalent to Cisco SIP IP Phone 7940/7960 Release 4.4 in every way with the exception of the digital signature. The addition of the signed binary files feature prevents downgrading Cisco SIP IP Phone 7940/7960 Release 5.0 to an earlier release.

If your current SIP image is 5.x or 6.x, complete these steps in order to convert to the desired SCCP images 5.x or later:

1. Download the latest SIP load for your 7940/7960 and unzip/tar it in the tftp directory.

2. Download the latest SCCP load for 7940/7960 and unzip/tar it in the tftp directory.

3. Search for the file named gkdefault.txt in the SIP load, and open it with a text editor (such as Notepad).

4. Open gkdefault.txt, and go to the lineupgradecode:3,0x601,0x0400,0x0100,0.0.0.0,69,0x060412a,CP7940080001SIP060412A.sbin.

5. This references a SIP image.Change gkdefault.txt to the file name of the SCCP file you want to load. You need to replace060412a with 051117a and CP7940080001SIP060412A.sbin with CP7940080001SCCP051117A.sbin based on which version of SCCP image you have downloaded.

   For example, if you have downloaded cmterm-7940-7960-sccp.8-0-4.zip, it might look like:upgradecode:3,0x601,0x0400,0x0100,0.0.0.0,69,0x051117a,CP7940080001SCCP051117A.sbin

6. After saving changes, run cfgfmt -tsip_ptag.dat gkdefault.txt gkdefault.cfg. The cfgfmt.exe file and sip_ptag.dat file come with the SIP load.

7. Make sure the phone has your tftp server IP address configured and they can communicate.

8. The phone should now download the gkdefault.cfg file and the SCCP file you referenced in gkdefault.txt.

[Advanced_Programs]

Thank you for your reply.

I had already seen the Cisco Link that you posted in your reply.

And I thought for a while that the problem I'm having could be related to the SIP version currently loaded on the Phone, which is POS3-07-03-00

But that Cisco Link also includes this section:

SIP Images 7.x/Later to SCCP Images 5.x/Later

And according to this section, if the current SIP version is 7.x and I'm trying to move to SCCP 5.x (I want to move to 8.x actually), then there is no need to make any changes.

I guess I can try anyway, although it doesn't make any sense to me.

[e2andreas]

I had a similar issue.

You can switch from SIP to SCCP only if you use the same/or compatible Firmware version.

In my case it was 7.1.2.

What is your current FW version on the phone?