@JaredBusch said in Yealink T46S Missing Opus Codec in 66.84.0.15 Firmware: @scottalanmiller said in Yealink T46S Missing Opus Codec in 66.84.0.15 Firmware: In other firmware revisions, Opus is in the codec list. But now it is missing. This is not what you stated in your opening post. You clearly stated several updates. @scottalanmiller said in Yealink T46S Missing Opus Codec in 66.84.0.15 Firmware: Anyone noticed that several firmware updates for Yealink T4xS phones seems to be missing the Opus codec It's been multiple for us, not just this one. Older ones have had the issue, then we update and Opus appears. But now we update and it disappears again. So yes, several just as I said. I never said "several consecutively."

@JaredBusch said in Make Yealink Ring While on the Phone: @scottalanmiller said in Make Yealink Ring While on the Phone: If you have Yealink T46S phone, and you are talking on the phone, instead of making it do a call waiting beep, can you make it ring normally? A bit odd, but there is a reason for it Not to my knowledge. It was supposedly added as a feature request a few years ago, and I have not noticed it in a firmware release note. That would explain why I have never seen it come up. Not that anyone has ever wanted it previously.

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

@JaredBusch said in Major outage at VoIP.ms today: @scottalanmiller said in Major outage at VoIP.ms today: Wait, I think we are talking on a voip.ms line right now, weird. The problem is inbound termination from upstream of them. Everything else works. Also not all inbound providers are affected. Okay, that makes sense then.

@Phil-CommQuotes said in Provide Foreign Toll-Free Number to US Call Center: @JaredBusch @wrx7m Hope I responded right but yes we can get Toll Free numbers a la carte anywhere in the world (well almost anywhere!). Mexico yes! Hit me up Message sent

Yeah, outdoor speakerphones arent a popular item.

@scottalanmiller said in Anyone ever use Univerge Blue by NEC for SIP: @JaredBusch said in Anyone ever use Univerge Blue by NEC for SIP: I refuse to use Skyetel because of their bullshit pricing practice. He's seen the pricing, he's converted already, lol. I’m not changing my opinion on unpublished pricing just because you like it and they pay you to advertise here.

@JaredBusch said in Call Out from FreePBX Conference Room: @scottalanmiller said in Call Out from FreePBX Conference Room: @JaredBusch said in Call Out from FreePBX Conference Room: Hit transfer, hit the conference extension, dial the participant code, speak their name, hit the transfer button again. The idiot will be in the conference. I've tried that, always seem to get stuck with the "enter a code" issue. You are going to force me to test those instructions aren't you? Tested what I typed above.. Works perfectly.

Well I tried maintenance mode - out of service for 10 mins, then back on - no go. I put the password back into the system - bam.. damn thing is registering again.

@scottalanmiller said in Getting Familiar with Sangoma S500 running with FreePBX as back end. . .: @JaredBusch said in Getting Familiar with Sangoma S500 running with FreePBX as back end. . .: @JasonMinard if you have not been on the FreePBX community today, you are simply out of luck with the Sangoma phones. https://community.freepbx.org/t/accessing-rest-contacts-from-horizontal-key-within-call/56374/10 Well that really sucks. Some of the REST-APP functionality is neat. But I find it slow to use.

@Dashrender said in All New VoIP Handsets for PBX Migration?: @DustinB3403 said in All New VoIP Handsets for PBX Migration?: @Dashrender said in All New VoIP Handsets for PBX Migration?: @scottalanmiller said in All New VoIP Handsets for PBX Migration?: @Dashrender said in All New VoIP Handsets for PBX Migration?: @scottalanmiller said in All New VoIP Handsets for PBX Migration?: @Dashrender said in All New VoIP Handsets for PBX Migration?: @scottalanmiller said in All New VoIP Handsets for PBX Migration?: @Dashrender said in All New VoIP Handsets for PBX Migration?: @DustinB3403 said in All New VoIP Handsets for PBX Migration?: You could also opt to purchase a few $25 poe injectors for the few phones that are required to have power all of the time and feed that from your UPS. The cost difference for Poe switch vs non is 400$.... over 48 phones that’s less tha $10 ea Let’s move on from POE But that's way more than wall warts typically. And the comparison is not against a normal switch, but against no switch. You don't need any switching at all beyond what you already have unless you go PoE, right? That is not right. I'm 50% or more laptops. So I would need at least another 30 ports, but probably more like 40 ports to include phones in random locations. Where you don't have ports today? It's not that you are laptops. I think you are trying to imply that your laptops are wireless? I may or may not have a wire there - but I definitely don't have a switch port connected to those wires. I replaced switches a while ago and didn't buy more than I needed for the APs, Printers, and Desktops. yes the laptops are 100% wireless. I see. Wherever we have a large amount of laptops, we wire them up for performance and stability. My users have shown that when they have to manage plugs on a daily basis, they damage them regularly. We're lucky we don't have more issues with power connectors. So eliminate the responsibility of having to plug things in. Get a softphone and have people start using that wholesale. huh? not sure where this came from? today users move from station to station, only plugging in their power brick to power their laptops. They just use the phone at the desk they are sitting at that time. I was responding to this comment. It didn't start from me, or you. Both of us responded to Dustin's topic.

@Dashrender said in Skyetel Inbound SIP Trunk on FreePBX: @JaredBusch said in Skyetel Inbound SIP Trunk on FreePBX: @scottalanmiller said in Skyetel Inbound SIP Trunk on FreePBX: @JaredBusch said in Skyetel Inbound SIP Trunk on FreePBX: @scottalanmiller said in Skyetel Inbound SIP Trunk on FreePBX: Locking a port to a single IP is a trivial task for any gear, even consumer. I wouldn't go that far. I don't know much consumer gear that doesn't make that easy. Super easy tomport forward? Yes. Able to restrict to a specific source IP? No. eh - if you're only open for the trunk provider, then you can likely lock to one or a few IPs. if you need mobile support - that's another story. How? Where? Been a while since I was in a consumer router, but port forwarding screens had nothing about source IP.

@JaredBusch said in Alternatives to OpenVPN for FreePBX on cell phone...: @scottalanmiller said in Alternatives to OpenVPN for FreePBX on cell phone...: @JaredBusch said in Alternatives to OpenVPN for FreePBX on cell phone...: There has never been a promise or timeline made for the mobile apps. Anyone expecting anything on that front is operating in their own little fantasy. That's the main use case of softphones, though. Like 95% I would guess. Softphones for the desktop are way more niche. I totally disagree. Softphone on the desktop is by far the largest user base thanks to call centers. Softphone on mobile is a far second to that. Maybe overall, but for FreePBX? FreePBX is pretty rare in call centers, AFAIK.

@scottalanmiller I was just about to ask if its a php setting that needed to be changed.

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 VOIP Provider: Skyetel: Well then, I stand corrected. I will add this is not something you have ever hinted at doing I. The past. Not mentioned a setup for (I would like to see that as I have no opportunities to use it yet). I only manage the phone bit of it, had nothing to do with the writing of the application. But it is neat what it does. The "users" (employees on our side) need to do a bit of fancy calling on behalf of their customers and the application handles setting everything up. It is quite involved. It has to be anonymous to one side, and has to handle non-voip scenarios on the other. So the application actually calls both parties most of the time. And handles automated recording and data collection and fills in a database with details and a copy of the call to go into a report to the customer.

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