black and brown rotary phone near gray wall

Microsoft Teams integration for analog and DECT endpoints

9 months have passed since my first article on this topic and I have had the opportunity to gain first experience with the extended possibilities for connecting devices without a Teams app.

Microsoft offers the SIP Gateway as connection instance for those endpoints. Via the SIP Gateway for Microsoft Teams, both analog and DECT devices can be integrated into Microsoft Teams. In addition to the name search for these endpoints in Microsoft Teams, this integration also includes the display of a presence status (e.g. as in a call during an active call). In addition, advanced functions like

  • Voicemail
  • Member in Microsoft Teams Call Queues
  • Rufumleitung
  • Busy-on-busy

are available. Prerequisite is the M365 license Teams Shared Device. In addition, the manufacturer and model of the ATA or DECT components must have undergone a certification process with Microsoft and be listed as a certified solution.

Other typical use cases for DECT infrastructures such as

  • Alarming
  • Emergency systems (Men-fell-down)
  • Central addressbook

still require additional, local Server components.

Endpoint integration

Nothing has changed since March, the connection of the end devices with the SIP Gateway for Microsoft Teams is complex:

  1. The hardware is supported with specified firmware versions only. Often, a firmware upgrade of all devices is necessary, depending on the manufacturer, additional costs may be incurred.
  2. A user account must be created for each device and a Teams Shared Device license must be assigned.
  3. Each MAC address must registered individually, a mass upload of the information in a csv is possible.
  4. Each endpoint must be activated individually by a voice call.
  5. Each endpoint must be remote signed-in individually with the user account created for this purpose.


For Teams phones, Microsoft provides centralized management of basic settings through configuration profiles. In these configuration profiles, for example, the language of the Teams app in the menu, date and time as well as network configuration can be distributed centrally. In addition, software updates can be installed centrally on Teams phones and monitoring of the device status is possible.

This image has an empty alt attribute; its file name is 2022-12-22-16_51_18-Clipboard-1024x213.png
This image has an empty alt attribute; its file name is 2022-12-22-16_53_20-Clipboard.png

For devices connected via the SIP gateway, Microsoft does not offer central management options. Customers still have to rely on solutions from the manufacturers in this case.

This image has an empty alt attribute; its file name is 2022-12-22-16_54_42-Clipboard-1024x245.png

I’m not sure about reliability of health monitoring yet: Both devices shown in the screenshot were disconnected from the network for several weeks (the Polycom VVX) or reset to factory settings re-configured with a local setup (the AudioCode MP-112), but the ATA is still displayed as Healthy.

My special thanks go to Dennis Jakob, who shared his personal experiences with the integration of a certified DECT solution with me.

Published by Natalie Jeschner

Natalie quit her profession as a social worker 2000 and started her IT career as a support employee. She sticked to error analysis and troubleshooting in enterprise infrastructures for 15 years and discovered her passion for Collaboration, Unified Communication and VoIP during that time. Her focus is on the design and implementation of VoIP infrastructures with Microsoft UC solutions for several years now.
%d bloggers like this: