Realtime session continues after Twilio SIP No Answer

@andrew_tomis.tech, appreciate you sharing this and including the timestamps + session ID, that really helps narrow things down.

This does sound familiar. We’ve seen a similar case before where the realtime session didn’t terminate even though Twilio marked it as “No answer,” and that one ended up being resolved on the backend side. So this might be related or a regression.

I’ll flag this with the engineering team so they can take a closer look. If you happen to catch any newer examples, feel free to drop them here too, those patterns help a lot.

Also, if anyone else is seeing the same mismatch between Twilio status and session behavior, chime in. It helps confirm if this is more widespread.

-Mark G