VoipNow 3 GA is finally here! In fact, even more than this, the first maintenance release is available, as we had a private release for customers. More information in the Release Notes.
While many of you already had some experience with the new VoipNow SPE, I want to share some interesting things about it.
VoipNow 3 passes another important milestone. Yesterday, the Release Candidate version was made public, which means that the GA version is going to be launched soon.
VoipNow 3 is almost feature-complete. We say “almost” because the final “twist” will be a surprise to our users, and will be wrapped up in the final release.
A couple of hours ago we published the repository for VoipNow 3 Service Provider Edition Beta. It has been a long journey – more than 18 months since the first line of code was written, tens of private Scrum iterations and thousands of issues fixed in JIRA.
Another interesting feature in VoipNow 3 is related to storage.
The industry has known many changes over the past years, but storage has remained a hot topic to the majority of Service Providers who consider scaling (read growing) their businesses.
Irrespective of how much storage space was available, sooner or later one would find herself / himself going out of space. This can apply to a personal computer, but also to the service provider’s environment when dealing with customer information.
We live in the era of apps. We have apps everywhere. Easy to use and performing very specific tasks, apps are the way to go. And with VoipNow 3, we introduce the support for apps.
An interesting new feature in VoipNow 3 is called extension virtualization. As it might prove useful in many cases, let’s review it. This feature is going to be available in all editions of VoipNow 3.
The basic idea is that we want to separate the phone (device) from the functionality stack, which is setup by the user (features offered by VoipNow).
We continue our series of VoipNow 3 articles with another important improvement introduced by VoipNow 3 – account level reorganization.
This reorganization will affect any software integration you might have with VoipNow. Although we tried to preserve compatibility, it was not totally possible, therefore you have to modify your SystemAPI calls to match the new concepts.
In the past week, we reached an important milestone – less than 100 bugs opened for the VoipNow 3 release. I know, it might sound a lot, but judging on the release size, they are a just few.
As the release could not take much longer, we are opening a series of short blog articles that describe the most important technical changes in VoipNow 3. We will focus on the changes that can affect you in a way or another.
Let’s start with the APIs. Many deployments use the APIs for provisioning operations (SystemAPI) or for controlling calls (CallAPI).
Interaction with students made me understand that computer science graduates need some guidance. Every teenager knows that an architect designs structures, a doctor heals people, and a professor teaches students. These jobs are easy to understand. Still, it’s not so obvious what a computer science graduate does. Sadly, many students remain pretty much confused about their mission, even after graduation.
I watch TV only when I have to, and most times I switch to Discovery or National Geographic. In the past weeks I’ve switched on the TV when they were running some programs about Maya civilization. There are plenty of interesting things to say about Maya, but instead all these programs were focused on the Maya calendar and the end of world.
The problem seems to be that all Maya calendars discovered end in 2012… And guess what, we are close to the end of 2012.
