On Sunday night we will upgrade the server handling VoIP presence information. There will be no visible functionality change - only bug fixes. No calls or registrations will be affected during the change, but phone statuses will not update for a couple of minutes during the upgrade.

Update (Friday, 12:50): Due to a number of problems with the presence server today, we have performed this maintenance earlier than planned and it is now complete.  We will continue to monitor the presence server today.

This change will have no effect on the majority of users, but it may affect a small number of users who have any automated call systems.  Note that response codes on PSTN call failures will not change, so if you have automated call system which call PSTN numbers, this change will not affect you.

This change will not cause any downtime, since we are changing the way our call routing is generated, and no systems need to be taken down.  Due to the way the routing is generated, it will not affect all customers immediately, but will be rolled out over the coming weeks.

At midnight on Sunday night/Monday morning we are performing some updates on our single/multi-user VoIP platform.  We anticipate approximately 10 minutes of downtime.  During this period, users will be unable to make or receive VoIP calls, and extensions may fail to register.  Any calls in progress when the maintenance start will not be dropped.

The following VoIP services will not be affected by this maintenance:

• All trunks (SIP and IAX, inbound and outbound)
• Remote Call Forwarding
• Fax-to-Email
• Diverts on single/multi-user VoIP extension (extensions will not receive calls, but diverts will still function) - provided the divert is configured through our control panel
• Hosted Unified Comms

Please accept our apologies for any inconvenience this may cause, and if you have any questions, please contact our support team.

Update (00:48): This maintenance work has now completed, with full service restored at 00:40.

We apologise for any problems this may be causing you

***Update 12:30***

Our system admin team have fully restored service and all of our NAT proxies are fully functioning. We again apologise for any problems this has caused.

We apologise for any problems this might cause you, but would like to assure all users that any downtime will be kept to a minimum and in most cases wont even be noticed due to our clustered server setup.

Users of other hosted VoIP products including Centrex/multi user/SIP/IAX trunks will be unaffected.

***Update 22:50***

We have finished the maintenance ahead of schedule and our hosted unified comms platform is now running in full high availability. We apologise if anyone experienced a dropped call due to this.

On the evening of Tuesday 9th February we are performing some maintenance on our VoIP NAT proxy cluster to improve its resilience to hardware and software failures.

We do not expect there to be any significant downtime during this work, however if you do experience problems making or receiving calls, we recommend you reboot your phone in the first instance.

We apologize for any inconvenience this work may cause you.

Update (Wednesday, 10:23): This maintenance was completed last night with minimal downtime, and the NAT proxy is functioning normally today.

We apologise for any problems caused by this

***Update 13:55***

The Unified Comms platform is now running at 100% We apologise again for any problems caused.

Users of our hosted VoIP platform, and SIP/IAX trunk users will be unaffected by this maintenance.

***Update 22:00***

We are about to start the planned maintenance on schedule. The Unified Comms platform is now offline

***Update 22:12***

We have finished the maintenance a little early. Our Unified Comms platform is now back up and running in full High Availability mode.

We apologise for any inconvenience caused by this maintenance.

SIP and centrex users are unaffected by this.

We apologise for any problems this is causing

***Update 14:00***

We have removed one of the IAX machines from the cluster and rebooted. We have now put this machine back into the cluster and tested. It is now handling calls as expected. We have opened an internal issue for both our VoIP development and sysadmin teams to investigate the cause so we may better protect against problems like this in future.

We apologise again for any problems this has caused you

Update 05:51 : This problem was first detected by our monitoring systems just after 4AM.  We have confirmed that this is likely to cause VoIP registration issues for some customers.  Our network engineers are working with our transit providers to restore connectivity.  We are not able to provide an ETA for restoration of our link with Sovereign House at the moment.  We apologise for any inconvenience this will be causing customers are are are working to ensure the link is restored by UK business hours.

Update: 06:14: We have opened an internal issue - 3108 for linking customer incidents where problems are proven to be related to this fault.  Typical problems involve not being able to send or receive email, and phones not registering.  You are still able to reach our web-site at www.gradwell.com

Update 06:50 - This issue appears to be resolved, however, we are awaiting an update from our network team to confirm the status of the resolution.

Update: This issue was resolved just before 07:00 and was related to one of our transit providers’ routers due to overnight maintenance.  If you are experiencing any issues with phones this morning, please try to reboot them, many phones will not continually retry if there is a network issue.  If problems persist, please contact our support team, who will be happy to advise.