This certificate will also need to be imported into the Trusted Root of the PC being used for the SmartTAP Teams App. Ensure its imported into the Local Computer container which ensures any user logging onto the server will automatically trust the certificate too. Once submitted browse to View/Modify Certificate List and export the certificate to your desktop.Īs the certificate is self-signed it must be imported into the Trusted Root on your server. Enter your details into the form and ensure you’ve added the ST FQDN as a SAN entry. But because this is a quick and dirty lab I used a self signed certificate issued by the ST itself.Ĭreating the new certificate/CSR is very straight forward. For a production deployment you absolutely want to use a certificate from a Public CA. If you then browse to manage devices you should see the updated FQDNĪs the Application ‘Web’ Service is advertised on SSL, and the default certificate will not contain the correct SAN/FQDN of your ST a new certificate needs to be created.
#Scopebox ip windows
From Windows Explorer browse to the “calldeliveryconfig.xml” and change the “Recorder IP” to the correct FQDN and then restart the AudioCodes Application Service for the new FQDN to take effect. I couldn’t see an elegant way to do this from the web UI so had to edit a config file instead to change my ST hostname from the default. If your ST is not already enabled with your own FQDN and is still using the system default hostname ‘SIPREC’ the ST will need to be renamed to the correct hostname/FQDN. I will not be covering those elementary configuration steps here but be warned if the ST isn’t accessible from the Public Internet the ST Teams App integration will not work! Likewise Public DNS needs to have an A record pointing to the Public IP address of your ST. So you’ll need to ensure the DNS resolver used on your server points to the internal IP address of your ST. This URL needs to be browsable locally on the server as well as from the Internet. EG you should be able to access your ST web UI from a PC on the internet. And the FQDN for the ST must be browsable from the Internet.
As your Microsoft Teams client will be accessing your SmartTAP directly via its FQDN you’ll need to have an A record in public DNS for your ST instance along with a static Public IP. Step 1 – SmartTAP must be published to the internet If you’ve followed the steps for enabling AAD integration in my previous blog post here then you’re part way there! There are some important caveats to get the SmartTAP Teams App to work though which I’ll cover in this blog post. There are a few moving parts to get this integration to work, namely integration your SmartTAP with your Azure AD instance. This is certainly a very useful feature so CR users can listen to recordings easily from within their Teams client. AudioCodes has a really cool integration with the Microsoft Teams client that enables an administrator or a compliance call recorded user to be able to manage the SmartTAP server or see their recordings.
0 kommentar(er)
