Known Issues and Recommendations
Voice Platform Resource Manager
The Known Issues and Recommendations section is a cumulative list for all 8.5.x releases of Voice Platform Resource Manager. This section provides the latest information on known issues and recommendations associated with this product. It includes information on when individual items were found and, if applicable, corrected. The Corrections and Modifications section for each release may list additional issues that were corrected without first being documented as Known Issues.
See also: Internationalization Issues
In Resource Manager HA (Active-Active) configuration, RM sometimes might not shutdown properly when the graceful shutdown is triggered while there are some active calls.
| ID: GVP-21576 | Found In: 8.5.110.03 | Fixed In: |
Resource Manager may terminate if it encounters issues around establishing a TLS connection, when the Media Control Platform contact is configured as DNS SRV.
| ID: GVP-21518 | Found In: 8.5.101.16 | Fixed In: |
Resource Manager might crash on shutdown if there are active calls during shutdown.
| ID: GVP-21516 | Found In: 8.5.101.16 | Fixed In: |
Resource Manager, in an active-active or active-standby HA deployment, no longer terminates in a race condition when a CANCEL from SIP Server and responses for INVITE from the resources managed by RM occur at the same time.
| ID: GVP-21484 | Found In: 8.1.700.68 | Fixed In: |
A bridge transfer will fail if the DNS SRV is used as the Media Control Platform contact.
| ID: GVP-21240 | Found In: 8.5.050.34 | Fixed In: |
When in a high availability active-active configuration, Resource Manager may terminate upon receiving a conference call, if both nodes in the configuration use the same hardware address.
| ID: GVP-21065 | Found In: 8.1.700.71 | Fixed In: 8.5.130.58 |
The Resource Manager (RM) MIB data (stored in a scalar table) may not reflect the correct number when RM is run in a high availability active-active configuration.
| ID: GVP-20257 | Found In: 8.1.7 | Fixed In: |
A Resource Manager in a high availability active-active configuration may respond to OPTIONS pings with a 503 error for a brief period of time when a node with higher priority comes online. As a result, calls are not directed to that RM during that brief period of time.
| ID: GVP-19668 | Found In: 8.1.700.21 | Fixed In: |
Resource Manager does not support key name values that are expressed in UPPER CASE LETTERS in OPM parameters. Workaround: When you use a key name in an OPM parameter value, use only lower case letters.
| ID: GVP-18808 | Found In: 8.1.601.10 | Fixed In: |
Internationalization Issues
Information in this section is included for international customers.
There are no internationalization issues for this product.