First note, I did not remove it because it did not work, I removed it as I linked our Demo 3CX to my personal tenancy for testing purposes as my own 3CX is Pro and not ENT edition.
Goal: link Teams Meeting Room to 3CX to use a single DID for outbound and transferable calls for inbound.
I was following the guide, though it is a little unclear in spots,
I went to SSL2BUY to purchase an ALPHA SSL Wildcard cert (First mistake) as this was a GlobalSign cert and on the list of supported vendors for MS Teams
I then set my DNS to point SBC.mydomain to mydomain.3cx.com.au
I then realized my SSL cert was wrong so I purchased a named sbc.mydomain cert and installed that,
To get the SSL cert I installed IIS on my personal windows machine, started the SSL Cert Request, for the sbc.mydomain then completed the DNS challange etc.
I then used OpenSSL to split the exported cert into the cet and key.pem files required by 3CX for the Teams integration.
I also replaced the SSL/TLS cert in the secure SIP, this was not required as I am not replacing the FQDN, but if you are using a custom FQDN for 3CX this may be required
I downloaded the setup script (script one) and ran, suggestion is to open PowerShell ISE as admin open the script and run the 1st and 2nd line seperatly then once you logged into the admin account bulk run the rest
The 3CX Teams Script sets up everything bar the number assigned to the users.
I then had to (as this was a meeting room and is covered in the 3cx docco) set a first name to the meeting room in Azure AD, also while there add the Business Phone in the E164 format (+612....)
Then setup the Azure Sync following the instructions on the first page, get app ID etc. and sync the "user" ([email protected]) the users page will say MS 365 + Teams in the Sync column
The 2nd script will not let you download if the Teams user is not teams synced and does not have a business number attached
Lastly, I created an outbound rule as I noticed that Teams was sending calls to 3CX without the +61 that was required by the carrier
Once I got though all of the steps I had functioning 2 way calling from a room running Teams Room Pro and 3CX Enterprise
IMO if you only want to link 3CX to Teams rooms and you don't need the extra features save yourself a buck and assign Microsoft 365 Phone System license + Teams room free (you may be able to get away with the virtual license, I did not test with a virtual license as I have a 60-day Pro trial.
In the Rollback it was easy,
Delete or diable the SBC in Teams
Disable the SBC in 3CX
My biggest issue was reverting the TLS/SSL cert for secure SIP, the forums all said to rollback to the latest backup
I was able to find a work around
if using 3CX SSL Certs by lets encrypt a copy is loged in the NGINX module in /var/lib/3cxpbx/Bin/nginx/conf/Instance1
I copied the contents of the crt and key files into the TLS Cert and Key boxes and that fixed the SSL/TLS issue for secure SIP
Long story short: TLDR
Teams can 100% be linked, however, you need the money and patience to set it up as Teams Calling is not cheap, but a single DID is amazing for the rooms.
Goal: link Teams Meeting Room to 3CX to use a single DID for outbound and transferable calls for inbound.
I was following the guide, though it is a little unclear in spots,
I went to SSL2BUY to purchase an ALPHA SSL Wildcard cert (First mistake) as this was a GlobalSign cert and on the list of supported vendors for MS Teams
I then set my DNS to point SBC.mydomain to mydomain.3cx.com.au
I then realized my SSL cert was wrong so I purchased a named sbc.mydomain cert and installed that,
To get the SSL cert I installed IIS on my personal windows machine, started the SSL Cert Request, for the sbc.mydomain then completed the DNS challange etc.
I then used OpenSSL to split the exported cert into the cet and key.pem files required by 3CX for the Teams integration.
I also replaced the SSL/TLS cert in the secure SIP, this was not required as I am not replacing the FQDN, but if you are using a custom FQDN for 3CX this may be required
I downloaded the setup script (script one) and ran, suggestion is to open PowerShell ISE as admin open the script and run the 1st and 2nd line seperatly then once you logged into the admin account bulk run the rest
The 3CX Teams Script sets up everything bar the number assigned to the users.
I then had to (as this was a meeting room and is covered in the 3cx docco) set a first name to the meeting room in Azure AD, also while there add the Business Phone in the E164 format (+612....)
Then setup the Azure Sync following the instructions on the first page, get app ID etc. and sync the "user" ([email protected]) the users page will say MS 365 + Teams in the Sync column
The 2nd script will not let you download if the Teams user is not teams synced and does not have a business number attached
Lastly, I created an outbound rule as I noticed that Teams was sending calls to 3CX without the +61 that was required by the carrier
Once I got though all of the steps I had functioning 2 way calling from a room running Teams Room Pro and 3CX Enterprise
IMO if you only want to link 3CX to Teams rooms and you don't need the extra features save yourself a buck and assign Microsoft 365 Phone System license + Teams room free (you may be able to get away with the virtual license, I did not test with a virtual license as I have a 60-day Pro trial.
In the Rollback it was easy,
Delete or diable the SBC in Teams
Disable the SBC in 3CX
My biggest issue was reverting the TLS/SSL cert for secure SIP, the forums all said to rollback to the latest backup
I was able to find a work around
if using 3CX SSL Certs by lets encrypt a copy is loged in the NGINX module in /var/lib/3cxpbx/Bin/nginx/conf/Instance1
I copied the contents of the crt and key files into the TLS Cert and Key boxes and that fixed the SSL/TLS issue for secure SIP
Long story short: TLDR
Teams can 100% be linked, however, you need the money and patience to set it up as Teams Calling is not cheap, but a single DID is amazing for the rooms.
