Our strategy at CTELO is that all configuration should be kept within the Microsoft 365 administration centre and Powershell, under the existing and controlled security regime. External portals that need any access to the company's tenant to make changes to a user is a security risk. This is especially important in a telephony perspective where number fishing and calling frauds are experienced frequently in the market.
Some M365 administrators find it hard and time-consuming using Powershell. Thus we have made the Routeams Console that requires no Powershell commands to onboard Teams Direct Routing telephony with Routeams.
To be able to run all the features in Routeams Console, you need access to a user with global admin role in Azure Active Directory. For user maintenance only, Teams Admin role is sufficient.
The UPN Suffix of the admin account cannot be a domain that has DNS records for an On-Prem Skype for Business environment. You can also encounter issues if the domain in the UPN Suffix is configured with a wildcard DNS record. If you encounter problems signing in to your tenant using Routeams Console, try to change the UPN suffix for the admin account to your .onmicrosoft.com domain.
Routeams Console will check for all software prerequisites during startup. You will be notified if you are missing prerequisites.
To run RouteamsConsole.exe you need to have Powershell version 5.0 or above.
Skype Online Connector
To allow Routeams Console to connect to your Teams Tenant, you need to have the Skype Online Connector installed. https://www.microsoft.com/en-us/download/details.aspx?id=39366
You need the MSOnline PowerShell module to use Routeams Console.
To install MSOnline powershell module, run Powershell with local administrative privileges and run “install-module msonline”. Confirm yes on any security prompts.
If your Azure environment is synchronized with Windows Server Active Directory using Azure AD Connect, you must make sure that the user attribute msRTCSIP-Line value is <not set>.
All changes made by the PowerShell cmdlets in Routeams Console are low-risk, and should not interfere with any other settings in your environment. However, if you are running Teams Direct Routing against any other SBC’s, and the routing for your existing Direct Routing solution is set up using other features than Online Routing Policies, there is a possibility that new settings will interfere with old settings. Ctelo AS assumes no responsibility for unintended changes to the customer's tenant based on the incorrect use of the application, or conflicts between existing and new setup.