Today I came across an issue where, when I try to call a cell phone number, VAPI gives a “customer busy” status. This is my cell phone number. I didn’t hear my cell phone ringing, and there is no voicemail. Sample Call ID:s 019d8729-98ad-7000-9a6b-a6b9e9f54e60 019d871d-13f7-7000-9bd4-a9c5d13aa3e7

This usually isn’t a real “busy” on your phone it’s happening inside Vapi before the call actually reaches the carrier. From experience, this can happen when the outbound leg fails early due to SIP/Twilio routing, caller ID restrictions, or the call being rejected by the upstream provider, so it never fully hits your mobile network—hence no ring and no voicemail. If you share the call logs, I can trace where it’s dropping (carrier vs Vapi layer) and help you stabilize the outbound flow @Dhina

Hi, Thank you for sharing the sample Call IDs. I reviewed the behavior, and the “customer busy” status is most likely happening because your org’s single outbound Twilio number has been spam-flagged and currently has a poor carrier reputation. Because of that, some carriers may reject the call with SIP 486 (Busy Here) before the destination phone is even notified

Suggestion: To investigate the "customer busy" status, go to your [Vapi dashboard](https://dashboard.vapi.ai/calls), locate the specific call using your Call ID, and review the call logs for any additional error details. If the issue persists and you still do not receive calls, share the Call ID and a description of the problem with Vapi support for further assistance. This helps the support team analyze backend logs and provide targeted troubleshooting based on your specific case. According to the documentation, including the Call ID and a clear description speeds up resolution. Sources: - [Vapi Debugging Documentation](https://docs.vapi.ai/debugging) - [Vapi Issue Reporting Guide](https://docs.vapi.ai/issue-reporting) - [Vapi Call Ended Reasons](https://docs.vapi.ai/calls/call-ended-reason)