Phone System Version Upgrade FAQs

This article will provide insight asto what to expect for phone systems that receive version upgrades.

Updated at July 27th, 2024

Scheduling and Downtime Expectations

Upgrades are usually scheduled outside of the end customers' normal business hours, which means nights and weekends.  The average length of downtime to be expected should be an hour or so. 

Not Happy with New Interface?

Original system images will only be maintained for 30 days past the upgrade date. This will ensure that in the event of a failure, a reversion to the original version can take place. 

 

Post-Upgrade Checklist

 The following items should be checked after a version upgrade to ensure that they are correctly set in place and operational:

  • All audio greeting files for : 
    • Auto-attendants (IVR)
    • Recordings
    • Voicemails
  • Inbound Call Flows
  • Outbound Call Flows

Expected Change

It is possible that the phone system credentials may change. If the credentials change, those credentials will be found in the bvoip control portal. 

 

Phone Provisioning Expectations

Softphone Applications

Softphones for Windows, Mac, and Mobile Applications for iOS / Android, as well as for the native phone system app should not need to be adjusted or re-provisioned after the software upgrade. 

Hard Phones

Physical phones and adapters should re-register on their own, but their template updates may be available under the new software version. When newer software versions for phones are available, we recommend the re-provisioning of phones.

Have Customized Templates?

If there are needed customizations on your phone templates, a request should be submitted into bvoip support to migrate those changes over for you to the newer template version.