CallTower Status
All Systems Operational

About This Site

Welcome to CallTower's home for real-time system status updates. Here you will find a current and historical data on system performance.

Cisco Unified Communications Operational
Cisco Voice Operational
Cisco Jabber ? Operational
VoiceCube Operational
Attendant Console Operational
Skype for Business Operational
Skype for Business - Voice ? Operational
Instant Messenger and Presence Operational
Attendant Console Operational
CT Cloud Operational
CT Cloud SIP ? Operational
CT Cloud Voice ? Operational
Attendant Console Operational
CT Cloud Fax Operational
Contact Center Operational
Clarity Connect Operational
Five9 Operational
Telax Operational
Microsoft O365/Teams Operational
Microsoft Teams - Direct Routing Operational
Conferencing Operational
CT Cloud Meeting Operational
Adobe Connect Operational
iMeet Operational
ON Demand Audio Conferencing Operational
CallTower Connect Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Apr 19, 2019
Completed - The scheduled maintenance has been completed.
Apr 19, 23:00 MDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 19, 22:00 MDT
Update - We will be undergoing scheduled maintenance during this time.
Apr 17, 18:09 MDT
Update - We will be undergoing scheduled maintenance during this time.
Apr 17, 18:06 MDT
Scheduled - Purpose: Patching and preventative maintenance on multiple systems.
Systems Affected:

Yealink:
-4/12/2019 Yealink: Firmware Rollback 66.9.0.66
***Possible Impact: Yealink – Phones will reboot Friday evening after the rollback.
Apr 17, 16:08 MDT
Apr 18, 2019

No incidents reported.

Apr 17, 2019

No incidents reported.

Apr 16, 2019

No incidents reported.

Apr 15, 2019

No incidents reported.

Apr 14, 2019

No incidents reported.

Apr 13, 2019
Completed - The scheduled maintenance has been completed.
Apr 13, 04:00 MDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 12, 22:00 MDT
Scheduled - Purpose: Patching and preventative maintenance on multiple systems.
Systems Affected:

Infrastructure:
-4/12/2019 Infrastructure: Production Data Center - Cat5 Cable Changes/Cleanup
***Possible Impact: Skype - Customers using Skype may experience a brief Connectivity Issues of Connecting & Disconnecting of their client's during the changes.


Cardinal:
-4/12/2019 Decommissioning of Cardinal
***Possible Impact: Cardinal Customers: - Customers may experience interruption of service during the transition process from 4/12/19 at 9:00 pm MST 4/13/19 at 3:00 am MST.
If you have a SIP trunk and make calls using the Caller ID of numbers that are NOT on your SIP trunk, these calls will fail after this maintenance. Customers should contact cardinalmigrations@calltower.com to migrate prior to 4/11 if this is a concern for you.
If, after 3:00 am MST on 4/13/19, you still have issues with your service, please contact our support team at support@calltower.com or 800-347-5444.


CT Cloud Fax:
-4/12/2019 Biscom - update licenses and fax server app
***Possible Impact: CT Cloud Fax: Fax services will be unavailable for customers briefly during maintenance window while fax services are restarted.


MasterFax:
-4/12/2019 MasterFax Server - Updates and general maintenance
***Possible Impact: MasterFax: Fax services will be unavailable briefly for customers during maintenance window while fax services are restarted.


Clarity:
-4/12/2019 Clarity: Apply Clarity 4.1.12.23 Hotfix to all 4.1.12 instances
***Possible Impact: Clarity Connect - Clarity dashboard and Admin console will be periodically unavailable during the maintenance window.

-4/12/2019 Clarity: Create L00DAGCC (SQL Distributed Availability Group - L00SLCAGCC & L00STLAGCC) and test fail-over
***Possible Impact: Clarity Connect - Clarity Connect services will be unavailable during changes.


Skype:
-4/12/2019 Skype/Yealink: Yealink Firmware Update 66.9.0.72
***Possible Impact: Skype - Customers Yealink T4x Series Phones will reboot after maintenance window updates. Customers already logged into the phones should stay logged in after the update.


Cisco/Jabber:
-4/12/2019 Cisco/CUPS - Reboot CUPs on Clusters 0, 1, 2, 3, 4, 7, and 10
***Possible Impact: Cisco/Jabber - Customers will experience a brief loss in connectivity with their Jabber Client/Services.

-4/12/2019 Cisco - Upgrade last 4 Jabber SLC Expressway Servers to X8.11.4
***Possible Impact: Cisco/Edge Phones - Customers will experience a brief loss in connectivity with their Jabber Clients and/or Edge Phones.
Users will likely need to log their phone back in after the Maintenance Window.

-4/12/2019 Cisco/Jabber - Update Imagicle in SLC to latest release
***Possible Impact: Cisco/Jabber - Customers will experience a brief loss in connectivity with their Jabber Client/Services.

-4/12/2019 Cisco - DC3-VoiceASA Reboot
***Possible Impact: Cisco - DC3 Voice - Customer will experience a loss in voice services for approximately 5 to 10 minutes while VPNs are rebooted.

-4/12/2019 Cisco - DST failover in SLC
***Possible Impact: Cisco CallManager - SLC customers could have a brief outage while testing the failover. This will not affect legacy/Appia Users.


CallTower Connect:
-4/12/2019 CallTower Connect - Test AGPROV failover to STL
***Possible Impact: Connect will be unavailable during maintenance window.
Apr 10, 11:42 MDT
Apr 11, 2019

No incidents reported.

Apr 10, 2019

No incidents reported.

Apr 9, 2019
Resolved - CallTower is seeing services normalize across the accounts affected by this incident. Five9 has reported:

“Our Engineers have resolved the issue as of 5:48PM, if you are still experiencing technical difficulties please contact Support. An official Root Cause Analysis will be provided upon completion of investigation.”

CallTower will be validating the restoration of services with those who have reported the issue. Please report any ongoing issues to support@calltower.com.
Apr 9, 19:13 MDT
Update - Five9 has provided the following additional updates:

· 04/09/2019 17:00 PM Five9 engineering team are continuously working towards service restoration.

· 04/09/2019 16:28 PM Five9 engineering team are continuously working towards service restoration.

Five9 has not provided an ETTR to CallTower. We continue to push Five9 for additional information regarding the incident, the impact to agents and the status of resolution efforts.
Apr 9, 18:25 MDT
Identified - Five9 has acknowledged an issue in their Santa Clara data center that is affecting agents and call routing. Five9 has sent the following updates:

· 04/09/2019 16:28 PM Five9 engineering team are continuously working towards service restoration.

· 04/09/2019 16:12 PM Five9 engineering team are continuously working towards service restoration.

· 04/09/2019 15:58 PM Five9 engineering team are continuously working towards service restoration.

· 04/09/2019 15:43 PM We have determined the source of the problem and working towards a resolution. All GR-enabled domains have now been moved to their alternate hosts.

· 04/09/2019 15:33 PM Our Engineers are continuing to investigate and working towards service restoration. Geo-redundancy process for all enabled domains in progress.

· 04/09/2019 15:18 PM Our Engineers are continuing to investigate and working towards service restoration. Domains that are geo-redundant are being moved to their respective alternate hosts.

· 04/09/2019 15:03 PM Engineering team is continuously working on moving all GR enabled domains to their alternate host. Our Engineers are continuing to investigate and working towards service restoration.

· 04/09/2019 14:47 PM We have identified an issue on the system and is impacting the Santa Clara Data Center. Our Engineers are diligently investigating and working on resolving the issue. All domains with Geo-Redundancy will be moved to their respective alternate hosts

CallTower is escalating the issue with Five9 as they work toward resolution. We will continue to post updates as they become available from Five9. Please report any issues to support@calltower.com.
Apr 9, 17:39 MDT
Apr 8, 2019

No incidents reported.

Apr 7, 2019

No incidents reported.

Apr 6, 2019

No incidents reported.

Apr 5, 2019

No incidents reported.