Created SIP trunk, Associated with phone number, tested called but getting SIP 480 Temporarily Unavailable. Please help { "assistantId": "3aaebee3-239a-435e-b73d-df1bb9a72079", "customer": { "number": "+98765432111", "numberE164CheckEnabled": false }, "phoneNumberId": "74cfc695-9cbb-49cd-baae-5b9d3e7359da" } { "id": "9ebe6d94-2962-4d1e-a81c-cf5007352237", "assistantId": "3aaebee3-239a-435e-b73d-df1bb9a72079", "phoneNumberId": "74cfc695-9cbb-49cd-baae-5b9d3e7359da", "type": "outboundPhoneCall", "createdAt": "2025-03-12T14:04:09.546Z", "updatedAt": "2025-03-12T14:04:09.546Z", "orgId": "289e9a2a-f610-4141-8aff-3c9ad3891cee", "cost": 0, "customer": { "number": "+98765432111", "numberE164CheckEnabled": false }, "status": "queued", "phoneCallProvider": "vapi", "phoneCallProviderId": "1647f045-aba0-4cbd-884b-dca62cc54398", "phoneCallTransport": "pstn", "phoneCallProviderDetails": { "sbcCallId": "b607405d-79ed-123e-c389-fa0f31a4279b" }, "monitor": { "listenUrl": "wss://phone-call-websocket.aws-us-west-2-backend-production2.vapi.ai/9ebe6d94-2962-4d1e-a81c-cf5007352237/listen", "controlUrl": "https://phone-call-websocket.aws-us-west-2-backend-production2.vapi.ai/9ebe6d94-2962-4d1e-a81c-cf5007352237/control" }, "transport": {} } https://cdn.discordapp.com/attachments/1349760652797022308/1349760652914331648/sip_log.txt?ex=67d44610&is=67d2f490&hm=22eea7461ffeed6e84b897cee00c307a662888423b78c282fc34a98e4b8e0634&

@Vladimir can you try making another call the issue must have been resolved for you by now?

The only issue I experience is a dead air from VAPI when I call to AI assistant. From me to VAPI no speech delivered to AI assistant as Assistant does not respond me and disconnects in 30 seconds by SIP trunk associated with phone number https://docs.vapi.ai/advanced/sip/sip-trunk while responds when I call on twilio number associated with same assistant. From VAPI to me it is all fine. I hear well what assistant says.

@Vladimir can you share the call ID so I could take a look?

please check these calls. there is no dead any more. but the issue is call record is few seconds but the call itself lasts few minutes. here are calls ids b9dbfe30-7d4b-4393-9ee9-c7282e5966c4 0689c945-e3c8-46ca-bab7-146e932b9265 18187c23-f1ad-40b5-9d96-e0f59b43bb5c

@Vladimir I see all of your these calls have call ended with reason

phone-call-provider-closed-websocket

which indicates successful calls. To determine if a call was unsuccessful, it is necessary to utilize successEvaluation. It is important to note Telephony terminated the connection from their end in this instance. We successfully answered the call and established the connection without any issues on our part. In summary, the

phone-call-provider-closed-websocket

typically signifies that the individual has ended the call.

The call log status is quite confusing. So why is "Phone Call Provider Closed Websocket" not labeled as just "Customer Ended Call" ? and why are there calls with "Customer Did Not Answer" with call duration and recordings?

Hey Max,I know that this is quite confusing. Phone call provider closed websocket as mentioned means the call was ended successfully, but because of SIP involved this got labeled with this weird error region. It's on our plan to change it. Regarding SIP gateway failed to connect, it doesn't mean customer did not answer. That means the telephony (either VAPI or your telephony) has some issues connecting with each other. For search errors, please create a new support ticket and share your call ID over there. I'll take a look and let you know.

Marking this ticket as Solved ✅