Why does this setting in the Architect flow fail to propagate to the WebRTC softphone recordings during bulk export? We use the Architect Export Job registration for legal discovery. The SIP trunks show the correct legal_hold flag, but the WebRTC JSON files omit it entirely. The S3 integration works fine, so it is not a storage issue. Is there a known limitation with WebRTC metadata retention in the Recording API?
1 Like