V20 U2 Release - OpenAI, Teams and More Control

[User1231231]

its there in templates now. But doesn't matter what i do, i cant get a provider xml to import. Even if i cut and paste from the OEM generic one. How about you?

That's the point, 3CX decided to remove the ability to import a generic provider template in the latest build with no explanation why. I can only presume it's because they want to force people to use their "preferred partner SIP providers" for financial benefit.

 

[NicholasP_3CX]

That's the point, 3CX decided to remove the ability to import a generic provider template in the latest build with no explanation why. I can only presume it's because they want to force people to use their "preferred partner SIP providers" for financial benefit.

LOW BLOW!

As it is 3CX that hosts the platform, we have a direct obligation for the smooth running of the instance. Using a non supported or preferred provider is not about financial gain, but about providing a good experience for the customers.

Also, some things might be restricted on the hosted by 3CX platform due to access levels, like the call rocessing scripts which could give access to the machine at the OS or filesystem level.

If you need that access we provide the capability to self host on a 3rd party hosting provider, or on your own server.

We do get abused and accused of many things, but come on man....

We do provide the capability of configuring a generic provider in the hosted platform, but within certain paramaters.



This is available under each country. You will no longer see a Generic country.

 

[User1231231]

LOW BLOW!

As it is 3CX that hosts the platform, we have a direct obligation for the smooth running of the instance. Using a non supported or preferred provider is not about financial gain, but about providing a good experience for the customers.

Also, some things might be restricted on the hosted by 3CX platform due to access levels, like the call rocessing scripts which could give access to the machine at the OS or filesystem level.

If you need that access we provide the capability to self host on a 3rd party hosting provider, or on your own server.

We do get abused and accused of many things, but come on man....

We do provide the capability of configuring a generic provider in the hosted platform, but within certain paramaters.

View attachment 42798

This is available under each country. You will no longer see a Generic country.

It wasn't meant to be an attack and I'm sorry if you took it that way; I can understand the reasons to have strategic partners in the industry and why it can be mutually beneficial. The current implementation of generic voip provider in 3CX Hosted lets you customize almost nothing compared to what's available in v18, and if you honestly believe that just getting a trunk registered is proper interoperability and all that's required to adjust between every possible voip provider out there then that's scary.

Also, your current implementation of the generic SIP trunk template in 3CX Hosted seems to have an error. You have duplicate parameters listed with different values.

<!-- Gateway / Provider Inbound Parameters -->
<field name="ParameterIn" custom="" parameter="ToUserPart">$CalledNum</field>
<field name="ParameterIn" custom="" parameter="FromUserPart">$CallerName</field>
<field name="ParameterIn" custom="" parameter="FromUserPart">$CallerNum</field>

It's strange to me to take the side that you feel you know better than your customers when it comes to what we want to do with what we pay for. What difference does it make? If you're going the route of adding generic SIP trunks you most likely are knowledgeable in what you're doing.

 

[tronic]

It wasn't meant to be an attack and I'm sorry if you took it that way; I can understand the reasons to have strategic partners in the industry and why it can be mutually beneficial. The current implementation of generic voip provider in 3CX Hosted lets you customize almost nothing compared to what's available in v18, and if you honestly believe that just getting a trunk registered is proper interoperability and all that's required to adjust between every possible voip provider out there then that's scary.

Also, your current implementation of the generic SIP trunk template in 3CX Hosted seems to have an error. You have duplicate parameters listed with different values.

<!-- Gateway / Provider Inbound Parameters -->
<field name="ParameterIn" custom="" parameter="ToUserPart">$CalledNum</field>
<field name="ParameterIn" custom="" parameter="FromUserPart">$CallerName</field>
<field name="ParameterIn" custom="" parameter="FromUserPart">$CallerNum</field>

It's strange to me to take the side that you feel you know better than your customers when it comes to what we want to do with what we pay for. What difference does it make? If you're going the route of adding generic SIP trunks you most likely are knowledgeable in what you're doing.

You also have to remember that they need to have product guidelines and position a product in a way that will result in the best outcome.
So SMB, hosted and self-hosted are all aimed at a different customer requirements.

Self-hosted has less of a controlled guideline, as this is positioned where the client will rely on a 3CX reseller and their expertise. This will mean that the overall cost is more, as you're now adding a partner that needs to charge for that expertise. They will know the pros and cons of changing things like the provider file. This is because they have 3CX training and deal with it on a daily basis.

This is why SMB has its limits on features, as once you hit this point you move to 3CX hosted. Then, once hosted doesn't meet your needs, you move to a partner and self-hosted through the dealer.

Like, I had a client that had an IT person who had hosted 3CX and installed their own system. This worked at the time, but as the business grew, they couldn't maintain the solution themselves and needed our expertise on the best ways to program things. Eventually we moved to our self-hosted solution, and we charged the to install and maintain the solution.
This overall now costs the company more per year, but now they have our expertise on the best ways to program the system and our support holding their hand, as well as 3CX support.

But this doesn't mean that the hosted solution they had was wrong and didn't work. It just meant that their requirements had changed, and they needed more support and the expertise of a dealer. Maybe you're in the same boat.
I think a lot of people, including some partners unfortunately, are missing how each product is positioned and how they differ.

Hope this helps.

 

[Ronald Lysmont]

I guess this is more about have limits on the basic small business solution. If the basic version did everything, then there would be little point to upgrade.

These are all PRO licensed 3CX hosted

 

[58voip]

Hi,

The blog refers to Windows installations. Currently, you can upgrade to V20 even if you have a PRO edition (Windows). We will notify you of any changes in due course. For new customers wanting to use Windows OS, please quote the ENT edition.

I hope this helps

Hi Gabe, for the existing V18 PRO edition user, when they upgrade to V20, will they see their license key be changed to Ent edition in 3CX V20, or still a PRO edtion license? Or this license edition change will be happen not now in V20 but the near future for V20?

 

[STUCKnCABLES]

i am seeing 2 issues with new build,

1 - when not having auto download selected, 3cx will always attempt to download templates repeatedly all day every day.

2 - the feature to record wav files for IVR is not so simple as it has been, i do see the mic icon but it is grayed out and can not use.