Voice Platform Resource Manager Release Notes
|Release Date||Release Type||Restrictions||AIX||Linux||Solaris||Windows|
This release contains the following new features and enhancements:
- You can now direct Resource Manager to not reapply RURI capability when falling back to VXML after CTIC returns a 404 error. Previously, reapplying RURI capability caused the fallback to fail.
Use a new configuration option in the Gateway LRG section in order to achieve this functionality:
Section: Gateway Resource group section
Valid Values: true or false (default)
Set to true to disable Resource Manager's use of the gvp.rm.resource-req option's capability during VXML fallback after a CTIC 404 error.
Set to false, to enable Resource Manager's use of the gvp.rm.resource-req.
Note: This option is NOT available during configuration of a Gateway Resource Group via Genesys Administrator. Specify this parameter manually in the Gateway Logical Resource Group (GW LRG) section, using the format remove-ruri-capability-on-fallback = true (or = false).
- Resource Manager now supports dynamic updating of a child tenant name change.
This release contains the following resolved issues:
The Resource Manager thread no longer freezes due to an internal error when RM retries an INVITE with a different MCP target. (GVP-22561)
The Resource Manager no longer terminates unexpectedly when it encounters a socket error while sending the response to a SIP message that has no branch in the via header. (GVP-22293)
The Resource Manager now correctly calculates usage-limits even when the gvp.site weight property for the RM site is empty or set to 0. (GVP-22222)
When falling back to VXML after CTIC returns a 404 error message, Resource Manager no longer uses the capability specified in the cti-capability-requirement option to select a VXML resource. (GVP-22221)
[ems]rc.certificate is now a default parameter of the Resource Manager application template (GVP_RM.tpl). This parameter identifies the TLS Certificate for Reporting Client. The TLS Certificate file name is required to be in PEM format, for connection to the Reporting server (ActiveMQ) over TLS. (GVP-22191)
Resource Managers that are configured in a high availability pair no longer stop unexpectedly because a socket in a race condition closed while one of them was sending data. (GVP-22163)
When in a high availability configuration, the Resource Manager node now reports the status of SIP, and the status of SIPS AOR of a physical resource, separately to the other RM node. (GVP-21068)
The Resource Manager (RM) MIB data (which is stored in a scalar table) for an active-active deployment mode now reflects the correct call statistics when RM is run in a high availability active-active configuration. (GVP-20257)
No special procedure is required to upgrade to release 188.8.131.52.