Hello Wazo Platform community!

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

New features in this release​

• Agents: Until Wazo Platform 20.11, agents were automatically logged in on their main line. In Wazo Platform 20.11, an agent may now choose on which of her lines will ring when receiving a call distributed from a queue.

• CTI: Wazo Platform offers API to control a physical phone. Until 20.11, Wazo Platform could mute or hangup a call on a physical phone. There is now a new API to put a physical phone call on hold. This feature is currently only available for Yealink phones.

• DND: Wazo Platform 20.11 API offers a new presence information: whether a user is on DND mode or not. This information can be changed either from a Wazo Platform API or from a physical phone.

Technical features​

• Asterisk: Asterisk was upgraded to 17.6.0.

Ongoing features​

• SIP lines and trunks: We are currently rewriting the SIP configuration API to match PJSIP options and be multi-tenant.

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 20.10 release.

Technical features​

• Asterisk: Asterisk was upgraded to 17.5.1.
• Multi-tenancy: We have improved the consistency of the database for multiple tenants. User credentials will now get deleted from the database after the tenant gets deleted.

Ongoing features​

• SIP lines and trunks: We are currently rewriting the SIP configuration API to match PJSIP options and be multi-tenant.

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

See you at the next sprint review!

Hello Wazo Platform community!

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

New features in this release​

• WebSocket: A new ping/pong command has been implemented in the Wazo WebSocket. This allows clients to detect more easily when the network connection with the server is interrupted.

Technical features​

• Asterisk: Asterisk process priority has been changed to realtime priority. This increases stability and voice quality when the server is under load.
• Performance: We have removed the use of encryption for internal HTTP communication between Wazo components. Encryption now only happens when Wazo is sending/receiving data from the outside world.

Ongoing features​

• Directories: We are adding a GraphQL API in wazo-dird to reduce the number of requests and improve performance.
• SIP lines and trunks: We are currently rewriting the SIP configuration API to match PJSIP options and be multi-tenant

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 20.08 release.

New features in this release​

• Calls: Wazo Platform is now able to emulate the pressing of DTMF keys via a REST API call. This makes remote-controlling a physical phone more transparent.
• Presences: In Wazo 20.08, the presence status of users takes into account the multiple channels for the same line to determine its state.
• Directories: In Wazo 20.08, reverse lookup will search through conference numbers. While not very useful when an incoming call arrives, it allows interrogating the system to know "what was that number I talked to the other day?".
• Provisioning: We have improved the documentation about physical devices that are supported by Wazo Platform. You can see the new version here: https://wazo-platform.org/uc-doc/ecosystem/supported_devices. This list is auto-generated, which makes it easier to maintain over time and to keep in sync with what the provisioning plugins can do. Let us know what you think!

Technical features​

• Asterisk: Asterisk was upgraded to 17.4.0.

Ongoing features​

• Performance: We will continue removing the use of encryption of internal communication between some Wazo components
• Directories: We are adding a GraphQL API in wazo-dird to reduce the number of requests and improve performance.
• SIP lines and trunks: We are currently rewriting the SIP configuration API to match PJSIP options and be multi-tenant

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 20.07 release.

New features in this release​

• Phones: Yealink phones now synchronize the DND status of phones with the DND status of Wazo. Before Wazo 20.07, the phone had its own independent DND status, leading to calls being rejected without having set the DND option in Wazo.
• Incoming call: An incall accepts a new parameter to configure a greeting sound played before forwarding the call to the destination.

Ongoing features​

• Performance: We will continue removing the use of encryption of internal communication between some Wazo components
• Directories: We are adding a GraphQL API in wazo-dird to reduce the number of requests and improve performance.
• SIP lines and trunks: We are currently rewriting the SIP configuration API to match PJSIP options and be multi-tenant

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 20.06 release.

New features in this release​

• Call logs: The API for call logs now returns two destination names: the one that was dialed and the one that answered. This is useful when a call was forwarded to another number, in order to know who forwarded the call to whom.

Technical features​

• Performance: We have removed the use of encryption for internal communication between some Wazo components. This results in some performance improvements, while keeping data secure: all communications to and from the outside of the Wazo Platform still use HTTPS.

Ongoing features​

• Performance: We will continue removing the use of encryption of internal communication between some Wazo components
• Directories: We are adding a GraphQL API in wazo-dird to reduce the number of requests and improve performance.
• SIP lines and trunks: We are currently rewriting the SIP configuration API to match PJSIP options and be multi-tenant
• Phones: We are working on synchronizing the DND status of phones with the status of Wazo, to avoid having two kinds of DND, one on the phone and another in Wazo applications.

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 20.05 release.

New features in this release​

• Phones: The DECT phone Yealink W80B can now be auto-provisioned with Wazo.
• Mobile applications: Wazo Platform 20.05 now accepts a new kind of token for Apple Push Notification service (APNs): it allows receiving chat and voicemail notifications on a mobile application. In previous versions, it was only possible to receive VoIP notifications from APNs.
• Conferences: Wazo Platform 20.05 offers new events for applications: they are notified when a conference participant starts or stops talking.
• Users: The bulk creation of users has been improved to be able to assign WebRTC lines to new users.
• SIP transports: SIP transports can now be configured using an API to leverage all possible fields of the Asterisk configuration.

Bug fixes​

• Directories: Directory lookup in Office365 now return more than 10 results.

Technical features​

• Documentation: The Wazo Platform documentation has moved from https://documentation.wazo.community to /uc-doc. Links to the former documentations should redirect you to the latter documentation automatically.
• Asterisk: Asterisk was upgraded from 16.8.0 to 17.3.0.
• Performance: We are in the process of removing SSL between services running on the same host, using plain HTTP instead.

Ongoing features​

• SIP lines and trunks: We are currently rewriting the SIP configuration API to match PJSIP options and be multi-tenant
• Phones: We are working on synchronizing the DND status of phones with the DND status of Wazo, to avoid having two kinds of DND, one on the phone and another in Wazo applications.

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 20.04 release.

New features in this sprint​

• WebRTC: We have added two new settings for WebRTC in the setup phase of Wazo Platform: WebRTC needs to discover the IP address of the two phones trying to communicate. For this, it uses the ICE protocol, exchanging the different IP addresses of the two hosts. However, for a host to know its public IP address, it needs to ask this information to a third-party service via the STUN protocol that is designed specifically for this. The two new settings allow 1) to enable the ICE protocol for exchanging IP addresses and 2) to specify the address of the third-party STUN server. Until now, those settings needed to be set after the setup phase in order for WebRTC to work correctly.
• Groups: In some cases, when calling a ring group, when one member answers the call, the other members would see a "missed call" on their phone. In the context of a ring group, this behavior is undesirable. We added an option to configure the behavior when a member of a ring group answers a call.

Bug fixes​

• Scalability: we have removed an internal cache from wazo-auth that prevented wazo-auth to be load-balanced: in some cases, a new tenant was not visible in one instance of wazo-auth, resulting in an "Unauthorized" error.
• Directories: Until Wazo Platform 20.04, when configuring physical phone directories, the administrator needed to restart wazo-phoned manually to apply the changes. In Wazo 20.04, the changes are applied automatically.
• Call quality: We have backported a patch from Asterisk 16.9.0 release candidate, preventing the audio playing static when using TLS/SRTP, possibly including WebRTC calls.

Technical features​

• SIP lines and trunks: We have added APIs to configure global PJSIP settings that will be used for all SIP lines and system-wide settings that will help configure Asterisk correctly for SIP calls.

Ongoing features​

• SIP lines and trunks: We are currently rewriting the SIP configuration API to match PJSIP options and be multi-tenant

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 20.03 release.

New features in this sprint​

• Calls API: Until now, a user placing a call could only ring one of its lines to place the call. A user may now ring all of its lines at once, without having to indicate which line should ring.

• Calls API: Until now, a user placing a call always had to answer the ringing line before the call was actually being placed. A user may now ask to auto-answer the call, so that the call is placed directly. In this case, the user would hear the ringback tone directly in his headphones or phone speaker.

• Calls events: Until now, when a call was answered, there was only a call_updated event sent. This event was not detailed enough to distinguish if the call was answered or if something else happened. This release adds a call_answered event, so that applications can know precisely when a call was answered.

Bug fixes​

• Function keys: BLF for DND and call forwards are now fully functional. BLF (Busy Lamp Fields) are small physical LEDs indicating on a physical phone whether the feature (e.g. Do Not Disturb) is currently activated for this phone.

Technical features​

• Asterisk: Asterisk has been upgraded to version 16.8.0

Ongoing features​

• SIP: We are currently changing the SIP configuration API to match the PJSIP configuration

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 20.02 release.

Security fixes​

• A security issue has been fixed that allowed the database of the engine to be accessed remotely when the following conditions were met:

  • Engine configured as a slave
  • Engine installed using ansible
  • Engine in version 19.12 to 20.01

  If your installation matches all of these conditions you MUST upgrade or execute this script on your engine.

New features in this sprint​

• Phones: We have added a provisioning plugin for Fanvil X Series phones, supporting 12 new phones models.
• REST API: A new REST API has been added to mute or unmute an arbitrary call. This allows a better control of physical phones from the REST API.
• Mobile applications: Two new kinds of push notifications are sent to FCM (Android) or APNS (iOS) when a call has been answered or cancelled from another line than a mobile line. This allows a better handling of calls for mobile applications developed for Wazo Platform.

Technical features​

• REST API: We have allowed some of our services to serve the REST API using HTTP instead of HTTPS. This will allow us to remove any unnecessary encryption for communication within Wazo Platform.

Ongoing features​

• SIP: We are currently changing the SIP configuration API to match the PJSIP configuration
• Class 4: We are still improving the new blocks in Wazo Platform to handle more calls and improve security. Kamailio is the core of those new features and serves as a Session Border Controller (SBC) and SIP router to multiple Asterisk instances.
• Phones: We are improving provisioning for Yealink phones in a NAT environment.

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

See you at the next sprint review!