2 conversations mixed
# support
m
Hey, we had a failed demo yesterday with a lead. We did 2 calls, and both of them failed. When browsing the logs and recording for these calls we notice that the first call did not ended correctly and seems to continue on the second call which results in a recording where bot conversations are mixed. First call: f004c3b3-e7e8-4bc1-a7a2-5d78384e3a85 We see that we have logs such as
Twilio Detected "human"
or
Twilio Detected "machine_end_beep"
even long time after the call Second call: 3a7760c4-4e47-4f80-afea-7617a4f6f4a2 Call duraction is 17s but on twilio it's 3min We hear during this call some human phrases that where spoken during the previous call. We had a hard time during the demo yesterday because of this and we need to give an explanation to our lead to restore trust. https://cdn.discordapp.com/attachments/1247840298126544917/1247840298474934364/Screenshot_-_2024-06-05T105726.027.png?ex=66617d56&is=66602bd6&hm=57bf5439b7d75fe0dfddcd6a1b7b662f66fcb4b0f6f68281d375ebe23605dd83&
v
Hi @marem, I'm an AI assistant for Vapi. I'll analyze available sources and get back to you shortly.
----------------------------- **While I generate an answer, here are some sources that might be helpful**: * [Get Call]() * [Call Ended Reason]() * [List Calls]() * [Create Phone Call]() -----------------------------
### Answer It sounds like you experienced a significant issue in call management and handling, which resulted in a merged or continuous call recording. This could be related to several factors such as server connectivity issues, webhook handling, or problems in the call teardown process between your system and Twilio. Typically, issues like
Twilio Detected "machine_end_beep"
persisting beyond the expected time suggest that the call was not properly terminated in the system, or that events are being mislogged or delayed due to network issues [(1)]() . Similarly, discrepancies in call durations as noted in your second call might indicate that the call session was not properly closed or was inadvertently reopened, which can happen if the end of the call isn't properly detected or communicated between the systems involved . Given the scenario you described, here are a few steps you can consider: 1. **Review Call Logs and Settings**: Double-check the call logs in detail, focusing on the end events and any errors reported. Ensure that your system or Twilio is correctly handling call termination signals. 2. **Check Webhook Configurations**: Ensure that your webhooks related to call status updates are set up correctly and are capable of handling rapid updates without delays. 3. **Server and Network Checks**: Sometimes, server lag or network issues could delay processing of call terminations. Make sure your network configurations and server responses are optimized for real-time communications. For a more detailed investigation, you might want to explore the specific
endedReason
for each call in the logs, which can provide insights into why the calls were not terminated properly or why they appear intertwined . This explanation should offer a foundation to communicate with your lead, demonstrating an understanding of the p
roblem and steps towards resolution. If you continue to encounter these issues, a deeper technical review might be necessary with direct support from Twilio or your service provider.
s
@marem let's debug it together on a meet.
Sent you a link.