We’re seeing a reproducible issue on outbound calls to Google Voice numbers where the audio stream is lost or severely delayed after the screening handoff. We’re attaching a full markdown report below with complete details. What’s happening: Google Voice screening is transcribed correctly, but after the handoff to the human, VAPI stops receiving the customer’s audio — either entirely or with up to a 30-second gap. The customer connects, speaks, hears nothing, and hangs up. Call `019e214d-909e-7000-91ef-b60948128851`:

[2.48s]  Google Voice: "Hello. Please state your name after the tone..."
[31.25s] Customer: "Hello?"   ← 29-second gap (customer was speaking the whole time)
[33.17s] Bot: "Hi. Is this James Bond?"

Call 019e214c-3f51-7001-9ce5-ba7ab01fdc11:

[2.70s]  Google Voice: "Hello. Please state your name..."
[7.24s]  Bot: "Hi. I'm trying to reach James Bond."
[—]      No customer audio for the remaining ~63 seconds

Recordings (confirm audio absent at RTP level — not a transcription issue): https://storage.vapi.ai/019e214d-909e-7000-91ef-b60948128851-1778675269264-85e39da8-16b7-4314-b756-cb379ff708ab-mono.wav https://storage.vapi.ai/019e214c-3f51-7001-9ce5-ba7ab01fdc11-1778675179639-7b131967-9908-4f17-8f09-2056ffc45832-mono.wav Already ruled out: prompt changes and replacing voicemail detection with the voicemail tool — __issue persists ONLY on Google Voice, NOT happening with iOS call screening__. Specific to Google Voice. Hypothesis: Google Voice’s screening-to-human bridge triggers a SIP re-INVITE that interrupts the RTP stream. The 29s recovery in one call suggests re-sync rather than full stream failure. Could you check raw RTP logs for the two calls above for a stream interruption during the handoff? Is this a known Google Voice issue? Additional calls from May 12: - 019e1d27-017d-711f-820b-fbf85dc550d3 - 019e1d26-a9c8-7000-b838-385bdd872980 - 019e1d23-1ab4-7000-8ed1-e3c4260dd759 - 019e1d1a-6ce8-7000-91a3-e5691e52194e https://cdn.discordapp.com/attachments/1504170169956696185/1504170170292375552/vapi-google-voice-bug-report.md?ex=6a060322&is=6a04b1a2&hm=5b416bf2db95f4a00d955c2f652823f2c236b5b0af4518da59e02f528579f62b&

Hi, I’d be happy to help investigate this. Based on your logs, it does look like a SIP re-INVITE or RTP renegotiation issue during Google Voice’s screening-to-human handoff, especially since iOS screening works fine and one call recovered after ~29 seconds. I can review the call flow, SIP signaling, and RTP behavior to pinpoint where the audio stream is breaking and help confirm whether it’s a VAPI handling issue or a Google Voice edge case. Feel free to send over any additional logs or access details. @DonutDeflector