Error: 422 Unprocessable Entity
Why does this setting fail when applying screen recording rules to our ap-southeast-1 BYOC trunks? The Architect flow triggers the recording, but the API returns a validation error on the recording_type field. We are using SDK v2.21.0. The SIP session logs confirm successful media establishment, yet the platform refuses to bind the screen capture to the trunk-specific routing profile. Any insights on the schema requirements?