@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

@JaredBusch

Everything works fine now.

The issue was a DNS resolution for devices within the LAN. I added an A record on the router for split dns. That solved the problem.

Thank you so much for your support

@JasGot said in VitalPBX / Asterisk Limit Calls Then Go To Voicemail:

@scottalanmiller said in VitalPBX / Asterisk Limit Calls Then Go To Voicemail:

We can't limit in Skyetel, or the calls won't make it to the voicemail.

My first thought would be to route calls (when their are 4 current calls) to a specific DiD that goes right to VM.

Are you working with Skyetel with custom programming or are you limited to their web portal options?

Not sure what we'd have them do to fix the issue.

@Dashrender said in DVX 8000 IP PBX CONFIGURATION:

Awesome to see more telephoney stuff show up.

Bad telephony, but meh. all good.

@DustinB3403 said in Kari's Law and Special SMB Onus on IT Staff:

@scottalanmiller You just said that Enterprise customers can be forced to update their information, but smaller orgs get a pass.

I must be misreading what you've typed.

Yes, the CUSTOMERS get a pass, IT that supports small customers has to provide the information that they don't have control over. Enterprise customers have to provide the information from the company.

SMB customers get to not tell anyone when changes are made and blame someone with no power or way to get that information for certain.

At least the notification requirements are pretty simple and straightforward. For almost everyone, just email out a notification.

@JaredBusch said in Incoming Call Issue:

@VoIP_n00b said in Incoming Call Issue:

Running FreePBX v14... No resent changes made, except to change the name on an extension.

When some calls in, and let's say they dial 555 then end up getting 511, 511 can then forward the call to 555 no issue, but I have no idea what is causing this.

Because they released a horrible fucking update to IVR.

Edit your IVR and set strict dial time out to No - legacy

That fixed it! Thank you so much!!!

Typo in the port, we found it.

Very nice.

That’s one thing that’s seriously missing from FusionPBX!

@JaredBusch
Hi, Jared, if you need support from Fanvil, just let me know, here is my email ID: [email protected]

@JaredBusch said in Prerequisites for Yealink YDMP Install:

@DustinB3403 worked with this I believe...

I did, but the install process was pretty easy.

https://drive.google.com/open?id=1-2hh-5N-vg-s2w8MS3GVaqDRVetLmbpp

@JaredBusch said in Building VitalPBX on Vultr Automatically:

@scottalanmiller said in Building VitalPBX on Vultr Automatically:

and be fully updated.

I noticed that the defualt CentOS 7 image was pretty much fully up to date before I ran the install script. Only thing that came down when I ran yum update -y was wget.

Yeah, it is more of a "just in case" something is out of date. I almost never see it not fully up to date when I fire it up.

@hobbit666 said in Exploring VitalPBX:

Do you know if they plan on changing

Not much choice, chan_sip is deprecated.

@Curtis said in Bria Mobile iOS and FreePBX:

I tried a few hours with Bira this morning...

Just a couple minutes ago I downloaded Acrobits Groundwire by Acrobits, and it instantly worked...

https://itunes.apple.com/us/app/acrobits-groundwire/id378503081

That listing clearly states it uses push. So how does that work?

@Dashrender said in Relationship Pricing:

@JaredBusch said in Relationship Pricing:

But with the second one there, I only perform a lookup once every 30 days for numbers that call me.

Is this because FreePBX caches the info?

Yes, but any system can be setup that way.

@JaredBusch said in Broadvox Outage 15 April 2019:

Broadvox is now named Inteliquent as far as where the domain redirects to.

Yeah, while passing through on Onvoy page along the way of the redirects.

@nadnerB said in Polycom and Plantronics Merger: Poly:

When thigs go wrong, they'll be Polygon ;)

JAJAJA

Okay, we got it. Doing the switch, then the fwconsole update, then rebooting, and running through it all again... eventually it fixed itself.