Core Platform Release Plans
Preparing for the Next Core Platform Release
Since August 1st, our development teams have been working around the clock to prepare for the next core communications platform version release. Our analogy is this something similar to a Windows 10 to a Windows 11 upgrade/migration.
As part of this, an actual account-by-account migration will need to take place in between today December 5th, 2024 and March 1, 2025. Our goal as part of this project to is make sure all work would be done outside of normal peak business hours for all partners and their downstream customers, likely nights and weekends.
We worked to make this process as automated and seamless as possible to include the ability to maintain desktop and mobile apps, physical device provisioning, and call flow. Meaning, little to no work would need to be done by our existing partners as part of this process.
There are some things that surely will change after the fact in some areas like system configuration and call flow. We are preparing a guide on the changes that you need to know post migration.
We understand that a lot of work needs to be done in a short period of time, and we will be doing our best to proactively post maintenance windows ahead of time and notify accounts on when they will be scheduled for migration.
Stay tuned here or on our Blog for more details.
You may have missed these:
If you're not reading our announcement posts unless the banner appears, you may have missed the following news posts:
- GlassHive Marketing, New Number Request Improvements, QoL Changes
- Reports-Only 1stream Permissions and Simpler Order Forms
- Pricing Calculator, Priority Routing Updates, QoL Changes
- Admin/Non-SSO User Import, Title Based Routing, CA Calling Plans
Progressive Web App Deployment for Windows
We've got a new script available under the Partners > Resources > Automation and APIs section which enables you to quickly deploy the soft phone as a Progressive Web App to your end users using the Windows operating system and a Chromium-based browser such as Edge or Chrome.
Simply follow our knowledgebase article Deploy the Progressive Web App (PWA) using the script shown below, and you'll have the app deployed to your team in no time.
FFotW: Alternative Routing for Outage Scenarios
Forgotten Feature of the Week
Whether or not you're using High Availability for your systems, you should always have a backup phone number configured for every number you own. This way in the event of a phone system outage or general trunk registration issue, you're able to still receive calls to an alternate destination like a backup cell number.
For our US-based SIPTrunk.com partners, this can be configured within your SIPTrunk.com portal to allow for either a backup phone number OR a voicemail to email mailbox which will only be presented when the call cannot get through to your system.
You can find more details on this in our knowledgebase article Adding Alternative Routing to SIPTrunk.com Trunks.
For our partners who purchase calling plans through bvoip, simply submit a new support ticket to us within the support portal using the category shown below.
If you are using an external/third party trunking partner, refer to their documentation on how to best configure this.