Rehan Sanjay VenkatesanandClaude Opus 5 a4e7afac83 fix(status): don't re-send pre-transfer call statuses after a transfer (#1584) ...

A call transferred between feature servers arrives at the receiving server as a
fresh INVITE, so the session runs through trying, ringing, early-media and
answered again as it accepts the REFER. The application was already told all of
that by the server that first handled the call, so it sees a second round of
events for a call it believes is long since answered.

Skip only the application-facing status callback for those four statuses when
the session is a transferred call. callInfo, the redis call record and
record-all-calls still run exactly as before, so the call record stays accurate
and answering a transferred call still starts recording.

Fixes #1392

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>

2026-09-09 14:43:32 +01:00

..

http-routes

add sip_reason_header to status Callback- #178 (#1579)

2026-08-21 07:35:38 -04:00

session

fix(status): don't re-send pre-transfer call statuses after a transfer (#1584)

2026-09-09 14:43:32 +01:00

tasks

Fix/siprec survives fs transfer (#1586)

2026-09-09 07:45:30 +01:00

utils

add sip_reason_header to status Callback- #178 (#1579)

2026-08-21 07:35:38 -04:00

config.js

ci: authenticate to AWS via GitHub OIDC using the role_arn credential path (#1582)

2026-08-26 13:53:14 -04:00

dynamic-apps.js

support direct call to conference (#746)

2024-05-28 10:30:52 -04:00

middleware.js

add sip_reason_header to status Callback- #178 (#1579)

2026-08-21 07:35:38 -04:00