
Telephony Security is being SHAKEN and STIR'd and now it's going flat.
See what's SHAKEN in the US Telephony industry and getting everybody STIRd up about. For these and more puns, and maybe some insightful information, have a read.
See what's SHAKEN in the US Telephony industry and getting everybody STIRd up about. For these and more puns, and maybe some insightful information, have a read.
Microsoft have recently announced they will be 'addressing a gap' in their systems by introducing additional licence checks to prevent bot-initiated PSTN call transfers, effective June 2025.
Why do it yourself when you can make Dynamics 365 do it for you? This is a workaround for a common SharePoint Document Integration 'issue'.
"Something went wrong" best error message ever, so versatile... fits every situation.
Microsoft at it again, killing off something half decent but old for a inadequate 'modern' replacement with a fraction of the capabilities.
Step by step, turning a local Node.js prototype into an Azure Function wrapped with a Custom Connector so it can be called easily from a Power Automate Flow.
Long awaited news about using existing Teams Phone deployment to extend telephone numbers in to Dynamics 365 Contact Center and any 3rd party solution that uses Azure Communications Services.
One of the Power Automate Flows wasn't showing up for a specific person, but it was still fine for everybody else. Here's how I tracked down and resolved the issue.