V18 Alpha 5: New Native Desktop App

[GiannosI_3CX]

Transferring calls / Line keys:

With the V18 Desktop App, attended transfer calls are working as expected. Only thing is, one can not toggle between Line 1 and Line 2. The second line is only visible while dialling the transferring number, once connected the line option disappear. From here, one can either transfer the call or hang up. It is not possible to switch/swap between the two active calls. This is possible with the current Windows V16 phone

1. Talking on Line1 to 303 | 2.Click Att.Transfer & enter destination| 3. only new destination is visible
View attachment 22855View attachment 22854View attachment 22853

Two lines are only visible when a new + New Call is made. But from here one can not connect/join Line1 with Line 2. Although in this scenario, one can switch Hold from Line 1 to Line 2, just not transfer them together, grrr.

View attachment 22856

It's in our ToDo list

 

[Obeya Digital Solutions]

I miss the BLF buttons in the Electron app. That was brilliant in the softphone. The user can define the BLF but only use it on a deskphone. It makes perfect sense to integrate these buttons as in the softphone.
Will this still be integrated in the Electron app?

 

[Obeya Digital Solutions]

Sorry....I've found the answer.

 

[Constantinos Constantinou]

@Obeya Digital Solutions now that you have the answer we hope that all users will be pushed to start using the Desktop App

 

[PhoneOnline]

We are willing to update to V18 Alpha 5. But using an Alpha-version in production does not give me a trusted feeling..

 

[PhilK]

I didn't choose the option "allow chat" but I'm still able to start a chat and a group chat on the "+" Button in the windows client.
I still hope that you will not keep this uggly looking interface for webclient and windows client!!

 

[PhilK]

In the Audio/Video Settings is no options for the ringtone. We're using the sennheiser D10 with an integrated speaker for ringtone in the base station. Please add this option again! At the moment the notebooks loudspeaker AND the headset station rings at the same time. That's not a good solution. Works better in V16

 

[GiannosI_3CX]

I didn't choose the option "allow chat" but I'm still able to start a chat and a group chat on the "+" Button in the windows client.
I still hope that you will not keep this uggly looking interface for webclient and windows client!!

Verified, eventhough chats removed the "+" button still appears. It will be addressed and fixed.

 

[aschildmeyerSTR]

I haven't been able to play around with the new build yet. For the text messaging improvements is there more error handling being put in place? For example my users sometimes text landlines or they text numbers that are wrong. Looking at the Telnyx API I can see where it gives off error codes for these different scenarios that do not get relayed back to the user and the user just thinks it was sent successfully. Maybe it's super hard because all of the SMS capable vendors? Just wondering if we are seeing an improvement on that front in V18?

 

[PhilK]

Some questions:

1. Will you change the current UI for webclient and windows app from the current alpha 5?
2. Windows App: Would it be possible to let the user decide if he wants to use the seperate dialer or a dialer as it looks now in v16 webclient that is not seperated?
3. Will you make it possible to take remote control (CTI?) from webclient to Windows App or 3CXphone for windows? At the moment it is only possible to do this from webclient and Windows App to the 3CXphone for windows, but not from webclient to the new Electron Windows App.
4. Will you go on with the 3CXphone for windows?
5. Is it possible to change the call list view for incoming calls forwarded to a ring group, that I can see better if the call was first on my extension or I just got it with the ring group? (Talking about call list v16 view)
6. Will you please add the big Q on the top right corner again to be able to log in and out from Queues fast?
7. Please add this CTI mode button back on the top right corner, too. ATM it is only available in the dialer and I think this is too hidden for many users.

 

[Constantinos Constantinou]

I haven't been able to play around with the new build yet. For the text messaging improvements is there more error handling being put in place? For example my users sometimes text landlines or they text numbers that are wrong. Looking at the Telnyx API I can see where it gives off error codes for these different scenarios that do not get relayed back to the user and the user just thinks it was sent successfully. Maybe it's super hard because all of the SMS capable vendors? Just wondering if we are seeing an improvement on that front in V18?

Hello @aschildmeyerSTR ,

Error messages are ported properly to the agents, and more specifically in my case that I tried the landline in US, I get the following error message.

40012: Invalid messaging destination number, The destination phone number was deemed invalid by the carrier.

Give it a try and let me know in a private message if you are experiencing something differently.

 

[DanielGarner]

Hello,

Where a user is an agent in multiple queues and receives a queue call back the queue making the callback doesn't seem to be present in V18 anymore.

In V16 windows desktop softphone, current Android apps the caller ID pop up would show the name of the queue that the callback was for:

• QCB:07825xxxxxx:IT Service Desk

Using the version 18 Windows App or web client, it doesn't show that anymore:

• QCB:07825xxxxxx

We rely on that feature to give some personalised service, so it would be great to keep it in V18!

Thank you

 

[aschildmeyerSTR]

Hello @aschildmeyerSTR ,

Error messages are ported properly to the agents, and more specifically in my case that I tried the landline in US, I get the following error message.

40012: Invalid messaging destination number, The destination phone number was deemed invalid by the carrier.

Give it a try and let me know in a private message if you are experiencing something differently.

Awesome, I'll give it a try in v18 and see how it goes. Thanks for looking into it @Constantinos Constantinou

 

[RichB]

I just gave version 18 a try and it all seems very nice, my only suggestion would be to update the terminology from Whitelist/Blacklist to Allowed List/Blocked List.

 

[VoIPTools]

Would it be possible to get a phone-style "ringing" notification when a new chat request has been received and have it continue to "ring" (or beep) until someone answers the chat?

With all the "dings", "beeps" and popup notifications that come from teams and windows and every other application it is too easy to miss a notification. Our current chat application mimics a ringing phone and we no longer miss chat requests.

Alternatively, is there a webhook we can subscribe to so we can make our own notifications?

 

[VoIPTools]

I assume the existing 3CX Phone for Windows plugin architecture will be replaced with some form of REST API? How will we create client-side CRM integrations? Any guidance on what will replace the CallTriggerCmd.exe?

 

[Stephen Quam]

I am hoping we get an Alpha 6 or Beta 1 soon.

 

[Evolute IT]

I am hoping we get an Alpha 6 or Beta 1 soon.

Beginning of next week for Beta 1, if everything goes according to plan!

 

[raldridge]

Sorry, where I can download this alpha version?

 

[jcostlow]

You can download the alpha here: https://downloads-global.3cx.com/downloads/debian10iso/debian-10.9.0_1c40016-amd64-netinst-3cx.iso