Update 7 - DECT, VoIP Providers, RPS Mass provisioning

As long as it stays an option, even as a paid support package or something like that, because we do have some smaller businesses using on-prem PSTN who still need their Pro 4/8SC, and they're not the "pain to support" type of clients.

Most partners can support those customers on our own and only talk to the support team when really needed.
 
As long as it stays an option, even as a paid support package or something like that, because we do have some smaller businesses using on-prem PSTN who still need their Pro 4/8SC, and they're not the "pain to support" type of clients.

Most partners can support those customers on our own and only talk to the support team when really needed.
Totally agree, and we've got similar. Folks with a PSTN gateway because they're located in Nowheresville and their DIDs are controlled exclusively by copper and unable to port yet. It's really crazy there are still places geographically where no relationship exists between local legacy telco and SIP carriers. Wild.
 
As long as it stays an option, even as a paid support package or something like that, because we do have some smaller businesses using on-prem PSTN who still need their Pro 4/8SC, and they're not the "pain to support" type of clients.

Most partners can support those customers on our own and only talk to the support team when really needed.

Definitely this. 75% (and growing) of our installs are 4SC and 8SC Pro's, and only ever will be for a multitude of reasons.
 
Generic SMS provider is a massive feature. I'll be upgrading a test server right away to try that one out.
 
  • Like
Reactions: Evolute IT and N_G
@sam.phillips but of course provider has to implement the API... Which is almost identical to many of the leading ones we already support. Providers can build and test against the API and can configure the generic template with the webhook URL for SMS. SMS API doc here.
 
Last edited:
As long as it stays an option, even as a paid support package or something like that, because we do have some smaller businesses using on-prem PSTN who still need their Pro 4/8SC, and they're not the "pain to support" type of clients.

Most partners can support those customers on our own and only talk to the support team when really needed.

Definitely this. 75% (and growing) of our installs are 4SC and 8SC Pro's, and only ever will be for a multitude of reasons.
Sounds like at the very worst, a customer used to a 4SC that wants to stay with the on premise edition can buy a 16SC if they truly need OnPrem. Yeah it's more money, but if that's the business need then that's the business need.
 
We need 4 and 8SC on premesis for the custom call flows. If its removed, most of our customers can't stay with 3CX. 16SC pricing is way too expensive for these customers. We made custom C# code to automate parts of their internal business processes which can never be achieved with the hosted by 3cx version. I hope 3CX will reconsider removing these licenses and also allow small businesses have some flexibility in automation.
 
Will update 7 also allow hotdesking Via Router Phone?
 
We need 4/8 SC self-hosted (Azure) for our clients,
Sure we have some bigger 16-96sc licenses self-hosted in azure, as we require backend SSH the hosted only is not an option,
plus it does not make sense to have customers on different platforms
 
  • Like
Reactions: mcsphones
@Nick Galea - Is there a possibility to get the welcome/password email (which is sent through to the user) updated with no reference to the old Windows Client? A direct link would be epic - https://COMPANY_NAME.3cx.com.au:5001/webclient/api/app/windows.

Just rolled out another client and the end users are all installing the v16 Windows App rather then reading the next line. Yep, could have guessed they would do that.
 
Hi;

I started getting an error as shown in attachment, both webclient and desktop app have the same problem.
 

Attachments

  • 1677480927117.png
    1677480927117.png
    47.5 KB · Views: 45
  • 1677480973169.png
    1677480973169.png
    33.8 KB · Views: 44
@Nick Galea - Is there a possibility to get the welcome/password email (which is sent through to the user) updated with no reference to the old Windows Client? A direct link would be epic - https://COMPANY_NAME.3cx.com.au:5001/webclient/api/app/windows.

Just rolled out another client and the end users are all installing the v16 Windows App rather then reading the next line. Yep, could have guessed they would do that.
You can change the email template in the management console under Settings - Email - Email template. The template you are searching for is 'Extension Welcome. You can put in your requested URL like so: %%WEBCLIENTURL%%/api/app/windows.
 
@GaSo Where does it say we will remove 4 SC or 8 SC licenses? Please stop jumping to conclusions without any official statements from our company.

That said, yes 4 SC or 8 SC on premise licenses are probably going to become more expensive. And if $200 a year is too much for a customer then yes they best start looking elsewhere. $200 for a system that is running custom call flows is peanuts
 
Last edited:
@Nick Galea , thanks that's good news. I think we and others made the conclusion based on your sentence its last part (see italic) "Self hosting a 4 SC or 8 SC is not worth it - not for the customer, nor for us to support it.". So we read that you would drop supporting it.
Hopefully it will also remain possible to install in an alternative way on lightsail (currently using it, for fixed pricing).
 
@GaSo - fair enough, you are right. No we will be keeping 4 SC or 8 SC on premise/self hosting for sure. When i said not worth it, i meant for $100 per year. And of course everybody says they will support it themselves but its not the case. So expect price increases for the 4 SC and to a lesser extent 8 SC self hosted. BTW our hosted will support call flows soon.

@Sparky Bear Sure we will keep Azure and we have market places images. But I believe if they can afford Azure they can also pay a bit more for the PBX license.
 
@Nick Galea Thanks. Most of our customers have 8SC. Currently we have storage on the linux system with SSH access to enable it. If possible it would be nice (and safer without the need for SSH) to have some automated web access to write key based storage by our automated server that can be read using the callflow C# (like from a method in the call flow checking certain key based values, without it querying each time an extern server for updates). We use the push method from the main medical server as it avoids any delays in the call (only needs to read locally for routing) and a lot lighter for all systems involved than an external query. But it's quite different than many call flows, we also wrote it in C# directly. Mainly it allows routing of calls in a complex dynamic way which could change every day.

Outside of the call flows, we also made a webcall that triggers the 3CX IVR audio recording to record new messages, so their phone rings automatically to record without them needing to go to the admin or user panel (all can be easy, but people easily forget repetetive tasks and nothing easier than the phone ringing :) ). For that an API would be safest/ideal in a cloud perspective. Currently we noticed the change to the xapi calls. But we only use it very limited, so still easy to follow these changes.

We also copy the original audio file prior to starting the audio recording, as when they hang up during recording without confirming, the file is deleted without the original remaining, so we copy it back in ssh automatically when they fail to complete (when the file is missing), else there is no audio at all and we force them to have at least an audio message active. If 3cx could leave the file in tact during a cancel recording it would be nice. (3CX support said it was by design, as it overwrites, which is technically right but not a desired end goal), and creating new files else pile up the whole storage.

We're quite demanding (sadly, as it's always dangerous to lose these benefits) but it's also because 3CX allows such a flexible solution which really helps these small medical locations with rotating people a lot. Which isn't an option with most other PBX systems. Most PBX system work in a quite static workflow, while such call flows and dynamic triggers really help people save time, mistakes and money. And in health care it's a big win.
 
  • Like
Reactions: N_G
You can change the email template in the management console under Settings - Email - Email template. The template you are searching for is 'Extension Welcome. You can put in your requested URL like so: %%WEBCLIENTURL%%/api/app/windows.
Thanks mate, while that can be done manually on all my clients. Updating the default would be ideal. Or am I missing something? v16 pales in comparison to v18 of the Win App.
 
  • Like
Reactions: Evolute IT
@techcare - we will check into this. I thought both links we're there ...
@GaSo - yes nice application. Yes this is what 3Cx is good at! But i think these healthcare practices are making quite a bit of money and i think they will have to get used to paying more for having 3CX automate so much of these tasks for them.....
 
we will check into this. I thought both links we're there ...
Currently it's just the v16 app link and a line that says "go to the webclient to install the DesktopApp".
 
This is the German version:1677507192003.png
 

Forum statistics

Threads
111,994
Messages
590,183
Members
164,934
Latest member
bunthoeun.may