so what we did was 3 step process - put the extension number on first alternative, another on second alternative, edit the call re-routing for the said extension number pointing to the line of 1st and 2nd alternative. we use the current timer but instead of going to VM it goes to the alternatives.

I agree that moving to a new system right away seems like the best course of action given that the phones are not actually down, but just cannot continue to be configured.

@JaredBusch said in Yealink VoIP Phone Powered by Ubiquiti ER-X PoE: @scottalanmiller said in Yealink VoIP Phone Powered by Ubiquiti ER-X PoE: Anyone tried this combination? Does the power output on the one PoE port of the UBNT ER-X properly power the PoE input on a Yealink phone? We are specifically looking at the T42S. The ERX should work if the power injector that you’re passing through is one design for the phone and not the fixed voltage unifi The ER-X models have warnings in the manual that you need a different power source than the included wall wart if you're going to provide PoE to a device. At that point, just use passthrough from a compatible phone adapter. @JaredBusch already nailed it.

@jaredbusch said in FusionPBX Install Error on CentOS 7: @fateknollogee said in FusionPBX Install Error on CentOS 7: Just emailed Mark at Fusion. He said "Yes, the official FusionPBX install script works fine with Debian 9 and Freeswitch 1.8." So outdated documentation? Or what? Seems like just one page of it wasn't updated. The rest was.

@JaredBusch - The Endpoint Manager has it Enabled. I set it as disabled to match your settings to see if that fixes it. I will report back later with the results. As always thank you for your assistance.

@jaredbusch Ok thanks for the explanation

@jaredbusch said in Asterisk 13 CRITICAL ERROR! Required Service CHAN_SIP is disabled! This device is unusable!: does chan_sip.so exist in /usr/lib/asterisk/modules/? My guess is, no. But once we determined that there was no simple restoration and all evidence of chap_sip was gone from the system, they just rolled back to a snapshot from before the outage and all is well. So we might never know.

@jaredbusch The model config file also has this option. So I "should" be able to use the "all" setting and have this work there as well, yet it doesn't seem to.

@dustinb3403 I see Polycom has some higher end models now. Nice and colourful.

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

We still have the error, but we did determine that it's just an error message and the clients can register fine. The registration issue was unrelated. So not a big deal, but it would be nice to know why we get this.

@360col Thanks for the feedback. I'll know more next week.

@scottalanmiller said in Public STUN servers: I tend to use: stun.stunprotocol.org This one.

@tm1000 said in FreePBX 14 Module Update Errors: Our QA team has confirmed that firewall has no issues: https://community.freepbx.org/t/bug-in-latest-firewall-adding-ip-to-firewall-trusted-zone-no-longer-updates-iptables-firewall-rules-on-firewall-restart/50181/9?u=tm1000 I've got a few on the latest and haven't seen anything ourselves, yet. Seems good.

This really old post gives a clue on what the structure is for their firmware numbering. http://forum.yealink.com/forum/showthread.php?tid=1661 The template of Firmware name of Yealink phone is X1.X2.X3.X4 (1) X1 means the Phone Model X1- Phone Model T4 Series 35 - T48G 28 - T46G 29 - T42G 36 - T41P (2) X2 means the Major version number X2-Major version number 61 - V61 70 - V70 71 - V71 72 - V72 (3) X3 means the Custom or Neutral version 0 or 1 means Neutral version Non 0 or 1 means Custom version (4) X4 means the Minor version Yealink will release some minor versions after solving some bugs.

Made no configuration changes to the firewall tonight. Shutdown FreePBX VM, made a new one, and stuff seems to be working as it should. I'll do a few more tests tomorrow to make sure all is well. Edit: I lied. I made a new DHCP reservation for my new FreePBX server.

@jaredbusch said in Flowroute adding more PoPs: ip auth with random p Right, my preferred pop is listed in the trunk. I am just uncertain how their failover POPs work. For example, if I have the NJ pop in my Trunk, but the NJ POP becomes unavailable, on the Flowroute side, failover occurs, and traffic is rerouted to another POP. However, in FreePBX, do I need to do anything to list the failover POP IPs in the firewall?

@krisleslie :{../name}: Got ya

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

@scottalanmiller said in Remote FreePBX Extension: @fuznutz04 said in Remote FreePBX Extension: @gjacobse said in Remote FreePBX Extension: NTG uses a responsive firewall on its internal PBX and have very very little rare issues. Set the phones server, stun, and such and you are good to go. You use STUN with the responsive firewall ? I haven’t had to use STUN for a while now, but I know a lot of people still have to use it. Just curious as to why? We use STUN always. The responsive firewall doesn't affect the need for STUN in any way. STUN is for the end points, not the server. Does the traffic from the endpoint via STUN not also appear form the STUN IP to the server? I rarely use it. so just wondering.

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

@bnrstnr said in Weird Network Errors on SIP Trunks, FreePBX: @scottalanmiller We still use the legacy wholesale thing. It probably wasn't as often as every 3 months, I'm sure I'm exaggerating a little. Oh okay, that's what we are using, too.

For another site I manage, I don't use stun and I also have ALG/SIP disabled on SonicWall but it is vlaned.