Getting status ringing in webhook when the call ha...
# support
m
The call was made yesterday and it cannot be still ringing for more than 12 hours.
Copy code
{
  "id": "ac0bf2d9-5ac6-42bf-b745-9de08802673d",
  "assistantId": "39d37de5-86f5-4214-8943-cd60ae7641ab",
  "phoneNumberId": "65a88a31-cc7f-4d88-bec4-5139567e48b4",
  "type": "outboundPhoneCall",
  "createdAt": "2024-12-26T14:49:53.978Z",
  "updatedAt": "2024-12-26T14:50:03.129Z",
  "orgId": "d1ca7720-1232-4cbe-b74b-479b00f9f83a",
  "cost": 0,
  "customer": {
    "number": "+919015153526",
    "name": "Yash Dhiman"
  },
  "status": "ringing",
  "endedReason": "customer-busy",
  "metadata": {
    "contact_id": "j3poyGD",
    "campaign_id": "7y9ma9o",
    "campaign_lead_id": "0DYrOA3"
  },
  "phoneCallProvider": "twilio",
  "phoneCallProviderId": "CAbb8c470766879dc614e16eb0719a35c0",
  "phoneCallTransport": "pstn",
  "assistantOverrides": {
    "variableValues": {
      "email": "dyash1810@gmail.com",
      "last_name": "Dhiman",
      "first_name": "Yash",
      "pnt_amount": "300",
      "deposit_date": "2024-12-10T17:28:02.466+0000",
      "phone_number": "+919015153526",
      "pnt_currency": "INR"
    }
  },
  "monitor": {
    "listenUrl": "wss://phone-call-websocket.aws-us-west-2-backend-production2.vapi.ai/ac0bf2d9-5ac6-42bf-b745-9de08802673d/listen",
    "controlUrl": "https://phone-call-websocket.aws-us-west-2-backend-production2.vapi.ai/ac0bf2d9-5ac6-42bf-b745-9de08802673d/control"
  },
  "transport": {}
}
v
@Manan Khurana I understand your concern. It seems there might be an issue with the call status not updating correctly after the call ended. The status indicates that the call is still "ringing," which is not possible for such a long duration. Rest assured, I will look into this matter and ensure that the call status is updated to reflect the correct state. If you need any further assistance or have any more details to provide, please let me know.
You can continue this conversation by mentioning me in the message.
Got it. Tagging @User for additional help.
m
one more example. call id: e40dd4f9-ec0e-42ca-8483-375d641e5a55
@User
s
logs
🔵 14:54:55:225 Call
ac0bf2d9-5ac6-42bf-b745-9de08802673d
Waited 300s But Transport Never Connected. @Manan Khurana teleophony failed to connect your call.
You have to check with your telephony for this.
m
Sure @Shubham Bajaj I'll check with them, but when i visited dashboard for the same call, the end reason was "Customer busy". We didn't receive the webhook for the same. So it got stuck on ringing on our end. Questions: 1. If the call never connected on telephony, the status should not be customer busy rather a twilio or telephony error or something? 2. If the call was never connected for whatever reason, i should get a webhook so that i can update the status and any other related information. https://cdn.discordapp.com/attachments/1322077414779781221/1324349932248895560/image.png?ex=6777d47d&is=677682fd&hm=78305a10e8e5aa1715f16aaae474170e3435feec537671a30b040ba70c83f2f8&
cc: @Yash
s
@Manan Khurana answered the same in another thread. FYI: If calls are not connected or picked by the customer then you won’t get the end of call report for it.