Release Number | AIX | HP-UX PA | HP-UX IPF | Linux | Solaris | Windows |
---|---|---|---|---|---|---|
8.1.200.25 [10/18/13] – General (Under Shipping Control) | X | X | ||||
8.1.100.30 [06/06/13] – Hot Fix | X | X | ||||
8.1.100.28 [04/26/13] – General (Under Shipping Control) | X | X | ||||
8.1.100.23 [02/25/13] – Hot Fix | X | X | ||||
8.1.100.20 [01/14/13] – Hot Fix | X | X | ||||
8.1.100.18 [11/30/12] – Hot Fix | X | X | ||||
8.1.100.14 [10/23/12] – General (Under Shipping Control) | X | X | ||||
8.1.000.30 [06/08/12] – General (Under Shipping Control) | X | X | ||||
8.1.000.23 [04/18/12] – General (Under Shipping Control) | X | X |
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.genesyslab.com for more details.
This release note applies to all 8.1 releases of Genesys Mobile Services (GMS).
Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. For additional information about third-party software used in this product, see the Read Me. Please contact your Genesys Customer Care representative if you have any questions.
Supported Operating Systems
New in This Release
Corrections and Modifications
This release is under shipping control. This section describes new features that were introduced in this release of Genesys Mobile Services.
web_port
option Alarm (EventId 2002).There are no corrections or modifications for this release.
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.
This release also includes the following corrections or modifications:
You can now perform a graceful shutdown on the GMS node using the Solution Control Interface. All of the in-progress requests will be completed successfully, and no errors will be generated. (GMS-609)
The default value (-1) for the _booking_expiration_timeout
option
no longer causes an error to be logged. (GMS-640)
Supported Operating Systems
New in This Release
Corrections and Modifications
This release is under shipping control. This section describes new features that were introduced in this release of Genesys Mobile Services.
request-chat
and request-chat-poll
service to /ixn/chat
request.
Section: service.request-chat-poll
Option Name: default_poke_message
Option Type: string
Restriction on Value: Optional
Valid Values: <your poke message>
Option Name: internal_api_url_base
Option Type: string
Restriction on Value: Optional
Valid Values: http://<gmshost>:<gmsport>
The service should be created by passing in _device_os
and _device_notification_id
parameters to enable push notifications.
This release also includes the following corrections or modifications:
Transcript events for client chat messages are now always received by the client application. Previously, the events were not received on a regular basis. (ER# 321074571)
GMS now responds with the appropriate parameters to a client request for creating
a chat interaction. Previously, the verbose
value was disregarded,
and the channel name was incorrect. (ER# 321074583)
The Start Chat API now supports anonymous chat sessions and allows the use
of nicknames. The firstName, lastName
and emailAddress
parameters are now optional, and a new parameter, userDisplayName,
is added so the client can specify the nickname to be displayed in the chat
conversation. Previously, GMS generated the nickname with a combination of characters
from firstName
and lastName.
(ER# 321269117)
You can now configure an endpoint for a GMS chat service. A new service configuration
parameter, chat_endpoint,
is added to request-chat
and request-chat-poll.
This configuration enables the chat interaction
that is created by services to be queued in different interaction queues. Previously,
all chat interactions were processed by only one queue, and therefore both the
request-chat
and request-chat-poll
scenarios could
not be configured to execute simultaneously. (ER# 321338367)
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 Genesys Mobile Services.
request-access
URI parameter.
Section: service.servicename
Option Name: _booking_expiration_timeout
Option Type: Integer
Restriction on Value: Optional
Valid Values (in seconds): 10–1000
This option is specific to the service.request-interaction
and service.request-access
services, and applies only to local
and cluster allocation strategies:
Note that the value passed through the request-access
URI
parameter will override the value in the service section.
This release also includes the following correction or modification:
GMS now displays the correct version during initialization. (ER# 310721331)
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.
This release also includes the following correction or modification:
GMS no longer generates an HTTP 301 code when using load balancing. (ER# 314610290)
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.
This release also includes the following corrections or modifications:
The Genesys Mobile Services template now includes the following option to allow
a 200 OK
message for a match-interaction that is not found. Previously,
GMS only returned a 404 Not Found
message.
Service Type:
match-interaction
Option Name:http_status_on_error
Default Value:404
Valid Values: all HTTP status code values according to RFC 2616
(ER# 313518341)
If a Genesys Mobile Services cluster has more than three nodes, it no longer fails to process requests if one node is out of service. (ER# 313518373)
Supported Operating Systems
New in This Release
Corrections and Modifications
This release is under shipping control. This section describes new features that were introduced in this release of Genesys Mobile Services.
CometD - Genesys Mobile Services now provides HTTP-based events using CometD.
Chat Support - Genesys Mobile Services now includes a Chat API, which customer-facing applications can use to create and manage a chat session associated with contact center-related services when used with Genesys Chat Server.
Improved OS Support - Genesys Mobile Services now provides support for the following operating systems:
Google Cloud Messaging - The push notification service now supports Google Cloud Messaging (GCM).
Push Notification Localization - Push notification now supports localized messages. The language specified during subscription is used to retrieve content from a custom XML file that is specified by the localizationFileLocation
option.
Improved Genesys Mobile Services API Security - Includes the ability to hide sensitive data in logs, and take advantage of client-side port definition when connecting to Genesys Servers.
Counters and Monitoring Support - This release provides support for displaying counters and monitoring Genesys Mobile Services nodes.
This release also includes the following correction or modification:
Requests to the ORS-based service that do not include a custom parameter are now processed correctly. Previously, subsequent requests to that service would fail at Genesys Mobile Services with a resource not found
error instead of being forwarded to the ORS session. (ER# 301769273)
Supported Operating Systems
New in This Release
Corrections and Modifications
This release is under shipping control. This section describes new features that were introduced in this release of Genesys Mobile Services.
API Updates—API naming conventions have been adjusted to be more intuitive and consistent.
Mobile Client Samples—Code samples are now available from the Developer's Guide section of the Genesys Documentation Wiki.
This release also includes the following corrections and modifications:
During certificate validation, the HTTPS connection is now established correctly when the keystore password is null or an empty string and the keystore contains a key. Please note that security certificates are changed periodically; be sure to use the current certificate. (ER# 297717431)
Running Genesys Mobile Services in a Windows environment no longer causes an Out of Memory
error when the system load is high due to updates to the launcher.xml
file located in the installation directory for your instance of Genesys Mobile Services. (ER# 298676961)
Supported Operating Systems
New in This Release
Corrections and Modifications
This release is under shipping control. This section describes new features that were introduced in the initial 8.1 release of Genesys Mobile Services.
Connect using Mobile Apps—Genesys Mobile Services allows mobile customers to connect with your contact center, automatically associating mobile contextual data with the phone call in order to improve the customer experience. Call timing can optionally be postponed until an agent is available to attend the call.
Informed Access Number Selection—The phone number used to call your contact center can be chosen for each individual inbound call, based on mobile contextual data, such as customer location.
Customer Location—Part of the mobile contextual data is customer location. For instance, customer location can be displayed on a map for the agent attending the call.
Mobile Application Samples (Android and iOS)—This release includes predefined mobile device code samples for Android and iPhone leveraging HTML5/JavaScript as well as native OS-specific code.
There are no corrections or modifications for this release.
This section provides the latest information on known issues and recommendations associated with this product.
When GMS is running on JDK 7 64-bit, you must increase allocated stack space. To do this:
launcher.xml
file."-Xss".
200k
to 228k
(minimum).For example:
<parameter name="jvm_option21" displayName="jvm_option21"
mandatory="true" hidden="true" readOnly="true">
<description><![CDATA[Cassandra related]]></description>
<valid-description><![CDATA[]]></valid-description>
<effective-description/>
<format type="string" default="-Xss228k"
/>
<validation></validation>
</parameter>
(GMS-1120)
Found In: 8.1.200.25 | Fixed In: |
The Service API incorrectly allows the user to overwrite service configuration options by passing them as request parameters. (GMS-830)
Found In: 8.1.200.25 | Fixed In: |
When creating a business-hours service through the Service Management UI,
the written data for Open dates
is incorrect. To workaround this
issue, you can correct the date in Configuration Manager (_bh_regularX
options) after the service creation. For example:
_bh_regular2="Mon 08:00 - Tue
23:00"
should be replaced with:
_bh_regular2="Mon-Tue 08:00-23:00"
(GMS-1132)
Found In: 8.1.200.25 | Fixed In: |
ORS sometimes fails to start when the DFM configuration is loaded on a GMS node that is not running. To workaround this issue, use ORS version 8.1.300.10 or later. (GMS-1009)
Found In: 8.1.200.25 | Fixed In: |
Only current Daylight Savings Time (DST) is taken into account. The service
is not able to project DST in the future if scheduling after summer when winter
DST is still in affect, and vice-versa. To workaround this issue, set an additional
parameter _timezone_offset
which stands for seconds offset when
comparing timezone with UTC. This parameter may be +/-, so for example 7200
is 2h (GMT+2). (GMS-1039)
Found In: 8.1.200.25 | Fixed In: |
GMS responds with an a Internal Server Error
message instead of a BadRequest
message when negative notification requests are received. (GMS-1101)
Found In: 8.1.200.25 | Fixed In: |
Default values for RAM allocation may be insufficient in the launcher.xml
file, causing Genesys Mobile Services to stop running unexpectedly with a "Map failed" error. To prevent this, adjust the following options in your launcher.xml
file before starting the Genesys Mobile Services application:
Option Name | Minimum Recommended Value |
---|---|
Xms | 256m |
Xmx | 512m |
(ER# 310704162)
Found In: 8.1.100.14 | Fixed In: |
Genesys Mobile Services shows an incorrect version number during initialization. (ER# 310721331)
Found In: 8.1.100.14 | Fixed In: |
The configuration option naming convention is different than the interface
request parameters. To workaround this issue, in the configuration database,
rename all the options to begin with an underscore (_
) prefix.
For example, rename the configuration provide_code
option to _provide_code
,
so that it matches the _provide_code
UI request parameter. (GMS-1048)
Found In: 8.1.1 | Fixed In: 8.1.200.25 |
In some cases, attempting to start Genesys Mobile Services through SCI results
in an Unable to start the Application <GMS_Application_Name> with
configured timeout
error message due to Cassandra taking extra time to
start. In this scenario, either start the server manually or increase the time
that SCS allows for applications to start (default value is 90 seconds).
Found In: 8.1.000.30 | Fixed In: |
After an SCXML application error response from ORS, the related HTTP connection is not released correctly.
The recommended workaround for this situation is to reduce the timeout value and increase the number of connections allowed, so that the connection can safely timeout if an error response is returned. Accomplish this by editing the Genesys Mobile Services Application object configuration setting under the GMS
section of the Options
table, as shown below:
Name | Value |
---|---|
http.connection_timeout | 10 |
http.max_connections_per_route | 20 |
http.max_connections_total | 100 |
http.socket_timeout | 10 |
Found In: 8.1.000.30 | Fixed In: |
If a request to the ORS-based service does not include a custom parameter, then all subsequent requests to that service fail at Genesys Mobile Services with a resource not found
error instead of being forwarded to the ORS session. (ER# 301769273)
Found In: 8.1.000.30 | Fixed In: 8.1.100.14 |
If the keystore password is null or an empty string and the keystore contains a key, then Java might fail to establish the HTTPS connection.
To correct this, update the keystore password for the stored keys to be non-null and non-empty. Provide the correct password by using JVM options, or the settings of the web server being used. Alternatively, you can disable certificate validation by setting the push.android.ssl_trust_all
option to true
; however, this approach is not recommended.
(ER# 297717431)
Found In: 8.1.000.23 | Fixed In: 8.1.000.30 |
When running Genesys Mobile Services in a Windows environment, an Out of Memory
error may occur in some cases when the system load is high. To correct this issue, add the following code to the launcher.xml
file, which is located in the installation directory for your instance of Genesys Mobile Services.
<parameter name="jvm_option2" displayName="jvm_option2" mandatory="true" hidden="true" readOnly="true"> <description><![CDATA[Cassandra related]]></description> <valid-description><![CDATA[]]></valid-description> <effective-description/> <format type="string" default="-Xms2G" /> <validation></validation> </parameter> <parameter name="jvm_option3" displayName="jvm_option3" mandatory="true" hidden="true" readOnly="true"> <description><![CDATA[Cassandra related]]></description> <valid-description><![CDATA[]]></valid-description> <effective-description/> <format type="string" default="-Xmx2G" /> <validation></validation> </parameter>
In this code, the -Xmx2G
value indicates that 2 GB of memory is reserved for the JVM. This value may need to be adjusted depending on your environment. For example, -Xmx1500m
would specify 1.5 GB of memory.
(ER# 298676961)
Found In: 8.1.000.23 | Fixed In: 8.1.000.30 |
The Genesys Mobile Services Dashboard displays incorrectly when Internet Explorer
8 is used to view the administration console (http://
).
(ER# 310721338)
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.
There are no discontinued items for this product.
Information in this section is included for international customers.
There are no internationalization issues for this product.
Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Customer Care website. The following documentation also contains information about this software. Please consult the Deployment Guide first.
Product documentation is provided on the Customer Care website, the Genesys Documentation website, and the Documentation Library DVD (produced monthly) or the Developer Documentation CD.
Note: For the DVD/CD, the New Documents on this DVD/CD 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.