End-User Issues Resolved in 17.1
The following table provides a summary of issues reported by customers that have been resolved in this release.
| Salesforce ID | Issue Summary |
|---|---|
| 734512/749277 | Files that were transcoded from WAV to WAV with FLE could not be played |
| 734760 | When the database was not available at start up, the CometDaemon service did not look at cached settings |
| 689384 | Improper handling for screen capture error code 13 |
| 760432 | Clicking I have a question on a QA form resulted in a database error |
| 753792 | "Agents Needing Evaluation Detail" report failed to run |
| 773363 | QA evaluations could not be performed using the HTML5 Interaction Player |
| 738837 | After transcoding encrypted calls from the Web Portal, audio, 0kb wav, and mp3 files were missing |
| 774948 | Ad hoc reports didn't show the correct data based on the date after the date was changed |
| 774624 | Broadcaster CTI Core failed to connect after the broadcaster was stopped and then restarted as a buddy core |
| 763232 | Perform QA action generated a null exception |
| 770179 | When using the Voice Board Reloading feature, phones were re-registered immediately after being deleted from a voice board |
| 780168 | The Publish button in the ad hoc report builder was disabled |
| 767570 | NICE Uptivity Survey caused CPU usage to hit 99% |
| 774916 | In Cisco built-in bridge recording integrations, CTI Core replied with a SIP 200 OK message without first configuring the IP Address |
| 783350 | In a Cisco TAPI-BiB integration, there was no audio for the call after it was transferred or conferenced for the second part of the call |
| 786210 | In a Cisco TAPI-BiB integration, calls were not recording after the agent placed a caller on hold and then made an outbound call |
| 774963 | CTI Core did not retry a single step conference after receiving an "invalidObjectType" failure |
| 784711 | Transcoder did not restore a database connection after the overall connection was restored |
| 789394 | Screen recording clients did not sort correctly in the System Status report |
| 796193 | The Archiver service was unable to insert large Device Alias values into the database |
| 795375 | CTI Core stopped sending screencapturestop messages to certain NICE Uptivity Screen Recording servers |
| 791373 | Using angle brackets in Active Directory authentication resulted in password issues |
| 797183 | The Live Info Broker service was not properly releasing ports |
| 808298 | An index was added to speed queries against a large database table (enhancement request) |
| 812626 | Attempting to retrieve a disputed QA evaluation triggered a null exception |
| 767245 | Audio quality was degraded in NICE Uptivity Survey |
| 821585 | QA evaluations did not load if the user selected Enable Arbitration on the form |
| 821494 | Searching for certain agents by name triggered a search timeout |
| 825956 | In some cases, CTI Core generated excessive logging |
| 831544 | An incorrect DLL file caused CTI Core to crash during patch application |
| 826415 | Secure LDAP (LDAPS) login using Active Directory failed |
| 837067 | In some cases, record_end events were generated after a new call had already begun |
| 835316 | Some agents were missing outbound calls |
| 838759 | In a Cisco TAPI-BiB integration, Caller ID information was sometimes incorrect |
| 840342 | Calls that reached max duration were incorrectly flagged as failed recordings |