Whenever we deal with a product for the first time, we can’t help exploring it. And, in most cases, we jump to it without any technical guidance. Because we’re curious by nature and, oh well, just because we think we know better. 😉 This usually works when we talk about simple products. But things change when dealing with complex software such as VoipNow SPE; it has an extensive feature set and covers so many usage scenarios. Of course, eventually everyone will find their way through, but it’s a lot easier and more straightforward if you use the resources that we have created.
Posts in Category: products
Back in August 2012, when we rolled out the 4PSA Community, we knew this project implied a great deal of responsibility.
Our community brings together people who team up on answers, solutions, and ideas about the products and services they use. Every community member is invited to have his/her say on our products, describing issues they have encountered as accurately as possible, offering guidance, sharing experience and know-how with their peers, tempering conflicts and promoting a collaborative attitude.
From the dust of old centuries until today’s computer-driven and smartphone-glued society, seven has always been considered a magical number. Many believe in the power of seven, be they sorcerers or mathematicians, historians or, in the past decades, even psychologists. Seven days in the week, seven wonders of the world, seven primary colors, seven notes in the musical scale, seven ages of man, Miller’s law on human brain’s capacity of processing information, and the list can go on and on.
Ever since our release of the world’s first UC software in 2006, all service providers have been asking for a way to turn communication into a more personal experience. After 2 years of intense development, we are finally ready to make the big announcement.
The entire 4PSA team proudly announces the release of TouchMeNow, a revolutionary solution that bundles software and hardware to deliver a previously unimaginable communication experience. Making use of haptic technology, TouchMeNow incorporates an unexpected, but highly desired element to Unified Communications: touch.
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.
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.
Never Enough
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.
