Most programmers think they know what this means. I’ve heard it many times because I often ask developers on job interviews to tell me what they prefer.
Might sound like a trivial question, but it is quite relevant. Programming languages are just tools and we want to know whether our possible future colleague is able to understand how things work.
Until recently, 4PSA has had a pretty standard organization, with function-based departments – Sales and Marketing, Software Development (with many teams), Technical Support, Administration, Human Resources etc. This worked decently for many years and that is why I still recommend it as the default organization for any company really focused on a single product.
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.
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).
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.
This informal article covers the very immediate future of VoipNow. While the picture is not complete now, we will update closer to the release date with more information. This article is organized as a FAQ.
We do not publish roadmaps because each major release of VoipNow is a generation change. Generation changes come with strategic improvements that involve a lot of IP. Revealing such IP far before executing it might affect our business, therefore we prefer to keep it undisclosed.
