In WMS 6 we updated the kernel version of the system and its core components. This means state-of-the-art stability, reliability, and security for your customers’ systems, better and faster performance, more efficient use of CPU and resources, and many other improvements.
In this blog article, you will learn what’s new in the WMS version 6.02. In particular, we will talk about major UX/ UI updates of WMS GUI, Veesion integration with x-hoppers, new APIs, meeting scheduling in Outlook calendar, and much more. The full changelog is available at by this link: https://wildix.atlassian.net/wiki/x/AQDIAw
...
With this release we add two new buttons to the Dialplan page: Expand all and Collapse all, allowing you to display or hide all the details of a certain Dialplan rule.
...
Onboarding new users becomes easier: from now on, when a user downloads the app following the link from the welcome email, the domain and extension parts fields are already filled out for them.
...
There are certain cases when we want to bypass the PBX when placing a call and redirect certain outgoing calls to the native dialer, bypassing the PBX. For example, when calling emergency services.
In this version, we add a possibility for the system administrator , to enable the forwarding of calls to certain call forwarding for the specific called numbers to the native dialer. To enable this behavior, the system administrator needs to edit a custom config file on the PBX, listing the called numbers.
...
Imagine, you have an agent present in multiple queues. In case there are ringing calls in several queues, which one will be distributed to this agent? Before WMS 6.02, the distribution order in such cases was random. In WMS 6.02 we add a global Dialplan variable allowing the system administrator to control this behavior.
By After enabling the new behavior , the agent present in multiple queues will be sure to get the longest waiting call. The system will check system will be checking the waiting time in all the queues before distributing the call. As a result, an agent present in multiple queues will get the longest waiting call.
...
Read the documentation: https://wildix.atlassian.net/wiki/x/5h3OAQ
...
Microsoft 365 allows the usage of additional attributes to map different fields when importing users. We for the mapping of fields. In WMS 6.02 we introduce the new field extensionAttribute1-15 that you can use to sync Custom attributesmap custom attributes when importing fields.
...
For Google, additional data can be imported using the new Custom_* field. In addition, we We also added the possibility to sync language.
...
With this update, we improve the security of connections to an external MySQL DB. SSL connection is can be enabled via a custom config parameter. Read the documentation for more details: https://wildix.atlassian.net/wiki/x/Fh3OAQ
...
With this release, you can gain more control over what other system administrators are allowed to do on WMS. An example is unexpected charges due to license upgrades performed by one of the system administrators for certain users on the PBXin WMS.
Now you can restrict the ability to change the license type of users, using the new ACL “Can/Cannot” - "Change license type". An example when this permission could be useful, is unexpected charges due to license upgrades performed by one of the system administrators for certain users on the PBX.
Remember to combine this restriction with another ACL that was already there - “Can/Cannot” - "Add and remove users". Using both of them gives you the level of control you should have.
...
Historically, g729 was set as the number one priority for codecs, for the one simple reason – it saved saves bandwidth. Nowadays, cutting bandwidth is no longer a concern for most customers. This is why we’re setting updating the new default priority for codecs in the SIP trunk configuration dialog: g711 which provides superior audio quality goes first, g729 is moved to the end of the list.
The new trunk priority is effective for newly created trunks, or after re-saving trunk an existing trunk’s settings.
...
SMS from Collaboration 💬
With this release , we improved improve the behavior of the “Standard SMS header”, which is set in the WMS - Fax/ SMS Server page.
...
Localization 🌎
Here are some localization updates, primarily for our customers in Spain and France:
...
Veesion AI camera monitoring software helps detect theft without human input. It analyses images coming through each camera, processes them, and assigns probabilities to each action the subject makes. Once the probability of theft exceeds a certain threshold, it can trigger an alert. The system can reduce theft by up to 60%, especially when used with on-floor headset systems.
On the other hand, x-hoppers is the complete retail headset communication system from Wildix for in-store messaging and intelligent retail support. It boosts in-store communication, and staff efficiency, and lets customers enjoy the best service possible, leading to increased sales and customer loyalty.
With the x-hoppers headset solution, all shop employees are connected to one voice channel, so they can tackle in-store tasks as soon as they arise. Check out the x-hoppers website to learn more.
| Easy html macro | ||||
|---|---|---|---|---|
| ||||
Useful links ⬇️
How to set up the integration between Veesion and x-hoppers: https://wildix.atlassian.net/wiki/x/AQA_Bg
...
Veesion integration with x-hoppers
...
Coming soon next in WMS 6.02 for x-hoppers:
Post footage from Veesion software to x-bees conversations
All interactions happening during the day over the x-hoppers system will be recorded and posted to x-bees so that they can be consulted and analyzed at any time.
x-caracal - Display of user status message
x-caracal is the light, agile, and integrated contact center analytics tool from Wildix. Learn more here: https://www.wildix.com/product/acd-stats-x-caracal/
In WMS 6.02 we’ve updated the real-time dashboard of x-caracal with the possibility to see not only the agents’ real-time status but also their status messages.
...