VoIP:VTX VPBX Teams Presence Synchronisation

With VTX VPBX Teams Presence Synchronisation, you can use the best of both VTX VPBX and MS Teams features syncing the "Rich Presence" status between Teams and VTX VPBX. I.e it means that call status and presence status ( "busy", "in a meeting", "presenting", "do not disturb") status are sync bidirectionally.

This feature could be used with or without the combination of VTX Teams Virtual service.

Introduction

• History: Since the upgrade of VTX VoIP platform to version 7 in late 2022, VTX VoIP platform does have an OpenAPI interface that allows to interact with other external tools. An a dedicated integrated framework has been developed to easily sync VTX and Teams Rich Presence

• How it works: We do have VTX and Teams APIs talking to each other to exchange real time information about presence status. A restricted API account needs to be created on both platforms to have them being able to talk to each other. Then, we only have to link each VPBX user with his Teams Email address to start the presence sync.

• What does it do : Sync VTX/Teams Rich Presence status in real time. Allowing not to be bothered by a Teams Call when on a "normal" VoIP call, or the other way around. Here are a few simple use cases

1. Teams->C5: Be visible as "presenting" on VoIP platform while sharing screen in a Teams Call
2. Teams->C5: Be visible as "in a meeting" on VoIP plarform while in a Teams Meeting in calendar
3. C5->Teams: Be seen as busy in Teams while on the "normal" phone

Setup Process Overview

Here is the process that will allow you to setup the service

1. Follow requirements below VoIP:VTX VPBX Teams Presence Synchronisation#Requirements
2. Perform Azure AD setup ( create Application + API User + Certificate )
3. Perform VTX C5 Setup ( Link Credentials + Certificate)
4. Setup VTX/Teams User mapping

"VTX VPBX Teams Presence Synchronisation" value added features

• Sync Rich Presence Status between VTX VPBX and MS Teams to benefit from both world without being visible as available when it is not the case

Requirements

You will find below all the needed requirements to use VTX VPBX Teams Presence Synchronisation Service

1. a VTX VPBX Service
2. A Microsoft 365 domain and accounts
3. A Microsoft Azure Portal Admin account

Azure AD Setup

Create an Azure App Registration

• Problematic: We would like to create an Azure App Registration named "VTX MS365 Presence Sync" to sync VoIP Platform and Azure ( that we will restrict to presence status sync only afterwards)
• Solution: Follow procedure below

1. Connect to https://portal.azure.com/ with an Admin Account of the domain you wish to sync presence status with the VoIP platform
2. Select the "Azure Active Directory" service in the list ( if not visible, click on the "More service" option or search for it )
3. Open the "App registrations" and create a new Registration in https://portal.azure.com/#view/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/~/RegisteredApps
   1. Name = "VTX MS365 Presence Sync c<CUSTOMERNUMBER>" ( ex: "VTX MS365 Presence Sync c429080" because 429080 is my VTX Test customer number)
   2. Set App as "Single tenant" access
   3. Click the "Register" button
4. Copy the value of "Directory (tenant) ID" in a notepad that will be required later (n°1)
5. Copy the value of "Application (client) ID" in a notepad that will be required later (n°2)

Azure AD - App Registration - Create App

Azure AD - App Registration - Copy Directory and APP Id

Create a Client Secret

• Information: To authenticate an access to the App, we 1st create a "secret" key, we will create a certificate to enhance security even more in next sections
• Problematic: Within the "VTX MS365 Presence Sync" App, create a "Client secret"
• Solution: Follow procedure below

1. Within the "VTX MS365 Presence Sync cXXXXX" app, go in the Certificates & secrets menu
2. Go in the "Client secrets" Tab
3. Click on "+ New client secret"
   1. Set Description = "MS365 Presence Client Secret cXXXXX"
   2. Set Expires = Maximum 730 days ( 24 months )
   3. Click the "Add" Button
4. Copy now the "Value" of the secret in a notepad and store the value for later use (n°3)

Azure AD - App Registration - Client secret Generation