| Release Number | AIX | HP-UX PA | HP-UX IPF | Linux | Solaris | Windows |
|---|---|---|---|---|---|---|
| 8.1.200.34 [08/21/12] – General (Under Shipping Control) | X | |||||
| 8.1.100.32 [12/23/11] – General (Under Shipping Control) | X | |||||
| 8.1.000.55 [03/15/12] – Hot Fix | X | |||||
| 8.1.000.53 [02/09/12] – Hot Fix | X | |||||
| 8.1.000.52 [01/26/12] – Hot Fix | X | |||||
| 8.1.000.48 [09/29/11] – General (Under Shipping Control) | X | |||||
| 8.1.000.40 [06/30/11] – General (Under Shipping Control) | 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 Hosted Provider Edition 8.1.
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 Read Me. Please contact your technical support 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 Hosted Provider Edition (HPE).
This release also includes the following corrections and modifications:
When deploying Genesys Desktop, the HPE Python script now correctly specifies the actual host name in the conf/server.xml file.
(ER# 297744687)
When deploying MCR Knowledge Manager, the HPE Python script now correctly adds a single connection to Universal Contact Server (UCS) from MCR Knowledge Manager. (ER# 295083170)
When deploying SNMP Master Agents, the HPE Python script now correctly adds client connections from each Solution Control Server (SCS) instance to SNMP Master Agents. (ER# 292695842)
The TrueConnect strategy sub_TrueConnect_getDN no longer sends an additional validateDN request when the ADP (that validates DNs) finds matching DNs. [(ER# 294194721)
When deploying Genesys Desktop, the HPE Python script now correctly add a Configuration Server Proxy connection to the Genesys Desktop application. (ER# 296330381)
The following Known Issues have been fixed in this release: 285752961, 289304037, 288650451, 289415608, 289214713, 286979866, 286979845, 286979841, 288212632, 288047390, 289450792, 289377689, 288770960, 277009881, 275475104, and 276064161.
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 Hosted Provider Edition.
This release also includes the following corrections and modifications:
The "Linux Applications" part of "Application Maintenance" section of the "System Maintenance" chapter in the Hosted Provider Edition 8.1 Solution Guide now includes the full description. (ER#s 280341331, 283101185, 283133769, 283166311)
The first step in the "Setting up NFS on All Nodes" procedure in the "Cluster Configuration" appendix of the Hosted Provider Edition 8.1 Solution Guide is now correct. (ER# 283141581)
The port number used for cluster interconnect communications is now in the garepository configuration file: /etc/sysconfig/network-scripts/garepository-confg. Previously, this port number was embedded in the garepository startup file: /etc/sysconfig/network-scripts/garepository. (ER# 286273989)
Genesys Desktop no long disconnects from T-Server and/or SIP Server when it is configured to use the ADDP protocol. Previously in this scenario, all agents were put out of service. (ER# 282919025)
Supported Operating Systems
New in This Release
Corrections and Modifications
This hot fix provides the following new functionality:
addTemplates. Previously, associations were unenforced, preventing the editing of applications in Genesys Administrator.
The new action:
application_type_hpe_template, such as DBServer_hpe_template or TServer_hpe_template;In contrast with standard application templates, the newly created templates do not include options, which Hosted Provider Edition deployments do not require.
To activate the new action, run the following command, substituting the values for your configuration:
$ hpe_config.py {'-host':'h-001.msite.domain.com', '-port':'7770', '-user':'default', '-password':'password', '-action': 'addTemplates'}
(ER# 295563855)
This release includes the following corrections and modifications:
The Python tenant creation script sometimes did not execute properly when calling the HasACE(), GetACE(), or SetAccount() functions of the Python gcti_cfg library, especially in 64-bit Linux environments. The script now executes properly. (ER# 295878842)
Python configuration scripts now create proper application templates for each application they create. Each application is now associated to a respective application template. Previously, Python configuration scripts created applications with no association to application templates, preventing the user from being able to edit these applications in Genesys Administrator. (ER# 296098663)
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 includes the following corrections and modifications:
When ADP detects multiple DNs and returns error code 0, the TrueConnect strategy now sends the user only one validateDN request to supply the Tenant DBID that is necessary to resolve the DN conflict. The sub_TrueConnect_getDN subroutine formerly sent an unnecessary second request. (ER# 294500362)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. There are no new features in this release of Hosted Provider Edition.
This release also includes the following corrections and modifications:
The sub_TrueConnect_getDN subroutine and the TrueConnect strategy have been modified so that an agent can enter their DN manually if the ANI provided with the call does not exist in the configuration database, or if the ANI matches a Route Point from another Tenant's switch. Previously, when an agent provided an ANI that did not exist in the configuration database, the call was disconnected. (ER# 293014041)
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 Hosted Provider Edition 8.1.
ARDBIDFIX.exe utility in Genesys Administrator release 8.1.000.16 automatically replaces incorrect DBIDs with the correct references. When you use the Configuration Import Wizard to import configuration information from an XML file, all Alarm Reaction Script objects that are imported from the XML file, and include instructions to start or stop Applications, might have incorrect references (DBIDs) to Application objects in the new database after the XML import is completed.
(ER# 279752239)
This release also includes the following corrections and modifications:
The "Adding a New Tenant to GoldenGate Replication" procedure is now included in the "System Maintenance" chapter of the Hosted Provider Edition 8.1 Solution Guide. (ER# 277062491)
The "Setting up rsync" procedure found in the "Cluster Configuration" appendix of the Hosted Provider Edition 8.1 Solution Guide now contains the correct steps to perform if the ARM Runtime Web Server instances are running in a different subnet than the Genesys Administrator Extension cluster is running. (ER# 277188706)
The Hosted Provider Edition has been verified with Reporting and Analytics Aggregates (RAA) hot fix version 8.0.100.07, which fixes an issue where primary key violations may have occurred for the AG2_* tables and/or
database locks when two Aggregation sessions were performing an INSERT INTO AG2_* table and another Aggregation session was performing a DELETE from the same table.
(ER# 277059381)
The Hosted Provider Edition has been verified with Genesys Administrator Extension release 8.1.001.33 which fixes an issue where Inbound Voice Service deployment for a Tenant did not work after the initial deployment because the required updates were not made to the Network SIP Strategy�s Transaction object that was used to route the call. (ER# 277260651)
For third-party applications on Linux OS hosts, when the Local Control Agent (LCA) is restarted, the Solution Control Server (SCS) now recognizes the primary application as running. Previously in this scenario, SCS would switch over to the backup application, and the virtual machine had to be restarted. (ER# 276275801)
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 Hosted Provider Edition 8.1.
This release also includes the following corrections and modifications:
There are no corrections or modifications in this release.
This section provides the latest information on known issues and recommendations associated with this product.
When deploying Inbound, eServices, and Outbound services for a tenant, the HPE Python scripts do not update the alias file for Genesys Interactive Insights. Update the file manually after a service deployment and manually invoke the aggregation engine. See the Genesys Interactive Insights 8.1 Deployment Guide and Reporting and Analytics Aggregates 8.1 Deployment Guide for details. (ER# 293931815)
| Found In: 8.1.200.34 | Fixed In: |
The HPE Python scripts do not provide migration steps for MCP from 8.1.3 to 8.1.5 release. Perform the following procedure:
Apply.Load default options from the template.Open.NO.NO for all further prompts except the following HPE-specific options:play.usedefaultsearchorder=false
http_proxy=initial_request_maxage= 604800000
routeset=<sip:s1hlb-MSRM.hpe.genesyslab.com:5060;lr>
securerouteset=<sip:s1hlb-MSRM.hpe.genesyslab.com:5061;lr>
transport.0=transport0 udp:s1hv-006.hpe.genesyslab.com:5060
transport.2=transport2 tls:s1hv-006.hpe.genesyslab.com:5061
cert=$InstallationRoot$/config/x509_certificate.pem key=$InstallationRoot$/config/x509_private_key.pem
play.musicbasepath=http://s1hlb-ARM.hpe.genesyslab.com
record.basepath=file://$InstallationRoot$
voipmetrics.localhost=codecs=pcmu
telephony eventsrtp.localaddr=logs=
silent_shutdown=1
no_cache_url_substring= cgi-bin,jsp,asp
change digits 1 to 0
session_vars=
session.connection.local.uri|LOCALURI|0|session.connection.remote.uri|REMOTEURI|0|session.connection.originator|ORIGIN|0|session.
connection.protocol.name|PROTOCOLNAME|0|session.connection.protocol.version|PROTOCOLVERSION|0|session.connection.protocol.
sip.headers|Sip.Invite|6|session.connection.protocol.sip.headers.originalcase|Sip.Invite.originalcase|6|session.connection.redirect
|REDIRECTHEADER|7|session.connection.callidref|CALLIDREF|0|session.vendor_name.instance.parent|PARENT|0|session.
connection.ocn|OCN|0|session.connection.rdnis|RDNIS|0|session.connection.rreason|RREASON|0|session.connection.uuid|
XGENESYSCALLUUID|0|session.connection.dn|IVRPORT|0|session.vendor_name.cs.username|XGENESYSCSUSERNAME|0|
session.vendor_name.cs.password|XGENESYSCSPASSWORD|0
| Found In: 8.1.200.34 | Fixed In: |
When deploying GVP components, verify that the HPE Python script added the following connections:
If these connections are missing, add them manually. (ER# 298675068)
| Found In: 8.1.200.34 | Fixed In: |
After deleting a tenant by using the HPE Python scripts, you must perform additional manual operations: delete the tenant's Applications folder and delete the eth1:x network interface manually from the correspondent virtual machines. (ER# 302371466)
| Found In: 8.1.200.34 | Fixed In: |
When using the HPE deployment script, verify that the log-filter section with the default-filter-type=hide option are added to the following applications:
Policy Server
MRCP Proxy
Reporting Server
Resource Manager
MCP
EZPulse Collector
GAX_EZPulse
If the default-filter-type option is missing, add it manually. (ER# 306638882)
| Found In: 8.1.200.34 | Fixed In: |
After using the Python scripts to upgrade HPE 8.1.1 to 8.1.2, perform the following manual tasks for Configuration Server and DB Server:
cfg_dbserver_bk (working as a backup).cfg_dbserver (working as a backup).confserv_bk (working as a backup).confserv (stopped before upgrade, the Python config file should use confserv_bk parameters).confserv_bk (working as a primary). The primary Configuration Server confserv becomes primary.confserv.confserv_bk.| Found In: 8.1.200.34 | Fixed In: |
During creation of the Management Site, the HPE Python scripts create roles without Genesys Administrator and Genesys Administrator Extension (GAX) privileges. Verify the role privileges manually using Genesys Administrator and set as necessary for each role according to the Hosted Provider Edition 8.1 Solution Guide. (ER# 303849881)
| Found In: 8.1.200.34 | Fixed In: |
When deploying the Inbound service (only) using the HPE Python scripts, verify the connections for tenant Desktop applications. If a connection to an Interaction Server is present, delete it manually. (ER# 304725420)
| Found In: 8.1.200.34 | Fixed In: |
When deploying eServices for a tenant, verify the connection of the corresponding WebAPI Server. If a connection to a Classification Cluster is present, delete it manually. (ER# 303732581)
| Found In: 8.1.200.34 | Fixed In: |
When deploying a new segment by using the HPE Python scripts, verify (and correct if needed) the sip-address option in the SIP Server Application for TrueConnect. Set the option value to hNN-TC-vip.sgNN.domain.com, where NN is the segment number. (ER# 305151206)
| Found In: 8.1.200.34 | Fixed In: |
Before deleting a tenant by using the HPE Python script, you must first delete the contents of the Transactions folder for the parameterized NSIP Strategy Object > Annex section > OPM entry that contains the Routing Point dedicated to delivery calls from Network SIP Server to that Tenant. (ER# 305564551)
| Found In: 8.1.200.34 | Fixed In: |
During creation of a tenant, the HPE Python scripts do not add Read permissions to the tenant Power Administrator for the tenant's host objects. Workaround: Add the permissions manually. (ER# 305135957)
| Found In: 8.1.200.34 | Fixed In: |
During a manual upgrade of HPE 8.1.1 to 8.1.2, eServices components on tenant virtual machines require the following upgrade procedure:
eServices810 folder that is packed in the tenant.tar.gz file on the HPE DVD to the tenant's virtual machines.Server Info/Working Directory for all tenant eServices applications to point to the new 810 directories.GES_HOME variable in startup files for UCS, Classification Server, Training Server, and E-Mail Server. Correct if necessary.| Found In: 8.1.200.34 | Fixed In: |
During a Management Site deployment, after GAX is deployed and started, you must manually add the following files to virtual machines that house GAX:
To the $CATALINA_HOME\webapps\gax\WEB-INF\classes directory:
$CATALINA_HOME\webapps\gax\WEB-INF\classes\DBScripts\eSContSrv—must contain the ucs_oracle.sql file taken from the Universal Contact Server component.
$CATALINA_HOME\webapps\gax\WEB-INF\classes\DBScripts\InfoMartDBScr—must contain the make_gim_view_for_tenant.sql file taken from the Genesys Infomart component.
$CATALINA_HOME\webapps\gax\WEB-INF\classes\HAScripts\TSrvSIP\—must contain the "eth1_0_up" and "eth1_0_down" files (for the HPE script file to bring up/down the sub-interface), as follows:
The eth1_0_up file must contain the following:
#!/bin/bash
SUDO=/usr/bin/sudo
IFCONFIG=/sbin/ifconfig
ARPING=/sbin/arping
AWK=/bin/awk
SCRIPT_NAME=`basename $0`
SUBINTERFACE=${SCRIPT_NAME/_up/}
NETWORK_DEVICE=${SUBINTERFACE/:*/}
if [ ! -f /etc/sysconfig/network-scripts/ifcfg-$SUBINTERFACE ]; then
exit 1
fi
if [ ! -f /etc/sysconfig/network-scripts/ifcfg-$NETWORK_DEVICE ]; then
exit 1
fi
if [ ! -f /etc/sysconfig/network-scripts/voiproute-conf ]; then
exit 1
fi
. /etc/sysconfig/network-scripts/voiproute-conf
. /etc/sysconfig/network-scripts/ifcfg-$SUBINTERFACE
#echo "ifconfig command: $SUDO $IFCONFIG $SUBINTERFACE $IPADDR netmask $NETMASK"
$SUDO $IFCONFIG $SUBINTERFACE $IPADDR netmask $NETMASK
. /etc/sysconfig/network-scripts/ifcfg-$NETWORK_DEVICE
#echo "arping command:$SUDO $ARPING -c 2 -U -I $NETWORK_DEVICE ${VOIP_IPGATEWAY_NAME} -s $IPADDR"
$SUDO $ARPING -c 2 -U -I $NETWORK_DEVICE ${VOIP_IPGATEWAY_NAME} -s $IPADDR >/dev/null
The eth1_0_down file must contain the following:
#!/bin/bash
#
SUDO=/usr/bin/sudo
IFCONFIG=/sbin/ifconfig
SCRIPT_NAME=`basename $0`
SUBINTERFACE=${SCRIPT_NAME/_down/}
$SUDO $IFCONFIG $SUBINTERFACE down
$CATALINA_HOME\webapps\gax\WEB-INF\classes\strategies—must contain the following files, provided by HPE:
- nailed_up.zcf
- Parameterized_Strategy1.rbn
- Parameterized_Strategy1.zcf
- sub_TrueConnect_getTarget.rbn
- sub_TrueConnect_getTarget.zcf
- sub_TrueConnect_playAnn.rbn
- sub_TrueConnect_playAnn.zcf
To the /home/genesys/GCTI directory:
/home/genesys/GCTI—must contain the following folders that you copy from the HPE DVD:
To the /mnt/ocfs2 (repository) directory:
/mnt/ocfs2/ip/ips/Standalone—must contain the subfolder GCTI with the tenant.tar.gz file that you copy from the HPE DVD.| Found In: 8.1.200.34 | Fixed In: |
Before deploying the Genesys Voice Platform service by using GAX, make sure that the directory /home/genesys/GCTI on the GAX virtual machine contains the Scripts, GVPIntegration, and SampleStrategies subfolders that are copied from the HPE DVD. (ER# 305242841)
| Found In: 8.1.200.34 | Fixed In: |
The special DB admin user HPE_DB_ADMIN may be required for a creation of tenant database users in Oracle using the HPE Python script. See the Hosted Provider Edition 8.1 Solution Guide for details. (ER# 305959301)
| Found In: 8.1.200.34 | Fixed In: |
After using GAX to deploy T-Server for Avaya CM and T-Server for Cisco UCM deployment, verify that the corresponding IP packages are present on the tenant virtual machines. If there are no packages, verify the presence of the tenant.tar.gz file in the /mnt/ocfs2/ip/ips/Standalone/GCTI directory on the GAX virtual machine. If the file is missing, copy it from the HPE DVD and repeat the deployment. If the file is present, you can manually execute the shell command from the GAX virtual machine and check for error messages. The shell command can be copied from the cmd value of the execShellCmd action from the Deployment Action Log of the deployed service. (ER# 303864048)
| Found In: 8.1.200.34 | Fixed In: |
The HPE Python upgrade script might not upgrade some single applications, issuing the following message:
12:21:19.411 INFO: Upgrade FAILED:
12:21:19.411 INFO: DBServer_sg01_icon_NetTsrvSIP_bk (could not switchover)
Or
12:05:26.804 INFO: Upgrade FAILED:
12:05:26.804 INFO: DBServer_sg01_icon_NetTsrvSIP_bk (could not replace files)
Workaround: Stop the affected applications, remove the already successfully upgraded applications from the configuration file, and run the script again.
(ER# 306537665)
| Found In: 8.1.200.34 | Fixed In: |
When using the HPE Python script, verify that the initial-page-uri configuration option (in the gvp.service-prerequsite section) of the Voice Platform Profile object for a particular tenant contains the proper URI to the location of the main VoiceXML application file for that tenant. If necessary, change this option value manually. (ER# 306829451, 306831161)
| Found In: 8.1.200.34 | Fixed In: |
While running, the virtual machines that house the Genesys Interactive Insights repositories cannot be moved using VMotion VMware.
Workaround: Turn off the nodes before attempting to move them using VMotion.
(ER# 296026835)
| Found In: 8.1.200.34 | Fixed In: |
Because of a defect in SAP BusinessObjects Enterprise, the Genesys Interactive Insights (GI2) Web Intelligence server might require a manual restart following a host reboot. (ER# 288212632; SAP issue 155711)
Workaround: See the instructions for ER# 288212632 in the Genesys Interactive Insights 8.1.x Release Note.
| Found In: | Fixed In: |
Announcements are not created automatically in ARM for a tenant when creating a tenant with Inbound and/or Outbound services using the Python scripts.
Workaround: Use Genesys Administrator Extension to create the required announcements for this tenant.
(ER# 285752963)
| Found In: 8.1.100.32 | Fixed In: |
You cannot automatically disable or remove a service from a tenant using the Python scripts.
Workaround: If a service for a tenant was deployed using Genesys Administrator Extension, use Genesys Administrator Extension to disable the service. If a tenant was created with a service using the Python scripts, manually disable this service.
(ER# 285752961)
| Found In: 8.1.100.32 | Fixed In: 8.1.200.34 |
Users are not created in the Oracle database for a tenant that is created with an Inbound, Outbound or eServices Service using the Python scripts.
Workaround: Create the database users for the tenant manually, and use the DB init scripts included on the Hosted Provider Edition DVD to initiate the databases.
(ER# 289304037)
| Found In: 8.1.100.32 | Fixed In: 8.1.200.34 |
Interaction Routing Designer (IRD) cannot access parameterized strategies for tenants after services deployment with Genesys Administrator Extension.
Workaround: Make the following adjustments in the configuration layer:
Ensure that the following tenant level strategies in the Scripts folder of the Management Framework have the value of the location option in the strategy section of the Annex tab set to database:
Parameterized_Strategy1sub_TrueConnect_playAnnsub_TrueConnect_getTargetNailedUpStrategyNailedUpStrategy should be copied from the \solution_specific\hpe\linux\SampleStrategies\nailed_up.zcf file on the Hosted Provider Edition DVD to the Tomcat server at the {CATALINA_HOME}/webapps/gax/WEB-INF/classes/strategies/ location.
(ER# 288650451)
| Found In: 8.1.100.32 | Fixed In: 8.1.200.34 |
When Genesys Administrator Extension deploys eServices in standalone mode (not on top of Inbound Voice or Outbound Voice Solution) it attempts to add a SIP agent that logs in as Genesys Desktop user. The deployment will be shown as failed. This error message could be ignored and the deployment could be considered as successful. (ER# 289415608)
| Found In: 8.1.100.32 | Fixed In: 8.1.200.34 |
When Genesys Administrator Extension deploys services with common applications (for example, Stat Server or SIP Server), the options for the common applications will be reset to default values, removing any customized options.
Workaround: Manually create and customize options for applications common to multiple services only after all services have been deployed.
(ER# 289214713)
| Found In: 8.1.100.32 | Fixed In: 8.1.200.34 |
When Genesys Administrator Extension performs a service deployment, no indication is given when the session has expired. In this case, an attempt to complete the deployment will fail.
Workaround: Ensure that the browser is not left idle in the middle of a deployment for longer than the configured timeout (<tomcat-install-directory>/conf/web.xml).
(ER# 286979873)
| Found In: 8.1.100.32 | Fixed In: |
Genesys Administrator Extension sets the Outbound Contact Server (OCS) DB Port to 6056 in an Outbound deployment. This is only an example value. You must specify the correct port number from your configuration before continuing with a deployment. (ER# 286979866)
| Found In: 8.1.100.32 | Fixed In: 8.1.200.34 |
When using Genesys Administrator Extension to deploy eServices, the Fields names on the Wizard's Credentials page displays incorrectly. Instead of "Genesys eServices Email Server", it should read as "Corporate Email Server." (ER# 286979845)
| Found In: 8.1.100.32 | Fixed In: 8.1.200.34 |
When using Genesys Administrator Extension to deploy the eServices files, the following are not shown in the list of components/applications to be installed on the second host: Genesys Desktop, Chat Server, and Third Party components 8.0.1 and 8.0.2. (ER# 286979841)
| Found In: 8.1.100.32 | Fixed In: 8.1.200.34 |
Massive updates to configuration can slow down IRD and make it unresponsive for a long period of time.
Workaround: Adjust the IRD settings to exclude unneeded objects types. This reduces the volume of information received by IRD from Configuration Server.
(ER# 289218831)
| Found In: 8.1.100.32 | Fixed In: |
On RedHat Linux 5.3 and above, you may see the following symptoms:
Failed in the Servers section of the CMC.Running state.Workaround:
BOHOME entry at the start of the Placeholders.sh file to reflect the install location of the BusinessObjects environment.Placeholders.sh -cms <cms:port> -pass <Administrator password> -global -update WEBI_LD_PRELOAD '$LD_PRELOAD$'
Placeholders.sh -cms <cms:port> -pass <Administrator password> -global -update MDAS_LD_PRELOAD '$LD_PRELOAD$'(ER# 288212632)
| Found In: 8.1.100.32 | Fixed In: 8.1.200.34 |
After installing RAA into the Genesys Info Mart root directory on Linux, an extra agg subdirectory is created in the Genesys Info Mart Root as GIM Root\agg\agg which results in Genesys Info Mart not being able to see the Aggregation engine.
Workaround: Move the content of the GIM Root\agg\agg directory into the GIM Root\agg\ directory.
(ER# 288047390)
| Found In: 8.1.100.32 | Fixed In: 8.1.200.34 |
When using Genesys Administrator Extension, the Inbound and Outbound deployment fail if the Oracle user already exists.
Workaround: If an Inbound or Outbound deployment is reported as failed, check the Actions where the failure occurred. If the deployment failed while in SQL execution, check that the user with the username is present in the database.
(ER# 289450792)
| Found In: 8.1.100.32 | Fixed In: 8.1.200.34 |
When using Genesys Administrator Extension to deploy an Inbound or Outbound Service that includes Virtual IP controlled applications, Auto-restart is enabled.
Workaround: Manually uncheck Auto-restart for the Virtual IP controlled applications after the Inbound or Outbound Service is deployed by Genesys Administrator Extension.
(ER# 289377689)
| Found In: 8.1.100.32 | Fixed In: 8.1.200.34 |
When attempting to edit the configuration object(s) from a server application that is connected to a writable proxy instance, and using its startup Config Server account that is allowed to make changes (such as the SYSTEM identity), Configuration Server rejects write attempts with the incorrect error message Config Server operates in emergency mode instead of the correct error message Insufficient permissions to complete this operation.
Workaround: Ensure that all application that require write access have the appropriate accounts with enough permissions.
(ER# 289231875)
| Found In: 8.1.100.32 | Fixed In: |
When using Genesys Agent Desktop during a campaign, the Do Not Call check box and the Call Result drop-down list are enabled, causing incorrect call results in progressive ASM dialing mode.
Workaround: To disable the Do Not Call check box and the Call Result drop-down list, set the [outbound] enable-chain-75api option to False.
(ER# 288884520)
| Found In: 8.1.100.32 | Fixed In: |
Genesys Administrator Extension performs a hostname to IP validation to ensure that the IP address in the interface file is configured correctly on the host during the Inbound and Outbound service deployment. If eth1:x does not exist on the host, the pre-requisite check done by Genesys Administrator Extension will fail, and Genesys Administrator Extension will not start the deployment.
Workaround: Ensure that eth1:x exists on the host prior to initiating an ASD deployment .
(ER# 288770960)
| Found In: 8.1.100.32 | Fixed In: 8.1.200.34 |
While running, the virtual machines that house the Genesys Administrator Extension and Audio Resource Management repositories cannot be moved using VMotion VMware.
Workaround: Turn off the nodes before attempting to move them using VMotion.
(ER#s 287644631, 289362509)
| Found In: 8.1.100.32 | Fixed In: |
When Genesys Desktop is configured to use the ADDP protocol, a disconnect from T-Server and/or SIP Server could occur. This will result in all agents being put out of service. (ER# 282919025)
| Found In: 8.1.000.48 | Fixed In: 8.1.100.32 |
When upgrading Genesys Interactive Insights to a new version, the database connections of the were configured in the previously installed version default to an internal database connection. This causes reports to fail.
Workaround: Change the connection in the BOE Universe. For more information, see the Genesys Interactive Insights Deployment Guide.
(ER# 283104311)
| Found In: 8.1.000.48 | Fixed In: |
The "Linux Applications" part of "Application Maintenance" section of the "System Maintenance" chapter in the Hosted Provider Edition 8.1 Solution Guide does not include the full description. It should be as follows:
Genesys recommends the following upgrade procedures for the Hosted Provider Edition components that run on the Linux Operating System:
upgrade-app.py script. Upgrade Application with the Python Script procedure:
\solution_specific\hpe\linux\Scripts\Application Upgrade Scripts directory from the Hosted Provider Edition DVD to the Application Upgrade Scripts directory on the Admin host.make-upgrade-list.README file.cfg-host,cft-port, cfg-user, cfg-password, target-user, and target-group.package—The application package location (could be the local directory). #keep gvma_asterisk.cfg—Uncomment and determine the file names required if you need to preserve the following files in the package: runLrm.sh file for License Reporting ManagercontactServer.sh file for Universal Contact Server gim_etl_server file for Genesys Info Mart app-type 1—The application type (it can be found in the ip_description.xml file—CfgAppType—for example, 1 for SIP Server and T-Servers).app-filter TSrvSIP_sg01_*_pr except 05_ABCD|07_XYZ—The list of the applications to be upgraded. app-filter TSrvSIP_sg02_*_pr.# to the LCA package and host-filter if the LCA upgrade is not necessary.# to the applications that are not being upgraded (see step 1 above). host-filter—The list of hosts on which LCA is to be updated.make-upgrade-list.py script creates the configuration file for the upgrade-app.py script:Go to the Application Upgrade Scripts directory and run the python make-upgrade-list.py script:
# python make-upgrade-list.py List Config
Check the information in the Config file that will appear in the Application Upgrade Scripts directory. The following is an example of this file:
[config]
cfg-host h-001.msite.domain.com
cfg-port 7770
cfg-user default
cfg-password password
scs-app-name SCServer_m_pr
ssh-user root
target-user genesys
target-group genesys
[upgrade]
package /home/genesys/pycfg1/Appl__
app SCServer_s1_1_pr
app SCServer_s1_1_bk
upgrade-app.py script.Go to the Application Upgrade Scripts directory and run the python upgrade-app.py script:
# upgrade-app.py Config
When the script finishes, verify the list of successfully upgraded / failed applications (and all serious warnings) which are printed at the end of script output.
(ER#s 280341331, 283101185, 283133769, 283166311)
| Found In: 8.1.000.48 | Fixed In: 8.1.100.32 |
The first step in the "Setting up NFS on All Nodes" procedure in the "Cluster Configuration" appendix of the Hosted Provider Edition 8.1 Solution Guide is incorrect. It should be as follows:
On each Genesys Administrator Extension host, edit the /etc/exports file, and add the /mnt/ocfs2/ as the exported file system specifying the hosts with which the /mnt/ocfs2/ directory is being shared and the respective options.
When sharing the file system with any host, the file should contain the following line:
/mnt/ocfs2/ *(rw,sync)
To limit the access to certain machines only, change the asterisk (*) to the fully qualified domain names or IP addresses of the respective hosts or networks.
For example, for the two-site environment, where the Management Site is co-located with Services Site One, and the Backup Management Site is co-located with Services Site Two, and the two sites use the 192.168.192.0/23 and 192.168.196.0/23 IP addresses, the /etc/exports file should contain the following lines:
/mnt/ocfs2 192.168.192.0/255.255.254.0(rw,sync)
/mnt/ocfs2 192.168.196.0/255.255.254.0(rw,sync)
Note: The Genesys Administrator Extension Repository File System must be accessible to the Genesys Administrator hosts of the Management Site in their respective primary and backup containers.
(ER# 283141581)
| Found In: 8.1.000.48 | Fixed In: 8.1.100.32 |
For third-party applications on Linux OS hosts, when the Local Control Agent (LCA) is restarted, the Solution Control Server (SCS) does not recognize the primary application as running; therefore, switches over to the backup application. A manual restart of LCA must be avoided. A restart of the virtual machine should be considered instead. (ER# 276275801)
| Found In: 8.1.000.40 | Fixed In: 8.1.000.48 |
After Disaster Recovery, the Genesys Administrator Extension repository nodes must be started one at a time as follows:
(ER# 277009881)
| Found In: 8.1.000.40 | Fixed In: 8.1.200.34 |
While running, Interaction Concentrator (ICON) does not support the addition of T-Servers.
Workaround: Re-start ICON when a new T-Server is added to the Hosted Provider Edition environment.
(ER# 275475104)
| Found In: 8.1.000.40 | Fixed In: 8.1.200.34 |
Interaction Server must be re-started when a new tenant is added to its tenant list. (ER# 276064161)
| Found In: 8.1.000.40 | Fixed In: 8.1.200.34 |
Genesys Administrator Extension does not currently automate the Tenant connection between Genesys Interactive Insights and the Business Objects Enterprise (BOE) Universe Connection.
Workaround: Configure Genesys Interactive Insights according to Chapter 4 "Setting Data-Access Restrictions for Multi-Tenant Environments" in the Genesys Interactive Insights 8.0 Deployment Guide.
(ER# 275766221)
| Found In: 8.1.000.40 | Fixed In: |
The Hosted Provider Edition solution does not support the association of alphanumeric Trunk Group DNs with IVR profiles in Genesys Administrator. (ER# 270271160)
| Found In: 8.1.000.40 | Fixed In: 8.1.100.32 |
Inbound Voice Service deployment for a Tenant does not work after the initial deployment, since the required updates are not made to the Network SIP Strategy's Transaction object that routes the call. Install Genesys Administrator Extension version 8.1.001.31, and re-upload the Inbound Voice Service XML that comes bundled with the IP to correct this issue. (ER# 277260651)
| Found In: 8.1.000.40 | Fixed In: 8.1.000.48 |
Primary key violations may occur for the AG2_* tables and/or
database locks when two Aggregation sessions are performing an INSERT INTO AG2_* table and another Aggregation session is performing a DELETE from the same table. To resolve this issue, Genesys recommends upgrading to the Reporting and Analytics Aggregates (RRA) Hot Fix version 8.0.100.07.
(ER# 277059381)
| Found In: 8.1.000.40 | Fixed In: 8.1.000.48 |
Currently, the Genesys Administrator Extension Linux Cluster Virtual Hostname and IP address cannot be accessed from a different subnet.
If the ARM Runtime Web Server instances are running from a different subnet than the Genesys Administrator Extension cluster, instead of using the "Setting up rsync" procedure found on page 425 of the Hosted Provider Edition 8.1 Solution Guide use the following instructions. Assuming that the Genesys Administrator Extension machines are configured with h-008.msite.domain.com as the hostname on the first Genesys Administrator Extension node in the cluster and with h-009.msite.domain.com as the hostname on the second Genesys Administrator Extension node in the cluster, make the following changes:
On the ARM Runtime Web Server machine1, edit the crontab file, and modify the rsync entries as indicated below to synchronize every 30 minutes (on the 15th minute and 45th minute of every hour) from the first Genesys Administrator Extension node, and every 30 minutes (on the 7th minute and 37th minute of every hour) from the second Genesys Administrator Extension node:
15,45 * * * * rsync -e ssh -avz root@h-008.msite.domain.com:/mnt/ocfs2/arm/ /mnt/ocfs2/arm/
7,37 * * * * rsync -e ssh -avz root@h-009.msite.domain.com:/mnt/ocfs2/arm/ /mnt/ocfs2/arm/
On the ARM Runtime machine2, edit the crontab file, and modify the rsync entries as follows to synchronize every 30 minutes (on the 0th minute and the 30th minute of every hour) from the first Genesys Administrator Extension node and every 30 minutes (on the 22nd minute and 52nd minute of every hour) from the second Genesys Administrator Extension node:
0,30 * * * * rsync -e ssh -avz root@h-008.msite.domain.com:/mnt/ocfs2/arm/ /mnt/ocfs2/arm/
22,52 * * * * rsync -e ssh -avz root@h-009.msite.domain.com:/mnt/ocfs2/arm/ /mnt/ocfs2/arm/
(ER# 277188706)
| Found In: 8.1.000.40 | Fixed In: 8.1.000.48 |
The following "Adding a New Tenant to GoldenGate Replication" procedure was omitted from the "System Maintenance" chapter of the Hosted Provider Edition 8.1 Solution Guide.
Adding a New Tenant to GoldenGate Replication
When a new tenant is added through Genesys Administrator Extension, the new service schemas are added to the Hosted Provider Edition database instances. These services must also be added to the GoldenGate replication procedures.
Note: Take note the schema names that are input to Genesys Administrator Extension during the add tenant creation process.
DUMPFILE=<Export File Name>.dmp
DIRECTORY=<Datapump Directory Object>
LOGFILE=<Log File Name>.log
SCHEMAS=<Outbound Tenant Schema Name>, <GIM Tenant Schema Name>
STATUS=100000
DUMPFILE=<Import File Name>.dmp
DIRECTORY=<Datapump Directory Object>
LOGFILE=<Log File Name>.log
SCHEMAS=<Outbound Tenant Schema Name>, <GIM Tenant Schema Name>
STATUS=100000
extract script to add the new schemas with the SEQUENCE and TABLE statements. The following are sample SEQUENCE and TABLE statements:
SEQUENCE =<Outbound Tenant Schema Name>.*;
TABLE =<Outbound Tenant Schema Name>.*;
SEQUENCE =<GIM Tenant Schema Name>.*;
TABLE =<GIM Tenant Schema Name>.*;
pump script to add the new schemas with the SEQUENCE and TABLE statements. The following are sample SEQUENCE and TABLE statements:
SEQUENCE =<Outbound Tenant Schema Name>.*;
TABLE =<Outbound Tenant Schema Name>.*;
SEQUENCE =<GIM Tenant Schema Name>.*;
TABLE =<GIM Tenant Schema Name>.*;
replicat script to add the new schemas with the MAP statements. The following is a sample MAP statements:
MAP <Outbound Tenant Schema Name>.*, <Outbound Tenant Schema Name>.*;
MAP <GIM Tenant Schema Name>.*, <GIM Tenant Schema Name>.*;
ADD TRANDATA procedure within the GoldenGate ggsci command line utility to activate supplemental logging on the tables. The following is a sample ADD TRANDATA procedure:
[oracle@m1h-OraSrv1 ~]$ cd <GoldenGate Installation Directory>
[oracle@m1h-OraSrv1 ~]$ ggsci
GGSCI (m1h-OraSrv1) 1> ADD TRANDATA <GIM Tenant Schema Name>.*
GGSCI (m1h-OraSrv1) 1> ADD TRANDATA <OCS Tenant Schema Name>.*
extract, pump, and replicat GoldenGate processes.For more information about these GoldenGate scripts, see the "GoldenGate" Appendix, in the Hosted Provider Edition 8.1 Solution Guide.
(ER# 277062491)
| Found In: 8.1.000.40 | Fixed In: 8.1.000.48 |
This section provides corrections and updates for issues found in currently released documentation for this product. The changes described here will be included in future published versions of the Hosted Provider Edition 8.1 Solution Guide.
In Task Summary: Deploying a Segment Block, "Configure startup scripts" step, the first substep in the Description ("configure the VoIP route startup script...") is no longer required. The second substep is now: "If deploying TrueConnect, configure SIP virtual interface startup scripts on Hosts 11 and 12 (see Table 50). See "Additional Startup Script for SIP Server Virtual IP Address" on page 556." (ER# 305536727)
In Site Common Block Deployment > Overview > Components > Recommended Configuration, the following are the correct recommendations for GVP components: Genesys recommends storing the VP Media Control Platform applications in their own directory. For example:
PROVISIONING > Environment > Applications > Services_Site_1 > Media_Server_site_1> vpMediaControl_s1_6
Genesys also recommends storing the VP Resource Manager, VP Reporting Server and VP MRCP Proxy applications in their own directory. For example:PROVISIONING > Environment > Applications > Services_Site_1 > GVP_site_1_1> vpResMngr_s1_1_2
PROVISIONING > Environment > Applications > Services_Site_1 > GVP_site_1_1> vpReportServer_s1_1_pr
PROVISIONING > Environment > Applications > Services_Site_1 > GVP_site_1_1> vpMRCPProxy_s1_1_pr
(ER# 305536269)
The description for the alterWhat parameter is missing (Python scripts) in Table 66.
This parameter is mandatory for alterSegmentalterCommonBlock actions.
For the alterSegment action, the alterWhat parameter should be addEZPulseBlock or dropEZPulseBlock (Adds/removes EZPulse blocks).
For the alterCommonBlock action, the alterWhat parameter should be addMCP or dropMCP (Adds/removes Media Control Platform (MCP)).
(ER# 306766219)
In Chapter 21 (Using Python scripts), the following actions are missing in Table 68: addTemplates, alterServices, redistributeStrategies and alterCommonBlock.
addTemplates: Checks all Applications for Application Template association and adds the association if it is missing. It creates an Application Template with the specific name (<Application type>_hpe_template) in cases where the template is not found.
alterServices: This action is in Table 68, but the following description is missing - It adds/removes EZPulse blocks on the segment level (the alterWhat parameter should be addEZPulseBlock or dropEZPulseBlock).
redistributeStrategies: Redistribution strategies across a list of tenants #configParams[tenantNames], configParams[strategyNames].
alterCommonBlock: Alters Common Block in the HPE configuration. Adds/removes MCPs (the alterWhat parameter should be addMCP or dropMCP).
(ER# 306766217)
GAX provides the deployment at a Tenant level for GVP, EZPulse, T-Server for Avaya CM, and T-Server fro Cisco UCM, as follows:
On the GAX hosts at the Management site level, copy Scripts, Sample Strategies, and the GVPIntegration/URSSample directories to the following respective locations:
/home/genesys/GCTI/Scripts/home/genesys/GCTI/SampleStrategies/home/genesys/GCTI/GVPIntegration/URSSample
Copy the tenant.tar.gz file from the HPE DVD to the /mnt/ocfs2/ip/ips/Standalone/GCTI directory.
The following corrections are required to the Solution Guide to the Procedure: Upgrading Genesys Administrator Extension for HPE 8.1.2 (page 554):
Genesys_Administrator_Extension_812.apd file from the installation package.Import Metadata, then
navigate to the folder in which the application template was
deployed.
Options tab and import the configuration options from the configuration file that you previously created. Select Yes to overwrite the option values if the corresponding option names match in the object you are editing, and the file you are going to import.
DBAccessPoint_m_gax_audit) with the following values:JDBC1521MainoracleGCOMMONMS_M1_1 (must be the same as in the DAP for logging on the Management Site)
Options tab, set the GAX/Role to the value of auditing.general/auditing option to true in the GAX Application.
When running the HPE Python scripts for a new Tenant deployment with the optGVP option set to a value of 1, add the ListForParameterized_NSIP_GVP_Strategy object to a list in the Transactions of the Environment before you begin the installation. (ER# 305188461)
The following LCA upgrade procedure should be included in the Application Maintenance section of the Solution Guide on page 516:
disconnect-switchover-timeout option to a value of 60 (seconds).(ER# 306537745)
The Task Summary: Deploying the Site Common Block, on page 310 of the Solution Guide, should be updated with the following task after Task 11:
Configure Tomcat on Hosts 3 and 4 to access WAR files from storage.
To configure Tomcat, see the following procedure:
Configuring Tomcat Web Application Server for GVP
Directory where the content should be located is webapps.
Deploy the .war file on your Production server. (Typically, on the webapps folder of your Tomcat server.)
In the directory webapps
/usr/local/apache-tomcat-6.0.20/webapps
Create links to point to the clustered file system:
# ln -s /mnt/ocfs2/arm/announcement announcement
# ln -s /mnt/ocfs2/arm/vxml vxml
# ln -s /mnt/ocfs2/arm/music music
For Tomcat, this looks like: /announcement/ /vxml/ /music/
Update environment settings (CATALINA_HOME)
CATALINA_HOME=/usr/local/apache-tomcat-6.0.20
Restart Tomcat.
Create a new folder on the clustered file system in the Management Site:
/mnt/ocfs2/arm/gvpapp
Wait till the synchronization of the new folder is complete.
Once /mnt/ocfs2/arm/gvpapp is seen on the Service Site host, link the new directory to webapps folder:
# pwd
/usr/local/apache-tomcat-6.0.20/webapps
# ln -s /mnt/ocfs2/arm/gvpapp gvpapp
Deploy a Composer application at the Management Site clustered file system:
h-008.msite. or h-009.. ).In the directory of GVP Applications (/mnt/ocfs2/arm/gvpapp), create a subdirectory with the name matching the name of the .war file. For example, for the file name WARfileName.war create the WARfileName directory
# cd /mnt/ocfs2/arm/gvpapp
# mkdir WARfileName
.war file to the newly created directory /mnt/ocfs2/arm/gvpapp/WARfileName (using Secure Shell Copy or FTP, for example)..war file, for example: # jar -xvf WARfileName.war.war file itself into the upper directory , for example: # mv WARfileName.war.Wait till it is synchronized to the Service Site repository.
Try to access the Composer application with http / Tomcat: http://s1h-001.hpe.genesyslab.com:8080/gvpapp/...appname
(ER# 306831145)
The following procedure must be added to Chapter 14 (Site Common Block Deployment):
Creating a Database for VP Reporting Server
Create the tablespase GVPRS, with a recommended size of 700 GB.
Create the DB user RS_S with DEFAULT TABLESPACE GVPRS.
Grant the following roles and privileges to this user:
CREATE TRIGGER
CREATE SEQUENCE
CREATE TABLE
CREATE PROCEDURE
FORCE TRANSACTION
CREATE VIEW
CREATE TYPE
CREATE SESSION
CREATE INDEXTYPE
ALTER SESSION
CREATE OPERATOR
EXECUTE ON DBMS_LOCK
The following roles are optional:
CREATE ANY DIRECTORY
ALTER DATABASE
CREATE DATABASE LINK
These optional roles are not needed for core RS operation, but could be useful for customer support situations, such as import/export of the database.
Initialize the DB user with the following SQL scripts:
vpReportServer/scripts/enterprise/oracle-schema.sql
vpReportServer/scripts/enterprise/oracle-lock-stats.sql
As well, in Chapter 14 (Site Common Block Deployment):
For VP Reporting Server applications, under the Options tab, in the persistence section, ensure that the following options have the values as indicated below:
hibernate.remote.dialect—set to a value of org.hibernate.dialect.Oracle10gDialect
hibernate.remote.driver—set to a value of oracle.jdbc.driver.OracleDriver
hibernate.remote.database—set to a value of jdbc:oracle:thin:@s1h-orasrv.hpe.genesyslab.com:1521/ggvprs
hibernate.remote.user—set to a value of RS_S1_1
(ER# 304541275)
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 features or functions in this release of the Hosted Provider Edition.
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 Technical Support website. The following documentation also contains information about this solution.
Hosted Provider Edition 8.1 Solution Guide, which provides details about the architecture and how to deploy a Hosted Provider Edition environment.
Product documentation is provided on the Technical Support website, the Genesys Documentation wiki, 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 Technical Support 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.