Upgrades differ in complexity and in manipulations doe.
Accordingly differs a duration of downtime.
Possible cases:
This is upgrade during which only Smartswitch version is upgraded, and possibly several packages are updated too.
For example, when moving from version 6.5 to version 6.6.
A sequence of manipulations done:
This is upgrade, in which OS version and all packages is upgraded.
For example, moving from version 6.6 to version 7.10.
A sequence of manipulations done:
For duration of each step and possible side effects see table below.
manipulation | duration | VoIP services working | side effects |
FreeBSD kernel upgrade | during system reboot - up to 10 minutes | no | Possible issues with launching new kernel, after which we'll need someone on the data-center to assist us or IP-KVM attached |
FreeBSD applications upgrade | during system reboot - up to 10 minutes | no | Possible issues with launching new kernel, after which we'll need someone on the data-center to assist us or IP-KVM attached |
delete all old packages | up to 10 minutes | no | |
install all new packages | up to 10 minutes | no | |
delete old Smartswitch package | up to 1 minute | no | |
install new Smartswitch package | up to 1 minute | no | |
upgrade several packages | up to 5 minutes | no | |
config database upgrade | up to 5 minutes when difference between version is 1 (for example, upgrade from 6.4 to 6.5) | no | |
CDR database upgrade | Duration depends on database size and on difference between versions - from several minutes to several days. | yes | This procedure doesn't affect configuring and using the system, however blocks CDR storing. Therefore, report generation doesn't work. All CDRs are accumulated in temporary database and will be handled automatically when procedure finishes. Balances are updated too. |