Is CallTower Down Right Now? Check if there is a current outage ongoing.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

border2.chi hardware update***Title:border2.chi hardware update***Possible impact:All PlatformsWe will be installing new hardware into Chicago core routers. No impact is expected***OutageNo

The log-in issue with CT Cloud Communicator issue is considered resolved and the associated cases will be closed out. Metaswitch identified a database syncing issue and CallTower Engineering performed a manual sync to restore services. Work is ongoing to ensure underlying issue is resolved. CallTower will be closing this master case and all associated cases. Within three business days, an Official Root Cause Analysis (RCA) or a Preliminary RCA will be available and provided to customers upon request.

CallTower Engineers are urgently working with Metaswitch to resolve the sign-in issue impacting CT Cloud Communicator. The root cause has been identified as a bug on Metaswitch’s end and is currently being escalated for resolution. Resetting the password for affected users has proven to resolve the issue. If you continue to experience difficulties signing in, please contact CallTower Support for assistance with resetting your password via CallTower Connect. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post additional updates as they become available. This issue is being investigated as a top priority.

The Vendor (Metaswitch) has identified a bug, and their Engineering and DEV teams are working urgently towards resolution. If you continue to experience the issue, reach out to CallTower Support, who can assist you in resetting your password through CallTower Connect. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 60 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower Engineers are actively collaborating with the vendor to identify the root cause of the sign-in issue impacting CT Cloud Communicator. We are also exploring a potential workaround as the investigation continues. If you continue to experience the issue, reach out to CallTower Support, who can assist you in resetting your password through CallTower Connect. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 60 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower Engineers continue to work closely with the vendor to urgently identify the issue affecting sign-in on CT Cloud Communicator. If you are still experiencing the issue, reach out to CallTower Support, who can assist you in resetting your password through CallTower Connect. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower continues to urgently investigate the issue impacting user sign-in on CT Cloud Communicator. CallTower has engaged the vendor to assist in resolving the issue. CallTower has determined that resetting a user's password through CallTower Connect resolves sign-in issues. If you need assistance, please contact CallTower Support. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower is investigating reports of customers not being able to log into the CT Cloud Communicator desktop application. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

The log-in issue with CT Cloud Communicator issue is considered resolved and the associated cases will be closed out. Metaswitch identified a database syncing issue and CallTower Engineering performed a manual sync to restore services. Work is ongoing to ensure underlying issue is resolved.CallTower will be closing this master case and all associated cases. Within three business days, an Official Root Cause Analysis (RCA) or a Preliminary RCA will be available and provided to customers upon request.

CallTower Engineers are urgently working with Metaswitch to resolve the sign-in issue impacting CT Cloud Communicator. The root cause has been identified as a bug on Metaswitch’s end and is currently being escalated for resolution. Resetting the password for affected users has proven to resolve the issue. If you continue to experience difficulties signing in, please contact CallTower Support for assistance with resetting your password via CallTower Connect.CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post additional updates as they become available. This issue is being investigated as a top priority.

The Vendor (Metaswitch) has identified a bug, and their Engineering and DEV teams are working urgently towards resolution.If you continue to experience the issue, reach out to CallTower Support, who can assist you in resetting your password through CallTower Connect. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 60 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower Engineers are actively collaborating with the vendor to identify the root cause of the sign-in issue impacting CT Cloud Communicator. We are also exploring a potential workaround as the investigation continues.If you continue to experience the issue, reach out to CallTower Support, who can assist you in resetting your password through CallTower Connect. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 60 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower Engineers continue to work closely with the vendor to urgently identify the issue affecting sign-in on CT Cloud Communicator. If you are still experiencing the issue, reach out to CallTower Support, who can assist you in resetting your password through CallTower Connect. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower continues to urgently investigate the issue impacting user sign-in on CT Cloud Communicator. CallTower has engaged the vendor to assist in resolving the issue. CallTower has determined that resetting a user's password through CallTower Connect resolves sign-in issues. If you need assistance, please contact CallTower Support.*CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower is investigating reports of customers not being able to log into the CT Cloud Communicator desktop application. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

The CallTower Engineering team has resolved an issue with customers using a limited selection of routes for increased T.38 compatibility. CallTower Support has tested several trunks and has confirmed the outbound issue to be resolved. CallTower will be closing this master case and all associated cases. Within three business days, an Official Root Cause Analysis (RCA) or a Preliminary RCA will be available and provided to customers upon request.

CallTower Engineering is actively investigating the issue causing outbound call failures with CT Cloud SIP. CallTower Support has set the trunk's outbound configuration to default as a workaround until a permanent resolution can be established. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower is investigating multiple reports of outbound calls failing for SIP trunking customers. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower has continued to work with Microsoft on the intermittent issue where Microsoft Teams call queues fail to properly receive inbound calls, instead triggering an immediate outbound call to the original caller. Microsoft is reporting that the issue was related to their incident TM1066289, which is included below. CallTower’s testing indicates that the issue has been resolved. From Microsoft: TM1066289 Title: Some call queue users are redirected on answering through Microsoft Teams to a new call with the caller User impact: Call queue users were redirected on answering through Microsoft Teams to a new call with the caller. Final status: We've confirmed that the recent change to call queue flow was resulting in impact and have since reverted this change. Upon completing the reversion, we reached out to a subset of impacted users who verified that our actions alleviated impact as expected. Scope of impact: Your organization was affected by this event, and call queue users were redirected on answering through Microsoft Teams to a new call with the caller. Start time: Wednesday, April 30, 2025, at 4:29 PM UTC End time: Thursday, May 1, 2025, at 10:00 PM UTC Root cause: A recent change to call queue flow was resulting in impact. Next steps: - We're analyzing the recent change further, and in tandem, are reviewing the methods in which we change call queue flow in an effort to avoid issues like this in the future. *CallTower will be closing this master case and all associated cases.

CallTower continues to work with Microsoft on the intermittent issue where Microsoft Teams call queues fail to properly receive inbound calls, instead triggering an immediate outbound call to the original caller. CallTower continues to escalate the issue with Microsoft and push for resolution. We will continue to provide updates as we receive them. If you are encountering this issue and CallTower is not your CSP, we strongly recommend escalating the matter directly through Microsoft support. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com.

CallTower engineers continue to work with Microsoft to urgently investigate the intermittent issue where Microsoft Teams call queues fail to properly receive inbound calls, instead triggering an immediate outbound call to the original caller. This appears to only be affecting a small portion of CallTower’s Microsoft Teams Customers. CallTower will continue to escalate and push for resolution. If you are experiencing this issue and CallTower is not your CSP, we strongly recommend escalating the matter directly through Microsoft support. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower continues to work with Microsoft to investigate an issue where inbound calls to Microsoft Teams call queues are intermittently not connecting as expected and are instead triggering outbound calls to the original caller. This issue appears to impact a small group of CallTower customers. We understand the impact this may have on your operations and appreciate your continued patience. If CallTower is not your CSP, we continue to recommend engaging Microsoft support directly for additional visibility and tracking on your tenant. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower is currently investigating reports of an intermittent issue where Microsoft Teams call queues fail to properly receive inbound calls, instead triggering an immediate outbound call to the original caller. We are actively working with Microsoft to identify the root cause and resolve the issue as quickly as possible. If CallTower is not your Microsoft Cloud Solution Provider (CSP), we recommend that you also engage Microsoft support directly to ensure proper escalation and visibility. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower continues to work with Microsoft on the issue causing some inbound calls to fail for Microsoft Direct Routing customers using Intermedia contact center. As of yesterday evening, CallTower has implemented a patch to resolve issues for all identified customers. CallTower will continue working with any additional customers who report related issues.

CallTower continues to work with Microsoft support to resolve the issue affecting Teams Direct Routing customers, which has been escalated for review and resolution. Our Management Team remains committed to securing a permanent resolution. In the meantime, CallTower has implemented effective workarounds, including migrating services to Microsoft Operator Connect or applying temporary fixes for Direct Routing—both of which are quick and simple processes. Our Support team has successfully migrated most impacted customers and remains available to assist those who wish to explore this option. If you're experiencing issues, please contact CallTower Support for assistance. *CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com as they become available.

CallTower Engineers have collaborated with Microsoft Support, providing detailed information that has been escalated to Microsoft's engineering team for review and solution development. Our Support team has successfully migrated most impacted Teams Direct Routing customers to Operator Connect. CallTower’s Management Team remains focused on escalating the matter with Microsoft to ensure a permanent resolution. CallTower can implement various workarounds to restore services for affected customers. If you're experiencing issues, please contact CallTower Support to migrate your services to Microsoft Operator Connect or apply a workaround to alleviate symptoms for Direct Routing —both of which are quick and simple processes. *CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

CallTower remains committed to urgently addressing the issue impacting inbound calls for certain Microsoft Teams customers using the Intermedia contact center. CallTower Support has migrated the majority of the affected Teams Direct Routing customers to Operator Connect. The CallTower Management Team continues to place a focus on escalating the matter with Microsoft to reach a permanent resolution. CallTower can implement various workarounds to restore services for affected customers. If you're experiencing issues, please contact CallTower Support to migrate your services to Microsoft Operator Connect or apply a workaround to alleviate symptoms for Direct Routing —both of which are quick and simple processes. *CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

CallTower remains committed to urgently addressing the issue impacting inbound calls for certain Microsoft Teams customers using the Intermedia contact center. While we actively implement a workaround for affected customers who have requested it, our management team continues to escalate the matter with Microsoft in an effort to reach a resolution. As an alternative solution, customers have the option to migrate their Teams Direct Routing services to Teams Operator Connect. This is a relatively quick and straightforward change. Customers interested in this migration are encouraged to contact CallTower Support for more details. *CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

CallTower continues to urgently address the issue affecting inbound calls for some Microsoft Teams customers using the Intermedia contact center. We are actively working with Microsoft to resolve the core issue while simultaneously implementing a workaround for affected customers. As an alternative solution, customers have the option to migrate their Teams Direct Routing services to Teams Operator Connect. This is a relatively quick and straightforward change. Customers interested in this migration are encouraged to contact CallTower Support for more details. *CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

CallTower Engineers are actively collaborating with Microsoft to resolve the issue affecting inbound calls for some of our Microsoft Teams customers using the Intermedia contact center. Resolving this issue remains our highest priority and is being urgently escalated. In the meantime, CallTower has implemented a workaround to help mitigate the impact while we continue troubleshooting. Customers experiencing this issue are encouraged to contact CallTower Support for assistance in applying the workaround. *CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

CallTower continues to work with Microsoft to investigate the intermittent issue affecting inbound calls for Microsoft Direct Routing customers using Intermedia contact center. CallTower engineers have rolled out a workaround while we continue to resolve the issue. CallTower will work with the affected customers to ensure the workaround is resolving inbound call issues. CallTower will continue to work this issue into the evening and provide further updates starting 8am MDT. *CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com.

CallTower continues to work with Microsoft to resolve the issue affecting some inbound calls for Microsoft Teams customers using Intermedia contact center. We are actively escalating the issue and pushing for a resolution. As an alternative, moving to Microsoft Operator Connect is an option. If you are interested in learning more, please reach out to CallTower Support. *CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

CallTower Engineers are actively working with Microsoft to resolve the issue affecting intermittent inbound call failures for Microsoft Teams customers using Intermedia Contact Center. CallTower continues to prioritize this issue and is working to resolve it as soon as possible. *CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

CallTower is actively troubleshooting the issue impacting inbound calls for Microsoft Direct Routing customers using Intermedia. We have identified an intermittent signaling problem originating from Microsoft and are working to engage Microsoft engineers for further investigation. If you are experiencing this issue and CallTower is not your Cloud Solution Provider (CSP), please contact our support team for guidance on how to request your CSP to escalate the matter with Microsoft. As an alternative, moving to Microsoft Operator Connect is an option. If you are interested in learning more, please reach out to CallTower Support. *CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

CallTower continues to urgently troubleshoot the intermittent issue impacting inbound calls for Microsoft customers using the Intermedia contact center. We have identified a call routing issue and are currently working to engage Microsoft to assist in resolving it. *CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

CallTower engineers are actively investigating the issue intermittently impacting inbound calls for Microsoft Direct Routing customers using Intermedia. Our engineering teams are working with the highest urgency to identify the root cause and implement a resolution as quickly as possible. We will continue to provide updates as more information becomes available. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower continues to urgently investigate the issue affecting inbound calls for Microsoft Teams. Reports seem to indicate that the issue only affects Microsoft Direct Routing customers using the Intermedia Contact Center. If you are experiencing an issue, please provide call examples of the issue to Support@calltower.com. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower support is investigating multiple reports of dropped calls on the Microsoft Teams side, but have not identified/confirmed there is an issue on our network or with our services. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower engineers have collaborated with our vendor to resolve the issue affecting some outbound calls. We are now observing successful traffic completion. CallTower will be closing this master case and all associated cases. Within three business days, an Official Root Cause Analysis (RCA) or a Preliminary RCA will be available and provided to customers upon request.

CallTower has identified the issue affecting the completion of some outbound calls. CallTower engineers are urgently working with our vendor to implement a fix. *CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

CallTower is urgently investigating reports of some outbound calls failing. We have engaged our carrier to assist in the investigation. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

Microsoft has confirmed that the fix has been deployed and the issue has been resolved. Microsoft’s final update is provided below. Issue ID: TM1022107 Affected services: Microsoft Teams Status: Service restored Issue type: Incident Start time: Mar 3, 2025, 9:46 AM MST End time: Mar 3, 2025, 1:19 PM MST User impact Users may not have been able to receive calls placed through Microsoft Teams provisioned auto attendants and call queues More info Callers routed through call queues may have heard a busy signal or the call may have rung for 45+ seconds and then ended. Scope of impact Users who expected to make or receive calls routed through Microsoft Teams provisioned auto attendants and call queues may have been affected. Preliminary root case A configuration change to an auto-attendant app ID record that matches inbound calls with users in call queues was preventing users from receiving calls and caused the impact. Next steps - We’re reviewing our testing and validation processes to understand how the impact of the configuration change wasn’t identified prior to implementation so that we can improve our testing and validation procedures and avoid similar issues in the future. We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days. Current status Mar 3, 2025, 1:50 PM MST Our fix was successfully deployed. After an extended period of monitoring, we’ve confirmed through telemetry that service is restored and impact has been fully remediated. *CallTower will be closing this master case and all associated cases.

CallTower has continued to work with Microsoft on the issue affecting inbound calling to auto attendants and call queues. Microsoft has applied a fix at this time. CallTower’s testing shows that calls are now completing as expected. Microsoft's update is provided below. Issue ID: TM1022107 Affected services: Microsoft Teams Status: Service degradation Issue type: Incident Start time: Mar 3, 2025 at 9:46 AM MST User impact Users may not be able to receive calls placed through Microsoft Teams provisioned auto attendants and call queues. More info Callers routed through call queues may hear a busy signal or the call may ring for 45+ seconds and then end. Scope of impact Users expecting to make or receive calls routed through Microsoft Teams-provisioned auto attendants and call queues may be affected. Preliminary root case A configuration change to an auto-attendant app ID record that matches inbound calls with users in call queues is preventing users from receiving calls and causing the impact. Current status Mar 3, 2025 at 1:20 PM MST We’ve deployed the configuration to the auto-attendant app and are seeing service functionality improvements as expected. We’re continuing to monitor to confirm the fix is mitigating impact. Next update by: Monday, March 3, 2025 at 2:30 PM MST *CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com.

Microsoft continues to work to resolve the issue affecting inbound calls to auto attendants and call queues for Microsoft Teams. Microsoft has provided an update which is included below. Issue ID: TM1022107 Affected services: Microsoft Teams Status: Service degradation Issue type: Incident Start time: Mar 3, 2025 at 9:46 AM MST User impact Users may not be able to receive calls placed through Microsoft Teams provisioned auto attendants and call queues. Scope of impact Users expecting to make or receive calls routed through Microsoft Teams-provisioned auto attendants and call queues may be affected. Preliminary root case A modification made to an auto attendant application ID record is rejecting Microsoft Teams call queues. Current status Mar 3, 2025 at 12:33 PM MST We've discovered that a modification to an auto attendant application ID record is rejecting Microsoft Teams call queues. We've deployed a fix to update the affected application ID record, which will mitigate impact. Next update by: Monday, March 3, 2025 at 1:30 PM MST *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. This issue is being investigated as a top priority.

CallTower continues to work with Microsoft on the issue affecting the completion of inbound calls for auto attendants and call queues. Microsoft has provided an update on the issue. Microsoft’s update is included below. Issue ID: TM1022107 Affected services: Microsoft Teams Status: Service degradation Issue type: Incident Start time: Mar 3, 2025 at 9:46 AM MST User impact Users may not be able to receive calls placed through Microsoft Teams provisioned auto attendants and call queues. Scope of impact Users expecting to make or receive calls routed through Microsoft Teams-provisioned auto attendants and call queues may be affected. Current status Mar 3, 2025 at 11:01 AM MST We've detected a potential authentication token issue that may be contributing to impact, and we're further examining this pathway to determine our next troubleshooting steps. Next update by: Monday, March 3, 2025 at 12:30 PM MST *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. This issue is being investigated as a top priority.

CallTower continues to work with Microsoft on the issue affecting the completion of inbound calls. Microsoft has acknowledged an issue affecting their services. Microsoft’s latest update is included below. Issue ID: TM1022107 Affected services: Microsoft Teams Status: Investigating Issue type: Incident Start time: Mar 3, 2025 at 9:46 AM MST User impact Users may not be able to receive calls placed through Microsoft Teams provisioned auto attendants and call queues. Scope of impact Users expecting to make or receive calls routed through Microsoft Teams-provisioned auto attendants and call queues may be affected. Current status Mar 3, 2025 at 10:11 AM MST Our monitoring has identified an increase in call failures for Microsoft Teams auto attendants and call queues. We're analyzing service telemetry and call metadata to better understand the nature of impact and determine our next steps. Next update by: Monday, March 3, 2025 at 11:30 AM MST *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. This issue is being investigated as a top priority.

CallTower support is investigating multiple reports of Microsoft inbound calls not completing. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower has identified the issue affecting outbound calling through Intermedia contact center. We have implemented a change and have confirmed that calls are again working as expected. CallTower will be closing this master case and all associated cases. Within three business days, an Official Root Cause Analysis (RCA) or a Preliminary RCA will be available and provided to customers upon request.

CallTower engineers continue to urgently investigate the issues affecting outbound calling through Intermedia contact center. We have this issue at our highest priority. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower is investigating reports of issues making outbound calls through the Intermedia contact center. Users report that the application gets stuck on the dial-out screen and is receiving a 55102 error. We have engaged Intermedia to assist in finding a resolution. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

The issue causing the “55102’ - “phone out of service error” in the Intermedia Contact Center has been resolved. CallTower has implemented a fix and validated that calls are completing normally. CallTower will be closing this master case and all associated cases. Within three business days, an Official Root Cause Analysis (RCA) or a Preliminary RCA will be available and provided to customers upon request.

We are receiving reports of test calls completing. CallTower engineers were able to implement a workaround as we continue to address the underlying cause of the inbound and outbound errors being received in the Contact Center application. Please continue to monitor and advise if you are experiencing any persisting issues. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We continue to investigate; Users will experience a "phone out of service error." (maybe identified as an 55102 error). CallTower engineers are working in conjunction with our vendor partner to identify the root cause of the inbound and outbound call failures and call drops occurring within the Contact Center application. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower engineers are actively investigating the root cause of the 55102 error being received in the Contact Center application. The issue is being treated with a high priority and we will continue to provide new information as it is made available. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower is investigating reports of customers receiving a 55102 error in the contact center application. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

The problem with users not being able to log into CT Cloud Communicator Desktop is fixed. CallTower worked with our vendor and found a bug that was preventing users from logging in. CallTower engineers are working on a permanent fix. Affected users should close and reopen the CTCC Desktop app, then log back in. CallTower will close this case and related cases. An Official or Preliminary Root Cause Analysis (RCA) will be available within three business days and provided to customers upon request. The issue is resolved, and the cases will be closed.

CallTower support is investigating multiple reports of users unable to log into the CT Cloud Communicator, but has not identified/confirmed there is an issue on our network or with our services. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower Support has confirmed with the affected customers that the inbound calling issues with Teams GCC High is resolved, and the associated cases will be closed out. Here is the resolution update from Microsoft: Title: Callers placing calls to Microsoft Teams hosted auto attendants and call queues may fail User impact: Callers placing calls to Microsoft Teams hosted auto attendants and call queues may be failing. Final status: We've completed our corrective actions to the affected configuration and validated this has remediated this issue with affected users and service telemetry. Scope of impact: Any calls placed to auto attendants and call queues hosted on the impacted infrastructure may have been impacted. Start time: Friday, November 1, 2024 at 7:58 AM MDT End time: Friday, November 1, 2024 at 3:18 PM MDT Root cause: A recent service configuration change contained an error, preventing auto attendant and call queues from operating as expected, resulting in impact. Next steps: - We're reviewing our configuration update procedures to better identify and prevent similar impact in the future. This is the final update for this event. CallTower will be closing this master case and all associated cases. Within three business days, an Official Root Cause Analysis (RCA) or a Preliminary RCA will be available and provided to customers upon request.

CallTower Engineering continues to work with Microsoft on the inbound calling issues with Teams GCC High. CallTower Support has tested with some customers and are getting positive tests back. Microsoft does not have any new updates posted. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

CallTower Engineering continues to work with Microsoft on the inbound calling issues with Teams GCC High. Here is the update from Microsoft: Title: Callers placing calls to Microsoft Teams hosted auto attendants and call queues may fail User impact: Callers placing calls to Microsoft Teams hosted auto attendants and call queues may be failing. Current status: Our monitoring has identified that a recent service configuration change contained an error, preventing auto attendant and call queues from operating as expected. We're in the process of correcting the configuration to remediate impact. Scope of impact: Any calls placed to auto attendants and call queues hosted on the impacted infrastructure may be impacted. Root cause: A recent service configuration change contained an error, preventing auto attendant and call queues from operating as expected, resulting in impact. Next update by: Friday, November 1, 2024, at 10:00 PM UTC CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

The issues with inbound calls to Auto Attendants and Call Queues for Microsoft Teams GCC High customers has been identified/confirmed as an issue with Microsoft. CallTower Engineering have a case open with Microsoft that they are actively escalating. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

CallTower support is investigating multiple reports of issues with inbound calls to Auto Attendants and Call Queues for Microsoft Teams GCC High customers. Engineers are working to identify the root cause of the issue. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

The issue with WebEx inbound and outbound calling is considered resolved and the associated cases will be closed out. CallTower will be closing this master case and all associated cases. Within three business days, an Official Root Cause Analysis (RCA) or a Preliminary RCA will be available and provided to customers upon request.

CallTower Support has received multiple reports from customers that the WebEx inbound and outbound calling symptoms have resolved. CallTower Engineering continues to investigate the cause of the WebEx inbound and outbound call disruption. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower support is investigating multiple reports of an inbound and outbound call failures on the WebEx Platform but has not identified/confirmed there is an issue on our network or with our services. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

Microsoft is reporting that the issue affecting inbound calls to Auto Attendants and Call Queues has been resolved. CallTower has confirmed the resolution in our testing. Microsoft’s incident TM907891 is included below. "Details Title: Users' calls routed through Auto attendants and Call queues within Microsoft Teams may fail User impact: Users' calls routed through Auto attendants and Call queues within Microsoft Teams may have failed. Final status: We've routed the affected call requests to a healthy portion of service infrastructure and confirmed through monitoring service telemetry that impact has been remediated. Scope of impact: Any user who attempted to make calls routed through Auto attendants and Call queues within Microsoft Teams may have been impacted. Start time: Thursday, October 10, 2024, at 3:51 PM UTC End time: Thursday, October 10, 2024, at 5:50 PM UTC Root cause: Auto attendant and Call queue call routed call requests were being routed to an unhealthy portion of service infrastructure, resulting in impact. Next steps: - We're continuing to monitor the affected infrastructure closely to gain further insight into the source of the underlying issue and better prevent similar impact in the future. - We’re assessing our automated recovery mechanisms in conjunction with our findings into the underlying problem to identify areas for improvement to reduce the time to mitigate similar future issues. This is the final update for the event." CallTower will be closing this master case and all associated cases.

CallTower continues to work with Microsoft on the issue affecting inbound calls to Teams Auto Attendants and Call Queues. Microsoft is working on rerouting traffic to fix this issue now and will provide further updates shortly. CallTower is seeing some successful calls in our internal testing and testing reported by customers.

CallTower continues to urgently investigate the issues affecting inbound calls for Microsoft Teams Operator Connect and Direct routing Auto Attendants and Call Queues. Microsoft has acknowledged a global outage at this time and is working to resolve it. If you need assistance in forwarding numbers, please reach out to support@calltower.com. Microsoft’s most recent update is provided below. Issue ID: TM907891 Affected services: Microsoft Teams Status: Investigating Issue type: Advisory Start time: Oct 10, 2024, 12:14 PM CDT Current status Oct 10, 2024, 12:14 PM CDT We're investigating a potential issue with users' Auto Attendant and Call Queue calls failing within Microsoft Teams, and we're checking for impact to your organization. We'll provide an update within 30 minutes.

CallTower is investigating reports of inbound calls ringing busy. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower Engineers have continued to monitor the issue and have not seen any further issues. CallTower believes the issue has been resolved. CallTower will be closing this master case and all associated cases. Within three business days, an Official Root Cause Analysis (RCA) or a Preliminary RCA will be available and provided to customers upon request.

CallTower Engineers have made a change to route around the issue. Our testing shows that calls are now completing as expected. CallTower will continue to monitor. If you are still experiencing an issue please provide Support with call examples to investigate. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

CallTower Engineers are aware of an issue causing call failures for our Teams Operator Connect and are working to resolve it. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower has continued to monitor the issue. Our testing and the testing of some of our customers have continued to show successful results. CallTower believes the issue is resolved. CallTower will be closing this master case and all associated cases. Within three business days, an Official Root Cause Analysis (RCA) or a Preliminary RCA will be available and provided to customers upon request.

CallTower Engineers have identified an issue and implemented a change. We have confirmed through testing that the issue with duplicate calls have been resolved. Please reach out to CallTower Support if you are still experiencing issues. CallTower will continue to monitor.

CallTower Engineers continue to investigate the issue of duplicate incoming calls for our Teams Operator Connect and Intermedia customers. Please continue to send in specific call examples to help us with our investigation. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower support has identified multiple reports of customer receiving inbound calls on the Teams Operator Connect platform. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

CallTower is investigating reports of customers receiving duplicate incoming calls on Intermedia. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

The call quality degradation and one way audio issue is considered resolved and the associated cases will be closed out. CallTower will be closing this master case and all associated cases. Within three business days, an Official Root Cause Analysis (RCA) or a Preliminary RCA will be available and provided to customers upon request.

CallTower engineers were able to isolate the root cause and have a workaround in place and will continue to monitor for any persisting issues. If you continue to experience trouble, please contact support right away. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com

CallTower engineers have identified a possible root cause and are continuing to treat this as a top priority. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

We see Traffic has stabilized and have confirmed that inbound and outbound calls are now completing. CallTower will be closing this master case and all associated cases. Within three business days, an Official Root Cause Analysis (RCA) or a Preliminary RCA will be available and provided to customers upon request.

We are nbow seeing traffic stabilize and getting reports from customers that services are back up in UK and Frankfurt. We are continuing to monitor at this time please retest and if you have any persisting issues, call support at 800-347-5444 and let us know. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com once more information is available, unless identified otherwise.

Efforts to resolve call failures in the UK and Frankfurt data centers are ongoing. Calltower engineers are looking at any possible workarounds while we work towards a resolution. More information will be provided as soon as it is made available. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower engineers are continuing to pursue a workaround while we isolate the underlying cause of the call failures. We will provide more information as it becomes available. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower’s engineering team is actively addressing the root cause of the issue while also exploring potential workarounds. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

The root cause of the failures in our UK and Frankfurt datacenters has not been identified at this time, but Calltower engineers are diligently working to isolate and additional updates will be provided as soon as more information is made available. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

Calltower engineers are continuing to actively investigate the call failures in our UK and Frankfurt datacenters. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

Service should be restored at this time. CallTower will be closing this master case and all associated cases. Within three business days, an Official Root Cause Analysis (RCA) or a Preliminary RCA will be available and provided to customers upon request.

CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise

CallTower Engineering has resolved issues involving inbound call failures for iOS (Iphone, Mac) using CT Cloud communicator. CallTower has confirmed with customers that services have been restored and believes the issue is resolved. Default messaging: CallTower will be closing this master case and all associated cases. Within three business days, an Official Root Cause Analysis (RCA) or a Preliminary RCA will be available and provided to customers upon request.

Identified: CallTower Engineering has identified an inbound call failure issue on our CT Cloud Communicator for users on iOS (Iphone, Mac) causing inbound calls to be directed straight to Voicemail. Default messaging: *CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

CallTower has continued to test and is confident that the issue affecting inbound calls to the Intermedia Contact Center has been resolved. Please reach out to support@calltower.com if you are still experiencing any issues. CallTower will be closing this master case and all associated cases. Within three business days, an Official Root Cause Analysis (RCA) or a Preliminary RCA will be available and provided to customers upon request.

CallTower is aware of an issue affecting inbound calls to Intermedia Contact Center. CallTower has deployed a fix and is testing now to confirm resolution. *CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com.

CallTower has confirmed with customers that services have been restored and believes the issue is resolved. There have been no further reports of the problem from customers. CallTower will be closing this master case and all associated cases. Within three business days, an official Root Cause Analysis (RCA) or a preliminary RCA will be available and provide to customers upon request.

CallTower Engineering continues to research the root cause for the inbound call issue on the CT Cloud Voice Platform. There have been no further reports of the issues from customers, and CallTower Support will continue to monitor the issue. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post the next update on status.calltower.com approximately at 8:00 AM MT, unless identified otherwise. This issue is being investigated as a top priority.

CallTower Support has confirmed with multiple customers that the issue is no longer occurring. Our team is working closely with Engineering to urgently identify and resolve the root cause of the inbound call issue on the CT Cloud Voice Platform, prioritizing this matter highly. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 1 hour, unless identified otherwise. This issue is being investigated as a top priority.

CallTower Support has confirmed with multiple customers that the issue is no longer occurring. Our team is working closely with Engineering to urgently identify and resolve the root cause of the inbound call issue on the CT Cloud Voice Platform, prioritizing this matter highly. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower Support has escalated with Engineering and continues to investigate the inbound call issue on the CT Cloud Voice Platform at a high priority but has not identified or confirmed the source of the issue. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower Support continues to investigate the inbound call issue on the CT Cloud Voice Platform, but has not identified or confirmed the source of the issue. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority

CallTower support is investigating multiple reports of an inbound call issue for the CT Cloud Voice Platform, but has not identified/confirmed there is an issue on our network or with our services. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

Intermedia is reporting that the issue affecting login and calling has been resolved. CallTower has also confirmed resolution with several customers. CallTower will be closing this master case and all associated cases.

CallTower continues to monitor the issue which is related to the global CrowdStrike outage. Intermedia reports that they are working with CrowdStrike to resolve the issue. Please reach out to CallTower Support if you need assistance in temporarily forwarding numbers. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com

CallTower continues to monitor the issue. We are currently pending an ETA on complete resolution but we have confirmed with some customers that they are again able to access the CCA application. We will continue to provide updates as we receive them. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com.

CallTower continues to work with Intermedia on the issue. Intermedia reports that the issue has been identified and a fix is being implemented. The Intermedia update is provided below. We do not yet have an ETA on resolution. Update from Intermedia: “Business impact: Some Account Administrators may continue to experience issues with login to Control Panels. Some users may continue to experience degraded performance connecting to services. Summary of issue: We want to update you on the significant global outage affecting Intermedia services due to a recent CrowdStrike update. This issue has disrupted many businesses worldwide, including airlines, banks, and technology companies. This outage has impacted Microsoft Windows systems that support Intermedia's services. Technical details: CrowdStrike has identified, isolated, and deployed a fix for the issue. Like all impacted organizations, we are now working to restore all our services. While many of our services are operational, some remain affected, and our teams are working tirelessly to resolve this as quickly as possible. We will keep you informed as we have more updates. Thank you for your continued patience and understanding.”

CallTower continues to work with Intermedia on the issue affecting access to the CCA application. Intermedia reports that they continue to be impacted by a global outage with CrowdStrike. The most recent intermedia update is provided below. CallTower will continue to monitor the issue and provide updates as we receive them. Intermedia Update: “Summary of issue: We want to inform you about a significant global outage that is currently affecting Intermedia services. This issue stems from a recent update by cybersecurity firm CrowdStrike, which has caused widespread disruptions for airlines, banks, media outlets, technology companies, telecom firms, and businesses and other organizations around the world. This outage has impacted Microsoft Windows systems that support Intermedia"s services. Business impact: Account Administrators may experience issues with login to Control Panels. Users may experience degraded performance connecting to services. Technical details: Many of our services and systems are working, but not all. CrowdStrike has communicated that they are in the process of rolling back the update that caused this issue. We understand the critical nature of the services we provide and regret any inconvenience this may cause. Our teams are working nonstop to resolve this issue as quickly as possible and to minimize the impact on your operations. We will keep you updated on the progress and provide further information as it becomes available. Thank you for your patience and understanding during this time. Jul 19, 2024 - 05:23 EDT”

CallTower is investigating reports of issues affecting the ability to log in and receive calls through the Intermedia contact center application. Intermedia is aware of the issue and has acknowledged that it is a part of a larger outage. Intermedia's most recent post is included below. CallTower will continue to work with the vendor and post updates as we receive them. From Intermedia: "Business Impact: Crowdstrike, a prominent security company utilized by Intermedia, is experiencing an outage that is affecting thousands of customers worldwide. Summary of issue: Our Team has identified a connectivity issue affecting some services availability due to a problem with Crowdstrike. The issue is being investigated and we will provide further updates as soon as we have them. Technical Details: Our Team has identified issues with service availability due to a problem with Crowdstrike. Crowdstrike is working to solve the issues and restore service as quickly as possible. We will provide further updates as soon as we have them."

Calltower has confirmed with vendor that the service disruption was related to the global Microsoft outage. Our partner has advised that service automatically recovered when the Azure service in Central US was restored and is now functioning normally. However, we will continue to monitor the situation closely. CallTower will be closing this master case and all associated cases. Within three business days, an Official Root Cause Analysis (RCA) or a Preliminary RCA will be available and provided to customers upon request. For more information, here are some links to news headlines related to the global outage: - https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.cnbc.com%2F&data=05%7C02%7Cdylan.lewis%40calltower.com%7C67c16343632949e60e8008dca7cde6b1%7C34a23b7014ed448cb453c1a79a3e5d27%7C0%7C0%7C638569750047095442%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=01BWviVjH8Kd6Jw5EpZsHIa4Iuj4P%2BvpywvUx3aD5VM%3D&reserved=0 - https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.bbc.com%2F&data=05%7C02%7Cdylan.lewis%40calltower.com%7C67c16343632949e60e8008dca7cde6b1%7C34a23b7014ed448cb453c1a79a3e5d27%7C0%7C0%7C638569750047594188%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=HfDw3Iomfq2PX6JDQOum5befpR7Dw5tNFtxAkwbnkYU%3D&reserved=0 - https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.cnbc.com%2F&data=05%7C02%7Cdylan.lewis%40calltower.com%7C67c16343632949e60e8008dca7cde6b1%7C34a23b7014ed448cb453c1a79a3e5d27%7C0%7C0%7C638569750047602998%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=733Ezq3EWkZpRhAdizf1vKCSX%2FzUPHwFUJ0BJL%2FhxjA%3D&reserved=0

Investigating: CallTower support has escalated with our vender and understand the urgency of this issue, CallTower will provide updates as they are received. Customers may experience loading issues, timeouts, or errors when trying to access the application in both Microsoft Teams and Webex. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com as we receive them., unless identified otherwise. This issue is being investigated as a top priority

Investigating: CallTower support is currently investigating an issue with the CT Text application. Customers may experience loading issues, timeouts, or errors when trying to access the application in both Microsoft Teams and Webex. We are working closely with our vendor to urgently address and mitigate the impact. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 60 minutes, unless identified otherwise. This issue is being investigated as a top priority.

This incident has been resolved.

Services have been restored for Operator Connect. Microsoft has identified an issue with their API code which is causing a memory leak. Microsoft is putting in a mitigation process (a redeployment of services) to control the leak until they can fully resolve the problem. CallTower and Microsoft will continue to monitor the issue and will provide updates once Microsoft has completed the code upgrade.

CallTower is investigating reports of delayed provisioning in CallTower Connect for Teams Operator Connect. Our Engineering teams are working with Microsoft to identify and resolve the issue. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. This issue is being investigated as a top priority.

CallTower will be closing this master case and all associated cases. Within three business days, an Official Root Cause Analysis (RCA) or a Preliminary RCA will be available and provided to customers upon request.

NOC engineers have confirmed with customers that services have been restored. Calltower engineers are going to continue to monitor the datacenters. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com as new information is made available.

Calltower engineers are continuing to monitor the call failures. A backend change has been made to alleviate some of issues in the New York datacenter, and the same change is currently being applied to our Los Angeles datacenter as well. More details will be provided as new information is made available. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

Calltower engineers are working with our vendors to eliminate the call failures we are seeing in our New York and Los Angeles SBC's. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority

We are currently investigating an issue with intermittent call failure. Calltower engineers are working diligently to isolate the root cause so a repair can be made. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority

We are currently investigating an issue with intermittent call failure. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority

Intermedia has applied a fix for the issue affecting users logging into the CCA application and report that the issue is now resolved. CallTower has confirmed with some affected customers that the login issue has been resolved. CallTower will be closing this master case and all associated cases.

CallTower is investigating reports of users having trouble logging into the Intermedia Contact Center application. Intermedia has acknowledged and issue and are working to resolve. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower Engineers have successfully implemented a fix to resolve the issue affecting CT Cloud Communicator notifications on iOS and MAC OS. CallTower will be closing this master case and all associated cases. Within three business days, an Official Root Cause Analysis (RCA) or a Preliminary RCA will be available and provided to customers upon request.

CallTower Engineers have identified the issue affecting CT Cloud Communicator notifications on iOS and MacOS. We are in the process of implementing a fix with an ETA of 3:30pm MDT. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com.

CT Cloud Communicator users using iOS and MacOS devices will not receive any notifications for missed calls, voicemails, IMs, etc. Calls and SMS/chat are not affected. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com as new information becomes available.

CallTower has continued to monitor the issue affecting the provisioning of Operator Connect numbers in Connect. CallTower has not seen any further occurrences of the issue. We are continuing to work with Microsoft to understand the root cause. CallTower will be closing this master case and all associated cases. Within three business days, an Official Root Cause Analysis (RCA) or a Preliminary RCA will be available and provided to customers upon request.

CallTower Engineers are now seeing Connect provisioning requests for Operator Connect complete successfully. Our testing and customer reports confirm the issue is resolved. CallTower is working with Microsoft to further identify the cause and ensure it doesn’t happen again. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com.

CallTower is investigating reports of processes not completing for Operator Connect number management in CallTower Connect. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com.

CallTower’s engineers have identified an issue and implemented a fix. Our internal testing and reports from our customers indicate that this issue has been resolved. CallTower will be closing this master case and all associated cases. Within three business days, an Official Root Cause Analysis (RCA) or a Preliminary RCA will be available and provided to customers upon request.

CallTower continues to investigate the issue affecting the number management of Teams Direct Routing in CallTower Connect. This is our top priority as our engineers urgently work to identify the issue. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com.

CallTower is investigating reports of customers receiving an error in Connect when trying to assign or release Microsoft Direct Routing numbers to users. CallTower Engineers are urgently investigating the issue. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com.

CallTower Engineers have continued to work the issue affecting the management of OC numbers in CallTower Connect. Number uploads are now going through in expected timeframes and all previously pending changes have been resolved. CallTower believes this has been resolved. CallTower will be closing this master case and all associated cases. Within three business days, an Official Root Cause Analysis (RCA) or a Preliminary RCA will be available and provided to customers upon request.

CallTower engineers have implemented a change and pending uploads are now completing successfully. CallTower will continue to monitor and test. If you are still experiencing issues, please open a case with CallTower Support. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

CallTower is investigating reports of admins having trouble uploading numbers to Operator Connect through CallTower Connect. CallTower is urgently working the issue. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower Engineers have addressed the circuit bandwidth limitations and continuous monitoring has confirmed no further issues since Monday at 2:30 PM MST CallTower will be closing this master case and all associated cases. Within three business days, an Official Root Cause Analysis (RCA) or a Preliminary RCA will be available and provided to customers upon request.

Calltower continues to see circuit utilization within threshold limits. We will closely monitor traffic until there is a confirmed resolution. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com as soon as new information is available.

Calltower engineers show circuit utilization is still within threshold limits and is continuing to reroute traffic to an alternate path. We continue to closely monitor and will provide additional updates as new information is made available. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 120 minutes, unless identified otherwise.

Calltower engineers have rerouted some traffic to an alternate path to prevent a recurrence of symptoms. We are actively working with our vendor partner to increase capacity and are closely monitoring circuit thresholds. Default messaging: *CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com as soon as new information becomes available, unless identified otherwise.

Calltower engineers are still seeing utilization well below the circuit's threshold. We are continuing to monitor for any signs of maxing while we continue to pursue resolution to prevent a recurrance of issues. Default messaging: *CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com as soon as new information becomes available, unless identified otherwise.

Reduced traffic volume due to the time of day has temporarily resolved call quality issues. CallTower engineers continue to monitor the network for other signs of circuit overutilization and continue to pursue resolution to prevent a recurrance of issues. Default messaging: *CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com as soon as new information becomes available, unless identified otherwise.

Calltower engineers are continuing to work with the circuit provider to have the maximum capacity increased. We have seen a drop in traffic which should alleviate call quality issues. We will continue to monitor while the order to update the MPLS is processed. Default messaging: *CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 2 hours, unless identified otherwise.

Calltower engineers are continuing to work with the circuit provider to have the maximum capacity increased. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes

We have identified a bandwidth issue on one of our MPLS circuits. Our engineers along with our telecom team are working with the circuit provider to have the maximum capacity increased. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes

Calltower has created case 01353056 after multiple reports of call quality degradation. Our engineers have been engaged and we are urgently working to resolve this issue. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

Microsoft is reporting that the issue has been resolved. CallTower is able to validate through testing that the issue is no longer occurring. CallTower will be closing this master case and all associated cases.

CallTower continues to work with Microsoft Operator Connect Support on the issue impacting the upload of Operator Connect numbers through CallTower Connect. This issue does not affect numbers that are already provisioned. We ask that customers experiencing the issue open a case with support@calltower.com. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation.

We are investigating an issue affecting Teams Operator Connect customers attempting to upload numbers in CallTower Connect. CallTower has also opened a case with Operator Connect support. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

Resolved: CallTower's Voice Engineers have implemented a solution to our routing in our NY Sansay location. We have confirmed with customers that the issue of one-way audio and intermittent call failures has been resolved. CallTower will be closing this master case and all associated cases. Within three business days, an Official Root Cause Analysis (RCA) or a Preliminary RCA will be available and provided to customers upon request.

Investigating: CallTower has initiated master case 01343366 after identifying an issue where users are experiencing intermittent call failures and no audio during inbound calls. Our Voice Engineers have been engaged, and we are actively working to resolve this issue urgently. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 60 minutes, unless identified otherwise. This issue is being investigated as a top priority.

The issue with CT Cloud SIP outbound calls ringing fast busy is considered resolved and all associated cases will be closed out. CallTower will be closing this master case and all associated cases. Within three business days, an Official Root Cause Analysis (RCA) or a Preliminary RCA will be available and provided to customers upon request.

CallTower Engineering and Support continue to monitor the issue. CallTower Support continues to not receive any further reports of the issue. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com tomorrow early morning, unless identified otherwise.

CallTower Engineering and Support continue to monitor the issue. CallTower Support continues to not receive any further reports of the issue. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 60 minutes, unless identified otherwise.

CallTower Engineering and Support continue to monitor the issue. CallTower Support has not had any new or further reports of the issue. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 60 minutes, unless identified otherwise.

CallTower Engineering has taken steps to mitigate the issue. Several CallTower customers have confirmed the issue to be resolved. CallTower will continue to monitor the issue. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

CallTower support is investigating multiple reports of CT Cloud SIP customer reporting outbound calls ringing fast busy but has not identified/confirmed there is an issue on our network or with our services. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

Microsoft is now reporting that the issue has been resolved. CallTower has also confirmed the resolution. Microsofts most recent posting is included below. Title: Users may be unable to join Microsoft Teams meetings using Public Switched Telephone Network (PSTN) User impact: Users may have been unable to join Microsoft Teams meetings using PSTN. More info: This issue could have impacted any Microsoft Teams user, regardless of if they were on the new or classic experience, or if they were on the mobile, web, or desktop client. Additional impact scenarios users may have experienced: - Users couldn't hear music while on hold, though the hold still succeeded - If the user left the call while on hold, the call would have dropped - Call Park failed for users - Users couldn't access Echo calls to test audio devices - Users who were dialing out to PSTN numbers from ongoing Teams meetings were impacted - Users connected to meetings using PSTN may have been unable to hear audio prompts or interact with meetings using Dual tone multi frequency (DTMF) Final status: We've reverted the offending configuration change, and confirmed with monitoring telemetry and with some users who initially reported the issue that the impact is remediated. Scope of impact: Any user that attempted to join Microsoft Teams meetings using PSTN may have been impacted. Start time: Wednesday, April 10, 2024 at 12:36 PM MDT End time: Wednesday, April 10, 2024 at 2:38 PM MDT

Microsoft has provided another update which is included below. CallTower has been successful in our recent tests. Title: Users may be unable to join Microsoft Teams meetings using Public Switched Telephone Network (PSTN) User impact: Users may be unable to join Microsoft Teams meetings using PSTN. More info: This issue can impact any Microsoft Teams user, regardless if they're on the new or classic experience, or if they're on the mobile, web, or desktop client. Additional impact scenarios users may experience: - Users can't hear music while being on hold, though the hold still succeeds - If the user leaves the call while being on hold, the call will drop - Call Park fails for users - Users can't access Echo calls to test audio devices - Users who are dialing out to PSTN numbers from ongoing Teams meetings are impacted Current status: We've identified a recent configuration change that contains a code issue and is resulting in various impact scenarios listed in the "More info" section of the communication. We're reverting the offending change and are monitoring internal telemetry to ensure the impact is remediated. Scope of impact: Any user attempting to join Microsoft Teams meetings using PSTN may be impacted. Start time: Wednesday, April 10, 2024 at 12:36 PM MDT Root cause: A recent configuration change contains a code issue and is resulting in various impact scenarios listed in the "More info" section of the communication. Next update by: Wednesday, April 10, 2024 at 4:30 PM MDT

Microsoft has identified an issue affecting calls into conference bridges. This appears to only be affecting our GCC High customers at this time. Provided below is Microsoft's posting regarding this incident. Microsoft Teams TM774378, Last updated: Apr 10, 2024, 2:42 PM MDT Estimated start time: Apr 10, 2024, 2:13 PM MDT All updates Apr 10, 2024, 2:42 PM MDT Title: Some users may be unable to join Public Switched Telephone Network (PSTN) conference calls in Microsoft Teams User impact: Users may be unable to join PSTN conference calls in Microsoft Teams. More info: For additional impact, users may be unable to hear music while being on hold, and users may be unable to use Echo to test audio devices. Current status: We're analyzing a portion of Microsoft Teams infrastructure responsible for PSTN conference calling to help understand the root cause of the issue. Scope of impact: Any user attempting to join a PSTN conference call in Microsoft Teams is impacted. Next update by: Wednesday, April 10, 2024 at 4:00 PM MDT

The brief interruption issue is considered resolved and the associated cases will be closed out. CallTower will be closing this master case and all associated cases. Within three business days, an Official Root Cause Analysis (RCA) or a Preliminary RCA will be available and provided to customers upon request.

CallTower customers may have experienced a brief interruption in services, which are currently up and running. CallTower Engineers are investigating the cause of the interruption. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

Microsoft indicated a network routing change through their infrastructure caused inbound and outbound calls to fail starting at 5:50 AM MDT. They have corrected the issue as of 6:20 AM MDT and are monitoring. Additional details can be found by your Microsoft 365 Admin under Service Health, and TM760143. We will be closing all related cases shortly. If you continue to experience issues, please submit a ticket to support@calltower.com or call 1-800-347-5444.

CallTower has verified that customers can successfully log in by adding "@CC_accountID.com" to their usernames. Consequently, we consider this issue resolved. If customers wish to update their usernames to add their "@domain.com", please contact support@calltower.com to initiate a case for the request. CallTower will be closing this master case and all associated cases. Within three business days, an Official Root Cause Analysis (RCA) or a Preliminary RCA will be available and provided to customers upon request

CallTower has initiated master case 01323257 to address an issue affecting users encountering login errors while accessing Intermedia. The error indicates incorrect username/password. Upon investigation, it was found that Intermedia implemented a new username policy, automatically updating usernames not in "email format" to include "@CC_'accountID.com" to their existing usernames. Passwords remain unchanged. We kindly ask users experiencing login errors to append "@CC_accountID.com" to their existing usernames when logging into Intermedia. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 60 minutes, unless identified otherwise.

Microsoft has made serveral optimizations and mitigation effors and have confirmed that the issues with Microsoft Teams services and features has been resolved. ***CallTower will be closing this master case and all associated cases. If provided by Microsoft an Official Root Cause Analysis (RCA) will be available and provided to customers upon request. Title: Some users may experience multiple issues with their Microsoft Teams User impact: Users may experience multiple issues with their Microsoft Teams. More info: Affected scenarios included, but weren’t limited to the following: - Users logging in or unlocking their devices after some time may have had missing messages. - Users may have been unable to load messages in channels and chats. - Users were unable to view or download their media (images, videos, audio, call recordings, code snippets). - Some users were experiencing delays sending and receiving chat messages. - Anonymous users may have been unable to join meetings. - Teams connectors for Power Automate/Power Apps were experiencing errors. -Call Recordings might take longer to appear in user's OneDrive for Business and SharePoint Online. - Users may have been unable to load previous Copilot history, or new history was not written - Bots may have been unable to download attachments - Sending and receiving read receipt notifications may have been delayed - Users may have experienced issues resuming or rejoining meetings. - Users within organizations leveraging an Information Barrier may have experienced issues joining meetings - Users performing a cold boot may have been unable to log into teams and would have seen an "oops" page Final status: After extended monitoring and various optimizations and mitigation efforts, we’ve confirmed that our Microsoft Teams service and features have been restored or returned to optimal health. Scope of impact: This issue could have potentially impacted any Microsoft Teams user in the scenarios outlined in the More info section. Start time: Friday, January 26, 2024 at 7:55 AM MST End time: Friday, January 26, 2024 at 6:30 PM MST

CallTower continues to monitor the Microsoft issue affecting some of our customers and have seen significant improvements. We are not experiencing any current impairments. Microsoft has provided an update regarding the issue and the affected services. Latest Microsoft Update: Jan 26, 2024, 5:22 PM MST Title: Some users may experience multiple issues with their Microsoft Teams User impact: Users may experience multiple issues with their Microsoft Teams. More info: Affected scenarios include, but aren't limited to the following: Mitigated/improving: - [Updated] Users logging in or unlocking their devices after some time may have missing messages. We believe that this symptom has been addressed. - [Updated] Users may have been unable to load messages in channels and chats. We believe that this symptom has been addressed. - [Updated] Users were unable to view or download their media (images, videos, audio, call recordings, code snippets). We believe that this symptom has been addressed. - [Updated] Some users were experiencing delays sending and receiving chat messages. We believe this symptom has been largely addressed, though some users may still experience brief delays. - [Updated] Anonymous users may be unable to join meetings. We’re seeing improvement in this area but some users may still be affected by this scenario. - [Updated] Teams connectors for Power Automate/Power Apps were experiencing errors. We believe that this symptom has been addressed. - [Updated] Call Recordings might take longer to appear in user's OneDrive for Business and SharePoint Online. This symptom has been addressed. Still affected/undergoing further evaluation: - Users may be unable to load previous Copilot history, or new history is not written - Bots may be unable to download attachments - Sending and receiving read receipt notifications may be delayed - Users may experience issues resuming or rejoining meetings. - Users within organizations leveraging an Information Barrier may experience issues joining meetings - Users performing a cold boot may not be able to log into teams and will see an "oops" page Current status: We’re seeing significant improvements with many of the Teams features affected by this incident as we continue to apply mitigations and optimize traffic. We’re evaluating the remaining impact scenarios and are developing fixes and workstreams to address all lingering impact associated with this event. Please see the “more info” section above for the latest information on each impact scenario. We understand the impact an issue like this can have on your organization, and we appreciate your partnership and patience as we work to remediate this issue. Scope of impact: This issue can potentially impact any Microsoft Teams user in the scenarios outlined in the More info section. Start time: Friday, January 26, 2024 at 7:55 AM MST ***CallTower will provide the next update by Saturday, January 27, 2024 at 10:00 AM MST, unless the issue is resolved by Microsoft.

CallTower continues to monitor the Microsoft issue affecting some of our customers. We have seen major improvements in our testing, and aren’t seeing any major impairment currently. Microsoft has provided an update regarding the issue and the affected services. Latest Microsoft Update: Jan 26, 2024, 3:58 PM MST Title: Some users may experience multiple issues with their Microsoft Teams User impact: Users may experience multiple issues with their Microsoft Teams. More info: Affected scenarios include, but aren't limited to: - Anonymous users may be unable to join calls or meetings - Users within organizations leveraging an Information Barrier may experience issues joining meetings - Users performing a cold boot may not able to log into teams and will see an "oops" page - Users logging in or unlocking their devices after some time may see missing messages - Users may fail to load messages in channels and chats - Users are unable to view or download their media (images, videos, audio, call recordings, code snippets) - Some messages may experience delays being sent - Call Recordings might take longer to appear in user's OneDrive for Business and SharePoint Online - Users may be unable to load previous Copilot history, or new history is not written - Bots may be unable to download attachments - Sending and receiving read receipt notifications may be delayed - Anonymous users may be unable to join meetings - Teams connectors for Power Automate/Power Apps may experiencing errors Current status: We're continuing to apply mitigations across the affected infrastructure and our telemetry is showing additional improvement in the user experience, though many customers are still affected by this issue. We're also working to apply fixes to address individual affected Teams features in parallel while our broader remediation strategy is ongoing. We're evaluating any and all additional workstreams that will allow us to reduce the impact to those customers that are still affected. We understand the impact an issue like this can have on your organization, and we appreciate your partnership and patience as we work to remediate this issue. Scope of impact: This issue can potentially impact any Microsoft Teams user in the scenarios outlined in the More info section. Start time: Friday, January 26, 2024 at 7:55 AM MST . Next update by: Friday, January 26, 2024 at 5:30 PM MST

CallTower continues to monitor the Microsoft issue affecting some of our customers. Microsoft has provided an update regarding the issue and the affected services. Latest Microsoft Update: Jan 26, 2024, 3:02 PM MST Title: Some users may experience multiple issues with their Microsoft Teams User impact: Users may experience multiple issues with their Microsoft Teams. More info: Affected scenarios include, but aren't limited to: - Users performing a cold boot may not able to log into teams and will see an "oops" page - Users logging in or unlocking their devices after some time may see missing messages - Users may fail to load messages in channels and chats - Users are unable to view or download their media (images, videos, audio, call recordings, code snippets) - Some messages may experience delays being sent - Call Recordings might take longer to appear in user's OneDrive for Business and SharePoint Online - Users may be unable to load previous Copilot history, or new history is not written - Bots may be unable to download attachments - Sending and receiving read receipt notifications may be delayed - Anonymous users may be unable to join meetings - Teams connectors for Power Automate/Power Apps may experiencing errors Current status: Our network and backend service optimization efforts are ongoing and we're monitoring internal telemetry to confirm that our efforts are effectively reducing the impact to customers. We're continuing to scale up our services and identify new workstreams intended to remediate this problem more rapidly. Although many customers remain impacted by this issue, we're seeing a reduction in errors and an increase in availability. We understand the impact an issue like this can have on your organization, and we appreciate your partnership and patience as we work to remediate this issue. Scope of impact: This issue can potentially impact any Microsoft Teams user in the scenarios outlined in the More info section. Start time: Friday, January 26, 2024 at 7:55 AM MST . Next update by: Friday, January 26, 2024 at 4:00 PM MST

Microsoft and some of our customers have reported service issues associated with Teams. Microsoft has provided an update regarding the issue and the affected services. Latest Microsoft Update: Jan 26, 2024, 1:02 PM MST Title: Some users may experience multiple issues with their Microsoft Teams User impact: Users may experience multiple issues with their Microsoft Teams. More info: Affected scenarios include, but aren't limited to: - Users performing a cold boot may not able to log into teams and will see an "oops" page - Users logging in or unlocking their devices after some time may see missing messages - Users may fail to load messages in channels and chats - Users are unable to view or download their media (images, videos, audio, call recordings, code snippets) - Some messages may experience delays being sent - Call Recordings might take longer to appear in user's OneDrive for Business and SharePoint Online - Users may be unable to load previous Copilot history, or new history is not written - Bots may be unable to download attachments - Sending and receiving read receipt notifications may be delayed - Anonymous users may be unable to join meetings - Teams connectors for Power Automate/Power Apps may experiencing errors Current status: Our failover operation did not provide the anticipated relief to end users in North and South America regions, and we are now working to optimize traffic patterns as part of the mitigation effort. We're applying configuration changes across the affected network infrastructure to reduce customer impact as quickly as possible. Scope of impact: This issue can potentially impact any Microsoft Teams user in the scenarios outlined in the More info section. Start time: Friday, January 26, 2024 at 7:55 AM MST Next update by: Friday, January 26, 2024 at 2:00 PM MST *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower is investigating reports of numerous issues affecting Microsoft Teams. Microsoft has acknowledged an issue in their status TM710344. We are closely monitoring the issue and will continue to provide updates as we receive them. Most recent Microsoft update: TM710344, Last updated: Jan 26, 2024, 11:16 AM MST Estimated start time: Jan 26, 2024, 8:37 AM MST Affected services Microsoft Teams Title: Some users may experience multiple issues with their Microsoft Teams User impact: Users may experience multiple issues with their Microsoft Teams. More info: Affected scenarios include, but aren't limited to: - Users performing a cold boot may not able to log into teams and will see an "oops" page - Users logging in or unlocking their devices after some time may see missing messages - Users may fail to load messages in channels and chats - Users are unable to view or download their media (images, videos, audio, call recordings, code snippets) - Some messages may experience delays being sent - Call Recordings might take longer to appear in user's OneDrive for Business and SharePoint Online - Users may be unable to load previous Copilot history, or new history is not written - Bots may be unable to download attachments - Sending and receiving read receipt notifications may be delayed - Anonymous users may be unable to join meetings - Teams connectors for Power Automate/Power Apps may experiencing errors Current status: We've completed the failover in the Europe, Middle East, and Africa (EMEA) region and telemetry is showing improvement. We're continuing with the failover processes in the Americas, and are monitoring whilst these processes complete. Scope of impact: This issue can potentially impact any Microsoft Teams user in the scenarios outlined in the More info section. Start time: Friday, January 26, 2024 at 7:55 AM MST Next update by: Friday, January 26, 2024 at 1:00 PM MST

CallTower Engineers have identified and fixed the issue affecting our CT Cloud faxing customers. Our internal testing, as well as confirmation from multiple customers, confirms the issue has been resolved. CallTower will be closing this master case and all associated cases. Within three business days, an Official Root Cause Analysis (RCA) or a Preliminary RCA will be available and provided to customers upon request.

CallTower Engineers continue to urgently investigate the issue causing faxes to fail for our CT Cloud Fax Customers. If you are experiencing faxing issues, please open a ticket with support@calltower.com and provide detailed examples to assist in our investigation. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower is investigating reports of faxes failing for our CT Cloud Fax customers. CallTowers engineers are engaged and urgently working the issue. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower Engineers have been working urgently to restore CallTower’s services. All issues with Auto Attendant and Voicemail functionality have been restored through CommPortal and CallTower Connect. Provisioning of all other services has also been restored in both platforms. We are no longer seeing any issues affecting our CallTower services. We continue to monitor the data center situation and work closely with our Data Center provider, who is working nonstop to resolve the heating issues. They continue to report that temperatures are gradually stabilizing. Latest update from our Data Center provider; There was a recent failure for chillers 2 and 3 due to low suction pressure and extremely cold ambient temperatures. The Equipment has been reset, and the site is recovering. The mechanical vendors arrived on site to assist in troubleshooting and repair. Another mechanical vendor is en route to the IBX. Thirteen portable coolers are now online and two more continue to be installed. For customers who powered down equipment, we strongly recommend waiting to restore operations until the temperatures reach a lower overall range. CallTower will be closing this master case and all associated cases. Within three business days, an Official Root Cause Analysis (RCA) or a Preliminary RCA will be available and provided to customers upon request.

CallTower’s Engineering team remains in close contact with our Data Center provider, who continues to make significant progress, and is still seeing temperatures gradually stabilize. Conditions are still not optimal for bringing the data center back online. We are still handling this issue with the utmost priority and appreciate your continued patience. Latest update from our Data Center provider: The facility continues to decrease temperatures slowly, with the current average temperature at 83F. For customers who powered down equipment, we strongly recommend waiting to restore operations until the temperatures reach a lower overall range. Additionally, the CallTower Engineering team is reporting that Commportal is now operational and Connect provisioning should restore within the hour. CallTower understands the importance of these services for our operations, and we appreciate your patience and understanding while we work urgently to provide a resolution. CallTower has opened a master case to investigate these issues as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com, next update scheduled for 2 hours, unless identified otherwise. This issue is being investigated as top priority.

CallTower’s Engineering team remains in close contact with our Data Center provider, who continues to make significant progress, and is still seeing temperatures gradually stabilize. Current conditions are still not optimal for bringing the data center back online. Rest assured, this matter is being handled with the utmost priority, and our dedicated team is working tirelessly to ensure that all services are up and running smoothly. Latest update from our Data Center provider; The facility temperatures continue to decrease slowly with a current average temperature of 88F degrees. 10 portable coolers are now online and five more are being installed. Customers may see their services returning to operation, but the issue remains in-progress. For customers who powered down equipment, site engineers are still strongly recommending waiting to restore Additionally, the CallTower Engineering team is actively engaged in the restoration process for Commportal and Connect provisioning. CallTower understands the importance of these services for our operations, and we appreciate your patience and understanding while we work urgently to provide a resolution. CallTower has opened a master case to investigate these issues as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltowercom. CallTower intends to post updates on status.calltower.com, next update scheduled for 2 hours, unless identified otherwise. This issue is being investigated as top priority.

CallTower’s Engineering team have remained in close contact with our Data Center provider, have made significant progress, and temperatures are gradually stabilizing. However, the current conditions are still not optimal for bringing the data center back online. Rest assured, this matter is being handled with the utmost priority, and our dedicated team is working tirelessly to ensure that all services are up and running smoothly. Latest update from our Data Center provider; The facility temperatures continue to decrease slowly with a current average temperature of 88F degrees. 10 portable coolers are now online and five more are being installed. Customers may see their services returning to operation, but the issue remains in-progress. For customers who powered down equipment, site engineers are still strongly recommending waiting to restore Additionally, the CallTower Engineering team is actively engaged in the restoration process for Commportal and Connect provisioning. CallTower understands the importance of these services for our operations, and we appreciate your patience and understanding while we work urgently to provide a resolution. CallTower has opened a master case to investigate these issues as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltowercom. CallTower intends to post updates on status.calltower.com, next update scheduled for 2 hours, unless identified otherwise. This issue is being investigated as top priority.

The efforts to address cooling issues in the Chicago datacenter are ongoing. Currently seeing temperatures stabalize, but still too high to bring the datacenter back online. This continues to be handled with the highest priority until all services are up and running. Latest update from our Data Center provider; Temperatures are observably decreasing at the site, with average temperatures at 98F, as chillers and cooling solutions are brought online. Customers may see their services returning to operation, but the issue remains in-progress. For customers who powered down equipment, site engineers are strongly recommending waiting to restore operations until the temperatures reach a lower overall range. We will continue to monitor temperatures at the site, and will provide updates as further information becomes available. CallTower Engineering, currently continuing to work on the restorations of Commportal and Connect provisioning and will push through the night, currently there is no ETA on resolution. CallTower has opened a master case to investigate these issues as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltowercom. CallTower intends to post updates on status.calltower.com, next update scheduled for 6:00 AM ET unless identified otherwise. This issue is being investigated as top priority.

The efforts to address cooling issues in the Chicago datacenter are ongoing. 2 of 6 chiller units are online and temperatures are improving, but still too high to bring the datacenter back online. This continues to be handled with the highest priority until all services are up and running. CallTower’s Engineers have been successful in restoring Auto Attendant and Voicemail service functionality to an alternative datacenter. We are continuing to work on the restoration of Commportal and Connect provisioning. CallTower has opened a master case to investigate these issues as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltowercom. CallTower intends to post updates on status.calltower.com approximately every 2 hours, unless identified otherwise. This issue is being investigated as top priority.

CallTower’s Engineering Team remains in close communication with our Data Center provider to restore services to affected platforms, which are critical for reinstating Auto Attendant and Voicemail functionalities. The following update is from our Data Center partner: Update: No ETR has been provided yet. Temperatures remain elevated at the site. Active cooling is in-place, but we have not seen a noteworthy decrease in temperatures thus far. We continue to monitor and will provide information as it becomes available. Since CallTower’s pre-configured redundancy was unsuccessful, CallTower Engineers have been actively working with Metaswitch engineering to implement failovers. The system is up and reachable on the network, however, is not processing calls. Currently no ETA on resolution, we are monitoring the situation closely and will keep you informed with any developments. We appreciate your patience during this time and apologize for any inconvenience this may have caused. CallTower has opened a master case to investigate these issues as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltowercom. CallTower intends to post updates on status.calltower.com approximately every 2 hours, unless identified otherwise. This issue is being investigated as top priority.

CallTower continues to work with our Data Center partner to restore services. Due to extreme weather conditions, on-site chillers, which are responsible for keeping the Data Center at an operational temperature, have malfunctioned. While working to resolve the issue with the chillers, additional resources have been acquired to assist with bringing in equipment to reduce the temperature in the Data Center. Currently there is not an estimated time to resolution. We continue to monitor the situation closely and will keep you informed with any new updates that we receive. We appreciate your patience during this time and apologize for any inconvenience this may have caused. CallTower has opened a master case to investigate these issues as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltowercom. CallTower intends to post updates on status.calltower.com approximately every hour, unless identified otherwise. This issue is being investigated as top priority.

CallTower's Engineering team remains in close communication with our Data Center partner to restore services to affected platforms, which is critical for reinstating Auto Attendant and Voicemail functionalities. Our partner is actively using ambient air techniques to lower temperatures and address the core issues. At present, we have not received an estimated time of resolution from the Data Center provider. The extreme weather conditions in Chicago were a significant factor in the initial disruption and is still posing challenges to our recovery operations. We are monitoring the situation closely and will keep you informed with any developments. We appreciate your patience during this time and apologize for any inconvenience this may have caused. CallTower has opened a master case to investigate these issues as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltowercom. CallTower intends to post updates on status.calltower.com approximately every hour, unless identified otherwise. This issue is being investigated as top priority.

CallTower continues to work with our Data Center provider on recovering services on the MetaSwitch, to re-enable functionality for AA and VM. Our Data Center provider continues to use ambient air to bring temperatures down in an effort to resolve the issue. Currently there is no ETA from the Data Center provider. The severe weather in Chicago contributed to the initial failure, and it continues to hamper efforts at a resolution. CallTower has opened a master case to investigate these issues as it has been reported by more than one than on CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltowercom. CallTower intends to post updates on status.calltower.com approximately every hour, unless identified otherwise. This issue is being investigated as top priority.

CallTower Engineering continues to work with the Data Center provider on recovering services on the Metaswitch to re-enable functionality for AA and VM. Concurrently, our data center vendor is continuing to work on addressing the cooling issue and has begun using ambient air to try to bring temperatures down. CallTower has opened a master case to investigate these issues as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltowercom. CallTower intends to post updates on status.calltower.com approximately every hour unless identified otherwise. This issue is being investigated as top priority.

CallTower’s Data Center Provider is experiencing an issue which may have an impact on multiple customers services. The below message is the latest update from our Data Center Provider: We are currently experiencing environmental issues at the site and are engaging all resources to investigate and resolve them. We will have remote hands investigate your devices as soon as possible, and will keep you updated There is currently no ETA on resolution of the site issue, but is currently being worked as a top priority with all hands on deck. Customers may experience: Post-dial delay. Voicemail and Auto attendants are currently down, customers may experience, not able to reach or access voicemail services. Auto Attendants could cause service for main lines to drop. Possible CT Cloud soft phones may drop services. Provisioning utilizing Connect is currently unavailable. CallTower has opened a master case to investigate these issues as it has been reported by more then one than on CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltowercom. CallTower intends to post updates on status.calltower.com approximately every hour, unless identified otherwise. This issue is being investigated as top priority.

CallTower Support has worked with CallTower Engineers, and have run successful fax tests after recovering system processes that unexpectedly stopped running. We have had confirmed test results from several customers. CallTower Engineers continue to investigate the root cause. CallTower will be closing this master case and all associated cases. Within three business days, an Official Root Cause Analysis (RCA) or a Preliminary RCA will be available and provided to customers upon request.

CallTower support is investigating multiple reports of CT Cloud Fax failures but has not identified/confirmed there is an issue on our network or with our services. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower Engineers have successfully increased the bandwidth capacity between CallTower and Five9. CallTower continues to see normal utilization with no audio degradation and considers this issue resolved. CallTower will be closing this master case and all associated cases. Within three business days, an Official Root Cause Analysis (RCA) or a preliminary RCA will be available and provided to customers upon request.

CallTower continues to monitor the circuit between CallTower and Five9. We currently see an increase in traffic utilization, hovering under 80% utilization and below critical status. CallTower Engineering continues to work urgently to implement a permanent resolution with no current ETA. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every hour unless identified otherwise.

CallTower continues to monitor the circuit between CallTower and Five9. We have seen an increase in traffic utilization but are below thresholds and have not seen any recurrence of audio issues. CallTower Engineering urgently continues to work with our vender to implement a permanent resolution with no current ETA. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every hour, unless identified otherwise.

CallTower continues to monitor the circuit between CallTower and Five9. We continue to see normal traffic utilization and no further call-quality audio issues. CallTower Engineering continues to work with our vendor to implement a permanent resolution. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every hour unless identified otherwise.

CallTower Engineering continues to engage with our vendor to implement a resolution after hours however, currently, there is no ETA on resolution. CallTower will continue to monitor the circuit between CallTower and Five9. However, traffic has normalized, and we are no longer seeing the issue on current calls. CallTower will continue to monitor the connection throughout the evening. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updated on status.calltower.com, next update at 8:00am ET 11/28th

CallTower continues to urgently investigate the issue affecting audio quality for inbound and outbound calls on Five9. We believe that we have identified an issue and Engineering is engaged on a conference call with our vendor working to implement a resolution. Customers can expect calls to connect as expected, however, static may occur intermittently on some inbound/or outbound calls. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 60 minutes, unless identified otherwise.

CallTower is investigating multiple reports of static audio on inbound and outbound calls with Five9. We have engaged our Engineering team to investigate but have not isolated the issue at this time. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower Customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every hour unless identified otherwise. This issue is being investigated as a top priority.

CallTower Engineers have identified an issue on our connection to Five9 and we are currently working with our vender to quickly resolve. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 60 minutes, unless identified otherwise.

CallTower is investigating multiple reports of static audio on inbound and outbound calls with Five9. We have engaged our Engineering team to investigate but have not isolated the issue at this time. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower Customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every hour, unless identified otherwise. This issue is being investigated as a top priority.

CallTower has identified the issue and applied a fix which is now allowing outbound calls to route normally. CallTower continues to monitor calls and asks that customers report any continued issues to support@calltower.com. CallTower will be closing this master case and all associated cases. Within three business days, an Official Root Cause Analysis (RCA) or a Preliminary RCA will be available and provided to customers upon request.

CallTower continues to urgently work on this issue. At this time we have called each of the reporting customers to schedule a time to implement a workaround. This workaround has been tested and does resolve the issue affecting outbound calling for our GCC High customers. CallTower will continue to work directly with the affected customers and provide our next update at 8:00 AM ET. *CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com.

CallTower continues to work with Microsoft to resolve the issue affecting outbound calls for our GCC High customers. CallTower is reaching out to affected customers to implement a workaround that restores outbound calling functionality. We do not yet have an ETA on resolution. This continues to remain our highest priority.

CallTower is urgently investigating the issue affecting outbound calls for our Microsoft Teams GCC High customers. Our previously mentioned changes did not resolve the issue. We have opened a priority case with Microsoft to assist in the investigation. We do not yet have any eta on the resolution. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 60 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower engineers continue to urgently work this issue. We believe we have identified an issue and are currently testing a potential fix in our internal testing environment. We will roll this fix out to the affected customers once confirmed. We do not yet have an ETA. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 60 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower continues to urgently investigate this issue. We do not yet have an ETA on the resolution. This continues to only affect a subset of our GCC High customers. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower continues to investigate an issue affecting outbound calling for our GCC High customers. Our engineering teams are urgently working the issue. We ask that customers continue to report failed calls to Support@calltower.com *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower is investigating reports of GCC High outbound calls failing. This appears to only be affecting a subset of our customers on GCC High. CallTower has made a change and is asking customers to retest and report any failed outbound calls to support@calltower.com

CallTower is able to confirm the CT Text application is again authenticating. CallTower continues to work with Yakchat to determine the root cause of the issue. If you are still having issues, please reach out to support@calltower.com. CallTower will be closing this master case and all associated cases. Within three business days, an Official Root Cause Analysis (RCA) or a Preliminary RCA will be available and provided to customers upon request.

CallTower continues to work with our vendor Yakchat to investigate the issues affecting the authentication of the CT Text application. We are urgently escalating for resolution. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 60 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower is urgently investigating reports of CT Text not authenticating. We have opened a priority ticket with the vendor Yakchat to also investigate. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

This incident has been resolved.

Microsoft is reporting that the issue has been resolved. Microsoft notification included below. Reach out to CallTower Support (support@calltower.com) if you are still experiencing any issues. "ID: TM679693 Status Service Restored Impacted services Microsoft Teams Details Title: Some users may be unable to opt in or out of call queues in Microsoft Teams User impact: Users may have been unable to opt in or out of call queues in Microsoft Teams. More info: Users may have also been unable to see information about call queues assigned to them. Final status: We've identified that a portion of Microsoft Teams infrastructure responsible for call queues wasn't accepting requests as expected, resulting in impact. To remediate this issue, we've rerouted traffic to healthy infrastructure, and we've verified with affected users that the issue is now resolved. Scope of impact: Some users may have been unable to opt in or out of call queues, or see information about call queues assigned to them in Microsoft Teams. Start time: Thursday, October 5, 2023, at 6:16 PM UTC End time: Friday, October 6, 2023, at 9:00 PM UTC Root cause: A portion of Microsoft Teams infrastructure responsible for call queues wasn't accepting requests as expected, resulting in impact. Next steps: - We're investigating why the portion of Microsoft Teams infrastructure responsible for call queues wasn't accepting traffic as expected to prevent this problem from happening again in the future. This is the final update for the event. " *CallTower will be closing this master case and all associated cases.

CallTower continues to work with Microsoft on the issue affecting call queues on Microsoft Teams. A workaround has been identified and is included below. CallTower has tested this workaround and seen successful resolution of the issue. CallTower will continue to provide updates as we receive them from Microsoft. Microsoft's next update is set for 5pm MTN. Within the Teams Admin center (https://admin.teams.microsoft.com) 1. Navigate to Voice 2. Navigate to "Call Queues" 3. Select the Call Queue you wish to re-enable 4. Navigate to "Agent Selection" 5. Toggle "call agents can opt out of taking calls" to "off" 6. Click Submit and wait for the page to reload 7. Return to Agent Selection and toggle "call agents can opt out of taking calls" back to "on" and submit. 8. The queue will once again be visible from the Teams desktop and mobile client. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. This issue is being investigated as a top priority.

CallTower has received reports from multiple customers having issues with their Microsoft Teams call queues. Microsoft has acknowledged the incident and is working to resolve it. Microsoft has posted service health alert ID: TM679693 which is included below. We will continue to post updates as we receive them. Microsoft Service Health Alert ID: TM679693 "Title: Some users may be unable to opt in or out of call queues in Microsoft Teams User impact: Users may be unable to opt in or out of call queues in Microsoft Teams. More info: Users may also be unable to see information about call queues assigned to them. Current status: We've received reports from some affected users that they're unable to opt in or out of call queues, or see information about which call queues are assigned to them. We're reviewing our telemetry systems to determine if our monitors show any preliminary spikes in errors or availability drops while gathering supplemental investigation details from some reporting users to determine the source of impact. Scope of impact: Some users may be unable to opt in or out of call queues, or see information about call queues assigned to them in Microsoft Teams. Next update by: Friday, October 6, 2023, at 11:00 PM UTC" *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. This issue is being investigated as a top priority.

During a maintenance window last night, Five9 adjusted their configurations in their US data center to resolve the outstanding degradation of their Digital Engagement (Chat/Email) services. Since changes were implemented, CallTower has received positive reports from our customer base that all services are online and operational. CallTower will be closing this master case and all associated cases. Within three business days, an Official Root Cause Analysis (RCA) or a Preliminary RCA will be available and provided to customers upon request. If you are still experiencing any further issues, please contact support by email support@calltower.com or by calling 8003475444.

Five9 has completed its process of mitigating Digital Engagement Services with its US data centers. Five9 has asked all affected users to clear their cache and cookies (All time if possible). Please close and restart all Five9 services and log back in. CallTower is monitoring for any additional reports involving Digital Engagement Services (chat and email) with Five9. If you are still experiencing any issues please reach out to CallTower by emailing support@calltower.com or calling our support line at 8003475444 and we can work with Five9 to resolve. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com and expects the next update at 9:00am MST on 9/26/2023.

The following is an update from Five9: Five9 is currently working on restoring services for digital engagement at the moment (email and chat). Please restart your system to see if you are able to run the system. If you are still experiencing downtime due to the outage, please let us know and we shall request for your services to be migrated to the ATL data center. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 60 minutes unless identified otherwise.

The following is an update from Five9: Five9 is in the process of restarting Digital Engagement services in the US West data center. During this time Digital Engagement (chat and email) services will be unavailable. The current estimated time for restoration is up to one hour. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 60 minutes, unless identified otherwise.

CallTower has escalated with Five9 management in an attempt to help drive a resolution for this issue. Five9 continues to work on mitigating a database issue in their US data centers. Digital Engagement Services has been restored for some customers and Five9 is continuing to restore services for all impacted chat and email customers. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 60 minutes, unless identified otherwise.

The following is an update directly from Five9: Five9 continues to work on mitigating a database issue in their US data centers. Digital Engagement Services has been restored for some customers and we are continuing to restore services for all impacted chat and email customers. The current estimated time to resolution to regain chat and email services is up to 15 minutes. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 60 minutes, unless identified otherwise.

Below is an update directly from Five9: Five9 continues to work on mitigating a database issue in our US data centers that is causing general application slowness with chat and email transactions, user login timeouts, and other symptoms. Digital Engagement services (chat and email) will not be available during this time. The current estimated time to resolution to regain chat and email services is up to one hour CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 60 minutes unless identified otherwise.

CallTower has escalated and continues to work urgently with Five9 on intermittent issues in an effort to come to a resolution. Customers may experience: Slow service on delivering Emails from queues, inability to send/receive chat messages, inability for some users to log into agent portal. However, Inbound and outbound calls are not affected. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 60 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower Support has received reports of slow or degraded service with Five9, Currently CallTower is working urgently with Five9 to come to a resolution. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes unless identified otherwise. This issue is being investigated as a top priority.

CallTower continues to see normal call completion. We have seen no further issues affecting call completion for our Intermedia and Teams customers since 9/11 at 11 am MT. CallTower believes the issue has been resolved but continues to work with Microsoft to identify the root cause. CallTower will be closing this master case and all associated cases.

CallTower continues to see successful calls and has not had any new related reports from our customers. CallTower continues to work with our vendors to identify the issue and ensure its resolution. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com.

CallTower and customers continue to see normal call completion. Engineering continues to work with associated vendors to ensure the underlying issue has been addressed. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com.

CallTower customers have not reported any call drop issue since 11 am MT. Although customers are no longer able to reproduce the issue, CallTower Engineers continue to investigate this issue that is potentially impacting some of our Intermedia and Teams users. If you are still experiencing the issue please report your call examples to support@calltower.com. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 60 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower continues to work with our Vendor to investigate the dropped calls. This continues to remain our highest priority. We do not yet have an ETA on resolution. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower and our vendor continue to investigate dropped calls affecting our Teams and Intermedia customers. Please continue to provide examples of the affected calls to aid in our investigation. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower continues to investigate the issue affecting dropped calls on Intermedia and Teams. We have opened a case with the vendor to assist in our investigation. We don't have an ETA on the resolution yet. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower engineers are urgently investigating the issue involving dropped calls with our Intermedia and Teams customers. If you are experiencing the issue, please reach out to support@calltower.com with call examples. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower is investigating reports of calls dropping for our Intermedia and Teams customers. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower has confirmed that inbound and outbound calls are completing. Should you have any persisting issues, please be sure to report them to our support team at support@calltower.com for further investigation. CallTower will be closing this master case and all associated cases. Within three business days, an Official Root Cause Analysis (RCA) or a Preliminary RCA will be available and provided to customers upon request.

CallTower is currently receiving feedback from customers that the calls are working as expected. We will continue to investigate the root cause of the inbound and outbound call failures with Cisco. CallTower has opened a master case for this issue as it is affecting more than one CallTower customer. This issue may or may not directly affect your services. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

CallTower is urgently investigating issues affecting inbound and outbound call failures for Webex calling PSTN services. We are engaging Cisco for further investigation. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower support is investigating multiple reports of call failures on Webex calling PSTN, but has not identified or confirmed if there is an issue on our network or with our services. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower has continued to monitor the issue and hasn't seen any further signaling issues or customer reports of the issue continuing. CallTower believes this issue has been resolved. CallTower will continue to work with Microsoft to identify the issue and ensure its resolution. CallTower will be closing this master case and all associated cases.

CallTower engineers continue to investigate the issue affecting Intermedia to Microsoft Teams calls. CallTower is no longer seeing calls with the signaling issue as of 10:23 MT and is asking customers to retest. If you are still experiencing the issue, please report your failed call example to support@calltower.com. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower Engineers are urgently investigating the issue affecting Intermedia to Teams calls failing due to the Teams call remaining active after the previous call. We are engaging Microsoft to assist in the investigation. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower is investigating reports of an issue affecting Intermedia contact center calls failing when being sent to a Microsoft Teams user. *CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

The Teams Presence Sync issue has been confirmed resolved with the Intermedia roll back of the recent service update. CallTower Support has confirmed resolution with several affected customers. CallTower will be closing this master case and all associated cases. CallTower Support will work with Intermedia for an Official Root Cause Analysis (RCA). This should be available within 7 business days.

CallTower Support is at a Level 3 escalation with Intermedia and will continue to escalate regarding this presence sync issue with Teams. Intermedia's DEV team continues to investigate affected clients logs. Intermedia has rolled back a recent service update. CallTower Support will directly ask a few customers to test after this roll back by Intermedia. This issue is causing agent calls to not complete. A temporary solution is to disable agent Presence Sync to allow calls to complete. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower Support is at a Level 3 escalation with Intermedia and will continue to escalate regarding this presence sync issue with Teams. Intermedia's DEV team is investigating affected clients logs. This issue is causing agent calls to not complete. A temporary solution is to disable agent Presence Sync to allow calls to complete. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower Support is at a Level 3 escalation with Intermedia and will continue to escalate regarding this presence sync issue with Teams. Intermedia has engaged their DEV team and they continue to investigate. This issue is causing agent calls to not complete. A temporary solution is to disable agent Presence Sync to allow calls to complete. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower Support is at a Level 2 escalation with Intermedia and will continue to escalate regarding this presence sync issue with Teams. Intermedia has engaged their DEV team and they are investigating. This issue is causing agent calls to not complete. A temporary solution is to disable agent Presence Sync to allow calls to complete. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower Support continues to investigate reports of Teams Presence issues with Intermedia. CallTower Support has escalated with Intermedia and their management team. This issue is causing agent calls to not complete. A temporary solution is to disable agent Presence Sync to allow calls to complete. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise. This issue is being investigated as a top priority.

CallTower support has opened a master regarding reports of presence issues between Teams and Intermedia, preventing agents from receiving calls. CallTower has opened a master case to investigate this issue as it has been reported by more than one CallTower customer. This issue may or may not directly affect your services and is currently under investigation. If you are affected, please report the issue to support@calltower.com. CallTower intends to post updates on status.calltower.com approximately every 30 minutes unless identified otherwise. This issue is being investigated as a top priority.