Have an itch with your communication system?

Posted on Wed 01 February 2017 in Wazo IPBX by The Wazo Authors • Tagged with wazo

French/Français: Une version française plus bas

Have an itch with your communication system?

Hello Wazo community! We would like to hear from you.

The development of Wazo is fast paced with a long term vision of what should be the future of telecommunications. But in order to reach that goal we have many features and milestones that we have to go through. That's why we would like to hear from you. To be able to start with what matters most to our users.

If you are a telecommunications solution provider tell us about you needs.

What are your customers asking for? What would make you more productive?

Help us improve Wazo the way you want. We are open to discussions to see how we can work together and contribute to the future of Wazo.

No taboos, everything can be discussed...

Join us on the forum or in private: contact@wazo.community

Votre système de communication vous rend la vie dure ?

Bonjour communauté Wazo ! Nous aimerions vous entendre.

Le développement de Wazo est rapide avec une vision à long terme de ce que devrait être le futur des télécommunications. Nous avons plusieurs fonctionnalités à développer pour atteindre ce but. C'est pour cette raison que nous aimerions connaître votre avis. Nous voulons savoir ce qui est le plus important pour vous, pour travailler ensemble sur ce qui importe le plus en premier.

Si vous êtes un intégrateur de solutions de télécommunications, dites-nous ce qui peut vous aider.

Qu'est-ce que vos client vous demandent ? Qu'est-ce qui vous rendrait plus productif ?

Aidez-nous à améliorer Wazo de la façon que vous voulez. Nous sommes ouverts aux discussions pour voir de quelle façon nous pouvons travailler ensemble pour contribuer au futur de Wazo.

Il n'y a pas de tabous, tous les sujets peuvent êtres abordés...

Joignez-nous sur le forum ou en privé: contact@wazo.community


Sprint Review 17.02

Posted on Mon 30 January 2017 in Wazo IPBX by The Wazo Authors • Tagged with wazo, development

Hello Wazo community! Here comes the release of Wazo 17.02!

We're back to our usual 3-weeks release cycle :)

New features in this sprint

API schedules: Schedules may now be managed via REST API. Schedules allow calls to be redirected to other destinations depending on the time and day that they arrive. For example during holidays, calls could be redirected to a voicemail instead of ringing a phone nobody would answer.

WebRTC lines: The web interface now allows associating "WebRTC lines" to users. WebRTC is a recent feature of browsers that makes it possible to have a web softphone: you don't need a specific application to handle your calls, instead you can answer, talk and hangup directly on a web page. You can try out WebRTC with Wazo on https://phone.wazo.community. The "WebRTC line" actually creates a SIP line with a bunch of predefined parameters that are required to be able to use this SIP line in a WebRTC application, so it will appear as a SIP line afterwards.

Ongoing features

Switchboard API: We are changing the internals of the Switchboard feature so that we can control more precisely how calls are answered, transferred, etc. We are also adding a REST API over the switchboard feature, to allow different interfaces for the switchboard, be it web or desktop client.

API policies permissions: The current model of permissions for authentication tokens is a bit too rigid to give users only the permissions they need. We are making the system more flexible in order to have more fine-grained control over what user is allowed to do, such as entering/leaving only certain groups, answering calls from certain switchboards, etc.

New web interface: The first lines of code of a new web interface have been written. This web interface will only use the REST API we've been developing in the past few years, with no brittle complicated internal logic like the current web interface has: all the logic is handled by the REST APIs. This web interface will not replace the current web interface before it has all the same features, so it will take time to become the default. However, both web interfaces will coexist during the maturation of the new one.


See you at the next sprint review!

Sources:


Sprint Review 17.01

Posted on Mon 09 January 2017 in Wazo IPBX by The Wazo Authors • Tagged with wazo, development

Hello Wazo community! Here comes the release of Wazo 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.


See you at the next sprint review!

Sources:


Sprint Review 16.16

Posted on Mon 12 December 2016 in Wazo IPBX by The Wazo Authors • Tagged with wazo, development

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 xivo.io 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.


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

Sources:


Introducing Wazo

Posted on Mon 05 December 2016 in Wazo software by The Wazo Authors

French/Français: La version française suit la version anglaise.

 

Hi everyone, long time no see!

We've been quite busy the last few days, but we are pleased to announce the birth of a new project in the world of communications, introducing: Wazo.

What is Wazo?

Wazo is a unified communication platform and a full-featured IPBX based on Asterisk, oriented towards enterprise communications. Wazo was forked from XiVO on November 25th, 2016, starting off the development version following XiVO 16.13. Every feature of XiVO 16.13 is still available in Wazo, and there are more to come...

Who are we?

The Wazo development team is led by Sylvain Boily (founder of XiVO in 2005) and working together on XiVO since 2010 in Québec City (Canada). This team is highly dedicated to develop and maintain its unique platform and share ideas with the community:

  • Sylvain Boily
  • Etienne Lessard
  • Pascal Cadotte-Michaud
  • Sébastien Duthil
  • François Blackburn

What is our vision?

We strongly believe that telephony should be available everywhere: on any device, in any application, in any software environment you have, so that you can call who you want, when you want. In order to achieve this, we want a telephony software that is easy to setup, easy to integrate with other software, scalable and extendable at will.

Free software is in our sense the only way to go in this direction because it ensures that users can adapt Wazo to their own specific situations where telephony is needed, and that they are free to choose who to ask for help. For this, the project needs a strong community and the most important part in this project is cooperation in the community: all the passionate people who use, install and modify Wazo should work together, exchange needs, feature requests, specifications, bug reports, patches and pull requests. Because that is in our sense the best way to make this project go further.

Be sure that Wazo will keep the spirit of the original XiVO project:

  • a totally free software, pure GNU GPL project,
  • stable release every 3 weeks,
  • developers can answer your questions,
  • and the most important, an incredible community on the forums, IRC (#wazo on Freenode) and Github

What's next?

We intend to continue the work we have started a few years ago: make Wazo completely controllable through REST APIs, which is one of the best way we know of to enable easy interconnection with other software systems. These APIs also allow people to develop graphical interfaces easily and we certainly intend to use those APIs to make graphical interfaces, like a more modern web interface or a mobile application. Moreover, APIs give more flexibility for creating distributed or centralised systems over multiple machines... Possibilities are vast and don't hesitate to share your own ideas: let's write together the future in telecommunications!

When is our next release due?

We will release Wazo 16.16 very shortly, in the next few days. We will provide a simple procedure to upgrade your XiVO installation to Wazo, we want to keep the transition as smooth as possible. Keep in touch!

 

Version française

Salut tout le monde, ça fait longtemps!

Nous avons été bien occupés ces derniers jours pour préparer la naissance d'un nouveau projet dans le monde de la communication: nous vous présentons Wazo.

C'est quoi Wazo?

Wazo est une plate-forme de communication unifiée et un IPBX complet basé sur Asterisk et orienté vers la communication d'entreprise. Wazo est un fork de XiVO, démarré le 25 novembre 2016 à partir de la version de développement suivant la sortie de XiVO 16.13. Toutes les fonctionnalités de XiVO 16.13 sont toujours présentes dans Wazo, et on ne va pas s'arrêter là...

Qui sommes-nous?

L'équipe de développement de Wazo est menée par Sylvain Boily (l'initiateur du projet XiVO en 2005) et travaille ensemble depuis 2010 à Québec (Canada). La principale motivation de cette équipe est de développer et maintenir cette plate-forme unique et de partager ses idées avec la communauté:

  • Sylvain Boily
  • Etienne Lessard
  • Pascal Cadotte-Michaud
  • Sébastien Duthil
  • François Blackburn

Quelle est notre vision?

Nous croyons fermement que la téléphonie devrait être accessible partout: quel que soit l'appareil, l'application, l'environnement logiciel que vous avez, vous devriez pouvoir appeler qui vous voulez, quand vous voulez. Pour accomplir cela, nous voulons un logiciel de téléphonie qui soit facile à mettre en place, facile à intégrer à d'autres logiciels, scalable et extensible à volonté.

Le logiciel libre est pour nous le seul chemin qui permette d'aller dans cette direction parce qu'il garantit aux utilisateurs qu'ils peuvent adapter Wazo à leur propre situation pour y inclure de la téléphonie, et qu'ils peuvent choisir à qui demander de l'aide pour ce faire. Pour cela, le projet Wazo a besoin d'une communauté active et la part la plus importante du projet est la coopération à l'intérieur de cette communauté: tous les passionnés qui utilisent, installent et modifient Wazo doivent pouvoir travailler ensemble et échanger des besoins, des idées de fonctionnalités, des spécifications, des rapports d'erreurs, des correctifs et des pull requests. C'est selon nous, le meilleur moyen pour faire avancer ce projet.

Bien sûr, Wazo garde l'esprit du projet original XiVO:

  • un projet complètement libre en GNU GPL,
  • une nouvelle version stable toutes les 3 semaines,
  • les développeurs peuvent répondre à vos questions
  • et le plus important, une super communauté sur les forums, IRC (#wazo sur Freenode) et Github

C'est quoi la suite?

Nous avons l'intention de continuer le travail que nous avons commencé depuis quelques années: rendre Wazo totalement contrôlable par des API REST, qui sont l'un des meilleurs moyens que nous connaissons pour faciliter l'interconnexion avec d'autres logiciels. Ces API permettent à tout le monde de développer des interfaces graphiques, et nous entendons bien écrire quelques unes de ces interfaces, comme une interface web plus moderne ou une application mobile. De plus, les API donnent une meilleure flexibilité pour mettre en place des systèmes téléphoniques centralisés ou décentralisés, répartis sur plusieurs machines... Les possibilités sont nombreuses, alors n'hésitez pas à partager vos idées: nous pourrons construire ensemble l'avenir des télécommunications!

Quand sortira notre prochaine version?

Nous publierons Wazo 16.16 très prochainement, dans les jours qui viennent. Nous fournirons une procédure simple pour mettre à jour votre XiVO en Wazo pour garder la transition la plus facile possible. Restez à l'affût!