Inbound Call problem with BYO Trunk
# support
n
I am currently doing a project on my voice assistant (AI is in German and I am working for it as a non-german speaker). I have been configuring the SIP Trunk Connection through the BYO Trunk number which actually works when I conducted the outbound call, but somehow it won't manage to pick up the phone when I tried to do the inbound call. The configuration for the Trunk credentials already matched with the assigned credentials by my own provider both for Inbound and Outbound with the right protocol, address, and netmask hence that is the reason why the Outbound call works. However, after the configuration I tried to do an Inbound call to the assistant that I have created and the message Multiple accounts are attempting to default carrier route (that was from the provider) and also in return call gets declined from the Vapi side. The provider also told me to check with Vapi on why it declined the call. I checked the logs and there are no incoming call that I receive from the Call Logs dashboard. I was wondering if there are any ways to check why this happened so that I could fix this issue with just the Inbound call? https://cdn.discordapp.com/attachments/1372539855300591737/1372539855455649932/Support1.png?ex=682724da&is=6825d35a&hm=77c4c789235382f1873b94f84e0f3872d0e59f49ecf1c4e5b56d152a6a20d980& https://cdn.discordapp.com/attachments/1372539855300591737/1372539855900512311/Support_2.png?ex=682724da&is=6825d35a&hm=f8c12e6b4e0e72191b5d20a48d3bdeb93bbc6b03cdd5dbb33a9848f7d2a7fac8&
v
The error "Multiple accounts are attempting to default carrier route" means your phone number is linked to more than one account or organization in Vapi, which causes inbound calls to be declined. To fix this, delete all existing SIPs with this number in Vapi, then recreate the configuration so the number is only linked to a single account or organization. This should resolve the inbound call issue. Note: There are no additional Vapi-side logs for this error beyond what you see in the dashboard. Source: - [Discord Vapi Support Thread](https://discord.com/channels/1211482211119796234/1339952678150868992)
n
It's only linked to one account or organization. So far I only have one account for this project and no more. I tried to delete the SIP Trunk Credentials and also reconfiguring it as well the same time as the phone number configuration. I tried to do Outbound call and it is still working but Inbound call never works. https://cdn.discordapp.com/attachments/1372539855300591737/1372544771624534076/Support3.png?ex=6827296e&is=6825d7ee&hm=df6601c340608de53346b7835cf4fd4a2263b8b52a666cb6d52d4ea7de2220cb&
n
@NazCaz based on your description, can I assume that your carrier provided you with an IP number or FQDN, a username and a password ?
n
Yes, the provider/carrier provided me with the FQDN/Username/Password and I'm using peoplefone for it
s
I have a similar issue where the trunk is registered, outbound calls work (really well, very impressed) but the inbound calls are not successful. I get a 404 not found response. It would be great if we had some visibility of the SIP signals at the VAPI end.
n
Forreal, I tried to check the problem from my provider's setting side and I received a message where it states that it was declined the SIP Server rejected the call and it says SIP/2.0 503 Service Unavailable.
a
Hey, Could you please schedule a brief call at your convenience so we can discuss this matter in detail? Kindly use the following link to book a suitable time: .
s
Correction, I don't receive a 404, it is a 500 server error. I will request a call to discuss.