Quick question about WFM quality score discrepancies during BYOC failover

Quick question about the /v2/quality/evaluations endpoint returning inconsistent scores when calls route via secondary trunks in Asia/Singapore. The primary trunk logs show full metadata, but failover calls drop specific SIP headers, causing the quality engine to misclassify interaction types.

  • Verified outbound routing rules prioritize secondary trunks correctly during drill scenarios.
  • Checked carrier-specific SIP registration logs for missing P-Asserted-Identity fields.

Any insights on preserving metadata during failover?