As of February 1, 2012, Genesys is no longer an affiliate of Alcatel-Lucent; any indication of such affiliation within Genesys products or packaging is no longer applicable. Please see the Genesys website at http://www.genesys.com for more details.
This release note applies to all 8.1 releases of Orchestration Server (ORS).
Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. For specific information on any third-party software used in this product, see the Legal Notices for Orchestration Server. Please contact your Customer Care representative if you have any questions.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is an update for this product. This release does not contain any new features or functionality.
This release contains the following corrections and/or modifications:
An issue with compiled script caching on Linux platform which under rare scenarios lead to execution of an incorrect JavaScript expression, is fixed. The issue was introduced in version 8.1.401.11.
The issue occurred under specific conditions, for example, a strategy did not recognize the end of the applied treatment because the request ID that came with dialog.playsound.done event did not match the stored value and, as a result, the call followed default routing.
(ORS-5010)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is an update for this product. This release contains the following new functionality:
With this ORS release, the libcrypto.so.3 library version has been updated to 3.0.15. (ORS-5002)
This release contains the following corrections and/or modifications:
ORS no longer terminates unexpectedly. Previously, at rare instances, ORS could terminate during background cache reloading. (ORS-5008)
Now ORS on Linux OS supports FIPS mode when downloading SCXML strategies from a Web Server. Previously, in this scenario, the connection in FIPS mode failed with the Insufficient randomness error. (ORS-4986, ORS-4926)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is an update for this product. This release contains the following new functionality:
Support for Red Hat Enterprise Linux 9. See the Genesys Supported Operating Environment Reference Guide: Orchestration Server page on the Genesys Documentation website for more detailed information and a list of all supported operating systems.
Note: For installing on RHEL 9, you must download and use a separate installation package.(ORS-4895)
ORS now supports TLS version 1.3.
(ORS-4896)
This release does not contain any corrections and modifications.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is an update for this product. This release contains the following new functionality:
Support for Windows Server 2022. See the Genesys Supported Operating Environment Reference Guide: Orchestration Server page on the Genesys Documentation website for more detailed information and a list of all supported operating systems.
(ORS-4960)
With this ORS release, the OpenSSL library version has been updated to version 3.x. With OpenSSL 3.x, in order to enable FIPS support in ORS, it is not enough to configure the option scxml\fips-enable, additional configuration steps are necessary. Also, there is a limitation in Linux when FIPS is enabled, the TLS connection may fail with an Insufficient randomness error.
This release contains the following corrections and/or modifications:
You can now set a cache size of more than 2 Gigabytes (GB) for the max-preprocessor-cache-size, max-assembled-cache-size, and max-compiler-cache-size options in the scxml section. Previously, these option values were not allowed to exceed 2 GB. (ORS-4905)
An issue that prevented the recovery process from restoring acdq property of a voice call is fixed. The issue occurred when ORS was configured for recovery of voice calls without persistence. (ORS-4946)
ORS now has an improved logging mechanism for cache usage. (ORS-4573)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is an update for this product. This release contains the following new functionality:
This release does not contain any corrections and modifications.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is an update for this product. This release contains the following new functionality:
Beginning with this release, ORS on Windows OS uses the Microsoft Visual Studio C++ 2019 Redistributable Package. The 2019 Redistributable Package is included in the ORS IP and is installed automatically. (ORS-4811)
Controlling session lifetime functionality is extended for deployments without Cassandra persistence. Previously, a connection to Cassandra was required for this functionality. The maximum session age in seconds is configured in the max-session-age option or in the _maxtime attribute in the <scxml> action element.
The following new ORS options are introduced to support this enhancement:
extend-max-session-age-action
Option section: orchestration in an ORS Application object
Configuration object: ORS Application object
Default value: false
Valid values: true, false
Value changes: Dynamically
This option is used to enable or disable session termination. It is semi-dynamic for sessions started before changing the value of the option and fully dynamic for new sessions. That is, changes take effect immediately for sessions that are started after the value of this option is updated.
max-session-age-notification-timeout
Option section: orchestration in an ORS Application object
Configuration object: ORS Application object
Default value: 15
Valid values: Any integer from 0 to 86400 (seconds)
Value changes: Dynamically (for new sessions when extend-max-session-age-action is set to true)
This option controls when ORS notifies a session in advance that it is about to be terminated using the session.terminating.forcedly event by default. This option allows to specify the time in seconds before reaching max session age at which to send the event.
This option value should be less than the max-session-age or _maxtime values. Otherwise, the option is ignored (set to 0), and no notification event will be sent.
override-notification-event-name
Option section: orchestration in an ORS Application object
Configuration object: ORS Application object
Default value: An empty string (the default event name is used if no value is provided)
Valid values: Any notification event name
Value changes: Dynamically (for new sessions when extend-max-session-age-action is set to true)
This option is used to specify any notification event name instead of the default event. It is not recommended to override the notification event with something that starts with error., because this may potentially break backward compatibility. For some specific strategies generated by recent versions of Designer for Azure, you can override this recommendation.
If you rely on _genesys_terminate_event processing when Cassandra is in use, set this option to _genesys_terminate_event.
(ORS-4795)
For the Microsoft Windows platform, the time taken for concurrent loading of large strategies that include a high number of files is improved. (ORS-4818)
Now, ORS always sends the DeleteVirtualCall request to URS when MediaServer stops interaction processing and an SCXML session ends due to any reason other than interaction.deleted. Previously, ORS may randomly not send the DeleteVirtualCall request to URS in very rare race conditions during the above scenario. (ORS-4806)
When connection to Stat Server is lost, ORS attempts to reconnect to both the primary and backup Stat Server. Previously, in some rare scenarios, ORS was repeatedly reconnecting to the last StatServer without trying to connect to the backup Stat Server. (ORS-4567)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new functionality:
A new option, sessionfm-fetch-esp-timeout, is introduced to specify timeout in seconds that ORS will use when the timeout attribute is omitted in the <session:fetch> action with the esp method. Previously, for such requests ORS used the hardcoded value of 60 seconds.
sessionfm-fetch-esp-timeout
Option section: orchestration in an ORS Application object
Configuration object: ORS Application object
Default value: 60
Valid values: Any integer from 0 to 86400
Value changes: Immediately
(ORS-4756)
A new option, user-data-for-esp-hints-tpserver, is introduced to ensure that the an interaction's user data is added to the ESP request sent to the third-party server specified in the tpserver property of the hints object of the <ixn:terminate> action. Previously, the ESP request was sent without user data.
user-data-for-esp-hints-tpserver
Option section: orchestration in an ORS Application object
Configuration object: ORS Application object
Default value: false
Valid values: true, false
Value changes: Immediately upon notification from Configuration Server
(ORS-4789)
This release does not contain any corrections and modifications.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is an update for this product. This release contains the following new functionality:
Now, ORS successfully handles execution of multimedia actions (createmessage, sendmessage, getcontent, and gettranscript) when they contain attributes with values of an improper type, and publishes a corresponding error event into the session. (ORS-4719)
The Hiding Sensitive Data feature is now also applicable to logging of the headers of HTTP messages triggered by the <session:fetch> action. To enable the feature, configure the ors-regex-<name> options in the log-filter-data section. If the options or section are not configured, a default rule, ors-regex-auth;hide=(?<=Authorization: ).* is applied and the value of the Authorization header is hidden in the log. (ORS-4636)
For more information on this enhancement, see the Hiding Sensitive Data topic in the Orchestration Server 8.1.4 Deployment Guide.
The cache_error metric name no longer appears as Undefined when ORS fails to cache a document. (ORS-4675)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is an update for this product. This release contains the following new functionality:
ORS now supports Red Hat Enterprise Linux 7 on ESXi 7 (as of April 7, 2022). (ORS-4689)
See the Supported Operating Environment: Orchestration Server page for more detailed information and a list of all supported operating systems.
mcr-pull-gradual-start
Option section: orchestration in an ORS Application object
Configuration object: ORS Application object
Default value: true
Valid values: true, false
Changes take effect: Immediately upon notification from the Configuration Server
When this option is set to true, ORS starts pulling with only 1 interaction per cycle for the strategy, until sessions for that strategy are successfully started (that is, the strategy is confirmed). Then, ORS starts pulling for that strategy according to the cycle quota. If creation of the session fails (strategy is non-confirmed), the pulling rate for this strategy drops to 1 until the strategy is confirmed again. Any changes in strategy configuration (Enhanced Routing Script) will change the status of the strategy to non-confirmed.
(ORS-4641)
fail-session-if-not-cached
Option section: scxml in an ORS Application object
Configuration object: ORS Application object
Default value: false
Valid values: true, false
Changes take effect: After restart
When this option is set to true, session creation fails if an SCXML document cannot be placed into the compiled document cache.
(ORS-4641)
Use these options to increase the send buffer for sockets used by CURL, and the internal CURL receive buffer.
http-buffer-size
Option section: scxml in an ORS Application object
Configuration object: ORS Application object
Default value: 131072
Valid values: Any integer between 1024 and 524288 (CURL_MAX_READ_SIZE)
Changes take effect: After restart
This option sets the CURLOPT_BUFFERSIZE option that represents the read buffer size, in bytes.
curl-socket-rcv-buffer-size
Option section: scxml in an ORS Application object
Configuration object: ORS Application object
Default value: None
Valid values: Determined by OS; 0 indicates that the option will not be set
Changes take effect: After restart
This option sets the SO_RCVBUF option (receive buffer size) for the socket used by CURL. SO_RCVBUF is set only if the new value is bigger than the current socket buffer size.
curl-socket-snd-buffer-size
Option section: scxml in an ORS Application object; Annex in an Enhanced Routing Script object
Configuration object: ORS Application object; Enhanced Routing Script object
Default value: None
Valid values: Determined by OS; 0 indicates that the option will not be set
Changes take effect: After restart
This option sets the SO_SNDBUF option (send buffer size) for the socket used by CURL. SO_SNDBUF is set only if the new value is bigger than the current socket buffer size.
For more information on the new options, refer to the ORS Deployment Guide.
(ORS-4471)
This update addresses an issue which caused an increase in memory usage when recompiling a SCXML strategy with the <foreach> element. Previously, when an SCXML strategy's size exceeded the compiled document cache size, recompilation occurred for each interaction. (ORS-4594)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain any new features or functionality.
ORS now uses the new Configuration Library that includes a fix for delays in adding a large number of configuration objects in environments that already contain a large number of these objects. This modification also reduces ORS startup time in large scale environments. (ORS-4607)
The message attribute's value in ORSURS events from URS is now printed in the log file. From version 8.1.400.86 to 8.1.400.99, this value was not printed in the log file. (ORS-4596)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is an update for this product. This release contains the following new functionality:
As a result of changes in the GTS core library:
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain any new features or functionality.
ORS now receives information about new agent logins created after ORS startup, and the resource property of the agent's party is provided as expected. (ORS-4516)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is an update for this product. This release does not contain any new features or functionality.
ORS now prints its main thread's CPU usage in the log, as shown in the below sample:
LCA perf counters: pid=4745 pctcpu=<Process CPU Usage> (tid=4745 pctcpu=<Main thread CPU Usage>), vmsize=<Process Memory usage> Mb
(ORS-4528)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain any new features or functionality.
One of the keys in the Agent functional module enum is changed from null to asnull. (ORS-4400)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is an update for this product. This release does not contain any new features or functionality.
ORS no longer logs an error while processing agent-related events from Interaction Server. Previously, in such cases, ORS versions 8.1.400.89 to 8.1.400.94 reported an error that might have prevented it from sending the interaction.partystatechanged event to the session in scenarios where a multimedia interaction was still controlled by ORS at the time the interaction was delivered to the agent. (ORS-4407)
Reconnecting to unavailable Cassandra nodes no longer affects ORS inter-thread communication. Previously, when some Cassandra nodes were not available, the ORS main thread could freeze for a few seconds when reconnecting and cause delays in processing events and inter-thread communication messages. (ORS-4419, ORS-4420)
ORS no longer terminates randomly when a session is started by an /scxml/session/start web request or with the <session:start> action, and the value of the src parameter is specified in the script:<ERScript name> format. Using this format denotes that the URL of the SCXML strategy is taken from the Application section of the corresponding Enhanced Routing Script object.
Important: Sessions started by voice calls or multimedia interactions are not affected by this issue, even if the Enhanced Routing Script object is used for starting the sessions.
(ORS-4446)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new feature:
See the Orchestration Server page in the Genesys Supported Operating Environment Reference Guide for more detailed information and a list of all supported operating systems.
ORS now performs a background reload of the SCXML application from the application server if previous reload attempts fail, for example, when a 404 HTTP response is received from the application server. Previously, in such scenarios, ORS did not initiate a subsequent background reload and always used the cached version of the document. (ORS-4324, ORS-4362)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is an update for this product. This release contains the following new features:
gcti-block-redirect-trans-on-queued, to handle redirect scenarios when a call is queued at the Routing Point with AttributeCallState 23. Setting this new option's value to 1 successfully performs a <ixn:redirect> of such calls. (ORS-4272, ORS-4284)gcti-block-redirect-trans-on-queued
Option section: orchestration
Configuration object: ORS Application object
Default value: 0
Valid values: 0, 1
Value changes: After restart
x-print-treatment-attr, is introduced to enhance hiding of sensitive data in TEvent attributes. The new option is used to specify whether the T-lib attributes, AttributeCollectedDigits, AttributeLastDigit, AttributeDTMFDigits, and AttributeTreatmentParms, are printed in the log. (ORS-4269)x-print-treatment-attr
Option section: log
Configuration object: ORS Application object
Default value: 1
Valid values: 0, 1
Value changes: Immediately
For more information on the new options, refer to the ORS Deployment Guide.
This release does not contain any corrections and modifications.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain any new features or functionality.
ORS is no longer unresponsive when persistence is enabled with multiple Cassandra nodes while under moderate to heavy load and intermittent Cassandra node connection failures and reconnect attempts occur. (ORS-4245)
An error message is now recorded in the log file when ORS exits on startup when attempting to connect to Cassandra and the value of the persistence/cassandra-strategy-options configuration option contains an incorrect value. Previously, ORS terminated in such scenarios without recording an error in the log file. (ORS-4167)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is an update for this product. This release contains the following new features:
eval_expr metric to be independent when they contain sensitive data. If sensitive information is found in the expression field (matching the regular expression specified in the ors-regex-<name> option), the result field is hidden automatically. (ORS-4257)This release does not contain any corrections and modifications.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is an update for this product. This release contains the following new features:
See the Orchestration Server page in the Genesys Supported Operating Environment Reference Guide for more detailed information and a list of all supported operating systems.
ORS can now connect to a T-Server in scenarios where the check-tenant-profile configuration option is set to true on the T-Server. (ORS-4139)
ORS now continues to make subsequent attempts to reconnect to Interaction Server when a connection attempt is unsuccessful. Previously, in some cases, ORS stopped reconnection attempts to Interaction Server. (ORS-4194)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is an update for this product. This release contains the following new feature:
(ORS-4015)
<session:fetch> action). A new configuration section, elasticsearch-request-headers, is introduced to define additional headers. (ORS-4127)Users can define the additional headers in the new section as shown below:
<header name>
Option section: elasticsearch-request-headers
Configuration object: ORS Application object
Default value: None
Valid values: <header value>
Value changes: Immediately
For more information on the new section, refer to the ORS Deployment Guide.
ORS no longer stops attempts to reconnect to a Cassandra node. In previous releases, at times, ORS could potentially stop reconnection attempts with a Cassandra node that repeatedly disconnected and reconnected. (ORS-4140)
Binary attributes that contain the ", /, or \ symbols in an ESP response are now properly converted to the JavaScript (JS) property of the session.fetch.done event if the esp-response-binary-conversion ORS option is absent or has a string value. Previously, ORS generated execution errors in such scenarios. (ORS-4133)
ORS now stores the correct session expiration time when persistence is enabled. In previous releases, incorrect expiration time may have resulted in unexpected session termination after recovery from persistent storage. (ORS-4124)
ORS no longer terminates unexpectedly while running under a heavy load, when persistence is enabled. (ORS-4118)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is an update for this product. This release does not contain any new features or functionality.
This release addresses an issue that causes ORS (versions 8.1.400.83 to 8.1.400.87) to exit on startup when the ORS scxml\default-encoding option is set to ISO-8859-15 or similar values. (ORS-4081)
The ixn:createcall and ixn:consultation actions are now executed successfully if the value of the to attribute is an object and the switch property is referencing the same switch that the device referenced in the from attribute belongs to (either explicitly or implicitly). In versions 8.1.400.83 to 8.1.400.87, these actions failed in the above described scenario. (ORS-4092)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is an update for this product. This release contains the following new features or functionality:
esp-response-binary-conversion, is introduced in this release to allow users to define the way binary attributes of an ESP response message are converted to the JavaScript (JS) property of the corresponding SCXML event. (ORS-4059, ORS-4056)
esp-response-binary-conversion
Option section: orchestration
Configuration object: ORS Application object
Default value: string
Valid values: ignore, string, array
Value changes: Immediately
ignore: binary attribute value is not added as a JS property in the SCXML event.
string: value is converted to string and control characters like CR, LF, and so on, are converted to escaped characters.
array: each byte is converted to a numeric element of an array.
keep-original-sesid-on-switchover, to true to allow other VXML/SCXML sessions to communicate with the restarted session. The existing restart-session-on-switchover option must also be set to true. (ORS-4010)
keep-original-sesid-on-switchover
Option section: orchestration
Configuration object: ORS Application object
Default value: false
Valid values: true, false
Value changes: Immediately (new value will apply only to sessions that are created after the change)
This release does not contain any corrections and/or modifications.
Supported Operating Systems
New in This Release
Corrections and Modifications
Important: The new features, and corrections and modifications that were part of the 8.1.400.82, 8.1.400.83, and 8.1.400.84 releases that were withdrawn on 05/08/19, are now included in this release.
This is a hot fix for this product. This release contains the following new features:
See the Orchestration Server page in the Genesys Supported Operating Environment Reference Guide for more detailed information and a list of all supported operating systems.
Starting from this release, all ESP requests issued by ORS upon execution of the <classification:screen> or <classification:classify> actions will contain all interaction user data. (ORS-4003)
ORS now properly sends requests to the backup Interaction Server instance running in primary mode. Prior to this release, in versions 8.1.400.82 to 8.1.400.84, ORS failed to send requests to the backup Interaction Server instance. (ORS-4018)
In rare cases, calls might get stuck in the dialing state after a SIP Server switchover and ORS will not receive any notifications regarding such interactions, which might lead to stuck SCXML sessions. To clear these stuck interactions from ORS memory, configure the sync-calls-on-switchover option to 1 in the gts section of the Switch object. ORS will delete inactive calls after a default timeout of 10 minutes and publish the related events into the corresponding SCXML session. For a complete option description, refer to the
Interaction Concentrator Deployment Guide, available on the Genesys Documentation website. (ORS-3918).
Supported Operating Systems
New in This Release
Corrections and Modifications
Important: As of 05/08/19, this release is no longer available due to an issue that affects multimedia deployments, and can no longer be downloaded.
This is a hot fix for this product. This release does not contain any new features or functionality.
This hot fix addresses a rare issue that causes ORS to terminate randomly during processing of multimedia interactions, when the setuData function updates user data of Unicode type. (ORS-3992)
Supported Operating Systems
New in This Release
Corrections and Modifications
Important: As of 05/08/19, this release is no longer available due to an issue that affects multimedia deployments, and can no longer be downloaded.
This is an update for this product. This release contains the following new feature:
Starting with this release, regular expressions defined via the log-filter-data\ors-regex-<name> option can be used to hide sensitive data in messages from URS, printed in the ORSURS debug log segment. (ORS-3971)
ORS no longer crashes when converting a JavaScript object into a string for logging, but the result fields in the eval_expr metric will be empty. Previously, there have been extremely rare occurrences of ORS crashing in similar scenarios, due to an issue with the Mozilla JavaScript library. (ORS-3962)
Supported Operating Systems
New in This Release
Corrections and Modifications
Important: As of 05/08/19, this release is no longer available due to an issue that affects multimedia deployments, and can no longer be downloaded.
This is an update for this product. This release contains the following new features or functionality:
ORS now supports Red Hat Enterprise Linux version 7.5. (ORS-3941)
See the Orchestration Server page in the Genesys Supported Operating Environment Reference Guide for more detailed information and a list of all supported operating systems.
Beginning with this release, the SCXML engine supports the Federal Information Processing Standard (FIPS) Publication 140-2 validated cryptography for connections used to retrieve SCXML documents and execute the <session:fetch> action of the HTTP methods. (ORS-3886)
ORS now caches HTTP documents fetched when processing an SCXML startegy or via the <session:fetch> action, irrespective of the value of the scxml/http-verbose option. Previously, HTTP documents were not cached if the scxml/http-verbose option was set to false. (ORS-3955)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This release contains the following new features or functionality:
Beginning with this release, the inqueues and outqueues properties of the hints attribute are supported in the <ixn:redirect> action for multimedia interactions, provided the destination type is a workbin. Previously, these properties were supported only for agent type destinations. This feature helps in post-routing processing of interactions pulled from workbins. (ORS-3895)
Note: This feature is supported by Interaction Server starting from release 8.5.300.07 only.
ORS introduces a new SCXML extension, Agent, which can be used for implementing agent management features like logout, DND, and ability to change agent state for voice media.
For more details, refer to the Agent Extension topic in the Orchestration Server 8.1.4 Developer Guide. (ORS-3767)
This version was first released as a Hot Fix on 01/11/19.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality:
Beginning with this release, the fetch-timeout ORS option can be set at the ORS Application object level as well. Earlier, this option could only be specified at the Enhanced Routing Script object level. The option defined at the Enhanced Routing Script object level overrides the one defined at the ORS Application object level. (ORS-3813)
The fetch-timeout option specifies the time (in milliseconds) before a document fetch operation is abandoned. If the SCXML document cannot be retrieved within this timeout value, the fetch operation is abandoned and a fetch operation for the alternate-url is attempted.
fetch-timeout
Option section: scxml in an ORS Application object; Application in an Enhanced Routing Script object
Configuration object: ORS Application object; Enhanced Routing Script object
Default value: 5000
Valid values: Any integer greater than 0
Value changes: After restart
The SCXML engine now properly caches DNS responses. In previous ORS releases, each HTTP request issued by the SCXML engine caused a DNS lookup, despite the default DNS entry TTL value of 60 seconds. (ORS-3816)
The new ORS option, http-curl-dns-cache-timeout, defines the TTL value for entries in the internal DNS cache (in seconds). If set to 0, internal DNS caching is disabled. If set to -1, cached DNS entries will have an infinite TTL.
http-curl-dns-cache-timeout
Option section: scxml
Configuration object: ORS Application object
Default value: 60
Valid values: Any positive integer or 0 or -1
Value changes: After restart
ORS now correctly handles scenarios when the Enhanced Routing Script object is deleted and re-created with the same name and the corresponding events from Configuration Server Proxy arrive in an invalid order. Previously, ORS could not find the re-created Enhanced Routing Script object and the session was not created. (ORS-3700)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality:
A new configuration option, use-only-enabled-script, is introduced that controls whether or not ORS uses Enhanced Routing Script objects for session creation, based on object state. If this option is set to true, ORS uses only enabled Enhanced Routing Script objects. Otherwise, any Routing Script object can be used regardless of its state.(ORS-3798)
use-only-enabled-script
Option section: orchestration
Configuration object: ORS Application object
Default value: false
Valid values: true, false
Value changes: Immediately
In a blind transfer scenario to Route Point, ORS now generates an error.interaction.redirect event after it receives an EventError for the <ixn:redirect> action applied to a consultation call which is deleted due to transfer completion. To enable ORS to generate an error.interaction.redirect event in such scenarios, set the new option, fin-acts-on-calldeleted, to true. (ORS-3762)
In addition, the new configuration option, fin-acts-on-calldeleted, enables ORS to finalize all pending actions associated with a call upon receiving a CallDeleted event after the call is disconnected.
fin-acts-on-calldeleted
Option section: orchestration
Configuration object: ORS Application object
Default value: false
Valid values: true, false
Value changes: Immediately
After opening a socket for communication with Cassandra, the Cassandra library attempts to resolve the address information. Starting with this release, the socket is closed if the attempt does not succeed, resulting in no increase in the number of open sockets. Previously, open sockets were not closed and resulted in an increased number of open sockets. (ORS-3769)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is an update for this product. This release contains the following new feature:
Beginning with this release, ORS on Windows OS uses the Microsoft Visual Studio C++ 2013 Redistributable Package. The 2013 Redistributable Package is included in the ORS IP and is installed automatically. (ORS-3555)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain any new features or functionality.
ORS now successfully handles a high volume of requests from ORS to Cassandra. Previously, in such scenarios, ORS sometimes terminated unexpectedly. (ORS-3669)
Supported Operating Systems
New in This Release
Corrections and Modifications
Important: The Graceful Shutdown feature, which was introduced in version 8.1.400.64 is no longer available, starting with this release.
This is a hot fix for this product. This release contains the following new features or functionality:
ORS now supports the Red Hat Kernel-based Virtual Machine (KVM). (ORS-3532)
ORS now supplies RequestorInfo data in all ESP requests that it generates. (ORS-3267)
The following information is now included in all ESP requests:
RequestorAppName - ORS application nameRequestorAppVersion - ORS application versionRequestorAppDBID - ORS application DBID (integer)RequestorAppType - ORS application type (integer)RequestorClientID - Strategy nameThis release does not contain any corrections and modifications.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality:
ORS now supports the CentOS Linux 7 operating system. (ORS-3531)
A new option is included to control if an arbitrary URL can be used as a value for the src parameter in a <session:start> action or an /scxml/session/start web request, when starting a new session. (ORS-3483)
web-start-accept-url
Option section: orchestration
Configuration object: ORS Application object
Default value: true
Valid values: true, false
Value changes: Dynamically
When this option is set to true, ORS allows a URL to be used as a value for the src parameter. When set to false, ORS accepts data only in the script:<ERScript name> format as a value for the src parameter. If data is not in the specified format, an HTTP error message is returned.
ORS now supports TLS connections to the Message Server when parameters for the TLS connections are specified in the host object. (ORS-3168)
TLS/SSL is now engaged if the default ORS port is provisioned as secured in accordance with the Genesys Security Guide. In previous versions, engaging TLS/SSL on the default ORS port was not possible. (ORS-3460)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This release contains the following new feature:
The DN registration flow control is added to ORS. To make DN registration configurable, the following two new options are introduced:
dn-reg-chunk-size: defines the maximum number of consecutive Register Address requests to a single T-Server.dn-reg-chunk-timeout: defines the timeout in seconds between sets of consecutive Register Address requests.The new options can be configured in the gts section of the ORS Application object or the Switch object. For more information on these new options, refer to the ORS Deployment Guide.
For more information on the existing gcti-re-registration-tout option that defines the timeout between re-registration attempts after a previous attempt fails, refer to the Configuration Options section on the Genesys Docs website. (ORS-1672)
Starting from this release, the Orchestration plug-in is compatible with all 5.x Kibana versions. Previously, beginning with ORS 8.1.400.70, Kibana failed to start if the Orchestration plug-in was deployed under any of the 5.x Kibana versions prior to 5.5.0. (ORS-3499)
ORS now updates the end attribute in the Elasticsearch session document. In previous releases, the end attribute was not updated if a session started before midnight UTC and terminated after midnight UTC. (ORS-3489)
ORS now properly processes delayed SCXML events after session recovery during successive ORS failovers. Earlier, at times, delayed SCXML events published through the <send> action were not processed by the session after recovery from persistent storage under the following conditions:
<send> action (for example, when the ORS HA pair has been switched over twice in a row). (ORS-3469)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality:
With this ORS release, the cURL library version has been updated to 7.57.0 and the openSSL library version has been updated to 1.0.2n. These libraries are part of the HTTP client implementation in the SCXML engine (used for retrieval of SCXML strategy documents and execution of the <session:fetch> SCXML actions of HTTP types).
Also, the FIPS-compliant mode can now be enabled in the SCXML engine (for details, see the description of the scxml\fips-enabled option in the Orchestration Deployment Guide). (ORS-3466)
ORS now provides the capability to define arbitrary headers for the HTTP requests generated by the SCXML engine to retrieve SCXML strategy documents. A new configuration section, scxml-doc-request-headers, is introduced to define additional headers. (ORS-3408)
Users can define the additonal headers under the new section as shown below:
<header name>
Option section: scxml-doc-request-headers
Configuration object: ORS Application object or annex of Enhanced Routing Script object (if the same header is configured in both objects, the header value in the Enhanced Routing Script object takes precedence).
Default value: None
Valid values: <header value>
Value changes: Immediately
Note: The <header name> option must not contain a ':' symbol. You cannot define multiple headers with the same name. ORS does not validate the consistency of the additional header definitions; they are added to the HTTP requests as is.
Now, when a session with a delayed event is made persistent before an ORS switchover, after session recovery the delayed event is queued with an appropriately adjusted delay and then processed. In previous releases starting from 8.1.400.67, at times and under certain conditions, the delayed event was queued and processed without any further delay after session recovery. (ORS-3471)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain any new features or functionality.
ORS now creates the ors_session_state Painless Elasticsearch script on startup, when running on a Linux platform and connected to Elasticsearch 5. In previous releases, ORS failed to create the ors_session_state script on startup, when running on a Linux platform and connected to Elasticsearch 5, and as a result, subsequent operations with documents in the session index failed. (ORS-3435)
Supported Operating Systems
New in This Release
Corrections and Modifications
Note: Starting with this release, the Orchestration plugin is not compatible with versions of Kibana prior to 5.5.0.
This is a hot fix for this product. This release contains the following new features or functionality:
A new session ID generation scheme is included in this release to easily determine the node that a session belongs to. This new ID generation scheme is optional. To enable the scheme, the sessionid-with-nodeid option is introduced. This option must be set to true in the orchestration section of the ORS application or the ORS cluster, if applicable. This option minimizes Cassandra lookups to determine node/session relations wherever possible. This change does not affect custom session IDs. ORS works with old style session IDs, even if the new ID generation scheme is enabled. Different nodes and/or ORS applications in a cluster can use different ID generation schemes. (ORS-1659)
sessionid-with-nodeid
Option section: orchestration
Configuration object: ORS Application object
Default value: false
Valid values: true, false
Value changes: After ORS restart
Note: Third-party log viewers might not work with the new session IDs.
Users can now designate an existing node in the ORS cluster to act on behalf of an excluded node. Earlier, when ORS processed interactions and an ORS node was dynamically excluded from a cluster, interactions associated with the running session on the excluded node, could get stuck. (ORS-3402)
The following new option is introduced to support this enhancement:
act-on-behalf-of
Option section: orchestration
Configuration object: ORS Application object
Default value: An empty string
Valid values: List of excluded ORS Node IDs separated by a comma or semicolon
Value changes: Immediately (this is a dynamic option)
Note: It is the user's responsibility to ensure that only one existing node is acting on behalf of any excluded node. This option must be used only in unavoidable exceptional situations.
ORS is enhanced to allow presentation of all values of key-value pairs having the same key name in an interaction's user data. Use this feature optionally, because the different forms of this presentation could affect existing strategies that use multivalued keys. In previous releases, only the first value associated with a multivalued key was presented in a udata object. Now ORS can optionally provide all values in the form of a special object with a reserved name, _genesys_Multivalue. For example, udata:{multikey:{_genesys_Multivalue:["1", "2", "3"]}}. (ORS-3400)
The following new option is introduced to support this enhancement:
multivalued-prop-in-udata
Option section: orchestration (in the ORS Application object) or application (in an Enhanced Routing Script object)
Configuration object: ORS Application object or Enhanced Routing Script object
Default value: false
Valid values: true, false
Value changes: Immediately; new value is effective for sessions created after option change. When configured in an Enhanced Routing Script object, that option value takes precedence over the option configured in the ORS Application object.
All the values are provided in the form of an array ordered the same way the values were presented in the interaction user data. ORS does not provide a way to modify the multivalued key-value pairs in the interaction user data. But it does allow to use this form of multivalued property in other actions (for example, in the createcall action or the <session:fetch method="'esp'"> action, where input parameters are specified as an ECMAscript object).
Note: Using this option on an EnhancedRoutingScript object may help avoid problems with SCXML strategies that expect only a single-value representation for a multivalued key.
A new property, visibility, has been added to the transcript array element. The new property is used to specify the visibility level of a particular chat transcript element. For more details, see the Orchestration Server Developer Guide. (ORS-3388)
Now, ORS does not remove any spaces from email addresses contained in attributes of the <ixn:createmessage> or <ixn:sendmessage> actions. Previously, spaces were removed from these attributes resulting in display names appearing without spaces in email messages. (ORS-3410)
Now, when using the transcript property of the chat.gettranscript.done SCXML event, no chat messages are missed. Earlier, certain chat messages were missed while populating the transcript property. (ORS-3388)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following improvement:
AttributeMediaType
The value for this new property must be defined as a number.
For a list of supported media types, see the TMedia Type section in Platform SDK documentation. (ORS-3380)
ORS no longer prematurely processes internal events. Previously, ORS sometimes prematurely processed internal events, raised via the <send> element, when actual processing happened earlier than requested by the delay attribute. (ORS-2823)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new feature:
print-cache-stats-interval
Option section: orchestration
Configuration object: ORS Application object
Default value: 60
Valid values: Any positive integer greater than 10
Value changes: Immediately upon notification
This option specifies the time interval, in seconds, for logging level 3 SCXML internal cache statistics messages in the ScxmlCacheStats log segment.
The ScxmlCacheStats log segment can be added as a value in the log-trace-segments option.
ORS no longer improperly decodes URL-encoded session parameters in the /scxml/start web request, if they contain non-ASCII symbols and the scxml\default-encoding option is not UTF-8. Previously, in this scenario, beginning with ORS 8.1.400.47, Java script exceptions occurred on mapping these parameters with the properties of the _data object. (ORS-3356)
Supported Operating Systems
New in This Release
Corrections and Modifications
Important: The Graceful Shutdown feature, which was introduced in this release, is no longer available starting with version 8.1.400.75 (released on 06/11/18).
This is a hot fix for this product. This release contains the following new features or functionality:
ORS no longer terminates unexpectedly when processing complex interaction user data containing a key-value pair with a non-UTF-8 symbol in its key or value and the scxml\default-encoding option is set to UTF-8. (ORS-3262)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality.
ORS now correctly processes complex "Redirect-Call Service" scenarios as described in the Genesys Events and Models Reference Manual on the Genesys documentation website. (ORS-3285)
This version of ORS fixes possible random/rare issues with actions <ixn:createcall>, <ixn:consultation>, and <ixn:singlesteptransfer> in mute transfer mode. Under certain conditions, the above actions reported errors despite successful call/consult call creation. If you experience these types of issues with an older version of ORS, upgrade to ORS 8.1.400.62 or later and set gts_core options on the ORS Application object as follows:
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain any new features or functionality.
ORS now uses the Enhanced Routing Script option, alternate-url, when an SCXML strategy document cannot be retrieved/validated via the main URL. Previously, starting from release 8.1.400.44, ORS did not use this option. (ORS-3191)
ORS now properly processes the scenario in which a web server returns a negative response upon retrieval of at least one of the SCXML documents included in an SCXML strategy. In previous releases, this scenario sometimes produced a memory leak. (ORS-3184)
When ORS is running and the value of any option in the orchestration section (and other sections) is changed, the log no longer erroneously indicates that the dynamic change was ignored. Previously, starting from version 8.1.400.57, ORS would process the option value update and print the following message in the log: Option <option_name> dynamic change ignored because the option is static. (ORS-3237)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality.
For information on these enhancements, see ORS Features, Elasticsearch Connector topic, Elasticsearch Connector Enhancements section, in the Orchestration Server 8.1.4 Deployment Guide.
This release does not contain any corrections and/or modifications.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain any new features or functionality.
ORS now successfully processes interactions redirected from an external party to a local Routing Point while handling Call Forwarding Loop scenarios in a SIP Server deployment with the Unified OpenScape Voice platform. (ORS-3187)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality.
Legacy pulling of multimedia interactions is no longer interrupted when the number of pending pulling requests reaches the number specified in the value of the mcr-pull-limit option. Previously, starting with ORS version 8.1.400.51, this scenario caused such pulling to stop. Enhanced pulling of multimedia interactions was unaffected by this issue. (ORS-3190)
ORS no longer terminates unexpectedly upon removal of a subscription for a statistic that is not used for an extended time period. (ORS-3169)
The getListItemValue function now raises an exception when the first parameter contains the name of a non-existent object in Configuration Layer. Previously, starting with ORS 8.1.400.49, this scenario caused the function to return an empty string. (ORS-3166)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality.
This release improves how ORS performs a re-association of an interaction with a remote target session started on different ORS node within a cluster. This release introduces new option complete-assoc-on-target-node. It defines the way ORS handles the interaction.added and interaction.present events when associating an interaction with a remote target session running on an ORS node other than the node executing <ixn:associate> action. Previously, in a multimedia deployment, ORS may wrongly distribute the interaction.present event to the remote target session before the interaction was pulled.
complete-assoc-on-target-node
Option section: orchestration
Configuration object: ORS Application object
Default value: false
Valid values: true, false. This option must have the same value for all ORS nodes in a cluster.
Value changes: Changes to this option are applied dynamically.
When this option is set to true, the remote ORS generates interaction.added and interaction.present events after the interaction is associated with the target session. This is the proper mode for handling interactions associated with a remote target session. Genesys recommends it for new deployments, for clusters where ORS nodes can be upgraded simultaneously, or for clusters where all ORS nodes are already upgraded to version 8.1.400.53 or higher.
When this option is set to false:
Use this mode in deployments where ORS nodes in the cluster are upgraded gradually. Set the option value to true as soon as the upgrade of all nodes is completed.
Please note that if you want the remote target session to be able to work effectively with a re-associated interaction, be sure to explicitly place this interaction in any interaction queue that ORS works with. ORS does not automatically do this placement because it does not know strategy developer intentions and subsequent actions.
(ORS-3145)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
ORS now properly sends an External Service Protocol (ESP) request when the application type in the <fetch> action URL (srcexpr attribute) is CFGSocialMS. Previously, ORS did not send such an ESP request. This scenario could occur, for example, with a strategy that used an External Service block to reply to a Social Media interaction. (ORS-3122)
Now, when ORS sends a request for an SCXML document and the HTTP response contains directive 'no-cache="set-cookie"' in the Cache-control header, the retrieved document will be cached. In previous releases, the retrieved document was not cached. (ORS-3120)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality.
Now, JSON arrays are supported in JSON-encoded session startup parameters in an /scxml/session/start HTTP POST request. In this case, set the option orchestration/parse-start-params to true. Previously, if a JSON-encoded array contained more than one element, no array elements were assigned to the array object. (ORS-3098)
ORS can now successfully handle simultaneous reconnect attempts to multiple Cassandra nodes after connections were lost. Previously, in such a scenario, ORS sometimes terminated unexpectedly. (ORS-3014)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
ORS no longer experiences a random/rare shutdown when a negative (4xx, 5xx) response is received for at least one of the non-conditional GET requests submitted by the SCXML library to retrieve root and included documents from a web server. Previously, such a shutdown could occur due to an issue in the third party library. (ORS-3088)
When retrieving SCXML strategies and executing <session:fetch> actions of HTTP types (GET, POST, and so on), ORS now supports IPv6 connections. If enforced resolution of domain names to an IPv6 address is required, use option scxml/http-curl-ip-family. (ORS-3083)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality:
For details, see the Orchestration Server 8.1.4 Deployment Guide, ORS Features, Elasticsearch topic.
(ORS-2920)
Important!: An update to your existing Composer/SCXML applications is required to support the above change. This change is implemented to maintain uniformity in managing data across services and also to provide better data management.
http-curl-ip-family
Option section: scxml
Configuration object: ORS Application object
Default value: <empty string>
Valid values: ipv4, ipv6
Value changes: During startup. Changes to this option are not applied dynamically.
Example: scxml/http-curl-ip-family = ipv4
This option specifies the type of IP address to be used in the SCXML library for host name resolution upon SCXML document retrieval via HTTP protocol or execution of the
Starting with ORS 8.1.400.50, ipv6 is supported as a valid value.
(ORS-2749)
This release includes the following corrections and/or modifications.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality:
| Option Name | New Default Value |
|---|---|
| http-max-cache-entry-count | 4000 |
| http-max-cache-entry-size | 5000000 |
| http-max-cache-size | 400000000 |
| max-compiler-cached-docs | 2000 |
| max-compiler-cached-doc-size | 50000000 |
| max-compiler-cache-size | 400000000 |
| max-assembled-cached-docs | 2000 |
| max-assembled-cached-doc-size | 50000000 |
| max-assembled-cache-size | 400000000 |
| max-preprocessor-cached-docs | 2000 |
| max-preprocessor-cached-doc-size | 50000000 |
| max-preprocessor-cache-size | 400000000 |
| max-includes | 1000 |
(ORS-2969)
username
Option section: persistence
Configuration object: ORS Application object
Default value: Empty string
Valid values: Valid alphanumeric string
Value changes: On restart
Defines the username that will be used to login to the Cassandra cluster. This is optional and will default to an empty string. If Cassandra is configured to require password authentication to log in, then the user name must be provided. See also option password. The value specified must have been set for the Cassandra cluster with the CQL client interface. See the Cassandra 2.2.5 Installation/Configuration Guide for details.
password
Option section: persistence
Configuration object: ORS Application object
Default value: Empty string
Valid values: Valid ASCII string
Value changes: On restart
Defines the password associated with the username that will be used to login to the Cassandra cluster. This is optional and will default to an empty string. If Cassandra is configured to require password authentication to log in, then the password must be provided. See also option username. The value specified must have been set for the Cassandra cluster with the CQL client interface. See the Cassandra 2.2.5 Installation/Configuration Guide for details.
The Cassandra 2.2.5 Installation/Configuration Guide is updated with username/password authentication configuration information.
(ORS-2921)
This release includes the following corrections and/or modifications.
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This release contains the following new features or functionality.
This release does not include any corrections.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality:
This release does not include any corrections.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality:
In support of this feature, ORS introduces two new configuration options:
restart-session-on-switchover
Set to true to have the ORS backup instance attempt to restart the processing of voice calls that have been processed by the ORS primary instance and sessions that have not been terminated at the moment of switchover.
session-restart-timeout
Option section: orchestration in ORS Application;
section Application in Enhanced Routing Script
Configuration Object: Enhanced Routing Script, ORS Application
Default value: 50
Valid values: Any numeric value (starting from 10)
Value changes: Immediately.
Specifies the timeout (msec) between cycles of session starts upon call processing recovery. The restart quota per cycle is equal to the number of engine-working threads defined with session-processing-threads option in the ORS SCXML section (default = 8).
A new asynchronous event, session.restarted, also supports this feature.
Attribute: Interactionid – String. ID of the interaction whose processing has been restarted. This event is raised when ORS restarts the processing of calls after an ORS switchover without using persistence.
For more information on this feature, see the Orchestration Server 8.1.4 Deployment Guide, High Availability topic, Recovery of Voice Calls Without Persistence section.
(ORS-2512)
This release includes the following corrections and modifications:
ORS now blocks an incorrect attempt to start a new session immediately after detaching an interaction until the free interaction is pulled again. (ORS-2901)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality:
ORS now supports a new configuration option:
cookie
Option section: orchestration
Configuration object: ORS Application object
Default value: An empty string
Valid values: Any valid cookie (see RFC 6265, section 4.1.1)
Value changes: Immediately upon notification
This option defines the value of the Set-Cookie header in web responses. If empty, the ORS will use its own value in the format ORSSESSIONID=sessionId.nodeId.
(ORS-2836)
This release includes the following corrections and modifications:
When a child element <param> of action <session:fetch method="'urs'"> uses a numeric property of a JavaScript object set as a value, ORS now properly encodes it upon transmission to Universal Routing Server. (ORS-2862)
ORS no longer terminates unexpectedly when the attr_party_type attribute is missing in Interaction Server events. (ORS-2849)
In previous 8.1.4 versions, if getMinData/getMaxData/getAvgData functions were called the first time (without explicit subscription preceding them) for a given combination of objects and statistics, they returned an undefined value. Now, in this scenario, these functions return the correct value of statistic. (ORS-2832)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality:
The default value of the ORS option scxml\max-state-entry-count is changed from 100 to 500. (ORS-2826)
ORS now stores two new Session Reporting fields into Elasticsearch, as follows:
(ORS-2803)
This release includes the following corrections and modifications:
ORS now correctly manages the Enhanced Routing Script if it was dynamically added in the Configuration Layer as the last object of the group containing the following objects required for enhanced pulling: Interaction Queue, Interaction Queue View, Interaction Submitter, and Enhanced Routing Script. Previously in this scenario, ORS did not detect the addition of the Enhanced Routing Script until the configuration of any object related to enhanced pulling was changed or ORS was restarted. (ORS-2831)
This version of ORS is built with a new Log Library that contains the fixed logging issue. Previously, ORS occasionally created empty log files. (ORS-2009)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality:
ORS can now delegate session creation to the Reserved Node when the Assigned ORS Node that is responsible for call processing can no longer create a session, if one of the following conditions occurs:
The following message will be printed in the log of the Assigned ORS Node responsible for call processing:
15:44:52.347 {SessionManager:1} Session is granted for this node (primary, delegating session): InteractionID=MTBG13L56H55F5VOFJ9NUV8T0K00000C, delegating to Node=828, reason: Max active session number reached
The following messages will be printed in the log of the Reserved ORS Node:
15:44:52.357 {SessionManager:2} [HandleCallInfoChanged]: Delegating session instruction is received for call (ID=MTBG13L56H55F5VOFJ9NUV8T0K00000C)
15:44:52.357 {SessionManager:2} [CallInterceptorTimer]: This ORS instance is responsible for call (ID=MTBG13L56H55F5VOFJ9NUV8T0K00000C) processing now
(ORS-2757, ORS-2515)
This release includes the following corrections and modifications:
In an ORS cluster deployment, where several ORS nodes pull interactions simultaneously from one queue and redirect them to another queue, ORS now correctly returns a multimedia interaction to the same queue from which it was taken. Previously, in this deployment, ORS sometimes incorrectly returned interactions to the first queue. (ORS-2772)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality.
14:30:10.259 {ElasticConnector:1} Response from ElasticSearch host:port:
This release contains the following corrections and/or modifications:
ORS no longer occasionally experiences unsolicited memory growth under high load conditions in a configuration with primary/backup synchronization enabled for voice treatment requests. (ORS-2746)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality.
http-keepalive-idle
Option section: scxml
Configuration object: ORS Application object
Default value: 7200
Valid values: Any valid integer
Value changes: Take effect after restart.
Defines the time between keepalive transmissions in idle condition for TCP sockets for fetching documents from an application server.
http-keepalive-intvl
Option section: scxml
Configuration object: ORS Application object
Default value: 75
Valid values: Any valid integer
Value changes: Take effect after restart.
Defines the time interval between keepalive re-transmissions, if an acknowledgement to the previous keepalive transmission was not received.
(ORS-2724)
This release contains the following corrections and/or modifications:
The lookup time for option def-statserver-name is improved in the following scenario: When the option is not configured on a Routing Point and the T-Server responsible for the call processing is not defined in the Switch object in Configuration Layer. Previously, a delay could occur (hundreds of milliseconds) when an ORS Connections list contained a large number of T-Servers. (ORS-2695)
ORS no longer terminates unexpectedly when configured with an unsupported value of the default-encoding option. ORS now prints an error message: Could not create default transcoder for: <configuration value> and gracefully exits. (ORS-2397)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality:
For Voice deployment configure a new option:
application@<Orchestration cluster name>
Option section: Orchestration
Configuration object: DN (Extension or Routing Point)
Default value: None
Valid values: Any valid URL
Value changes: For the next interaction that uses this resource
This option specifies the URL of the SCXML document to load for ORS nodes that belong to a specific Orchestration cluster as defined in the option name. When this option is configured, only the ORS nodes that belong to the defined cluster will process calls. If this option is not configured, ORS will load and execute the SCXML document configured in the application option.
For information on how to dynamically transition the processing of interactions to a new Orchestration cluster, refer to DN- Level Options, application@<Orchestration cluster name> in the Orchestration Server 8.1.4 Deployment Guide.
For deployments with Enhanced Pulling of multimedia interactions, configure a new option:
cluster-id
Option section: Orchestration in Annex of the Interaction Submitter Script object
Configuration object: Interaction Submitter Script object
Default value: None
Valid values: List of ORS clusters separated by ';'
Value changes: Immediately upon notification. Applicable to subsequent pull requests.
When this option is configured, it restricts usage of the Submitter to only the ORS nodes that belong to the clusters listed in this option. If this option is not configured in a Submitter, the Submitter can be used by any ORS node. Applicable only for Enhanced Pulling.
(ORS-2408, ORS-2624)
This release contains the following corrections and/or modifications:
An updated application no longer terminates unexpectedly when ORS requests a long list of Universal Contact Server interactions, or when requesting another large JSON object through a callback. (ORS-2679)
ORS no longer terminates unexpectedly when a Routing Point is dynamically added to the Configuration Layer during a call involving this Routing Point. (ORS-2655)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality:
max-script-duration
Option section: scxml (in the ORS Application object) or Application (in an Enhanced Routing Script object)
Configuration object: ORS Application object and Enhanced Routing Script object
Default value: 2,000 milliseconds
Valid values: 500 - 10,000 milliseconds
Value changes: When configured on an ORS Application object, takes effect during startup. When configured on an Enhanced Routing Script object, takes effect for sessions that started after that update. When configured in an Enhanced Routing Script object, that option takes precedence over the option configured in the ORS Application object.
If the execution time for JavaScript within a <Script> element exceeds the configured limit, execution will be interrupted, an Alarm-level message will be printed in ORS log, and the error.script.Script event will be raised for the corresponding session.
(ORS-2621)
This release contains the following corrections and/or modifications:
ORS no longer terminates unexpectedly when executing sessions that persist for too long. Previously, ORS could sometimes interpret such sessions as timed out and mistakenly terminate them. (ORS-2529)
ORS no longer becomes unresponsive when executing multiple sessions that use JavaScript. Previously, deadlocks could sometimes occur during this scenario when persistence was enabled. (ORS-2428)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality.
This release does not contain any corrections and/or modifications.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality.
same-node-for-cons-prim-calls
Option section: orchestration
Configuration object: ORS Application object
Default value: false
Valid values: true or false
Value changes: Changes to this option will take effect immediately, but only for consult calls created after that change.
When set to false, ORS 8.1.4 and 8.1.3 call distribution works the same: ORS determines the ownership of consult calls in the same way as it determines the ownership of any other call. The only exceptions are ORS versions 8.1.400.30 through 8.1.400.32, where compatibility with 8.1.3 was broken. When set to true, consult calls will be handled by the same node that handled the related primary call.
(ORS-2601)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
In a Linux environment, ORS now properly handles the scenario where a zero socket handler is used for a socket connection. Previously in this scenario, socket connections could unexpectedly close and all subsequent connections could be incorrectly processed. (ORS-2563, ORS-1608)
ORS can now redirect pulled Interactions to the Agents and/or Places that were created after ORS startup. Previously in this scenario, ORS printed an error and the redirect was not completed. (ORS-2546)
The sData function now correctly returns an undefined value when that function is used to obtain statistical data through URS and the required Stat Server is not accessible or an invalid statistic was requested. Previously in this scenario, the function did not return any value and ORS stopped processing the interaction. (ORS-2500)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This release contains the following new features or functionality.
A new Debug Log Segment header ScxmlMetricEvalExpr is added for METRIC:eval_expr. In a log file, it will appear as follows:
14:47:11.414 [T:8436] {ScxmlMetricEvalExpr:3} METRIC <eval_expr sid='ors2521' expression='global._data = new Object();' result='[object Object]' thread='8436' />
The existing log-trace-segments option adds ScxmlMetricEvalExpr as a new value.
filter-eval-expr
Option section: orchestration
Configuration object: ORS Application object
Default value: false
Valid values: true or false
Value changes: Immediately upon notification
This option enables hiding of sensitive data in expression and result fields of the eval_expr log metric. If set to true, ORS verifies that string data against the regular expression defined in the ors-regex-<name> option.
(ORS-2521
This release does not contain any corrections and/or modifications.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality.
ORS processing is improved to minimize the probability of a User Data update failure if an SCXML script does not explicitly detach an interaction before a successful <ixn:redirect>. Previously, in this scenario, ORS could fail to remove session-specific User Data from an interaction when an automatic detach was performed upon session termination and a race condition existed where one party in a call was already deleted before the new one was added. Genesys recommends to explicitly detach an interaction from a session before routing. (ORS-2465)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new features or functionality.
On the Windows 64-bit platform, ORS now uses a third-party memory allocator instead of a standard heap performance counter, which improves performance under high load conditions.(ORS-2445)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality.
creation-session-rate measures the rate of session creation in sessions per second.
state-rate measures the rate of exits from state in states per second.
func-execution-rate measures the rate of function execution in number per second.
fetch-rate measures the rate of fetch action executions in fetches per second.
active-calls measures the current number of active CTI calls.
(ORS-2368) (ORS-2364)For information on these enhancements, see Performance Monitoring in the Orchestration Server 8.1 Deployment Guide.
ORS now correctly provisions Orchestration-specific User Data in an interaction created via <ixn:createmessage> with the relatedixn attribute defined as a child interaction. Now, if the parent session is still active, child interactions will be attached to it. Previously, in this scenario, when processing such a child interaction that it did not create, ORS attempted to create a new session when the parent session had not yet terminated. (ORS-2388)
ORS now correctly raises error.interaction.redirect to a session in the following scenario: when RequestRouteCall fails on T-Server, the call is abandoned, and T-Server distributes EventError for the RequestRouteCall message after the EventCallDeleted event. Previously in this scenario, ORS did not raise error.interaction.redirect to a session. (ORS-2365)
In a blind transfer scenario, ORS now properly raises the dialog.start.done event into a session after it receives the EventTreatmentEnd event when the <dialog> action is applied to a consultation call, but the corresponding treatment finishes after transfer completion. Previously, in such a blind transfer scenario, ORS did not raise the dialog.start.done event. (ORS-2280)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality.
When operating in a Red Hat Enterprise Linux platform environment, ORS can now successfully handle URLs of a length greater than 2,048 bytes. Previously in such an environment, ORS sometimes terminated unexpectedly upon execution of the <session:fetch> action with the HTTP GET method. (ORS-2451)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality.
_genesys.session.getServerVersion
Parameters: None
Return value type: STRING (version of Orchestration Server)
(ORS-2356)
ORS now honors the configured value of scxml/persistence-max-active and will begin deactivating sessions once the active session load reaches 75% of this configured value. Previously, ORS could begin prematurely deactivating sessions as soon as there were at least 750 active sessions, which could lead to ORS resources being completely consumed by session restoration, consequently delaying the processing of SCXML sessions. (ORS-2383)
ORS no longer sometimes terminates unexpectedly in the scenario where the processing of events interferes with session recovery, when ORS is under heavy load. (ORS-2384)
ORS has improved its compilation of pre-processed SCXML documents. Because of this, it no longer experiences memory growth when the allocated cache size for compiled documents is exceeded—either when the allocated cache size is insufficient for storing all compiled documents or when some documents exceed the maximum size. (ORS-2385)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new features or functionality.
Now, Orchestration Server no longer becomes unstable if it receives certain call-related T-Events with an empty ThisDN or OtherDN attribute. (ORS-2200)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in the 8.1.400.21 release of Orchestration Server.
To support this new functionality, ORS introduces two new options: alarm-name and alarm-check-interval.
<alarm-name> (The name of this option is the alarm name.)
Option section: performance-alarms
Configuration object: ORS Application object
Default value: None
Valid Values: Specify an Alarm Definition string.
Value changes: Immediately upon notification.
This option defines the alarm name and the performance monitoring parameters.
alarm-check-interval
Option section: performance-alarms
Configuration object: ORS Application object
Default value: 60
Valid values: Any non-negative integer from 1 to 600
Value changes: Immediately upon notification.
This option defines the time interval, in seconds, to use when checking for alarm conditions.
For more information on this new feature and the alarm-name and the alarm-check-interval options, see Performance Monitoring in the Orchestration Server 8.1 Deployment Guide.
(ORS-2083)
Successful Redirect/detach=true
In the case of a successful execution of a redirect action with detach=true, a routed interaction (previously belonging to the session that invoked this action) will be automatically detached. The SCXML session invoking this action receives interaction.notcontrolled and interaction.deleted events with resultof=detaching, and then interaction.redirect.done event.
Unsuccessful Redirect/detach=true
In the case of a failed <ixn:redirect> action (with detach=true), the session invoking this action receives only the error.interaction.redirect event. The interaction remains in the same attached/detached state as it was before invoking <ixn:redirect> action with detach=true.
Note:
If the <ixn:redirect> action is provided with the ID of an interaction that is already detached, then the detach attribute has no effect. In this case, ORS produces warning IxnVMMThreadData::CommonPartHandler: WARNING - ixn action attribute 'detach' has no effect, interaction 'ZZZ' is already detached and operates as if detach=false. If a redirect error happens, the interaction remains in the same state (is still detached) and the application developer must decide the next step for the interaction.
(ORS-2260)
ORS no longer pulls interactions from a Workbin's Private views when View\WorkbinView is configured as true. (ORS-2288)
Upon reconnect to Interaction Server or its backup instance, ORS is now able to continue processing interactions in a routing state that were pulled at the moment of the Interaction Server unexpected termination. (ORS-2286)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality:
http-verbose
Option section: scxml
Default value: true
Valid values: true, false
Value changes: Takes effect after restart.
The option allows you to configure the amount of information written to the log when ORS reuses the connection for a new HTTP request.
(ORS-2300)
The SData function now returns the correct value of a statistic when called for the first time for a given combination of objects and statistics. Previously, the function sometimes returned an undefined value. (ORS-2299)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new features or functionality.
The ORS parameter substitution feature, described in Release 8.1.300.27, now works properly when configuring parameters in an Enhanced Routing Script object. When specifying the SCXML document to load, ORS no longer sometimes stops unexpectedly during pre-emptive revalidation of cached entries. This could occur when processing parameter substitutions for Enhanced Routing Script url/alternate-url options and/or <xi:include>paths. (ORS-2269)
ORS now dynamically processes changes to and configuration of the def-statserver-name option for a Tenant. (ORS-2264)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality.
detaching
deletion
routing
revoking
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality.
getlistitem-binary-conversion
Option section: orchestration
Default value: ignore
Valid values: ignore, string, array
Value changes: Immediately upon notification.
When set to ignore, no value is returned (as if it does not exist in the List).
When set to string, the value is converted to string. If there are bytes with a zero value, then the string will contain bytes only until the first zero byte.
When set to array, each byte is converted to element of array. Previously, binary attributes were converted to array.
Notes:
If Transaction List item attributes are stored in non-string format and the _genesys.session.getListItemValue(list, item, key) function retrieves the value of a particular key , it is returned as string. Previously, in this scenario, the _genesys.session.getListItemValue() function ignored non-string attributes.
Also, if _genesys.session.getListItemValue() is called with two arguments or with '*' as a third argument, the returned object will also include attributes whose values are empty strings. Previously, in ORS version 8.1.300.29, a minor defect was introduced, and attributes with empty values were not included in the returned object, when _genesys.session.getListItemValue() retrieved the Transaction List directly via ORS.
(ORS-2060)
While operating under load following the use of the Composer ORS Debugger, Orchestration Server no longer sometimes becomes unresponsive with unterminated debugging sessions.
Note: Genesys does not recommend the use of Composer's ORS Debugger in a production environment. Use the ORS Debugger only for development purposes. (ORS-2197)
Orchestration Server now correctly processes voice interactions when attempting to connect to an HA pair of initializing T-Servers, when the connection to the T-Server running in Backup mode is established first. Previously, in such a scenario, interaction processing could fail. (ORS-2192)
The Orchestration Server persistence component no longer occasionally fails to persist a session to a server-node relationship. Previously, this could cause session recovery failure upon an Orchestration failover. (ORS-2190)
Orchestration Server no longer stops unexpectedly in a scenario where it attempts to terminate a session for a second time. (ORS-2171)
While processing sessions, Orchestration Server no longer becomes unresponsive as a result of an abnormally high frequency of requests to execute the getListItemValue function. (ORS-2159)
In a deployment where T-Server sends only EventRouteRequest but not EventQueued, upon session creation, Orchestration Server now successfully handles the first user data update when information about the session is attached to the interaction. In this case, ORSI key with sessionID+ is set. (ORS-2153)
Orchestration server now correctly handles disconnection from one Cassandra instance in a deployment with multiple Cassandra instances per ORS node. (ORS-2064)
Orchestration Server now successfully processes delayed events under high load conditions. Previously (but rarely), under high load conditions, delayed events could sometimes not be raised (processed) at all, which caused a session to become permanently stuck. (ORS-2214).
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new features or functionality.
Now, when the ucs attribute of the hints attribute is set to true in the <ixn:terminate> action, ORS sends all existing user data in the external_service_request message, when Method = StopProcessing in addition to the key-value pairs required for this request. As a result, user data is no longer lost. (ORS-2020)
Now, upon detaching an interaction from a session (explicitly or during auto-detaching when a session ends), ORS only sends a request to delete the ORSI:xxx:<Real_ixn_ID> key, and does not send a request to delete the ORSI:xxx:0 key. Previously, ORS sent both requests.
Note: ORS still may send both requests during session recovery (as before this fix) when one ORS instance tries to recover a session that was created by another ORS instance. (ORS-2047)
Now, upon startup, an ORS Application will report a status of Service Unavailable to Management Layer until it is completely initialized. Previously, an ORS Application reported a status of Running to Management Layer before it was fully initialized. (ORS-2048)
The following Open Media interaction attributes are now accessible as properties of msgbased or chat objects:
received_at—reflects attr_itx_received_atsubmitted_at—reflects attr_itx_submitted_atplaced_in_queue_at—reflects attr_itx_placed_in_queue_atis_online—reflects attr_itx_is_onlineis_locked—reflects attr_itx_is_lockedmoved_to_queue_at—reflects attr_itx_moved_to_queue_atNote:The properties is_online and is_locked are presented as Boolean values [true | false] while appropriate attributes in events are presented as integer values [1 | 0]. (ORS-2052)
When ORS simultaneously reconnects to Configuration Server and Universal Routing Server and the connection to Configuration Server was established first, ORS no longer occasionally stops trying to reconnect to Universal Routing Server. (ORS-2081)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality:
mcr-pull-cycle-quota
Option section: orchestration
Configuration object: ORS Application object
Default value: 100
Valid values: Any non-negative integer less than 50000
Value changes: Immediately upon notification
Defines the maximum number of interactions that will be requested in a pulling cycle. This number is divided equally and rounded up to the nearest integer among the routing strategies that have no outstanding pull request. If there is an outstanding pull request for a strategy, then no pull request will be sent and this strategy will not be used in the calculation of the per-strategy quota for this particular pulling cycle.
(ORS-1994)
ORS adds support for Windows Server 2012 native 64-bit. (ORS-2019)
max-assembled-cache-age
Option section: scxml
Configuration object: ORS Application object
Default value: 60
Valid values: Any non-negative integer
Value changes: Takes effect after restart
Determines the expiration time, in seconds, of an entry in the Assembled Document Cache.
assembled-cache-reload-threshold
Option section: scxml
Configuration object: ORS Application object
Default value: 45
Valid values: Any non-negative integer
Value changes: Takes effect after restart
Determines the period of time, in seconds, after which the pre-emptive re-validation of a cached entry occurs. When the age of a cached document in the assembled document cache exceeds the assembled-cache-reload-threshold, the next request re-validates the document and updates the cache.
(ORS-1970)
(ORS-1508)
This release includes the following corrections and modifications:
ORS no longer terminates unexpectedly when, while running under a heavy load, it reads the configuration after a reconnection to Configuration Server. Previously in this scenario, ORS sometimes terminated. (ORS-1966)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in this release of Orchestration Server.
ixn.redirect action is successfully completed, and there is no other associated interaction attached to that session during the configured timeout. This functionality is enabled by the new Application-level option, ixnfm-idle-session-ttl, in the orchestration section. (ORS-1658)
<session:start> action or web request. The script name can be defined in script:ScriptName format as a value of the src attribute of the <session:start> action element, or as a value of the src parameter of the /scxml/session/start web request. When the script: notation is used, the URL of the SCXML strategy is taken from the Application section of the corresponding Enhanced Routing Script. (ORS-1785)Examples:
<session:start src="'script:Script1'" sessionid="newid"/>
http://localhost:7031/scxml/session/start?src=script:Script1
interaction.deleted events now contain a new property resultof. The values of this property are: detaching and deletion. (ORS-1661)
mcr-queue-on-fails, in the orchestration section. This option specifies the interaction queue into which the interaction is placed if session creation for multimedia interaction fails, instead of returning it to the same interaction queue. (ORS-1398)This release includes the following corrections and modifications:
Orchestration Server now populates the AttributeLocation in RequestInitiateTransfer when the action element is used to initiate a consultation call to a multi-site destination. (ORS-1254)
When an HTTP request is delivered to the Orchestration Server (ORS) node that owns the session, but has no cookie related to this session, ORS now adds a Set-Cookie header in a 200 OK response. This allows for a load balancer that supports "sticky" sessions to redirect any subsequent requests about that ORS session to the ORS node that handles the session. Previously in this scenario, ORS did not add a Set-Cookie header in the HTTP response, which resulted in additional redirections of the HTTP requests to the proper ORS node. (ORS-1845)
For multimedia interactions the data automatically provided by Universal Routing Server for reporting solutions is now available. This includes data which is attached to interactions and partial data that is provided in Virtual Queue events. The keys that apply to multimedia interactions include:
RVQID, RVQDBID, RTargetRule, RTargetAgentGroup,
RTargetPlaceGroup, RPVQID, Reason, RTargetRuleSelected, RTargetTypeSelected, RTargetObjectSelected, RTargetAgentSelected,
RTargetPlaceSelected, RTenant, RRequestedSkillCombination. (ORS-1038)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality:
ORS no longer terminates unexpectedly when a Routing Point object is dynamically added to the Configuration Layer during a call involving this Routing Point. (ORS-2653)
When operating in a Red Hat Enterprise Linux environment, ORS can now successfully handle URLs of a length greater than 2,048 bytes. Previously in such an environment, ORS sometimes terminated unexpectedly upon execution of the <session:fetch> action with the HTTP GET method. (ORS-2462)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new features or functionality.
ORS now honors the configured value of scxml/persistence-max-active and will begin deactivating sessions once the active session load reaches 75% of this configured value. Previously, ORS could begin prematurely deactivating sessions as soon as there were at least 750 active sessions, which could lead to ORS resources being completely consumed by session restoration, consequently delaying the processing of SCXML sessions. (ORS-2370)
ORS now correctly restores loop detection settings during session recovery. (ORS-2355)
ORS no longer sometimes terminates unexpectedly in the scenario where the processing of events interferes with session recovery, when ORS is under heavy load. (ORS-2332)
ORS has improved its compilation of pre-processed SCXML documents. Because of this, it no longer experiences memory growth when the allocated cache size for compiled documents is exceeded—either when the allocated cache size is insufficient for storing all compiled documents or when some documents exceed the maximum size. (ORS-2325)
The ors.js file must always be defined in the js-preload-files option to ensure successful execution of SCXML applications if the ixnid parameter is not explicitly provided in the request. (ORS-2335)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new features or functionality.
The ORS parameter substitution feature, described in Release 8.1.300.27, now works properly when configuring parameters in an Enhanced Routing Script object. When specifying the SCXML document to load, ORS no longer sometimes stops unexpectedly during pre-emptive revalidation of cached entries. This could occur when processing parameter substitutions for Enhanced Routing Script url/alternate-url options and/or <xi:include>paths. (ORS-2269)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality.
Orchestration Server now successfully processes delayed events under high load conditions. Previously (but rarely), under high load conditions, delayed events could sometimes not be raised (processed) at all, which caused a session to become permanently stuck. (ORS-2220).
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new features or functionality.
While operating under load following the use of the Composer ORS Debugger, Orchestration Server no longer sometimes becomes unresponsive with unterminated debugging sessions.
Note: Genesys does not recommend the use of Composer's ORS Debugger in a production environment. Use the ORS Debugger only for development purposes. (ORS-2101)
Previously, Orchestration Server sometimes did not properly react on T-Events when T-Server incorrectly distributed them for non-registered DNs, which resulted in sessions not being created and voice interactions not being processed. This issue was fixed in T-Server Common Part. Consult Genesys Customer Care to determine if this issue was resolved for your specific type of T-Server. (ORS-2025)
Orchestration Server now correctly processes voice interactions when attempting to connect to an HA pair of initializing T-Servers, when the connection to the T-Server running in Backup mode is established first. Previously, in such a scenario, interaction processing could fail. (ORS-2166)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new features or functionality.
Orchestration Server no longer stops unexpectedly in a scenario where it attempts to terminate a session for a second time. (ORS-2170)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new features or functionality.
While processing sessions, Orchestration Server no longer becomes unresponsive as a result of an abnormally high frequency of requests to execute the getListItemValue function. (ORS-2133)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new features or functionality.
Orchestration Server now allows call user data to be updated when the SCXML session does not own the call. (ORS-2112)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new features or functionality.
When ORS simultaneously reconnects to Configuration Server and Universal Routing Server and the connection to Configuration Server was established first, ORS no longer occasionally stops reconnect attempts to Universal Routing Server. (ORS-2011)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new features or functionality.
Now, upon detaching an interaction from a session (explicitly or during auto-detaching when a session ends), ORS only sends a request to delete the ORSI:xxx:<Real_ixn_ID> key, and does not send a request to delete the ORSI:xxx:0 key. Previously, ORS sent both requests.
Note: ORS still may send both requests during session recovery (as before this fix) when one ORS instance tries to recover a session that was created by another ORS instance. (ORS-1954)
Now, upon startup, an ORS Application will report status Service Unavailable to Management Layer until it is completely initialized. Previously, an ORS Application reported status Running to Management Layer before it was fully initialized. (ORS-1631)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new features or functionality.
Orchestration Server now correctly handles disconnection from one Cassandra instance in a deployment with multiple Cassandra instances per ORS Node. (ORS-2028)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality:
ORS now supports Debug Logging Segmentation, which provides more precise control of the logging when the log-trace-segments option is configured. The debug segment header {<segment_name>:<log_level>} is now added right after the timestamp.
For example: 10:31:02.249 {ScxmlMetric:3} METRIC <event_queued sid='MLO6K6519D5UPAGSHNE41VJBSS00000M' name='interaction.added' type='external' thread='15800' />
orchestrationall/AllORSInternal, ORSInit, ORSSynch, Cluster, ItxLink, ItxManager, CallMonitor, ORSURS, Persistence, Schedule, SessionManager, ThreadSync, ScxmlCommon, ScxmlLog, ScxmlMetric, ScxmlQOS, ORSScxml, ScxmlConfig, ScxmlIxnAction, ScxmlOrsAction, DFM, ScxmlEvent, FMClassification, FMDialog, FMInteraction, FMQueue, FMResource, FMSession, FMStat, FMWeb, ScxmlProperty, ScxmlIOSpecifies debug messages that will be printed into the log files. When set to all or All (the default), all debug messages are printed with the log level defined by the log/x-server-trace-level option. To control the log levels for each segment, use syntax: <segment_name>:<log_level>. If <log_level> is not specified or invalid, ORS applies the default value (defined in x-server-trace-level). If an unknown segment is specified, ORS ignores it without generating an error. Also see the enhancement in Release 8.1.400.31.
Example:
| Setting | Description |
|---|---|
| all, ORSInternal:0, ORSURS:0 | Everything is enabled except ORSInternal and ORSURS |
| ScxmlIO,ThreadSync | Only ScxmlIO and ThreadSync are enabled |
| all,ORSURS | Everything is enabled (the same as all) |
| ORSURS:0 | Everything is disabled (the same as empty) |
| CallMonitor,all:0 | Everything is disabled (the same as empty) |
| all,ORSURS:1 | Everything is enabled with the default trace level, but the trace level for the ORSURS segment will be changed to 1 |
| (empty) | Everything is disabled (the same as all:0, or x-server-trace-level=0) |
| all:3 | The same as all with x-server-trace-level=3 |
(ORS-1679)
This release includes the following corrections and modifications:
Orchestration Servers configured as High Availability pairs can now automatically synchronize voice treatment request data when a treatment is directly requested by ORS, thereby ensuring a smooth switchover. For more information, see Data Synchronization Between Primary and Backup ORS. (ORS-1990)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality:
ORS supports two new configuration options, max-assembled-cache-age and assembled-cache-reload-threshold, to allow users to fine tune the behavior of the assembled document cache.
scxmlApplication object60Determines the expiration time, in seconds, of an entry in the Assembled Document cache.
assembled-cache-reload-thresholdscxmlApplication object45
Determines the period of time, in seconds, after which the pre-emptive revalidation of a cached entry occurs. When the age of a cached document in the Assembled Document cache exceeds the assembled-cache-reload-threshold, the next request revalidates the document and updates the cache.
(ORS-1917)
This release includes the following corrections and modifications:
ORS no longer terminates unexpectedly when, while running under a heavy load, it reads the configuration after a reconnection to Configuration Server. Previously in this scenario, ORS sometimes terminated. (ORS-1889)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new features or functionality.
Now after an Interaction Server switchover/reconnect, Orchestration Server properly creates an SCXML session for an interaction that it pulled immediately after the reconnect to the new Primary Interaction Server. Previously in this scenario, due to race conditions, Orchestration Server did not always create a session for the pulled interaction. (ORS-1918)
Orchestration Server now submits the proper values to Universal Routing Server for UserData attributes Queue and PlacedInQueueAt in requests CreateVirtualCall and UpdateVirtualCall when an interaction is redirected from one interaction queue to another. Previously, Orchestration Server sometimes used the attribute values from requests related to the initial interaction queue. (ORS-1933)
Orchestration Server now correctly uses the values set in Application level options scxml/http-max-age and scxml/http-max-stale. (ORS-1877)
When Orchestration Server processes the classification:screen or classification:classify action with attribute fromudata, it now correctly attaches the original interaction user data pair, referenced by the fromudata attribute, to the external service request generated upon execution of that action. This functionality is available beginning with Composer version 8.1.301.01.(ORS-1822)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new functionality:
xincludes in subsequent sessions.
max-assembled-cache-size
Option section: scxml
Configuration object: ORS Application object
Default value: 10000000
Valid values: Minimum = 0, no maximum value
Valid changes: Take effect after restart.
Determines the maximum allowed size (in bytes) of the assembled document cache. The size of the cache is determined by the total size of all cached documents stored in the cache.
max-assembled-cached-docs
Option section: scxml
Configuration object: ORS Application object
Default value: 1000
Valid values: Minimum = 0, no maximum value
Valid changes: Take effect after restart.
Determines the maximum number of documents to be stored in the assembled document cache. If this number is exceeded, the least referenced cached items will be removed from the cache to make room for new entries.
max-assembled-cached-doc-size
Option section: scxml
Configuration object: ORS Application object
Default value: 10000000
Valid values: Minimum = 0, no maximum value
Valid changes: Take effect after restart.
Determines the maximum allowed size (in bytes) of each individual entry in the cache. If a fully-assembled SCXML strategy exceeds this size, it cannot be stored in the cache.
(ORS-1827)
getListItemValue and ListLookupValue functions. (ORS-1821)
Orchestration Server no longer unexpectedly terminates when a malformed XML message is delivered via the Debug client. (ORS-1826)
Orchestration Server now exhibits shorter document retrieval times when cached items expire or need renewal. (ORS-1824)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new functionality:
AttributeErrorCode and AttributeErrorMessage from EventError into the error and description attributes of the error.interaction.redirect event when T-Server fails to redirect a voice interaction. (ORS-1666)
Orchestration Server no longer exits unexpectedly when an SCXML session terminates as a result of exceeding the value configured in the max-state-entry-count option. (ORS-1786)
Orchestration Server now sets the time to live in Cassandra for information required to support proactive session recovery, which corrects an issue when failover within the Composer debugger occurred and the session was terminated. The time to live for the information in Cassandra is the configured scxml/max-session-age plus 3600 seconds. After this period the data within Cassandra will be marked as deleted. (ORS-1544)
Supported Operating Systems
New in This Release
Corrections and Modifications
cassandra-read-timeout
Option section: persistence
Configuration object: ORS Application object
Default value: 500
Valid values: Any integer value from 201 to 4999
Value changes: Takes effect after restart.
This option defines the maximum time, in milliseconds, that ORS will wait for a Cassandra connection to become ready to read. If this time is exceeded, ORS considers the connection to be lost.
cassandra-write-timeout
Option section: persistence
Configuration object: ORS Application object
Default value: 500
Valid values: Any integer value from 201 to 4999
Value changes: Takes effect after restart.
This option defines the maximum time, in milliseconds, that ORS will wait for a Cassandra connection to become ready to write. If this time is exceeded, ORS considers the connection to be lost.
Note: This version was first released as a Hot Fix on 07/28/14.
Supported Operating Systems
New in This Release
Corrections and Modifications
max-session-create-time, to prevent the build-up of script execution jobs in the ORS SCXML engine as a result of network latency or URS overload. Previously, this scenario could sometimes cause an increase in session creation time.
ORS now detects overload conditions by the measuring the time consumed by the SCXML engine to create sessions and the number of pending session-creation requests. If a growing session creation time becomes higher than the configured max-session-create-time threshold and the number of pending requests to create sessions is higher than 0, ORS stops creating new sessions and will remain in that state until all pending session creation requests are completed.
max-session-create-time
Option section: orchestration
Configuration object: ORS Application object
Default value: 3600
Valid values: Any integer between 5 and 3600
Value changes: Immediately
Maximum session creation time in seconds. If session creation will take longer, ORS will enter an overload mode and stop creating sessions until all pending session creation requests are completed.
(ORS-1669)
thread-synch-ipv, which can improve strategy execution time by preventing delays that can occur when establishing the initial connection to session processing threads.
thread-synch-ipv
Option section: orchestration
Configuration object: ORS Application object
Default value: any
Valid values: any, 4, 6.
Value changes: During startup. Option changes take effect after restart only.
This option specifies the protocol version for inter-thread communication in ORS. The value any indicates any version (this mode was used before introducing the option). The value 4 indicates the IPv4 protocol version. The value 6 indicates the IPv6 protocol version. Mixed modes are not allowed, such as 4, 6 or 6, 4.
For example: thread-synch-ipv=4
max-cache-count option. Previously, processing of the oldest sessions could fail due to ORS improperly removing active session data from the cache.
(ORS-1694)
Supported Operating Systems
New in This Release
Corrections and Modifications
http-pending-max-time
Option section: orchestration
Configuration object: ORS Application object
Default value: 10
Valid values: Any non-negative integer between 1 and 600
Value changes: Takes effect after restart.
This option defines the maximum time, in seconds, that Orchestration Server will process an HTTP request before sending a timeout response (HTTP message with status code 408) to the client.
http-orphan-session-action
Option section: orchestration
Configuration object: ORS Application object
Default value: none
Valid values: none, terminate, <valid scxml event name>
Value changes: Immediately upon notification.
This option defines the Orchestration Server action if a response to an HTTP request to create an SCXML session cannot be sent to the client or when a timeout message is already sent:
Valid values:
none—No action will be taken.
terminate—The SCXML session will be terminated.
<valid scxml event name>—The event will be sent to the SCXML session.
When an HTTP connection is closed and new one is created with same file descriptor, Orchestration Server now sends the HTTP response to the correct connection. Previously in this scenario, Orchestration Server could sometimes send the HTTP response for the request that came from the first connection to the new connection. (ORS-1662)
Orchestration Server now properly writes to the log file on a network drive when the network is restored after an outage. (ORS-1576)
Supported Operating Systems
New in This Release
Corrections and Modifications
_statePersistDefault as a new attribute to the top-level <scxml> element. Orchestration Server uses the value of _statePersistDefault as the default for the <state> _persist attribute, if it is not specified at the <state> level.
Valid values:
may—Default value. ORS will persist the SCXML session in the entered state once the event queue becomes empty.
must—ORS will immediately persist the SCXML session in the entered state.
no—ORS will not persist the SCXML session in the entered state.
Orchestration Server no longer fails to persist Sessions when the connection to a single Cassandra instance in a Cassandra cluster is lost. The issue only applies to a Cassandra cluster deployed on Linux. (ORS-1650)
Supported Operating Systems
New in This Release
Corrections and Modifications
Orchestration Server will now properly populate the event.data.requestid property for various events, such as queue.submit.done or dialog.playsound.done, when the corresponding action has been executed via Universal Routing Server. Previously, after requestid became larger than 16777215, ORS sometimes populated that property with the wrong value due to incorrect conversion of JSON-encoded event data received from Universal Routing Server.
For example, in SCXML code generated for standard Play Sound block in Composer, the transition for the dialog.playsound.done event looks like this:
<transition event="dialog.playsound.done" cond="_event.data.requestid== App_PlaySound1['requestid']" target="$$_MY_PREFIX_$$.COMPLETE">
As a result, if the event.data.requestid property has an incorrect value, a condition check will return false, the transition will never occur, and the session will remain in that state. (ORS-1632)
Supported Operating Systems
New in This Release
Corrections and Modifications
new-session-on-reroute
Option section: orchestration
Configuration object: ORS Application object
Default value: false
Valid values: true or false
Value changes: Immediately.
In the scenario of T-Server performing default routing, T-Server redirects a call that is processed by some strategy on some Routing Point. The call is then diverted and queued on another Routing Point with call state 22. Option new-session-on-reroute allows you to explicitly specify how ORS should process the call. It also enables ORS and Universal Routing Server (URS) to handle this scenario in a consistent fashion.
If new-session-on-reroute is set to true, ORS will terminate the existing live session or abort the session recovery process (whatever takes place) when it receives events related to call redirection. Upon being diverted from the Routing Point (only) with call state 22 (only), ORS breaks the existing call/session association (if any). As a result, the call becomes free to create a new session upon arriving at the default destination DN loaded with the strategy.
If new-session-on-reroute is set to false, ORS reverts to its previous behavior where it does not break the existing call/session association when it receives events related to call redirection. As for live sessions, their execution will be continued, and they will receive the usual events indicating that the initial Routing Point party disappeared. As a result, the live session can handle the situation when the call being handled is moved to another DN by T-Server in the middle of the routing process.
Note: It is necessary to keep the both ORS option new-session-on-reroute and URS option use_ivr_info synchronized (both are either true or false).
(ORS-1570)
Standard log level messages upon connecting to or disconnecting from Universal Routing Server:
Std 04503 Connected to Universal Routing Server <URS Application> at <host>, <port>
Std 04504 Connection to Universal Routing Server <URS Application> at <host>, <port> lost
(ORS-1586)
functions-by-urs and get-list-item-by-urs take effect immediately. (ORS-1560)
Now, when the functions-by-urs option is set to false, Orchestration Server overrides value of the get-list-item-by-urs option and retrieves the List item value directly from Configuration Layer. Previously, to retrieve the List item value directly from Configuration Layer, the value of both options should have been manually set to false. Note that the get-list-item-by-urs option, which covers only one function, is now obsolete should not be used. It is replaced by the functions-by-urs option, which covers six functions. (ORS-1560)
Orchestration Server now successfully detaches an interaction from a session in the scenario where the interaction originated from a DN not monitored by ORS. Previously, in such a scenario, the attempt to update User Data on behalf of such a DN could lead to a failure to detach the interaction from the session. (ORS-1559)
Orchestration Server performance under high load conditions is improved by changes in thread management and additional levels of caching. Previously, under high load conditions, Orchestration Server could experience delays during document retrieval and session creation. (ORS-1520, ORS-1499)
Changes in Orchestration Server's internal threading model and underlying ECMAScript implementation have produced more consistent and efficient ECMAScript execution times. (ORS-1497)
If persistence is enabled, Orchestration Server now successfully persists a session in a state where the _persist attribute of the <state> element is set to must. (ORS-1543)
Orchestration Server does not persist a session in a state where the _persist attribute of the <state> element is set to no. (ORS-1542)
Supported Operating Systems
New in This Release
Corrections and Modifications
_genesys.session functions: isSpecialDay, timeInZone, dateInZone, dayInZone, listLookupValue, and getListItemValue. To enable this functionality, use the new option functions-by-urs.
Note: The behavior of this option has changed in Release 8.1.300.39.
functions-by-urs
Option section: orchestration
Configuration object: ORS Application object
Default value: true (enabled)
Valid values: true or false
Value changes: Takes effect after restart. Changes to this option are not applied dynamically.
If set to true, Orchestration Server sends requests to Universal Routing Server.
If set to false, Orchestration Server retrieves information directly from Configuration Layer.
Note: When using the getListItemValue function to retrieve the List item value directly from the Configuration Layer, the new functions-by-urs option and the existing get-list-item-by-urs option should be set to false.
(ORS-1503)
dialog.play.done event in the scenario where a SIP Server failover occurs while a treatment requested by ORS is in progress. Previously, ORS did not report the dialog.play.done event in such a scenario. (ORS-1551)
Supported Operating Systems
New in This Release
Corrections and Modifications
keepalive transmissions on TCP sockets used by Orchestration Server.
http-enable-keepalive
Option section: scxml
Configuration object: ORS Application object
Default value: false
Valid values: true or false
Value changes: Takes effect after restart. Changes to this option are not applied dynamically.
If set to true, enables keepalive transmissions on TCP sockets for fetching documents from an application server.
http port of the ORS Application object. All new connections to that port will be encrypted. For detailed information on how to configure security, refer to the Genesys Security Deployment Guide.
(ORS-1232)
http-max-age and http-max-stale options configured on the ORS Application object. Previously, ORS ignored values specified in the options and loaded SCXML documents from the application server for every new session. (ORS-1477)
Orchestration Server no longer terminates unexpectedly after a T-Server is removed from the Connections tab of the ORS Application object in the Configuration Layer while processing a high volume of calls. (ORS-1495)
Supported Operating Systems
New in This Release
Corrections and Modifications
Orchestration Server no longer delays sending new statistic subscription requests to Universal Routing Server in the scenario where the same statistic for the same object was simultaneously requested from two or more SCXML applications. (ORS-1500)
Supported Operating Systems
New in This Release
Corrections and Modifications
GET request for /heartbeat URI in the format http://<ORS_host>:<ORS_HTTP_port>/heartbeat, it responds with 200 OK. If an ORS instance is running in Backup mode, it responds with 503 Service Unavailable or with the HTTP response code defined in the new configuration option heartbeat-backup-status.
heartbeat-backup-status
Option section: orchestration
Configuration object: ORS Application object
Default value: 503
Valid values: Valid HTTP response codes
Value changes: Immediately
This option allows you to define a valid HTTP response code sent by an ORS instance running in Backup mode to the requestor, after receiving a heartbeat query.
Note: It is recommended to configure health monitoring in deployments with Load Balancing.
(ORS-1451)
Debug log message level assignments, which allow configuring ORS logging so that log output will contain enough information for initial troubleshooting but, at the same time, produce log output that is significantly more compact than a full Debug log. Recommended log configuration (only relevant options mentioned):
[log]
verbose=all
x-print-attached-data=1
x-server-config-trace-level=3
x-server-gcti-trace-level=3
x-server-trace-level=1
[orchestration]
map-composer-log-levels=true
scxml-log-filter-level=1:TRC;2:STD;3:TRC;4:DEBUG;5:ALR
Note: Setting the scxml-log-filter-level option value to 1, 2, 3, 4 or 5 will override the logging results of the map-composer-log-levels option.
(ORS-1392)
sessionfm-fetch-timeout option to set a custom value of the timeout attribute used in the <session:fetch> action element.
sessionfm-fetch-timeout
Option section: orchestration
Configuration object: ORS Application object
Default value: 60
Valid values: Any integer from 0 to 86400
Value changes: Immediately
This option specifies the timeout in seconds that ORS will use when the timeout attribute is omitted in the <session:fetch> action element.
Note: When ORS is operating on Windows, due to the operating system default settings, the timeout reaches a 21-second maximum regardless of the value configured in the sessionfm-fetch-timeout option.
(ORS-1463)
_transitionStyle attribute in the <scxml> element. It allows defining the order in which the <transition> content will be executed when the <parallel> action element contains two or more transitions.
Valid values:
legacy—Default value. Transitions are executed by line number order (transition child elements closer to the top of document are executed first). It mimics the behavior used in Orchestration 8.1.2.
w3c—Transitions are executed in the order in which they were selected. Transition selection order is from the least-nested parallel branch to the most-nested parallel branch. Tie-breaker is the lowest line number (transition child elements closer to the top of the document are executed first).
genesys—Transitions are executed in the order from the most-nested to least-nested. Tie-breaker is the highest line number (transition child elements closer to the bottom of document are executed first).
(ORS-1350)
Supported Operating Systems
New in This Release
Corrections and Modifications
map-composer-log-levels option, which allows mapping of log levels defined in the <log> action element into the specific Genesys log events.
map-composer-log-levels
Option section: orchestration
Configuration object: ORS Application object
Default value: false (disabled)
Valid values: true or false
Value changes: Immediately
If enabled, Orchestration Server will generate log events of the Alarm, Standard, Interaction, Trace or Debug levels. The log levels defined in the level attribute of <log> element are mapped as follows:
Info (log level 1) is mapped into the Trace log event 23023
Error (log level 2) is mapped into the Standard log event 23011
Warning (log level 3) is mapped into the Interaction log event 23022
Debug (log level 4) is mapped into the Debug log event 23026
Alarm (log level 5) is mapped into the Alarm log event 23012
Note: Setting the scxml-log-filter-level option value to 1, 2, 3, 4 or 5 will override the logging results of the map-composer-log-levels option.
scxml-log-filter-level option is expanded to allow defining multiple custom log levels as well as mapping to specific Genesys log events.
scxml-log-filter-level
Option section: orchestration
Configuration object: ORS Application object
Default value: Empty (disabled)
Valid values: Any valid combination of custom-defined and Genesys log levels, where:
Custom log level: An Integer composed of the digitsValid changes: Immediately1,2,3,4, or5and less than or equal to 9 digits in length (minimum of 1 and maximum of 555555555).
Genesys log levels:STD,INT,TRC,ALRandDEBUG. These are not case-sensitive.
If this option is configured and the level parameter of the __Log function or level attribute of the <log> action element in the SCXML application matches the custom log level value, ORS generates corresponding Genesys log events of the Standard (23011), Alarm (23012), Interaction (23022), Trace (23023) or Debug (23026) levels. The value of scxml-log-filter-level option can contain:
a. A semi-colon list of colon-delimited pairs of custom and Genesys log levels.Note: Setting the
b. A semi-colon list of custom log levels (no explicit mapping to Genesys log levels). ORS always generates a log event of theStandard(23011) level.
c. Any combination of both value types listed above.
scxml-log-filter-level option value to 1, 2, 3, 4 or 5 will override the logging results of the map-composer-log-levels option.
Examples
For example, if the SCXML application contains:
<log> action element:
<orlog expr="'Custom Log Level 45'" label="'Test example'" level="45" />
<log expr="'Custom Log Level 222'"label="'Test example'"level="222" />
__Log() function:__Log('Custom Log Level 45','Test example','45');
__Log('Custom Log Level 222','Test example','222');
scxml-log-filter-level = 45:TRC;222:INT
ORS will generate following events:
Trc 23023 METRIC<log sid='31RJ0AHJQP3851BFQ6QSJR0LA4000001' expr='Custom Log Level 45' label='Test example' level='45' />
Int 23022 METRIC<log sid='31RJ0AHJQP3851BFQ6QSJR0LA4000001' expr='Custom Log Level 222' label='Test example' level='222' />
b. scxml-log-filter-level = 45;222
ORS will generate following events:
Std 23011 METRIC<log sid='31RJ0AHJQP3851BFQ6QSJR0LA4000001' expr='Custom Log Level 45' label='Test example' level='45' />
Std 23011 METRIC<log sid='31RJ0AHJQP3851BFQ6QSJR0LA4000001' expr='Custom Log Level 222' label='Test example' level='222' />
c. scxml-log-filter-level = 45:TRC;222
ORS will generate following events:(ORS-1427)
Trc 23023 METRIC<log sid='31RJ0AHJQP3851BFQ6QSJR0LA4000001' expr='Custom Log Level 45' label='Test example' level='45' />
Std 23011 METRIC<log sid='31RJ0AHJQP3851BFQ6QSJR0LA4000001' expr='Custom Log Level 222' label='Test example' level='222' />
List Item values from Transaction List objects directly from Configuration Layer without having to query Universal Routing Server. To enable this functionality, use the new option get-list-item-by-urs.
get-list-item-by-urs
Option section: orchestration
Configuration object: ORS Application object
Default value: true (enabled)
Valid values: true or false
Value changes: Take effect after restart. Changes to this option are not applied dynamically.
If set to true, Orchestration Server will send a request to Universal Routing Server to get the List item value from Transaction List objects configured in Configuration Layer.
If set to false, Orchestration Server will retrieve the List item value directly from Configuration Layer.
Standard log level messages related to connection to Cassandra:
Std 23024 Connected to Cassandra at host '<host_name>', port <port_number>.
Std 23025 Connection to Cassandra at host '<host_name>', port <port_number>, lost.
duration attribute in the
<doc_retrieved>
METRIC. For example:
16:42:02.279 METRIC <doc_retrieved sid='AB12DEFG34HI56PLRLNRF5QP9K000006' result='success' url='http://appserver/scxml/route_to_agent.scxml' cached='false' duration='750' />
Orchestration Server 8.1.3 now properly populates the AttributeExtensions of a RequestMakeCall
request with the hints attribute specified in the <ixn:createcall> action
element. (ORS-1312)
When debugging SCXML applications, Orchestration Server no longer terminates a session when infinite loop prevention is enabled. Now, ORS disables loop prevention functionality when the Debug Client is connected. (ORS-1407)
Orchestration Server no longer terminates unexpectedly when working with Universal Routing Server releases earlier then 8.1.3. (ORS-1377)
Supported Operating Systems
New in This Release
Corrections and Modifications
RequestPrivateService to SIP Server when the resource attribute is not specified in the <ixn:privateservice> action element when an inbound call diverted from a Routing Point to an external destination is answered. When integrated with SIP Server, the extensions parameter of the <ixn:privateservice> action element should contain key-value pair AOC-Destination-DN with the value referring to the party in established state where the AoC (Advice of Charge) notification should be delivered.
Note: This feature is available when integrated with SIP Server beginning with version 8.1.100.93. (ORS-1367)
The URL of the SCXML application specified in the url option or alternate-url option may contain parameters in the format $$parameter-name$$ where parameter-name should match the name of the option configured in the ApplicationParms section. When this parameter-name is found, the parameter will be substituted for its value. For example, configure the following options in the ApplicationParms section:
APPSERVER1=http://appserver:8080
REGION1=CA
REGION2=NY
Configure the url and alternate-url options in the Application section:
url=$$APPSERVER1$$/service/$$REGION1$$/Workflow1.scxml
alternate-url=$$APPSERVER1$$/service/$$REGION2$$/Workflow2.scxml
The url will be substituted at run-time with:
http://appserver:8080/service/CA/Workflow1.scxml
The alternate-url will be substituted at run-time with:
http://appserver:8080/service/NY/Workflow2.scxml
- Sessions started using an HTTP request with parameters. For example:
http://localhost:17011/scxml/session/start?
src=http://appserver:8080/service/CA/Workflow1.scxml&APPSERVER1=http://appserver:8080®ION1=CAThese parameters can be utilized in a started SCXML application as a value of the
hrefattribute in an <xi:include> action element. For example:<xi:include href="$$APPSERVER1$$/service/$$REGION1$$/RouteToAgGroup.scxml" . . ./>
At run-time, the
hrefvalue will be substituted with:"http://appserver:8080/service/CA/RouteToAgGroup.scxml"
- Session started with parameters specified in <session:start> action element. For example:
<session:start sessionid="_data.NewID" src="_data.Path + '/Workflow1.scxml'">
<
param name="APPSERVER1" expr="'http://appserver:8080'"/>
<param name="REGION1" expr="'CA'"/><
/session:start>These parameters can be utilized in a started SCXML application as a value of the
hrefattribute of an<xi:include> action element:
<xi:include href="$$APPSERVER1$$/service/$$REGION1$$/RouteToAgGroup.scxml" . . ./>At run-time, the
hrefvalue will be substituted with:"http://appserver:8080/service/CA/RouteToAgGroup.scxml"
Notes:
parameter-name can be used in all subroutines started from the main SCXML session.
To avoid unexpected outcomes, Genesys recommends avoiding a parameter-name with a space at the beginning, end, or in the middle.
parameter-name is case-sensitive.
(ORS-1363)
Orchestration Server now populates all key-value pairs into RequestUpdateUserData when the input parameter of the_genesys.ixn.setuData function is an Array object containing more than 100 elements. Previously, ORS did not populate the 100th key-value pair into RequestUpdateUserData sent to T-Server. (ORS-1362)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in the 8.1.3 release of Orchestration Server.
ORS now supports a Multiple Data Center architecture where each Data Center is served by a cluster of ORS nodes with support for Data Center failover.
In Orchestration Server 8.1.3, the cluster is configured by creating a Transaction object of type List. Each section in the
List represents a single Orchestration cluster. Each of the key/value pairs in that section links a specific Orchestration application to a
Data Center.
In ORS 8.1.3, by default, the pulling of multimedia interactions is not enabled. To allow pulling of interactions, the mcr-pull-by-this-node option
should be set to true.
The Apache Cassandra open source solution packaged with Genesys Orchestration Solution now supports a single Cassandra instance across multiple Data Centers.
Support for a new version of Cassandra: ORS supports Apache Cassandra 1.1.x, beginning with Version 1.1.12.
Orchestration Server now supports automatic Cassandra schema loading upon the first successful connection to the Cassandra cluster.
Beginning with release 8.1.3, Orchestration Server connection to Cassandra is not required. Note that if a connection is not present, Session recovery and Scheduled session functionality are not available.
Enhanced voice interaction action: The <createcall> action with type predictive was extended by providing
Call Progress Detection (CPD) results for voice interactions in Interaction interface events. The CPD result shows the outcome, either positive
(live voice), semi-positive (answering machine, fax, or silence), or negative (busy, no answer, and so on) of an attempt to reach an intended
party. This allows ORS to determine the next actions for this interaction, such as redialing at a later time for negative call results or
connecting an established outbound call to a pre-recorded message instead of an agent for "answering machine" call result.
Orchestration Server 8.1.3 performs " loop prevention," checking to avoid infinite loops between states, or in situations where a state is entered an endless number of times as a direct result of a transition element, when processing an SCXML application. The following new options support infinite
loop prevention: max-state-entry-count, max-microstep-count, max-pending-events, and process-event-timeout.
Multi-site support is enhanced and simplified: processing of multi-site interactions now separates interaction objects from different sites between different SCXML strategies.
Orchestration Server now allows the saving of a compiled SCXML Application as a separate file into an ORS
working directory if the new _debug attribute specified in the <scxml> action
element is set to true. The resulting scxml file is named according to the session ID. (ORS-1197)
When debugging an SCXML Application with Composer, for a session started using the HTTP interface, Orchestration Server now returns the session ID as soon as the session is created.
Orchestration Server now supports controlling the lifetime of a session. The maximum session age in seconds is configured in the
max-session-age option in the scxml section of the ORS application or in the _maxtime
attribute in the <scxml> action element. After this age is reached, ORS attempts to exit the session.
To disable this feature, set the max-session-age to 0.
Note that the value specified in the _maxtime attribute overrides the value in the
max-session-age configuration option. Connection to Cassandra is required for this functionality.
Orchestration Server now supports serialization of session parameters by configuring the new
option parse-start-params in the Orchestration section of the ORS application. When this option is set
to true, parameters delivered to the child session which were started using <invoke> or
<session:start> action elements retain their original type. When the option is set
to false, the session parameters are converted to string. (ORS-1151)
Orchestration Server now generates a Standard level log message for each statistic.update event in the following format:
Std 23011 Statistic Update: statistic object='<name_of_statistic_object>';
statistic name='<name_of_statistic>'; statistic value=<value_of_statistic>.(ORS-1161)
Orchestration Server now allows you to specify a URL destination with a new option, external-url, to redirect HTTP requests in scenarios when an HTTP request about a specific session is delivered to an ORS node that is not handling the session. This URL will be populated into the Location header of a 307 Temporary Redirect response as a redirect target.
external-url
Option section: Orchestration
Configuration object: Application
Default value: None
Valid values: Any valid URL
Value changes: For the next interaction
Configure this option on the Primary ORS Application object. Set its value to the URL of Load Balancer located in front of the ORS node. Another ORS node will use this option and populate its value into the Location header of a 307 Temporary Redirect response as a redirect target. It allows delivery of the HTTP request to the session owner. (ORS-1339)
This release contains the following corrections and modifications:
Orchestration Server now sends the HTTP fetch request to the address specified in the alternate-url option
after the fetch-timeout has expired. (ORS-1057, ORS-1048)
Orchestration Server no longer terminates on startup if connection to Cassandra is not established. ORS 8.1.3 does not require a connection to Cassandra. If a connection is not present, a corresponding error message is printed in the log and ORS continues to operate. Note that Session Recovery and Scheduled Session functionality will not be available. (ORS-1055)
Orchestration Server 8.1.3 now correctly handles processing of voice interactions where, due to the network related issues, ORS nodes have inconsistent information about which T‑Server from an HA pair is running in primary mode. Previously, in these scenarios the same interaction was processed by multiple nodes. (ORS-1029)
The "split-brain" scenario issue, in which a reconnect between Super Nodes leads to two Master Super Nodes, is resolved with the new architecture. Orchestration Server 8.1.3 does not support Super Nodes and Master Super Nodes in the new ORS cluster architecture. (ORS-1018)
Orchestration Server no longer terminates on startup if there are stuck sessions in Cassandra. (ORS-991)
A change in cluster configuration no longer results in Orchestration Server termination. This issue is resolved with the new ORS 8.1.3 architecture. (ORS-990, ER# 316085692)
Session processing thread mechanism has been improved. Issue with stuck threads no longer occurs. (ORS-989)
Orchestration Server no longer places multimedia interactions back into the queue when an ORS Node terminates. The processing of these interactions continues when ORS is restarted. (ORS-980)
Orchestration Server no longer places multimedia interactions back into the queue when the interaction is routed to the agent. (ORS-974, ER# 313650126)
Supported Operating Systems
New in This Release
Corrections and Modifications
This release contains the following corrections or modifications.
Orchestration Server no longer prints misleading event processing error messages in the log. (ORS-1491)
Supported Operating Systems
New in This Release
Corrections and Modifications
keepalive transmissions between Orchestration Server nodes within a cluster.
tcp-keepalive-time
Option section: cluster
Configuration object: ORS Application object
Default value: -1 (disabled)
Valid values: -1 or any integer greater than 0
Value changes: During startup. Changes to this option are not applied dynamically.
The duration (in seconds) between two keepalive transmissions in idle condition.
clusterApplication objectThe number of retransmissions to be sent out before declaring that the remote Orchestration Server node(s) is not available.
tcp-keepalive-intervalclusterApplication object
The duration (in seconds) between two successive keepalive retransmissions, if an acknowledgement to the previous keepalive transmission was not received.
This release does not contain any new corrections or modifications.
Supported Operating Systems
New in This Release
Corrections and Modifications
This release contains the following corrections and modifications:
Orchestration Server no longer delays session creation while operating under a large workload in a high-concurrence environment where internal tasks are competing for resources. (ORS-1326)
The process of negotiation between Orchestration Server Super Nodes to select the new Master Super Node has been improved. Orchestration Server now correctly selects one Master Super Node in a scenario where an existing Master Super Node has been disconnected from the cluster by a temporary network outage. Previously, a temporary disconnect of the Master Super Node could result in two ORS Master Super Nodes controlling the same call. (ORS-1313)
Orchestration Server now sends RequestDistributeUserEvent to the correct Network T-Server when operating with multiple
Network T-Servers. To insure proper results, the interactionid attribute must be specified in the <ixn:userevent>
action element. Previously, RequestDistributeUserEvent was sometimes distributed to the incorrect Network T-Server. (ORS-1299)
Orchestration Server now generates an error.queue.cancel event after receiving an error message from Universal Routing Server in
response to the <queue:cancel> action. Previously, in this scenario, ORS did not report the error.queue.cancel event
and there was no possibility for a transition to the next state. (ORS-1296)
Orchestration Server now successfully selects a new Master Super Node in a scenario where the existing Master Super Node has been disconnected from the cluster due to a temporary network outage. Previously, a temporary disconnect of the Master Super Node could lead to a failure of the ORS cluster to select a new Master Super Node. (ORS-1288)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new functionality:
interaction.onrouterequest,
which is generated upon receiving EventRouteRequest from a T‑Server
application. The new event allows the handling of special call flows
when the EventRouteRequest is delayed by a T‑Server.
The SCXML application should be updated to wait
for the interaction.onrouterequest event before continuation of
the SCXML application execution. (ORS-1302)
This release contains the following correction or modification:
Orchestration Server now properly populates the AttributeExtensions of a TMakeCall request with the hints attribute specified in the <ixn:createcall> action element. (ORS-1306)
Supported Operating Systems
New in This Release
Corrections and Modifications
This release contains the following correction or modification:
Orchestration Server no longer becomes unstable upon receipt of a large number of EventPlaceAgentState messages from Interaction Server in a short duration. Previously, Orchestration Server could terminate in this scenario. (ORS-1278)
Supported Operating Systems
New in This Release
Corrections and Modifications
This release contains the following corrections and modifications:
Orchestration Server now properly registers Routing Points and other types of DNs added to the configuration while ORS is running. Previously, these configuration changes were ignored. (ORS-1247)
Supported Operating Systems
New in This Release
Corrections and Modifications
This release contains the following corrections and modifications:
Orchestration Server no longer becomes unstable during race conditions while executing an
SCXML application triggered by a call transferred to a Routing Point.
Previously, ORS could terminate when EventTreatmentNotApplied was reported by T‑Server
in response to the RequestGiveRingBackTreatment issued by Universal Routing Server. (ORS-1227)
Orchestration Server no longer becomes unresponsive if a new session is created at the same time an existing session ends. (ORS-1233)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new functionality:
Orchestration Server now supports <ixn:clear> and <ixn:terminate> action
elements after <ixn:detach> element to operate on uncontrolled interactions.
(ER# 324881288)
This release does not contain any new corrections or modifications.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new functionality:
Orchestration Server now handles conflicts that may arise during excessive network latency or temporary network outages, and prevents a "split-brain" scenario from occurring wherein two Super Nodes attempt to promote themselves to Master Super Node.
The new configuration option worker_node_connect_timeout is introduced
to control the preventative behavior.
worker_node_connect_timeout
Option section: cluster
Configuration object: ORS Application object
Default Value: 0 (disables functionality)
Valid Values: Any positive integer (in seconds)
Value changes: During startup. Changes to this option are not applied dynamically.
This option specifies the waiting time for a Worker Node to connect or reconnect to a quorum of Super Nodes. The option must be set on each Super Node in the same cluster. This feature requires a minimum of 3 Super Nodes to be configured.
If the option is enabled, the following behavior is observed:
A quorum is defined as the number of configured Super Nodes in the cluster, divided by 2, rounded down to the nearest integer, plus 1. For example, if there are 3 Super Nodes configured, a quorum would be 3/2 + 1, or 2 Super Nodes.
If Orchestration Server exits upon one of the above conditions, the following log message will be generated:
Std 21034 // ORS Cluster: Stopping node %ld - worker node unable to connect to %d super
nodes of the %d configured super nodes.
Where %ld - DBID of the Application, the first %d – quorum of configured Super Nodes,
and the second %d – number of configured Super Nodes.
(ER# 322692464 )
This release does not contain any corrections and modifications.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality:
This release includes the following corrections and modifications:
The processing of scenarios causing race conditions, while operating under a large workload, has been improved. Previously, Orchestration Server could terminate unexpectedly in such scenarios. (ER# 322246393)
Orchestration Server now properly restores variables defined within the <state>
element upon recovery of the persisted session. Previously, ORS sometimes failed to
restore variables in such a scenario. (ER# 322280941)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new functionality:
The chat object has been extended with new queue
and view properties for the chat interactions processed by Interaction
Server. (ER# 322059070)
This release includes the following corrections and modifications:
Orchestration Server no longer creates sessions for new calls after the Orchestration section was
deleted from the Annex tab of the Route Point configuration object
while operating in the load-sharing Network T‑Servers or IVR T‑Servers environment.
Previously, in such scenarios, ORS ignored configuration updates. (ER# 317849739)
The _genesys.ixn.interactions[x].voice.acdq function now returns the correct acdq
property value during execution of the SCXML application that is triggered by the call's arrival to a
Route Point in the scenarios affected by an events delay.
Previously, in such scenarios, an 'undefined' acdq property value was returned.
(ER# 322265291, 321764481)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new functionality:
Orchestration Server now supports the new configuration option stuck-thread-timeout.
stuck-thread-timeout
Option section: scxml
Configuration object: ORS Application object
Default Value: 60000
Valid Values: Any positive integer
Value changes: During startup. Changes to this option are not applied dynamically.
This option specifies waiting time in milliseconds before declaring a
session processing thread as being stuck.
(ER# 319231219 )
This release includes the following corrections and modifications:
Orchestration Server no longer terminates when a single session processing thread is stuck while other threads in the pool remain unoccupied.
Note: In a scenario in which all session processing threads are declared stuck, ORS will exit and log the list of all stuck session IDs.
(ER# 319231219 )
Orchestration Server now successfully retrieves data from the files specified in the
<xi:include> element where the attribute parse="text",
if the included file contains non-ASCII characters. The value of the ORS
default-encoding option should be set according to the actual encoding of the included
document. (ER# 315131079 )
Orchestration Server now successfully delivers delayed events simultaneously sent by SCXML applications. Previously, some events were not delivered. (ER# 317604961 )
Orchestration Server no longer terminates unexpectedly while processing scripts or recovering data with content greater than 64 kilobytes. Previously, such scenarios caused Orchestration Server to terminate. (ER# 321580261)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality:
This release includes the following corrections and modifications:
Orchestration Server (ORS) no longer becomes unstable when subscribing a statistic if Stat Server is not running. Previously, in this scenario, ORS may have terminated while processing subscription events received from Universal Routing Server. (ER# 319398286)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality:
This release includes the following corrections and modifications:
Orchestration Server now sends the RequestRouteCall to the correct Network T-Server when operating with multiple Network T-Servers. Previously in this scenario, ORS sometimes sent a RequestRouteCall to the incorrect Network T-Server. (ER# 318890954)
Orchestration Server now re-subscribes to the statistics after a temporary disconnect from Universal Routing Server or a URS switchover. Previously, a restart of ORS was required. (ER# 318343075)
While operating under a large workload, Orchestration Server no longer terminates unexpectedly
when it sends RequestApplyTreatment to the T‑Server during execution of the SCXML
application if the device
attribute is specified in the <dialog:start> action. (ER# 317377466)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new functionality:
ORS now supports the new configuration option scxml-log-filter-level
to enhance logging control. This option must be specified in the orchestration
section of the ORS application.
scxml-log-filter-level
Default Value: Empty string
Valid Values: Any combination of the digits 1,2,3,4,5 (minimum of 1 and maximum of 555555555)
Changes Take Effect: Immediately
If this option is configured and the level parameter of the __Log function or level attribute of the <log> element in the SCXML application equals to the option value, ORS generates corresponding log events of the Standard level.
For example, if scxml-log-filter-level = 45:
<log expr="'This is level 45...'" label="23011" level="45" //>
or
__Log('This is level 45...',23011,45);
then the following log is generated:
Std 23011 METRIC <log sid='MGRMMP0T1L1JN5U4TN7N5MOFPS000002' expr=''This is level 45...' label='23011' level='45' />
(ER# 316293355)
ORS now supports the new configuration option mcr-pull-by-msn-only
to limit the pull capability of queued eServices interactions to the
current Master Super Node. This option must be specified in the orchestration section of the ORS application.
mcr-pull-by-msn-only
Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately
This option must be configured in the same way for all nodes in the ORS cluster. If the option is set to true, only the current Master Super Node will pull interactions.
If the option is not specified or set to false, any Node configured for eServices will pull interactions.
The startup process should be such that if there are multiple Super Nodes, and some of them are not configured for eServices, that the Super Nodes configured to process eServices interactions should be started first.
(ER# 316497633)
This release includes the following corrections and modifications:
ORS no longer sends other error messages to Composer when
debugging the SCXML application. Previously, an error message caused the
termination of the debugging session. (ER# 316308851)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
ORS now successfully attaches an interaction to the session by using the <attach>
action during execution of the SCXML application that is triggered by a
consultation call transferred to a Routing Point where the call was
previously transferred between multiple sites before an agent answered
the call and initiated a consultation. (ER# 316029691)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
ORS no longer fails an <unsubscribe> action when an SCXML application is unsubscribed from a particular statistic for the session. Previously, when ORS failed an <unsubscribe> action, it incorrectly generated a <requestid> attribute. (ER# 314894170)
ORS now correctly starts an SCXML script on a Routing Point when a call is transferred to the Routing Point from a non-monitored party. (ER# 314039407)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new functionality:
A new Queue Functional Module function named useMediaChannel
is introduced with this release to specify the type of controller that
owns the interaction (either T‑Server/SIP Server or Interaction Server).
Queue FM assumes T‑Server/SIP Server as the default controller type.
void _genesys.queue.useMediaChannel (ixnid, enable)
Parameters (all parameters are mandatory):
ixnid: STRING which can be a variable or a constant -
This parameter defines the ID of the interaction which should have this
action applied. enable: BOOLEAN which can be a variable or a
constant - This parameter defines whether the interaction is controlled
by T‑Server/SIP Server (if it is set to false) or Interaction Server (if it is set to true).
Returns: void
Using this functionality requires URS 8.1.200.25 or later.
(ER# 302470293)
The SCXML <transition> element now accepts a
space delimited list of events in the attribute event. Previously, only
one event could be specified. (ER# 311243887)
In an ORS Cluster deployment, a new session will not be created by the Member Node if none of the defined Super Node(s) are running. On an attempt to process a voice interaction, one of the following log messages will be generated:
21031 - STANDARD Super node is not running 21032 - STANDARD Master Super node is not known
Note: For eServices interactions, the 21031 message will not be observed. If no Super Node is connected on startup, interactions are not pulled, and the session creation process will not be invoked.
(ER# 310445683, 310445681)
ORS Nodes will not start if Super Nodes are not defined in the ORS Cluster. (ER# 310372305)
ORS now supports the new option js-preload-files. This option should be specified in the scxml section of the ORS application.
js-preload-files
Default Value: No value
Valid Values: A semi-colon delimited list of JavaScript files
Changes Take Effect: On restart
This option provides a list of JavaScript files that are preloaded at ORS startup. If the full file path is not provided, ORS will look for files in the ORS working directory. This allows users to specify functions or variables that are available to all sessions.
(ER# 310659766)
ORS now supports the new configuration option webfm-event-hold-response to enhance behavior of WebFM Event responses. This option should be specified in the orchestration section of the ORS application.
webfm-event-hold-response
Default Value: true
Valid Values: true, false
Changes Take Effect: Immediately
When this option is set to true, the HTTP response depends on how the event is processed:
200 and Reason-Phrase: OK 204 and Reason-Phrase: No Content
400 and Reason-Phrase: Bad Request
When the option is set to false, once the event has been successfully published, ORS responds with 200 OK
(ER# 310659761)
In the SCXML application, HTTP Response headers presented as key-value pairs can be accessed in the header attribute of the session.fetch.done event. (ER# 310649463)
This release includes the following corrections and modifications:
ORS no longer terminates unexpectedly in scenarios where Statistic requests for a skill expression are defined as a Target.
Note: Genesys recommends using only defined and valid statistic objects.
(ER# 306847103)
The Dialog Functional Module now correctly populates ROUTE for the key name in AttributeTreatmentParms of the TApplyTreatment request for the treatment type RAN. Previously, the RAN key name was populated. (ER# 312099651)
The events specified in the event attribute of a transition element will now be trimmed of whitespace before they are compared against processed events. (ER# 309581091)
ORS no longer creates a session for eServices interactions which are not pulled and are redirected to another ORS managed queue. URS version 8.1.200.25 or later is required. (ER# 309957451, 310191649)
The done.invoke.child-session-id event is now returned to the invoking SCXML session when an invoked session is terminated. (ER# 309370609)
The _genesys.ixn.getMediaIntValue function now returns -1 when the media type is not found. Previously, it was returning 0 (zero) when the string was not found. (ER# 311016211)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
When using <send> to generate events, and an event that has been sent needs to be canceled, the idlocation attribute should be used instead of id. To use <cancel>, either the id or the sendid attributes can be used. However, both cannot be defined at the same time. (ER# 308626629)
ORS now supports the new default-encoding option to correctly process the return value of the getListItemValue function. This option should be specified in the scxml section of the ORS application.
default-encoding
Default Value: UTF-8
Valid Values: Any valid converter name supported by ICU
Changes Take Effect: After restart
This option activates Unicode support for List Objects. When this option
is set to the valid name of a converter, ORS correctly processes the
return value of the getListItemValue function if the return value contains non-English symbols.
(ER# 311209208)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
ORS now correctly restores sessions after a switchover when the SCXML contains session states with a "." in them. (ER# 307294603)
ORS now correctly provides unique submit IDs to URS when invoking multiple queue:submit
requests for the same session. Previously, this resulted in
intermittent loss of target groups attached to the call by router, and
failure to route the call.
Please note the following:
queue:submit is not supported.
(ER# 307877672)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new functionality:
priorityLimits function. This
function provides maximum and minimum limits on priority values for an
Interaction in a queue. Using this functionality requires URS 8.1.200.22
or later.This release includes the following corrections and modifications:
ORS now includes the key MediaType with the value of the Interaction media type within the UpdateVirtualCall context user data for eServices interactions. (ER# 305094059)
ORS no longer becomes unstable if a server connection is removed from the ORS Connection tab while ORS is active. (ER# 304342767)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This section describes new features that were introduced in this release of Orchestration Server (ORS).
This release includes the following corrections and modifications:
With this release of ORS, the following keys of user data key-value
pairs have been added to VirtualCalls created for eServices. The values
are taken from EventPartyStateChanged when an email is queued to the ORS controlled Interaction Queue.
| Keys |
|---|
PlacedInQueueAt |
MediaType |
ParentId |
TenantId |
InteractionType |
InteractionSubtype |
InteractionState |
IsOnline |
IsLocked |
Queue |
SubmittedBy |
ReceivedAt |
SubmittedAt |
MovedToQueueAt |
For example:
'InteractionId' [str] = "0007Sa6W88DY001F"
'TenantId' [int] = 101
'MediaType' [str] = "email"
'InteractionType' [str] = "Inbound"
'InteractionSubtype' [str] = "InboundNew"
'InteractionState' [int] = 1
'IsOnline' [int] = 0
'IsLocked' [int] = 0
'Queue' [str] = "Sales_test"
'SubmittedBy' [str] = "E-MailServer"
'ReceivedAt' [str] = "2011-05-24T14:50:37Z"
'SubmittedAt' [str] = "2011-05-24T14:50:58Z"
'PlacedInQueueAt' [str] = "2011-05-24T14:51:05Z"
'MovedToQueueAt' [str] = "2011-05-24T14:51:05Z"
Note: ParentId is only present if the interaction is created within ORS from an existing session/interaction. For example, if ixn:createmessage is used to create a new email, this new email has a ParentId with the interaction ID of the interaction that created it.
(ER# 304037808)
ORS no longer has the possibility to become unstable when it logs the
content of an email. Previously, this may have occurred when the value
of the x-server-trace-level option was set to 3. (ER# 296157257)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
ORS now correctly sends TUpdateUserData requests to a
Network T-Server that owns a call in environments where ORS operates
with multiple Network T-Servers, and the value of the switch-multi-links-enabled option is set to true (and set to 1 on the switch level). (ER# 303524897)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
ORS now adds the following Key-Value pair when creating a virtual call within URS for MCR type interactions:
| Key | Value |
|---|---|
InteractionId |
The value of _attr_itx_id for the interaction. |
This is reflected in events distributed from URS within the user data.
(ER# 302357627)
ORS now reports when Cassandra requests exceed a configurable latency. ORS also reports, after the configured maximum latency is exceeded, if the latency falls below the configured maximum latency. These are standard log messages that ORS reports:
23007 // ORS WARNING Cassandra latency %d ms, exceeds the expected latency of %d ms on %s request
Where the first %d is the latency, the second %d is the configured
maximum latency, and %s is an indication of the ORS request that
experienced the excessive delay.
23008 // ORS Cassandra latency %d ms, has recovered from excessive latency condition on %s request
Where %d is the latency of the request that recovered from the excessive delay, and % s is an indication of the ORS request.
Note: No warnings are reported when Cassandra requests do not exceed the configurable latency.
A new ORS configuration option has been introduced to the Orchestration/Options/persistence section to define the maximum latency:
cassandra-max-latency
Default Value: 100
Valid Values: Any number greater than 0
Changes Takes Effect: After restart
Defines the maximum latency, in milliseconds, to allow before reporting excessive latency, and recovery.
(ER# 300170362)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
Starting with this release, a new ORS configuration option has been introduced to the Orchestration/Options/orchestration section as follows:
switch-multi-links-enabled
Default Value: false
Valid Values: true, false
Changes Take Effect: After restart
This option determines whether ORS supports multilink switch
configurations (load sharing Network T‑Servers or IVR Servers). When
set to true, ORS enables support of multilink switch configuration. When set to false, ORS does not enable multilink switch support.
Note: The ORS switch-multi-links-enabled configuration option and the switch-multi-links-enabled configuration option specified on the load sharing switch object must both be enabled to support this functionality.
The switch-multi-links-enabled option, specified on the load sharing switch object (Switches\"SharedSwitchObject"\Annex\gts),
determines whether the switch is working in load-balancing mode; that
is, it is served by multiple Network T‑Servers or IVR T‑Servers.
Orchestration uses this option to determine whether to enable connection
to more than one Network T‑Server or IVR T‑Server serving this switch.
switch-multi-links-enabled
Default Value: 0
Valid Values:
| Value | Description |
|---|---|
1 |
A network or IVR switch in load-balancing mode. |
| Any other integer | Not a network or IVR switch in load-balancing mode. |
This option should be used only in a configuration in which Network T‑Servers or IVR T‑Servers are working in load-balancing mode; that is, when there is no duplication in notification events received in Orchestration via connections to these T‑Servers. Currently, load balancing mode is supported only for Network T‑Servers and IVR T‑Servers.
(ER# 301592364, 300981248)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
It is no longer possible for a deadlock to occur when URS fails and certain functions are used. (ER# 296405133)
ORS now correctly reports an error if the interaction ID is incorrectly specified in <ixn:sendmessage>. Previously, ORS incorrectly sent an email. (ER# 295868980)
ORS now periodically interrogates the SCXML Engine threads to determine
if they are actively processing sessions. If no threads respond, an 23004 ORS SCXML engine threads not responding ERROR: Orchestration terminating error message is issued and Orchestration Server exits. (ER# 296514679)
For multimedia interactions processed by ORS, the age of an interaction, if used, is now defined by the interaction property ReceivedAt.
Previously, the age of multimedia interactions were defined by the time
the interaction was pulled by URS from the Interaction Queue.
Note: For this functionality to work properly, URS version 8.1.200.18 (or later) is required.
(ER# 298843027)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in this release of Orchestration Server (ORS).
extensions data in redirect and all dialog functional module actions. (ER# 293135012)resource for the interaction functional module action <terminate>. It provides a value expression which returns the resource address for the call to be terminated. (ER# 281813085)EventTreatmentNotApplied). (ER# 294565991) This release does not contain any corrections and modifications.
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in this release of Orchestration Server (ORS).
This release does not contain any corrections and modifications.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This section describes new features that were introduced in this release of Orchestration Server (ORS).
This release introduces the following new configuration options within the scxml section:
max-preprocessor-cached-doc-size
Default Value: 10000000
Valid Values: Any non-negative integer
Changes Take Effect: After restart
The maximum size (in bytes) of the cached results of the preprocessed document.
max-compiler-cache-size
Default Value: 10000000
Valid Values: Any non-negative integer
Changes Take Effect: After restart
The maximum amount of memory (in bytes) allowed for the compiler cache.
max-compiler-cached-docs
Default Value: 1000
Valid Values: Any non-negative integer
Changes Take Effect: After restart
The maximum number of items that the compiler cache can have.
max-compiler-cached-doc-size
Default Value: 10000000
Valid Values: Any non-negative integer
Changes Take Effect: After restart
The maximum size (in bytes) allowed to cache the results of the compiled document.
(ER# 283652830)
This release does not contain any corrections and modifications.
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in this release of Orchestration Server (ORS).
cassandra-nodes option is mandatory for
Orchestration server 8.1.1. Please verify that it is properly configured
on any ORS node. (ER# 282278438)This release includes the following correction and modification:
The current orchestration-schema-sample.txt will not
work for Cassandra version 0.8.x. This has been updated with the
correction to support Cassandra 0.8.x, within a commented section. For
use with Cassandra 0.8.x the current section for 0.7.x should be
commented out, and the section for use with Cassandra 0.8.x should be
uncommented. (ER# 282278440)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following correction and modification:
Interactions created through <ixn:createmessage> are now properly handled by a new Orchestration session. (ER# 282034561)
Queue functions that return a string no longer enclose the result in double quotes. (ER# 282563163)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in this release of Orchestration Server (ORS).
<privateservice> action. This feature
enables SIP Server to act as a Charge Determination Point (CDP) to
specify the charges/billing rates that are applied when a service is
used.session:fetch action.This release includes the following corrections and modifications:
ORS no longer sends more multimedia interactions to some agents than the capacity rules specify when it is under large workloads. (ER# 272494071)
Issues with ECMAScript scoping have been resolved. Previously, when using <xi:include> to include nested states, the use of local ECMAScript scopes may have resulted in unexpected behavior. (ER# 280324561)
Use Composer version 8.1.010.13 (or newer) with this version of Orchestration Server. (ER# 298754308)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following correction and modification:
Orchestration Server (ORS) now supports predictive call types (ixn:createcall type=predictive). (ER# 272909793)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in the initial 8.1 release of Orchestration Server (ORS).
xdata attribute, which presents the extensions parameter for a given T-Event.
routing-timeout option, information about which can be found in the Interaction Server documentation. mcr-pull-limit, which is configurable in the orchestration section of the ORS Application
object. This option allows you to limit the number of interactions ORS
attempts to pull from Interaction Server at any given time, potentially
saving Interaction Server processing during heavy work periods.
mcr-pull-limitThe second new ORS option is
Default Value:5000
Valid Values: Any integer from0to50000
Changes Take Effect: Immediately (Note: although the value does not require a restart to take effect, if you decrease the number, a delay might occur before the new pulled interaction number is reached.)
Specifies the maximum number of pulled interactions that every node in a cluster, or ORS working in standalone mode, is allowed to have at any given time. Setting the value of this option to0disables all pulling of multimedia interactions for this instance of ORS.
mcr-relative-pull-rate, which is configurable in the Orchestration section of the Interaction Queue View object (of Script
type). This option defines the relative rate at which ORS pulls
interactions from a queue through a view where the option is specified.
Its value should be related to the characteristics of the view.
mcr-relative-pull-rate
Default Value:1
Valid Values: Any integer from0to100
Changes Take Effect: Immediately
Defines the relative rate at which interactions will be pulled from a queue through the view where the option is specified. Setting the value of this option to0disables pulling of multimedia interactions through the view where it is specified.
This release does not contain any corrections and modifications.
This section provides the latest information on known issues and recommendations associated with this product.
In versions 8.1.400.83 to 8.1.400.87, the ixn:createcall and ixn:consultation actions fail if the value of the to attribute is an object and the switch property is referencing the same switch that the device referenced in the from attribute belongs to (either explicitly or implicitly). (ORS-4092)
| Found In: 8.1.400.87 | Fixed In: 8.1.400.88 |
Starting from version 8.1.400.57, ORS prints the following log message: Option <some option name> dynamic change ignored, because the option is static. This message can occur after the value of any option in section orchestration (as well as other sections) is changed while ORS is running. Ignore the message because it is false. In reality, ORS has properly processed the option value update. (ORS-3237)
| Found In: 8.1.400.57 | Fixed In:8.1.400.60 |
Orchestration Server 8.1.3 requires Universal Routing Server 8.1.3.
Orchestration Server 8.1.4 requires Universal Routing Server 8.1.4.
| Found In: | Fixed In: |
Orchestration Server 8.1.400.09 does not contain improvements in the SCXML documents processing area that minimizes the session creation time. (ORS-1969)
| Found In: 8.1.400.09 | Fixed In: 8.1.400.11 |
Beginning with versions 8.1.3, Orchestration Server can load the Cassandra schema on start up, upon connection to any Cassandra instance listed in the cassandra-nodes configuration option. During the schema load, if another Orchestration Server instance is started, it is possible for the schema loading to fail, based upon whether or not the previous schema loading process has completed, including migration of the schema to the remaining Cassandra instances in the cluster. This is a known limitation, and can be prevented by starting only a single instance of Orchestration Server, and allowing the schema loading process to complete prior to starting any other Orchestration Server instances. (ORS-1202)
| Found In: 8.1.3 | Fixed In: |
Orchestration Server does not override the default value of the get-list-item-by-urs option if the functions-by-urs option is set to false when the getListItemValue function is used to retrieve the List item value directly from Configuration Layer. Genesys recommends that you set both the functions-by-urs and get-list-item-by-urs options to false. (ORS-1560)
| Found In: 8.1.300.36 | Fixed In: 8.1.300.39 |
Orchestration Server 8.1.300.25 is not available on the Red Hat Linux 5 32-bit platform. (ORS-1481)
| Found In: 8.1.300.25 | Fixed In: 8.1.300.32 |
If an Orchestration Server configured as Primary stops while handling a session started via HTTP interface,
subsequent HTTP requests about this session to another ORS node in the cluster are not correctly processed, as the
other node forwards the requests only to the Orchestration Server that is configured as Primary. This issue is resolved with the external-url option described in the New in this Release section of 8.1.300.25. (ORS-1339)
| Found In: 8.1.300.25 | Fixed In: 8.1.300.25 |
When debugging SCXML applications, Orchestration Server might sometimes terminate a session when infinite loop prevention is enabled. Genesys recommends disabling loop prevention by setting the scxml section option process-event-timeout to 0 (zero). (ORS-1407)
| Found In: 8.1.300.25 | Fixed In: 8.1.300.29 |
Any changes of ORS-specific User Data (outside of ORS scope) are prohibited, because they will lead to unpredictable ORS behavior. An interaction/call-processing application can modify only User Data that is in the scope of the application and nothing else. (ORS-1122)
| Found In: | Fixed In: |
Operational Reporting is not supported in Orchestration Server 8.1.3 and 8.1.4.
| Found In: | Fixed In: |
Backup Orchestration Server application fails to connect to Cassandra when both Primary and Backup ORS instances start simultaneously when loading a schema. Genesys recommends that you start one ORS application at a time when loading a schema. (ORS-1322)
| Found In: 8.1.300.25 | Fixed In: |
In Orchestration Server 8.1.3, specifying empty or invalid values for
max-state-entry-count, max-microstep-count,
or process-event-timeout options disables the Infinite Loop Prevention feature. (ORS-1314)
| Found In: 8.1.300.25 | Fixed In: 8.1.300.39 |
Orchestration Server does not populate the AttributeLocation in RequestInitiateTransfer when the action element is used to initiate a consultation call to a multi-site destination. (ORS-1254)
| Found In: 8.1.300.25 | Fixed In: 8.1.400.09 |
Orchestration Server 8.1.3 does not properly populate the AttributeExtensions of a TMakeCall request with the hints attribute specified in the
<ixn:createcall> action element.
(ORS-1312)
| Found In: 8.1.300.25 | Fixed In: 8.1.300.29 |
For multimedia interactions the data automatically provided by Universal Routing Server for reporting solutions is not available. This includes data which is attached to interactions and partial data that is provided in VQ events. The list of affected keys applicable to multimedia interactions includes:
RVQID, RVQDBID, RTargetRule, RTargetAgentGroup,
RTargetPlaceGroup, RPVQID, Reason, RTargetRuleSelected, RTargetTypeSelected, RTargetObjectSelected, RTargetAgentSelected,
RTargetPlaceSelected, RTenant, RRequestedSkillCombination. (ORS-1038)
| Found In: 8.1.300.25 | Fixed In: 8.1.400.09 |
The client-side port definition feature between Orchestration Server and Configuration Server/Configuration Server Proxy does not work when connection is established from an IPv6 address. (ORS-1335)
| Found In: 8.1.300.25 | Fixed In: |
Orchestration Server may experience memory growth due to the delay of the internal memory structures cleanup related to the ended scheduled sessions. The memory will eventually be cleaned when a new schedule request arrives. (ER# 323299121)
| Found In: 8.1.200.63 | Fixed In: 8.1.200.64 |
Orchestration Server could become unresponsive or exit if infinite loops exist in your application. SCXML application should be thoroughly revised to prevent and handle any possibility of infinite loops. (ORS-1275)
| Found In: 8.1.200.59 | Fixed In: 8.1.300.25 |
The use of <session:fetch> assumes that responses are encoded in UTF-8.
This can impact Composer generated strategies that access a database
using these functions where the values stored in the database are not UTF-8 encoded. (ER# 312013017)
| Found In: 8.1.200.44 | Fixed In: 8.1.200.61 |
If the connections to both primary and backup Universal Routing Servers are lost for any reason, Orchestration Server is unable to subscribe to Stat Server statistics, and any existing subscriptions are lost. (ORS 948)
| Found In: 8.1.200.43 | Fixed In: |
ORS may become unstable while debugging SCXML strategies. Genesys recommends using ORS for debugging SCXML strategies only in a non-production environment. (ER# 305884971)
| Found In: 8.1.200.40 | Fixed In: 8.1.200.41 |
ORS may become unstable if a server connection is removed from the ORS Connection
tab while ORS is active. As a workaround, when a connection
configuration needs to be modified, stop the Orchestration server,
change the configuration, and restart the Orchestration server.
(ER# 304342767)
| Found In: 8.1.200.39 | Fixed In: 8.1.200.40 |
The current orchestration-schema-sample.txt will not work for Cassandra version 0.8.x. To allow operation with Cassandra 0.8.x, the following line:
with replication_factor = 1
should be replaced with:
with strategy_options=[{replication_factor:1}]
(ER# 282278440)
| Found In: 8.1.000.19 | Fixed In: 8.1.100.20 |
In situations where ORS is working with large workloads, some agents might receive more multimedia interactions than the capacity rules specify. (ER# 272494071)
| Found In: 8.1.000.19 | Fixed In: 8.1.100.18 |
A session triggered by session:start might not
have the same Tenant ID as its parent,
although it should have. Instead, it might indicate the
Environment ID (101). (ER# 269008161)
| Found In: 8.1.000.19 | Fixed In: 8.1.200.16 |
This section documents features that are no longer supported in this software. This cumulative list is in release-number order with the most recently discontinued features at the top of the list. For more information on discontinued support for operating environments and databases, see "Discontinued Support" in the Genesys Supported Operating Environment Reference Guide.
The Red Hat Enterprise Linux (RHEL) v6 operating system is no longer supported.
| Discontinued As Of: February 24, 2021; All releases |
Orchestration Server support for Windows Server 2008 is discontinued.
| Discontinued As Of: July 15, 2020; All releases |
Orchestration Server support for Red Hat Enterprise Linux 5 is discontinued.
| Discontinued As Of: March 15, 2019; All releases |
32-bit versions of ORS are no longer provided.
| Discontinued As Of: 8.1.400.75 |
Orchestration Server support for Microsoft Windows 2003 is discontinued.
| Discontinued As Of: 8.1.400.27 |
Orchestration Server support for Red Hat Enterprise Linux 4 is discontinued.
| Discontinued As Of: 8.1.300.25 |
Orchestration Server does not support the Solaris OS.
| Discontinued As Of: 8.1.000.19 |
Information in this section is included for international customers.
There are no known issues for internationalization in this 8.1 release of Orchestration Server.
Additional information on Genesys is available on our Customer Care website. The following documentation also contains information about this software. Please consult the Deployment Guide first.
Orchestration Developer's Guide, which includes an SCXML Language Reference and information on ORS Extensions.
Cassandra 2.2.5 / 3.9 Installation/Configuration Guide, which provides information relevant to the deployment of the Cassandra database.
Product documentation is provided on the Customer Care website, the Genesys Documentation website, and the Documentation Library DVD.
Note: For the DVD, the New Documents on this DVD page indicates the production date for that disc. Due to disc production schedules, documentation on the Genesys Documentation website may be more up-to-date than what is available on disc immediately after a product is released or updated. To determine the version of a document, check the version number that is located on the second page in PDFs or on the About This File topic in Help files.