Voice Platform Resource Manager Release Notes
|Release Date||Release Type||Restrictions||AIX||Linux||Solaris||Windows|
This release includes only resolved issues.
This release contains the following resolved issues:
RM now checks the SIP transaction state when timer B fires, and abandons/cancels the transaction only if the SIP Transaction state is CALLING. (GVP-24113)
RM no longer runs into the race condition at the transport layer which resulted in call leg rejections. Previously, some recordings were lost due to RM returning 500 and 408 timeout responses. (GVP-24043)
RM now supports resource monitoring. RM does not declare a resource offline unless the pinging by RM through SIP OPTIONS fails because it has reached the counter’s maximum limit. In this scenario, RM defaults to 1, that is, RM on not receiving a response for the SIP OPTIONS, declares the resource offline immediately. (GVP-24039)
RM no longer routes delayed responses back to the INVITE transaction after the transaction is timed out. Previously, when the INVITE transaction timed out, RM routed the request to the next available Media Control Platform (MCP) from its list. If the first MCP responded, RM routed it back to the SIP Server statelessly, thereby establishing a SIP dialog with the first MCP and causing record failures. (GVP-23999)
RM now prints the MCP resource ID (IP address) instead of MCP AOR when it performs resource matching before bypassing MCP resources. Previously, if MCP was configured with SIPS AOR, then RM did not print the matched MCP's IP address in logs. (GVP-23938)
RM now bypasses MCP resources that are specified in the userpart@<ip>:<port> format in the X-Genesys-bypass-resource-list header. (GVP-23937)
RM now reverts to the weight value 100 (default) for a site whose weight is specified with special/invalid characters. Previously, RM calculated weight incorrectly when the gvp.site.weight parameter contained special characters. (GVP-23892)
RM no longer terminates abnormally with a race condition when the following conditions apply:
- It is in active-standby configuration.
- It has just been declared either primary or secondary.
- It is sending inter-node data to the other RM node.
- LAN recovery happens at the time when inter-node data is being sent to the other RM node. (GVP-23870)
No special procedure is required to upgrade to release 18.104.22.168.