Do not hear VAPI agent, but it hears me
# support
c
Setup: Vapi integrated in Make.com with a Twilio number. Expected behavior: When I start the make.com scenario a http request send is to the Vapi Api with all the data needed. The agent calls me on my phone and I can talk to him. It worked fine with the Vapi number when I called another US-number. The US-number was connected to a softphone which I could use in Germany (where I live). Current behavior: When I start the make.com scenario a http request send is to the Vapi Api with all the data needed. The agent calls me on my phone and it can hear me (I hear my voice in the log files) and reacts to my input, but I cannot hear the agent. Call-ID: 7d4d9218-4db6-432b-a73b-dec78b835be8 Timestamp: 21:02:18:410
v
Suggestion: Double-check that your Make.com scenario and Vapi tool configuration include the correct Phone Number ID and Assistant ID. If these fields are missing or incorrect, the agent may not generate audio output, even though it processes your input. Tip: In the Vapi dashboard or API request, ensure both IDs are explicitly set for the call. If the issue persists after verifying these, please share your configuration details or logs for further troubleshooting. Source: - [Vapi Support Community Discussion](https://discord.com/channels/1211482211119796234/1370485222214336564)
c
Both are correct.
I just changed the Phone Numer ID and the Assistant ID in the working setup and then it stopped working.
v
Thanks for confirming the IDs. Since the issue started after changing them and persists even when set correctly, could you please confirm: Are you able to hear the VAPI agent if you revert to the original Phone Number ID and Assistant ID that previously worked? This will help determine if the issue is with the new IDs or something else in the configuration. [Reference: Vapi Support Community Discussion](https://discord.com/channels/1211482211119796234/1370485222214336564) Source: - [Vapi Support Community Discussion](https://discord.com/channels/1211482211119796234/1370485222214336564)
c
Yes, with the original numbers it worked. The original numbers were from Vapi, the not working number is from Twilio (German number)
v
Suggestion: Check that your Twilio SIP trunk for the German number is correctly configured to allow two-way audio with Vapi. Specifically, ensure that the Vapi SIP server IPs (
44.229.228.186
and
44.238.177.138
) are whitelisted in your Twilio trunk's access control, and that your trunk supports media in both directions. After updating, test the call again. Reference: [Vapi Twilio SIP Integration Guide](https://docs.vapi.ai/advanced/sip/twilio) Sources: - [Vapi Twilio SIP Integration Guide](https://docs.vapi.ai/advanced/sip/twilio) - [Vapi Phone Calling Overview](https://docs.vapi.ai/phone-calling)
c
I did the integration directly in Vapi - shouldn't the rest be worked out in the background? When I test the agent directly in Vapi with the Twilio number everything works fine.
j
I'm seeing similar issues, but only when I have a Rime.Ai voice in use. Swapping to a different voice provider seems to solve the problem. Are you using Rime vocies by chance?
c
No, it's 11Labs. And it worked great before I used a Twilio number.
c
looking into it.
Hey Chris, can you please share a few more call ids with similar issue?>
2 Views