Jump to: navigation, search

Known Issues and Recommendations

Recording Muxer Script

The Known Issues and Recommendations section is a cumulative list for all 8.5.x releases of Recording Muxer Script. 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 Resolved Issues section for each release describes the corrections and may list additional issues that were corrected without first being documented as Known Issues.

The default parameter of the split_window_enabled option is not producing the intended default behavior and Muxer may fail to mux recordings.

Workaround: Set call_recording_extra_query_string to userData=SRSScreenRecordingStateStarted .

ID: GIR-26090 Found In: Fixed In:

If MCP has failed to post a recording to the Recording Processor Script (RPS), and the recording is recovered by the LVR Recovery Script, the resulting muxed file may have duplicate screen recordings that are muxed together.

The root cause of this error is, MCP does not write the correct stop time if it cannot post the recording to RPS and LVR Recovery Script will not attempt to update the stop time during recovery. Due to this, the resulting recording contains the same start and stop time and Muxer appends the padded video because the difference in call recording stop time and video recording stop time is less than 0.

ID: GIR-15662 Found In: Fixed In:

If the environment variable REQUESTS_CA_BUNDLE is specified, the Recording Muxer Script will validate the certificate used for a TLS connection even if the trusted_ca parameter is set to false. This applies to the TLS connections to Interaction Recording Web Services (RWS), Recording Crypto Server (RCS), and WebDAV.

Workaround: If TLS validation is to be disabled, ensure that the REQUESTS_CA_BUNDLE environment variable is not set in addition to setting the appropriate trusted_ca parameter to false.

ID: GIR-13861 Found In: Fixed In: 

If a call recording is marked with the non-deletion label and there is a corresponding screen recording, then the muxed screen recording does not contain the non-deletion label—and is not protected from deletion.

ID: GIR-11061 Found In: Fixed In:

The Recording Muxer Script sleeps unnecessarily in the following scenario: when using the bulk API to query a recording and there is no screen recording being processed.

ID: GIR-10196 Found In: Fixed In:

If the RWS has CSRF enabled, the Recording Muxer Script might not work properly due to handling the CSRF token.

Workaround: Disable CSRF on the RWS side.

ID: GIR-6538 Found In: Fixed In: 

If Voice Recording is not encrypted and Screen Recording is encrypted, the Muxed Recording will not be encrypted after it is processed by the Recording Muxer Script.

Workaround: Configure the encryption setting for both Voice Recording and Screen Recording, to ensure that the Muxed Recording is encrypted.

ID: GIR-5764 Found In: Fixed In: 

Muxer might leave over files when the media is processed. This will cause the disk usage to accumulate after it runs for a long period.

Workaround: Set up an alarming script to monitor the free disk space.

ID: GIR-5764 Found In: Fixed In: 

The Recording Muxer Script repeatedly processes a failed recording that is more than 200 MB in the following scenario:

  1. Encryption is enabled.
  2. The video_padding_slice_length_ms option is set to a value less than 1000.
  3. The screen recording starts later or ends earlier than voice recording by more than 20 minutes.

Workaround: Set the video_padding_slice_length_ms option to 5000.

ID: GIR-2386 Found In: Fixed In:

The Recording Muxer Script's sample configuration contains inaccurate information for the video_padding_slice_length_ms option. The default value should be 5000 instead of 1000. And the description is incorrect, this parameter is used to append video if it stops earlier than voice.

ID: GIR-2319 Found In: Fixed In:

HTTP requests made to Web Services and Applications fail due to incorrect cookie handling.

ID: GIR-3344 Found In: Fixed In:

Internationalization Issues

Information in this section is included for international customers.

There are no internationalization issues for this product.

This page was last edited on October 19, 2020, at 12:46.
Comments or questions about this documentation? Contact us for support!