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).
Not so long ago, we celebrated 5 years of VoipNow. We appreciate the feedback we received from our customers and partners, whether it was by email, phone or on social networks. We do build Unified Communications solutions after all, so we greatly value having such diverse means of communication. However, in some cases, it’s important to provide a central, accessible resource where all documentation and feedback can be gathered.
Today VoipNow is celebrating 5 years of existence. On May 30 2006, 4PSA was the first company in the world to introduce a communication platform that enabled service providers to offer affordable VoIP services, a state-of-the-art substitute for traditional PBX boxes.
Along with Internet development, some of the traditional actions have been implemented into the virtual space. Nowadays, we do not use paper and pen to send a letter, we email messages; we do not socialize only face to face, we also use Facebook, Twitter or Hi5. We have now access to an extremely fast method of sharing information. For all these technologies we have unique accounts that enable others to recognize our identity. Many accounts mean a lot of user names and passwords that we need to remember in our every day virtual world.
It’s that time of the year again. Everybody is trying to finish the projects started along the year or at least bring them close to the end. Meetings, forecasting, budgeting, strategy revision and of course planing. Some people want to try new things, to get new ideas that will eventually improve their business revenue. Others simply want to cut costs and improve efficiency inside their companies.
SIP presence is a tricky subject, mainly because there are some different ways to achieve the same thing. VoIP users are interested to know if “something” has happened in their network. They don’t care how this is technically done, or how many RFCs describe a simple scenario. The truth is that there are indeed many RFCs that handle various aspects:
Every now and then I hear questions on how to secure servers and especially how to secure voice traffic. We hear lots of myths from our customers :).
Most people feel more secure if they have a simple firewall installed.
While firewalls are good, having a firewall to protect closed ports usually doesn’t help. I mean for VoipNow you will probably leave opened all ports for VoIP services and close most of the others. My question is: what is the point of doing this at server level, if the ports are closed anyway? This makes sense on a consumer desktop, but on a server it usually does not help much.
I’ve been answering to sales inquires for many years. Most of the questions are of course related either to Unified Communications or to the hosting world and sometimes they can be very funny. For example, a couple of days ago, someone asked me why we’ve chosen orange as our brand color.
The changelist for the next major version of VoipNow Professional 2.5 will be announced on 23 June 2010 in the VoipNow group. You can join the group now