In this section you will find the changelogs for the latest VoipNow Platform 2.5 releases.
On this page:
Requirements
For details with regard to the minimum hardware requirements and compatibilities, please consult the Hardware Compatibility List (HCL).
Installation
The VoipNow Platform includes VoipNow Professional and VoipNow Automation. The installation can be performed:
- Using the Command line installation script (check the Command Line Installer section for more details);
- Using the ISO Image (check the ISO Image Installation section for more details);
- Using a Virtuozzo server (check the Virtuozzo Templates Installation for more details);
- Using a VMware Server, VMware Workstation or VMware Player. Also on VMware ESX, deployed with VMware Converter (check the VMware Image Installation section for more details).
You can also install VoipNow in the public cloud:
- On Amazon cloud. The installation is simplified using the VoipNow Amazon AMI;
- On other cloud infrastructures. In this case, VoipNow can be installed using the VoipNow Command Line Installer.
Before Upgrade
Before getting started with the upgrade to VoipNow Platform 2.5.0 or higher, please read the recommendations below.
 | Highly Recommended Do not attempt to upgrade VoipNow Professional HA on your own. Please contact 4PSA for technical assistance before attempting to do this. |
Upgrading from VoipNow Professional 1.x to 2.x
This is the checklist you need to verify when upgrading from VoipNow Professional 1.x to 2.x:
Configure SIP Domains
If your customers use SIP:Register and send SIP:Invite requests to your server hostname (instead of the IP), then you must add this hostname to the Accepted SIP Domains list from the Unified Communications → System Preferences → SIP Preferences page.
Configure IPs
VoipNow Professional will not accept incoming calls from channels (SIP trunks) by default, unless you configure the IPs that are allowed to send these calls to the server. You can configure them following the next steps:
STEP 1: Click the Channels link available in the left navigation panel.
STEP 2: Choose the desired channel from the list and click on it.
STEP 3: Click the Edit channel icon and set the allowed networks using the controls available next to the Accept calls from IPs/network option.
Configure Processing Numbers
In VoipNow Professional 2, it is possible to process dialed numbers in outgoing routing rules before and after the call cost is interrogated according to the cost set up for the channels. When you Route a number through a channel (or through the best cost), the call cost is retrieved from the database at that time. The input for the call interrogation procedure is the processed number (the number can be modified using process directives). If you want to further process the number after the cost is interrogated and settled, you can use the basic number processing available in the Route type rules.
In VoipNow Professional 1.x, the number processing was always performed before cost interrogation and even the processing on the Route rules (previously called Transfer rules) was applied after call cost interrogation. If you want to preserve the same behavior, you need to modify the number using the process rules.
Upgrading from Former VoipNow Professional Versions to 2.5.0 or Higher
This is the checklist you need to verify when upgrading from older VoipNow Professional versions to 2.5.0 or higher:
License Key
VoipNow Professional 2.5.0 and higher requires a new license key.
| Important Notice Do not upgrade to VoipNow Professional 2.5.x if your perpetual license is not actively maintained using SUS (Software Update Subscription) or your leased subscription is not current. |
Parallels Licenses
VoipNow Professional licenses issued by 4PSA's reseller Parallels are not compatible with the latest versions of VoipNow Professional. If you happen to use such a license, do not upgrade to VoipNow Professional 2.5.0 or higher! The Parallels sales team can provide you with more details on how to upgrade such licenses.
Installer
In order to upgrade your installation, you must always use the latest version of the installer, which is available here.
Machine Hostname
Please make sure that your machine hostname resolves, otherwise daemons will start very slowly. Minimally, you can add a static entry for your machine hostname to /etc/hosts.
Queue Extension
VoipNow Professional 2.5.0 comes with a new design for the Queue extension. When the software is upgraded from a previous version, all agents lose their queue registration. Consequently, you will have to log the agents into the queue again over the phone or via the management interface. Furthermore, you must pay attention to the queue options because several new parameters have been added to control the queue behavior when all agents are logged out from the queue.
Language Packs
The structure of the language packs has been changed in order to increase the speed of API calls. To benefit from the translation of former versions of VoipNow Professional, you need to migrate to the new structure.
 | We Are Here to Help For any questions on this process, please open a support ticket at http://help.4psa.com. |
Concurrent Calls Limit
The concurrent calls limit fall under two categories: one for internal calls and another for public calls. By default, they use the old value of the concurrent calls limit. This might not be exactly what you want, so you should adjust them manually.
CallAPI
A new CallAPI has been introduced. For more details, please check the Developer's Guide. For compatibility reasons, two legacy REST methods are still available: NewCall and Test. All old CallAPI methods will be removed in VoipNow Professional 2.6.0.
Asterisk Manager Interface
VoipNow Professional exposes an Asterisk Manager compatible interface. Since its scalability is limited and it does not provide a consistent programming environment for third-party developers, this interface is going to be removed in VoipNow Professional 2.6.0. If you still want to login to the Asterisk manager interface, you can do so, but strictly from an extension level account. However, it is best that you change your application so that it will use the new CallAPI REST HTTP interface and the CallAPI Events.
Settings Moved
The Cascade, Ring All, and Authentication to reach extension settings, which were previously available in the Phone Terminal properties configuration page, have been moved to the Incoming Call Rules (ICR). The old Cascade action is now an incoming call rule, while the Ring All functionality is achieved using a Transfer rule. Although the upgrade script will convert the old properties to incoming call rules, there is no warranty that the new behavior will be absolutely identical. However, by changing the ICR, you can achieve any behavior you want.
SOAP Engine
When trying to use the SOAP engine from PHP over SSL, you might encounter connection issues, which are caused by a PHP bug. A solution would be to download the WSDL before loading it into the SOAP connection method. More details are available in the 4PSA Knowledge Base.
CallerID
The CallerID control is more complex. To make sure the CallerID behavior has not changed on your environment, you should check the CallerID settings of your extensions after the upgrade. The newly introduced CallerID management permission also allows you to restrict users to perform CallerID changes.
SystemAPI
The old SOAP API was renamed SystemAPI. Many methods have changed, mainly due to the new properties introduced in VoipNow Professional 2.5.0. If you connect to an old version of the SOAP server, the default values will be used for the newly introduced fields that were not defined on that version. This might lead to unexpected results, and so, it is highly recommended to update your SOAP client. In the new version, it is also possible to enable/disable the SystemAPI access on a user level.
MyVoipNow
VoipNow Professional 2.5.x contains references to MyVoipNow, an upcoming 4PSA product. All settings related to MyVoipNow should be ignored until the new product becomes available. In terms of functionality, they do not have any impact on VoipNow Professional.
Update libxml2
You must be careful to update your operating system so that you have the latest version of the libxml2 library. The CallAPI Events service needs the libxml2 library to be compiled with thread support. This is done in libxml2-2.6.26-2.1.12 or higher.
Add Comment