- Joined
- Oct 10, 2019
- Messages
- 6
- Reaction score
- 1
Hi there,
Having some issues getting Teams direct routing going.
Issue: Teams calls fail immediately upon dialing.
The following error is showing in the Microsoft 365 Integration menu within 3CX:
I have verified the following:
- Dial plan etc. is loaded
- User has a phone system license
- User has the correct 3CX policies applied in the Teams admin panel, as per the PowerShell script.
- Valid certificate for teams.mydomain.com is applied within 3CX
- Port 5001 is open and I can access https://3cx.mydomain.com:5001 and https://teams.mydomain.com:5001 from outside
- Port 5062 is open, verified with several "port forwarding checker" utility sites.
- Port 443 is open, verified with several "port forwarding checker" utility sites.
Any ideas?
Having some issues getting Teams direct routing going.
Issue: Teams calls fail immediately upon dialing.
The following error is showing in the Microsoft 365 Integration menu within 3CX:
- Real Time Notifications to Microsoft 365 changes will not work because it seems that HTTPS port forwarding is not configured. This means that when changes occur, they will not be updated real time. A synchronization will still occur every night.
- Code: InvalidRequest Message: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. Inner error: AdditionalData: date: 2021-10-07T19:46:44 request-id: bb7cbf1f-1300-40bb-b542-710c34b177f6 client-request-id: bb7cbf1f-1300-40bb-b542-710c34b177f6 ClientRequestId: bb7cbf1f-1300-40bb-b542-710c34b177f6
I have verified the following:
- Dial plan etc. is loaded
- User has a phone system license
- User has the correct 3CX policies applied in the Teams admin panel, as per the PowerShell script.
- Valid certificate for teams.mydomain.com is applied within 3CX
- Port 5001 is open and I can access https://3cx.mydomain.com:5001 and https://teams.mydomain.com:5001 from outside
- Port 5062 is open, verified with several "port forwarding checker" utility sites.
- Port 443 is open, verified with several "port forwarding checker" utility sites.
Any ideas?