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
NoRN - This is already documented in product limitations.
| ID: GIR-734 | Found In: 8.5.2 | Fixed In: |
The Recording Processor script supports the ability to connect to multiple ICON database servers for backup or multi-site support. The dbserver connection configurations in the RP config file are keyed on the hostname. Therefore, it is normally expected that each dbserver run on a separate host. If multiple dbservers are running on the same host, you must still use a different dbserver_host value to uniquely identify the connection. An IP address or hostname alias could server this purpose.
| ID: GIR-632 | Found In: 8.5.0 | Fixed In: |
Customers should only use Python 2.7.x on Windows.
| ID: GIR-418 | Found In: 8.5.000.17 | Fixed In: |
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.15 | Fixed In: |
Not required.
| ID: GIR-408 | Found In: 8.5.0 | Fixed In: |
The python interpreter may pause execution on a Windows system when running the RP using the command console and clicking on the console. This may occur when the console window is running under QuickEdit Mode. To avoid this issue, do not use QuickEdit Mode in the RP's console window, or run the RP process in the background without a visible console window.
| ID: GIR-406 | Found In: 8.5.000.15 | 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.15 | Fixed In: |
If a freshly installed RCS fails to startup due to some configuration problem, it sometimes partially initializes the keystore file, such that it remains in an invalid state. Subsequent starts of RCS fail because the keystore file is invalid.
A work around for this problem is to delete the keystore file (default is keystore.bin located in the RCS installation root directory).
| ID: GIR-220 | Found In: | Fixed In: |
Internationalization Issues
Information in this section is included for international customers.
There are no internationalization issues for this product.