Significant number of calls ended due to "unknown-...
# support
n
Hi, I'm noticing many of our calls are ended (5 - 10 per day) due to the above error. Any idea why these are happening? example call id 2000b2e0-06dc-4f3f-9f82-e8f33102cfeb
v
message has been deleted
You can continue this conversation by mentioning me in the message.
@nisalr I'm sorry to hear that you're experiencing issues with your calls. Based on the context provided, it seems like there are multiple errors occurring, such as out-of-credits, rate limit exceeded, and gateway errors with PlayHT, as well as issues like silence timeouts and calls being rejected by Vonage. For the PlayHT-related errors, it's possible that you've either exceeded your credit limit or hit the rate limit set by PlayHT, which could be causing the 502 and 504 gateway errors. The silence timeout issue might be related to a configuration that ends calls when no audio is detected for a certain period. Lastly, Vonage rejecting calls could be due to various reasons, including configuration issues or problems with the numbers being used. To help you further, I would need to check the details of the specific call ID you provided. Could you please confirm the
orgId
and the
createdAt
timestamp for the call with ID
2000b2e0-06dc-4f3f-9f82-e8f33102cfeb
? This information is required to investigate the issue accurately.
n
@User
s
Looking into it.
@nisalr call failure reason is silence timed out, and it's because server messages failed.
Copy code
json
// https://api.phonely.ai/call
"message": {
    "message": "Request failed with status code 400",
    "data": {
      "message": "Invalid message type conversation-update",
      "status": "error"
    }
  }
n
Thanks @Shubham Bajaj. Is this because our server couldn't handle the request?
s
I believe it's because your either send request at wrong end point or something is missing.
Please check your server logs, and confirm. If it's because of vapi then create a new issue, will check it again.
For now closing this issue.
3 Views