VAPI voice call agent not listening
# support
o
@Pigeon @Sven @Vapi Please my Voice agent is only saying the first message. Then continues with my idle message till it hangs up call even when I keep saying words and screaming. Please help my clients is angry 😡😡😡
v
Hi there! I understand how frustrating it can be when your voice agent isn't working properly, especially when it's affecting your clients. Let's get this fixed! 🛠️ I can definitely help you troubleshoot why your VAPI voice call agent is only saying the first message and then defaulting to the idle message until hanging up, even when you're speaking. ## Initial Troubleshooting Steps First, let's check some basic issues that could be causing this problem: 1. Check for network issues - Ensure you have a stable connection as network delays can cause the agent to not properly receive input [source](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334024569861963788). 2. Review recent configuration changes - Confirm if you've recently changed any settings in your VAPI agent's configuration [source](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334024569861963788). 3. Check the transcriber - This could be a "deafness bug" where the agent doesn't hear anything. Try changing the transcriber from Deepgram to alternatives like Whisper, Gladia, or Azure [source](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1343612796717371393). ## Configuration Settings to Review Several settings could be affecting your agent's behavior: 1. Idle message configuration - Check your
messagePlan
settings, particularly: -
idleMessages
-
idleMessageMaxSpokenCount
-
idleTimeoutSeconds
[source](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1333783762579755020) 2. Silence timeout settings - Review
silenceTimeoutSeconds
,
responseDelaySeconds
, and
llmRequestDelaySeconds
[source](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1332286268805087272).
3. Voicemail detection settings - These might be interfering with the agent's ability to listen [source](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1333472116984778894). 4. Endpointing behavior - Consider adjusting or disabling endpointing if it's causing issues [source](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1344633027925377064). ## Advanced Troubleshooting If the basic steps don't resolve the issue: 1. Examine logs - Look at VAPI logs for error messages or warnings that could provide more insight [source](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334001638876250233). 2. Check the listen URL - Ensure it's valid and not expired. It should look like:
wss://<domain>/<unique-call-id>/transport
[source](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1329235631855108128). 3. Test with a WebSocket client - Use a tool like
wscat
to test the URL directly [source](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1329235631855108128). Would you like me to help you check any specific part of your configuration, or do you need more details on any of these troubleshooting steps? Sources: - [VAPI voice call agent not listening troubleshooting](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334024569861963788) - [VAPI idle message configuration](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1333783762579755020) - [Troubleshooting VAPI voice call agent issues](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1332286268805087272) - [Common issues with VAPI voice call agents](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1343612796717371393)
- [Preventing premature call hang-ups in VAPI voice call agent](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1344633027925377064)
s
hey, my condolences, its a bug ... vapi devs are on it, but we all have to suffer thru this ... just another case of "dont fix it if its not broken"
message has been deleted
You can try this workaround mentioned by @Silverstar307 in another post regarding the same issue ... i didnt try it yet but let me know if it worked if you do https://discord.com/channels/1211482211119796234/1357701801964736704/1357712404720648283
i
The workaround doesnt work
s
sh!t ... thanks for trying
o
Thank you Sven for responding it eans alot to me right now
s
sell it to your client as: A failure of one of the systems components. not your fault. it would have happend with or without you but with you he has somebody who takes responsibility to fix it. ... good luck brother
@Arvind @Sahil Still not fixed unfortunately... Are you on it? Any update? Thanks in advance
try change to google or openai ... save and then change back to deepgram... that worked for me ... kinda ... the agents responses are whacky still but the language remains changed
@Arvind Agents working reliably again ... thanks for your effort
a
@Sven Appreciate it! Do ping me if you anything comes up. Will make it a priority to help our beloved discord community out! 😄
o
Is there anything I must do at my end?
a
Just refresh the page. Make the necessary transcriber updates and publish them to see your changes reflect on the Assistant.
o
Thank you @Arvind I would try it out once I get on my PC
s
@OgagaPengist If it is not working right away: plz try to refresh first. then choose google as a provider and your language. then hit "Publish" and take a close look at the icon within the button give it some time a few seconds ... if the rocket comes back hit the button again until the white checkmark remains within the button. if it does so, refresh again to see if the changes remain on google... if so repeat the process with deepgram, choose nova 2 and your language and hit the button until the checkmark stays ... remember ... give it 2 to 3 seconds if its not changing to a rocket try refreshing the page to check if the changes are saved. Good luck ... let me know how it went
o
@Sven bless you man. I would be back here soon
@Sven this is still not working. I have updated the transcriber and yes the rocket left already after 2 to 3 clicks and refresh. But when i feed my json into the transietn asssistant it still does not hear me. Please what else can be done
@Arvind
@Sven @Arvind I even just created a new assistant and published with default set ups.... if itest the asssitant by clicking talk to assistant it works well. But once the call is initaited it is not responding at all after the first opening line. what can i do please this is frustrating
s
does the language save?
which transcriber are u using?
@OgagaPengist
o
i am using deepgram
i checked my call logs and i saw something i want to share
s
did the language save?
yes the language saved
I refreshed 2 to 3 times to make sure
s
cool ok ... did you send the language parameter in the payload?
o
How do you mean. I dont know how.
s
do you use assistant overrides or do you create an assistant?
o
All I did is set up the assistant. opy the id and run a get request to get it json. and use that for transient on make
s
you talked about transient
o
Yes...
s
so you created an assistant via the dashboard and want to push in the variable via make correct?
o
Yes correct
Do you want to make outbound or inbound call?
o
I would be doing both
in bound on different workflow
Outbound on different workflow
s
this is for outbound
use a "set variable" tool in make and define the variables you want to use or just hard code it instead of each reference
o
Yeah I did that
for outbound
s
what does your HTTP request look like?
ok please delete these asap your token is visible
i cant see an assistantId
try to use the schema from above
o
I used assistant not assistantid because i made the assistant into a json object
But I want to try out the schema above
On of my major issue now is this thing has worked before now and just stopped wioking
Without me altering anything
s
weird
o
Very weird. Even inbound is not listening either
did you see the first set of image i sent? the error message from the logs?
s
yea
o
Okay.... @Sven what are the alternatives i have if i dont want to use a transient assistant
s
do you use twilio or vonage
o
I use telnyx
s
ok ... i dont have any experience with them ... but you said by talking via the dashboard it works and your call logs mentioned webhook rejections by the server which in this case would be a telnyx server right? ... so i would assume the cause of the error there
maybe ping @Arvind with this new information
o
You have a point
let me try setting up vonage
and see if that solves it
because this is sudden and weird
s
i use twilio and it works ... i dont have experience with vonage either
o
And when i played the audio record from the call i could only hear the asisstant and with lots of noise nothing from my voice
My client twillio got suspended dont know what he did wrong
s
ouch
o
I would set up my own twilio and get a number and use it to try things out
s
sounds like a plan
o
@Sven whether this finally works or not I must say you have being heven sent
@Sven your guess was right. Telnyx is mesing me up
a
checking if this is resolved/solved for you?
o
@Shubham Bajaj yes
5 Views