Teams Calling | Number porting diary - Day 1

During my time at Microsoft I did not have a chance to migrate any customer since Microsoft Calling plan was not available for Asia Pacific.

The list of articles here are all my experiences with migrations to Teams calling plan and also from Teams calling plan to Telco porting. I searched in several places for documentations by individuals about the process and how to proceed, and I did not have much luck in my search. Hence, I thought why not I give back to the community about my daily hustle in summary.

Number porting can be very simple to complex, this completely depends on the environment, the type of numbers available in that environment, their usage, and the level of knowledge the customer has about their own environment. Prior to submitting any order (be it Microsoft or any Telco around the world), number planning is required, and the entire process can consume many hours.

Porting request submission 

Porting request(s) can be submitted from two locations:

1.  Teams Admin Center (TAC) > Voice 

2. Access via PTN portal - https://pstnsd.powerappsportals.com/ 

 

Teams Calling | Number porting diary - Day 2

Cannot assign phone number to licensed user - Microsoft Teams Calling 

Currently i'm doing some testing related to Microsoft Teams calling, It seems to me like Teams Admin center replication with M365 backend. According to my experience sometimes it can be quick, or replication can go up to long hours. 

Refer this - https://docs.microsoft.com/en-us/microsoftteams/assign-change-or-remove-a-phone- number-for-a-user 

but sometimes we get lucky using PowerShell.  PS faster than GUI /Admin  center since it is talking to M365 fabric directly.

Try using PowerShell  (Connect to Microsoft Teams first)

#Connect to Microsoft Teams

$credential = Get-Credential

Connect-MicrosoftTeams -Credential $credential

 Once it prompt, use your Teams Admin login and password

 Once you connected following command will help you to assign using PowerShell

Set-CsOnlineVoiceUser -Identity teste5@enkiii.info -TelephoneNumber +136567xxxx -Verbose 

at the moment i'm still getting error to assign the number. Its only 1 hr gone from the time i added the license and Phone number and Location

 

Similar article found - Can not assign phone number to licensed user - Microsoft Tech Community

When i was checking Teams Admin Center (https://admin.teams.microsoft.com) then i found calling policy not assigned and Emergency address was "null". Once i done with those variables, i able to assign a number by selecting user

Assign phone number 

 it was showing dial pad in the Teams client and manage to dial calls

            Assign Emergency address  

It was pretty easy for customers who have small and medium size, less complex environment to have hosted/cloud telephone service from Microsoft PhoneSystem using Microsoft Calling plans. #CallingPlans #MicrosoftPhoneSystem 

Enjoy!

Would you like to join to our community - https://chat.whatsapp.com/CqUn6StAKL5L9Bo0XlIkjK  

 

Move-CsUser bulk using script from SfB to Teams

Moving users from Skype for business to Teams part of the migration process, We can do this process using GUI and also we can use the PowerShell to do the work. Following scripts i have added to my github too just incase someone want to take from it instead of my blog post.

In my script i was using csv file with one header which is "SipAddress". List down all the SipAddress of users you plan to move to Teams prior to following steps. 

  

Define following variables 

$cr=Get-Credential

$url="https://admin10.online.lync.com/HostedMigration/hostedmigrationService.svc"

Important:  provided account should have global admin or Teams admin & User Admin with SfB CSAdministrator permission 

#//Add all the users SIP address which required to move to Teams//

$User = import-csv .\Userslist.csv
    ForEach ($Alluser in $User)
    {
    Move-CsUser -Identity $AllUser.SipAddress -Target "sipfed.online.lync.com" -  ProxyPool "lyncpool.abc.com" -Credential $cr -HostedMigrationOverrideUrl $url -Verbose
 

#Convert TeamsOnly
        Grant-CsTeamsUpgradePolicy -PolicyName UpgradeToTeams -Identity $AllUser.SipAddress -verbose
 

#EnterpriseVoiceEnabled if you need to set remove and in my case i have remove it.
      #Set-CsUser -identity $AllUser.SipAddress -EnterpriseVoiceEnabled $true -verbose
}

Next article ill be sharing migration and bulk number mapping both using PowerShell

Rollback users from Teams to Lync Server

 

 Rollback users from Teams to Lync Server 

This scenario apply only for individual or bulk moved users to Teams from Lync/SfB environment using Move-CsUser commands. 

It's not a common scenario where users move back to Lync from Teams but in a situation you might need it. 

Part of the process you may required to find hostedmigrationService related to your tenant. 

$url="https://admin1a.online.lync.com/HostedMigration/hostedmigrationService.svc"

you need to check above highlighted parameter which is related to your account. If you're using Get-TenantInfo.PS1 also one way of find the script and try 

https://www.powershellgallery.com/packages/SkypeForBusinessHybridHealth/1.1.3.0/Content/Get-TenantInfo.ps1

Once you done with $url defined you can go for next step to move user back to onprem 

$cr=Get-Credential

Move-CsUser -Identity "madushka@deployskypeforbusiness.com" -Target "lyncpool.deployskypeforbusiness.com" -Credential $cr -Verbose

Prompt for $cr=credential make sure enter Teams administrator 

Once you move the user successfully can verify using following parameter 

HostingProvider should change it to SRV: 

Bulk users 

Save these users in CSV with a header sipaddress (this can be text with csv)

$Userlist = import-csv .\Userslist.csv

    ForEach ($AllMoveuser in $Userlist)

    {

    Move-CsUser -Identity $AllMoveUser.SipAddress -Target "sipfed.online.lync.com" -ProxyPool "lyncpool.deployskypeforbusiness.com" -Credential $cr -HostedMigrationOverrideUrl $url -Verbose

}

Enjoy! 

Why not skype for business 2019

Just give it a try :) i started a VM and done with AD and CA in the same test server (not recommended) just to see how it look like and the changes. 

OS - Windows Server 2019 (Nov 2020 update) and trying to install the SfB2019 of course the prerequisites functional support is windows server 2016. 

On my VM mount the SfB2019 ISO and run it. 

Then push with Add-features couple of things are failing and need to go ahead with manual check and understand that .net framework 3.5 needed for topology to start with but it is failing part of the process. 

and i try to install the the topology on windows 10 latest update i manage to do that just to open the topology and take a look. 

Continue....

What's New in Microsoft Teams | Microsoft Ignite 2020 event

Announcement for meeting new together mode  - https://techcommunity.microsoft.com/t5/microsoft-teams-blog/what-s-new-in-microsoft-teams-microsoft-ignite-2020/ba-p/1665600

Microsoft announced new together mode scenes coming this calendar year and this is super exiting news for lots of customer who enjoying the features 

and another nice function announced was participants will be able to see the presenter's video feed transposed onto the foreground of the slide. 

few more like breakoutrooms

Meeting recap

calling plans availability for new list of countries such as Austria, Denmark, Itay, Portugal, Sweden and Switzerland 

Collab area such as templates, Conversation button in channels, search experience 

Limitations increased to 5000 to 25000 member per Team was one of important factor for large environments

New C470HD Native Microsoft Teams IP phone released

Amazing news and everyone waiting for new devices for Teams, 13th Aug AudioCodes released a new native phone which is C470HD. It is having 5.5" color touch screen which we love to have and just like smart mobile with USB headset,bluetooth,PoE, GbE support. 

HD Voice quality with native teams client i think we dont have think twice about the device. and pretty thin display too. Enjoy!

cc - audiocodes youtube -https://www.youtube.com/channel/UCZFOqdMjlnmqmiwoSmHXAAg