Page History

...

Upgrade from VoipNow 3.5.

...

x, 3.6.

...

x or 3.7.

...

x

In VoipNow 4.0.0 and newer versions, the email address of VoipNow accounts (Service Provider, Organization, User) should be unique. Before upgrading to the latest version it is required necessary to check the accounts database for duplicate emails. We have made available a script that allows you to detect such accounts before starting the upgrade.

Login to the VoipNow server (single server deployments) or Infrastructure Controller (distributed deployment). Execute the following command:

this This will download the check script on your machine.

Run the script by executing the command:

/usr/local/httpsa/php/bin/php --define register_argc_argv=On --define open_basedir=/usr/local/voipnow:/sbin:/tmp:/etc/voipnow:/usr/local/hubphp --define include_path=/usr/local/voipnow/admin/htdocs:/usr/local/hubphp/libs/PEAR:/usr/local/hubphp:/usr/local/hubphp/libs -q detectduplicateemails.php

if If any duplicated emails are found, you it will display an output like this:

Found 8 duplicate emails. A csv file with complete information was saved at /tmp/duplicate_emails20151112120024.csv

...

We recommend you to check the release notes, as they might contain important notes, such as the ones about deprecating technologies.

...

Due to the newly introduced ICE support, SIP packages will contain more information (candidates) and therefore will be larger. While this is normal and creates many benefits, it might also create problems issues with very old equipment that have trouble dealing with SIP packages larger than 1500 bytes. We advise you to test the latest version of VoipNow with your existing trunking channels.

G729

...

not enabled by default

While G729 is still supported, we disabled it by default because a very small number of customers acquired appropiate appropriate licensing for it.

On a side note, VoipNow 3.5.0 comes with modern codecs that provide a better voice quality and smarter bandwidth usage than G729.

...

Upgrade from VoipNow Professional 2.5.x

Upgrade from VoipNow Professional 2.5.x to VoipNow 3 is technically supported, assuming that a valid license is available for VoipNow 3.

...

The SystemAPI will be phased out in the future and replaced by a management service in UnifiedAPI.

UnifiedAPI for

...

call control

The old CallAPI requests must be migrated to the UnifiedAPI requests, the new API that will cover in the future all Apps interaction with VoipNow.

...

The former Platform Plug-ins section in Automation has undergone severe many changes. Technology plug-ins can now be used to define a cloud instance for a specific technology version. The cloud instance can be upgraded to the newest technology version when the platform gets upgraded on the deployment facility.

...

There is no Asterisk Manager Interface in the new version. This is a deprecated, old technology that has been removed forever. UnifiedAPI  UnifiedAPI is the way to go.

VoipNow Desktop is deprecated

VoipNow 3 is not compatible with VoipNow Desktop. VoipNow Desktop is a discontinued product.

Devices that

...

do not answer to SIP options

VoipNow is now recording unreachable extensions (those that do not answer to SIP:Options requests). The unreachable status is now considered by the Incoming Call Rules engine in Transfer rules, if "Not registered/Unreachable" option is enabled. Because some SIP devices might not answer to SIP:Options, in order to prevent the Transfer rule to always trigger disable pinging for those extensions.

...

VoipNow is not accepting incoming calls from any IP. You have to configure the information related to the IPs that are allowed to send calls on a specific SIP trunk. You can configure them following the next steps in the web user interface:

1. Click the Channels link available in the left navigation panel.
2. Choose the desired channel from the list and click on it.
3. Click the Edit channel icon and set the allowed networks using the controls next to the Accept calls from IPs/network option.

...