Yesterday's calls were working okay, but all the calls I made today resulted in the same connection error: call.in-progress.error-sip-outbound-call-failed-to-connect. No changes in the assistant since 27/06/25 With our testing phone, the call actually arrives but stays silent and the connection drops. Call id: 979f0f49-56ab-4ddb-8b44-ab27af1c354b Timestamp: Every call today, but for this specific id 19:36 utc. Any logs on your guys side so that I can validate what happened?

@Isoca Where did you connect VAPI to? Is that to your own PBX system?

Kinda, we have an enterprise account with a local 3rd party that provides the pbx service. Was it an specific issue connecting with them?

I don't know - but many of them can't connect directly to VAPI (and other AI platforms) - simply because they lack the proper tech stack to do it. Which provider is it ?

Sonax. The problem is that it was working fine for the entire month of june: 3e8c4fe3-29ee-4b12-bd83-e1aac0570c6d On 01/07/25 at 13:06 connected fine. I can check multiple other examples where the call connected and there was some kind of voice not error. The calls currently are connecting when I check on their dashboard and on the testing phone, it just stays silent. So I'm looking for more information

We are reviewing the details of your request and will reach out to you when we have an update or if we need additional information.

Hello! Any news? I will have to start testing alternatives soon. I tried connecting to the phone using microsip ✅️ which worked Tried connecting only from the phone in vapi ignoring the assistant ❌️ did not work Also tried another number also using sip integration, error changed to customer-busy but did not connect (this number isnt really thrustworthy so not getting to hung up on this)

Hey, can you book a quick call and we can discuss it over there? 

Booked the call, but update, talked with sonax, according to them the sip.vapi.ai is weird, and should be ipbx.sonax.net.br, as it is on the credentials used. https://cdn.discordapp.com/attachments/1390059175798771875/1391865091821142126/Sem_titulo.jpg?ex=686d72e1&is=686c2161&hm=585fefd4626a2c6a039985db152b311e3fa363c7863d0a7080d8d4943246e411& https://cdn.discordapp.com/attachments/1390059175798771875/1391865092152234034/Sem_titulo.jpg?ex=686d72e1&is=686c2161&hm=d0266e6c88debfeacd8410420f2743c3062a3628e2ceadc9079b0dcd8352eb13&

@Isoca This means that sonax expect VAPI to do a

SIP Register

to their PBX system, which is a functionality of a B2BUA (or SBC). You should perform the integration via Cloudonix or Jambonz, in order to properly maintain the

SIP Registration

with sonax. This is a common issue with PBX providers around the world.

Still does not make sense to me that I need a B2BUA. If it never worked, fine. But it started giving the connect error on july 3rd. I will speak with sonax again with this info. I still would like to compare the logs with calls from july 2nd.

Well, if it worked and then stopped - that's a different story completely

Looking forward to chatting with you soon!