Forum Discussion
Direct Routing - Q.850 Cause 63 Get Inbound Direct routing - no trunk config found in ACMS
DanLeaf810 I was meant to update this at the time. I had to remove the domains in full from Microsoft 365 and add them again (not forgetting to activate them by assigning users).
I didn't find one specific thing that was wrong when checking the setup end-to-end so can only assume something didn't activate correctly on the back end. Having removed the SBCs from the Teams admin portal and the domains and started from scratch all worked second time around.
JaySummerfield this problem is mainly due to wrong contact header, check the invite sent to teams and check the header specially the sbc fqdn l.
I am facing the same issue. Let me explain it as it is:
We have a very simple setup for Microsoft Teams direct routing. Everything is working fine with incoming and outgoing calls.
We are facing problems after implementing LBR. I am stating a problem as it is with respect to the setup we have.
We have users who are sitting in the office , using team applications on their PCs and able to make and receive calls.
Now we have implemented LBR to restrict these users to make calls when they are not connected to the office network or restrict when they are trying to make calls from any network except the office.
Now in the office the private network is 192.168/168.0/24 and public IP is X.X.X.X/27.
I have defined the private subnet in the network topology subnet And public IP's in the trusted IPs list.. So , ideally the call should work when users are trying from the office network. But the problem is calls are not working even from the office network which is allowed as per the LBR.
Users are getting error : calls failing with Get Outbound Direct routing - no trunk config found by LBR selection criteria.
