01-21-2016 01:24 PM - edited 03-19-2019 10:37 AM
Hi Everyone
I wanted to know has anyone out there ever seen where the call history stops working for an entire office. I have an office where the call history stopped on the 18th of Dec and I've even swapped out phones and the call history still doesn't work. I've opened a case with TAC and they've did packet captures and phone log files but he told me he's never seen this before. Any help would be greatly appreciate and thanks in advance and have a great day.
Eric
01-21-2016 01:37 PM
On the latest CUCM releases missed calls is a CUCM service, do you have it listed in your CUCM services with enterprise subscription, which is the default?
01-21-2016 01:42 PM
That was one of the places I checked to see if it was set to enterprise subscription and it is.
01-21-2016 07:02 PM
Hi Eric,
The office that you mentioned, does it have phone models of all types or a specific type only? Are these phones registered to a specific server, pointed to specific TFTP or in a specific device pool compared to the other offices where call history works fine? If the exact cucm version and phone firmware versions can be shared then we can check for any known issues.
Manish
01-22-2016 07:20 AM
Hi Manish
All phones in that office are 7961 and they are all on the same server, TFTP, and device pool. And he Load file is SCCP41.9-4-2SR1-1S.
01-22-2016 08:04 AM
Hi Eric,
Very strange issue!
Can you provide the exact CUCM version?
Were the 7961's upgraded to 9-4-2x using just the firmware files or by installing a new device pack? The release notes for this firmware version do include this note;
Before you install the firmware release, you must ensure that your Cisco Unified Communications Manager is running the latest device pack.
Important:
If your Cisco Unified Communications Manager does not have the required device pack to support this firmware release, the firmware may not work correctly.
From;
Cheers!
Rob
01-22-2016 08:08 AM
Hi Rob
System version: 10.5.1.10000-7
Latest device pack installed, I just have never seen this before and it so strange.
01-22-2016 09:30 AM
Hi Eric,
I don't see any bugs related to this type of issue in either the CUCM version or firmware version. Hopefully TAC may be able to help here, but I'm guessing because you are on the initial 10.5.1 release they may ask you to upgrade to 10.5.(1)su1a or better yet 10.5.(2)su3.
Sorry man!
Cheers!
Rob
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide