Jason Warm
05/21/2025, 9:49 PMVapi Support Bot
05/21/2025, 9:52 PM1786577XXXX@<your_credential_id>.sip.vapi.ai
Replace <your_credential_id> with the actual credential ID from your Vapi SIP trunk setup. Also, ensure that the Vapi signaling IPs (44.229.228.186 and 44.238.177.138) are allowlisted in your Voip.ms account. This should help route inbound calls correctly to your Vapi assistant.
[See Vapi SIP trunking docs for details.](https://docs.vapi.ai/advanced/sip/sip-trunk#inbound-call-test)
Source:
- [Vapi SIP Trunking Documentation](https://docs.vapi.ai/advanced/sip/sip-trunk#inbound-call-test)Nir Simionovich (CEO@Cloudonix)
05/21/2025, 9:56 PMSIP Registration can sometimes maintain the wrong SIP Contact information, and thus, when calling out to the subscriber, will not use the proper SIP R-URI to dial with. If you would like, please DM me and we can investigate the issue. I've seen these kind of cases before, and piping the call via Cloudonix resolved the issue in seconds.Jason Warm
05/21/2025, 10:11 PMNir Simionovich (CEO@Cloudonix)
05/21/2025, 10:28 PMJason Warm
05/22/2025, 1:08 PMJason Warm
05/22/2025, 1:09 PMChiranjeet Mishra
05/23/2025, 8:03 AMRiz
08/08/2025, 3:54 PMChiranjeet Mishra
08/12/2025, 9:34 PMRiz
08/13/2025, 5:44 PMChiranjeet Mishra
08/14/2025, 6:55 AM{
"provider": "byo-sip-trunk",
"name": "My SIP Trunk",
"gateways": [
{
"ip": "sip.provider.com",
"port": 5060,
"outboundEnabled": true,
"inboundEnabled": false,
"outboundProtocol": "udp"
},
{
"ip": "203.0.113.10",
"port": 5060,
"outboundEnabled": false,
"inboundEnabled": true
}
]
}Riz
08/17/2025, 5:22 PMRiz
08/18/2025, 5:21 AM