Hangup on assistant transfer in Squad
# support
o
Hello On Call ID : 07bd0e64-42c8-4483-9174-a19170cdb8fb I get the message from the first assistant, I answer, get transferred, and according to the logs, I get the second assistant to respond, but I don't hear anything, and after a while the call hangs up. I can't seem to understand where the issue occurs because the logs are incomplete, no messages, just the Logs.
v
Hi there! šŸ‘‹ I'm sorry to hear you're experiencing issues with call hangups during assistant transfers. Unfortunately, I can't determine the exact cause for your specific call ID without complete logs. However, I can definitely help you understand potential causes and provide troubleshooting steps for this type of issue. ## Potential Causes for Call Hangups During Assistant Transfers There are several common reasons why calls might hang up during assistant transfers in Squad: 1. **Assistant Configuration Issues**: - The "phone-call-control" server event might be enabled on your assistant. According to [Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1335869152535121960), this can prevent call transfers from executing correctly. - Your squad members might not have destinations properly configured, which results in no transfers as mentioned in [Discord](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1339776555639115776). 2. **Transfer Function Issues**: - The assistant may not be triggering the transfer call function correctly, leading to premature call termination. - The logs might show "No transfer destination returned" error as noted in [Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336644455582928906). 3. **Network and Telephony Issues**: - Network delays or unstable connections can cause call hangups. - There might be a failure in the handshake between the telephony system and Vapi. ## Troubleshooting Steps Here are some steps you can take to troubleshoot this issue: 1. **Review Squad Configuration**: - Verify your squad configuration, including how squad members are set up and the destinations specified. - Ensure squad config members have destinations configured, connecting root assistants to other assistants. 2. **Check Assistant Settings**:
- Remove the "phone-call-control" server event from your assistant if it's enabled. - Check the
maxDurationSeconds
setting to ensure it's not set too low. 3. **Examine Available Logs**: - Even with incomplete logs, look for any error messages or patterns that could indicate what went wrong. - Check for specific errors like "No transfer destination returned" or transfer function failures. 4. **Contact Vapi Support**: - Reach out to Vapi support with your call ID (07bd0e64-42c8-4483-9174-a19170cdb8fb) and a description of the issue. - They can check their internal logs and provide specific information about your call. ## Why Logs Might Be Incomplete Your logs might be incomplete due to several reasons: 1. **System Issues**: According to [Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1330990957650378762), incomplete logs can result from delays, configuration problems, or technical glitches within the logging system. 2. **Call Setup Problems**: Issues during call setup, such as connection failures, can lead to incomplete logs. 3. **System Outages**: System outages or timeouts can interrupt the logging process. Would you like me to provide more specific debugging strategies or information about any particular aspect of this issue? Sources: - [Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1335869152535121960) - [Discord](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1339776555639115776) - [Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336644455582928906) - [Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1330990957650378762)
p
Thank you for reaching out to us. We've received your message and will get back to you as soon as possible.
Hi, checking if this is resolved/solved for you?
o
Not yet, I'm having transcription issues at the moment so my greeting assistant can't understand what I'm saying anymore.
ok if you look a the call logs for Call ID : 77c95566-963d-4d97-ad8c-392ff3b0eaf8 - it seems like the transfer is "successful" in the logs, but I don't hear the second assistant greeting and the call hangs up due to lack of activity it seems, so can't tell what is going on
@Shubham Bajaj I've rebuilt my squad using the UI tools, as I was getting stuck with the API built / transient assistants not transferring. Now I have an issue where I can see that my assistant is supposed to be getting a tool and reading a text, which according to the logs it is doing, but I don't hear anything, and the call logs say it hung up because of inactivity on my part, so there is something not working here Call ID : 0234ce8b-6bfe-44db-87a4-0d7fe24c32b8 Squad ID : 7aa5920f-4ed0-4535-9e2b-9c61f25070bd
Ok it gets more complicated, this time it actually worked, so I have no idea why it sometimes works and sometimes doesn't?
s
@Ouranos šŸ”µ 09:44:52:855 Transferring Assistant to { "type": "assistant", "assistantName": "Book Passage", "message": "Let me connect you with our book passage reader.", "description": "Transfer to book passage assistant", "transferMode": "rolling-history" }... šŸ”µ 09:44:52:860 Say Request...109 (say: "We shall identify a page from a book. You will need to give us a hint to do this correctly. Shall we proceed?", interruptible: true, audio: false, endCallOnError: true, addToModelOutput: true, endCallAfterSpoken: false) 🟔 09:44:52:867 Couldn't Complete Say Request { "task": { "content": "We shall identify a page from a book. You will need to give us a hint to do this correctly. Shall we proceed?", "endCallOnError": true, "interruptible": true }, "error": {} } 🟔 09:44:52:865 Couldn't Get Speech For hume:aeaaf1f8-fe31-49ae-893d-c744e5207bc2:octave:16000:6e1ea6c9206e058fb5274ef1497decb078a1d060dde4b09de022f25c20677b36, "We shall identify a page from a book. You will need to give us a hint to do this correctly. Shall we proceed?" 🟔 09:44:52:864 Couldn't Generate Speech. Voice: { "provider": "hume", "voiceId": "aeaaf1f8-fe31-49ae-893d-c744e5207bc2", "model": "octave", "isCustomHumeVoice": false, "chunkPlan": { "enabled": true, "minCharacters": 30, "punctuationBoundaries": [ "怂", ",", ".", "!", "?", ";", "،", "Ū”", "ą„¤", "ą„„", "|", "||", ",", ":" ], "formatPlan": { "enabled": true, "formattersEnabled": [ "markdown", "asterisk", "newline", "colon", "acronym", "dollarAmount", "email", "date", "time", "distance", "unit", "percentage", "phoneNumber", "number" ], "numberToDigitsCutoff": 2100, "replacements": [] } }, "fallbackPlan": {"voices": []}, "inputMinCharacters": 30, "inputPunctuationBoundaries": [ "怂", ",", ".", "!", "?", ";", "،", "Ū”", "ą„¤", "ą„„", "|", "||", ",", ":" ], "inputPreprocessingEnabled": true, "inputReformattingEnabled": true }
@Ouranos What's happening here is when your request is sent to the voice provider, it's returning an error which by mistake from our side is not being logged as an error. Instead, we continue the call, which is why you get the call marked as "customer ended the call with silence timeout" instead of a call ended because of voice provider failure. I just suggest you to try to change your voice provider either to 11 Labs Cartesia or Azure, and then try out it will work
Could you share this call ID so I could take a look?
p
checking if this is resolved/solved for you?
o
Sorry not yet, I need to troubleshoot a bit further, I recently realized that my calls where getting a ton of noise, and I think it might be telnyx related, so I need to make sure that isn't just messing things up
p
Hey Ouranos, please let me know if I can help you further. Until then, I'm closing this again.
Hey Ouranos, please let me know if I can help you further. Until then, I'm closing this ticket\*.