BYO SIP trunk issue
# supports
Sajad
04/01/2026, 2:09 PMHi Vapi team, I’m currently working with our SIP provider to set up a BYO SIP trunk in Vapi, and I’d appreciate some help reviewing the setup from the Vapi side.
At this point, I’m able to create the SIP trunk / gateway connection in Vapi, import the DDI number, assign the number to the SIP trunk connection, and place outbound call attempts. However, the calls are still failing.
During testing with the provider, they shared logs showing timeout and blacklist-related behavior on the SIP signaling side. They also mentioned that they applied a configuration change and are checking whether that resolves the TLS-related issue as well.
In addition, they mentioned that when incoming credentials are left empty, an error appears, even though they provided the credentials separately.
Could you please help review whether the SIP trunk setup on the Vapi side looks correct and whether there is anything specific in the configuration that could be causing these issues?
Please let me know if you need any screenshots, configuration details, or logs from my side.
#1211483291191083018
v
Vapi Support Bot
04/01/2026, 2:10 PMThanks for reaching out! To help review your SIP trunk setup, could you please share the exact gateway configuration you used in Vapi (with any sensitive info like passwords redacted)? This will help identify if there are issues such as using a hostname instead of an IP, incorrect port, or flag settings.
If you prefer, you can paste just the relevant JSON snippet for the
gateways Copy code
{
"provider": "byo-sip-trunk",
"name": "My SIP Trunk",
"gateways": [
{
"ip": "203.0.113.10",
"port": 5060,
"outboundEnabled": true,
"inboundEnabled": false
}
]
}s
Sajad
04/01/2026, 2:34 PM Copy code
{
"provider": "byo-sip-trunk",
"name": "GO_Test",
"gateways": [
{
"ip": "provider-domain-redacted",
"port": 5067,
"netmask": 32,
"outboundProtocol": "tls/srtp",
"outboundEnabled": true,
"inboundEnabled": false,
"optionsPingEnabled": true
}
]
}c
Chiranjeet Mishra
04/01/2026, 11:04 PMplease also share a call id where the connection failed and we will review the logs
s
Sajad
04/02/2026, 7:11 AM019d48b3-39f2-7000-8afb-91365c3bf89c
Sajad
04/06/2026, 9:22 AM@User any update regarding my request pls ?
c
Chiranjeet Mishra
04/07/2026, 11:13 PMthis is what we’re seeing in our logs:
Copy code
🔵 10:59:58:738 Processing callComplete: {
"status": "ended",
"endedReason": "customer-busy",
"phoneCallProviderDetails": {
"sbcCallId": "c3f0feda-a85c-123f-0295-02c16c8be2c9",
"sipStatus": 603,
"sipReason": "Decline"
}
}