Hello! I’m developing an AI caller app with Vapi (Electron desktop). Connectivity works: I can list assistants, create a BYO SIP trunk, and import my DID. Issue: • When I start a demo call (POST /call/phone), the API returns a callId and the call appears in Vapi logs, but it is immediately rejected with different statuses (no ringing/connection). My setup: • Provider: . • SIP trunk credentialId: . • PhoneNumberId (from Vapi): . • AssistantId: . • SIP gateway host: , resolved IP: . • Auth: username= / password=** (registration , realm/domain: ). • Dial format: tried E.164 with “+” and without. • From: , To: . Recent failing calls: • callId • callId <894b88c8-e9a2-44e9-acf9-94b8af171dda Happy to provide full request/response snippets if needed. Thanks!

Hi 4DoorsMoreWhores, When your demo call is immediately rejected with different statuses and no ringing or connection occurs, several factors might be at play. Here’s a troubleshooting checklist based on common issues associated with calls being rejected: 1. **Check Call Ended Reason**: Verify the

endedReason

field in your call logs to understand why the call did not progress. You can find all possible reasons [here](https://docs.vapi.ai/calls/call-ended-reason). 2. **SIP Credential Configuration**: Ensure that your SIP trunk credentials are correctly set up. Check that

credentialId

is properly associated with the right configuration for your service provider. 3. **Connection Status**: Double-check that your network and SIP service provider configurations allow call traffic. Investigate telephony provider logs for any rejected connection attempts. 4. **Provider Settings**: Review the settings with your SIP provider to ensure their system isn’t blocking or rejecting the calls. Provider-specific settings sometimes need adjustments for compatibility with Vapi. 5. **Server Messages Configuration**: Make sure your assistant’s serverMessages configuration doesn't include

phone-call-control

unless you're managing call logic outside of Vapi. 6. **Call Control Settings**: Check if

phoneCallProviderBypassEnabled

is set correctly. It should typically be

false

unless custom call logic is implemented through your provider. 7. **Check SIP REFER Packets**: If you're using SIP and the call is not transferred correctly, analyze the SIP packets as detailed in our [debug call forwarding guide](https://docs.vapi.ai/phone-calling/transfer-calls/debug-forwarding-drops). By understanding these aspects, you can better isolate where the call process is breaking down. If the issue persists after these checks, you might need to verify your setup configurations with both Vapi and your SIP provider.