Following on from a known bug in Asterisks whereby a PBX sends an occasional “unauthorized registration” message to our softswitch following on from a SIP OPTIONS request resulting in an account ban if received more than 3 times during the life of the registration.
We have made some changes to our core softswitch to eliminate this problem. These changes require a reload of the active configuration files on the server and will drop any active call. This reload should take no more than 30 seconds.
We apologise for any inconvenience this may cause.
UPDATE01 – 21:01
This work is complete.
We are aware of an issue with inbound calls via one of our carriers. Engineers are working to urgently restore service.
Service was restored however has been lost again. Outbound calls are routing over alternative carriers. Our senior engineer is currently dealing directly with the carrier.
Service has been restored; An RFO will be issued shortly. We apologise for any inconvenience caused.
This issue has reoccured, the root of the problem has been identified and we are building an RFO that will be published shortly.
Major Incident Report – EasyIPT Outage 21-07-14
We have been advised by our wholesale partner ENTANET that where is BT’s network problem preventing some DSL users connecting. The issue spans multiple nodes and is not geographically restrained to one area. They are investigating this as a matter of urgency and further updates will be provided when they become available.
This has been confirmed as resolved by wholesale.
We have been advised by Zen that they have a maintenance window between 22:00 and 05:00 on the 18th/19th of July for “Essential Software upgrades”
Expected impact duration: 2 x 30min outages within a 7hr window.
During this time we may lose our peering to Zen.
We will be conducting a controlled failover test to our backup aggregation server following today’s failure to ensure this transfer process is working correctly. A few small outages will be seen during this window for bonded customers.
UPDATE01 – 20:54
Testing has completed and the service failed over as expected on 3 simulated failures
We are aware of an outage that has just taken place on our bonded platform and we are working to find the root cause.
UPDATE01 – 16:12
We have been able to restore service and are reviewing the logs with out software vendor. Once we know the cause of the outage an RFO will be published.