Stuck on resolving SIP 488 errors specifically during BYOC failover in Asia/Singapore. The primary trunks handle Answering Machine Detection correctly, but secondary carriers drop the flag immediately.
This affects our quality scoring logic. The QMS evaluations fail when the trunk switches, returning a 500 Internal Server Error.
We use SDK v2.1.4. Is there a known conflict with the new analytics engine during carrier rotation? The logs show no SIP issues.
Any insight into why the secondary provider breaks the AMD handshake would help us adjust the failover thresholds.