Sprint Review 17.04

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

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

New features in this sprint

CSV import of a phonebook: The CSV import had been removed from the web interface when we allowed many phonebooks to be available on the same Wazo. Many administrators have reported that they used that feature for their end users. You told us and we heard you. The CSV import is back.

Technical features

Asterisk: Asterisk has been updated from 14.2.1 to 14.3.0

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: 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 interface. However, both web interfaces will coexist during the maturation of the new one. We'll keep you posted when the new web interface becomes usable.

Plugin management: We are currently working a plugin management service as well as a standard plugin definition that will be easy to write. The goal is to allow users to add features easily to Wazo and to be able to distribute their extensions to other users. This new system will be used to install features on the new administration interface.


The instructions for installing Wazo or upgrading Wazo are available in the documentation.

See you at the next sprint review!

Sources:


How to configure Asterisk when Wazo does not implement a functionality

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

Customizing your Asterisk configuration on Wazo

Wazo is a full featured IPBX using Asterisk. It has many functionalities implemented in its configuration interface and many API to configure your telephony system. But sometimes what you need is simply missing. This article will show some common ways to modify your Wazo server to use features from Asterisk that are not available in the wide range of Wazo tools.

Dialplan

Dialplan is used to modify the flow of a call. The easiest way to add dialplan to Wazo is through its web interface in the Services -> IPBX -> Configuration files menu. The xivo-extrafeatures context is available to all users and can be used to add new extensions to your dial plan. New contexts can also be added using the Asterisk dialplan syntax.

Customizing asterisk configuration files

Extra dialplan files can be added in /etc/asterisk/extensions_extra.d/.

The Wazo dialplan

The dialplan shipped with Wazo can be found in /usr/share/xivo-config/dialplan/asterisk reading this dialplan may help find available options that can be tweaked using subroutines and debug call flow problems.

Subroutines

Most resources (a group, a user, a conference room, etc.) on a Wazo can execute a dialplan subroutine before being reached. This allows the administrator to add custom dialplan before calling the Asterisk application.

For example:

With the following contexts in xivo-extrafeatures.conf

[aastra-autoanswer]
exten = s,1,SIPAddHeader(Alert-Info: info=alert-autoanswer)
same = n,Return()

If a user has the aastra-autoanswer subroutine, his phone will answer automatically, instead of ringing.

User preprocess subroutine

Configuration files

Asterisk configuration files are in /etc/asterisk. Most configuration files are generated by xivo-confgend. To view the generated output of a configuration file, use the command that is in the configuration file.

For example, the content of /etc/asterisk/sip.conf is:

; autogenerated from xivo-confgend

#exec /usr/bin/xivo-confgen asterisk/sip.conf

To view the generated configuration file you can do the following command:

xivo-confgen asterisk/sip.conf

You can add or overwrite values to a section using the following syntax:

; autogenerated from xivo-confgend

#exec /usr/bin/xivo-confgen asterisk/sip.conf

[general](+)
accept_outofcall_message=yes
outofcall_message_context=astsms

This example adds or modify the options accept_outofcall_message and outofcall_message_context in the general section of the sip.conf file.

Note that these changes will have to be redone at each upgrade modifying the configuration file. The old version will be kept in a .dpkg-old file:

> ls /etc/asterisk/sip.conf*
sip.conf  sip.conf.dpkg-old

Some configuration files also include another directory that should be used when available, e.g.:

/etc/asterisk/manager.conf

[general]
enabled = yes
webenabled = yes
port = 5038
bindaddr = 0.0.0.0

#include manager.d/*

All files in /etc/asterisk/manager.d/ will be read when reloading the configuration and these files will not be modified during an upgrade.

Here's a summary of what happens when Asterisk starts, and what configuration files will be read on Wazo. Thanks to J Az from the Wazo forum for this diagram!

Asterisk configuration read flow

If you do these kinds of customizations on your own, make sure you read the Wazo upgrade notes before upgrading: major updates of Asterisk can break your custom configuration if you're not careful.


Sprint Review 17.03

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

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

New features in this sprint

Music on hold API: There are new REST API for managing music on hold classes and audio files related to music on hold. Music on hold control what callers hear when they arrive in a queue or user group, while agents or users are ringing. One music on hold class may contain multiple sound files that will be played one after the other.

Technical features

Consul: Consul has been updated from 0.7.2 to 0.7.3. Consul is used for service discovery across multiple Wazo installation.

libpri: LibPRI has been updated from 1.5.0 to 1.6.0. LibPRI is used for some hardware telephony cards (E1, T1, J1).

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 interface. However, both web interfaces will coexist during the maturation of the new one. We'll keep you posted when the new web interface becomes usable.


See you at the next sprint review!

Sources:


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: