equal-aqua•5mo ago

my sip trunk is connected but it is not working

It says, An error occurred in this call: "call.in-progress.error-sip-telephony-provider-failed-to-connect-call". My sip provider says they are not receving any data, please help me solve this issue

26 Replies

equal-aquaOP•5mo ago

i dont know how to solve it and its quite urgent

Vapi Support Bot•5mo ago

To resolve the call.in-progress.error-sip-telephony-provider-failed-to-connect-call error, please ensure you have allowlisted the following Vapi IP addresses in your SIP provider's firewall or network settings:

44.229.228.186/32
44.238.177.138/32

44.229.228.186/32
44.238.177.138/32

This step is required for SIP signaling and media to work between Vapi and your provider. After allowlisting, try your call again.
See Vapi SIP trunking network requirements Sources: - Vapi SIP Trunking Network Requirements - Vapi Call Ended Reasons

⤵️ Mention @Vapi Support Bot for follow-ups 🐥

Vapi Support Bot•5mo ago

Thanks for sharing the error details. To help troubleshoot, could you confirm if you have allowlisted the required Vapi SIP signaling IP addresses (44.229.228.186/32 and 44.238.177.138/32) on your SIP provider's firewall or portal? Sources: - Call ended reasons (Vapi documentation) - SIP trunk setup and network requirements (Vapi documentation) Thanks for sharing the details.
Based on the error and your provider not receiving data, a common cause is missing network allowlisting.
Have you allowlisted the required Vapi SIP IPs (44.229.228.186/32 and 44.238.177.138/32) in your SIP provider's firewall or network settings?
This is often necessary for proper SIP signaling and media flow (see documentation). Sources: - Vapi Call Ended Reasons - Vapi SIP Trunk Network Requirements

equal-aquaOP•5mo ago

yes we have allowlisted the required Vapi SIP IPs

Vapi Support Bot•5mo ago

Thanks for confirming that you have allowlisted the required Vapi SIP IPs. Since your SIP provider is still not receiving any data and the main network configuration step has already been completed, it sounds like you've covered the most common cause for this error. If you have recently made changes, sometimes it can help to double-check that the changes have taken effect and that there are no additional network restrictions or firewall rules in place. If everything looks correct on your end, you might want to review any recent changes to your SIP trunk configuration or check for any service interruptions on either side. Let me know if there are any other details you can share about your setup or recent changes, and I'll do my best to help!

Kyle Brunker•5mo ago

Hey, can you share the latest call_id?

equal-aquaOP•5mo ago

77df13d4-0555-4b40-94ed-a7a487c955c7 this is the id

equal-aquaOP•5mo ago

equal-aquaOP•5mo ago

it says this

Vapi Support Bot•5mo ago

I understand how urgent and frustrating this situation is, especially since you've already taken the main recommended steps like allowlisting the required IPs. At this point, you've covered the most common causes for this error. If there are any recent changes or additional details about your setup, sharing those could help narrow things down further. I'm here to help however I can as you work through this. I understand this issue is quite urgent and appreciate you providing all the necessary details, including the call ID and confirmation that the required IPs are allowlisted. If there are any other specifics about your setup or recent changes that you can share, please let me know—I'm here to help and will do my best to assist you further. Next step:
After confirming the IP allowlisting, please double-check that your SIP trunk configuration in both Vapi and your SIP provider's portal matches exactly—especially the SIP server address, authentication credentials, and phone number/DID mapping. Even a small mismatch can prevent calls from connecting.
Example checklist: - SIP server address (e.g., sip.provider.com) is correct in Vapi. - Username/password (if used) are accurate. - The phone number is linked to the correct SIP trunk credential. If all details are correct and the issue persists, consider reaching out to Vapi support with your call ID for deeper investigation.
See Vapi SIP trunk setup steps Sources: - Vapi SIP Trunking Network Requirements - Vapi SIP Trunking Setup Process Since you have already allowlisted the required Vapi SIP IPs, the next best step is to carefully review your SIP trunk configuration for any errors or recent changes that might block SIP signaling or media. If everything appears correct and your provider is not experiencing outages, please contact Vapi support and provide your call ID (77df13d4-0555-4b40-94ed-a7a487c955c7) for deeper investigation.
Tip: Double-check that all changes have taken effect and no additional firewall or NAT rules are interfering with SIP traffic.
See Vapi SIP trunking network requirements Sources: - Vapi SIP Trunking Network Requirements - Vapi Call Ended Reasons Next step:
Please verify your SIP trunk configuration in Vapi to ensure all required details are correct. For example, your setup should look like this (replace with your actual values):

curl -X POST "https://api.vapi.ai/credential" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_VAPI_PRIVATE_KEY" \
  -d '{
    "provider": "byo-sip-trunk",
    "name": "Your Trunk Name",
    "gateways": [{ "ip": "your.sip.provider.com" }],
    "outboundAuthenticationPlan": {
      "authUsername": "YOUR_SIP_USERNAME",
      "authPassword": "YOUR_SIP_PASSWORD"
    }
  }'

curl -X POST "https://api.vapi.ai/credential" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_VAPI_PRIVATE_KEY" \
  -d '{
    "provider": "byo-sip-trunk",
    "name": "Your Trunk Name",
    "gateways": [{ "ip": "your.sip.provider.com" }],
    "outboundAuthenticationPlan": {
      "authUsername": "YOUR_SIP_USERNAME",
      "authPassword": "YOUR_SIP_PASSWORD"
    }
  }'

Double-check that all signaling IPs are included and credentials are correct. If the issue persists, please contact Vapi support with your call ID for deeper investigation.
Reference: Vapi SIP Trunk Setup Sources: - Vapi SIP Trunk Setup - Vapi Call Ended Reasons

equal-aquaOP•5mo ago

please help @Shubham Bajaj @Vapi Team

Vapi Support Bot•5mo ago

Please double-check your SIP trunk configuration in Vapi for any errors. Your setup should look like this (replace with your actual values):

curl -X POST "https://api.vapi.ai/credential" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_VAPI_PRIVATE_KEY" \
  -d '{
    "provider": "byo-sip-trunk",
    "name": "Your Trunk Name",
    "gateways": [{ "ip": "your.sip.provider.com" }],
    "outboundAuthenticationPlan": {
      "authUsername": "YOUR_SIP_USERNAME",
      "authPassword": "YOUR_SIP_PASSWORD"
    }
  }'

curl -X POST "https://api.vapi.ai/credential" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_VAPI_PRIVATE_KEY" \
  -d '{
    "provider": "byo-sip-trunk",
    "name": "Your Trunk Name",
    "gateways": [{ "ip": "your.sip.provider.com" }],
    "outboundAuthenticationPlan": {
      "authUsername": "YOUR_SIP_USERNAME",
      "authPassword": "YOUR_SIP_PASSWORD"
    }
  }'

If all details are correct and the error persists, please contact Vapi support with your call ID for deeper investigation.
Reference: Vapi SIP Trunk Setup Sources: - Vapi SIP Trunk Setup - Vapi Call Ended Reasons

equal-aquaOP•5mo ago

yes i have double checked my SIP trunk configuration it is configured successfully

Vapi Support Bot•5mo ago

Since you've already confirmed your SIP trunk configuration and allowlisting are correct, the best next step is to contact Vapi support with your call ID for deeper investigation. Please provide your call ID and a summary of the troubleshooting steps you've taken so far. This will help the support team quickly review backend logs and assist you further.
Reference: Vapi SIP Trunk Setup Sources: - Vapi SIP Trunk Setup - Vapi Call Ended Reasons Since you've already confirmed your SIP trunk configuration and allowlisting are correct, the best next step is to contact Vapi support directly with your call ID for a deeper investigation. Please include any relevant details about your setup and recent changes when reaching out. This will help the support team diagnose the issue more efficiently. Reference: Vapi SIP Trunk Setup Sources: - Vapi SIP Trunk Setup - Vapi Call Ended Reasons

equal-aquaOP•5mo ago

Can i connect with vapi engineer on a google meet??

Vapi Support Bot•5mo ago

Vapi does not explicitly offer Google Meet sessions as a standard support channel in its documentation.
To request a live session with a Vapi engineer, please email support@vapi.ai with your call ID, a summary of your issue, and your request for a Google Meet. The support team will review your case and let you know if a live session can be arranged. Contact:
- Email: support@vapi.ai
- Include: Call ID, troubleshooting steps, and your request for a Google Meet For urgent or enterprise issues, mention the urgency in your message for prioritized handling. Source: - Vapi Support Options To request a live meeting with a Vapi engineer, please email support@vapi.ai with your call ID, a summary of your issue, and explicitly request a Google Meet or live call for urgent troubleshooting. If you are an enterprise customer, mention this in your message for priority handling. The support team will advise on next steps and whether a meeting can be arranged. Sources: - Vapi Support Options - Vapi Enterprise Plans

equal-aquaOP•5mo ago

ok then please try to resolve my issue here itself, these are the screenshot given by the sip provider. The sip is connected sucessfully but it is unable to comunicate

Vapi Support Bot•5mo ago

Please ensure your SIP trunk credential in Vapi includes the correct authUsername and authPassword for your SIP provider.
Here's the code snippet for reference—replace with your actual values:

curl -X POST "https://api.vapi.ai/credential" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_VAPI_PRIVATE_KEY" \
  -d '{
    "provider": "byo-sip-trunk",
    "name": "Your Trunk Name",
    "gateways": [{ "ip": "your.sip.provider.com" }],
    "outboundAuthenticationPlan": {
      "authUsername": "YOUR_SIP_USERNAME",
      "authPassword": "YOUR_SIP_PASSWORD"
    }
  }'

curl -X POST "https://api.vapi.ai/credential" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_VAPI_PRIVATE_KEY" \
  -d '{
    "provider": "byo-sip-trunk",
    "name": "Your Trunk Name",
    "gateways": [{ "ip": "your.sip.provider.com" }],
    "outboundAuthenticationPlan": {
      "authUsername": "YOUR_SIP_USERNAME",
      "authPassword": "YOUR_SIP_PASSWORD"
    }
  }'

If your credentials are set correctly and the issue persists, please contact Vapi support with your call ID for further investigation.
Reference: Vapi SIP Trunk Setup Source: - Vapi SIP Trunk Setup Your SIP trunk is reachable, but the error "No auth credentials for any realms in context" means authentication details are missing or incorrect.
Please update your SIP trunk credential in Vapi to include the correct authUsername and authPassword:

curl -X PATCH "https://api.vapi.ai/credential/YOUR_CREDENTIAL_ID" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_VAPI_PRIVATE_KEY" \
  -d '{
    "provider": "byo-sip-trunk",
    "name": "Your Trunk Name",
    "gateways": [{ "ip": "your.sip.provider.com" }],
    "outboundAuthenticationPlan": {
      "authUsername": "YOUR_SIP_USERNAME",
      "authPassword": "YOUR_SIP_PASSWORD"
    }
  }'

curl -X PATCH "https://api.vapi.ai/credential/YOUR_CREDENTIAL_ID" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_VAPI_PRIVATE_KEY" \
  -d '{
    "provider": "byo-sip-trunk",
    "name": "Your Trunk Name",
    "gateways": [{ "ip": "your.sip.provider.com" }],
    "outboundAuthenticationPlan": {
      "authUsername": "YOUR_SIP_USERNAME",
      "authPassword": "YOUR_SIP_PASSWORD"
    }
  }'

After updating, test your call again. If the issue persists, contact Vapi support with your call ID for further investigation.
Reference: Vapi SIP Trunk Setup Source: - Vapi SIP Trunk Setup

rare-sapphire•5mo ago

To help track down this issue, could you share one or two: - The call ID - 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!

Vapi Support Bot•5mo ago

To help resolve your issue:
Have you already updated your SIP trunk credentials in Vapi to include the correct authUsername and authPassword as shown in the documentation, and if so, are you still seeing the same authentication error?
This will help determine the next troubleshooting step. Source: - Vapi SIP Trunk Setup

equal-aquaOP•5mo ago

the call is not even connecting, thats the main issue

Vapi Support Bot•5mo ago

Thank you for clarifying that the call is not connecting at all. Have you recently updated your SIP trunk credentials in Vapi (specifically authUsername and authPassword), and are you still seeing the same authentication error in your SIP provider's logs after doing so? This will help determine if the issue is with the credentials or if further investigation is needed. If you have already updated them and the error persists, please let me know so I can suggest the next step. Source: - Vapi SIP Trunk Setup Please update your SIP trunk credential in Vapi to include the correct authentication details, as missing or incorrect credentials are a common cause of connection failures.
Use the following command (replace with your actual values):

curl -X PATCH "https://api.vapi.ai/credential/YOUR_CREDENTIAL_ID" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_VAPI_PRIVATE_KEY" \
  -d '{
    "provider": "byo-sip-trunk",
    "name": "Your Trunk Name",
    "gateways": [{ "ip": "your.sip.provider.com" }],
    "outboundAuthenticationPlan": {
      "authUsername": "YOUR_SIP_USERNAME",
      "authPassword": "YOUR_SIP_PASSWORD"
    }
  }'

curl -X PATCH "https://api.vapi.ai/credential/YOUR_CREDENTIAL_ID" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_VAPI_PRIVATE_KEY" \
  -d '{
    "provider": "byo-sip-trunk",
    "name": "Your Trunk Name",
    "gateways": [{ "ip": "your.sip.provider.com" }],
    "outboundAuthenticationPlan": {
      "authUsername": "YOUR_SIP_USERNAME",
      "authPassword": "YOUR_SIP_PASSWORD"
    }
  }'

After updating, test your call again. If the call still does not connect, please contact Vapi support with your call ID for further investigation.
Reference: Vapi SIP Trunk Setup Source: - Vapi SIP Trunk Setup To clarify and help resolve your issue:
Have you already updated your SIP trunk credentials in Vapi to include the correct authUsername and authPassword, and are you still seeing the "No auth credentials for any realms in context" error when attempting to connect? This will help determine the next troubleshooting step. Source: - Vapi SIP Trunk Setup

exotic-emerald•5mo ago

@meer sheikh Based on your screenshots, looks like you are trying to configure an Asterisk server that is running Vicidial to work together with VAPI? If I'm correct, I'm sorry to tell you that the way Vicidial works and VAPI aren't as compatible as you would like them to be. I've helped multiple Vicidial customers to connect to VAPI over the past 2 months, so feel free to DM me and I'll help you connect it via Cloudonix, which will "translate" between the two platforms.

Vapi Support Bot•5mo ago

To resolve the "No auth credentials" error, update your SIP trunk credential in Vapi to include your SIP provider's authUsername and authPassword. Use the following command (replace with your actual values):

curl -X PATCH "https://api.vapi.ai/credential/YOUR_CREDENTIAL_ID" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_VAPI_PRIVATE_KEY" \
  -d '{
    "provider": "byo-sip-trunk",
    "name": "Your Trunk Name",
    "gateways": [{ "ip": "your.sip.provider.com" }],
    "outboundAuthenticationPlan": {
      "authUsername": "YOUR_SIP_USERNAME",
      "authPassword": "YOUR_SIP_PASSWORD"
    }
  }'

curl -X PATCH "https://api.vapi.ai/credential/YOUR_CREDENTIAL_ID" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_VAPI_PRIVATE_KEY" \
  -d '{
    "provider": "byo-sip-trunk",
    "name": "Your Trunk Name",
    "gateways": [{ "ip": "your.sip.provider.com" }],
    "outboundAuthenticationPlan": {
      "authUsername": "YOUR_SIP_USERNAME",
      "authPassword": "YOUR_SIP_PASSWORD"
    }
  }'

After updating, test your call again. If the issue persists, please contact Vapi support with your call ID for further help. Source: - Vapi SIP Trunk Setup To resolve the "No auth credentials for any realms in context" error, update your SIP trunk credentials in Vapi to include the correct authUsername and authPassword.
Use the following command (replace placeholders with your actual details):

curl -X PATCH "https://api.vapi.ai/credential/YOUR_CREDENTIAL_ID" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_VAPI_PRIVATE_KEY" \
  -d '{
    "provider": "byo-sip-trunk",
    "name": "Your Trunk Name",
    "gateways": [{ "ip": "your.sip.provider.com" }],
    "outboundAuthenticationPlan": {
      "authUsername": "YOUR_SIP_USERNAME",
      "authPassword": "YOUR_SIP_PASSWORD"
    }
  }'

curl -X PATCH "https://api.vapi.ai/credential/YOUR_CREDENTIAL_ID" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_VAPI_PRIVATE_KEY" \
  -d '{
    "provider": "byo-sip-trunk",
    "name": "Your Trunk Name",
    "gateways": [{ "ip": "your.sip.provider.com" }],
    "outboundAuthenticationPlan": {
      "authUsername": "YOUR_SIP_USERNAME",
      "authPassword": "YOUR_SIP_PASSWORD"
    }
  }'

After updating, test your call again. If the issue persists, please contact Vapi support with your call ID for further investigation.
Reference: Vapi SIP Trunk Setup Source: - Vapi SIP Trunk Setup

equal-aquaOP•5mo ago

we are using PBX Device GSM gateway to connect

Kyle Brunker•5mo ago

Hey, can you book a quick call and we can discuss it over there? https://calendly.com/sahil-vapi

my sip trunk is connected but it is not working

Did you find this page helpful?