the agent says he transferred the call but never does and then just silence forever

Hi there! 👋 I see you're having an issue with Squads transfer resulting in a "Silence timed out" error. I don't have access to your specific implementation details, but I can definitely help explain what might be happening and suggest some troubleshooting steps. According to the [documentation](https://docs.vapi.ai/squads), Squads enable calls to transfer between assistants mid-conversation while maintaining full conversation context. When you're experiencing the "Silence timed out" error during a transfer, several things could be causing this: ## Potential Causes 1. **Tool Call Response Issues**: After a tool call (like the transfer request), the agent might go silent if it's not properly sending a response back to Vapi, leading to a silence timeout. This can happen intermittently with custom tools according to [user reports](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1327662627882795059). 2. **Timeout Settings**: The

machineDetectionSilenceTimeout

parameter might be too short (currently set to 6000 milliseconds/6 seconds by default). If silence lasts longer than this setting, it could cause a timeout before the transfer completes. 3. **External Service Delays**: Delays from services like 11labs responding can trigger the silence timeout. Some users have reported that [increasing the

silenceTimeout

to 30 seconds](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1338586561662419055) helped resolve this issue. 4. **Squads Configuration**: If squad members don't have proper destinations configured, transfers might fail. According to [user discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1339776555639115776), if squad config members don't have destinations, the root assistants might not connect to other assistants, resulting in no transfers. ## Troubleshooting Steps

@Vapi Support Bot checked all that, still doesn't work

I understand your frustration with this persistent issue. Since you've already tried all the standard troubleshooting steps and the problem still persists, I'm escalating this to our technical support team for further investigation. They'll need to take a deeper look at your specific implementation and the logs to identify what's causing the Squads transfer to fail with the "Silence timed out" error. This could be related to a more complex configuration issue or potentially a bug that needs addressing. A support specialist will reach out to you shortly with more personalized assistance. In the meantime, if you have any additional logs or details about your implementation that might help with troubleshooting, please feel free to share them. Thanks for your patience while we work to resolve this issue! 👍

Hey Jetsoccer, Function Name Transfer Call is a reserved keyword, so you can use it. Instead, you have to use a different name such as Custom Transfer Call. I will suggest you don't need a Transfer Call function to do the transfer between the squad assistant destinations. You can do it by prompting the but if you require it to use the function, Then I suggest just change the name and try another call, and it will work.

@Shubham Bajaj I'm a bit confused, my first assistant in the squad will transfer the call to either 2a or 2b and each one of those 2s has its own phone number in the transfer. But those 2a/b agents don't forward the call to the "forwarding phone number" unique to each https://cdn.discordapp.com/attachments/1355540189359112383/1356226940045889648/image.png?ex=67ebcc43&is=67ea7ac3&hm=61740ddbd6544eb12cb9168becc521a9c1f78da3630bef29d8f905ad6da16cf6&

Can you share the call ID where you are observing this behaviour?

@Shubham Bajaj Call ID: 0b085449-475f-4a16-9213-ae9010596f8a Squad ID: 237bb12e-fb03-4158-99b1-da74a678ee17

🔵 13:12:19:067 Completion Request Aborted (#1, provider: azure-openai, model: gpt-4o-mini-2024-07-18, region: westus, credential: false) Hey Jetsoccer, the call ended because of silence timeout. The model triggered the tool, but then the model triggered the tool and selected based on the destination selected the message as well sent to the voice provider. Eventually, the completion request was aborted from the OpenAI side, which resulted in failure. This means your call could not be transferred, and eventually gives you a perception of a call transferring not working.

@Shubham Bajaj sometimes the error is 'silence timed out' but most often it's "assistant forwarded the call" but nothing happened really, the callbot closed the call after sayin "transferring now". I have the same pb for France, both Twilio and Vonage phone numbers don't forward calls anymore, ex call: 14ac33d5-0c0d-4b52-aa5a-dc3ca19d5831 or 6c22c3b0-438f-49d3-8d88-1e3827b9f6dc or d2db39e6-9b22-4271-83ee-af4362960694

Hi, checking if this is resolved/solved for you?

@Shubham Bajaj same as this ticket for me: https://discord.com/channels/1211482211119796234/1351795353573134357

Remove the

phone-call-control

server event from your assistant server messages.