Need some help troubleshooting
Quick question about the stability of the /v2/recordings/screen endpoint during trunk failover events. We see immediate 500 Internal Server Error responses when traffic shifts to secondary BYOC providers in Asia/Singapore. Primary trunks function normally. Does the recording service require specific SIP headers or latency thresholds that these secondary carriers fail to meet during the switch? Any insights on configuring timeouts or retries would be appreciated.