https://vapi.ai/ logo
Join Discord
Powered by
SIP Direct (Free SIP) - Calls from external PBX ne...
# support
e
Goal: Transfer calls from our cloud PBX (MirtaPBX/Hostitel, Asterisk-based, chan_sip) to a Vapi assistant "Lidia" via SIP, preserving the original caller ID. What we configured in Vapi: Created a Free SIP endpoint named lidia-pbx No authentication (no username/password) Assistant "Lidia" assigned to this endpoint Assistant ID: 908cf588-1470-468a-bc94-9c9d1dd1454e What we configured in MirtaPBX: SIP Provider "Vapi-Lidia": Host: sip.vapi.ai Port: 5060 Transport: UDP From Domain: sip.vapi.ai NAT: Yes Qualify: No (Vapi doesn't respond to OPTIONS) Insecure: Port, Invite No registration (no username/password) Send RPID: Yes Trust RPID: Yes CallerID Presentation: Auto Privacy, CallerID not screened Codecs: G.711 u-law, G.711 A-law Custom Extension 814: Type: Custom Extension Unconditional forwarding to a Custom Destination Custom Destination "Vapi-Lidia": Type: Custom dial() with param. Dial Command: SIP/vapi_lidia/lidia-pbx Routing Rule (Profile Default): Regex: ^814$ Provider: Vapi-Lidia Digits to Add: lidia-pbx Digits to Delete: 3 Agent extensions (e.g. ext 103): Send RPID: Yes Trust RPID: Yes Block External Caller ID: unchecked All Dial Commands we tested (Custom Destination): Dial Command Result SIP/vapi_lidia/lidia-pbx 503 vapi_lidia/lidia-pbx 503 SIP/lidia-pbx@sip.vapi.ai:5060 503 lidia-pbx@sip.vapi.ai 603 908cf588-1470-468a-bc94-9c9d1dd1454e@sip.vapi.ai 603 Critical finding: We also tested calling sip:lidia-pbx@sip.vapi.ai directly from a softphone (Zoiper) registered on the PBX server - same result (603). This rules out any routing, extension, or transfer configuration issue. The SIP INVITE is simply not reaching Vapi. Zero call attempts appear in Vapi dashboard logs. Our assessment: This points to a network-level issue (firewall, DNS resolution, or UDP 5060 being blocked toward sip.vapi.ai) on the PBX hosting side (Hostitel). Please need help to set this ext from our side to call lidia-pbx
I add: Questions for Vapi team: What IP(s) does sip.vapi.ai resolve to? We want to ask Hostitel to explicitly whitelist them. Does Vapi require any specific SIP headers or authentication even for Free SIP endpoints? Is there any known issue with certain hosting providers or IP ranges being unable to reach sip.vapi.ai? Can you confirm what a valid inbound SIP INVITE should look like for the endpoint lidia-pbx? (Request-URI, required headers, etc.) Is there any way to test connectivity to sip.vapi.ai from our side (e.g. a health-check endpoint)? Any help is appreciated. We've exhausted all configuration options on our end. Thanks
a
Do you still need help getting this done or you already fix it? @Estefan
e
Still need help
@Adam still need help
a
Okay
I send you a friend request let’s connect
e
ok
Nobody answer form Vapi ??
a
As you can see
You accept? @Estefan
e
Subject: SIP Direct inbound INVITE gets 401 Unauthorized (Digest challenge) — Free SIP endpoint expected no-auth We captured a pcap from our PBX (Asterisk chan_sip). Our INVITE reaches sip.vapi.ai:5060/UDP and Vapi responds: SIP/2.0 100 Trying SIP/2.0 401 Unauthorized WWW-Authenticate: Digest realm="sip.vapi.ai", algorithm=MD5, qop="auth", nonce="..." INVITE target: INVITE sip:lidia-pbx@sip.vapi.ai:5060 SIP/2.0 (also tested assistantId 908cf588-1470-468a-bc94-9c9d1dd1454e) We created this as a Free SIP / SIP Direct endpoint with no auth. Our PBX trunk has no username/password. Therefore the call can never complete. Questions: Does SIP Direct / Free SIP actually require SIP Digest auth? If yes, where do we obtain the username/password? If it should be no-auth, why are we receiving a 401 challenge? Is there an IP allowlist / authorization step required for inbound SIP Direct? Our PBX public IP is 172.104.244.8.
PreviousNext
Powered by