Call Tower 장애 기록

1. 2026년 7월 15일 오후 4:39 UTCinvestigating

   CallTower는 Name 기능에 의해 Dial의 조사 보고서는 운영자가 고객의 일부에 대해 작동하지 않습니다. 우리는이 문제를 조사하기 위해 Microsoft와 케이스를 열었습니다. *CallTower는 하나의 CallTower 고객에 의해보고 된이 문제를 조사하기 위해 마스터 케이스를 열었습니다. 이 문제는 직접 서비스에 영향을 미치지 않을 수 있으며 현재 조사 중입니다. 영향을 받으면 [email protected]으로 문제를 신고하십시오. CallTower는 state.calltower.com에 대한 업데이트를 게시 할 예정이며, 60 분마다 다르게 식별되지 않습니다. 이 문제는 최고 우선 순위로 조사됩니다.

2. 2026년 7월 15일 오후 5:43 UTCinvestigating

   CallTower 엔지니어는 팀 운영자의 하위 세트에 대한 이름 기능에 의해 Dial에 영향을 미치는 문제를 조사하기 위해 계속. 우리는 Microsoft와 적극적으로 참여하고 가능한 한 빨리 지속적인 원인과 회복 정상적인 서비스를 식별하는 데 도움이되는 문제를 해결하기 위해 노력합니다. *CallTower는 하나의 CallTower 고객에 의해보고 된이 문제를 조사하기 위해 마스터 케이스를 열었습니다. 이 문제는 직접 서비스에 영향을 미치지 않을 수 있으며 현재 조사 중입니다. 영향을 받으면 [email protected]으로 문제를 신고하십시오. CallTower는 state.calltower.com에 대한 업데이트를 게시 할 예정이며, 60 분마다 다르게 식별되지 않습니다. 이 문제는 최고 우선 순위로 조사됩니다.

3. 2026년 7월 15일 오후 7:01 UTCinvestigating

   CallTower 엔지니어는 Microsoft와 협력하여 일부 팀 고객에 영향을 미치는 Name 문제로 Dial을 조사합니다. 이 문제는 활성 검토 하 고 에스컬레이션 노력은 모두 팀 분석 가능한 진단 정보로 진행 됩니다. 우리는 새로운 정보가 유효하게 될 때 추가 업데이트를 공유하고이 조사가 계속되는 동안 당신의 인내에 감사드립니다. *CallTower는 하나의 CallTower 고객에 의해보고 된이 문제를 조사하기 위해 마스터 케이스를 열었습니다. 이 문제는 직접 서비스에 영향을 미치지 않을 수 있으며 현재 조사 중입니다. 영향을 받으면 [email protected]으로 문제를 신고하십시오. CallTower는 state.calltower.com에 대한 업데이트를 게시 할 예정이며, 60 분마다 다르게 식별되지 않습니다. 이 문제는 최고 우선 순위로 조사됩니다.

4. 2026년 7월 16일 오후 6:31 UTCresolved

   Microsoft는 Microsoft Teams 고객에 대한 이름 기능에 의해 Dial에 영향을 미치는 문제에 대한 수정을 구현했다고보고했습니다. 수정의 배포에 따라 CallTower 엔지니어는 여러 고객 참가자의 유효성 검사를 완료했으며 예상대로 서비스가 기능을 확인했습니다. 문제가 발생하면 [email protected]으로 연락하십시오. CallTower는이 마스터 케이스와 관련된 모든 케이스를 닫을 것입니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 9일 오전 9:57 UTCinvestigating

   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 [email protected]. 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.

2. 2026년 7월 9일 오전 10:28 UTCinvestigating

   Microsoft Teams and Zoom customers in EMEA are receiving failures when attempting outbound calls. Calltower's voice network engineers have been engaged and are working diligently to restore services in EMEA. 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 [email protected]. 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.

3. 2026년 7월 9일 오전 11:00 UTCidentified

   CallTower engineers are continuing their efforts to isolate and restore services in EMEA for all affected 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 [email protected]. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise

4. 2026년 7월 9일 오전 11:33 UTCidentified

   CallTower Network Engineers have identified a potential cause of the service disruption and are actively working to implement remediation measures. At this time, our engineers are focused on validating the identified cause and restoring full-service stability as quickly as possible. We are continuing to monitor the environment closely and are treating this issue 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 [email protected]. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise

5. 2026년 7월 9일 오후 12:02 UTCmonitoring

   CallTower engineers have completed remediation efforts and service appears to be restored, based on current monitoring and testing. We ask that affected customers please retest their services and confirm that normal functionality has been restored. If you continue to experience any issues, please contact CallTower Support and provide details of the impact so that our teams can investigate further. 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 [email protected]. CallTower intends to post updates on status.calltower.com as any new information becomes available.

6. 2026년 7월 13일 오후 2:51 UTCresolved

   CallTower considers the issue resolved at this time. We 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.

1. 2026년 4월 29일 오후 5:22 UTCinvestigating

   CallTower Support has received reports of issues impacting some Five9 customers. Users may experience call delays, Audio issues, intermittent slow browser speed, and connection issues to Five9. CallTower support is currently investigating with Five9 engineering to mitigate and resolve these 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 [email protected]. 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.

2. 2026년 4월 29일 오후 6:59 UTCresolved

   CallTower Support has confirmed resolution of the Five9-related issues that were impacting call delays, audio issues, browser speed, and connection issues to Five9. The issue was addressed in coordination with Five9 Engineering, and services are operating normally 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.

1. 2026년 3월 2일 오후 4:52 UTCinvestigating

   CallTower Support is actively investigating multiple reports of inbound and outbound call failures and login issues with CT Cloud Communicator Mobile 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 [email protected]. 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.

2. 2026년 3월 2일 오후 5:25 UTCidentified

   The issues affecting CT Cloud Communicator Mobile have been identified as vendor-related. CallTower engineers are actively working with the vendor to determine and implement a 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 [email protected]. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

3. 2026년 3월 2일 오후 5:56 UTCidentified

   CallTower Engineering remains engaged with the vendor and is providing logs and diagnostic information as part of the ongoing resolution process. 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 [email protected]. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

4. 2026년 3월 2일 오후 6:32 UTCidentified

   CallTower Engineering continues to partner with the vendor on log and diagnostic review. The issue has been isolated to an affected system, and investigation is ongoing. 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 [email protected]. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

5. 2026년 3월 2일 오후 7:37 UTCmonitoring

   Based on vendor guidance, CallTower Engineering completed a configuration change designed to address the CT Cloud Communicator Mobile issue. CallTower Support will continue to monitor the environment to confirm the issue is fully resolved. 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 [email protected]. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

6. 2026년 3월 2일 오후 8:15 UTCresolved

   CallTower Support has received positive confirmation from affected customers, and the CT Cloud Communicator Mobile issue is considered 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.

1. 2026년 2월 20일 오후 7:15 UTCresolved

   Some CallTower customers may have briefly experienced issues with Intermedia Contact Center Voice and login. The issue was identified as an Intermedia service outage and has since been resolved. Update from Intermedia: Intermedia Engineering teams identified the root cause as a Cloudflare service disruption that affected connectivity to certain Intermedia services. The third-party provider has since restored service, and Intermedia has verified that Email, Contact Center, and Voice services are fully operational. If any issues persist, customers are advised to contact Intermedia Support for assistance. 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.

1. 2026년 2월 4일 오후 4:27 UTCinvestigating

   Microsoft has reported issues with opting into Teams call queues. Microsoft has released an official service health alert for this issue (TM1226887), which is included below. Calltower has identified a workaround for the issue by toggling off the option "Call agents can opt out of taking calls" in the Teams Admin Center. Microsoft also reports that using the Teams application on mobile is a valid workaround. Microsoft's Posting (TM1226887) Issue ID: TM1226887 Affected services: Microsoft Teams Status: Service degradation Issue type: Advisory Start time: Feb 4, 2026, 9:10 AM MST User impact Users may be unable to toggle call queues on or off in the Microsoft Teams web or desktop client. More info As a workaround, users may be able to use the Microsoft Teams mobile app to toggle call queues as expected. Scope of impact Some users hosted in the North America region attempting to toggle call queues in the Microsoft Teams web or desktop client may be impacted. Root cause A code change contained within a recent service update is causing request to be sent to an incorrect URL, resulting in impact. Current status Feb 4, 2026, 9:11 AM MST We've identified that a code change contained within a recent service update is causing requests to be sent to an incorrect URL, resulting in impact. We're reverting the offending service update as a potential remediation action, and anticipate this process will complete by our next scheduled communications update. Next update by: Wednesday, February 4, 2026 at 11:00 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 [email protected]. 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.

2. 2026년 2월 4일 오후 5:33 UTCresolved

   Microsoft is now reporting that the issue affecting Teams users ability to toggle call queues has been resolved. Microsoft’s final posting is included below. Issue ID: TM1226887 Affected services: Microsoft Teams Status: Service restored Issue type: Advisory Start time: Feb 4, 2026, 2:30 AM MST End time: Feb 4, 2026, 9:22 AM MST User impact Users may have been unable to toggle call queues on or off in the Microsoft Teams web or desktop client. More info As a workaround, users may have been able to use the Microsoft Teams mobile app to toggle call queues as expected. Additionally, admins may have been unable to make changes to call queues, auto attendants, and holidays within the Microsoft Teams admin center. Scope of impact Some users hosted in the North America region attempting to toggle call queues in the Microsoft Teams web or desktop client may have been impacted. Additionally, admins making changes to call queues, auto attendants, and holidays in the Microsoft Teams admin center may also have been affected. Root cause A code change contained within a recent service update was causing requests to be sent to an incorrect URL, resulting in impact. Next steps - We're reviewing our update procedures to understand why impact to call queues wasn't caught during the testing phase. This will allow us to drive service improvements by proactively identifying similar issues in the future and improve our update testing processes. Current status Feb 4, 2026, 10:08 AM MST We've reverted the offending service update and confirmed through monitoring service health telemetry that the impact has been remediated. This is the final update for the event. * CallTower will be closing this master case and all associated cases.

1. 2026년 1월 2일 오후 4:23 UTCinvestigating

   CallTower engineers have identified and resolved an issue impacting customers using CT Cloud Communicator. The problem was caused by a failed update that did not download correctly, resulting in application failures. To restore service, our engineers have reverted the update and will not reapply it until we have confirmed with the vendor that it can be deployed successfully. This will not affect customers who have manually updated to the newest version of the app; they can continue to use it without issue. A detailed summary of the event is provided below. If you continue to experience any issues, please contact CallTower Support for assistance. Start Time: Around 6:30 AM MST End Time: 8:18 AM MST Resolution Action: The update was rolled back to the previous version.

2. 2026년 1월 2일 오후 4:24 UTCresolved

   This incident has been resolved.

1. 2025년 11월 4일 오후 6:43 UTCinvestigating

   CallTower Support has received multiple reports of failures affecting Toll-Free inbound calls. Our Engineering team is actively 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 [email protected]. 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.

2. 2025년 11월 4일 오후 7:34 UTCmonitoring

   CallTower Engineering has worked with affected vendors to implement a resolution for the Toll-Free inbound call issue. We are currently seeing resolution of the issue and are continuing to monitor to ensure continued stability and performance 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 [email protected]. CallTower intends to post updates on status.calltower.com approximately every 60 minutes, unless identified otherwise.

3. 2025년 11월 4일 오후 8:31 UTCmonitoring

   CallTower Engineering has worked with affected vendors to implement a resolution for the Toll-Free inbound call issue. We are currently seeing continued stability and performance and will continue to monitor. If you experience any persisting issues, please provide the most recent call example and we will continue 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 [email protected]. CallTower intends to post updates on status.calltower.com as soon as any new information is made available.

4. 2025년 11월 5일 오후 2:28 UTCresolved

   CallTower is considering this issue resolved. If you experience any persisting issues, please provide the most recent call example and we will troubleshoot accordingly. 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.

1. 2025년 9월 4일 오후 9:30 UTCidentified

   Identified: CallTower Support has received reports of inbound and outbound call failures with Five9. We are actively working with Five9 to investigate and mitigate the issue. In the meantime, we ask customers experiencing this issue to retest their 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 [email protected]. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

2. 2025년 9월 4일 오후 9:45 UTCresolved

   Resolved: CallTower Support has confirmed with Five9 as well as multiple customers that the issue is now resolved. CallTower will be closing this master case and all associated cases. If you continue to experience any problems, please contact CallTower Support at 800-347-5444 or [email protected]

1. 2025년 8월 15일 오후 6:52 UTCinvestigating

   CallTower Support is investigating multiple reports of issues with the CT Cloud Voice EAS service. This service affects Commportal, Voicemail, Auto Attendants, Call Park, etc. CallTower Support 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 [email protected]. 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.

2. 2025년 8월 15일 오후 7:40 UTCmonitoring

   CallTower Engineering transferred CT Cloud Voice services from CHI to DAL. CallTower Support has confirmed the functionality of CT Cloud Voice services from multiple customers and will continue to monitor. 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 [email protected]. 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.

3. 2025년 8월 15일 오후 8:29 UTCmonitoring

   CallTower Support is actively monitoring the CT Cloud Voice Services issue following the move from CHI to DAL. Meanwhile, CallTower Engineering is working on implementing a permanent fix to fully 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 [email protected]. CallTower intends to post updates on status.calltower.com approximately every 2 hours, unless identified otherwise. This issue is being investigated as a top priority.

4. 2025년 8월 15일 오후 11:08 UTCmonitoring

   CallTower Support is actively monitoring the CT Cloud Voice Service issue. All services have now been restored following the transition from CHI to DAL. Meanwhile, CallTower Engineering is fully engaged in resolving the remaining API issue, which is critical for maintaining connectivity with both Connect and Metaview Web 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 [email protected]. CallTower intends to post updates on status.calltower.com approximately every 4 hours, unless identified otherwise. This issue is being investigated as a top priority.

5. 2025년 8월 16일 오전 3:46 UTCresolved

   CallTower Support has not had any further reports of the issue with CT Cloud Voice Services. CallTower Engineering continues to work through the issue with Connect and Metaview Web Services. However, these do not have a customer service impact. This issue will be considered 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.

1. 2025년 7월 30일 오후 3:33 UTCidentified

   Cisco has announced they are continuing to experience a network event similar to the one they had Yesterday, 730/2025. Cisco Engineering teams are collaborating on potential mitigation actions, including rerouting and optimizing network traffic to resolve the impact. This issue may cause degradation in media quality for some Webex Calling users and Webex Contact Center agents in the US region. Additionally, some provisioning tasks and emergency calls may fail, and certain Cisco Calling Plan services may also experience failures. 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 [email protected]. CallTower intends to post updates on status.calltower.com approximately every 60 minutes, unless identified otherwise.

2. 2025년 7월 30일 오후 6:04 UTCmonitoring

   Cisco's Engineering team has successfully implemented mitigation measures, and all impacted services are now fully operational and stable. CallTower will continue to monitor the situation closely and will share further updates as they become 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 [email protected]. CallTower intends to post updates on status.calltower.com.

3. 2025년 8월 1일 오후 3:26 UTCresolved

   This incident has been resolved.

1. 2025년 7월 29일 오후 4:09 UTCinvestigating

   Cisco has announced they are continuing to experience a network event similar to the one they had Yesterday, 7/29/2025. The issue may cause media quality degradation for some Webex Calling users and Webex Contact Center agents in the US region. Additionally, some provisioning tasks and emergency calls may fail, and some Cisco Calling Plan services may experience failures as well.

2. 2025년 7월 29일 오후 5:16 UTCresolved

   Cisco's Engineering team has completed mitigation efforts and Cisco reports all services are now fully 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.

1. 2025년 7월 28일 오후 5:37 UTCinvestigating

   Cisco has advised they are currently experiencing a global event impacting Webex calling, media quality degradation and provisioning. 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 [email protected]. 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.

2. 2025년 7월 28일 오후 6:04 UTCinvestigating

   We are continuing to investigate this issue.

3. 2025년 7월 28일 오후 6:04 UTCinvestigating

   Cisco has announced a network event that is impacting provisioning and degrading call quality for Webex Calling and Webex Contact Center. Calltower has engaged Cisco Support and is closely monitoring for any new information related to the event. 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 [email protected]. 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.

4. 2025년 7월 28일 오후 6:26 UTCidentified

   Cisco has announced a network event that is impacting provisioning and degrading call quality for Webex Calling and Webex Contact Center. They have also noted that some 911 services may fail and that some Cisco Calling Plan services, and Contact Center Agents may experience failures. Their engineers have been able to identify the issue, but there is no estimated repair time yet. Calltower is engaged with Cisco Support and is closely monitoring for any new information related to the event and will provide updates as they are made available to us. 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 [email protected]. 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.

5. 2025년 7월 28일 오후 6:58 UTCidentified

   Cisco Engineers have identified a network event and are working diligently toward a resolution. The event is impacting multiple services including Webex Calling, Webex Contact Center, Emergency 911 services, and some Calling Plan Services. Symptoms could include quality degradation or in some cases, call failures. The event is isolated to the US region. There has not been an estimated repair time provided yet, but any new informaiton received will be provided once it has been 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 [email protected]. CallTower intends to post updates on status.calltower.com approximately every 60 minutes, unless identified otherwise.

6. 2025년 7월 28일 오후 7:25 UTCresolved

   Cisco Engineering has completed mitigation activities. Services should now be fully operational. Please retest and confirm if there are any persisting issues, and please let us know if further support is needed. CallTower will be closing this master case and all associated cases.

1. 2025년 7월 10일 오후 12:23 UTCinvestigating

   CallTower has identified the issue affecting the completion of some inbound calls in the EMEA region. 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 [email protected]. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

2. 2025년 7월 10일 오후 12:40 UTCinvestigating

   CallTower has isolated the issue to a faulty network device that is causing inbound calls to fail on certain routes. Our network engineers are working diligently to restore service as quickly 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 [email protected]. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

3. 2025년 7월 10일 오후 12:51 UTCmonitoring

   Voice network engineers were able to apply a workaround, and are seeing inbound calls completing at this time. Please retest and advise if you are experiencing any persisting issues. CallTower continues to work on resolving the faulty network device that is impacting inbound calls to the EMEA region. 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 [email protected]. CallTower intends to post updates on status.calltower.com as soon as any new information is available.

4. 2025년 7월 10일 오후 3:34 UTCresolved

   The issue is considered resolved and the associated cases will be closed out. 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.

1. 2025년 5월 19일 오후 7:26 UTCinvestigating

   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 [email protected]. 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.

2. 2025년 5월 19일 오후 7:58 UTCinvestigating

   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 [email protected]. 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.

3. 2025년 5월 19일 오후 8:26 UTCresolved

   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.

1. 2025년 5월 19일 오후 1:41 UTCinvestigating

   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 [email protected]. 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.

2. 2025년 5월 19일 오후 2:36 UTCinvestigating

   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 [email protected]. 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.

3. 2025년 5월 19일 오후 3:37 UTCinvestigating

   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 [email protected]. 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.

4. 2025년 5월 19일 오후 4:43 UTCinvestigating

   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 [email protected]. 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.

5. 2025년 5월 19일 오후 5:32 UTCmonitoring

   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 [email protected]. 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.

6. 2025년 5월 19일 오후 8:25 UTCmonitoring

   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 [email protected]. CallTower intends to post additional updates as they become available. This issue is being investigated as a top priority.

7. 2025년 5월 20일 오후 4:46 UTCresolved

   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.

1. 2025년 5월 1일 오후 3:48 UTCinvestigating

   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 [email protected]. 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.

2. 2025년 5월 1일 오후 4:32 UTCinvestigating

   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 [email protected]. 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.

3. 2025년 5월 1일 오후 5:06 UTCinvestigating

   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 [email protected]. 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.

4. 2025년 5월 1일 오후 8:41 UTCinvestigating

   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 [email protected].

5. 2025년 5월 2일 오후 3:10 UTCresolved

   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.

1. 2025년 3월 24일 오후 5:34 UTCinvestigating

   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 [email protected]. 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.

2. 2025년 3월 24일 오후 6:13 UTCinvestigating

   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 [email protected]. *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 [email protected]. 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.

3. 2025년 3월 24일 오후 6:54 UTCinvestigating

   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 [email protected]. 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.

4. 2025년 3월 24일 오후 7:29 UTCidentified

   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 [email protected]. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

5. 2025년 3월 24일 오후 8:41 UTCidentified

   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 [email protected]. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

6. 2025년 3월 24일 오후 9:38 UTCidentified

   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 [email protected]. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

7. 2025년 3월 24일 오후 11:23 UTCidentified

   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 [email protected]. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

8. 2025년 3월 25일 오전 1:30 UTCidentified

   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 [email protected].

9. 2025년 3월 25일 오후 2:02 UTCidentified

   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 [email protected]. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

10. 2025년 3월 25일 오후 3:22 UTCidentified

    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 [email protected]. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

11. 2025년 3월 25일 오후 4:11 UTCidentified

    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 [email protected]. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

12. 2025년 3월 25일 오후 7:40 UTCidentified

    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 [email protected]. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

13. 2025년 3월 25일 오후 8:41 UTCidentified

    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 [email protected]. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

14. 2025년 3월 25일 오후 10:23 UTCidentified

    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 [email protected]. CallTower intends to post updates on status.calltower.com as they become available.

15. 2025년 3월 26일 오후 3:18 UTCresolved

    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.

1. 2025년 3월 18일 오후 8:40 UTCinvestigating

   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 [email protected]. 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.

2. 2025년 3월 18일 오후 9:07 UTCinvestigating

   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 [email protected]. CallTower intends to post updates on status.calltower.com approximately every 30 minutes, unless identified otherwise.

3. 2025년 3월 18일 오후 9:31 UTCresolved

   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.

1. 2025년 3월 3일 오후 4:58 UTCinvestigating

   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 [email protected]. 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.

2. 2025년 3월 3일 오후 5:24 UTCidentified

   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 [email protected]. This issue is being investigated as a top priority.

3. 2025년 3월 3일 오후 6:30 UTCidentified

   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 [email protected]. This issue is being investigated as a top priority.

4. 2025년 3월 3일 오후 7:43 UTCidentified

   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 [email protected]. This issue is being investigated as a top priority.

5. 2025년 3월 3일 오후 8:46 UTCmonitoring

   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 [email protected].

6. 2025년 3월 3일 오후 10:29 UTCresolved

   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.