CCM 5.0(4) and 7936 Phone

Unanswered Question
May 20th, 2007

Hi,


I am having a problem adding a 7936 IP Phone with CCM 5.0(4). The 7936 is stuck in "Upgrading 50% , Do not power off".


Can anyone tell am I missing anything here ?


Thanks,

Manu

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Rob Huffman Sun, 05/20/2007 - 16:12

Hi Manu,


I definately think you are hitting these 2 bugs;


CSCsg95361 Bug Details

Headline 7936 phones intermittently fails to upgrade to new load

First Found-in Version 5.0(4.1000.1)


Symptom:

7936 phones fail to upgrade to a different load when upgrade is attempted immediately after re-registration to CCM. This situation happens when the phones unregister first due to callmanager getting restarted or upgraded.



Conditions:

The 7936 phones running either cmterm_7936.3-3-1-0.bin or cmterm_7936.3-3-2-0.bin loads can fail to upgrade to new load if the phones first unregister from CCM, followed by re-registration and firmware upgrade attempt.


Workaround:

Change the default load on the CCM to cmterm_7936.3-3-3-0.bin or newer and upgrade the 7936 phones without stopping CCM service first.

If the phones experience this problem due to proactive workaround not performed, power cycling the phone recovers them in most cases.


Further Information

This problem was fixed first to address the issue reported by CSCed26422, but the phones coming out from manufacturing were not updated to newer load, thereby increasing the chances of failure



-------------------------------------------------------------------



CSCed26422 Bug Details

Headline 7936:App Load id got corrupted during upgrade/dowgrade of phone load

Condition:

Phone fails to upgrade to a new image when it encounter

a Callmanager failure , like callmanager getting restarted or upgraded.


Symptoms:

After the phone encounter a upgrade problem like getting stuck

or corrupted image. The phone need to be power cycled. once

the phone comeup back. The App Load id in system info menu could

display a blank space instead of dispalying the firmware name.


Workaround:

None. And there is no way to restore this problem.


This problem has been fixed in CMTERM_7936.3-3-3-0 or later.


Hope this helps!

Rob

Actions

This Discussion