[cisco-voip] 8832s

Mon Apr 30 10:37:24 EDT 2018

Hi Jason,

Please try booting from the alternate image as Charles mentioned.  Here is the process for the 8832 phones.

1. Hold the * key while connecting the power to the 8832.
2. After the LED bar light turns ON green and then OFF, you can release the * key.
3. The 8832 should proceed to boot from the image in the alternate partition.

The problem is caused by the older (downgraded) firmware not recognizing the USB-C to ethernet adapter the phone is using, therefore no network connectivity.  If you can boot off the image that the phone came with the ethernet adapter will be detected.

We are making changes to prevent the phone from downgrading to a version that is not compatible with the connected ethernet adapter.

Joe

On Apr 30, 2018, at 9:18 AM, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:

But in this case, it was “older” firmware on CUCM. ☹

It’s not always very clear which version will be available in the CUCM version. I remember it was easy. They would list default firmware versions per version. Now it’s a bit harder to find.

---
Lelio Fulgenzi, B.A. | Senior Analyst
Computing and Communications Services | University of Guelph
Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1
519-824-4120 Ext. 56354 | lelio at uoguelph.ca <mailto:lelio at uoguelph.ca>

www.uoguelph.ca/ccs <http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram, Twitter and Facebook

<image001.png>

From: cisco-voip <cisco-voip-bounces at puck.nether.net> On Behalf Of Anthony Holloway
Sent: Monday, April 30, 2018 9:07 AM
To: Charles Goldsmith <wokka at justfamily.org>
Cc: cisco-voip (cisco-voip at puck.nether.net) <cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] 8832s

I wish CUCM didn't ship with newer phone firmware.

Since Cisco already drops support for all firmware older than the most recent firmware:

- For each IP Phone model, once Cisco releases a new firmware version, the older versions are no longer supported.
- Cisco expects customers who encounter a problem on an older version of firmware to test the latest firmware on a subset of phones in order to confirm that the problem still exists.
Source: http://www.cisco.com/c/en/us/support/docs/collaboration-endpoints/unified-ip-phone-7900-series/116684-technote-ipphone-00.html <http://www.cisco.com/c/en/us/support/docs/collaboration-endpoints/unified-ip-phone-7900-series/116684-technote-ipphone-00.html>

And most people agree that you should upgrade firmware before a CUCM upgrade anyway, just remove firmware from CUCM.

Not too mention it clutters up TFTP.

I also think that the firmware should be decoupled from the Device Packs.  When adding support for a single model phone, rarely am I also trying to upgrade 100% of the phones in the environment too.

On Sun, Apr 29, 2018 at 8:22 PM Charles Goldsmith <wokka at justfamily.org <mailto:wokka at justfamily.org>> wrote:
Since the 8832 is a dual bank phone, shouldn't it have the old image on it in the backup bank?  Maybe hardcoding the old image on the phone configuration and doing a reset will cause it to boot from it?

On Sun, Apr 29, 2018 at 7:06 PM Ryan Huff <ryanhuff at outlook.com <mailto:ryanhuff at outlook.com>> wrote:
Sounds like the ole’ ‘step upgrade’ issue that plagued the 79xx series back in the 8.x days ....

My guess is they don’t actually need RMA’ed, just the easiest way to deal with it .... 

I’d flash the phones and advertise an isolated tftp server to them with the firmware load and XML bootstrap file. The phones aren’t working now, so flashing them and then still not getting them to load right isn’t going to make it any worse.

Use DNS in the DHCP scope in your isolation network with the TFTP server and pcap/debug the DNS queries to see the bootstrap and load files it’s looking for. 

In the 79xx series back in the day when I would perform this Lazarus trick for some lucky customers; the bootstrap filename was XMLDefault.cnf.xml. Not sure if it’s the same nowadays though.

Here is the Cisco doc on the procedure for the older stuff .... worth a shot but not sure if it still works on the newer gear.

https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200582-Update-Cisco-IP-Phone-Firmware-through-T.html <https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200582-Update-Cisco-IP-Phone-Firmware-through-T.html>

-Ryan-

On Apr 29, 2018, at 18:53, Jason Aarons (Americas) <jason.aarons at dimensiondata.com <mailto:jason.aarons at dimensiondata.com>> wrote:

I have a customer with four 8832 conference room phones. Their CUCM was running version 12.0.1 of the 8832 firmware. These phones shipped with version 12.0.1SR2. When they registered the first two phones they downgraded from 12.0.1SR2 to 12.0.1 and are now unusable. They sit on “Connecting” after booting up. They do not get an IP address. You cannot set an IP address manually. If you reset the phone it doesn’t fix it, nor does a factory reset <https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cuipph/8832/english/adminguide/cs88_b_conference-8832-admin-guide-cucm/cs88_b_conference-8832-admin-guide-cucm_chapter_01011.html> allow the phone to revert to the firmware they shipped with. Cisco TAC says they must be RMA’d. We upgraded CUCM to 12.0.1SR3 and the other two phones upgraded fine from 12.0.1SR2 to 12.0.1SR3.

Does anyone have any ideas on what we could do to fix these phones other than RMAing them?

Get Outlook for Android <https://aka.ms/ghei36>

This email and all contents are subject to the following disclaimer:
"http://www.dimensiondata.com/emaildisclaimer" <http://www.dimensiondata.com/Global/Policies/Pages/Email-Disclaimer.aspx>
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip <https://puck.nether.net/mailman/listinfo/cisco-voip>
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip <https://puck.nether.net/mailman/listinfo/cisco-voip>
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip <https://puck.nether.net/mailman/listinfo/cisco-voip>_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180430/ffa9b1a7/attachment.html>