Trying to understand why our BYOC trunks are mapping SIP 408 Request Timeout events to ‘No Answer’ instead of a specific disposition.
We see a significant discrepancy in the Architect flow analytics compared to the carrier logs. The system defaults to ‘No Answer’ when the timeout isn’t explicitly handled.
Is there a specific configuration in the outbound campaign settings to override this default behavior?
Need to ensure our WFM adherence reports reflect accurate call outcomes for the Chicago team.
The documentation actually says BYOC trunks map SIP 408 to ‘No Answer’ by default because the carrier hasn’t sent a final response within the timeout window.
Cause:
The outbound campaign relies on the trunk’s default mapping logic when no explicit disposition override is configured in the flow.
Solution:
Add a ‘Call Disposition’ block in Architect immediately after the dial block to explicitly set the disposition to ‘Timeout’ if the call state remains ‘In Progress’ past the threshold, rather than relying on the trunk’s default behavior.