Teams Presence synchronization for a 3CX on premises

 The recent posts about setting Teams presence and being notified about Teams presence changes are the building blocks to synchronize the presence state between MS Teams and our 3CX PBX both ways.

• a call on Teams sets the 3CX presence state to "Away" if it was "Available" before
  
• if Teams becomes "Available" and 3CX state is "Away" => set 3CX to "Available"
• a call on 3CX tries to set the Teams presence "Busy" - there is some logic behind the scenes, we can't control about overriding "Offline" and "Away" in Teams which comes in handy in this case
  

Teams Presence Notification via CLI

Receiving phone calls on our regular soft phone while in a Teams meeting is quite annoying. It would be quite useful to set the soft phone presence according to the Teams presence.

In my last blog entry I wrote about how to do this the other way around.

Microsoft moved the notification on Graph changes via webhook from beta to 1.0 some time ago. Yet there are a few obstacles to overcome:

• the need for a webhook listening service that handles validation
• since presence state notification contains rich information data needs to be encryted/decrypted
• for now Presence.Read.All only supports delegated permissions, which requires some sort of user interaction when first acquiring a token

Teams Presence Status via CLI

 Microsoft finally came around at the beginning of this year to open the option to set the (Teams) presence state via their MS Graph API.

For my Asterisk telephony application this comes in handy as I can now set Teams busy when a user is on the phone.

Blue Boxing 2.0

Was müssen das für aufregende Zeiten gewesen sein, als es dank "Security through Obscurity" sooo viel zu entdecken gab. Ich kann mich noch gut an das aufregende Gefühl bei meiner ersten (legitimen) Modem-Einwahl in einen Unix-Server erinnern, aber das war fast zehn Jahre nach War Games eigentlich nichts Besonderes mehr... für echtes Phreaking bin ich wahrscheinlich eine halbe Generation zu alt (und wahrscheinlich nicht talentiert genug).

Ein kleines Revival erfuhr das Phone Phreaking mit den innovativen Features der neuen Mobilfunkbetreiber (ViagIntercom - O2). Die angebotene Festnetznummer und kostenlose Rufumleitungen innerhalb des gleichen Netzbetreibers führten Anfang der 2000er Jahre zur Möglichkeit einer BWHZ (Bundesweite Home Zone) - d.h. man war Deutschlandweit unter der (damals kostengünstigeren) Festnetznummer erreichbar.

In Kombination mit den damals verfügbar werdenden VoIP-Festnetz Flatrates und einem Asterisk-Server haben wir unsere ganz eigene BWHZ gebaut, die in logischer Konsequenz auch kostenlose Anrufe ins O2-Netz ermöglichte.