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

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 Where Does a 66 Block Get Its Name:

@Dashrender said in Where Does a 66 Block Get Its Name:

OK because of comments I looked more closely at the picture - I've never seen anyone do loops like that before - I guess it works though.

Looks like they had a pretty common for pots but the way they were made ive never seen that done

Agreed - hell, this could be in someone's home - just an odd one is all.

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

@JaredBusch said in Getting Familiar with Sangoma S500 running with FreePBX as back end. . .:

I've given up on EPM for anything complicated with non Sangoma phones.

Same, I don't find it to be valuable for us.

@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 Ok thanks for the explanation

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.

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

@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