8.5.100.25
Local Control Agent Release Notes
Release Date | Release Type | Restrictions | AIX | Linux | Solaris | Windows |
---|---|---|---|---|---|---|
05/08/18 | General | X | X | X | X |
Helpful Links
Releases Info
Product Documentation
Genesys Products
What's New
This release contains the following new features or enhancements:
- You can now specify the maximum time that can elapse between LCA sending an application mode change request to an application and the application responding to that request and making the change. If the application does not respond within that time, LCA sets the application to Unknown mode. To specify this time interval, use the new option AppRespondTimeout, in the new [lca] section of the LCA configuration file.
- AppRespondTimeout
- Default value: 20
- Valid values: 1 to 60 seconds
- Changes take effect: After restart of LCA
- Specifies the time interval (in seconds) in which LCA expects a response to its switchover request to an application. If the application does not acknowledge the switchover request and make the mode change within this time, LCA puts the application in Unknown state.
- ImportantThis feature is not valid if heartbeat is configured.
- AppRespondTimeout
- When requested by Customer Care, debug functionality provided by the LCA debug options and corresponding environment variables can now also be configured on the LCA command line. Specifically:
Environment Variable | Configuration Option | Command-line Parameter |
---|---|---|
GCTI_CONN_DEBUG_ALL | x-conn-debug-all | -conn-debug-all |
GCTI_CONN_DEBUG_OPEN | x-conn-debug-open | -conn-debug-open |
GCTI_CONN_DEBUG_SECURITY | x-conn-debug-security | -conn-debug-security |
GCTI_CONN_DEBUG_SELECT | x-conn-debug-select | -conn-debug-select |
GCTI_CONN_DEBUG_TIMERS | x-conn-debug-timers | -conn-debug-timers |
GCTI_CONN_DEBUG_WRITE | x-conn-debug-write | -conn-debug-write |
For more information about these configuration options, refer to the Framework Configuration Options Reference Manual, available from here.
Resolved Issues
This release contains no resolved issues.
Upgrade Notes
No special procedure is required to upgrade to release 8.5.100.25.
This page was last edited on May 8, 2018, at 17:41.
Comments or questions about this documentation? Contact us for support!