techhub.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A hub primarily for passionate technologists, but everyone is welcome

Administered by:

Server stats:

4.7K
active users

#calling

1 post1 participant0 posts today

Microsoft Teams Call Queue no agents opted or logged in

Have you ever wondered how to cope with calls in Call Queues if there is no agent signed in? Well, there is another option now available which enables you for building smoother call flows in Microsoft Teams. The following screenshots will show you what’s new and what can be configured.

Source: Microsoft Teams Admin CenterSource: Microsoft Teams Admin Center

This section with „No Agents Opted/Logged In“ is new (July 28, 2023).

Source: Microsoft Teams Admin Center

As you can see here, there are four settings available. First of all, you can decide if the setting should only be applied for new incoming calls (or all calls/callers in the queue).

The next thing you can configure is what you would like to happen if there is no agent online (available to be called/opted in the queue) for this queue. Well, „Disconnect“ is the worst you could do for a smooth call flow (if the call flow’s termination/end is not reached), and queuing „Queue call“ is the default, so that’s why there is „Redirect call to„.

Source: Microsoft Teams Admin Center

„Redirect call to“ should be the way to go and that’s where you can define what should happen in case. So there you’ve got the common and known options available to forward it to „Person in organization„, „Voice app„, „External phone number„, „Voicemail (personal)“ or „Voicemail (shared)„.

Conclusion, opinion and summary

Alright, that’s pretty nice! It can help in certain situations to leave no caller behind if (suddenly) agents are opting out for receiving calls or are not logged in anymore. To me this is defintly going to be a standard I’ll direct leverage in my Teams telephony projects with call queues.

Resources

Transitioning Teams Android Devices to AOSP Device Management from Device Administrator

This blog post is about the required transition of Teams Android devices to the Android Open Source Project (AOSP) Device Management in Microsoft Intune. This is a new mobile device enrollment method which requires some actions to be completed to keep your Teams Android devices up and running. The current method is the Android Device Administrator for Teams Devices on Android.

  1. Device Management Changes for Microsoft Teams Android Devices
  2. What is Android Device Administrator?
  3. What is AOSP?
  4. What steps do I have to configure at least?
    1. Configure new AOSP management enrollment profiles
    2. Configure AOSP Management Configuration Policies
    3. Configure AOSP Management Compliance Policies
    4. Deploy AOSP Management capable device firmware
  5. Extended Token Expiration in Intune AOSP Device Enrollment Profile (October 8, 2024)
  6. Updating Teams Phone (Yealink MP56, October 8, 2024)
  7. 📫 Update December 10, 2024 📫
  8. 📫 Update June 22, 2025 📫

Device Management Changes for Microsoft Teams Android Devices

Source: Microsoft 365 message center MC665936 Device Management Changes for Microsoft Teams Android Devices

What is Android Device Administrator?

Android Device Administrator in Microsoft Intune is a legacy method for managing Android devices, allowing IT admins to enforce policies and manage apps on enrolled devices. However, this method is being deprecated, with support ending on December 31, 2024, for devices with access to Google Mobile Services (GMS). Admins are encouraged to transition to Android Enterprise for more advanced and secure management options. In case of Teams Android Devices AOSP is the way to go.

What is AOSP?

Android Open Source Project (AOSP) Management in Microsoft Intune is designed for managing corporate-owned Android devices that do not use Google Mobile Services (GMS). It allows IT admins to enforce policies and manage apps on these devices, which are often used for specific tasks or shared among multiple users. Transitioning to AOSP Device Management is recommended if you have been using Android Device Administrator, as it provides a more secure and modern management solution.

What steps do I have to configure at least?

To enable AOSP you must enable and configure it in your Microsoft Intune tenant accordingly. The following steps provide an overview:

  1. Configure new AOSP management enrollment profiles
  2. Configure AOSP Management Configuration & Compliance Policies
  3. Deploy AOSP Management capable device firmware

Configure new AOSP management enrollment profiles

  • Corporate-owned, user-associated devices
  • Create profile
  • Save the profile

Configure AOSP Management Configuration Policies

I’m not walk through these steps because currently only the Device Restrictions profile with “block screen capture” is allowed. Furthermore, this is optional.

Configure AOSP Management Compliance Policies

Also, the supported set for device compliance is limited to:

  • rooted devices can be blocked
  • minimum OS version
  • maximum OS version
  • System Security Require encryption of data storage on device

Deploy AOSP Management capable device firmware

This step cannot be carried out currently via the Teams Admin Center (TAC) because the AOSP firmware is not yet there but will probably become available during H2 2024.

If the configuration was successful Microsoft says that it should later on show the Microsoft Intune and Authenticator App on the Teams Android device as the following screenshot by Microsoft shows.

Source: https://learn.microsoft.com/en-us/microsoftteams/rooms/android-migration-guide#setup-aosp-management-enrollment-profiles

To compare it, currently before AOSP it should look like this:

Source: Screenshot, see TAC Devices \ Phones \ <Device> \ Health

Extended Token Expiration in Intune AOSP Device Enrollment Profile (October 8, 2024)

Microsoft changed the validation period for AOSP Device Enromment Profile tokens. That’s why I deleted the old AOSP profile and created a new one because the old one blocked me from creating a new, second one. The following screenshot shows the expiration date in the year 2089 not just a few days in the future.

Updating Teams Phone (Yealink MP56, October 8, 2024)

Recently I checked my demo device, a Teams Phone, Yealink MP56 via Teams Admin Center. It displayed available updates, so I initiated the updates as the following screenshots show.

📫 Update December 10, 2024 📫

There is now a list available in the faq section showing a list of devices and when each is probably get its firmware upgrade automatically. https://techcommunity.microsoft.com/blog/microsoftteamssupport/moving-teams-android-devices-to-aosp-device-management/4140893

Source: https://techcommunity.microsoft.com/blog/microsoftteamssupport/moving-teams-android-devices-to-aosp-device-management/4140893

What’s also interesting to read is:

Isn’t Device Administrator being deprecated by end of year 2024? What happens if my devices haven’t migrated to AOSP by then?

Although Device Administrator will be deprecated by end of year for devices with GMS, Teams Devices are not GMS devices and therefore will remain supported with Device Administrator for Intune enrollment until AOSP migration is completed as Device Administrator is not being deprecated for non-GMS devices. 

📫 Update June 22, 2025 📫

After my Yealink MP56 was offline for some time, I reconnected it to bring it back online. I noticed that a firmware upgrade had been carried out. After it finished, I could finally see that it was on AOSP by checking the Software Health via TAC.

Resources

Calling Comey? McCabe says Rosenstein wanted Comey’s advice

Calling Comey? McCabe says Rosenstein wanted Comey's advice - CBS News Watch CBS News Rod Rosenstein asked to contact James Comey for advice about appointing a special counsel -- after Comey's firing -- says McCabe. Be the first to know Get browser notifications for breaking news, live events, and exclusive reporting. Not Now Turn On #Calling #Comey #McCabe #Rosenstein #wanted #Comeys #advice

12sknnews.com/calling-comey-mc

Calling Comey? McCabe says Rosenstein wanted Comey's advice
12sknnews · Calling Comey? McCabe says Rosenstein wanted Comey's advice - 12sknnewsCalling Comey? McCabe says Rosenstein wanted Comey's advice - CBS News

#calling : a crying aloud, esp. in order to summon, or to attact the attention of, some one

- French: appelant

- German: Ruf, Aufforderung, Bestimmung

- Italian: chiamata

- Portuguese: chamando

- Spanish: llamando

------------

Join our new Discord Server for language learners @ wordofthehour.org/discord

DiscordJoin the Learn A New Language Discord Server!Check out the Learn A New Language community on Discord - hang out with 421 other members and enjoy free voice and text chat.

Configure Microsoft Teams Calling Plan Spend Limit

In this post I like to highlight that a new configuration option for calling plans appeared in the Microsoft Teams Admin Center. To be more precise, in the calling policies. As you can see in the screenshot below [May 2025]: Now you can configure PSTN Spend limits to set a monthly limit the overall consumption – and costs – for making PSTN calls beyond the included calling plan amount.

At the time of writing this post the documentation was not yet updated to include more details but I assume this will soon change. You can configure it in an individual calling policy to assign it for specific users as well as using the global / org-wide calling policy for it.

Resources

New Call Waiting Beep in Microsoft Teams

Microsoft announced an audio indicator for another incoming voice call so that you are going to know that there is another (second) caller waiting for you to answer a call. In the current roadmap it is said that the beep is a soft tone in order not to disrupt or disturb to intense. The feature is planned to be rolled out starting from June 2025 onwards.

How will this affect Microsoft Teams calling users?
Well it depends on the configuration especially on the calling policy’s busy settings. If users can receive multiple calls or not, e.g. busy on busy (BOB) enabled (by admin or user, personal decision).

Source: Microsoft 365 roadmap feature id 491472 Microsoft Teams: Call Waiting Beep Enabled on Desktop

Resources