----------------------------- **While I generate an answer, here are some sources that might be helpful**: * [Inbound Calling]() * [List Calls]() * [Import Vonage Number]() * [Get Call]() -----------------------------

### Answer Based on the information available, if your Vonage number is working fine for outbound calls but shows "line busy" for inbound calls, while Twilio numbers are working correctly, the issue may not be directly tied to Vapi itself but could relate to the way the Vonage number has been integrated or possibly an issue on Vonage's end. For inbound calls, ensuring that an assistant is properly assigned to your imported Vonage number is crucial. As you mentioned you've done this through the dashboard, it's important to verify if the assistant setup and its configurations are correctly tailored for handling inbound calls [(1)]() . Additionally, checking the server URL setup and ensuring it's correctly handling incoming requests without errors is critical. Errors in handling requests on your server URL could lead to failed inbound call attempts. It's also worth considering potential issues not directly tied to Vapi but related to how Vonage manages inbound calls or how it interacts with Vapi. Since you've already reached out to Vonage support, they might be able to provide more insight into whether there's something on their end affecting the inbound call functionality. If the issue persists and you've ensured that your Vapi and server setups are correct, monitoring the Vapi's documentation or reaching out for support might provide further assistance or updates on any known issues affecting the integration with Vonage numbers [(2)]() .

Got it. Tagging @User for additional help.

and sorry for the late reply man. I am in IST.

No prob mate