Pexip incident
SIP Guest Join calls to Microsoft Teams meetings with 13-digit Meeting IDs may fail to connect
Resolved after 6 hours 10 minutes, affecting Connect for Microsoft Teams Meetings and One-Touch Join, on April 11, 2025.
The Cloud OTJ fix has been implemented, and we are currently monitoring the results. For customers using the Ad Hoc Join for Teams macro on Cisco endpoints, we recommend updating the meetingId regex in the msteams_macro_settings.js configuration file to support 13-digit Meeting IDs. If you have any questions or need support related to this update, please reach out to your Pexip authorized support representative.
Affected components
Update timeline
- investigating Apr 11, 2025, 07:02 AM UTC
We are currently investigating an issue affecting SIP Guest Join calls to Microsoft Teams meetings. Users may be unable to connect to meetings when the Meeting ID is 13 digits long.
- identified Apr 11, 2025, 07:39 AM UTC
A fix has been implemented for the SIP Guest Join call connectivity issue. Our team is now working on a related problem where Microsoft Teams meetings with 13-digit Meeting IDs may not be correctly recognized by Cloud OTJ. A fix for this is currently being implemented.
- monitoring Apr 11, 2025, 09:39 AM UTC
The Cloud OTJ fix has been implemented, and we are currently monitoring the results. For customers using the Ad Hoc Join for Teams macro on Cisco endpoints, we recommend updating the meetingId regex in the msteams_macro_settings.js configuration file to support 13-digit Meeting IDs. If you have any questions or need support related to this update, please reach out to your Pexip authorized support representative.
- resolved Apr 11, 2025, 01:12 PM UTC
This incident has been resolved.
Your product runs on more than Pexip
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services