Compass release 2023a, bundled with Studio 1.4, contains improvements on a wide variety of Compass features, and takes care of a few long outstanding bugs.
Compass 2023a highlights
On the Compass side, the REST API now has full support from prompt management, including replacing audio files. This adds new integration opportunities for our partners.
One of the older issues on Compass relates to the way that caller-ids are handled in case of attended transfers. With this release, Compass will now update the phone’s display of the receiving party with the newly connected party.
For phone provisioning, the ‘call waiting’ setting can now be set company-wide (for a specific phonetype). We have furthermore simplified the provisioning setup by removing some little used features like adjusting volumes. As always, you can use custom provisioning for any custom wishes you may have on provisioning.
Following a few disruptions, we have again improved the redundancy setup of Compass and its behavior during datacenter fallout.
More new things
This release contains a fully working WebRTC setup, although it’s considered beta at this point. Starting with 2023a, you are able to connect with and dial via Compass with a browser-based softphone. We are now working on integrating this into our product suite, like Bridge.
On the Studio side, you are now able to create queues within the dialplan editor, as well as editing all queue properties with a brand-new modern interface. You can even manage queue agents from the same interface. We plan on expanding the dialplan editor more and more in future releases, so that you don’t have to go back and forth anymore.
The Prompt API is an addition to our REST API, making it possible to create, read, update and delete prompts by external applications. Use the Swagger interface to discover the new endpoints:
- Get prompts via
- Create prompts via
- Modify prompts via
PATCH /prompt/:id(or use PUT)
- Upload/download audio via
The new operations have been added to Compass API v3; the API stays fully backwards compatible with the previous version.
CLI for attended transfers
After an attended transfer, the caller id is now updated correctly, to indicate the newly connected party of the call. For example, if a secretary transfers an external call to a Compass user, the Compass user now sees the external number after the transfer is completed.
Call waiting is inherited
If you configure ‘call waiting’ on a per-phonetype basis in Compass, and not overwrite it in the per-phone configuration, it will now be successfully inherited.
WebRTC is now available as a technical-preview. Using Studio (or API), you can create a Compass phone of type ‘Generic SIP Softphone with call control’. Then, with any SIP-over-websockets library (for example, sip.js) you are able to dial out and receive phone calls on Compass. Technical resources are available for our partners.
We have improved the speed and stability of the platform’s ability to run on a single datacenter, in case of major disruptions.
Compass 2023a does no longer support INI-style provisioning for SNOM phones. The checkbox for XML provisioning is no longer available in Studio – it’s always enabled. We have migrated all connected phones to XML already, so this will have no impact for customers.
A few settings have been removed from the SNOM provisioning, as they are barely used and clutter up the configuration interface. The removed settings are:
- Headset sensitivity
- Earpiece sensitivity
- Speaker sensitivity
- Only indicate Call waiting visually
Please refer to previous mails for implementation details.
After long testing with various customer environments, we are now rolling out our ‘fair queue’ patches to all customers. This makes sure that callers are being handled by agents in a fair order, ie. callers are handled in the order they entered the queue. This only affects certain rare conditions in call centers.
Studio 1.4 enables the inline creation and editing of queues in the dialplan editor.
We are aware of the following issues. Please don’t open new support tickets for them.
- GL-2868 – Semi-attended transfer generates an extra call recording
- GL-3376 – Large XMPP rosters are shortened by the platform
- GL-3847 – User call forwards are not followed in accordance with the availability status