Anyone else having issue with inbound call? I am using same prompt and did an inbound call and an outbound call (using make.com) and the AI responses is not the same. The Voice AI kept going on loop when using inbound but works perfectly when using outbound.

Yes, you're not alone with this issue! 😊 There have been reports of Voice AI getting stuck in loops during inbound calls while working fine for outbound calls. Possible causes: - Network latency issues affecting inbound call processing - Configuration differences between inbound and outbound call handling - Voice settings that might work differently in each direction Recommended troubleshooting steps: 1. Check your network configuration to ensure there are no delays affecting the process [source](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1332133296347549797) 2. Review your assistant's configuration settings - incorrect configurations between the assistant and telephony service can cause looping [source](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1332114653252647894) 3. Verify that your AI logic correctly interprets responses and proceeds accordingly to prevent looping [source](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1330872643037167626) 4. Check voice settings like

voiceId

and speed settings which might need adjustment for inbound calls [source](https://docs.vapi.ai/tools/GHL) 5. Examine logs for both VAPI and any telephony services you're using to identify error patterns [source](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1332133296347549797) Let me know if any of these steps help resolve your issue! Sources: - [Discord Thread on Voice AI Looping Issues](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1330872643037167626) - [Discord Thread on Network Configuration](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1332133296347549797) - [Discord Thread on Assistant Configuration](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1332114653252647894) - [Vapi Documentation on Voice Settings](https://docs.vapi.ai/tools/GHL)

Well, depending on your connected telephony provider, inbound and outbound uses 2 different paths at the provider level. Assuming you are using a normal VAPI number, which is Twilio, your inbound call is routed one way, and the outbound call is routed another - which means, they may yeild different results. When it comes to these issues, I normally advise people to take ownership of their telephony channels and use Cloudonix to connect multiple carriers, so they can leverage mutltiple carriers, possibilites and capabilities as required.

Hey! To help track down this issue, could you share: - The call ID - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!

Hi Shubham, I note that this issue was cause by https://discord.com/channels/1211482211119796234/1351338779348304003

Hello Ivy, We're currently looking into this error that seems to be coming from Twilio. I'll keep you updated on the main issue as the team looks into it.

Hi Shubham, it seems like yesterday call still the same

Hey @ivy, Looking at the call logs, I can still see there is some drift from twilio side. I suggest you try contacting Twilio team and asking them why there is a drift observe on your account calls. They will have the right idea about it. Once it's fixed from their side, you won't be seeing mixing of LLM outputs and audio on our end. Twilio Call SID: CA0cff3f5e503561990e389aa0d8ea1e78