CallTower, working with a vendor, has identified the a software bug as the root-cause to the issue. CallTower will continue to work with the hardware vendor to review the bug and implement a permanent resolution. The vendor provided a workaround to restore services that was implemented yesterday afternoon. Reporting customers have responded that services have normalized.
CallTower will work with the vendor to implement a software patch and implement during an appropriate maintenance window.
Jun 24, 09:23 MDT
CallTower continues to research the root-cause of the issue earlier today. Customers who have reported the issue to CallTower Support are confirming the issue is no longer impacting connectivity.
CallTower engineers will continue to monitor and escalate the issue with the associated vendors to ensure full resolution of the issue. An additional update will be provided by Monday, June 24 at 9:00 AM MT.
Jun 23, 20:35 MDT
CallTower engineering has taken some preliminary steps to alleviate impact Please retest and report any additional issues back to CallTower Support.
CallTower engineering has escalated with vendors to review and identify next steps. This issue will remain open as we continue the investigation to ensure full resolution. The next update will be provided as additional information becomes available or by 8:00 PM MT.
Jun 23, 16:56 MDT
CallTower support is continuing to investigate an issue with CT SIP customers who are utilizing their own 3CX PBX. It appears that the error is being caused by an update to the 3CX software customers may have loaded to their 3CX instance on 6/21. At this time CallTower engineering is suggesting customers who are experiencing this issue disable auto updates if configured, and roll back any updates to their 3CX PBX made during the last week.
Jun 23, 16:06 MDT
A limited number of CT SIP customers are reporting a 503 error. The issue appears to be isolated to customer on a 3CX platform. CallTower engineering is investigating this issue and will provide further information as it becomes available.
If you believe you are being affected by this error, please contact firstname.lastname@example.org
Jun 23, 15:27 MDT