V18 Beta 2 - A Step Closer to Final Release

Status
Not open for further replies.

N_G

Founder
Joined
Jun 6, 2006
Messages
4,866
Reaction score
9,339
V18 Beta 2 has just been released! Following your feedback, this Beta should be good to go as a Release Candidate in the coming days. Update to Beta 2 today for more bug fixes, including the recent Hotfix.

Beta 2 Fixes​

  • Fixed issue with transfers causing no audio.
  • Fixed recording and renegotiations.
  • Fixed deadloc...
 
Last edited by a moderator:
Hopefully means we will soon see a Windows release!
 
  • Like
Reactions: MH_INDUS
We decided to upgrade our internal production system to this release, keeping a snapshot of before the upgrade handy and on standby. The upgrade (stretch to buster and V18) went without any issues. It took about 10 minutes. We like the Management Console. The new windows client is a lot different, but it's growing on us. The click to call works on some sites, while others it does not. We're hoping that gets resolved in future releases. I'd say it's a success from what we've seen so far.
 
Hi, 2 Question about the new Client:
1. Will there be a way to provision the Client in ANY WAY on a Windows AD Domain? It would be very important! Or - if this isn’t a way: PLEASE add a command, I can run in netlogon for provisioning on Login!!!
2. Will there be a way to display Contacts from a ODBC Database Source?
Thanks!
 
  • Like
Reactions: Shawfire Solutions
Thanks for the update. Are we getting Helpdesk in the final release?
 
Is this going to fix any issues with the Teams Sync?
Followed the configuration with the manual, can see in the logs that PSTN connection is coming from 365 to 3cx pbx, but Teams admin page keeps showing this:
1627549049257.png
 
Is this going to fix any issues with the Teams Sync?
Followed the configuration with the manual, can see in the logs that PSTN connection is coming from 365 to 3cx pbx, but Teams admin page keeps showing this:
View attachment 23240

the page is 100% showing you all is OKEY, the TLS is connected and both systems are exchanging keep-alive messages. The red part in the front may be misleading but you have 0 calls, so Teams cannot measure the effectiveness of the calls made via the link. But this is more call analytics then connectivity
 
  • Like
Reactions: Evolute IT
Thanks for the update. Are we getting Helpdesk in the final release?

no, this will be for a later stage. The feature set for the initial release, after we added MS Teams Direct Routing, is now complete. After the final release, we will set sail to integrate the helpdesk system into 3CX.
 
Does this update fix the issue with teams to teams transfer showing 403 forbidden?
 
There are two types of transfers in the Teams client. To my knowledge is the "blind" transfer now working.
The attended one not yet as it is a bit of a peculiar way how this is handled in Lync/Teams Direct Routing.
 
  • Like
Reactions: Evolute IT
There are two types of transfers in the Teams client. To my knowledge is the "blind" transfer now working.
The attended one not yet as it is a bit of a peculiar way how this is handled in Lync/Teams Direct Routing.
Thanks Stefan looking forward to the final release
 
I like to make a small extension to my previous posts reg. transfers from and to teams.

From a Teams users point of view:
you can transfer a call to a 3CX user blind and attendant.
For attendant to work, the 3CX user must allow multiple calls within the extension forwarding rules as
it creates a second call to the extension while the first leg is still established.

What is not working is to transfer a call to another Teams user currently. This will be mostlikeley possible with U1.
 
  • Like
Reactions: Evolute IT
we have been testing the V18 since it came out, and now that it supports MMS we have noticed one thing utilizing flowroute. if you send more than one photo per MMS, you only get the first photo and the rest are stripped or not delivered. curious if receiving multiple pics in one message would be supported in the future?
 
I tested 3CX V18 Beta 2 since very intensive with some colleagues since yesterday in the evening.

I just wanted to let you know some things:

The users are still missing this big Q at the top of the clients to log in and out from the queue(s). Atm it is only possible with the dropdown on the top left corner or in the view of each queue. In my opinion there are some settings, that should be available more easier. One of them is the Q button that should get to the top bar again, the other thing is the audio/video settings that could also be available on the top or something like a bottom bar. Maybe the little Q in the teams view could also be used for it? Would be better than now, but the thing is, that this one is really small.

With a call in progress, it is sometimes necessary to hide the dialer so that you can click something behind it. In V16, this is possible via the telephone handset button, which was fairly intuitive. Now there is only an X and an X like this does not look like minimising, but rather like ending/closing. Wouldn't it be easier to place an arrow pointing up or to the right here to make it clear that you can only "move" it and bring it back again?

The different views, for example in the panel or in the teams, are also very hidden via the small drop-down menu in the top right corner. I have to explain all this to our employees because otherwise they won't find it, I know that for sure now and I don't think it will be any different in other companies. With another small bar next to the menu bar on the left side or the top side, it would be much easier to find, which is how it is done in the current web client.
 
Where did the Phone / App Options go in v18? It included Firmware Settings with an option to clean old firmware, and Configure Queue Ringtones with the option to allow custom ringtones.
 
Where did the Phone / App Options go in v18? It included Firmware Settings with an option to clean old firmware, and Configure Queue Ringtones with the option to allow custom ringtones.
Phones > Options (blue button on the right of the toolbar)
 
  • Like
Reactions: accentlogic
Does anybody know how to install v18 beta 2 on Pi4 by new installation?
Following the actual 3cx manual installs raspian based on buster, with latest v16 pbx utilizing this command

wget https://downloads-global.3cx.com/downloads/misc/d10pi.zip; sudo bash d10pi.zip

Afterwards no update option is offered from the WebUi, whereas customers who have older Installations with stretch would have option to upgrade OS to buster and get v18 alpha.
 
Does anybody know how to install v18 beta 2 on Pi4 by new installation?
Following the actual 3cx manual installs raspian based on buster, with latest v16 pbx utilizing this command

wget https://downloads-global.3cx.com/downloads/misc/d10pi.zip; sudo bash d10pi.zip

Afterwards no update option is offered from the WebUi, whereas customers who have older Installations with stretch would have option to upgrade OS to buster and get v18 alpha.
See here:
https://www.3cx.com/community/threads/v18-beta-1-gearing-up-for-release.82821/post-386473
 
we have been testing the V18 since it came out, and now that it supports MMS we have noticed one thing utilizing flowroute. if you send more than one photo per MMS, you only get the first photo and the rest are stripped or not delivered. curious if receiving multiple pics in one message would be supported in the future?
We will be making improvements in this area for V18 Update 1, which will also address a similar behavior that exists with incoming Facebook messages.
 
Status
Not open for further replies.

Forum statistics

Threads
112,149
Messages
590,964
Members
165,170
Latest member
SupportRock