why does this setting in the analytics dashboard strip the trunk context from screen recordings routed through our byoc trunks?
we are seeing a discrepancy where the /api/v2/analytics/conversations/details endpoint correctly returns the carrierId and trunk name for voice calls, but the associated screen recording blobs lack this metadata. when exporting recordings via the sdk v2.14.0, the filename only contains the conversationId, making it impossible to correlate the recording with the specific byoc trunk used for the session in our ap-se-2 environment.
this is critical for our compliance audits as we need to verify that calls routed to specific carriers via our 15 byoc trunks are being recorded with the correct retention policies. the sip registration logs confirm the trunk was active, but the recording service seems to be treating all inbound/outbound sessions as generic cloud calls rather than byoc-specific traffic.
has anyone managed to inject custom metadata into the recording storage path or is this a known limitation of the current api version? we need a way to tag these recordings at the source.