Call logs are missing messages
# support
m
Here's an example call: e1f50996-931b-4776-9fe0-eafdf55e5abf The assistant is reacting in a very strange way, almost like it isn't saving all my responses. Also, the messages tab in the call logs is missing lots of the messages both from the caller and the assistant. This is occurring for all calls right now for this assistant: ac343119-5009-412f-a9d5-bcc671f68fa5
u
Wondering if a few of our aupport requests and similar. I've just posted one and it's the same the logs and calls are not in sync. Listen to your call backs (check my phone recording vs the vapi version)
s
@mcondie I looked into the call ID here, the call recording and the call messages, its true that ok user messages are out of sync in the transcript and I am looking into it, and meanwhile I will suggest you try making another call by setting the transcriber deepgram end pointing to 300ms using API and start speaking plan wait seconds to 0.6 and smart end pointing set to true this will ensure that it captures the user's speech when it has finished at the right time and most of the times so eventually you won't have overlap as I can see in the call recording for the first message the bot started speaking looks like it has cut off you in between.
Regarding the call transcripts appearing out of order, if you have one more call ID, it would be really helpful to reproduce it. I tried reproducing, but couldn't. We won't stop your thread over there. I'll look for all other calls throughout my day and I will try to reproduce this behavior so that I can share this with the team and get it fixed.
Try the change suggested and let me know how it goes for you.
Can you please create a new support ticket for your issue so that I can look into it as well?
m
I added the configuration changes. It seems like there is a broader issue with UK phone numbers. I’m seeing audio quality issues that are affecting transcription on most of our assistants, but particularly UK phone numbers. I created a new ticket with more details
Here's a new call with the same bot that has incomplete messages, and messages out of order: 0202574b-10ba-4f6e-893b-1dcf1d0fdb6e
Here's the link to the related issue I created: https://discord.com/channels/1211482211119796234/1351585238316355647
@Shubham Bajaj any update? We've shut down all of our UK assistants due to this issue and the one I linked
s
@mcondie @~Stu~ CoreAspect.Agency Hey guys, an update for you. We have identified the issue; it was on our end, and it will be fixed by the end of day. Sorry for the bad experience. You guys can give it a try after some time, and for sure you won't see this happening again
@mcondie really sorry for your experience, our team is on it and it will be fixed maximum by end of the day.
m
@Shubham Bajaj can we get more information on what happened? We’re having to evaluate whether we stay with Vapi or look at other providers because this issue took so long to resolve and we had no information in the mean time.
Still seeing these issues: ea136c3e-3eb7-4fde-ae24-45efdcdb41e1
Here's some more ids: 172ef413-35fc-4885-be07-478337d971b5 ca9f1766-18f1-4e15-bc88-5a88baf4410f
@Shubham Bajaj Did the fix ever get deployed?
More calls with issues: ad2cbd67-3fdb-4144-80d4-cf8666839d9d db391e3a-5eba-45e8-99ef-b753b643774b
s
@mcondie @~Stu~ CoreAspect.Agency After investigating the logs from your recent calls, we've identified that Twilio's audio delivery is experiencing significant delays. These delays are causing what we call "drift" in our system: 1. **What's happening**: Twilio is not delivering your audio packets at a consistent rate, causing audio processing components to wait longer than expected between chunks. 2. **Impact**: This inconsistent audio delivery creates a cascade effect through our pipeline: - Voice activity detection becomes less reliable - Processing appears delayed - Overall call quality and responsiveness suffer
ref[other-threads]
https://discord.com/channels/1211482211119796234/1351585238316355647/1351946087124177016
m
@Shubham Bajaj that's great to know. How can we get more visibility to this? We've been dealing with this for multiple days, but none of the tools we have access to show this issue, and we haven't seen any discussion on Vapi support about this.
u
Very strange, I'm in Australia... only happens in one account.
I'm still experiencing the issue @Shubham Bajaj
m
@~Stu~ CoreAspect.Agency so are we. We're looking at forwarding calls through vonage to mitigate
u
@mcondie looks Ill have to setup a Vonage account then.
m
You could also try forwarding to a Vapi number if you don't want to set up a vonage account. We already had some test numbers there so we're going that way as a temporary measure
It's weird that twilio has been broken for so long. They are usually pretty reliable
u
it sure is... I'm wondering if its a wider networking issue, whatever their backbone system is (Amazon, Google etc)
s
@mcondie I identify the issue and flag it to the team. The team quickly realizes it's a Twilio issue and suggests it'll be automatically fixed. After some time, it still isn't fixed, so I confirm it's a Twilio issue by checking the drift and Twilio status pages. Currently, there's no easy way to determine which service is down, but we'll update you through our dashboard or discord when a service goes down.
For the next time, you can flag to me again, and I'll quickly look into the logs. Now that I know you guys are operating on a UK number, it will be easy for me to first check Twilio Drift and then logs for the other service providers.
**TLDR: **status page of the service providers can be used to identify if some service is down .
u
@Shubham Bajaj the number i have in an Australian number, so im confued if this is just an uk number issue
@mcondie did you get this resolved or find a work around?
s
@~Stu~ CoreAspect.Agency Can you ping me to your support ticket with the call ID? I'll take a look and let you know if it was from Twilio or something else.
u
2 Views