Azure 'Size' Recommendations: ~100 Users, 3xSBCs, 8 Channels (low usage)

Status
Not open for further replies.

KaveMan

Customer
Joined
Apr 14, 2022
Messages
9
Reaction score
3
Hi All,

As an Architectural firm, our onsite 3cx is moving to the cloud and like many now, our 'phone' requirements are quite low - mainly just to handle inbound calls and a low volume of outbound. All comms internally is now using Teams**.
But, being Downunder, 3CX does not have hosting 'directly' availible :(. There are a number of reasonable reseller offerings for 3cx hosting, but we have the technical ability to 'do it ourselves' with a SIP trunk, which is most cost effective.

Question: Given
  • 3 offices with Yealink handsets (currently testing Debian SBCs in VMs)
  • about 100 Users.
  • about 80% of users have Yealink Handset, softphone on laptop AND iPhone concurrently. (20% users, only have handset)
  • a few road warriors using softphone (windows+iPhone) only
  • 8 Channel Professional License
  • No call recording. No use of video conferece etc.
  • ** Later, we will be testing the integration with Teams, but, will only ever integrate it with about 10 users.

What Spec or 'size' of Azure VM would be best fit and not overkill (or strugling)?

Ideally, would something like the B2ms, which has "2 cores and 8 Gigs or RAM" work?
Would it still run OK on the B2s "2 Cores and 4 Gigs of RAM"?
Remembering that we have a max of 8 concurrent calls.

Other than making a bunch of calls at once, is there a methodolgy to 'stress test' a 3cx server?

Cheers!
 
Vultr has datacenters in Sydney and Melbourne. We've had great success with their Cloud Compute service for hosting 3CX. You can upload the 3CX iso and deploy directly. Referral link https://www.vultr.com/?ref=7310749
 
As you are moving your 3CX from onsite it would seem you already have an idea of the resources you would need based on the current sizing and resource consumption. Also, unless you are transcoding or recording, simultaneous calls don't really factor very much into CPU or memory which is why the 3CX sizing is based off extensions. The nice thing about Azure and virtualization in general is that you can resize instances. So start with the largest your budget allows and monitor resource usage and adjust accordingly if you are on the paranoid side. Or start with a small instance and adjust the other way as needed if you can afford a few bumps.
 
please check here also as AU has 3CX hosting since Thursday:

Well this does make things intersting!!! Thanks for the heads up!!!
...now to figure out the pricing .....
 
  • Like
Reactions: KaveMan
Status
Not open for further replies.

Forum statistics

Threads
111,974
Messages
590,083
Members
164,900
Latest member
Silent_Guru