Calls succeed in SIP trunk, but Vapi shows endedRe...
# support
i
Hi Vapi team, I’m seeing outbound calls that work correctly in my SIP trunk/provider, but in Vapi the same attempts are logged as: status: ended endedReason: customer-busy phoneCallProviderDetails.sipStatus: 603 phoneCallProviderDetails.sipReason: Decline Example recent calls: 019d8ccf-75a9-7aa9-a4f8-a3c496150dda 019d8ccb-d59c-744c-9d17-fb3ca01f28d0 019d8cca-9d14-7aa9-a48b-6f37c5841c61 019d8cca-2800-7000-8fd9-f97efdfc3fa6 019d8cc9-7b24-7ffa-997a-a5bf5c5e538e Question: Why is Vapi labeling these as customer-busy when the behavior on my trunk indicates the call flow is working? Is Vapi simply mapping SIP 603 Decline → customer-busy, or is something else causing the 603 to be generated/propagated?