Known Issues and Recommendations
Interaction Server
The Known Issues and Recommendations section is a cumulative list for all 9.0.x releases of Interaction Server. 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 Resolved Issues section for each release describes the corrections and may list additional issues that were corrected without first being documented as Known Issues.
See also Internationalization Issues.
In some cases, IXN can unexpectedly terminate. It can happen if the incoming XML message for capture points contains a text data field longer than 4000 symbols with new lines or escaped symbols.
Workaround: Limit the description field to under 4000 characters, avoiding newlines and escaping symbols when possible.
| ID: IXN-7722 | Found In: 9.0.007.04 | Fixed In: 9.0.013.05 |
On Windows, when running Interaction Server in UTF-8 codepage mode, and with Oracle database using a version of Oracle ODBC driver higher than 12.2.0.1.0, many DB requests fail with error messages in the Interaction Server log (for example, ORA-01461: can bind a LONG value only for insert into a LONG column). This is due to a bug in the Oracle ODBC driver. While the issue is not critical (all database requests eventually succeed and Interaction Server works properly), it may have significant impact on performance as, after each failed request, Interaction Server has to re-establish a connection to the database and then send a new request. Genesys strongly recommends that you apply the official Oracle patch 29833984 to fix the bug.
| ID: IXN-7125 | Found In: 9.0.006.12, 9.0.007.03 | Fixed In: |
Windows installer does not contain countersignature. This makes Windows treat this installer as not signed after Genesys certificate expiration date.
| ID: IXN-6735 | Found In: 9.0.003.06, 9.0.004.07 | Fixed In: 9.0.004.11 |
Interaction Server applies the default strategy limit instead of the strategy limit specified for the router.
Workaround: Configure the strategy limit instead of the strategy limit for router.
| ID: IXN-6811 | Found In: 9.0.000.05 | Fixed In: 9.0.006.12 |
Interaction Server does not reset the handling timeout correctly when a secondary invited party rejects or misses the invitation. The timeout is incorrectly set to seconds instead of minutes.
| ID: IXN-6140 | Found In: 8.5.307.02 | Fixed In: 9.0.002.04 |
Starting with version 8.5.307.02, in rare cases, Interaction Server does not handle the pull from view requests properly. Interaction Server could execute the same DB request in loop infinitely under some conditions.
| ID: IXN-5831 | Found In: 8.5.307.02 | Fixed In: 9.0.001.07 |
In rare cases, Interaction Server behaves incorrectly when an agent does not answer on routing-based conference invitation.
| ID: IXN-5831 | Found In: 8.5.307.02 | Fixed In: 9.0.001.07 |
Interaction Server does not process any incoming requests when it is not able to initialize correctly on the first attempt. For example, when connection to Configuration Server is lost during initialization.
| ID: IXN-6147 | Found In: 8.5.302.12 | Fixed In: 9.0.002.04 |
Interaction Server does not send interactions from the segmented view to Orchestration Server for routing if the segment-total-limit parameter is not specified in the configuration of this view.
Workaround: Explicitly specify segment-total-limit in the view configuration.
| ID: IXN-5962 | Found In: 8.5.201.05 | Fixed In: 9.0.003.01 |
The routing-related health counters that were introduced in the 8.5.201.05 release are available via ping events and REST web interfaces, but not via webservice/SOAP requests.
| ID: IXN-4023 | Found In: 8.5.201.05 | Fixed In: |
On non-Windows platforms, the Web Service Capture Point works correctly only if you use UTF-8 as the codepage for Interaction Server. If you use any other codepage, the data received from the Web Service Capture Point might be corrupted.
| ID: IXN-3317, ESR-13023 | Found In: 8.5.000.10 | Fixed In: |
When a client sends RequestStopProcessing to Interaction Server while the Interaction Server database is unavailable, Interaction Server does not send a request to delete this interaction from the database after the database becomes available again. At the same time in this situation Interaction Server sends EventAck to the client.
| ID: IXN-2392, ESR-8208 | Found In: 8.5.000.10 | Fixed In: |
Internationalization Issues
Information in this section is included for international customers. Release numbers in the Found In and Fixed In fields refer to the English (US) release of Interaction Server unless otherwise noted in the issue description.
There are no internationalization issues for this product.