Merge pull request 'fix: treat AST_CAUSE no-route/unallocated as a no-answer retry outcome' (#10 ) from fix/no-route-retry-cause into main

fix: treat AST_CAUSE no-route/unallocated as a no-answer retry outcome
process_agent_dial_outcome only recognized hangup causes 17/18/19/21/34/38. When the reserved agent's AOR has zero registered contacts (e.g. the softphone dropped, or nobody ever registered), Asterisk immediately hangs up with cause 3 (no route to destination) instead of running a Dial() long enough to produce a DialEnd/NOANSWER at all - so the retry listener silently ignored it and the escalation was left dangling in 'ringing' status (the agent itself still got released via the call-ended fallback path, but no retry to the next agent was ever attempted and the escalation record never reflects the failure). Added causes 1 (unallocated number), 3 (no route), 20 (subscriber absent), 22 (number changed) alongside the existing set.
2026-08-30 19:43:43 +00:00 · 2026-08-31 00:43:20 +05:00
1 changed files with 1 additions and 1 deletions
@@ -1233,7 +1233,7 @@ def process_recording_ready(


 _NO_ANSWER_DIAL_STATUSES = {"NOANSWER", "BUSY", "CANCEL", "CHANUNAVAIL", "CONGESTION"}
-_NO_ANSWER_HANGUP_CAUSES = {"17", "18", "19", "21", "34", "38"}
+_NO_ANSWER_HANGUP_CAUSES = {"1", "3", "17", "18", "19", "20", "21", "22", "34", "38"}


 def process_agent_dial_outcome(session, row: AsteriskEventLogRow, payload: dict[str, Any]) -> None: