Reinvent Telecom experienced a minor incident on August 16, 2023 affecting Max UC, lasting 3h 14m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Aug 16, 2023, 02:39 PM UTC
Microsoft has identified a problem with the MaX Meeting server and are diligently working to correct the issue. At this time, customers may experience issues creating or joining meetings. We will update you as soon as we hear back from the vendor.
- monitoring Aug 16, 2023, 04:30 PM UTC
Microsoft has deployed a fix to remediate this issue, but has noted that may be several hours before these changes propagate to all users.
- resolved Aug 16, 2023, 05:54 PM UTC
Metaswitch has cleared the issue with MaX Meeting. Thank you for your understanding as we navigated this issue. In the event that you or your customers are experiencing any trouble, please follow the appropriate process listed below from Metaswitch. If still you have additional issues, please contact our Support line at 855.245.1433 or open a service request in ServiceNow. For MaX Desktop users please follow these steps if your trouble persists: If your business runs their own DNS server, ensure that the cache on it is flushed. Exactly how to do this will depend on the exact DNS software in use. For the end user: On Windows: Open a CMD window as administrator Type "ipconfig /flushdns" Restart MaX UC On Mac: Open a Terminal window Type "sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder" Restart MaX UC If things still do not work, then it's likely cached at a centralized DNS server. Unfortunately you will need to wait for that cached entry to expire. This could take up to 2 days. For iPhone users to clear the cache, please place your phone briefly into "Airplane Mode" and back to normal.
- postmortem Aug 16, 2023, 07:45 PM UTC
Earlier today, MaxUC meeting experienced a GLOBAL outage. This outage was due to an SSL certificate issue which caused the MaxUC meeting functionality to fail until it could be corrected by Metaswitch. The certification issue originated with Metaswitch, and all service providers were affected until they resolved the issue and DNS replication was completed.