Skip to main content

109 posts tagged with "development"

View All Tags

Wazo Platform 20.15 Released

· 2 min read
The Wazo Platform team

Hello Wazo Platform community!

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

New features in this release

  • Contact Center Stats API: The queue statistics have been improved and may now be aggregated by day or by month, to provide insights on a queue on long periods of time.
  • Contact Center Stats API: The begin and end time of the statistics are now timezone aware.
  • External application API: A new API has been added to configure external applications for users and tenants. This API can be used by an administrator to control how an external application will behave.

Technical features

  • Asterisk: Asterisk was upgraded to 17.8.1. This is a security release, so we strongly recommend you to update your Wazo Platform.

Ongoing features

  • Contact Center Stats API: We are working to expose all the statistics for queues and agents through REST API.

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

See you at the next sprint review!

Wazo Platform 20.14 Released

· 2 min read
The Wazo Platform team

Hello Wazo Platform community!

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

New features in this release

  • Contact Center Stats API: Wazo Platform 20.14 introduces a new HTTP API to retrieve statistics for calls received in queues. The statistics were collected but not available in any way since they were displayed in the web interface of Wazo 18.03.

  • Tenant API: A new API has been added to Wazo Platform 20.14 to easily retrieve resources that have been created along with a new tenant. Currently, this API exposes the PJSIP templates automatically created with the new tenant.

  • Phones: Two new phone provisioning plugins have been added to support Yealink T31G & T33G phones and Cisco 78XX.

Technical features

Ongoing features

  • Contact Center Stats API: We are working to expose all the statistics for queues and agents through REST API.

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

See you at the next sprint review!

Wazo Platform 20.13 Released

· 3 min read
The Wazo Platform team

Hello Wazo Platform community!

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

New features in this release

  • SIP lines and trunks: The SIP configuration API has been revamped to match the possibilities of the Asterisk PJSIP configuration file. The SIP general configuration has been removed in favor of a global configuration template for each tenant. Here is an article describing the changes done on lines and trunks. https://wazo-platform.discourse.group/t/wazo-20-13-how-trunk-works-now/567

  • SIP Templates: SIP endpoints (lines and trunks) can now inherit their configuration from templates. If you want to assign a given configuration to multiple lines, you can create a template with that given configuration and assign it to all the lines you want. If you ever decide to add a new option to that group of lines or if you wish to rollback that change, you can do it using the template. No more clicking on all users. If multiple templates are applied, for example "global", which is the SIP configuration that is meant to be used on all endpoints of a tenant, and "webrtc", then all options from the "global" template are used, then all options from the "webrtc" template are applied over the "global" template. Finally, the endpoint options will be applied over the options coming from the templates. This makes line endpoints very lightweight containing only a caller id in most cases.

  • Permissions and ACL: wazo-auth now makes it possible to remove permissions from a policy. This allows an administrator to create a new policy to remove permissions for a specific group of users instead of re-writing and maintaining a whole policy without the undesired permission.

  • Menu revamp: The menu as been revamped in wazo-ui.

  • Global settings: A global settings section has been added in wazo-ui to configure settings that are shared amongs all tenants.

  • Group members: Extensions can now be used as group members in wazo-ui

Bug fixes

  • Schedules: Schedules with no timezone defined prevented the call from being distributed.

Documentation

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

See you at the next sprint review!

Wazo Platform 20.12 Released

· 2 min read
The Wazo Platform team

Hello Wazo Platform community!

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

New features in this release

  • Conferences: until Wazo Platform 20.12, the only way to create conferences was to ask users to dial a specific extension pointing to a conference room. It is now possible to merge two or more existing calls together to create what we call an adhoc conference.

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

Bug fixes

  • Outcalls: if a user had set a custom music-on-hold on their account, the default system music-on-hold was being played anyway when the user placed an outcall on hold. Now it is the correct one that is used.

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!

Wazo Platform 20.11 Released

· 2 min read
The Wazo Platform team

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!

Wazo Platform 20.10 Released

· One min read
The Wazo Platform team

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!

Wazo Platform 20.09 Released

· 2 min read
The Wazo Platform team

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!

Wazo Platform 20.08 Released

· 2 min read
The Wazo Platform team

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!

Wazo Platform 20.07 Released

· 2 min read
The Wazo Platform team

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!

Wazo Platform 20.06 Released

· 2 min read
The Wazo Platform team

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!