Quick question about a discrepancy we are seeing with WebRTC softphone recordings in our legal discovery bulk exports. We are processing a high-volume batch of digital channel interactions, specifically focusing on WebRTC sessions initiated via the Genesys Cloud softphone client. The bulk export job completes successfully, but the resulting JSON payloads lack critical metadata fields required for chain of custody verification.
Specifically, the recording_metadata object is missing the webrtc_session_id and client_ip_address fields for approximately 15% of the exported WebRTC recordings. This is problematic for our legal hold procedures, as we need to verify the exact endpoint origin for compliance audits. The remaining 85% of the records include this data correctly.
We are using the /api/v2/recording/bulkexports endpoint with the metadata parameter set to all. The environment is Genesys Cloud EU (London), and we are on the 2024-06 API version. Here is a snippet of the problematic payload:
{
"recording_id": "abc-123-def",
"media_type": "audio",
"start_time": "2024-05-10T14:23:00.000Z",
"recording_metadata": {
"channel_type": "webrtc",
"participant_ids": ["user-123", "user-456"],
"webrtc_session_id": null,
"client_ip_address": null
}
}
The audit trail in the admin console shows these recordings were created successfully, and the webrtc_session_id is visible in the individual recording detail view. However, it is consistently null in the bulk export JSON. This pattern seems to correlate with recordings that had a duration of less than 30 seconds, though not exclusively.
Is this a known limitation with how WebRTC metadata is batched for export? Or should we be using a different API endpoint to ensure complete metadata retrieval for short-duration WebRTC calls? We need a reliable method to capture this data for legal discovery without manually fetching each recording, which is not scalable for our current case volume.