@JaredBusch We are intentionally being vague on this because the technical stuff on the backend isn't solid yet. We may be able to attest those calls depending on the circumstances. So the vagueness is simply because the product is still in motion.
Still using swap file? Memory is cheap. I don't recall a server where I created swap partition or swap file.
Memory is NOT cheap, not at all.
It is if you own it. If you rent your hardware, yeah, it adds up.
Even if I own it, throwing away 2-3GB of RAM makes no sense. Now, if I own it, I can easily assign 4GB of RAM then remove it once installed, by why? That's harder to script and still no benefit.
It's a bad habit to see resources as cheap and so waste them just because you can. Extra memory doesn't improve performance, it hurts it (just the tiniest bit). And it's not free, if you always apply twice as much RAM as you use (or four times, here), that gets costly one way or another. Either you wasted money overspeccing in the beginning, or you are stuck buying more now.
I believe ./run.sh restarts all services, and I suspect that includes Nginx.
Yes, Nginx is inside a Docker container. But there are three.
All you need is...
systemctl start docker
systemctl enable docker
And you are good to go. It's just a process that needs to be started like any other. There's nothing to know about Docker in this instance. Think of it as the server itself, it just needs to be turned on.
We've been using Skyetel as our primary trunks for some time now, and most of our customers are either using them now or porting over to them in the near term. Service has been great, and very easy to use.
Go into your @Skyetel endpoint setting and make sure it is talking to your PBX on port 5160 also.
This seems likely to be my issue then. I had left it at 5060 in the skyetel portal as you showed above and initially had it port forwarded to 5060 on the FreePBX. When I realized that I had set port 5060 up as the chan_sip port instead of the pjsip I changed the firewall to forward 5060 to 5160 on the FreePBX. I'll try making the change in the Skyetel portal directly to 5160 and just direct port forward 5160 in the morning.
As @JaredBusch figured, this fixed my issue. Once I made this change I had two way audio and no call's being taken down prematurely.
Audio issues are always port related. Though mostly because firewalls are fucking things up.