105 posts tagged with "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!

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!

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!

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!

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!