This step is moved from the 5th of June 2016 to the currently displayed date.
We are going to upgrade the Voyced platform to the next stable version.
In order to improve the upgrade procedure and reduce risk, the upgrade process consists of two parts that will be performed in 2 successive off-peak periods.
Service Affected: Step 2 involves
- update the Database (during this period all services will be stopped)
- permanently reboot to the new partition
- apply the new configuration
Impact: Major Impact
Start Date: Saturday, 11th of June 2016, 01:00 AM (GMT+1)
End Date: Saturday, 11th of June 2016, 06:00 AM (GMT+1). We will, however, strive to keep this as short as possible.
Status Report: Service Status
Description:
The main downtime occurs during the Database update as the servers will be rebooted several times.
During the Database update and server reboots, Hosted IPPBX and SIP services will be down.
The downtime for this second part of the upgrade can take up to 4 hours, but SIP servers will be prioritised to minimise downtime on calls.
Since the configuration server will be updated to new release during the 1st stage, the logging features might (temporarily) be affected.
We thank you for your patience and understanding and apologise for the inconvenience that this may cause. If there are any questions or concerns, please contact our technical support team.
Kind Regards
the Voyced Technical team
Update:
The implementation and reboots have all gone well and as expected with as little downtime as possible.
We are now focussing on further implementing the changes in the Web interface, additional services and any issues that we may encounter.
The web interface is expected to be back online later this afternoon.
If you come across any unexpected issues, do let us know by creating a ticket with:
- the description of what you were trying to do
- what you expected to happen
- what actually happened
- and if you can, add a screenshot as well
This will help us pinpoint the possible issue, check it and, if needed, tackle the issue as quickly as possible.
Update 2:
The implementation and reboots have all gone well and the upgrade has been completed.
If you come across any unexpected issues, do let us know by creating a ticket with:
- the description of what you were trying to do
- what you expected to happen
- what actually happened
- and if you can, add a screenshot as well
This will help us pinpoint the possible issue, check it and, if needed, tackle the issue as quickly as possible.
Friday, May 20, 2016
