Forum Discussion
Solved
Inbound calls to derived direct routing trunk fails with 404
I'm working on setting up a multi-tenant SBC but I can't get inbound calls to work (inbound to Teams). Domains: teams1.example.com - This i registered in the Carrier tenant teams2.example.com ...
- Thanks for the reply.
I found the problem and it was that I used the carrier domain teams1.example.com / teams2.example.com as domains in the record route headers. Changing to using the customer tenants sbc-domain (sub-domain) customer1.teams1.example.com / customer1.teams2.example.com in the record route headers made it work.
I thought that the Contact header was the important one. But apparently not
I'm sure you have but ust want to check that customer1.teams1.example.com has been added as a sub-domain in the customer tenant and a licensed user has been added to that domain to activate it?
404 normally means it got to the end tenant but couldn't find the number which in your screenshot shows the number is. Can you also check that the user doesn't have a Calling Plan license, they just need Phone System.
404 normally means it got to the end tenant but couldn't find the number which in your screenshot shows the number is. Can you also check that the user doesn't have a Calling Plan license, they just need Phone System.
Thanks for the reply.
I found the problem and it was that I used the carrier domain teams1.example.com / teams2.example.com as domains in the record route headers. Changing to using the customer tenants sbc-domain (sub-domain) customer1.teams1.example.com / customer1.teams2.example.com in the record route headers made it work.
I thought that the Contact header was the important one. But apparently not
I found the problem and it was that I used the carrier domain teams1.example.com / teams2.example.com as domains in the record route headers. Changing to using the customer tenants sbc-domain (sub-domain) customer1.teams1.example.com / customer1.teams2.example.com in the record route headers made it work.
I thought that the Contact header was the important one. But apparently not