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)


New in Release 8.5.1

22 January 2018

Media Control Platform

  • Displays the new Genesys logo for video conference participants who do not provide video input.
  • Introduced two new configuration options, cpa.postconnsilresult and cpa.postconnsilduration, to return a configurable CPA result if a configurable length of silence is detected right after the postconnect event arrives.
  • Supports DNS A/AAAA queries to be internally cached for SIP interfaces.
  • As part of the Cloud requirement, offers custom prompts under the music/on_hold_saas/ folder.
  • Supports OPUS audio codec for RTP transport along with transcoding to and from OPUS. Recording and playback using OPUS are currently not supported.

22 November 2017

T-Server-CUCM to Media Server Connector Release Notes

  • Supports Windows Server 2012 R2 64-bit.
  • Supports TLS1.2 protocol as the transport protocol for SIP over TLS.

See the T-Server-CUCM to Media Server Connector 8.5.184.06 Release Note for important information about other improvements and issues resolved with this release.

MRCP Proxy

  • Supports TLS 1.2 for a secure connection to the Configuration Server and the GVP Reporting Server.
  • MRCP Proxy can now run on the Microsoft Windows Server 2012 operating system.

See the MRCP Proxy 8.5.184.42 Release Note for important information about other improvements and issues resolved with this release.

Reporting Server

  • Supports connections to SQL Server AlwaysOn Availability Groups for SQL Server 2012, 2014, and 2016.

See the Reporting Server 8.5.181.77 Release Note.

15 September 2017

Reporting Server

  • Supports CentOS Linux 7.
  • Supports Red Hat Enterprise Linux 7.0.
  • Supports JRE Version 8.

See the Reporting Server 8.5.181.77 Release Note.

07 September 2017

Media Control Platform

  • A new Media Control Platform (MCP) configuration option cpa.no_ring_result specifies the call progress analysis (CPA) result if no ringback is detected before the postconnect event arrives for important information about other improvements and issues resolved with this release.
  • MCP now supports a new codec library for media processing. The legacy codec continues to be available and is set as the default option.

See the Media Control Platform 8.5.181.78 Release Note.

24 May 2017

Media Control Platform

  • Media Control Platform (MCP) now supports two new security parameters (swirec.secure_context and swirec.mute_wcr) specific to Nuance Server (version 10.2 and above).

See the Media Control Platform 8.5.178.78 Release Note.

Reporting Server

  • Reporting Server 8.5.130.86 and above versions support Oracle 12c and Oracle 12c RAC database versions.

See the Reporting Server 8.5.130.86 Release Note.

15 May 2017

Resource Manager

  • Resource Manager (RM) no longer accepts calls when the weight parameter of a site is set to zero in the corresponding gvp.site folder.
  • A new configuration option optionsofflineresp is available to configure SIP OPTIONS response codes that RM checks while marking a resource offline.

See the Resource Manager 8.5.178.66 Release Note.

30 January 2017

Media Control Platform

  • MCP now uses OpenSSL libraries version 1.0.2j. Note: Refer to the 8.5 Product Alerts before upgrading MCP to the latest version.
  • Masking of a customer's sensitive information (DTMF) in MCP log files is possible now, by configuring a new option.
  • MCP now supports uploading the call recordings to S3 servers that need Amazon Web Services (AWS) V4 signature.
  • Two new configuration options are now available that allows MCP to perform health check on the media threads.

See the Media Control Platform 8.5.176.05 Release Note.

Resource Manager

  • RM now uses OpenSSL libraries version 1.0.2j. Note: Refer to the 8.5 Product Alerts before upgrading RM to the latest version.
  • A new configuration option is now available in RM to override the policy setting for IVR recording.

See the Resource Manager 8.5.175.95 Release Note.

Reporting Server

  • Microsoft SQL Server 2005 support is discontinued as of 31 December 2016.

See the Reporting Server Release Note.


27 September 2016

Media Control Platform

  • MCP supports TCP keep-alive functionality. Manage Keep Alive functionality with MCP configuration options.
  • To support IVR Recording, MCP honors these recording Request URI parameters when executing VoiceXML applications: start, stop, pause, and resume.
  • MCP supports pass-through when caller and agent are using the same codecs and GIR recording is enabled.

See the Media Control Platform 8.5.170.71 Release Note.

Resource Manager

  • RM enables VXML IVR Recording, in a way similar to MSML GIR recording, with the configuration optiongvp.policy.voicexml-recording-allowed.
  • RM supports the service-type record in an IVR Profile. RM locates and selects the appropriate record IVR profile.
  • RM supports geo-location based selection of the record IVR profile, configured by the gvp.general.geo-location option in the IVR profile.

See the Resource Manager 8.5.170.64 Release Note.


16 June 2016

  • GIR call recording can now continue even if the public key recording certificate has expired.
  • Now you can use the option curlredirect to control how HTTP redirects are handled, so that HTTP redirection can function properly.
  • Genesys Media Server supports the CentOS Linux 7 operating system.
  • Genesys Media Server supports the Red Hat Enterprise Linux (RHEL) 7 operating system.
  • Genesys Media Server supports Apple's HTTP Live streaming (draft-pantos-http-live-streaming-16) subset of features. Media Server can now play media and master playlists of the type On-Demand, Event and Live.

See the Media Control Platform 8.5.161.34 Release Note.

  • Resource Manager supports the CentOS Linux 7 operating system.
  • Resource Manager supports the Red Hat Enterprise Linux (RHEL) 7 operating system.

See the Resource Manager 8.5.160.74 Release Note.


05 February 2016

  • Users can now use the GVP Reporting plugin for GAX to provision IVR profiles and manage DID groups for IVR profiles. See the GVP Reporting plugin for GAX Release Note.

  • Note: In large-scale deployments of GVP (with 10,000+ DIDs), users may experience up to 15-20 seconds response times when editing or saving DIDs in a DID group, through the GVP Reporting plug-in for GAX.

  • Tenant Administrators can now provision DIDs to DID Group mapping.

  • Note: DID group provisioning succeeds when you remove the conflicting entries in overlapping ranges (example: 100-200 and 150-250).

  • Backend filtering no longer removes the call record from a report when you use an IVR profile or Tenant or component in the filter. Instead, certain filtering rules apply. See the GVP Reporting plug-in for GAX Release Note.
  • Resource Manager (RM) has three new configuration options in the CTI Connector (CTIC) Logical Resource Group (LRG) for handling CTIC failover. See the Resource Manager Release Note.
  • The TCP setup timer is now configurable. See the Resource Manager Release Note.
  • MRCP Proxy supports provisioning MRCP resources with the same URI, if the resource names or types are different.


January 2016

  • MCP uses the SpiderMonkey 1.7 engine to perform ECMAScript (JavaScript) processing. SpiderMonkey 1.7 supports ECMA-262 3rd edition.


15 December 2015

  • The Sip.Body value in the [vxmli] session_vars configuration option enables access to the body of SIP INVITE messages. See the MCP Release Note.
  • Use the configuration parameter [callmgr] enable_sip_response_in_transfer_metric to configure Media Control Platform to append the SIP response code (when it is available) to transfer_result metrics. See the MCP Release Note.
  • TCP Timer Setup—You can configure the wait time to keep a needed resource available, when waiting to establish a TCP or TLS connection. See the MCP Release Note.


16 November 2015

  • You can use the GVP Reporting plugin for GAX to "self-service" provision IVR profiles, Map individual DIDs to DID groups, and Map DID Groups to IVR profiles. Read complete details here.


28 August 2015

  • The Supplementary Services Gateway now supports including custom HTTP response headers in the HTTP responses to HTTP requests. Enable this behavior with the [http]ResponseHeaders configuration parameter. Enter the value in this format: Header1:Value1|Header2:Value2 Notes:
    • If your value includes the characters |/ or :, precede them with a backslash (\| or \:).
    • The default value for this parameter will be set to X-Frame-Options:DENY—part of Genesys software defense against “clickjacking”.
    • This behavior also applies to accessing the SSG root page.
  • The Media Control Platform supports DTMF Masking while agent and caller are in conference with IVR. See Managing DTMF Clamping in MSML Recordings.
  • Now you can configure the duration of the MP3 recording buffer. Use the option [mpc] mediamgr.recordmp3audiobuffer (in the MCP application) to specify the duration of the audio buffer for MP3 recording, in milliseconds.
    mediamgr.recordmp3audiobuffer must be an integer 2000 or greater; the default is 4000.
    Any change takes effect at start/restart.
  • The Media Control Platform's NGI VXML interpreter supports caching of JavaScript (JS) content, which improves performance.
  • The Media Control Platform supports mp3 compression at 8 kbps for mono recording. Set the option [mpc] mp3.bitrate=8 to enable 8 kbps mono recording. The default compression remains 16 kbps.
  • The Media Control Platform supports mono-channel recording during MSML GIR recording for all file formats.
    • Use the parameters (both in the gvp.service-paramaters section of the IVR profile record) to specify the channel information:
      Both options recordingclient.channels=fixed and recordingclient.channels2=fixed can have the possible value 1(mono) or 2(stereo, the default).
      If a parameter is missing from the IVR profile configuration, then MCP uses the configuration parameters msml.record.channels and msml.record.channels2 (which specify the number of channels that MCP must use for MSML recording to dest2). These two have the same possible values (1=mono and 2=stereo, the default).
      Any change takes effect immediately.
    • Use the configuration option [msml]record.amazonallowpublicaccess to enable public download access to an MSML recording file that was uploaded to Amazon s3. Set to true to enable access to the uploaded recording file, and to false (the default) to disable access.
      This option will grant access to both the primary recording destination (recdest) and the secondary recording destination (recdest2), if you configure both destinations to use the s3 URI format (s3:bucketname).
      Any change takes effect at start/restart.


23 March 2015

  • The Media Server function Call Progress Detection (CPD) now performs voice print analysis and beep analysis to identify the specific preconnect carrier messages that occur in different countries.
    1. Media Server's configurable database of preconnect tones is initiated during installation and loaded when Media Server starts. You can update the database with different carrier messages at any time, without stopping Media Control Platform.
    2. Other features include the ability to leave postconnection messages such as voicemail.
    3. Some new VoicePrint Configuration Options support this functionality.
  • The Reporting Server (RS) adds support for Windows 2012 64-bit and MS SQL Server 2012, in native 64-bit mode using the 64-bit version of the Java Virtual Machine. RS also adds support for Standard and Enterprise editions of the SQL Server 2012 database.
  • Resource Manager can now be configured to reject a call request if the geo-location of the targeted Logical Resource Group (LRG) does not match the geo-location attribute of the call request. This extends to all calls, a behavior that previously applied only to recording solution calls. Read about this behavior and the option that controls it, reject-on-geo-location-nomatch (new in release 8.5.1), in Locating Resources Using Geo-Location.


18 December 2014

  • GVP added support for Genesys Interactive Recording (GIR):
    • Media Control Platform added two new mp3 encoding compressions—16kbps (new default) and 24kbps—to the existing configuration option [mpc]mp3.bitrate.
  • VP Reporting Plugin for GAX added new support and compatibility requirements:
    • Added support for Management Framework 8.5 and Genesys Administrator Extension 8.5.
    • Added support for Windows Server 2012 R2 64-bit.
    • The plugin now requires GAX 8.5.0; support for GAX 8.1.4 is discontinued.
    • VP Reporting Plugin for GAX Help is now online.
  • Management Information Base (MIB) added support for Windows Server 2012 R2 64-bit.


19 September 2014

  • Support for Windows Server 2012 R2 64-bit.


15 July 2014

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)


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)


What's New in Genesys Media Server for 9.0

For full information about supported operating systems, databases, browsers, and virtualization platforms, refer to the GVP page of the Genesys Supported Operating Environment Reference Guide.

October 11, 2018

Media Control Platform

  • Supports Windows Server 2016 Standard edition.
  • Provides file integrity using checksum computation. The checksum is calculated using the SHA256 algorithm while the files are being recorded. The checksum is accessible only if MCP is integrated with the Genesys Interactive Recording (GIR) service.

See the Media Control Platform 9.0.013.61 Release Note for information about new features and issues resolved in this release.

Resource Manager

  • Supports Windows Server 2016 Standard edition.
  • Supports TLS connectivity for inter-node communication in Active-Active and Active-Standby configurations.

See the Resource Manager 9.0.013.55 Release Note for information about new features and issues resolved in this release.

Call Control Platform (CCP)

  • Supports Windows Server 2016 Standard edition.
  • Uses OpenSSL libraries version 1.0.2j.
  • Supports the TLSv1, TLSv1.1, and TLSv1.2 versions of TLS.
  • Supports the SSLv2, SSLv3, and SSLv23 versions of SSL.

See the Call Control Platform 9.0.013.03 Release Note for information about new features and issues resolved in this release.

Supplementary Services Gateway

  • Supports Windows Server 2016 Standard edition.

See the Supplementary Services Gateway 9.0.013.16 Release Note for information about new features and issues resolved in this release.

Reporting Plugin for GAX

  • Supports Windows Server 2016 Standard edition.
  • Displays VAR Action Reason values.

See the Reporting Plugin for GAX 9.0.013.74 Release Note for information about new features in this release.

MRCP Proxy

  • Support Windows Server 2016 Standard edition.

See the MRCP Proxy 9.0.013.55 Release Note for information about the new feature in this release.

Reporting Server

  • Supports Windows Server 2016 Standard edition.

See the Reporting Server 9.0.013.36 Release Note for information about the new feature in this release.

CTI Connector (CTIC)

  • Supports Windows Server 2016 Standard edition.

See the CTIC 9.0.013.14 Release Note for information about the new feature in this release.

T-Server-CUCM to Media Server Connector

  • Supports Windows Server 2016 Standard edition.

See the T-Server-CUCM to Media Server Connector 9.0.013.04 Release Note for information about the new feature in this release.

July 10, 2018

Media Control Platform

MCP now supports mutual TLS authentication by using TLS 1.2 with Reporting Server (RS).

See the Media Control Platform 9.0.010.72 Release Note for information about new features and issues resolved in this release.

Resource Manager

RM now supports mutual TLS authentication by using TLS 1.2 with Reporting Server (RS).

See the Resource Manager 9.0.010.68 Release Note for information about new features and issues resolved in this release.

June 26, 2018

Reporting Server

  • Supports TLS 1.2 for connection with:
    • Configuration Server
    • Message Server
    • Databases:
      • SQL Server
      • Oracle
  • Supports an updated JDBC driver for Oracle to version 12.2.0.1.

See the Reporting Server 9.0.010.62 Release Note for information about new features in this release.

Reporting Plugin for GAX

Connects with Reporting Server by using the TLS 1.2 HTTPS interface.

See the Reporting Plugin for GAX 9.0.010.06 Release Note for information about the new feature in this release.

June 01, 2018

CTI Connector

TLS 1.2 support added for the following interfaces:

  • Resource Manager
  • Message Server
  • Configuration Server
  • IVR Server

See the CTI Connector 9.0.010.07 Release Note for information about issues resolved with this release.

April 18, 2018

This release does not include any new feature.

See the Media Control Platform 9.0.000.52 Release Note and Resource Manager 9.0.000.49 Release Note for information about issues resolved with this release.

Genesys Media Server

[+] What is GMS?

What's New

Genesys Media Server is part of 9.0, which can include component releases from both 9.0.x and 8.5.x code streams. Use the table below to check which component releases are part of 9.0.

All 9.0 products 9.0 Genesys Media Server Release Notes
Product Component Latest Starting

Genesys Media Server

T-Server-CUCM to Media Server Connector

9.0.013.04

9.0.013.04

Voice Platform Media Control Platform

9.0.013.61

9.0.000.52

Voice Platform Reporting Server

9.0.013.36

9.0.010.62

Voice Platform Resource Manager

9.0.013.55

9.0.000.49

VP Reporting Plugin for GAX

9.0.013.74

9.0.010.06


Documentation

Genesys Media Server 8.5 Documentation Supplement

Corrections and Additions to the Media Server (and GVP) documentation set for 8.5 and 9.0 releases.

Genesys Media Server 8.5 Deployment Guide

Use this guide to install and configure Genesys Media Server for 8.5 and 9.0 releases.


Supported SIP Devices

Read about supported SIP phones and gateways.

Genesys Media Server (and GVP) 9.0 Release Information

Click below to see New in This Release and Readme information for 9.0 releases.

[+] Show release information

What's New

Release Notes

Documentation

Genesys Media Server 8.5 Documentation Supplement

Corrections and Additions to the Media Server (and GVP) documentation set.

Genesys Media Server 8.5 Deployment Guide

Use this guide to install and configure Genesys Media Server.


Supported SIP Devices

Read about supported SIP phones and gateways.

Genesys Media Server (and GVP) 8.5 Release Information

Click below to see New in This Release, Readme, and Product Alerts information for 8.5 releases.

[+] Show release information

Release Notes

Documentation

Genesys Media Server 8.1 Documentation Supplement

Corrections and Additions to the GVP/Media Server documentation set.

Genesys Media Server 8.1 Deployment Guide

Use this guide to install and configure Genesys Media Server.

Genesys Media Server Configuration Options Reference

A complete list with descriptions and parameters.

Readme and Advisory

Media Server did not exist as a standalone product in Genesys 8.0.
Please see the Genesys Voice Platform 8.0 documentation for more information about Media Server.

This page was last modified on October 22, 2018, at 07:35.