System Limitations
Following are the limitations of the features in the release:
Archival Service
Summary | Description |
---|---|
Manual Controls | Calls cannot be manually deleted, Archived recordings cannot be retrieved and Manual archiving of calls is not supported. |
Outbound EFCX Recordings | Recordings of Outbound EFCX Calls can’t be Archived |
Rsync and Archival Service clash | If the Archival Service retention period is set shorter than the housekeeping job interval, conflicts may occur between Archival Service and Rsync. Always ensure that the housekeeping retention period is shorter than the Archival Interval. |
Audit Logs
Summary | Description |
---|---|
Export and Retention Policies Not Supported | Audit logs cannot be exported for external analysis or reporting and Retention policies for managing the lifecycle of audit logs are not currently supported. |
Search/Filter Recordings Not Logged | Filtering or searching for recordings is not captured in the Audit Logs and will not appear on the Audit Logs page. |
High Availability
Summary | Description |
---|---|
Container/Component Level Failover | VRS High Availability does not support container-level failover. As a result, if a component on one server experiences downtime, the corresponding component on another server will not be notified of the downtime. |
Same Subnet | VRS Servers must Reside on the Same Subnet for High Availability Mode. |
Hostname Requirement | Hostnames of both VRS servers running in High Availability (HA) mode must be unique. If they are identical, HashiCorp Consul will not function correctly, preventing it from locking one of the JTAPI connectors to process call events. |
Failover during call | Failover during an ongoing call is not supported. Therefore, if the server goes down during a call, the recording will not be saved in the system. |
No Backup of Replay Server | The current architecture does not support High Availability (HA) for the Replay Server. If the Replay Server remains unavailable for a long time, recorders may experience storage overflow, which can lead to unexpected system behavior. |
Recorder and Mixer Binding | The Recorder and Mixer components do not support High Availability. If the Recorder is capturing audio and its assigned Mixer fails, the other VRS Server’s Mixer cannot take over. |
Rsync Logs | Currently, if the Replay Server goes down during the rsync process, the transfer status may not be accurately reflected in the rsync logs, preventing precise tracking of successfully transferred recordings. |
Pause and Resume Recording
Summary | Description |
---|---|
No UI | The Pause and Resume recording functionality does not have a user interface. No buttons are available for this feature. It can only be controlled through Endpoints/APIs. |
Nonsupport with HA | Pause and Resume recording functionality is not supported in the High Availability (HA) solution. If primary server goes down, the feature will not work on the secondary server. |
Outbound EFCX Calls | For outbound calls in EFCX, the API requires the agent's extension instead of the customer's number to pause and resume call recording. |
Screen Recording
Summary | Description |
---|---|
Operating System Compatibility | Screen Recorder is only compatible with Windows. Other operating systems are not supported. |
Low FPS | To optimize performance and manage storage, the recorder captures the screen at a lower FPS, which prevents Full HD (FHD) recording quality |
Lag on a streaming video | The recorder is not designed to capture dynamic content, such as ongoing videos or moving objects. As a result, it may not properly record video playback from platforms like YouTube. |
Startup Time After Shutdown | The recorder requires approximately 6 to 7 minutes to initialize after the computer is powered on following a shutdown. |
Incompatibility with EFCX | The screen recording feature is only compatible with Cisco and is not supported with EFCX. |
Single-leg Calls Only | This feature is only supported for single-leg calls, including normal inbound and outbound calls. It doesn’t support Direct/Consult Transfer, Consult and Consult Conference calls. |
Firefox Incompatibility | Screen Recording Video streaming is not supported on Firefox Browser. |
Single Active User | For the recorder to function properly, only one user account should be signed in on Windows at a time. Other user accounts must be signed out. Switching between user accounts will prevent the recorder from working. For example, if an admin user is signed in, a non-admin user will not be able to use the screen recording feature until the admin user signs out. |
Recording Encryption
Summary | Description |
---|---|
No Streams Encryption | Only mixed audio call recordings are encrypted in the system. Streams are not encrypted. |