Anyone know why the bulk export job fails immediately when filtering by specific SIP trunk headers for legal discovery?
We are attempting to export voice recordings and associated call detail records (CDR) for a specific date range. The goal is to maintain chain of custody for interactions routed via our primary SIP trunk. The environment is Genesys Cloud EU-West-1. We use Python SDK 2.14.0.
The job creation endpoint POST /api/v2/recordings/bulkexport/jobs returns a 400 Bad Request. The error message indicates an issue with the callDetail filter configuration. Specifically, when we include sip_trunk_id in the filter payload, the validation fails.
{
"message": "Invalid filter value for field 'sip_trunk_id'. Expected string, got null.",
"code": "bad_request"
}
The sip_trunk_id is definitely present in the interaction metadata. We verified this via the Interaction Search API. The ID format matches the UUID structure required. Is there a limitation on filtering voice recordings by SIP trunk attributes in the bulk export API? Or is this a known issue with the SDK serialization of complex filter objects?
We need this export for a legal hold request. Any insight into the correct payload structure for voice recording filters would be appreciated.