Known Issues and Recommendations
Recording Processor Script
The Known Issues and Recommendations section is a cumulative list for all 8.5.x releases of Recording Processor Script. This section provides the latest information on known issues and recommendations associated with this product. It includes information on when individual items were found and, if applicable, corrected. The Corrections and Modifications section for each release may list additional issues that were corrected without first being documented as Known Issues.
See also: Internationalization Issues
Recording Processor Script now starts faster when connecting to a Configuration Server with more than 2000 objects configured. Previously, in this scenario, Recording Processor Script would take up to an hour to start causing unresponsive hosts.
| ID: GIR-1496 | Found In: 8.5.000.31 | Fixed In: 8.5.000.33 |
The Recording Processor script might unexpectedly terminate when removing skills from multiple agents.
| ID: GIR-735 | Found In: 8.5.000.22 | Fixed In: 8.5.000.25 |
The Recording Processor script supports the ability to connect to multiple ICON database servers for backup or multi-site support. The DB Server connection configuration in the Recording Processor Script configuration file are keyed on the hostname. Therefore, it is normally expected that each DB Server run on a separate host. If multiple DB Servers are running on the same host, you must use a different dbserver_host value to uniquely identify the connection.
| ID: GIR-632 | Found In: 8.5.000.22 | Fixed In: |
The Recording Processor Script might unexpectedly terminate if an agent login's ID contains non-numeric characters and that agent login is deleted from a Person object.
| ID: GIR-601 | Found In: 8.5.000.22 | Fixed In: 8.5.000.25 |
If your Genesys Interaction Recording deployment uses an MS SQL ICON database, and also uses non-ASCII characters (0-127) for agent names or metadata, the Recording Processor Script might encounter encoding errors preventing the call from being saved to the SpeechMiner database. To work around this, you must update the Recording Processor script to a different character set. Please contact Customer Care for additional information.
Note: This work around will avoid the errors, but SpeechMiner might not process the data correctly.
| ID: GIR-535 | Found In: 8.5.000.20 | Fixed In: 8.5.000.21 |
For certain multi-switch transfer scenarios, where a call gets re-transferred back to a previously used switch, some call segments may not be searchable as part of the same call interaction.
| ID: GIR-417 | Found In: 8.5.000.22 | Fixed In: |
To minimize memory use, the Recording Processor script may occasionally need to be restarted if operating in an environment where the connection to the Configuration Server is not stable.
| ID: GIR-402 | Found In: 8.5.000.21 | Fixed In: |
The Recording Processor python script can receive metadata from the Media Control Platform (MCP) using SSL (if enabled). The pyOpenSSL package is required to enable SSL between the MCP and Recording Processor. However, certain versions of pyOpenSSL are susceptible to the heartbleed defect in OpenSSL. To workaround this, Genesys recommends using a OpenSSL version that does not contain the heartbleed defect (for example, pyOpenSSl version 0.12).
| ID: GIR-187 | Found In: 8.5.000.20 | Fixed In: 8.5.000.22 |
Internationalization Issues
Information in this section is included for international customers.
There are no internationalization issues for this product.