FYI for the archives.<div><br></div><div>This was a firmware issue, since these phones were refurbs out of the box, they had an older version of firmware (7.2.4 in this case) and 8.1.2 was current on my upgrade, and you cannot go from 7.2.4 directly to 8.1.2 (had to hop through 8.1.1).</div>
<div><br></div><div>If anyone has more questions on this, let me know, case is closed</div><div><br></div><div>Thanks for the assist Wes.</div><div><br></div><div>Charles<br><br><div class="gmail_quote">On Tue, Jul 6, 2010 at 12:35 PM, Charles Goldsmith <span dir="ltr"><<a href="mailto:wokka@justfamily.org">wokka@justfamily.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">I just opened a TAC case on an interesting thing that seems like a bug. I upgraded our 7.1.3 CUCM last week to 8.0.2c, and after testing for several hours, everything seemed perfect.<div>
<br></div><div>Fast forward to today, I get asked to add a few new phones with BLF's programmed. The phones are 7960 and program fine with the extension, however, the BLF's are empty, the Label doesn't show, let alone the BLF symbol on the display. Editting an existing phone that has BLF's act normally.</div>
<div><br></div><div>Doing a super copy of the working phone (one on my desk) doesn't resolve the issue, still no BLF's, but the Line 1 copies just fine.</div><div><br></div><div>Very bizarre behavior. A few quick searches through the release notes on 8.0.2 and 8.0.2c didn't show anything specific to this issue, however there are two BLF caveats, but they have to do with empty partitions, and I'm using non-empty partitions with these phones and BLFs.</div>
<div><br></div><div>Anyone else run into this issue?</div><div>Charles</div>
</blockquote></div><br></div>