Monitoring - We have discovered that recent updates to the Teams clients on Mac and Windows have corrected the dialplan issue.
The known "good" versions are

Windows11 26043.2016.4478.27
MacOS 26072.603.4515.6584

The availability of these versions may vary by region, and may depend on your specific release channel.

Microsoft has escalated our case and seems to be taking it seriously.

Mar 31, 2026 - 22:54 EDT
Investigating - We have become aware of an issue with the latest versions of the Microsoft Teams clients. It appears as though the dialplan policy that should control outbound dialstring manipulation is not being obeyed, and the default Microsoft treatment is applied.

This may have different impacts depending on the specific dialplan rule customizations in a particular tenant, but the general effect is that any dialed number may have a '+CC' prefixed to the number before being sent onward. For example, dialing '1234' would typically be sent as '1234' using the default dialplan rule we install, but now we are seeing the number sent as '+11234' (which fails to reach the intended target and likely results in a rejected call).

The affected versions seem to include:

- MacOS desktop Version 26059.604.4471.2584

- Windows desktop 26058.713.4529.5861

There may be other versions on Mobile that have this issue as well.

Browser versions of Teams do not seem to have this problem.

We have opened a ticket with Microsoft. We will update this information as we receive updates.

Mar 28, 2026 - 18:13 EDT

About This Site

Information and Notifications about the Connector to Microsoft Teams from a SIP PBX.

PBX Connector Operational
90 days ago
100.0 % uptime
Today
Call App Operational
90 days ago
100.0 % uptime
Today
SIP Trunk Connector Operational
90 days ago
100.0 % uptime
Today
SMS Connector Operational
90 days ago
100.0 % uptime
Today
Provisioning Portal Operational
90 days ago
99.86 % uptime
Today
API Operational
90 days ago
98.72 % uptime
Today
Microsoft Teams SIP Gateway Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Apr 15, 2026

No incidents reported today.

Apr 14, 2026

No incidents reported.

Apr 13, 2026

No incidents reported.

Apr 12, 2026

No incidents reported.

Apr 11, 2026

No incidents reported.

Apr 10, 2026

No incidents reported.

Apr 9, 2026

No incidents reported.

Apr 8, 2026

No incidents reported.

Apr 7, 2026

No incidents reported.

Apr 6, 2026

No incidents reported.

Apr 5, 2026

No incidents reported.

Apr 4, 2026

No incidents reported.

Apr 3, 2026
Resolved - We believe that the error causing this issue was corrected as of 16:21 EDT. Please contact support if you continue to experience any problems. An RFO will be provided following a review of the incident to determine the root cause. We apologize for any disruption of service.
Apr 3, 16:24 EDT
Identified - The root cause of the issue causing instability to provisioning portals and API has been identified and a remedy is being applied. We are diligently working to resolve the issue in a timely manner a d expect service to resume normal operation shortly.
Apr 3, 16:14 EDT
Investigating - We are experiencing errors with the provisioning portals and API resulting in transactions relying on these components to fail. We are actively pursuing solutions and will provide updates as more information becomes available. Calling services are not affected.
Apr 3, 15:23 EDT
Apr 2, 2026

No incidents reported.

Apr 1, 2026

No incidents reported.