Vidmantas
11/26/2025, 9:07 AMAn error occurred in this call: call.start.error-get-transport which only seems to occur when calling out to US numbers. This is using Twillio provider and there are no logs on their end for this seemingly.
Sample Call ID: 019abf62-8bf8-711c-aa30-365ab1305709
Org ID: a266008d-460f-4c11-8a96-1fc935391154
Timestamp: 2025-11-26T08:58:17.976ZVapi Support Bot
11/26/2025, 9:08 AMcall.start.error-get-transport means Vapi could not retrieve transport information when starting the call.
To resolve this, please contact Vapi support and provide your call ID and account details for investigation, as recommended in the [Call ended reasons documentation](https://docs.vapi.ai/calls/call-ended-reason).
This is especially important since the issue is specific to US numbers and not immediately clear from your configuration.
Source:
- [Call ended reasons documentation](https://docs.vapi.ai/calls/call-ended-reason)tf-117
11/26/2025, 12:38 PMVidmantas
11/26/2025, 3:54 PMChiranjeet Mishra
11/28/2025, 12:48 AM/call endpoint for making outbound calls. Make sure to specify a phoneNumberId and a customer number correctly [here](https://docs.vapi.ai/calls/outbound-calling).
3. **Scheduling Calls**: To schedule, use the schedulePlan with the earliestAt parameter in ISO date-time format [here](https://docs.vapi.ai/calls/outbound-calling).
4. **Batch Calls**: For multiple calls, provide an array of customers in the API call [here](https://docs.vapi.ai/calls/outbound-calling).
5. **International Calls**: Ensure you're using an imported number since free numbers don't support international calling [here](https://docs.vapi.ai/phone-calling).
Check that you have the correct authorization and that your configuration meets these requirements. If the issue persists, verify the configurations in your account and the logs for any error codes to diagnose further.