V20 Update 9 Alpha - Web Client Gets a New Look

[Guillaume Bourgeois]

…

Terrible is a bit harsh, its not that much different.. the new lick of paint looks very nice - stick it in dark mode and its easier on the eyes.

First, with you, things went well. People are so resistant to change, it’s crazy.

Regarding the web client, I really like the new layout they introduced for the call forwarding menu (profile management). It feels much more user friendly in my opinion.




On the flip side, I’m less fond of the web dialer’s visual design. The default display of recent numbers directly on the dial pad throws me off, though it’s probably just because I wasn’t expecting it.



No offense to the designers, but it feels more like a calculator interface, with round number buttons and a framed display area.




I preferred the previous dialer, but the new theme isn’t dysfunctional. I just need a bit of time to get used to it.

…

[…] but I feel it a bit "over-sized" compare to the old one.

View attachment 51399

I agree that the width of the left-hand menu could be slightly reduced without affecting its content scaling, to free up some space on interactive pages, though the overall impact would be minimal.

—

It is a bit like a man who is not particularly old, but already rich in « wisdom and experience », deciding to dye his hair for a touch of youth.

@N_G


(Edit: On second thought, I am not entirely sure this is the best way to make my return to the forum. … …. I think I’ll go hide now ! )

 

[N_G]

it's an improvement indeed send it to me

 

[Bodart]

Has anyone experienced API issues with Update 9?

Since the update, I haven’t been able to access ‘Voice & Chat’ or ‘Outbound Rules’. I keep getting a 500 error.

I also get the same 500 error when sending a direct GET request for the trunks.

 

[Guillaume Bourgeois]

Has anyone experienced API issues with Update 9?

Since the update, I haven’t been able to access ‘Voice & Chat’ or ‘Outbound Rules’. I keep getting a 500 error.

I also get the same 500 error when sending a direct GET request for the trunks.

I noticed several changes in MyPhone and xAPI behavior that required adjustments on my side.

First, I observed changes in MyPhone, specifically in the structure and/or payload of the Protobuf messages exchanged through /MyPhone/MPWebService.asmx. I had to dig quite a bit to fully understand the changes and adapt my scripts to the new message format and serialization behavior, although things may still evolve over time. Let's just say it was not exactly straightforward.

I also noticed a change in how voicemail audio files are delivered client-side. They are no longer exposed through temporary blob: object URLs, but are now returned inline as Base64-encoded Data URIs, for example data:audio/wav;base64,....

As a result, any logic that previously relied on extracting or resolving blob: URLs now needs to handle embedded Data URI payloads directly.

I also noticed a change in how requests must be constructed when calling /xapi/v1/Trunks and /xapi/v1/OutboundRules, as both endpoints appear to be affected by the same behavior.

More specifically, the handling of the $select parameter seems to have changed. Requests that use percent-encoded commas (%2C) inside $select are no longer interpreted consistently, and the API now appears to expect a literal comma-separated field list instead.

Because of this, query construction needs to be adjusted so that commas inside $select are not encoded, and the parameter is sent as a plain comma-delimited list.

I do not know whether this behavior is intentional or whether it may change over time.

 

[Guillaume Bourgeois]

@N_G

If I may share some constructive feedback:

On the Office Hours configuration page, could the side menu listing the department names be made resizable by drag and drop?
Department names can sometimes be quite long and do not fully display within the current layout.

In my screenshots, I replaced the actual names with random characters while keeping the same character length.
Names that are too long are simply truncated and replaced with "..." or, when there are no spaces in the name, they are just cut off.








The naming convention we use, particularly in multi-site environments running on the same 3CX system, is as follows:

Office Name - Department

For example, in the case of car dealerships, using fictional names for illustration:

CHEVROLET LAWRENCEVILLE - USED CARS

As a result, when we need to modify the office hours for a specific department within a specific office, the full name is often truncated due to the limited space available. At the moment, the workaround is to inspect the HTML in order to identify the correct entry, which is not very practical.

Are we the only ones experiencing this issue?
It is possible that we are simply pushing the “Department” field a bit too far.

Of course, using abbreviated names would be a possible workaround. That would be functional, but since the Department Name field allows up to 50 characters, we naturally tend to use clear and descriptive names.

To better illustrate the desired enhancement, I also created a mockup showing the expected functionality.

That being said, if we are the only ones experiencing this “issue,” I fully understand that adjusting the layout would not necessarily make much sense. I am simply throwing the idea out into the 3CX universe, just in case.

Here in Quebec,Canada we even have an expression for that:
If my request gets accepted, I am going to buy myself a 6/49 ticket.
I will let you look up what that means, if you are curious.


** MOCKUP : This functionality does not exist; it is a demonstration of a desired feature. **
​

 

[ThomB_3CX]

@Bodart sending you PM

 

[RoryJ]

Many thanks for a superb update, we love the new interface and think our customers will too. It's very sleek and "sharp" looking compared to the .8, like comparing a Yealink T7/8 series phone to a T4/5. I know some customers will immediately make use of the cumulative ringing in queues as soon as this goes to release.

One thing I did notice, maybe we got unlucky but the update wiped out our entire company phonebook (I was able to restore the entries from a .8 backup). Personal phonebook entries weren't affected.

 

[dhill835]

Is anyone having an issue with Click to Dial in Microsoft Edge after update?

 

[N_G]

Many thanks for a superb update, we love the new interface and think our customers will too. It's very sleek and "sharp" looking compared to the .8, like comparing a Yealink T7/8 series phone to a T4/5. I know some customers will immediately make use of the cumulative ringing in queues as soon as this goes to release.

One thing I did notice, maybe we got unlucky but the update wiped out our entire company phonebook (I was able to restore the entries from a .8 backup). Personal phonebook entries weren't affected.

Thank you for the nice feedback! We will check it out re the phonebook, I wonder if it could be a rights issue, I.e. maybe a user changed role and could no longer view the entries?

 

[RoryJ]

Thank you for the nice feedback! We will check it out re the phonebook, I wonder if it could be a rights issue, I.e. maybe a user changed role and could no longer view the entries?

You're welcome, thanks for the good work.

This was on our main NFR which is the only instance we've applied the update to. System owners couldn't see the entries and when I checked they had disappeared from the backup. I don't see anyone else has mentioned it so maybe just us.

 

[dhill835]

Is anyone having an issue with Click to Dial in Microsoft Edge after update?

I had to remove webclient at end. https://xxxx.xx.3cx.us:5001

 

[ThomB_3CX]

@dhill835 yes removing /webclient at the end will fix the issue.
We have already fixed this from our end to keep backwards compatability for you, but yes removing /webclient is the quick fix here

 

[patrickb_de]

I assigned the trunk to a department and set up a holiday for that department. When I call a number from this trunk, it correctly routes me to the holiday prompt. However, after the prompt, the call is not terminated. Instead, it continues to the normal destination defined for that number.

For users, this behavior can be a bit confusing. However, for departments, queues, ring groups, and IVRs, it is actually beneficial because it provides more flexibility.

It allows administrators to define additional routing steps after the holiday prompt, in case the customer wants the call to continue instead of being terminated. For example, routing the call to an external number for "emergency" calls or to a voicemail to leave a message.

 

[Corsin]

For users, this behavior can be a bit confusing. However, for departments, queues, ring groups, and IVRs, it is actually beneficial because it provides more flexibility.

It allows administrators to define additional routing steps after the holiday prompt, in case the customer wants the call to continue instead of being terminated. For example, routing the call to an external number for "emergency" calls or to a voicemail to leave a message.

Okay, so this is intended behavior?
If so, we will have to make a bit of an effort once the update releases to make sure the holiday destination of every queue etc. on every instance is set correctly. Because, as stated earlier, we always set that to the holiday script and not to end call – as in most scenarios, we want it to end after the prompt.

As for how we will handle it for numbers directly routed to users, I'm not quite sure yet. Currently they are excluded from the holiday prompt if no time-based status is configured, which won't be the case anymore.
I still wonder how I can exclude a number part of the trunk from playing the holiday prompt.

 

[rjdalejr]

I agree, filtering the recording list by date is important. Also it would be nice to be able to see the durations.

one more thing we can now hear the recording directly from the UI which is GREAT!

but the filter by date is gone any news about it? to filter recording via dates is very important

 

[PBX128]

I still wonder how I can exclude a number part of the trunk from playing the holiday prompt.

Holiday message is only played when there is an holiday activated in department. If you put those users in a different department without holiday entry, they can be reached

 

[JoshuaM]

It would be great if the color of the dialer can be adjusted via user settings. Dialer being in blue after being so used to white or black for years is probably something that many dont want to change (including me )

 

[WebNeuch]

Hello, I accidentally migrated to the alpha version. I want to migrate to another machine, but it's impossible with the ISO. The backup is too recent compared to the ISO version. Do you have the official ISO for the alpha version?

 

[bitn2]

Hello, I accidentally migrated to the alpha version. I want to migrate to another machine, but it's impossible with the ISO. The backup is too recent compared to the ISO version. Do you have the official ISO for the alpha version?

There is no ISO for that. Just install, upgrade to alpha and restore.

 

[UCMUserAZ]

Should we see the Beta build offer? Mine says up to date, but only showing 670 Alpha installed. Thanks in advance!