SIP Trunk 408 Timeout Impact on Queue Metrics

Looking for advice on why specific SIP 408 Request Timeout events are not reflected in the standard queue activity reports within the EU data center. The Architect flow handles the reconnection logic successfully, yet the performance dashboard shows these as successful calls rather than failed attempts, skewing the service level calculations. The environment is running standard voice routing with no custom data actions involved.

Thank you for the insights.

This looks like a reporting latency issue rather than a SIP failure.

1. Verify the recording status via GET /api/v2/recordings/{id} to confirm final disposition.
2. Check if the Architect flow is overriding the call result before the metrics engine processes it.