@BraswellJay said in What determines the interface that SIP RTP streams over ...:

@BraswellJay

I finally figured out what was causing my issue.

In FreePBX under Settings->Asterisk SIP Settings there is a parameter to set the External Address used. I had this still set to the public IP of the original interface. Once I changed that parameter to the public IP of the new interface then all started to work over the new interface as expected.

Glad you sorted it out. Good work!

@BraswellJay

Turned out to be a SIP port issue. I remember when I set this particular site up I ended up using port 5160 instead of 5060 but when I configured the new IP group in the skyetel portal I didn't change to the correct port. Once I made that change the portal now shows the new interface as healthy.

@skyetel said in Did you notice the Skyetel outage today?:

I put this on another forum, but I figured you guys would like to read this too:

For those interested, Our network operates in 4 AWS regions that we keep siloed from one another (meaning no region knows about the existence of another one). When the connectivity issues started, we disabled the network connectivity for all Skyetel assets in the two impacted AWS regions which caused our network to fully failover. (Because the impacted regions had partial connectivity, our network did not fully fail over and tried to limp along with all 4. This is by design; we don't want to automate disabling network routers of our network for obvious reasons... so an engineer needed to click the buttons).

The impact of this was some calls failed to establish, but if they did establish, they would work normally. This is because we are not in the audiopath of the calls. Once the distressed regions were fully down, our network could fully fail over and 100% of all calls completed normally.

The total impact time was 19 minutes, and we estimate about 7% of our calls failed to establish during that period. Sorry for the inconvenience 🙂

Did I mention @Skyetel is awesome lately? Being fixed almost before the customers noticed was insanely awesome.

@jaredbusch said in Anyone know of current Skyetel Promo codes ?:

Contact your rep for that

@skyetel said in Anyone know of current Skyetel Promo codes ?:

60F85B623E

Good till Saturday.

Or the President will casually drop a code.

@jasgot said in ATA sp112 behind Sonicwall to Skyetel:

@jclambert said in ATA sp112 behind Sonicwall to Skyetel:

I never had an issue with Cisco ATAs connected to a cloud service behind Sonicwall devices. I don't recall setting anything up, but I am curious enough to review my setup notes to confirm.

We have not either. We have many Cisco SPA ATAs in service. All of them behind Sonicwalls. This is the only one connected to Skyetel.

Would need to see the packet as I mentioned above to try and give you any kind of answer on why.

Thanks @JaredBusch

Look towards Europe, where IPv6-only internet service is not uncommon.

https://teamhelp.sipgate.co.uk/hc/en-gb/articles/207403895-sipgate-IP-Port-Ranges

https://www.dus.net/en/sip-default-settings

https://en.easybell.de/help/telephone-configuration/general/voip-expert-settings/

@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.

@Skyetel said in Phone Outages for February 19, 2021:

Skyetel’s President is addressing this personally, and all options are on the table. He’s, uh, pretty upset.

Hahhhaahahahahhah

I just followed this guide, worked great! Thanks!

@Skyetel said in Skyetel Postcards - What's Needed:

The single login per computer is probably pretty easy to change, and I can add that to the change request.

Seems like this died on the vine 😞
8ef7946f-8922-41b8-93bd-d2fd252f1b73-image.png
2c52ae98-d7b5-46da-9da6-a8576ba99463-image.png

I would love to make use of this if the issues raised above were resolved.

@marcinozga said in Install Skyetel Postcards on CentOS 7:

@scottalanmiller said in Install Skyetel Postcards on CentOS 7:

@marcinozga said in Install Skyetel Postcards on CentOS 7:

@black3dynamite said in Install Skyetel Postcards on CentOS 7:

Still preferred fallocate instead of dd to create a swap file?

dd if=/dev/zero of=/swapfile count=4096 bs=1MiB && chmod 600 /swapfile && mkswap /swapfile && swapon /swapfile && echo "/swapfile swap swap defaults 0 0">>/etc/fstab

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.

@JasGot said in Skyetel Postcards Redirect Issue:

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.

@krzykat said in Postcards for SMS by Skyetel.:

@JasGot

Have you checked your LE credentials to see that its working properly?

Not sure how. The only sign of LE I can find in the OS or the Docker is a file called letsencrypt_services_data
I can't find a conf file or a binary to do a manual run of LE.

@JaredBusch

There is a current issue with the SSL let's encrypt that I just submitted to them to resolve (they are using an outdated version with Acme 1 instead of the newer Acme 2):

FYI - we've resolved the issue, and I can only assume anyone else that has installed Postcards should have the same issue.

The problem is indeed an issue with Let's Encrypt, and specifically:

docker: jrcs/letsencrypt-nginx-proxy-companion

To fix this issue, please update the docker-compose.override.yml file during builds.

Row 35 should read: image: jrcs/letsencrypt-nginx-proxy-companion:latest

This will insure that the current version for the let's encrypt proxy is called and eliminate the issue.

@Skyetel said in Skyetel sign up working better:

Maybe this?
https://mangolassi.it/topic/20290/ad-blockers-advice

I thought I had posted in your thread because I know that you posted that after my issue.

So yup, going with I slacked and didn't post.

@JaredBusch said in Skyetel support:

Never heard back from T-Mobile, but calls now connect.

Ain't that always the way.

@Dashrender said in Skyetel defenses tripped:

I have to hand to it to @Skyetel - it's outside of Support hours but they got the notice of my post and came in and responded.

Very awesome!

I hope that at some point Skyetel can hire some people to be in the support desk 24/7 (even if from home) so there is less stress on @Skyetel.

But for now I'll take the win in being part of MangoLassi!

Thanks @Dashrender for the nice words :).

FWIW - we do have on call 24/7, but only for emergency tickets from current customers. But I'm happy that I was able to get you setup!

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.