Separate names with a comma.
Discussion in '3CX Phone System - General' started by Bianca, Apr 2, 2018.
Continue reading the Original Blog Post.
Excelent news! Congrats 3CX Team!
Good to hear of official Azure support. After reading the blog post and instructions articles, I'm left wondering:
- What kind of machine is created? I assume this is the Debian version, not Windows?
- What machine specs are recommended (memory, processor, disk) and what Azure machine type does that correspond to? Maybe a couple examples based on number of simultaneous calls...
- Does the wizard take care of the necessary options for creating a fixed IP, opening firewall ports, clock configuration (Hyper-V integration?), etc?
I've been running 3CX on Azure for a couple years under Windows Server 2012 R2. Works great since they started supporting static MAC addresses. Is 3CX on Windows on Azure now supported as well? Is there an article about how to configure that?
you can select the size of the instance based on your needs and SC of the 3CX. Here is a reference guide: https://www.3cx.com/docs/recommended-hardware-specifications-for-3cx/
We install debian 9 as guest os.
Yes, we create all those things. Once created see them in the resource group "pbxexpress"
Do the hardware recommendations apply to both Windows and Debian?
Is 3CX for Windows now supported on Azure as well?
BTW I think this page needs to be updated: https://www.3cx.com/partners/hosted-pbx-providers/.
thx for the attention to the document, we will update it.
Our tests have only been made at current with Debian 9 on Azure and we do not plan to test Windows as the main focus is the usage via PBXexpress.
Thank you for the clarification.
I moved my 3CX to the Azure using this, works great! Right now using SBC connection for the office phones and STUN for the home phones to connect and all works well.
I would love to test On-Prem to Azure VPN instead for the office phones.but the way the 3cx pbxexpress tool created the virtual network the subnet assigned to the VM consumes the entire virtual network subnet class 10.0.0.0/16 of a 10.0.0.0/16 subnet.
As such I can't create a gateway vpn subnet inside the virtual network subnet to allow communications.
Do you have any suggestions on this? It would be extremely helpful to use on-prem to azure vpn for larger locations instead of sbc.
I'm no azure expert but what I found is that I can't edit the subnet settings if there are VMs using it. I can stop the VM but it still won't let me edit it. From what I can find the only way to correct it is to delete and re-create the VM but i'm not comfortable doing that because likely it will mess up other things.
you can just change the network and move the instance to this new network (reboot of instance is needed)....