Release Summary

This is a major release of the solution, this release supports UCCX and MSSQL.

New Features

MSSQL support is also available in this version of VRS. This release is tested with MSSQL server 2016.

In this release, the solution supports the UCCX support.
This release is tested with UCCX 12.0.

Issue	Summary
Core-recorder got stuck and no recordings	There was an issue reported by a customer about the core recorder service. It used to get stuck after running for several days. No calls were recorded. Fixed in this release

Following scenarios are not handled in VRS

Issue	Summary	Alternative
The row size for the call having multiple legs on front-end is not equal to call having a single leg.	The records are appearing on VRS front-end, the row size is not equal for all calls only in firefox. It appears equal and perfect in Google Chrome.
Voice Recording Solution unable to fetch the Agent's info for the conference call leg.	Currently, when an agent made a conference call, the system is unable to get the agent's info for the conference leg.
On login from front-end, an error appears on the screen	On login, the front-end shows the error of invalid credentials, but it login the admin at the same time.
When an outbound call is made the called number is assigned as calling number, which can be seen from API response.	For outbound calls, called number is appearing against the calling number.

Following are the limitations of the solution

Summary	Description
Licensing utility not integrated with VRS Front-end	The UMM (User Management Module) is not integrated with the Voice Recording Solution. Hence there will be only one user as the user creation for VRS frontend is not available currently.
Hold duration of the call is configurable, which can cost a call to the system	Currently, we are getting the same BYE event for the Hold and End call and the application can't differentiate if a call is gone on hold or it is ended. The application waits for a configurable amount of time and if within the time another event is received for the same call then it means that the call was on hold and now it is resumed and it is co-related to the same call as another leg. If no event is received then the call is closed with one leg. This means that if a call is On-hold for more than the configurable time then the second leg of the call is treated as a separate call. This also affects the ended calls as they are put on wait for no reason.
Currently, the solution is handling the single codec	The Voice recording solution is not supporting multiple codex. It is only handling the G711 codec.