You may also want to look into cable management solutions as well.

@scottalanmiller said in All Yealink Phones Down at One Site:

@dbeato said in All Yealink Phones Down at One Site:

@scottalanmiller said in All Yealink Phones Down at One Site:

@i3 said in All Yealink Phones Down at One Site:

Factory reset a phone and try manually programming? How about a packet capture at the site firewall, do you see attempts from that IP phone to where? I am assuming that the PBX is hosted elsewhere.

This is basically where we went. We did this series of events and it appears to be fixed...

Rebooted the firewall. Removed SIP-ALG, but this appears to have had no effect. Updated the firmware on each phone. Went to static DNS rather than DHCP set. DNS to CloudFlare instead of AD. Ensures STUN was on and set correctly. Added the PBX as a Proxy, manually enabled STUN for the proxy.

After those seven steps, all phones are now registered. Couldn't find any step there that individually made a difference.

To me looks like the DNS was caching something for the devices to get to. That's my theory.

If so, why did changing the DNS alone not fix it?

Not sure, I am just going by what you said. Basically very strange.

@scottalanmiller said in Public STUN servers:

I tend to use:

stun.stunprotocol.org

This one.

@mmicha

Yup, it's a good solution for sure. Nothing is perfect, but as long as you have CommQuotes by your side, you will have someone there to help you if you need it. We have clients with a few phones to hundreds of seats, as well as call centers that push millions of minutes per month over their network.

You are in good hands and I think you are going to save so much money that you will be hoisted up on to a chariot and whisked away to the kingdom that awaits you as King of Phones at your company

It's my first time running into it. Wondering if it might not be a corrupted client.

@bbigford said in FreePBX Reload Failed Retreive_Conf Encountered Error 1:

@scottalanmiller said in FreePBX Reload Failed Retreive_Conf Encountered Error 1:

Shut down Asterisk manually, restarted again with fwconsole start. Seems okay now. Odd that a reboot didn't pick that up.

That is weird... Was the service not running after the reboot?

Oh it was running. It just wasn't happy.

@smitherick Thanks for your suggestion

I just tried with Reid method and it is working well. The red notification has been removed

@jaredbusch Thank you

@stuartjordan said in Yealink T19PE2 FreePBX:

I personally like freepbx and will continue using it, the interface is a bit dated I must admit, but that doesn't bother me.

FreePBX interface is definitely dated. But also .... why would the interface ever matter that much? But even if it did, I've used 3CX and their interface was far worse.

@scottalanmiller said in FreePBX 14 Firewall Start Warning:

@jaredbusch said in FreePBX 14 Firewall Start Warning:

@scottalanmiller said in FreePBX 14 Firewall Start Warning:

Well, we are one step newer, so that might be it.

# fwconsole ma list | grep firewall | firewall | 13.0.46.1 | Enabled | AGPLv3+ |

I do not know the CLI command to revert, but it is simple to do in the GUI.

CLick "Check upgrades and then expand the Firewall and you will have a previous versions option.

Tested and you are right, rolling back to 45.5 and the message goes away.

You could upgrade to edge and see if it is different, but I would just wait for the next update.

@biglittle said in The Basics of VoIP SAMIT Video:

Just realized today when routing a ticket that our VOIP is pbx based? No idea what any of this means, but excited to learn

Essentially all business VoIP uses a PBX. There can be exceptions, but it’s mostly theoretical.

@jaredbusch said in SIP Softswitch Real Addr vs Gave Addr:

@gjacobse said in SIP Softswitch Real Addr vs Gave Addr:

I am not sure how this will relate,.. but I am staring at our PBX and and this page. And then I see the different port numbers - It's interesting to see so many that are not 5060

No relation. this is NAT networking 101.

All of your devices connect to pbx.ntg.co:5060
But their local outbound ports cannot all be 5060. How would the router know which devices to translate it back to.

Yup,. I get that. - well anyway. moving right along...

@jaredbusch said in At What Size Should a Business Have a PBX:

@travisdh1 said in At What Size Should a Business Have a PBX:

@jaredbusch said in At What Size Should a Business Have a PBX:

@travisdh1 said in At What Size Should a Business Have a PBX:

2-3 seems large when I'm setting one up just for myself, now that I know my cell phone randomly refuses to go to voice mail 😞

WTF?

Yes, exactly my reaction when I heard about this. Waiting on my tech support request response. Just got that in today.

No, I mean the first part. WTF does that even mean.

Confused, late night postings apparently.

@whoolly said in Switchvox phone issues:

Vendor insisted he has never had any VOIP issues with Sonicwall and didn't want to budge on that.

Even while it doesn't work. So you know that he'll say this to other customers now, even after this one. Chances are, he's had problems at all customers. SonicWall is culprit #1 for VoIP issues. I mean that literally. I get a call that someone has VoIP audio issues, my first question is always "Do you have a SonicWall?" Nine times out of ten, the answer is yes and nine times out of those ten, the SW was the issue. It's nearly a sure bet with audio issues.

Had you led this question purely with "I have these audio issues..." we'd have said "I bet you have a SonicWall."

As far as many comments about redundancy and not all eggs in one basket. Just need to have a backup system that runs a nightly backup and restore script to another server or two. Setting up a server cluster is also possible for both systems.

@bigbear This is still a good idea. How is it going now?

@jaredbusch said in Issabel PBX " Elastix Alternative ":

@scottalanmiller said in Issabel PBX " Elastix Alternative ":

@alyragab said in Issabel PBX " Elastix Alternative ":

I think that the purpose of the Issabel is to continue creating the Add On Modules that was supported by Elastix , also it is based on CentOS 7 which will be more reliable than what Elastix 2.5 was.
anyway i think we need to wait till we find Issabel is stable distro and we can depend on it as we did with Elastix.

I assume that they are working form the nearly released Elastix 4 work. That was on CentOS 7 at the end.

And it did work with a lot of patience and knowledge of the underlying systems. But it was a hard fail for the layman.

True. I had it working, but it wasn't ready for prime time when they gave up on it all.

@scottalanmiller said in DID Block Puchases:

@Danp said in DID Block Puchases:

@scottalanmiller said in DID Block Puchases:

That's just weird.

How so? Each DID is independent of the B channel, so I can have a multitude of DIDs and only a few B channels if so desired.

Except it's a weird pairing. If you wanted flexibility to sell one at a time. Not "almost every channel."

But it is a did not a number assigned to a channel.

@scottalanmiller is right. The bottleneck is always the customer router. And not so much bandwidth as much as packets per second. Your dropbox sync is killing your phone calls 50 to 1 over bandwidth 99% of the time. Your $50 linksys router can't handle a million pps.

Most ISP's are little more than Broadsoft resellers with no interconnects in their local market. Even on the WISP side speeds are so good now that bundling voice isn't relevant.