Cisco Bug: CSCvs71038 - CDR dateTimeConnect is incorrect for Hunt pilot reports
Jul 21, 2020
- Cisco Unified Communications Manager (CallManager)
Known Affected Releases
11.5(1.10000.6) 12.0(1.10000.10) 12.5(1.10000.22) 12.5(1.11900.146)
Symptom: Hunt Pilot CDR reports shows wrong date in header. Conditions: When searching for Hunt pilot reports from CDR, we are getting wrong time. Getting correct details/time stamp in scroll bar. DR report tries to fetch the records without honoring entries in "datetimeconnect" and "datetimestamptconnect".As as result customer is seeing invalid report. Ideally datetimeconnect should be between datetimeorigination and datetimedisconnect but in some case some wrong entries were stored for datetimeconnect.But without considering this CDR generates report and it is ending up in misleading information to customer So we have to put one more condition for report generation in such a way that datetimeconnect should always greater than datetimeorigination.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases