V18 Update 1 Beta: Fine-Tuning Teams Integration

[NickD_3CX]

Is there a way to have it compress outgoing Pictures on MMS? since many large carriers have a 1mb restriction, and gives an error. Most photos you will try to send from a smartphone will be larger.

We are exploring options on how to handle this, but we are aware of it.

 

[JohnGrenfell]

How to get V18 Update 1 Beta​

Try out V18 Update 1 Beta for Linux 3CX V18 on Debian 10 ISO or Windows.

So is this download (3CXPhoneSystem_18.0.1.214) a beta or the released 18 version? We want to upgrade to v18 on production and need to ensure it is not a beta release. It would be very helpful if the download was listed in the customer download portal section https://portal.3cx.com/customer/downloads

 

[SethTalley]

Continue reading the Original Blog Post.

Nick, how close is 3CX to MMS integration? I'm just a small clinic with a high availability problem (our clients are pregnant women who need to be able to page midwives) and the ongoing VoIP.ms DDOS attack has been problematic. We've got one published phone number and if our SIP provider can't be reached, neither can we.

Our SMS/MMS trunk is with a different provider. We can communicate via that number and could have texted all of our patients in dates, but we haven't used texting beyond a test phase because what we *really* need it for is easy, HIPAA-compliant (or defensibly compliant) exchange of images. If MMS was up and running this would have been much less of a crisis for us.

I'm just trying to figure out how to improve our availability for when this happens again and assessing all my options. Thanks.

 

[Wihan]

Did the Yealink headset integration make it into this update as was mentioned?

 

[Evolute IT]

Did the Yealink headset integration make it into this update as was mentioned?

Not yet

 

[StefanW]

how close is 3CX to MMS integration?

MMS support is already in the released version of V18 for Telnyx, Flowroute and Twillio.
Ensure that the WebHook URL set in the provider is V3 to enable the capability.

However, MMS and HIPPA compliance is something that will not go together due to the general nature of how those messages are sent and stored by the telcos in the process.

 

[JohnGrenfell]

@Nick Galea going around a little in circles here looking for information on a supported version V18 for Windows, current download is a beta. Will v18 be released or are you going straight to V18 update 1 for Windows and if so do you have a timeline or it's release?

Thanks.

 

[Evolute IT]

@Nick Galea going around a little in circles here looking for information on a supported version V18 for Windows, current download is a beta. Will v18 be released or are you going straight to V18 update 1 for Windows and if so do you have a timeline or it's release?

Thanks.

Windows will be v18U1 directly. Currently in beta but should be ready for release within 2-3 weeks (depending on how many things they add in it.)

 

[PhilK]

Is there already a release date for the final version of the first v18 update?

 

[VasilisV_3CX]

Hi @PhilK,

No date just yet, but we are working on it so it shouldn't be too long now.

 

[Rashid Raza]

@VasilisV_3CX,

What are the additional Features added in the coming update?

Can we get the 3CX Helpdesk/ticketing software?

 

[SteveITS]

What are the additional Features added in the coming update

https://www.3cx.com/blog/change-log/phone-system-change-log/

 

[Rashid Raza]

https://www.3cx.com/blog/change-log/phone-system-change-log/

And what about the 3CX Helpdesk/ticketing?

 

[ChrisC_3CX]

And what about the 3CX Helpdesk/ticketing?

The 3CX Helpdesk feature has yet to be implemented but it is on our roadmap. There's still no ETA for it.

 

[Gravité Managed IT]

Just wondering, has anyone tried to connect multiple 3CX PBXs (same customer, different locations) to the one Office365 subscription?

There is no issue when I have joined other vendors SBCs in to the one Office365 subscription so I am hoping that we are able to do the same with 3CX's SBC.

Also, being able to have a backup/HA 3CX server would require more than one 3CX SBC to be registered to Office365.

 

[StefanW]

@Gravité Managed IT
Yes, we have done this ourselves, however, it requires you to modify manually the scripts for this to work.

1)
You need two AAD applications for each location and then configure which users shall be synced into which 3CX.(Selected Users)

2)
You need to mod. the PowerShell scripts provided, as they only deal with a single 1:1 relation. The extension of your modification depends on many factors, do the locations also need different dial plan patterns (for example to cover US and UK per location), extension length, dial codes etc. The simplest version is to only generate a second Teams SBC and add it to the routing policy.

My advice, use the default for one location, check how it works and then mod. from there your config as you needed it. Please understand, this is a complex story, therefore 3CX'ssupport end with the default setup of the trunk.

 

[bgrattan]

Just checking in to see if V18 has a firmer release date. My predecessor upgraded FW on our Yealink T46s phones (3CX Windows V16) and I have been unable to update key programming on phones for several months now. I understand it has to do with HSTS and I understand that aspect. Any advice or guidance and an idea on the timeline for release is greatly appreciated.

Brian

 

[Evolute IT]

Just checking in to see if V18 has a firmer release date. My predecessor upgraded FW on our Yealink T46s phones (3CX Windows V16) and I have been unable to update key programming on phones for several months now. I understand it has to do with HSTS and I understand that aspect. Any advice or guidance and an idea on the timeline for release is greatly appreciated.

Brian

V18 is already released for Linux.

Update 1 is compatible with Windows, but it is a beta right now.

It should be released officially within a few weeks IMO.

 

[Gravité Managed IT]

@Gravité Managed IT
Yes, we have done this ourselves, however, it requires you to modify manually the scripts for this to work.

1)
You need two AAD applications for each location and then configure which users shall be synced into which 3CX.(Selected Users)

2)
You need to mod. the PowerShell scripts provided, as they only deal with a single 1:1 relation. The extension of your modification depends on many factors, do the locations also need different dial plan patterns (for example to cover US and UK per location), extension length, dial codes etc. The simplest version is to only generate a second Teams SBC and add it to the routing policy.

My advice, use the default for one location, check how it works and then mod. from there your config as you needed it. Please understand, this is a complex story, therefore 3CX'ssupport end with the default setup of the trunk.

Thanks @StefanW

1. When you say two AAD application for each location I assume you mean to just register each PBX in to Azure and ensure I only selectively sync the users to the one location, not twice in other words, to their respective 3CX PBX they should be added to?
2. In terms of the script modification the only change, for me, would be the geographic location around the one country (Australia)....so we have an 02, 03, 07 and 08 requirement depending on which state one is in etc....I assume the script change would be fairly easy if this is the only change?

 

[StefanW]

@Gravité Managed IT

1) Yes, so you can have the correct users per 3CX system
2) this makes it a bit simpler as you could get away with only one dial plan assuming users always dial the area code (02 or 03) for outbound calls. In this case, you have to create a second SBC connection (you can copy the general idea from it from the script New-CsOnlineVoiceRoute) After creation you need to modify per user which SBC they should be using in the voice route.