https://vapi.ai/ logo
Join Discord
Powered by
Hi Team! 👋
# general-english
y
Hi Team! 👋 I'm trying to get Vapi SIP to connect, and I’m running into some issues. Tried two different setups — neither worked, and hoping you can help me debug it: 1️⃣ Direct SIP Trunk to CallGear via “Add New SIP Trunk” I attempted to connect Vapi directly to a CallGear SIP account using the “Add New SIP Trunk” form inside Vapi. (configuration in the thread below) 🛑 Problem: — Vapi UI allowed me to save the configuration — But no calls or registration occurred — CallGear reported no registration attempts from Vapi — No SIP traffic or logs on CallGear’s side 2️⃣ Proxy SIP via Local Asterisk + Ngrok Tunnel I set up a local Asterisk 18.11.2 instance inside Docker and exposed it via ngrok TCP tunnel (configuration in the thread below) 🛑 Problem: — Asterisk endpoint stayed Unavailable in pjsip show endpoints — pjsip set logger on showed no incoming REGISTER or SIP traffic — Confirmed ngrok tunnel was active and open — Vapi appeared to not initiate any connection ❓ Help Needed In the CallGear setup: — does Vapi fully support registering to external SIP providers like CallGear? In the proxy setup: — Does Vapi support TCP-based SIP over custom ports? — Does Vapi initiate REGISTER automatically after saving a SIP trunk? https://cdn.discordapp.com/attachments/1211484481848873020/1364569176726966402/Screenshot_2025-04-23_at_13.37.29.png?ex=680a2594&is=6808d414&hm=5297468c431be585022d3bd725b3d65b8af52f5b10a43227fe93a22348a9e23b&
Configuration: Gateway (SIP Server): sipve.callgear.com (actual domain provided by CallGear) Port: 9060 Protocol: udp Direction: Inbound & Outbound Options Ping: disabled Username / Password: provided by CallGear SIP Registration: Enabled Domain: sip.callgear.com Username: same as trunk username Realm: sip.callgear.com https://cdn.discordapp.com/attachments/1364569176965910599/1364569621541158983/Screenshot_2025-04-23_at_13.46.08.png?ex=680a25fe&is=6808d47e&hm=ff8014da0e389d38c033e7c1d70d0cc998bbadcb63cc01a74d8a9ff33b0b84c8& https://cdn.discordapp.com/attachments/1364569176965910599/1364569622103330847/Screenshot_2025-04-23_at_13.42.15.png?ex=680a25fe&is=6808d47e&hm=9447fa985a2a74f77a95174a660712b9325a9a67467862f4591eede7b9c915a6& https://cdn.discordapp.com/attachments/1364569176965910599/1364569622606643260/Screenshot_2025-04-23_at_13.41.58.png?ex=680a25fe&is=6808d47e&hm=42189bd08b8d4412a1ea222adea1359794eb49900507362dc4f8d83f303eeb00&
s
cc: @Nir Simionovich (CEO@Cloudonix) might be able to provide some help here.
n
@Sahil thanks for the ping
@YellowGlassesDude Your connection to CallGear will not work. As with many other Cloud PBX systems, they require that your remote endpoint must be registered to their platform. VAPI SIP trunking doesn't perform registration, as it doesn't behave like a user-agent, it's a server. To enable such functionality, VAPI will be required to implement a full B2BUA SBC - which is beyond the scope of their platform. If you would like, you can use Cloudonix and our experimental SBC connector to do the connection. Right now it's a manual setup that I need to do for you, but later on, you'll be able to manage it directly from your management console.
y
Thanks, now I see what the nuance is — yes, let’s try the Cloudonix and SBC connector option 👍 Would you be able to help with the steps? What do I need to do on my side?
n
well, first you need to setup an account with Cloudnix at cloudonix.com
then we can continue
y
n
@YellowGlassesDude Great - now follow this link https://calendly.com/cloudonix/cloudonix-vapi-integration and pin a meeting on my calendar, so we can do this the organized way 🙂
12 Views
PreviousNext
Powered by