Solved 3CX - Teams Direct Routing connection issue

[MetroAnakin]

Hi team,

I've encountered an error message when trying to run the dial plan script in Powershell. Google is showing a lot of solutions however none of them have made a difference, it may be a permissions / license issue.

Important information down below:

1. PBX Version: 18.0 (Build 314)
2. Teams licenses: MS365 Business Basic + MS Teams Phone Standard
3. On-prem/Cloud/Hosted?: Hosted on Amazon Lightsail
4. What brand of firewall, and is SIP ALG disabled? Unsure and SIP ALG is disabled
5. What trunk provider do you use? Voyager

The certificate for Teams Routing is valid.
The private key has been added.
Port 5062 is open.


Command:
New-CsOnlinePSTNGateway -Fqdn xyz.com -Enabled $true -SipSignalingPort 5062 -MaxConcurrentSessions 100 -ForwardCallHistory $true -ForwardPai $true

Error:
New-CsOnlinePSTNGateway : Connecting to remote server api.interfaces.records.teams.microsoft.com failed with the
following error message : The WinRM client received an HTTP status code of 403 from the remote WS-Management service.
For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-CsOnlinePSTNGateway -Fqdn xyz.com -Enabled $true -Sip ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ResourceUnavailable: ) [New-CsOnlinePSTNGateway], PSRemotingTransportException
+ FullyQualifiedErrorId : System.Management.Automation.Remoting.PSRemotingDataStructureException,Microsoft.Teams.C
onfigApi.Cmdlets.NewCsOnlinePSTNGateway

 

[MetroAnakin]

Just an update on this if anyone else comes across this post. The issue was caused by not assigning teams administrator rights to the user in Active Directory. I had assigned ownership rights in MS365 but not teams admin rights.

Thanks all!

 

[NickD_3CX]

Thanks for sharing the solution!

I will mark this as 'Solved'.