Thursday, 12 May 2022

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

Wednesday, 27 January 2021

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.



Wednesday, 1 April 2020

Assign Number to Teams Resource Accounts

This has been bugging me for awhile, I wasn't able to assign a number to a resource account that had been created for a Teams AA or CQ.  When trying to assign via Teams Admin Centre (TAC) I was able to search for the number but it was ALWAYS displaying the "No results were found" error.




Turns out I had set the location of the users licence to "United States", once this was change to "Australia" i was able to assign the phone number.



I spent way to much time trying to figure this one out, so hopefully this serves as a reminder..

Monday, 23 March 2020

Post-migration from Skype to Teams toolbox

Ståle Hansen has this great blog post, and since I keep loosing it, just wanted to post so that I can find it next time..


Thursday, 12 September 2019

Set LineURI via PowerShell Teams

Set the LineURI for a user using calling plans (Telstra Calling)

1. Need the location ID
Get-CsOnlineLisLocation


2. Set-CsOlineVoiceUser -Identity name -LocationID GUID-from-step-1 -telephonenumber +E.164-format



Monday, 5 August 2019

Office 365 IP Address and URL Web service

Using the Office 365 IP Address and URL Web service to pull the latest information.

The website above has all the listed parameters that you can use to grab specific data, but here are the shortcuts I use for specific products:


Common parameters

These parameters are common across all the web service methods:
  • format= JSON | CSV - By default, the returned data format is JSON. Use this optional parameter to return the data in comma-separated values (CSV) format.
  • ClientRequestId=guid - A required GUID that you generate for client association. You should generate a GUID for each machine that calls the web service. Do not use the GUIDs shown in the following examples because they may be blocked by the web service in the future. GUID format is xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx, where x represents a hexadecimal number. To generate a GUID, use the New-Guid PowerShell command.
First you need to generate a GUID, from PowerShell run the following:
New-Guid


Endpoints web method

The endpoints web method returns all records for IP address ranges and URLs that make up the Office 365 service. While the latest data from the endpoints web method should be used for network device configuration, the data can be cached for up to 30 days after it is published due to the advance notice provided for additions. We recommend you only call the endpoints web method again when the version web method indicates a new version of the data is available.
Parameters for the endpoints web method are:
  • ServiceAreas= Common | Exchange | SharePoint | Skype - A comma-separated list of service areas. Valid items are CommonExchangeSharePoint, and Skype. Because Common service area items are a prerequisite for all other service areas, the web service will always include them. If you do not include this parameter, all service areas are returned.

Skype and Teams CSV output
https://endpoints.office.com/endpoints/Worldwide?ServiceAreas=Skype&ClientRequestId=5017483f-93b2-4051-b08e-d8af77ab2f2d&Format=CSV

Exchange CSV output
https://endpoints.office.com/endpoints/Worldwide?ServiceAreas=Exchange&ClientRequestId=5017483f-93b2-4051-b08e-d8af77ab2f2d&Format=CSV

Import into Excel You can also use the above URL to import data straight into Excel
1. Open new Excel Workbook, select "Data"

2. Select "From Web"

3. Past in value for required O365 Workflow, click "OK"
4. Make any required changes to the data to be imported, click "Load"

5. Data import complete for selected O365 Workflow.

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....