Assistant request is still getting made to our server, and a successful response is returned, however we get this error from Vapi. Call Ids: 1ffcd90e-7fd8-493a-875a-45a07e6fa603 c73e630e-7b6b-49a2-90d7-b4de04949d70 We usually get this sometimes per week, but we are seeing a spike in the past two days Need to know what is happening here

Suggestion: To reduce 'twilio-reported-customer-misdialed' errors, ensure all outbound phone numbers are validated and formatted in E.164 before sending to Vapi/Twilio. Here’s a sample validation in JavaScript:

js
function isE164(number) {
  return /^\+[1-9]\d{1,14}$/.test(number);
}

Validate each number before making the call to catch formatting issues early. [See more in the Vapi documentation.](https://docs.vapi.ai/calls/call-ended-reason) Source: - [Call ended reason codes (Vapi documentation)](https://docs.vapi.ai/calls/call-ended-reason)

These are inbound calls

Hey! To help track down this issue, could you share: \- 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!