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 Voice Platform (GVP) Reporting Server.
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. Contact your Customer Care representative if you have any questions.
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:
When configured to work with redundant (HA) Configuration Servers (primary and backup), Reporting Server now reconnects immediately to the primary Configuration Server after two or more switchovers occur. Previously in this scenario, Reporting Server would sometimes lose its connection to Configuration Server and would try continuously to connect to the backup Configuration Server (instead of the primary one). (GVP-15678)
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 Voice Platform Reporting Server (RS).
This release includes the following correction\ and modification:
This release corrects a syntax error in some rarely used code within the Oracle partitioning script (for Reporting Server in partitioned mode). (GVP-20274 / ER# 324169810)
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 Voice Platform Reporting Server (RS).
No corrections or modifications have been made in this release.
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:
This release updates the Reporting Server IP with the following v8.1.4 to v8.1.5 Upgrade Scripts:
mssql-schema-upgrade-814-815-std.sql
mssql-schema-upgrade-814-815-partitioned.sql
oracle-schema-upgrade-814-815-std.sql
oracle-schema-upgrade-814-815-partitioned.sql
All updated files are located in this directory:
..\RS Installed folder\scripts\upgrade\
(ER# 300763980)
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 Voice Platform Reporting Server (RS).
This release includes the following corrections and modifications:
When a pair of Reporting Servers are configured as Segregated Primary/Backup
High Availability pairs, when calls are switched over from one RS to another,
the message session removed due to timeout
is no longer written
to the logs. Previously, this message was written repeatedly to the logs during
the switch-over. (ER# 279100381)
The Reporting Server no longer logs an error when the [sqa] error.notification.threshold
configuration is not configured, or has been configured with an empty value.
(ER# 279074352)
The Reporting Server no longer writes the message com.gvp.rpt.var.service.CallTimeoutMonitorService
Error when processing timeout notification for: VARStatsGenerator java.lang.NullPointerException
repeatedly to its logs. (ER# 279074331)
The Deployment Guide has not yet been updated with the following information about creating a user to create the database tables:
The database administrator should grant the following system privileges to the user who owns the Reporting Server (RS) schema:
CREATE TRIGGER
CREATE SEQUENCE
CREATE TABLE
CREATE PROCEDURE
FORCE TRANSACTION
CREATE VIEW
CREATE SESSION
The RS database user should be used to work only on the RS database. The privileges granted to RS user only apply to RS’s own schema. The optional privileges are not required for installation and operation, but they may be required for special tasks such as troubleshooting, backup and restore. (ER# 284052789)
Deploying any GVP Windows IP through Genesys Administrator no longer results in an error. Previously, an error message might have occasionally occurred even when the deployment was completed successfullly. (ER# 258776961)
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 Voice Platform Reporting Server (RS).
No corrections or modifications have been made in this release.
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 Voice Platform Reporting Server.
This release includes the following correction and modification:
The Reporting Server no longer generates errors when the Oracle 8.1.2 database schema is upgraded to 8.1.3. This issue is resolved in this release. (ER# 262144271)
Genesys Administrator now successfully connects to the Reporting Server after High Availability (HA) switchover. Previously, Genesys Administrator failed to connect to the Primary Reporting Server after switchover if the Backup server was still in operation. (ER# 262929074)
The Reporting Server can now support an IP address configured as a blank value on its Host object, with TLS connections to GVP resources. See also, the New in This Release section of this release. (ER# 259455161)
The Media Control Platform, Call Control Platform, or Resource Manager no longer terminate unexpectedly if the Reporting Server runs out of available memory or if the server disk space is full. (ER# 237608549)
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:
The operational status of the Reporting Server (RS) is now displayed consistently in Genesys Administrator, Solution Control Interface (SCI), and the RS logs after restarting. Previously, when the Reporting Server failed to initialize properly, the status sometimes still displayed as Started
in Genesys Administrator and the SCI, preventing a system administrator from properly managing the Reporting Server to enable other GVP components to connect to and send data to it. (ER# 272875725)
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 Voice Platform Reporting Server.
This release includes the following corrections and modifications:
Internal errors are no longer generated when local or remote URIs are used to filter data in the historical browser in Genesys Administrator. (ER# 228951482)
The Genesys Voice Platform 8.1 Deployment Guide now contains the following information:
When you are setting up Oracle 10g/11g as the Reporting Server database, Genesys recommends that the Reporting Server database username be unique and different from the Management Framework Configuration database username.
(ER# 247801781)
Reporting Server log settings are no longer ignored if the same log output file is specified for multiple log levels. Previoulsy in this scenario, a single log was generated but not rotated, even if segmentation and expiration was enabled. (ER# 245139921)
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:
This release of the Reporting Server is compatible with GVP 8.1.1 and later Reporting Clients (Resource Manager, Media Control Platform, and Call Control Platform). (ER# 257511179)
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 Voice Platform Reporting Server (RS).
This release includes the following corrections and modifications:
The peak time on the Genesys Administrator Dashboard is no longer off by up to five minutes from the real peak time. The dashboard now provides accurate peak times. (ER# 229342910)
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 Voice Platform Reporting Server (RS).
This release includes the following corrections and modifications:
The CDR VAR data now includes the Media Control Platform (MCP) ID when calls are shorter than the configured batch timeout for CDRs (10 seconds by default). (ER# 217050041)
On Windows operating systems, the Deployment Wizard for the Reporting Server now prompts for the Database Name. Previously, the Wizard prompted for the DBMS Server name, which was erroneously labeled. (ER# 217584021)
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 Voice Platform Reporting Server.
This release includes the following corrections and modifications:
The Reporting Server Client no longer takes a long time to initialize if there is a large amount of data in the local database queue for the Resource Manager, the Media Control Platform, or the Call Control Platform. Previously, the component took up to several minutes to start depending on the amount of data that had been queued locally. (ER# 189683144)
Reporting Server now uses KBs as the default unit in the [log]
configuration section if no units are specified. Previously, Reporting Server used Bytes as the default unit. (ER# 192801271)
Changing the segment
or the expire
option in the
Reporting Server's [log]
section while the Reporting Server is
running no longer deletes the current log file. (ER# 192801273)
This section provides special instructions associated with deploying this product.
- mssql-schema-upgrade-814-815-std.sql
- mssql-schema-upgrade-814-815-partitioned.sql
- oracle-schema-upgrade-814-815-std.sql
oracle-schema-upgrade-814-815-partitioned.sql
- CREATE TRIGGER
- CREATE SEQUENCE
- CREATE TABLE
- CREATE PROCEDURE
- FORCE TRANSACTION
- CREATE VIEW
CREATE SESSION
Important: The RS database user should be used to work only on the RS database. The privileges granted to RS user only apply to RS�s own schema. The optional privileges are not required for installation and operation, but they may be required for special tasks such as troubleshooting, backup and restore.
This section provides the latest information on known issues and recommendations associated with this product.
A minor change is required when Reporting Server is deployed with an Oracle RAC database. When the hibernate.remote.database
configuration option is configured, the Reporting Server internally appends some parameters to the value of the hibernate.remote.url
option, including the value of the hibernate.remote.database
option. Therefore, to ensure the hibernate.remote.url
option is properly configured for use with Oracle RAC, ensure the following appropriate action is taken, based on the Reporting Server release you are using:
hibernate.remote.database
option with the value blank
.hibernate.remote.database
configuration option.Found In: 8.1.301.26 | Fixed In: |
Deploying any GVP Windows IP through Genesys Administrator may occasionally result in the following error, although the actual deployments are completed successfully:
Execution of installation failed. Retcode = 1
(ER# 258776961)
Found In: 8.1.301.26 | Fixed In: 8.1.502.62 |
Certain Reporting Server retention policies are required to be above a minimum value; however, the Data Retention Policy Wizard does not currently support the enforcement of these restrictions. Consequently, if a retention policy value is set below the minimum, the Reporting Server ignores this value and uses the minimum value instead. All of the daily, weekly, and monthly retention policies have a minimum retention requirement of 31 days, and all retention policies must have a duration of at least 1 day.(ER# 246766671)
Found In: 8.1.202.28 | Fixed In: |
When you are setting up Oracle 10g/11g as the Reporting Server database, Genesys recommends that the Reporting Server database username be unique and different from the Management Framework Configuration database username. (ER# 247801781)
Found In: 8.1.202.28 | Fixed In: 8.1.3 release of the Genesys Voice Platform Deployment Guide |
If the Reporting Server runs out of available memory or if the server disk space is full, it could cause the Media Control Platform, Call Control Platform, or Resource Manager to terminate unexpectedly. (ER# 237608549)
Found In: 8.1.202.28 | Fixed In: 8.1.401.64 |
The peak time on the Genesys Administrator Dashboard might be off by up to five minutes from the real peak time. (ER# 229342910)
Found In: 8.1.101.40 | Fixed In: 8.1.202.28 |
Using local or remote URIs to filter data in the historical browser in Genesys Administrator, can generate internal errors. Genesys recommends using the IVR Profile (or some other filter) together with local or remote URI queries to obtain the desired results. (ER# 228951482)
Found In: 8.1.101.12 | Fixed In: 8.1.301.26 |
Log settings in the Reporting Server are ignored if the same log output file is specified for multiple log levels. In this scenario, a single log is generated and not rotated, even if segmentation and expiration is enabled. (ER# 245139921)
Found In: 8.1.001.49 | Fixed In: 8.1.300.47 |
The CDR VAR data is missing the Media Control Platform (MCP) ID when calls are shorter than the configured batch timeout for CDRs (10 seconds by default).
Note: The batch timeout parameter for CDRs is [ems]rc.cdr.max_batch_time.
(ER# 217050041)
Found In: 8.1.001.49 | Fixed In: 8.1.101.40 |
The Deployment Wizard for the Reporting Server, on Windows, asks for two very similar entries during the deployment process: the DBMS Host name and DBMS Server name. The second one is erroneously labeled. When asked for the DBMS Host name, enter the name of the machine where the DBMS resides. When asked for the DBMS Server name, enter the name of the database to be used for the Reporting Server. (ER# 217584021)
Found In: 8.1.001.49 | Fixed In: 8.1.101.40 |
After migrating, the IVR Action report does not provide the IVR Action result reason. For data compatibility reasons, the GVP 8.1 IVR Action Usage summary report does not display a breakdown of IVR results by reason for data that was generated by the GVP 8.0 deployment. However, the report does display the result reason breakdown for new data that is generated by GVP 8.1 IVR actions. (ER# 216545723)
Found In: 8.1.001.11 | Fixed In: 8.1.001.29 |
When querying for call log events through the Reporting Server web services,
if you specify the from
parameter, you must also specify the to
parameter. (ER# 191736736)
Found In: 8.0.004.46 | Fixed In: |
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 release.
Information in this section is included for international customers.
There are no known 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 Genesys Voice Platform 8.1 Deployment Guide first.
Framework 8.1 Deployment Guide, which provides information about configuring, installing, starting, and stopping Framework components.
Framework 8.1 Genesys Administrator Help, which provides information about configuring and provisioning contact-center objects by using the Genesys Administrator.
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.