Release Advisory

Genesys Voice Platform


Genesys Telecommunications Laboratories, Inc. © 2009–2013

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 for more details.

Link to 8.0 Product Release Advisory

The following information applies to Genesys 8.1.x software and is important for you to note:

Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. For specific information about any third-party software used in this product, see the Read Me. Contact your Customer Care representative if you have any questions.

GVP 8.1.7 supports Red Hat Linux 6, but some GVP components run at lower capacities when compared to RHEL 5.x.
At release time, the best performance is achieved using RHEL 5. (GVP-19454 / 321172627)

In GVP 8.1.5, the MCP and CCP added a feature to allow a GVP system maintainer to clear the internal in-memory cache within those processes without restarting. This is done by using Genesys Management Framework to send a custom message to the MCP or CCP. To use this command, do the following:

  1. Depending on your operating system, copy the command mlcmd.exe (Windows), or mlcmd_64 (64-bit Linux), or mlcmd_32 (32-bit Linux) from the Genesys Management Framework > Solution Control Server bin directory to your MCP or CCP bin directory.
  2. Edit the (Linux) or the clearfmcache.bat (Windows) shell scripts in the MCP or CCP bin directory as follows:
    1. In the CSUSER, CSPASSWORD, and CSAPPNAME variables, enter the Management Framework credentials you use to log into Genesys Administrator.
    2. In the SCSHOST variable, enter the address of the machine that is hosting the SCS.
    3. Modify the SCSPORT variable if your Solution Control Server is deployed on a non-default port.
  3. Run the script by either ./ (Linux) or clearfmcache.bat (Windows) at the command prompt.

Note: This procedure is applicable if you are using Genesys Management Framework 8.1.1 or higher. If you are using an older version of Management Framework, contact Genesys technical support for help.

When GVP sends attached data to SIP Server, if one of the variables contains an empty value, it may be ignored by SIP Server. The workaround is to send a dummy variable named zzzzz. (ER# 296104557)

GVP supports the following upgrades and new features in the 8.1.4 release:

Three new components are introduced in the 8.1.4 release of GVP:

If you plan to upgrade or deploy the PSTN Connector with GVP CTI Framework during migration, there are special considerations for provisioning IVR port numbers, depending on the version to which you are migrating. For more information about this issue, see "Deploying the PSTN Connector with CTI Framework" in the GVP chapters of the Genesys Migration Guide.

The Resource Group Wizard in Genesys Administrator has a limitation which prevents you from adding more than two levels of child tenants (child and grandchild) below the parent tenant. You can work around this issue by completing the following steps:

  1. In the Tenant: field at the top of the Genesys Adminstrator GUI, browse to select the tenant to which you want to add the child and grandchild tenants by clicking the browse button.

  2. In the Provisioning > Voice Platform > Resource Groups pane, click New to launch the Resource Group Wizard.

  3. Complete the steps in the wizard, as required.

For more information about how to use the Resouce Group Wizard, see Framework 8.1 Genesys Administrator Help.

Note: The workaround procedure that was documented in the previous release of this Release Advisory, is no longer needed, as the issue has been corrected..

(ER# 258940284)

When installing or upgrading Reporting Server, you must modify the Oracle scripts prior to execution, otherwise some scripts will produce errors. To resolve this issue, remove any unmatched trailing parentheses in the following scripts:

For example, change SELECT custom_vars_seq.nextval, CSID, SESSION_ID, SEQUENCE_ID, COMP_ID, START_TIME, APP_ID, NAME, VALUE)

This issue was corrected in the 8.1.4 release of Reporting Server. (ER# 262024867).

GVP 8.1.31 Media Control Platform's Next Generation Interpreter (NGI) now supports DTMF-only barge-in capability. This functionality is enabled by configuring the bargein="dtmf" parameter for on-board DTMF recognition.

GVP 8.1.31 High Availability (HA) Resource Manager is improved by the inclusion of enhanced NLB.bat scripts for Windows Network Load Balancing (NLB).

GVP 8.1.31 Resource Manager Installation Package (IP) includes a gvp section in the installation template with default option values that are compatible with Windows and Linux operating systems.

GVP 8.1.31 Resource Manager performance is enhanced by a larger User Datagram Protocol (UDP) socket buffer that is now configurable.

The following items further clarify the scope of support for the GVP 8.1.3 Reporting Server Database:

GVP 8.1.3 now packages the Media Control Platform (MCP) and Resource Manager (RM) on the Genesys Media Server 8.1.3 CD.

GVP 8.1.3 has a new prerequisite for Windows 2003 SP2. In addition to Microsoft Visual C++ 2005, SP1 Redistributable Package (x86), you will also need Visual Studio 2005 Service Pack 1 ATL Security Update (KB971090).

HTTP Digest Authentication is supported for the Conversation Manager Solution.

Live upgrades, in-service migration, and mixed modes are supported across GVP 8.x versions.

For customers upgrading from GVP 8.1.2, the SIP messages between GVP components might switch to use Transmission Control Protocol (TCP) from UDP due to additional internal data transmitted between the components. If it is confirmed that the upgrade has led to a switch of using TCP and causes unexpected behavior in the application, you might need to change the [sip]mtusize parameter of the components to 1550. (ER# 258198448)

If a child tenant is assigned a Logical Resource Group (LRG) by its parent tenant, and then is moved within the hierarchy, the LRG remains assigned until the assignment is manually removed. (ER#  247518907)

In multi-tenant deployments, child tenant users must be given logon access to Genesys Administrator before they can view and download their reporting data. You can grant access to child tenants by completing the following tasks, the procedures for which can be found in Framework 8.0 Genesys Administrator Help:

  1. Create a new tenant by using the Manually Creating New Tenants procedure.
    You can view the newly created tenant, in the provisioning > Environment > Tenants panel. If you do not see the new tenant immediately, log out and log back in again.
  2. Create a new user by using the Creating Users procedure.
  3. Add the new user to a group by using the Add Users by Using the Task Panel procedure.
  4. Create a new role, add the new user to the role, and assign permissions by using the information in the Users: Overview section.
  5. Select Environment > Applications, double-click the default application, and grant Read and Write permissions to the user.
  6. Logout of Genesys Administrator and log in again as the new user.

For optimal performance, Genesys recommends a maximum number of 750 tenants per multi-tenant deployment.

The GVP User Interface (GVPUI) in Genesys Administrator provides scaling options for multi-site reporting by aggregating reports from multiple independent Reporting Servers, allowing administrators to view an aggregation of data across multiple sites.

In some instances, the Media Server might not be able to play prompts on Linux. To work around this issue, add the machine’s IP address to the /etc/hosts file, and then restart the Media Control Platform. For example:

(ER# 218690361)

Genesys recommends using static IP addresses for all GVP machines. This applies to both Windows and Linux.

This product includes software that was developed by the University of California, Berkeley and its contributors.

This product includes software that was developed by the NetBSD Foundation, Inc. and its contributors.

Top of Page