Update 7 Beta - New Deployment Server

[SweetAction]

Regarding the new "ish" router phone feature. For a cloud hosted instance, does anyone see any reason to not just make every phone a router phone? Now every phone is it's own point of failure instead of an on prem SBC, or 1 router phone with 10 other phones connected through it. I think RTP handoff (Not entirely sure router phones handle RTP handoff for phones proxied through it. Haven't tested this yet) might come into play but most of our customers are close enough to the DC where they won't notice the difference of 30ms compared to LAN latency.

Is there a limit to the number of router phones an instance can have? Maybe too many router phones eats up RAM or something I'm not aware of? I was just thinking, it's probably the best to make each phone a router phone, for cloud hosted that is.

I would make each it's own router phone. There will be more load on the 3CX server, but it's worth it to eliminate single point of failures.

 

[tronic]

Regarding the new "ish" router phone feature. For a cloud hosted instance, does anyone see any reason to not just make every phone a router phone? Now every phone is it's own point of failure instead of an on prem SBC, or 1 router phone with 10 other phones connected through it. I think RTP handoff (Not entirely sure router phones handle RTP handoff for phones proxied through it. Haven't tested this yet) might come into play but most of our customers are close enough to the DC where they won't notice the difference of 30ms compared to LAN latency.

Is there a limit to the number of router phones an instance can have? Maybe too many router phones eats up RAM or something I'm not aware of? I was just thinking, it's probably the best to make each phone a router phone, for cloud hosted that is.

Be good to hear the 3cx viewpoint on this, as I've thought the same thing.

 

[N_G]

I totally agree with you. We use lightsail as well as EC2 is hard to quote under when you don't know the total cost.

You could qoute 3CX hosted of course.

@jestruch You can do it now problem as @SweetAction said. I just dont believe its necessary but there is almost no overhead on the server. We are planning a backup router phone feature.

 

[N_G]

So are you saying that a user can't just grab an off the shelf headset and use it like they can now?

Obviously there is no support this way. But I have a lot of users that like to use apple or google buds or even some some cheap 3.5mm headset.

No I am not saying that - how did you infer this? As @SweetAction already correctly pointed out these types of headsets are supported by the OS. So these work out of the box with 3CX. The special integration is only needed for the "in ear" answer button in the case of a desktop app. (mobile app already supports it natively)

In fact i want to add i really recommend use of off the shelf headsets. Installing drivers on the OS, then having to support these over the years i believe is a hassle for users, admins, partners and of course 3CX.

Also i think there are health benefits to not having a DECT transmitter with the power of a microwave in your head 8 hours a day.

 

[tronic]

No I am not saying that - how did you infer this? As @SweetAction already correctly pointed out these types of headsets are supported by the OS. So these work out of the box with 3CX. The special integration is only needed for the "in ear" answer button in the case of a desktop app. (mobile app already supports it natively)

In fact i want to add i really recommend use of off the shelf headsets. Installing drivers on the OS, then having to support these over the years i believe is a hassle for users, admins, partners and of course 3CX.

Also i think there are health benefits to not having a DECT transmitter with the power of a microwave in your head 8 hours a day.

Thanks for the confirmation.I must have read it all wrong.

 

[N_G]

@tronic - thats great ! Just seeing maybe i was not clear. But i agree 100% with your off the shelf comment just in case i was not clear

Check the partner forum for news about Lightsail ....

 

[bit101]

Continue reading the Original Blog Post.

Hi Nick,

i would like to know, what is the reason that the old wizzard will not be implemented at future releases? We use 3cx *only* at on premise server and could get running each 3cx installation without any trouble on Linux very easy. So the wizzard was a good think all the time!

In the new configuration wizzard the credentials for the management console are missing. Why?

regards, Norman

 

[N_G]

Hi Norman - I am sorry but we dont have time to explain and justify our decisions and strategy to our 20,000 plus partners on an individual basis. We have good reasons for everything we do.

We are happy to be open about our direction and strategy so that you can make your own decisions in choosing the right product for you. System deployment will be online (there are still some features to be added such as own certificate) and then at one point the onboard wizard will go. You will need to use split DNS.

If this is not acceptable to you then you have to use another product. But keep in mind that clients or apps connecting to local IPs without a fully qualified secure FQDN - i would think that this will be blocked at browser and OS level quite soon anyway for security reasons. (i.e. google or apple will block it not 3CX)

 

[bit101]

Hi Norman - I am sorry but we dont have time to explain and justify our decisions and strategy to our 20,000 plus partners on an individual basis. We have good reasons for everything we do.

We are happy to be open about our direction and strategy so that you can make your own decisions in choosing the right product for you. System deployment will be online (there are still some features to be added such as own certificate) and then at one point the onboard wizard will go. You will need to use split DNS.

If this is not acceptable to you then you have to use another product. But keep in mind that clients or apps connecting to local IPs without a fully qualified secure FQDN - i would think that this will be blocked at browser and OS level quite soon anyway for security reasons. (i.e. google or apple will block it not 3CX)

Hi Nick,

yes i understand that you have your strategy because we have this too and therefore it is important to know, why the old wizzard that works fine for us, will not be implemented in future releases?

We have no technical issues with 3CX Split DNS is ok. But in the new wizzard there is no management credentials shown. Can you tell me why? We need further access to that.

thanks & regards,
Norman

 

[N_G]

Hi Norman - Ok i see what you mean Well in the new wizard we setup a system admin for you. The root admin of the management console you can set it up later, although this access, together with the management console, is going away over time.

 

[kent3]

Hi Norman - I am sorry but we dont have time to explain and justify our decisions and strategy to our 20,000 plus partners on an individual basis. We have good reasons for everything we do.

We are happy to be open about our direction and strategy so that you can make your own decisions in choosing the right product for you. System deployment will be online (there are still some features to be added such as own certificate) and then at one point the onboard wizard will go. You will need to use split DNS.

If this is not acceptable to you then you have to use another product. But keep in mind that clients or apps connecting to local IPs without a fully qualified secure FQDN - i would think that this will be blocked at browser and OS level quite soon anyway for security reasons. (i.e. google or apple will block it not 3CX)

Hi Nick

Sorry for hijacking this

Will Split DNS be required for sites with SBC machines and cloud 3CX?

 

[N_G]

@kent3 - no problem no split DNS is only relevant for on premise PBX. Cloud has full qualified FQDN built in as it we're

 

[bit101]

Hi Norman - Ok i see what you mean Well in the new wizard we setup a system admin for you. The root admin of the management console you can set it up later, although this access, together with the management console, is going away over time.

Hi Nick

ok thanks for that. But on premise versions will be existing further hopefully?

regards, Norman

 

[N_G]

Of course its a key part of our strategy.

 

[nbalmadier]

Hi @Nick Galea

Many months since your message and it seems that 3CX is still not available on OVH market.
Since 3CX stopped the Openstack API integration, we can no longer deploy 3CX in OVH.
Do you have a delivery date to communicate ?

Thanks in advance for you feedback

BR
Nicolas

 

[anonymouse]

Image isn't available on Vultr marketplace; is there an ETA on this?

 

[N_G]

We will release a Vultr Marketplace image when we release update 8 in the coming weeks. In regards to OVH, there is no marketplace that we can support so if you want to use OVH you have to upload the image yourself to OVH.

 

[PrismaNetworks]

Good evening, I didn't want to open another topic since I see this one is similar to what we're looking for.

I'm noticing in the deployment for 3CX that Vultr no longer appears in the creation of pbxexpress, is this something permanent or will we be able to make deployments at some point through API?

Thanks to anyone who can support me.

Kind Regrads,

Mario L. Gutiérrez A.

 

[tronic]

R

Good evening, I didn't want to open another topic since I see this one is similar to what we're looking for.

I'm noticing in the deployment for 3CX that Vultr no longer appears in the creation of pbxexpress, is this something permanent or will we be able to make deployments at some point through API?

Thanks to anyone who can support me.

Kind Regrads,

Mario L. Gutiérrez A.

Read post above yours