Need help reviewing this. Across numerous accounts, having this affect 75%+ of our inbound calls. TraceID: - 5dddc73e-26e4-4682-b6fa-6245f07f912a - 06f4e73f-8a10-406c-8f35-ac8cc193dfac - 06305e9a-146a-4dd6-bcc3-3108cb6562f1 Call ID: - 019b0649-dff1-7aa3-aa92-c1a496829f5b - 019b0609-64c3-7cc9-a8ee-6ec2d8d44a77 - 019b05ef-1321-7226-bb7d-97c410d0152f Vapi Org: - b8e24584-0a9a-483b-9954-4c43eb851e02

Action Required: Since

call.in-progress.error-providerfault-transport-never-connected

indicates a provider-side failure, please escalate this to Vapi support with your call IDs and account details for investigation. You can include your TraceIDs and a summary of the issue in your support request. Reference: [Vapi Call Ended Reason Documentation](https://docs.vapi.ai/calls/call-ended-reason) Source: - [Vapi Call Ended Reason Documentation](https://docs.vapi.ai/calls/call-ended-reason)

@Zack Here is an interesting fallacy about telephony in general, and SIP Telephony in particular - it's not a bullet proff technology. Most of us tend to think of telephony as a "wire between two places", but in fact, there are hundreds of elements between two parties on a phone call - which means, the call can fail along the way, and the receiving party will never know a call even took place. Now, I'm assuming your phone number are provided to VAPI via BYO SIP trunking ?

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!