WarmTransferTask greetingSpeech not triggered, AI remains in session after transfer

[royibernthal]

1. It’s a good thing that you tried to repro, made me double check myself.

My initial diagnosis was inaccurate - agent speech was triggered on connect, but I wasn’t hearing the brief greeting due to this premature 200 OK issue:

Outbound call - waitForParticipant doesn't wait for the participant to answer the call

Update from Quo: they confirmed they send SIP 200 OK before a human answers, so they can establish the external SIP leg and play hold music or run call flows while ringing team members internally. The actual pickup then happens inside Quo, with no additional SIP signal sent. So waitUntilAnswered isn’t 100% reliable for detecting a human answer. I imagine this behavior is not unique to Quo.

Can potentially measure how fast the call was answered to determine if it was answered by a system or a human, and behave accordingly (e.g. no proactive greeting if answered by a system). Either in WarmTransferTask or createSipParticipant. However it sounds like I’m the only one who reported this premature 200 ok issue so far, so not sure how many people would benefit from this in the near future.

2. What does a session.generateReply() with empty instructions do?
3. After a successful transfer, if either human leaves the call, it stays active indefinitely, leaving the other person on the call alone. Might be worth handling this in WarmTransferTask?