barto_95 | π΅πΉ
11/25/2025, 10:01 PMVapi Support Bot
11/25/2025, 10:02 PMbash
curl -X POST "https://api.vapi.ai/credential" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_VAPI_PRIVATE_KEY" \
-d '{
"provider": "byo-sip-trunk",
"name": "My SIP Trunk",
"gateways": [{ "ip": "YOUR_SIP_SERVER_ADDRESS", "inboundEnabled": false }],
"outboundAuthenticationPlan": {
"authUsername": "YOUR_SIP_USERNAME",
"authPassword": "YOUR_SIP_PASSWORD"
}
}'
Gather your SIP server address and credentials, then use this API call to connect Vapi to your VOIP server.
For more details, see the [Vapi SIP Trunking guide](https://docs.vapi.ai/advanced/sip/sip-trunk).
Source:
- [SIP Trunking | Vapi Documentation](https://docs.vapi.ai/advanced/sip/sip-trunk)barto_95 | π΅πΉ
11/25/2025, 10:17 PMVapi Support Bot
11/25/2025, 10:17 PMbarto_95 | π΅πΉ
11/26/2025, 9:47 AMbarto_95 | π΅πΉ
11/26/2025, 8:36 PMVapi Support Bot
11/26/2025, 8:37 PM44.229.228.186/32
44.238.177.138/32
Add these to your SIP server's firewall or access control list to ensure proper connectivity. These IPs are used exclusively for Vapi SIP traffic.
For more details, see the [Vapi SIP Trunking documentation](https://docs.vapi.ai/advanced/sip/sip-trunk).
Source:
- [SIP Trunking | Vapi Documentation](https://docs.vapi.ai/advanced/sip/sip-trunk)barto_95 | π΅πΉ
12/01/2025, 9:06 PMVapi Support Bot
12/01/2025, 9:07 PM44.229.228.186/32 and 44.238.177.138/32) on your SIP server's firewall or ACL. If not, Vapi cannot reach your server and credential creation will fail.
Hereβs the required step:
plaintext
# Add these to your SIP server's allowlist:
44.229.228.186/32
44.238.177.138/32
After updating your firewall, try creating the SIP trunk credential again.
For more details, see the [Vapi SIP Trunking documentation](https://docs.vapi.ai/advanced/sip/sip-trunk).
Source:
- [SIP Trunking | Vapi Documentation](https://docs.vapi.ai/advanced/sip/sip-trunk)barto_95 | π΅πΉ
12/01/2025, 9:40 PMChiranjeet Mishra
12/11/2025, 1:48 AM