Using Vultr for FreePBX 13
-
@JaredBusch said in Using Vultr for FreePBX 13:
I like Vultr's stat page.
Here is the network usage of a PBX with ~80 extensions (all pjsip, if that matters) and 15 simultaneous calls at peak.What is the specs of your vultr instance with that usage, ~80 extensions and 15 simultaneous calls at peak.
Also, do you have some formula on how to decide what to get instance base on extension and simultaneous calls ?
-
@jasonraymundo31 said in Using Vultr for FreePBX 13:
What is the specs of your vultr instance with that usage, ~80 extensions and 15 simultaneous calls at peak.
Bottom line is that the $5 instance is as small as you can go. You need the 1GB of RAM. If they offered a 900MB option, sure that might work. But the 512MB option will not. So you can't go smaller than the $5 option on the low end, don't try. You'll be swapping and things will get bad, fast, if it will even run.
That said, you could handle hundreds of extensions and way more than 15 calls on that $5 1 vCPU / 1GB RAM option. We use that and we do closer to 30 simultaneous and it doesn't break a sweat. And we don't use g711 either, so we are working it harder than normal users.
You would need a LOT of calls or special usage to make you need a larger VM. We have no customers going larger based on RAM or CPU needs, only on storage needs (we have customers doing huge amount of call recordings or voicemails and just need more space.)
-
@scottalanmiller said in Using Vultr for FreePBX 13:
And we don't use g711 either, so we are working it harder than normal users.
Actually 722 doens't use anything in resources jsut like 711. It is all about being on the same codec for the entire call path.
-
@scottalanmiller said in Using Vultr for FreePBX 13:
Bottom line is that the $5 instance is as small as you can go. You need the 1GB of RAM.
Also, you can scale an instance to a larger plan if needed.
-
@JaredBusch said in Using Vultr for FreePBX 13:
@scottalanmiller said in Using Vultr for FreePBX 13:
And we don't use g711 either, so we are working it harder than normal users.
Actually 722 doens't use anything in resources jsut like 711. It is all about being on the same codec for the entire call path.
If you have it on the full path and don't transcode. We don't. We have Opus where we can and G722 where we can't, so we are transcoding regularly.
-
@JaredBusch said in Using Vultr for FreePBX 13:
@scottalanmiller said in Using Vultr for FreePBX 13:
Bottom line is that the $5 instance is as small as you can go. You need the 1GB of RAM.
Also, you can scale an instance to a larger plan if needed.
Yes, good point. Start small and only grow if you measure and find a need later.
-
@scottalanmiller said in Using Vultr for FreePBX 13:
@JaredBusch said in Using Vultr for FreePBX 13:
@scottalanmiller said in Using Vultr for FreePBX 13:
And we don't use g711 either, so we are working it harder than normal users.
Actually 722 doens't use anything in resources jsut like 711. It is all about being on the same codec for the entire call path.
If you have it on the full path and don't transcode. We don't. We have Opus where we can and G722 where we can't, so we are transcoding regularly.
Why are you using OPUS?
-
@JaredBusch said in Using Vultr for FreePBX 13:
@scottalanmiller said in Using Vultr for FreePBX 13:
@JaredBusch said in Using Vultr for FreePBX 13:
@scottalanmiller said in Using Vultr for FreePBX 13:
And we don't use g711 either, so we are working it harder than normal users.
Actually 722 doens't use anything in resources jsut like 711. It is all about being on the same codec for the entire call path.
If you have it on the full path and don't transcode. We don't. We have Opus where we can and G722 where we can't, so we are transcoding regularly.
Why are you using OPUS?
Adaptable call quality. We notice a huge quality improvement on it. The sound is incredible and when call path degrades it adapts and can hold call quality better than g711 even on flaky connections. We notice a very big overall improvement with it. Plus it uses less bandwidth so offers HQ audio on some pretty tiny connections, but that's a rare need.
-
@scottalanmiller said in Using Vultr for FreePBX 13:
@JaredBusch said in Using Vultr for FreePBX 13:
@scottalanmiller said in Using Vultr for FreePBX 13:
@JaredBusch said in Using Vultr for FreePBX 13:
@scottalanmiller said in Using Vultr for FreePBX 13:
And we don't use g711 either, so we are working it harder than normal users.
Actually 722 doens't use anything in resources jsut like 711. It is all about being on the same codec for the entire call path.
If you have it on the full path and don't transcode. We don't. We have Opus where we can and G722 where we can't, so we are transcoding regularly.
Why are you using OPUS?
Adaptable call quality.
That is the point of it, but for most PBX implementations there is no need for it. Sure for people on mobile using unknown signal strengths, but that is still al low over all percent of implementations. I know it is the standard for anything using WebRTC, which I assume SonataSuite does.
Then, what providers support OPUS? Most only support 711 and sometimes 722.
-
@JaredBusch said in Using Vultr for FreePBX 13:
Then, what providers support OPUS? Most only support 711 and sometimes 722.
Hence why we transcode to g722 for Skyetel. But the g722 path is from a datacenter to datacenter, so not really worried about questionable call path qualities.
Opus seems to help on everything from wifi to mobile to offices with low quality WANs. We have people on fractional T1 still, so fight some tight bandwidth battles.
