02-21-2013 01:44 PM - edited 03-16-2019 03:52 PM
Curious....has anyone successfully upgraded from 9.2.x to 9.3.2.11 SCCP firmware on Cisco 8945 telephone over a POE connection? I have handful of the 8945 phones and have been able to upgrade over POE in the past to prior firmware releases. I have to plug in a AC adapter to successfully upgrade to SCCP 9.3.2.11 firmware. The 8941 phone upgrades without problems to 9.3.2.11 over POE without problems.
Have worked with Cisco TAC but unable to resolve.
02-21-2013 02:37 PM
Hi Alan,
I upgrade to version 9.3 firmware over POE and the upgrade goes well without any failure.
I face another problem after the upgrade, 8945 phone can't access corporate direcotry. due to that I revert back.
is this the problem you are talking about
Anas
02-21-2013 04:18 PM
Thanks for replying Anas, I don't recall having problems with the Directory but will check when I get back in the office tomorrow. I'm experiencing problems with the 8945 phones not requesting the firmware from the TFTP server over POE on bootup.
When I plugin AC adapter the phones upgrade without problems consistently, but over POE all phones fail to upgrade.
We are running 8.6.2 on the CUCM and the different switch types we are using are 3526 and 6506.
best,
Alan B,
02-21-2013 07:49 PM
Anas, for the directories issue check out this document: https://supportforums.cisco.com/docs/DOC-25559. If you did not install the device pack this is a known problem and requires the device pack for directories to work properly. Reason being due to security by default on 9-3-1 the phones cannot download their TFTP config files properly causing the phone services not to work correctly.
Alan, I also have successfully upgraded an 8945 firmware to 9-3-2 using POE.
02-22-2013 12:52 AM
Hi Joe,
thanks for your reply, it is really helpful. it describes my issue exactly
Anas
02-21-2013 07:57 PM
Alan, I have successfully updated 8945 phones to SCCP 9.3.2 using PoE. I'm not sure why you are having difficulty.
I'm using CUCM 9.0 and 2960 PoE switches. Ultimately I'm going to the 9.3.2 SIP firmware, but since you can't upgrade directly to SIP 9.3.2 from firmware versions earlier than 9.3.1, we routinely let unconfigured phones upgrade themselves to the SCCP 9.3.2 firmware so they can make it to the latest SIP firmware.
02-25-2013 12:21 PM
Alan, what switch model are you using? I tested with a 3560 running c3560-ipbasek9-mz.150-1.SE3.
02-26-2013 06:13 PM
I left out an important piece of information, our CUCM sits behind a firewall.
We are using the FWSM's and after seeing the feedback here I worked with one of our fireall network techs to place the phone on the CUCM network and the 8945 IP phone upgraded to 9.3.2 without problems.
Our firewall tech mentioned that our Unix team experienvced problems with TCP-SACK sending large amounts of data through the FWSM's and had to make adjustments to their servers.
The BUG CSCsi54863 looks like it describes potential problems with TCP-SACK support or lack of. I see in the packet captures the from the 8945 it negotiates TCP-SACK. I'm working with our Firewal team now to see if we can resolve this problem.
04-07-2013 07:00 PM
OK, we fixed the problem by upgrading our FWSM to a release that allowed us to disable TCP-SACK. Of all the different phone types we have the 8945 was the only one that was affected by TCP-SACK. The way I understood it, was the FWSM was allowing the 8945 IP phone to negotiate TCP-SACK with the CUCM. Was seeing alot of duplicate and re-transmits in a packet capture.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide