Compass release 2023c contains a new Compass feature called Queue Cherry Picking to Extension and takes care of some regressions. Furthermore, we extended our REST API with 1 new API call and improved 4 others, introduced NextJS in our back-end and added several new firmware versions for both Yealink and Snom.
Queue cherry picking to internal extension
We extended the Queue cherry picking premium feature of queues. When enabled you could already cherry pick calls as a user via de API or via Bridge. In this release we added the possibility to cherry pick calls to an extension. One of the use cases is that this will enable routing calls in queues based on external info without manual intervention of an agent. This feature has been added to our REST API (see below). In the future we hope to add it to Bridge as well to cover other use cases.
The CallerID Name when using Queue cherry picking to Extension will be the original caller. To make the two cherry picking features consistent we changed the behavior of Queue cherry picking to User to show the CallerID Name of the original caller as well. Previously “Dialler” was shown.
Some parts of the Compass webinterface (Studio) are very old and hard to change. NextJS is a new component in the back-end which will help us with the transition to new usability and functionality features of Compass Studio. In the end this will make administrating Compass easier and faster.
In our 2023a release we changed the CLI for attended transfers. As a reminder: After an attended transfer, the Caller ID is now updated correctly to show the number of the original caller. Because the SIP headers were changed for this, in some cases this caused an MTU issue: the maximum size of packets became too large at certain customers. In order to fix this, we changed our SIP headers which now have “Topology hiding” enabled. This will reduce some headers in the SIP Invite message. Specifically, the Record-Route and Via headers often appeared multiple times in an Invite. We have reduced the number of instances of these headers to only one of each. The topology info itself is stored elsewhere so the packets have become smaller. NB: We will enable this functionality only after consulatation with our partners.
To make our API’s more efficient and needing less API calls to retrieve certain information the fields userId and identityId have been added to:
To retrieve the current PBX a company is attached to the field pbx has been added to:
As mentioned before Queue cherry picking to internal extension has been introduced and added to:
Use the Swagger interface to discover these changes.
In 2023b when using multiple Music On Hold files in the Music On Hold element the appearance in Studio was broken. It looked random and non-aligned. A similar issue was found internally with the settings of a Call Flow Switch. We fixed both.
We’ve certified new firmware for the next Yealink phones.
- T40P: 220.127.116.11
- T41P: 18.104.22.168
- T42G: 22.214.171.124
- T46G: 126.96.36.199
- T41S, T42S, T46S: 188.8.131.52
For Snom we added: 10.1.159.12 for all models.
For Yealink we removed the next old firmwares:
- T41S: 184.108.40.206
- T42S: 220.127.116.11
- T46S: 18.104.22.168
For Snom we removed:
- D712: 22.214.171.124
- D715: 126.96.36.199 and 188.8.131.52
- D725: 184.108.40.206 and 220.127.116.11
See our Phone Support page for more details.
Finally, we also added the possibility for Snom phones to downgrade to cover certain scenarios in which you would like to revert to an older version. See our Admin manual -> Phones -> Editing for more info.
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