Jump to: navigation, search

Genesys Voice Platform 8.5 Product Alerts

Link to 8.1 Product Release Advisory


Media Control Platform (MCP) v8.5.178.xx does not reuse the SIP request’s TCP connection when responding to the request. Subsequently, MCP tries to initiate a new TCP connection to the FQDN or IP (and port) present in the VIA header of the request.

As a result, MCP might fail to send a SIP response to the request if the remote doesn't accept a new TCP connection. For example, the remote is a F5 load balancer or Genesys Composer.

If you have installed MCP v8.5.178.xx, Genesys recommends you uninstall this version and install/upgrade to MCP v8.5.181.78 or a later version.


Reporting Server aggregated reports (data) do not maintain time zone information because, as designed, report generation uses the time zone format used by the host on which Reporting Server is installed. For consistent reports, Genesys recommends that you locate the Reporting Server, Genesys Administrator, and Genesys Administrator UI in the same time zone.


Resource Manager (RM) v8.5.178.66 does not reuse the SIP request’s TCP connection when responding to the request. Subsequently, RM tries to initiate a new TCP connection to the FQDN or IP (and port) present in the VIA header of the request.

As a result, RM might fail to send a response to the request if the FQDN cannot be resolved. If the request happens to be a SIP OPTIONS request, then SIP can put RM out of service. (GVP-24000)

If you have downloaded RM v8.5.178.66, Genesys recommends you uninstall this version and reinstall RM v8.5.178.79.


Starting from Media Control Platform (MCP) 8.5.176.xx and Resource Manager (RM) 8.5.175.xx, the default value for SIP TLS communications for various interfaces has been changed to TLSv1_2. Setting TLSv1_2 as default value avoids the security issues associated with the SSLv23 which allowed MCP and RM to downgrade to the vulnerable SSLv2 and SSLv3 protocols.

This means that when using the default configuration, the new MCP 8.5.176.xx and RM 8.5.175.xx versions and above will not support any protocols lower than TLSv1_2 for SIP TLS communications.

Important:

  • In scenarios where MCP or RM communicates with other components that support TLSv1 or TLSv1_1 protocols, the default configuration parameters corresponding to those SIP TLS interfaces on MCP or RM must be changed appropriately.
  • If only one MCP or RM is upgraded to the latest version, then modify the default configuration for both the MCP and RM to use TLSv1 to support interfacing with other MCPs and RMs running in older versions.

Refer to the Media Control Platform 8.5.176.05 Release Note and Resource Manager 8.5.175.95 Release Note for more details about the configuration parameters that requires changes.


Upgrading the Resource Manager to 8.5.170.64 might cause conferencing issues in the Media Control Platform. Workaround: Upgrade the Media Control Platform to 8.5.170.71 or higher versions. Or, configure the gvp.policy.voicexml-recording-allowed option to false in the tenant properties, to disable the IVR recording functionality.


VP Reporting Plugin for GAX versions 8.5.151.23 and 8.5.151.28 may not generate Call Peaks Report appropriately. Genesys recommends that customers use this feature in a lower version of the software until an appropriate resolution is provided for this issue. The latest version for this plugin is 8.5.151.14.


The Media Server DVD for the 17 April 2015 release of GVP 8.5.1 is missing the VP Reporting Plugin for GAX 8.5.120.30 in the Linux Installation Package (IP). That omission will be corrected soon; until then you can download the Linux IP through Genesys software download.


Deploy with GAX, not with GA: IMPORTANT! Functionality for deploying Genesys Voice Platform components to remote and local hosts has been discontinued in Genesys Administrator as of version 8.1.303. This functionality is now available in Genesys Administrator Extension; please refer to documentation for Genesys Administrator Extension for details.


Optimize Red Hat Enterprise Linux Performance Tip: GVP 8.1.7 and above support Red Hat Enterprise Linux (RHEL) 6. However, GVP components run at lower capacities on RHEL 6.x, as compared to RHEL 5.x when using ext4. Thus, expect the best performance from GVP while using RHEL 5, or using RHEL 6 with ext3.


Customers using the VP Reporting Plugin for GAX (version 8.5.120.30 or lower) should not upgrade to GAX version 8.5.220.19—this combination has not been qualified.


MCP releases 8.5.130.82, 8.5.130.91, and 8.5.130.93 consume excessive memory during Third Party Recording. Other recording configurations, such as MSML GIR recording, are not impacted. This behavior is scheduled to be corrected in the next release of GVP 8.5.1, scheduled for 9 September 2015.


MCP now correctly interprets the specification RFC2616 and does not revalidate an HTTP response that contains a “must-revalidate” directive until it has become “stale”(expired).

To achieve the previous behavior (revalidate any response that contains a “must-revalidate” directive) with the version 8.5.1 MCP IP (18 December 2015 and later), configure your application servers/web servers to return the following directives with each HTTP response that requires immediate revalidation:

Cache-Control: max-age=0 and must-revalidate


A memory growth issue discovered in Resource Manager 8.5.120.62 was fixed in Resource Manager version 8.5.120.67. Previously, Resource Manager memory grew excessively when connected to SNMP Master Agent.


Correction: The initial IP ReadMe for components incorrectly stated that GVP 8.5.0 supports 32-bit RHEL 6.


All GVP 8.x versions support live upgrades, in-service migration, and mixed modes.


GVP 8.x HTTP Digest Authentication, for the Conversation Manager Solution.


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.


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


Genesys recommends using static IP addresses for all GVP machines running Windows or Linux.


Sometimes while using Genesys Interaction Recording (GIR), you may see a message similar to Recv failure: Connection was reset in MCP logs when you try to post recording files to Amazon S3, and fail. Workaround: Configure the MCP configuration parameter [fm].http_proxy to be empty (containing no value), to disable SQUID/proxy server caching. (GVP-20940)


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. Log out of Genesys Administrator, then log in again as the new user.

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:
127.0.0.1 localhost localdomain.localhost
172.32.45.66 machine1.domain.com machine1

(ER# 218690361)


8.5.176.05

Voice Platform Media Control Platform Release Notes

Release Date Release Type Restrictions AIX Linux Solaris Windows
01/30/17 General X X

Helpful Links

Releases Info


Product Documentation

GVP

Genesys Products

List of Release Notes

What's New

This release contains the following new features and enhancements:

  • Two new configuration options are now available to allow the Media Control Platform (MCP) to perform health check on the media threads.
health.maxprocessingtime
Section: mpc
Valid values: Any positive integer
Default value: 600000
Takes effect: At start/restart
Specifies the maximum processing time (in milliseconds) that a media thread can take to process a media object, exceeding which, the MCP will be terminated. If the option is set to 0, MCP does not perform any processing time check on media threads.
health.waittime
Section: mpc
Valid values: Any positive integer
Default value: 0
Takes effect: At start/restart
Specifies the wait time (in milliseconds) after which the health thread performs the health check on the media threads. If the option is set to 0 (the default), MCP does not perform any health check.
Genesys recommends to configure the health.waittime option only when necessary. Also, note that the value of the health.waittime option must be smaller than the value of the health.maxprocessingtime option.
  • MCP now uses OpenSSL libraries version 1.0.2j. MCP supports these versions of Transport Layer Security (TLS): TLSv1.2, TLSv1.1, and TLSv1; and these versions of Secure Sockets Layer (SSL): SSLv2, SSLv3, and SSLv23.
The following configuration options support the versions of TLS and SSL listed above:
  • sip.transport.<n> type = (default is TLSv1_2)
  • mrcpv2client.sip.transport.<n> type = (default is TLSv1)
  • vrmrecorder.sip.transport.<n> type = (default is TLSv1_2)
  • fm.ssl_version = (default is 0)
Note: Please refer to the 8.5 Product Alerts before upgrading MCP to this version.
  • You can now mask a customer’s sensitive information in MCP log files with asterisks (*) by using a new configuration option mask_sensitive_data in the [log] section. Masking sensitive data using this new option applies only when the MCP logging level is set to trace, debug, or all. This masking capability is not available for the standard or interaction levels of MCP logging, use the gvp:private option in such cases.
mask_sensitive_data
Section: log
Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately
Determines whether a customer’s sensitive information needs to be masked in the MCP log file. This parameter is effective when the logging level is set to trace, debug, or all.
When the mask_sensitive_data parameter is set to true, the following values in the MCP log file are masked and replaced with four asterisks (****) regardless of the length of input information:
  • DTMF and ASR input
  • DTMF and TTS output
  • All HTTP/HTTPS GET/POST data
  • All URL query strings processed in VXML and the fetching modules
  • Expressions or values evaluated during VXML runtime
When the mask_sensitive_data parameter is set to false, a customer’s sensitive information are not replaced with asterisks (*).
Important
A customer’s sensitive data logged at the transport level for protocol requests such as SIP, RTSP, and so on are not masked.
  • MCP now supports uploading the call recordings to S3 servers that need Amazon Web Services (AWS) V4 signature.
Configure the two new parameters record.amazonsignatureversion and record.amazonsignedpayload in the [msml] section that allows MCP to support the AWS V4 signature.
record.amazonsignatureversion
Section: msml
Valid values: V2, V4
Default value: V4
Takes effect: Immediate or session
Specifies the Amazon’s method to generate the authentication signature for GET and PUT requests while uploading the call recordings to S3 servers.
The V4 signature algorithm (the default) requires the bucket location or region information as an authentication criterion. MCP retrieves the bucket or region information using the following methods:
  • Automatic: MCP retrieves the bucket or region information using an Amazon service automatically.
  • Manual: MCP retrieves the bucket or region information from the IVR profile parameters recordingclient.AWSRegion and recordingclient.AWSRegion2 that are manually configured by the user.
record.amazonsignedpayload
Section: msml
Valid values: true, false
Default value: false
Takes effect: Immediate or session
Determines if the payload needs to be signed with the Amazon V4 signature. Applies only when the signature authentication is configured as V4 in the option recordingclient.AWSRegion.
  • When set to false (the default), MCP doesn’t calculate the payload hash.
  • When set to true, MCP calculates the Hash SHA256 of the Amazon POST payloads.



Resolved Issues

This release contains the following resolved issues:


MCP no longer enters into an unresponsive state when the Configuration Server switches from primary to backup or vice-versa. (GVP-23620)


MCP now generates the SNMP traps for non-recoverable errors.

The non-recoverable error occurs in specific scenarios during the post-processing operations of the recording files. (GVP-23592)


When using SIP Secure, the MCP no longer terminates abnormally. Also, the issue of calls getting dropped is now resolved. (GVP-23540)


MCP no longer terminates abnormally when its recorder UserAgent receives the non-REGISTER SIP requests with wrong transports in the VIA header. (GVP-23528)


MCP now correctly uploads the recorded files to the newly created Amazon S3 buckets by enabling a new configuration option enableuploadcontentrewind.

enableuploadcontentrewind
Section: fm
Valid values: 0, 1
Default value: 1

Specifies whether the libcurl resends the uploaded content during PUT requests when the content is redirected.

  • When set to 1 (the default), the libcurl resends the uploaded content to the redirected location.
  • When set to 0, the libcurl doesn't resend the uploaded content to the redirected location. (GVP-23455)



Upgrade Notes

No special procedure is required to upgrade to release 8.5.176.05.

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on March 16, 2017, at 05:08.