Has anyone experienced an issue with this setup? We've previously managed to make it work, but it suddenly stopped working today. When we dial the GHL number it doesn't forward to Vapi and we hear something "please enter password". Then inside Vapi call logs it shows as "Call.ringing.sip inbound caller hungup before call connect."

Action Step: Check the call ended reason in your Vapi call logs to confirm if forwarding was initiated. Use the following API call (replace

{call_id}

and

YOUR_API_KEY

):

bash
curl -X GET "https://api.vapi.ai/call/{call_id}" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json"

If the

endedReason

is not

"assistant-forwarded-call"

, review your telephony provider's configuration, as the "please enter password" prompt suggests an issue on their end. See more in the [Debug call forwarding drops guide](https://docs.vapi.ai/phone-calling/in-call-control/transfer-calls/debug-forwarding-drops). Source: - [Debug call forwarding drops](https://docs.vapi.ai/phone-calling/in-call-control/transfer-calls/debug-forwarding-drops)

do u have API from GHL, that will solve the issue @User

Hi @Subhankar Ghosh, what do you suggest we do with the API from GHL?

texted u @User

please provide the GHL number you used in VAPI where this occurred