Hello Wazo Platform community!

Here is a short review of the Wazo Platform 20.01 release.

New features in this sprint​

• Switchboard: We have worked on improving the switchboard reactivity. In this version, the time to answer a call has been reduced by half. These changes may also impact positively the response time of other actions made on the calls in a switchboard.
• Monitoring: We have added a new HTTP resource to retrieve the current status of user telephony lines in wazo-calld REST API. This allows an external application to know which phones are busy, available or disconnected. This feature is currently very similar to the wazo-chatd presence features, but it will be improved with more details irrelevant to wazo-chatd, like the round-trip time to a phone.
• Users: We have improved the users REST API to add information related to user interception. When getting a user's details, you may now get the list of people that this user is allowed to intercept.
• Class 4: We are releasing a first version of the SBC and call routing features of Wazo Platform, featuring Kamailio. Here are the links to the installation documentation and REST API documentation.

Contributions​

• Hardware: While not directly related to this version, we're excited to share with you the announcement of a distribution for Wazo Platform on Raspberry Pi, named Sparrow [https://sparrow.b5.pm]. You can find the announcement on our forums.

Technical features​

• Asterisk: Asterisk was updated from 16.6.2 to 16.7.0, including 2 security fixes.
• Orchestration: wazo-calld can now run independently from Asterisk. Of course it can not do much without it, since the main purpose of wazo-calld is to manage calls that are placed through Asterisk. This makes Wazo Platform easier to setup in a orchestrated environment such as containers.

Ongoing features​

• Reliability: We are working on improving the stability of Wazo Platform in different scenarios: high number of users, REST API calls and events, temporary loss of one of Wazo services...
• Class 4: added new blocks in Wazo Platform to handle more calls and improve security. Kamailio is the core of those new features and will serve as a Session Border Controller (SBC) and SIP router to multiple Asterisk instances

For more details about the aforementioned topics, please see the roadmap linked below.

See you at the next sprint review!

Hello Wazo Platform community!

Here is a short review of the Wazo Platform 19.17 release.

New features in this sprint​

• Directories: In wazo-dird, a new HTTP endpoint has been added to retrieve multiple contacts in one request when you only know their contact UUID
• Trunks: A new HTTP resource has been added to list the status of all trunks, including their registration status and the number of current calls

Bug fixes​

• Call center: After and agent and a skill were associated or dissociated via the REST API, the modification was not applied in Asterisk automatically.
• Websocket: The number of events processed by wazo-websocketd has been significantly reduced by ignoring all technical messages coming from the Asterisk AMI
• Presences: Fixed initialization when non-PBX users have refresh tokens
• Call logs: When a call was placed to a call group, answered then hung up, the call log genration of that call consumed a lot CPU time
• Trunks: Fixed a bug that made a trunk stop trying to reconnect after a failed attempt due to missing configuration options in wazo-confgend

Technical features​

• Asterisk: Asterisk was updated from 16.6.1 to 16.6.2 (security fix)
• Phone directories: All wazo-dird phone plugins that handled specific directories for physical phones have been migrated to wazo-phoned
• Google integration: wazo-dird Google backend now filters out e-mail contacts automatically generated by Google
• DAHDI: DAHDI is not longer an explicit dependency of Wazo. It is now an optional component that should only be installed when server-side telephony hardware is used.
• Performance: The CPU usage of wazo-websocketd has been reduced significantly

Ongoing features​

• Switchboard: We are working on improving the switchboard call flow response time
• Reliability: We are improving the stability of the platform in different scenarios: high number of users, temporary loss of one of Wazo services, high number of API calls / events...
• SBC: We are adding new blocks in Wazo Platform to handle more calls and improve security. Kamailio is the core of those new features and will serve as a Session Border Controller (SBC) and SIP router to multiple Asterisk instances
• Monitoring: We are adding a new HTTP resource to retrieve the status of user telephony lines (disconnected, available, on call...)

For more details about the aforementioned topics, please see the roadmap linked below.

See you at the next sprint review!

Hello Wazo Platform community!

Here is a short review of the Wazo Platform 19.16 release.

New features in this sprint​

• Directories: lookups are now insensitive to accented characters.

Ongoing features​

• Switchboard: We are working to improve the switchboard call flow response time.
• BLF: The Busy Lamp Field (BLF) of Do Not Disturb mode, call forwards and call filtering are being reimplemented to restore the behavior of Wazo 18.03.
• Call logs: We are handling more scenarios in the Wazo Platform CDR. We are focused on the call forwarding scenarios, in order to present the correct numbers to users.
• SBC: We are adding new blocks in Wazo Platform to handle more calls and improve security. Kamailio is the core of those new features and will serve as a Session Border Controller (SBC) and SIP router to multiple Asterisk instances.

For more details about the aforementioned topics, please see the roadmap linked below.

See you at the next sprint review!

Hello Wazo Platform community!

Here is a short review of the Wazo Platform 19.15 release.

New features in this sprint​

• Trunks: It is now possible to create two trunks with same username

Bug fixes​

• Presence status: There were some scenarios where the presence status was incorrect, e.g. hanging up a hold call. They are now fixed.
• Call interception: Up until Wazo Platform 19.15, call interception was enabled for every user through the extension *8, e.g. *81001 for intercepting user 1001. This setting is now disabled by default. The preferred way to setup call interception is to use Interception groups, which define which user can intercept which other user.
• Call reliance: We fixed a problem with WebRTC calls: sometimes, the call was hungup before even ringing the destination.

Technical features​

• Asterisk: Asterisk was updated from 16.5.1 to 16.6.1, fixing 1 security issue.

Ongoing features​

• Switchboard: We are working to improve the switchboard call flow response time, because the switchboard user needs the most reactivity from its application. These improvements may also have a positive outcome on non-switchboard calls reactivity as well.
• BLF: The Busy Lamp Field (BLF) of Do Not Disturb mode, call forwards and call filtering are being reimplemented to restore the behavior of Wazo 18.03.
• Call logs: We are handling more scenarios in the Wazo Platform CDR. We are focused on the call forwarding scenarios, in order to present the correct numbers to users.
• SBC: We are adding new blocks in Wazo Platform to handle more calls and improve security. Kamailio is the core of those new features and will serve as a Session Border Controller (SBC) and SIP router to multiple Asterisk instances.

For more details about the aforementioned topics, please see the roadmap linked below.

See you at the next sprint review!

New features in this sprint​

Admin-UI web interface: A lot of management plugins have been improved. Also, plugins for managing general settings (SIP, voicemails, conference rooms), schedules, devices, boss-secretary filters, call permissions, CDR export, extension features (like DND, call forwards, call recording, etc.) have been added.

Admin-UI web interface: The login page has been redesigned.

Contributions​

Aastra/Mitel firmware: We thank Alexis de Lattre and José Herbrecht for submitting updates to the provisioning plugins for Aastra/Mitel phones.

Technical features​

Asterisk: Asterisk was updated from 15.2.0 to 15.2.2, fixing 6 security issues.

Ongoing features​

User and Tenant Management: We are currently reworking the user and entities (a.k.a tenant) configuration. This should make installations with multiple entities feel more natural in future versions.

REST API: We are working towards replacing the old orange admin web interface with the more modern and easier to maintain blue web interface (wazo-admin-ui on /admin). Since wazo-admin-ui is only using REST API under the hood, we need REST API to cover all cases of administration of Wazo. Hence we are completing the set of REST APIs offered by Wazo. You can find the complete API documentation on https://wazo-platform.org/documentation.

Authentication: We are changing the authentication mechanism of users and administrators to use a more secure storage. Most of the login experience will be the same, with a few limitations, like not being able to see passwords in clear text.

---

The instructions for installing Wazo are available in the documentation. The instructions for upgrading Wazo as also available in the documentation. Be sure to read the breaking changes.

For more details about the aforementioned topics, please see the roadmap linked below.

See you at the next sprint review!

New features in this sprint​

REST API: We added new REST APIs to manage call filters (i.e. boss-secretary filters). Those APIs will allow us to manage call filters from the new admin-ui web interface.

CDR: The CDR REST API has been improved: for a given call, we have the two following information: 1. what extension has been dialed and 2. what extension or user has answered the call.

Admin-UI web interface: A lot of management plugins have been improved. Also, plugins for managing sound files, SIP trunks, IAX trunks and SIP, SCCP and custom lines have been added.

Ongoing features​

User and Tenant Management: We are currently reworking the user and entities (a.k.a tenant) configuration. This should make installations with multiple entities feel more natural in future versions.

REST API: We are working towards replacing the old orange admin web interface with the more modern and easier to maintain blue web interface (wazo-admin-ui on /admin). Since wazo-admin-ui is only using REST API under the hood, we need REST API to cover all cases of administration of Wazo. Hence we are completing the set of REST APIs offered by Wazo. You can find the complete API documentation on https://wazo-platform.org/documentation.

---

The instructions for installing Wazo are available in the documentation. The instructions for upgrading Wazo as also available in the documentation. Be sure to read the breaking changes.

For more details about the aforementioned topics, please see the roadmap linked below.

See you at the next sprint review!

New features in this sprint​

REST API: REST APIs have been added for:

• SCCP general configuration
• IAX trunks configuration
• ConfBridge configuration
• Special extensions configuration, e.g. setting DND extension to *55 instead of *25, etc.
• Sound files
• Trunk registrations

Technical features​

System: the underlying Debian GNU/Linux system is upgraded to Debian 9 Stretch. The upgrade procesure is a bit different than usual and will take longer than previous upgrades. See the specific release notes for more details.

Asterisk: Asterisk is upgraded to the latest version 15.2.0.

Contributions​

Yealink: The provisioning plugin for Yealink now includes the v82 firmware. Thanks to DamienB505 for the patches!

Ongoing features​

User and Tenant Management: We are currently reworking the user and entities (a.k.a tenant) configuration. This should make installations with multiple entities feel more natural in future versions.

REST API: We are working towards replacing the old orange admin web interface with the more modern and easier to maintain blue web interface (wazo-admin-ui on /admin). Since wazo-admin-ui is only using REST API under the hood, we need REST API to cover all cases of administration of Wazo. Hence we are completing the set of REST APIs offered by Wazo. You can find the complete API documentation on https://wazo-platform.org/documentation.

---

The instructions for installing Wazo are available in the documentation. The instructions for upgrading Wazo as also available in the documentation. Be sure to read the breaking changes.

For more details about the aforementioned topics, please see the roadmap linked below.

See you at the next sprint review!

Hello Wazo community!

This release is our birthday release, since the fork! Thanks for following us this last year and keep in touch, the best is yet to come. :)

New features in this sprint​

REST API: REST APIs have been added for SIP trunks, timezones, prompt languages, call permissions voicemail and IAX configuration.

Network: NAT configuration has been simplified, when the Wazo server is hosted in a datacenter.

API interconnection: Wazo is now able to use OAuth2 authentication client mechanisms to interact with external API systems. The first example we are working on is to interconnect Wazo with Zoho, other such API include Google, Office 365, etc.

Ongoing features​

User and Tenant Management: We are currently reworking the user and entities (a.k.a tenant) configuration. This should make installations with multiple entities feel more natural in future versions.

REST API: We are working towards replacing the old orange admin web interface with the more modern and easier to maintain blue web interface (wazo-admin-ui on /admin). Since wazo-admin-ui is only using REST API under the hood, we need REST API to cover all cases of administration of Wazo. Hence we are completing the set of REST APIs offered by Wazo. You can find the complete API documentation on https://wazo-platform.org/documentation.

---

The instructions for installing Wazo are available in the documentation. The instructions for upgrading Wazo as also available in the documentation. Be sure to read the breaking changes.

For more details about the aforementioned topics, please see the roadmap linked below.

See you at the next sprint review!

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

New features in this sprint​

REST API: Groups can now ring arbitrary extensions. This was already possible with a specific user, a custom line and a Local channel. This API does the same thing, only a lot simpler. There is no graphical interface to use this API yet, though.

REST API: Until now, schedules in REST API could only be associated to incoming calls. Schedules can now be associated with users, groups and outgoing calls via REST API.

Ongoing features​

User and Tenant Management: We are currently reworking the user and entities (a.k.a tenant) configuration. This should make installations with multiple entities feel more natural in future versions.

REST API: We are working towards replacing the old orange admin web interface with the more modern and easier to maintain blue web interface (wazo-admin-ui on /admin). Since wazo-admin-ui is only using REST API under the hood, we need REST API to cover all cases of administration of Wazo. Hence we are completing the set of REST APIs offered by Wazo. You can find the complete API documentation on https://wazo-platform.org/documentation.

---

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

For more details about the aforementioned topics, please see the roadmap linked below.

See you at the next sprint review!

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

We are looking for beta testers for the Wazo Zapier plugin. You can click this invite link to try Wazo with Zapier.

Security update​

Chat: We fixed a security issue of Wazo 17.14 where the chat history of a user could be seen by another authenticated malicious user.

Important bug fix​

Web client: Wazo servers installed or upgraded on 17.14 between October 10 and October 24 2017 are incompatible with Web clients such as Unicom. We released a fixed version on October 24 to fix Wazo 17.14. Wazo 17.15 also fixes the issue.

New features in this sprint​

REST API: We have added a new API to be able to switch a call between devices while keeping the conversion going. For example, if Alice is on the phone with Bob from her office, Alice can switch the call from her desk phone to her mobile phone without disrupting the call so that she can leave her office without ending the conversation.

Ongoing features​

User and Tenant Management: We are currently reworking the user and entities (a.k.a tenant) configuration. This should make installations with multiple entities feel more natural in future versions.

Performance: We are making changes to the way xivo-ctid-ng handles messages from Asterisk to be able to handle more simultaneous calls.

New upstream versions​

Asterisk: Wazo now includes Asterisk 15.0.0.

---

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

For more details about the aforementioned topics, please see the roadmap linked below.

See you at the next sprint review!