I upgraded from CCM 4.1(3)sr2b to CCM 4.1(3)sr4d 2 weeks ago. After that I had a few phones that were set to Call Forward All to other numbers before the upgrade. After the upgrade, I had a few users who could not remove the CFWD All. I was able to pull the phone up in CCMAdmin, enter a number in CFWD All, do an update, remove the number and do an Update again and the issue was resolved. This weekend I upgraded to 4.1(3)ES94 because of a bug in 4.1(3)sr4d with 7970's. Ran into the same CFWD All issue, but the last fix isn't working this time. Been on the phone with TAC for over 3 hours now with no resolution. We've restarted the Database Layer Monitor service, the CallManager service and the RIS Data Collector service.
Re: Warning: Call Forward All Issue After Upgrades
Actually looks like User Error was the cause. We have a MOH server that was on an older version of CCM. Eventhough this server doesn't process calls or phone, it looks liek it was the problem server. This caused different version of AUPAIR.EXE to exist. I was told by TAC that this is the file that controls the CFWD All. Updated that server to the same version as my other servers, rebooted the Publisher then all the Subscribers and the MOH server and everything is currently working.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...