Message Hi Vapi Support, I need help troubleshooting an inbound calling setup from Netelip (Netelip vPBX) into Vapi. The issue is that inbound calls never appear in Vapi Call Logs / Sessions, and callers hear a short English message (about ~2 seconds) or the call ends immediately. On the Netelip side, the call shows as “Hang up” or “Busy/Occupied” with 0 seconds duration. Subject: Netelip SIP trunk inbound calls hang up, no Vapi call logs Message: Hi Vapi Support, We’re trying to receive inbound calls from Netelip (vPBX) into Vapi via BYO SIP Trunk, but calls immediately hang up and Vapi Call Logs stay empty (no session created). What we set up / tested: Vapi: BYO SIP Trunk created successfully, UDP 5060, inbound + outbound enabled, options ping enabled. Netelip: DID +34 910 05 30 14 routed to extension 616 (shows registered/green in Netelip). We also tried routing the DID as “Servidor SIP” → sip.vapi.ai with “Add + in e164” enabled. Same result. Netelip call history shows the inbound attempts, but status is “hang up / busy / ocupado”, duration 0s. In Vapi dashboard, Call Logs remain empty for those attempts. Could you confirm: The correct inbound SIP destination for providers (FQDN / IP allowlist) and any required headers/format. Whether you see any inbound SIP INVITEs from Netelip hitting our Vapi trunk (and if rejected, why). Any known compatibility requirements (transport, SRTP/TLS, codecs, registration vs IP auth) that could cause immediate hangup before a call log is created. Thanks.

Action Step: Please ensure that Netelip is forwarding inbound calls to the SIP URI in the format:

{your_phone_number}@{your_credential_id}.sip.vapi.ai

Also, make sure the following Vapi IPs are allowlisted in Netelip for SIP signaling: -

44.229.228.186/32

-

44.238.177.138/32

This is required for inbound calls to reach Vapi and appear in your Call Logs. Reference: Vapi SIP Trunk documentation Source: - [SIP Trunking Vapi Documentation](https://docs.vapi.ai/advanced/sip/sip-trunk)

Thank you so much.. but How can I get my CredentialId ? for that: {your_phone_number}@{your_credential_id}.sip.vapi.ai

Message marked as helpful by @Estefan! 🎉

Please

you got it working?

Once you create the SIP trunk via the Vapi API, the response will include a credentialId. Use that credentialId in your SIP URI like this:

sip:+E164_NUMBER@<credentialId>.sip.vapi.ai

That’s the value Netelip should route inbound calls to.