https://vapi.ai/ logo
Join Discord
Powered by
Issue with Outbound Calls through Telnyx SIP and V...
# support
m
Hey everyone! 👋 I'm trying to set up outbound calling through VAPI using Telnyx as the SIP provider. I keep getting this persistent error:
Copy code
An error occurred in this call: call.in-progress.error-sip-telephony-provider-failed-to-connect-call
Inbound calls were working fine, but after attempting to configure outbound calling, I've been running into issues. What I've already checked: - Created proper SIP credentials in VAPI according to the documentation - Configured SIP Trunk in Telnyx (both inbound FQDN and outbound credentials) - Created an Outbound Voice Profile in Telnyx and assigned it to the SIP trunk - Tried initiating calls through VAPI API using the correct format with 
/call/phone
Configuration details: - API endpoint works correctly (status "queued") - Using 
customer.number
format for the destination number - The issue likely occurs at the communication level between VAPI and Telnyx Has anyone experienced a similar issue or have any ideas about what might be causing this? Any help would be greatly appreciated! Thanks in advance! 🙏​​​​​​​​​​​​​​​​
Could you please: Check if there are any logs on your side for the Call ID c506f620-e61b-4981-b751-6d2422d6f79f Confirm which specific mechanism VAPI uses to communicate with Telnyx for outbound calls (standard SIP, Call Control API, etc.) If I'd get the error code that would be amazing, because SIP logs aren't appearing in Telnyx's debugging tools, indicating either the SIP signaling isn't reaching Telnyx's infrastructure at all or it's being routed through an intermediary system whose communication isn't visible in standard SIP debugging logs.
n
@Marcello I've seen a similar issue to your description with BYO SIP trunks and also some other people reported a similiar issue with Twilio. I suspect this is not an isolated issue with Telnyx or other, but potentially an issue with the VAPI outbound call scheduler. I've relayed the issue to @Shubham Bajaj with a detailed description.
s
Hey @Nir S (CEO/Founder @Cloudonix) , I’m currently away and expect to be back in ~4 hours. I’ve seen your message and will review it as soon as I’m back online. If it’s urgent, feel free to ping me—I can jump in sooner if needed.
u
did it stop working or it has never worked since you set it up?
m
@20 it has never worked
@Shubham Bajaj Do you have some update? 🙏
a
Hey, could you follow this guide and send me the latest call_id if it doesn't work? I'll check the logs.
m
Yes, I have followed precisely the docs guide. The latest call ID is 68559743-ce1c-449c-ae90-e5af774a3e3c
I noticed in the VAPI documentation for Telnyx integration, there's mention of configuring the "Translated Number" field in Telnyx to match a VAPI SIP URI (format: sip:@sip.vapi.ai). However: The Telnyx "Translated Number" field only accepts numerical values (no @ or . characters) This field's description states it only affects inbound calls (which are working fine) I'm unsure if I need to create a "Free VAPI SIP" URI in addition to my Telnyx SIP configuration Could these issues be affecting my outbound calls? Do I need to set up a VAPI SIP URI somewhere for outbound calls to work properly, and if so, how do I properly link it with my Telnyx configuration?
@User Any updates? 🙏
k
Looking into it
s
sent you my calendar link. Let's debug it together.
m
@Sahil thank you, I've responded to you
c
What was the resolution for this @Marcello @Sahil ? Facing the same issue with Telnyx right now as well
a
Glad the issue was resolved. Please reach out to us if you have any other questions regarding this issue
PreviousNext
Powered by