I followed the Steps of SIP trinking doc to create...
# support
d
THe number is listed on the Vapi dashboard, the Call create API Calls are getting 200 response but there are not calls going (I Tested calling my own Number). I don't see any errors in the logs. How can I debug?
v
message has been deleted
@donnydjaco12 I'm sorry to hear you're experiencing issues with the Create Phone Call API. Here are some steps you can take to debug the situation: 1. **Check API Request Details**: Ensure that the API request is being made with the correct parameters, including the
to
and
from
phone numbers, and that the numbers are in the correct E.164 format (e.g., +15551234567). 2. **Review Account Configuration**: Verify that your VAPI account has the correct permissions and that there are no restrictions that might be preventing outbound calls. 3. **Inspect Webhook URLs**: If you're using webhooks to handle call events, make sure that the URLs are correctly configured and that the server handling the webhooks is receiving and responding to the events as expected. 4. **Check Network and Firewall Settings**: If you're making API calls from a server, ensure that your network and firewall settings allow outbound HTTP requests to VAPI's API endpoints. 5. **Examine Call Logs**: Even if there are no errors in the logs, look for any warnings or unusual patterns that might indicate what's going wrong. 6. **Test with a Different Number**: Try making a call to a different number to see if the issue is with the specific number you're trying to reach. 7. **Contact Support**: If you've gone through these steps and still can't identify the issue, it's best to reach out to VAPI support for further assistance. They may be able to provide more detailed logs or insights into what's happening. If you would like me to assist you further, please provide more details about the API request you're making, such as the payload you're sending (with sensitive information redacted), and I can help you troubleshoot from there.
You can continue this conversation by mentioning me in the message.
Got it. Tagging @User for additional help.
s
@donnydjaco12 could you share the recent call id so I could take a look?
d
Yes let me share
ID -c1138521-5ba4-4235-bb30-b562a800752f Response - {'id': 'c1138521-5ba4-4235-bb30-b562a800752f', 'assistantId': 'e5d4014c-1c2e-4118-990a-73096519542a', 'phoneNumberId': 'e8132b03-aebd-49b9-9004-a408c3e2f52c', 'type': 'outboundPhoneCall', 'createdAt': '2025-01-20T06:50:02.805Z', 'updatedAt': '2025-01-20T06:50:02.805Z', 'orgId': '14212ef9-39f7-4753-95b5-9a4d14aa4a08', 'cost': 0, 'customer': {'number': '+919920512044'}, 'status': 'queued', 'phoneCallProvider': 'vapi', 'phoneCallProviderId': '151e48d5-2f06-4558-89ae-9fcc3cb4ba2d', 'phoneCallTransport': 'pstn', 'monitor': {'listenUrl': 'wss://phone-call-websocket.aws-us-west-2-backend-production3.vapi.ai/c1138521-5ba4-4235-bb30-b562a800752f/listen', 'controlUrl': 'https://phone-call-websocket.aws-us-west-2-backend-production3.vapi.ai/c1138521-5ba4-4235-bb30-b562a800752f/control'}, 'transport': {}}
Let me know if you need more details
s
@donnydjaco12 As shown in the screenshot, the telephony system blocked the outbound call because the server at 204.89.148.66 denied the request. This may be due to authorization or routing issues. The 403 Forbidden error indicates a possible authentication or permission problem. Please ensure credentials and access rules are configured correctly. Review the logs on 204.89.148.66 to identify the exact reason for the rejection. Additionally, we do not accept any traffic on our IPs - traffic should be directed to sip.vapi.ai instead. https://cdn.discordapp.com/attachments/1330765690227130398/1330912084048740483/Screenshot_2025-01-20_at_19.59.47.png?ex=678fb3f7&is=678e6277&hm=50ccf27060e434095c966cda94f2fce9d77bb7e936115fe50643fbe01ecaebf4&
d
Thanks a lot. Let me check with them