BYOD SIP failing to register
# support
r
Hi Everyone, I've ran into a snag and need a second(or more) eyes to tell me what im doing wrong. My sip trunk provider gave me the following SIP Authentication ID:888888 SIP Password:5555555 Server:hpbx026.XXXXXX.com Port:5060 This is the api call I made: curl --location 'https://api.vapi.ai/credential' \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer XXXXXXXXX' \ --header 'Cookie: _cfuvid=a8llnlIQA9cCjTJV05wE1t0qkJihOrMc41Enf_24yrE-1753911541612-0.0.1.1-604800000' \ --data '{ "provider": "byo-sip-trunk", "name": "TestTrunk", "gateways": [{ "ip": "hpbx026.XXXXXXXXXX.com" }], "outboundLeadingPlusEnabled": false, "outboundAuthenticationPlan": { "authUsername": "888888", "authPassword": "5555555" } }' Unfortunetly its not registering. Am I missing something?
@Nir Simionovich (CEO@Cloudonix) with some tweaking its now registered but inbound and outbound calls are not working
n
Then it's not registered. If you want, DM me and we can test it via our SBC.
r
Yes please
k
in my case, for inbound calls, it was number missconfiguration in the dashboard
c
Just a quick question RocketMan, are you expecting to use inbound and outbound calling with this number?
r
Inbound
actually fixed it all!
How do I get the Transfer_call to use a specific gateway
c
Ensure your assistant is linked to a phone number that uses the desired SIP trunk credential, and optionally specify a sipUri in the transfer destination for precise routing..
g
how did you fix this? I tried adding it I keep getting 400. If I add
"inboundEnabled": false
it returns success But I want it to have inbound capabilities so i remove it and it returns 400.
3 Views