top of page
Search
  • Writer's picturesamanthaeasterday

I set up direct routing with our sip providers sbc. But didn't have a dial pad in Teams to make any test calls. After some research and convincing our Microsoft support provider of the licenses I need (that's a different story). I outlined you need 3 things to have a dial pad in Teams.

1. The user must have a voice license, like Phone System or Business Voice.

2. The user must have Enterprise Voice enabled. This is typically done in PowerShell using Set-CsUser.

3. The user must be "granted" a Voice Routing Policy.

The Phone system license will either be an add-on to our E3 license or will be apart of an E5 license.

If you are migrating from Skype for Business to Teams, Enterprise Voice should already be enabled.

You should have Voice Routing Policy set up for Teams and you will use the command Grant-CsOnlineVoiceRoutingPolicy -Identity username@domain.com -PolicyName "TeamsRoute".




286 views0 comments
  • Writer's picturesamanthaeasterday

Updated: Jul 13, 2021


In a past blog post, I talked about how our Polycom phones wouldn't sign in a new or difference user. After A LOT of troubleshooting, I found out tls 1.0 is getting blocked somewhere in our network, which is not allowing the phones to reach the ports they need.

Recently, I have been working on Direct Routing in Teams. I wanted to move myself to TeamsOnly (bye bye Skype) but received an error:

User is homed on-premises in a Skype for Business or Lync deployment. On-premises users can be upgraded to Teams using Move-CsUser in the on-premises tools. For details, see http://aka.ms/UpgradeToTeams

I thought, okay, no problem, I'll do what they say and use PowerShell. BUT low and behold, I received the same error message. This told me a lot and helped me figure out, fairly quickly, what the command was looking for on the backend and helped me down my path of yet, another, tls 1.0 issue.


Rather than spending the next, however long, to continue my search of finding where it is getting blocked. I thought, why do I have to use tls 1.0? So I found a command to force PowerShell to use tls 1.2, so I can move my account to TeamsOnly and move on with my life!

Open PowerShell on your Skype server or install the modules (search for past blog post). And run these:

[Net.ServicePointManager]::SecurityProtocol =

[Net.SecurityProtocolType]::Tls12

move-csuser -identity username@domain.com -target sipfed.online.lync.com -useoauth


You are now on TeamsOnly!

So, you might ask, but....what now?

Well, It's simple, I added the commands to my script for when I move more users to TeamsOnly for the pilot. But yes, yes...I will still work on where tls 1.0 is getting blocked, in my spare time ;)


13 views0 comments
  • Writer's picturesamanthaeasterday

Microsoft has discontinued the user of Skype Online module and has replaced it with the Teams module. There are lots of blogs and information out there on how to do this, yet I ran into an issue.

Scenario:

Work laptop, administrative creds, SfB Onpremises, Teams up and running, moving myself to TeamsOnly. Need access to both Skype and Teams.

Open Powershell (or ISE) in Admin mode

This next one is what I had to run to allow the modules to download (thanks security ;)

Set-ExecutionPolicy Unrestricted

Copy and paste one at a time:

Install-Module -Name PowerShellGet -Force -AllowClobber

Install-Module -Name MicrosoftTeams -Force -AllowClobber

Connect-MicrosoftTeams

Sign in with your 365 account


$UserCredential = Get-Credential (log into your admin account)

Copy and paste the below into a notepad and replace the server name with yours.

$Session = New-PSSession -ConnectionUri https://sfbfe.domain.com/ocspowershell -Credential $UserCredential

Import-PSSession $Session



7 views0 comments
  • Twitter
bottom of page