Direct Routing - Q.850 Cause 63 Get Inbound Direct routing - no trunk config found in ACMS

New Contributor

I'm currently attempting to setup Direct Routing on a new SBC cluster which is a direct copy of an existing server with just new FQDNs and IP addresses.


I can make calls fine from all users, however inbound calls get the following Cause 63 Forbidden message:


REASON: Q.850;cause=63;text="3590c12b-5610-41e1-9266-1d135e125008;Get Inbound Direct routing - no trunk config found in ACMS."


I've attempted to remove and recreate the users on the SBC domain as well as remove and add licences but I still get the same.


The SIP INVITE looks identical to the platform that works apart from the FQDN now being the new cluster address which is active on the Tenant.


Has anyone seen this specific trunk config ACMS error before?

6 Replies




In the INVITE message to Teams from the SBC.  Can you check the message and check that the SBC FQDN is correct and matches the OnlinePSTNGateway configured?


You want to make sure it's not the local FQDN e.g. your SBC may be contoso.local but the MS FQDN is configured as  If the SBC isn't configured correctly, it could be sending out the wrong FQDN which means MS wouldn't accept your incoming message



@JaySummerfielddid you get a fix for this ? I have the exact same issue - so hoping you got somewhere?


best response confirmed by ThereseSolimeno (Microsoft)

@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 - thanks for getting back to me so quickly - appreciated ! I'll give that a go as all looks fine with the setup and I can't find any other articles relating to the issue. 

@DanLeaf810 Did this resolution solve your issue as well?