[cisco-voip] dev packs - ugh

Sat Aug 18 10:47:38 EDT 2018

When it comes to dev packs the “bugs” listed aren’t really bugs. They are just the identifier we use to track the changes in the device xml files that get inserted into the database for device definitions.

Recalling the ES vs SU thread, the truth is in the versioning. Dev packs are generated with engineering specials, so their versioning follows the same rules when comparing to an SU. This also means they are definitely cumulative.

The good part about listing the defect IDs used for each device update means that if you aren’t sure if an SU, devpack, or ES you got includes the change just look up the defect on Cisco.com<http://Cisco.com>. All the versions with the fix are listed (and accurate).

Lastly, it’s pretty common these device update bugs are put into an ES well before the devpack is released. That’s how a fix may end up in an SU for one version before a devpack for another.

-Ryan

On Aug 18, 2018, at 10:04 AM, Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>> wrote:

On Aug 17, 2018, at 7:13 PM, Anthony Holloway <avholloway+cisco-voip at gmail.com<mailto:avholloway+cisco-voip at gmail.com>> wrote:

Each device pack file contains all of the logic to add new firmware, and add support for all of the phones contained within it.  So yes, they're cumulative.

Ok. Good to know.

When you say that SUs are not listed, do you mean the matrix?  If so, that's probably because it's not a factor.  Just match Major.Minor.Patch.

I can work with that. For now.... :)

Are you referring to Table-2 in the Device Pack Readme when you say "shows database updates for" or "does not show updates for"?

That's just a list of the defects fixed/addressed by the device pack, not which phones are getting updates.

I see that they are there to address a defect, but the fact that there is a database update means I can’t get away with just installing the updated firmware. The devpack is need to address this bug. Yes?

Personally, I would not use any version, other than the one listed on the matrix.  In your case, that would rule out 11.5(1.16083) device pack for me.  If it's too new for Cisco to put out proper documentation, then it's too new for me to use.  The reason is simple: I would not be able to cite documentation stating that the version is on the supported version list (the matrix).  And being able to cite documentation is important to me.

Ok - so I went back and took a second look. In the matrix, the links to the dev packs are different, based on what the model needs. So, under the Unified CM 11.5(1) column, although the all say “cmterm-devicepack11.5.1<https://software.cisco.com/download/release.html?i=!y&mdfid=286306100&softwareid=282074299&release=11.5(1.11007)&os=>”, they link to different published versions. You can see the date below the text which indicates this. I missed this the first time around.

Lastly, it sounds like you already have support for these phone models, if you're seeing the device defaults listed in your 11.5(1)SU4.  So, are you trying to add support, or just upgrade the firmware on them?

Yes - support is there with firmware shipped with 11.5(1)su4. I do want to update the firmware to the latest version, but I also want to ensure I have the latest database updates to address any of the bugs. Specifically: CSCvj22837 : UCM Configuration files for 8832/8832NR 12.1.1 release included in 11.5(1.15078)

If the packs are cumulative, I might as well load the latest. Which has been referenced in the matrix for other phones.

On Fri, Aug 17, 2018 at 4:13 PM Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>> wrote:

I have to tell you, figuring out when to install a dev pack or not is confusing as hell to me. The documentation never includes (or is updated to include) SUs.

Can I assume (*scream*) that if I need any of the database updates included in the readme for a dev pack that is dated after my SU, that I need to install that dev pack? Is going by date enough?

Are dev packs cumulative? Their readmes don't appear so. A database update note that appears in one dev pack does not appear in the later dev pack release notes.

Here's my scenario:

I'm on CUCM 11.5(1)SU4 (dated 05-FEB-2018) and we're looking to deploy some 8832 and 8865 phones. CUCM 11.5(1)SU4 has default firmware listed for both these phones in the readme. This is what the TAC told me indicates that v11.5(1)SU4 supports the phones without the need for a dev pack.

When I look to the dev pack downloads page, I see the following dev packs available that are dated after 05-FEB-2018:

11.5(1.15078) - 04-Jun-2018
11.5(1.16083) - 13-Aug-2018

v11.5(1.15078) shows database updates for 7800/8800 series phones, 8832 conference phone. Fine, I'm good with that.
11.5(1.16083) does not show updates for any of the 8800 series phones, but does show updates for "Collaboration Endpoint Software" - which I think I might need.

So, is my process correct - I need to install only 11.5(1.16083) since it's cumulative and includes v11.5(1.15078) which has things I need? And I don't have to worry about any of the others because they were dated earlier than 05-FEB-2018?

---
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><mailto:lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>

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

[University of Guelph Cornerstone with Improve Life tagline]

_______________________________________________
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
_______________________________________________
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180818/2f12853c/attachment.html>