Force Peripheral updates in room series codecs?

[Bobby McGonigle]

Hello,

I'm having issues with the Cisco Quad Camera in relation to it's updates, as well as some p60 cameras in ce9.1.x, ce9.2.x, and ce9.3.x.

For a lot of SRK+ units I've acquired, the quad camera and codec plus have been on separate software versions. Some of which, "refuse" to upgrade the camera once connected.

The P60 just needs a simple power cycle and this usually triggers the upgrade.

With the quad camera, it's another story. I've attempted the following:

-Power cycle the quad camera; does not resolve

-Power cycle both codec plus and quad camera in tandem; does not resolve

-Factory reset the quad camera; does not resolve

-Factory reset the codec plus and quad camera in tandem; does not resolve

-Match software version of the codec plus to the effected quad camera, then upgrade to desired software; resolves in some, but not all instances

-Connected affected quad camera to a different codec plus or sx80 system and repeat; same results, no definitive "end-all, be-all" resolution

(All updates I've pushed have either been sent to the unit via TMS[15.5.0] or my machine directly, both yield the same outcome)

I was wondering if anyone knows of an xAPI command to the codec to trigger a peripheral (in this case a camera) to perform its upgrade cycle? I've checked the xAPI commands for 9.1/9.2/9.3 and I can't find one that may help.

Or

If they have a workaround to get the quad camera to upgrade other than the attempts I mention above.

I haven't attempted cisco TAC as of yet for their solution as of yet, but if this is going to continue as it has up to ce9.3.x, I'd much rather a solution I can implement on myself if at all possible.

Thanks

[Bobby McGonigle · Accepted solution]

Solution found.

Downgrade to cameras matching software with ".loads" file rather than ".pkg" and upgrade in the same manner.

[Tony Segneri]

I'm having the same issue: can you tell us how you upgrade the codec with the .loads file?  Does this have to be done through CUCM?

[elder.arias]

Hopefully this will answer your question (or for those that will have it ) as I ran into the same...

1) Installed the Collaboration Endpoint Software bundle in CUCM TFTP nodes, which included the firmware for different types of codecs, which is what I needed.

Example: cmterm-ce9_14_7-6e216653a72.k3.cop.sgn

2) Once installed the bundle, in addition to the pkg firmware files, I noticed that there is a "generic" .loads files in the TFTP server:

07 May,2021 11:20:19 337,517,344 s52010ce9_14_7-6e216653a72.pkg
07 May,2021 11:20:20 546,161,775 s52020ce9_14_7-6e216653a72.pkg
07 May,2021 11:20:20 194,503,463 bifrostce9_14_7-6e216653a72.pkg
07 May,2021 11:20:21 42,484,685 halleyce9_14_7-6e216653a72.pkg
07 May,2021 11:20:21 18,988,171 moodyce9_14_7-6e216653a72.pkg
07 May,2021 11:20:21 113,530,372 pyramidce9_14_7-6e216653a72.pkg
07 May,2021 11:20:21 318,575,124 s52030ce9_14_7-6e216653a72.pkg
07 May,2021 11:20:22 831,344,216 s53200ce9_14_7-6e216653a72.pkg
07 May,2021 11:20:22 209,963,871 s52040ce9_14_7-6e216653a72.pkg
07 May,2021 11:20:23 817,130,485 s53300ce9_14_7-6e216653a72.pkg
07 May,2021 11:20:31 5,921 ce9_14_7-6e216653a72.loads  <<<--- THIS FILE
07 May,2021 11:20:33 256 ce9_14_7-6e216653a72.loads.sgn

3) If you open/view this file from UCM TFTP CLI, you'll notice that it looks like a JSON file that includes the firmware/drivers needed for all types of supported codecs... See example below:

[
{
"product": "s52010",
"packageLocation": "s52010ce9_14_7-6e216653a72.pkg",
"version": "ce9.14.7 6e216653a72 2021-05-07",
"targets": [
"101790-2",
"101790-3",
"101790-4",
"101790-5",
"102330-0",
"102330-1",
"102330-2",
"102331-0",
"102331-1",
"102331-2"
],
"checksum": "621286b44e65b4bef85a3105f90a5c2e491af87d1c25e03df841029daa765c38578c882634f39ee6e910d58c5ca74f603b1a44cd20ad7d470b942654c9ba43f3"
},
{

"product": "Bifrost",
"packageLocation": "bifrostce9_14_7-6e216653a72.pkg",
"version": "ce9.14.7 6e216653a72 2021-05-07",
"targets": [
"73-102038-0",
"73-102038-0-dev",
"73-101864-0",
"73-101864-0-dev",
"73-101864-1",
"73-101864-1-dev"
],
"checksum": "9fbdbd55d393cc3502c48473d5f9e151d89f5b2d79550a4a8cf430362b14d818d985d19c1f3195b9174cd08ac695dda2f54801efbf68c3323c1c268a86f36205"
},
{
"product": "s52020",
"packageLocation": "s52020ce9_14_7-6e216653a72.pkg",
"version": "ce9.14.7 6e216653a72 2021-05-07",
"targets": [
"101730-0"
],

"checksum": "fb48f878d34efcfd46a53ba60c71bec9ac41e34ee3d60409ebe31963b24bd7801336df614bf0b26925d0842b475fc7f5c92e856a1e18e8d4b66be0fbe591782c"
},
{
"product": "s52030",
"packageLocation": "s52030ce9_14_7-6e216653a72.pkg",
"version": "ce9.14.7 6e216653a72 2021-05-07",
"targets": [
"100183-0",
"100183-1",
"100183-2",
"100183-3"
],
"checksum": "ee7f00eccac76065c381ec127df1efbd2b8a741a6abf134322d5dca78b5759349fb409c6b98b330fae34bc842e41c2effe92a547f3d8be41704f9a27ec783f95"
},

4) So when upgrading your device, instead of telling it to use the .pkg firmware (example: s52010ce9_14_7-6e216653a72.pkg, have it point to ce9_14_7-6e216653a72.loads and the device will parse the file and download the firmware/files that it needs.