Jump to: navigation, search

9.0.035.04

Voice Platform MRCP Proxy Release Notes


Voice Platform MRCP Proxy is part of 9.x starting in 9.0.013.55.
Release Date Release Type Restrictions AIX Linux Solaris Windows
06/26/20 General X X


Helpful Links


What's New

This release contains the following new features and enhancements:

  • MRCP Proxy now supports Red Hat Enterprise Linux (RHEL) 7. See the Genesys Media Server page in the Genesys Supported Operating Environment Reference Guide for more detailed information and a list of all supported operating systems. (GVP-40960)
  • MRCP Proxy triggers a new trap for connect failures. (GVP-41536)
  • A new parameter, ping_alarm_threshold, is introduced to enable MRCP Proxy trigger a new trap when the configured alarm threshold for continuous ping failures is reached for a resource. (GVP-41475)
  • MRCP Proxy does the following in relation to resource pool:
    • Checks the availability of resources periodically (with the default value of 30 seconds) and a new SNMP trap is triggered when the configured unavailable resource alarm threshold (with a default value of 30%) is reached. This is enabled by a new parameter, resource_alarm_threshold.
    • Provides a SNMP scalar table to present the total/available numbers of recognizer and synthesizers respectively. The SNMP scalar table can be queried like any other SNMP scalar tables through tools like snmpget or MIB browser.
    • Disconnects a resource when the ping timeout occurs if the option vrmproxy.disconnect_ping_timeout is set to true (enabled by default). MRCP Proxy will automatically try reconnecting to any resource that is disconnected. A new parameter, timeout.check_avail_res, is introduced to check the available resources. If the unavailable resource alarm threshold is reached, an alarm will be raised. (GVP-41299)


Resolved Issues

This release contains no resolved issues.


Upgrade Notes

No special procedure is required to upgrade to release 9.0.035.04.

This page was last edited on June 26, 2020, at 13:41.
Comments or questions about this documentation? Contact us for support!