Migrate Poly VVX Phones from Skype/Teams to Zoom Phone

All Phones at once..

The process of migrating Poly VVX phones from Teams/Skype to Zoom Phone is a three (3) step process.

1. Configure the IP Phone within the Zoom Phone portal
2. Remove DHCP options that point to Teams/Skype provisioning server URL
3. Factory rest the IP phone, and it will complete via zero-touch provisioning

When using DHCP options to provide a provisioning server (DHCP option 160 or 161 - depending on the SKU that was used to purchase the phone).

If using DHCP options, the IP phone will pickup the provisioning server via specific option values.  If you are migrating all IP phones at once, you can just delete/clear the option within the DHCP scope/server, and factory rest the IP phones.

Staged Migration

If you are migrating phones in a phased approach, one (1) way to complete is via DHCP Policies.

Policy processing

Since you can configure multiple policies at both the scope level and server level, each policy is assigned a processing order. The processing order can also be modified, assuming more than a single policy exists. The following conditions exist:

1. When processing DHCP client requests, the DHCP server evaluates each client request against the conditions in all applicable policies, based on their processing order.

2. Scope level policies are processed first by the DHCP server, followed by server wide policies. Theoretically, a client can match the conditions of several scope policies and also several server policies.

3. If a client satisfies the conditions of more than 1 policy, it will get the combined settings from all policies that it matched. If the same option setting is provided in multiple policies, the client will use the setting from the first policy that is processed.

Poly Specific "Vendor Class Identifier"

Poly Product	Vendor Option Name
CCX350	Poly-CCX350
CCX400 (UC Software 6.2.11 or later)	Poly-CCX400
CCX500	Poly-CCX500
CCX505	Poly-CCX505
CCX600	Poly-CCX600
CCX700	Poly-CCX700
Edge E 100	Poly-EdgeE100
Edge E 220	Poly-EdgeE220
Edge E 300	Poly-EdgeE300
Edge E 320	Poly-EdgeE320
Edge E 350	Poly-EdgeE350
Edge E 400	Poly-EdgeE400
Edge E 450	Poly-EdgeE450
Edge E 500	Poly-EdgeE500
Edge E 550	Poly-EdgeE550
Edge B10	Poly Edge B10
Edge B30	Poly Edge B20
Edge B30	Poly Edge B30
VVX501	Polycom-VVX501
VVX601	Polycom-VVX601
VVX101	Polycom-VVX101
VVX150	Polycom-VVX150
VVX201	Polycom-VVX201
VVX250	Polycom-VVX250
VVX301	Polycom-VVX301
VVX311	Polycom-VVX311
VVX350	Polycom-VVX350
VVX401	Polycom-VVX401
VVX411	Polycom-VVX411
VVX450	Polycom-VVX450
VVX D230	Poly-VVX-D230
Poly Rove B DECT	IPDECT-V2/80.03.0009 (MAC=64167FF4C9ED; SER= 00000; HW=4)
Polycom Trio 8300	Poly-Trio8300
Polycom Trio 8800	Polycom-Trio8800
Polycom Trio 8500	Polycom-Trio8500
Polycom RealPresence Trio Visual+	Polycom-TrioVisualPlus
Polycom Trio C60	Poly-TrioC60
SoundStation IP 5000	Polycom-SSIP5000
SoundStation IP Duo	Polycom-SSDuo

A DHCP policy will need to be created that matches, both the MAC Address and the Vendor Specific option listed above.

The assisted provisioning server from Zoom outlines the value required for options 160 or 161.

Assisted provisioning URLs - Poly

Landis Attendant Console Install

Attempting to setup a test tenant with access to Landis Attendant Console, and was getting errors around granting access to the tenant.

The error message I was receiving via the browser URL..

The app is trying to access a service 1fd5118e-2576-4263-8130-9503064c837a (Azure Communication Services) that your organization <GUID> lacks a service principal for.

To fix I needed to manually add the "Azure Communication Services", via PowerShell.

Connect-AzureAD

New-AzureADServicePrincipal -AppId "1fd5118e-2576-4263-8130-9503064c837a"   

After waiting for about 3 mins, I was able to grant consent ant get access to Landis Attendant Console.

Unable to write to Active Directory due to lack of permissions

At times when I attempt to move a user from Skype to Teams I have been receiving the following error:

To view account that are causing the issue you can run the following PowerShell command

Get-ADUser -SearchBase "OU HERE" -Filter * -Properties nTSecurityDescriptor | ?{ $_.nTSecurityDescriptor.AreAccessRulesProtected -eq "True" }

List of Agents in Skype Work Groups

To get a list of agents in a skype work group run the following command via PowerShell:

++++++++++++++++++++++++++++

Get-CsRgsAgentGroup | select Name, @{Name=’AgentsByUri’;Expression={[string]::join(",", ($_.AgentsByUri))}} | Export-Csv agent-export.csv

++++++++++++++++++++++++++++

This can then be opened in Excel and manipulated to be used easier..

Open in Excel and "text to data" the AgentsByUri column, copy and then paste with "transpose" option to get in a nice format.

M365 Call Flow Visualizer

This is a port so that I remember where to find the scripts..

https://github.com/mozziemozz/M365CallFlowVisualizer

Shout out to the author:

martin heusser

Teams Tracing/Logging

This post is to outline the logging/tracing items for a MS Teams environment, most of the tracing will be from the Teams Client/Web App/etc.

It will hopefully be a "living" post that is updated when I find new things.

First Step - Get log files from the Client:

Use log files to monitor and troubleshoot Microsoft Teams

Teams Client, right click the icon in the task bar and select "Collect support files"

Time stamps in the log files are in epoch time:

What is epoch time?

The Unix epoch (or Unix time or POSIX time or Unix timestamp) is the number of seconds that have elapsed since January 1, 1970

https://www.epochconverter.com/

Log files:

"MSTeams Diagnostics Log <date><time>_calling.txt" has calls made received:

Context Details:

SlashCommand           "/call <number>" in the search field

CentralDataLayer        Call from the dial-pad in Teams client

Teams Resource Accounts

Trying to crate a "Resource Account" for a Teams CQ and/or AA, and came across an issue where via both TAC and Power Shell it would fail.

TAC

Power Shell

I had seen this before when the Teams/Skype Online was a Hybrid environment, but in this case the deployment has no on-premises Skype environment.

The Fix

Turns out DNS is the issue, even when in a cloud only environment the Skype DNS entries are required.