Wazo 17.01: ISO issue

Added by Sébastien Duthil 12 days ago

Hello Wazo community!

We just found out there was a bug in the Wazo 17.01 installation process from the ISO image (#6547).

This issue only affects ISO installations. The symptom shows when validating the installation web wizard: you would see a big red block mentioning "Error 500". If your ISO installation did not show this symptom, then this bug will not have any other side-effect.

We have replaced the 17.01 ISO file to include the correction of the problem. Any 17.01 ISO file downloaded before Wednesday 2017-01-11 20:15:00 UTC should be replaced:

We also found out that installing any Debian package before validating the wizard would circumvent the issue. That's the reason why the bug slipped through our testing harness. Rest assured that we adjusted our tests accordingly.

We apologize for this error and hope you enjoy Wazo 17.01!

The Wazo dev team

Wazo 17.01 released (1 comment)

Added by Sébastien Duthil 15 days ago

Sprint Review 17.01

We took a bit of extra time to release this version, due to the holidays here in Québec City. So this version took 4 weeks to release, but upcoming versions will be released every 3 weeks.

New features in this sprint

REST API: Parking lots may now be managed via REST API. A parking lot is a range of phone numbers reserved for pending calls: by default, you can park call to the parking lot 700 and retrieve those calls by dialing 701, 702, etc. Currently, the web interface only allows one parking lot, from 700 to 750 by default. The REST API allows you to create as many parking lots as you want, for example one per entity, to avoid mixing up calls from different entities in the same parking lot.

REST API: We added another REST API for paging groups. This API offers about the same features than the web interface, allowing you to use a group of phones as PA speakers.

REST API: A new REST API has been added in order to place a new call from the mobile phone of a user. This will come in handy for a mobile application, where you can call a contact by clicking a button. Your mobile phone will be called by Wazo and once you answer you will hear your contact ringing. This means your mobile operator will charge an inbound call to your mobile phone instead of an outbound call.

Technical features

Consul: Consul was upgraded to 0.7.2. We also removed the management of authentication tokens from Consul and used good old PostgreSQL instead. So Consul now only serves for service discovery, which is useful when connecting multiple Wazo together.

LibPRI: LibPRI was upgraded to 1.5.0.

9 bugs were fixed, 5 features were added and 4 technical issues were resolved since Wazo 16.16. The complete list of features and fixes is available at


As usual, upgrading your Wazo must be done by following this procedure:


Instructions to install Wazo:
You can download the ISO here: The client can be downloaded from the following links:


You can consult the documentation in the following formats:

Tests reports

Wazo tests report (french version) can be consulted here: (manual tests) (automatic tests)

See you for the next sprint review.

Wazo 16.16 released (1 comment)

Added by Etienne Lessard about 1 month ago

Sprint Review 16.16

Hello Wazo community! Here comes the first release of Wazo, Wazo 16.16!

If your are new to the Wazo project, you should take a look at this blog post that explains why the project was created.

We will describe here the changes made since XiVO 16.13, which is the release of XiVO where Wazo starts from. This sprint review is a bit longer than the others, since it includes the equivalent of 3 versions, 16.13 having been released more than 2 months ago. Future releases will come out every 3 weeks, except for quality assurance no-gos.

New features in this sprint

Migration from XiVO infrastructure: Since the domain went down, we spent some time rebuilding everything that was needed to make Wazo work correctly from a XiVO installation. You can find the instruction to migrate from XiVO on the documentation. Note that you don't have to upgrade your XiVO to use the new infrastructure. See the documentation for more details.

Codecs: The Opus codec is now available in Wazo. The Opus codec is a very efficient codec that has been around for a while, but is a potential subject for patent-infringement lawsuits. The Asterisk editor Digium came out with a solution that we deem satisfying, given the great advantages of the Opus codec.

Documentation: We have improved the documentation for using REST APIs. You can see the instructions on this page

REST API: A new REST API has been added to manage SIP trunks and outgoing calls. Trunks and outgoing calls were the last missing APIs to be able to control inbound and outbound call routing without the need of the web interface.

REST API: Groups may now be managed via REST API. A very popular usage for groups is to ring the multiple phones of the same user with the same phone number. Note that the REST API allows you to assign multiple lines to a single user, giving you the same behavior as the aforementioned group configuration, but without some drawbacks of the groups. So this REST API is mainly intended for groups ringing multiple users.

REST API: We have added another REST API to manage conference rooms. The conference rooms from the REST API are quite different from the conference rooms we were used to from the web interface: they use a different backend (Confbridge instead of Meetme) and have the additional feature of conference administration: by entering the right PIN, one becomes administrator of the conference and may mute or reject other members.

REST API: Yet another REST API, this time for IVR (interactive voice response): you can create simple IVR via the REST API, without needing to write dialplan.

Directories: Until now, XiVO allowed only one phonebook, that was shared across all entities, meaning all users of different entities would see the same contacts that are stored in the phonebook. This was clearly not a good idea, since the purpose of entities is to isolate users from each other while staying on the same server. You may now configure multiple phonebooks on the same Wazo. Phonebooks may be shared across entities or isolated, at your convenience.

Scalability: We've made it a bit easier to share contacts between multiple Wazo servers, in that new servers will be auto-discovered, instead of having to manually configure each server to share contacts. See the updated documentation for the new procedure.

Technical features

Asterisk: Asterisk has been upgraded from 13.11.2 to 14.2.1, including security fixes.

Ongoing features

Switchboard: We are changing the internals of the Switchboard feature so that we can control more precisely how calls are answered, transferred, etc.

20 bugs were fixed, 25 features were added and 11 technical issues were resolved since XiVO 16.13. The complete list of features and fixes is available at


Upgrading from XiVO to Wazo requires a special procedure:


Instructions to install Wazo:
You can download the ISO here: The client can be downloaded from the following links:


You can consult the documentation in the following formats:

Tests reports

Wazo tests report (french version) can be consulted here: (manual tests) (automatic tests)

Thanks for you support and encouragement and see you at the next sprint review!

Introducing Wazo

Added by Sébastien Duthil about 2 months ago

Hi everyone, long time no see!

We are pleased to announce the birth of a fork of XiVO named Wazo. You can find more details about the fork in this blog post.

If you have comments or questions, we'll be happy to discuss on our forums, in english or in french.

See you soon!


Also available in: Atom