How Can We Help?
-
Teamwork Analytics
-
-
- Target Specific Team Owners by Country with Information
- Reminder about Team Guests
- New Public Teams without Guests
- Single Owner Reminder with Channel ID
- Public Teams Reminder with Channel ID
- Target Specific Team Members by AD attributes
- Teams Activity Reminder with Channel ID
- New Public Teams without Guests
-
-
- Summary
- Activity by Country and Modality
- Active User Counts
- Active User Percentages
- Active User Percentages All Bands
- Month on Month
- Device Usage
- Device Usage Details
- Avg Use Per User Per Day by Country
- Relative User Activity
- Users and Attributes
- Custom AD Attributes
- Data Freshness Detail
- Daily Active Users
- Weekly Active Users
- Monthly Active Users Percentage
- Relative Daily Active Users
- Relative Weekly Active Users
- Relative Monthly Active Users
- Activity Counts Daily
- Activity Counts Weekly
- Activity Counts Monthly
- Per User Activity Daily
- Per User Activity Weekly
- Per User Activity Monthly
- Show Remaining Articles10 Collapse Articles
-
- Team Stats
- Teams Distribution
- User Collab Activity
- Collab Activity (Averages)
- Collab Activity (Totals)
- User Mention Activity
- Team Files
- Per Team Profile
- Guest Distribution
- Guest Details
- Users and Attributes
- Threads Country Interaction
- Replying Country Interaction
- Threads Department Interaction
- Replying Department Interaction
- Active Teams Files and Chat
- Teams Channel Chat Activity
- Data Freshness Detail
- Show Remaining Articles3 Collapse Articles
-
- Meeting Trends
- Meeting Detail
- Meetings Per User Trends
- Meeting Join Stats
- Meeting Join Dashboard
- Meeting Joins by Country
- Meeting Join Country Detail
- Meeting Joins by User
- Calls Per User Trends
- Call Stats
- Calls Dashboard
- Calls by Country
- Calls Country Detail
- Calls by Users (All)
- Calls by Users (Last 14 days)
- Interaction Overview (Last 14 days)
- Call Interactions (Last 14 days)
- Meeting Interactions (Last 14 days)
- Show Remaining Articles3 Collapse Articles
-
-
-
- Querying the RAW JSON Call Records Files
- Data Issues with Microsoft Teams user activity Get user detail Endpoint
- Check Data Freshness from Microsoft Reporting API
- Get Call Record from Graph
- Calls and Meetings Database Schema
- Deploy a Calls & Meetings Automation scenario (CAT)
- CAT Installs – Customer Monitoring
- Configure Task Scheduler for Automation
- SQL Backups
- CAT Configuration Notes
- Data Nuances
- DeadLetterManager
- Calls and Meetings Aggregate Table Calculations
- Anonymisation of Selected Users PII Data
- Excluding teams from file scan
- Configure Custom User Attributes – Usage and Governance
- Configure Data Retention – Usage and Governance CAT
- Data Collection Configuration (Scan)
- Show Remaining Articles3 Collapse Articles
-
- Call Queue and Auto Attendant data
- Collecting Logs – Usage and Governance
- Comparing Teamwork Analytics to other solutions
- Data Collection Explained Usage and Governance
- Data Dictionary and Reporting Capabilities Usage and Governance
- Decommission
- Determining current data collection state
- FAQ Usage and Governance
- Files / Drive Items
- Messages
- Monitoring and Maintenance Tasks Usage and Governance CAT
- Relative User Activity Thresholds
- Security Details
- Usage and Governance Data Collected and Capabilities
- Usage and Governance Dependencies
- Calls & Meetings Definitions
- Database Version
- Show Remaining Articles2 Collapse Articles
-
-
Teams Audit
-
Teams Chat Assist
-
OneConsultation
< All Topics
Print
Calls and Meetings Aggregate Table Calculations
PostedJuly 2, 2024
UpdatedJuly 2, 2024
The TWA Database contains both the [aggregates].[P2PMinsByUsers] and [aggregates].[ConferenceMinsByUsers] tables. These tables are updated by their respective stored procedure which is exucted once per day by the CallAggregating function. The aggregation is done for the previous day as we should already have all the data for that day.
The tables are split by their call type, groupCall/Conference and peerToPeer. This is done for both ease of use and performance reasons. Both tables consist of the same properties as follows:
- Id: A unique Identifier for this row.
- _HashUserId: The SHA256 hash of the Caller/Callee Id.
- UserId: The Id of the Caller/Callee. This could be their mobile for a pstn user, an azure id for a teams user or null if the user is Unknown or NoIdentity.
- UserType: The type of user, defined by the Identity objects of the call record. Can either be 0 (Unknown), 1 (Internal), 2 (External), 3 (Pstn) or 4 (NoIdentity).
- Date: The aggregation date.
- TotalSegmentMinutes: The sum of minutes in any modality a user has sent/received in calls they’ve been in.
- AudioMinutes: The sum of audio minutes a user has sent/received in calls they’ve been in.
- VideoMinutes: The sum of video minutes a user has sent/received in calls they’ve been in.
- DesktopShareMinutes: The sum of desktop share minutes a user has sent/received in calls they’ve been in.
- TotalConferenceCount / TotalCallCount: The sum of streams in any modality a user has in calls they’ve been in.
- AudioConferenceCount / AudioCallCount: The sum of audio streams a user has in calls they’ve been in.
- VideoConferenceCount / VideoCallCount: The sum of video streams a user has in calls they’ve been in.
- DesktopShareConferenceCount / DesktopShareCallCount: The sum of desktop share streams a user has in calls they’ve been in.
For users that don’t have a UserId/_HashUserId, which would normally be users of UserType 0 (Unknown) or 4 (NoIdentity). Instead of having a row each they are squashed together into a single row for that aggregation date and UserType. You would typically only see these rows in the aggregated Conference table as the Callee of each segment is almost always going to be a Microsoft service endpoint which doesn’t have an Identity.
Table of Contents