Is it possible to strip specific SIP header metadata from our audit logs during bulk compliance exports? We are managing 15 BYOC trunks across APAC regions, and the current export pipeline includes raw Via and Contact headers that expose internal carrier routing IPs. This creates a conflict with our data residency policies in Asia/Singapore. When querying the GET /api/v2/analytics/details endpoint, the response payload includes these headers in the call_leg object. We attempted to mask them via Architect flow variables, but the analytics service seems to pull directly from the underlying SIP transaction records before our flow logic applies. The environment runs on Genesys Cloud v2.0 with BYOC trunks configured for SIP-T interoperability. The specific error is not a system failure but a compliance audit finding. We need the call detail records (CDRs) for reporting but must exclude the carrier-specific SIP footprint. Has anyone successfully implemented a pre-export sanitization rule or found a configuration flag in the trunk profile that suppresses this header inclusion? The current workaround of post-processing the CSV exports is unsustainable for our volume.