Ive made an outbound calls they are being placed but not delivered - when the transcript you can hear the agent speak first then the call ringing then its dropped very weird. Please advise

@KMlearning84 I'm sorry to hear you're experiencing issues with your outbound calls. It sounds like there might be a problem with the call setup or routing. To better assist you, I would need to check the configuration of your Voice API and possibly review the call logs to identify any errors or misconfigurations. Could you please provide me with more details about the issue? Specifically, I would need to know if this is happening with all calls or just specific ones, and if there have been any recent changes to your call setup or routing configurations. Additionally, if you have any error messages or codes, that would be very helpful in diagnosing the problem. In the meantime, please ensure that your Voice API credentials are correct, your account has sufficient balance, and that there are no network issues that might be affecting call delivery. If everything seems in order on your end, we may need to escalate this to our technical support team for a deeper investigation. Please let me know how you would like to proceed.

@Vapi there are no error messages but you can view the call ID here: fa715cc2-2846-4b8f-ad63-67fcd4f3bc0f The call is being successfully placed - The AI assistant is speaking before the call is even being placed to the appropriate number. How could this be?

@KMlearning84 It sounds like there may be an issue with the call flow or the timing of the actions within your setup. Typically, the AI assistant should not start speaking until the call has been connected to the recipient. Here are a few things to consider: 1. **Call Flow Configuration**: Check your call flow configuration to ensure that the AI assistant is set to speak only after the call has been answered. There might be a misconfiguration causing the assistant to start speaking prematurely. 2. **Event Handling**: Ensure that the events in your call logic are being handled correctly. For example, the assistant should be triggered by an 'answered' event rather than a 'dialing' or 'initiated' event. 3. **Network Latency**: Sometimes network latency can cause a delay in the call connection, which might result in the AI assistant starting to speak before the recipient has answered. 4. **API Configuration**: If you're using the Create Assistant API, make sure that the

forwardingPhoneNumber

attribute is set correctly. As per the context provided, if this attribute is not needed, consider setting it to null or an empty string to avoid any potential issues. Since you've provided the call ID, I can look into the specific call logs for this ID to see if there's anything unusual. However, without direct access to the system or logs, I can only provide general advice. If you have access to the call logs or the system where the Voice API is configured, please review the call flow and event handling related to the call ID you've provided. If everything appears to be configured correctly and you're still experiencing this issue, it may be best to reach out to technical support for a more in-depth analysis. If you need further assistance with this or would like me to guide you through checking the configurations, please let me know.

I get the same issue even if the call is being placed directly via the outbound call via vapi website

@KMlearning84 can you share call id.

Hi Shubham - Please find the Call ID: 59e48206-6305-44db-bcff-50a5eb734ddd

@KMlearning84 allow me some more time to find RCA, not sure about it.

ok no worries take your time - but please update me when you have found the issue as it is really weird.

@KMlearning84 just confirmed it was one of the chances, mostly likely because number wa not reachable or voicemail was enabled.