Jump to: navigation, search

New in This Release

This section contains a brief description of the new features in Genesys Orchestration Server (ORS) 8.1.3 release. For information on the new features in the Genesys Orchestration Server 8.1.2 release , see the Orchestration Server 8.1.2 Deployment Guide.

Release 8.1.300.25

  • ORS provides an enhanced high-availability (HA) environment architecture. The enhancement to a high-availability (HA) architecture implies the existence of redundant ORS Applications: a primary and a backup (i.e., nodes). If the primary application fails, the backup can take over its operations without significant loss of data or impact to business operations.
  • Multiple Data Center architecture. ORS now supports a Data Center architecture where each Data Center is served by a cluster of ORS nodes. ORS supports Data Center failover.
  • A single Cassandra instance across multiple Data Centers. The Apache Cassandra open source solution packaged with Genesys Orchestration Solution now supports a single Cassandra instance across multiple Data Centers.
  • Support of new version of Cassandra. ORS 8.1.3 supports Apache Cassandra 1.1.x, beginning with Version 1.1.12.
  • 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, etc.) of an attempt to reach an intended party. This allows ORS to determine the next actions for this interaction, such as redialing at the later time for negative call results or connecting an established outbound call to pre-recorded message instead of an agent for ‘answering machine’ call result. Refer to the Orchestration Server Developer's Guide for more information.
  • Infinite loop prevention. A change has been implemented in ORS behavior called infinite loop prevention. This modification prevents ORS from infinite loops between states or from an endless number of times a state is entered as a direct result of a transition element.
  • Enhanced Multi-Site support. Simplification of processing multi-site interactions by separating interactions objects from different sites between different SCXML strategies.

Subsequent Releases

  • Starting with Release 8.1.300.47, ORS now populates the values of 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.
  • Starting with Release 8.1.300.45, ORS 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.
  • Starting with Release 8.1.300.36, Orchestration Server now allows you to retrieve information directly from the Configuration Layer without sending requests to Universal Routing Server when using the following _genesys.session functions: isSpecialDay, timeInZone, dateInZone, dayInZone, listLookupValue, and getListItemValue. To enable this functionality, use the new option functions-by-urs.
  • The following attributes have been added: Starting with Release 8.1.300.41, to ensure proper session persistence during High Availability recovery, a new attribute, _statePersistDefault is added to the top-level <scxml> element. Starting with Release 8.1.300.32, a new _transitionStyle attribute is added to the <scxml> element, which allows defining the order in which the <transition> content will be executed. For details on these attributes, see the SCXML Langage Reference in the Orchestration Server Developer's Guide.
  • Starting with Release 8.1.300.39, ORS reports Standard log level messages upon connecting to or disconnecting from Universal Routing Server:
  • Starting with Release 8.1.300.35, ORS supports SSL for HTTP requests. To use this feature, SSL/TLS must be enabled on the 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 8.1 Security Deployment Guide. See the Orchestration Server 8.1.x Release Note for the recommended log configuation.
  • Starting with Release 8.1.300.32, adjustments were made 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.
  • Starting with Release 8.1.300.29, ORS reports the elapsed time between the time a request to fetch a document is issued and the time the requested document is retrieved. This information is provided in the duration attribute in the <doc_retrieved> METRIC.
  • Starting with Release 8.1.300.27, ORS successfully distributes 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.
  • Starting with Release 8.1.300.27, ORS allows substitution of parameters, provided in the URL of an SCXML application, with predefined values. See the Orchestration Server 8.1.x Release Note for details.
This page was last modified on October 3, 2014, at 15:32.

Feedback

Comment on this article:

blog comments powered by Disqus