@NerdyDad said in Yealink DECT dongle for T41S and T42S:

Does the cordless and the deskphone both share the same extension? If so, this would be great for my wandering receptionist.

These are independent units so no. But you can put the same ext on them if the PBX supports it.

So with FreePBX and PJSIP based extensions you can have multiple devices registered all to the same ext.

@eaglex said in FreePBX Contact Manager to Yealink Address Book:

Hello,

First of all, let me thank you for your wonderful work. This made our lives much easier...

If you don't mind, I would like some help: I'm running this script on 2 FreePBX machines, both are practically the same. On one machine, I have no problems viewing contacts with more than one number (In both the XML file and on the phone itself).
However, on the other machine, I can only see on phone number for each contact, even if they have more than one phone number, again, it happens both when I visit the XML file directly from a browser and on the phones.
I can't think of any difference between both the pbx's.

I'd appreciate your help and I'll be happy to provide additional details, logs, info, etc..

Thanks a lot!

My fingers are still crossed for a solution 😞

Thanks!

@JaredBusch said in How to add a sip notify command to FreePBX 14 to force Yealink phones to reboot:

After everything reloads, you can open up a ssh session and tell a phone to restart like this.

asterisk -rx "pjsip send notify restart-yealink endpoint 110"

You can also do more than one phone at a time. Just space delimit them .

asterisk -rx "pjsip send notify restart-yealink endpoint 103 108 110"

I would prefer the phones to go out to 0.us.pool.ntp.org and 1.us.pool.ntp.org for all of their time sync issues but they appear to be having some issue.

Of which I am unable to determine what that could be with the error provided.

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

@DustinB3403 said in Anyone looked at Yealink DaaS - Device as a Service:

One thing you haven't taken into consideration though - is the time value of money.

But I have. It takes moments to do the math that this is a bad idea. In any case we're discussing a business who is installing a new phone e system and phones.

So the business has the money, but would it be better to expense with however many thousands upfront? At least in my business they would opt to make the spend today, and then they'd write it off over the usable life of the equipment.

With that, yes it's still a capital expense. And hopefully that expense was planned for and already budgeted.

That had been the typical situation here until recently. Much to my utter amazement we've leased two pretty major pieces of gear - CT machine and our entire printer fleet. I know in the case of printers, we'll be saving money over what we were paying our previous provider, the purchase option might have saved us a small amount, but we would have to have taken out a loan, and the interest would have made the end spend nearly the same.

Mixed results.

Web based connections to the provisioning server work and the web based address books now work.

But TLS for the SIP connection is not working right.

But I ran out of testing time..
More to come.

I personally have refused to comply with GDPR. There's a weird irony in that so many non-EU companies (specifically American) felt the need to comply just because, as I saw on SW oh no, the EU gonna come after you somehow! yet when the EU implements a pain in the butt copyright law, suddenly "well, those laws don't apply to us." So I moved my company location from Czech Republic to Russia, and I'll sell to EU citizens anyway. I say, bring it on:

0_1537911046859_VMKrIq7.gif

@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

The purpose of the "ECHO" is to prevent the other party from hearing himself (echo). If a user is using headsets, then there is no need for AEC since there will be no echo generated on his side. In this case it might be better to disable "ECHO" to avoid unnecessary audio filtering and also to save CPU. A user that is using hands-free mode, MUST have "ECHO" enabled to prevent all other participants from hearing themselves. If ""ECHO" is enabled but still echo could be, it means that the acoustic echo cancellation software that is running is not robust enough to handle the echo. Following is a nice blog series on the principles and challenges of acoustic echo cancellation.

@jaredbusch The model config file also has this option.

0_1535737838531_chrome_2018-08-31_13-50-20.png

So I "should" be able to use the "all" setting and have this work there as well, yet it doesn't seem to.

So this has been changed in their newest release 2.0.0.25 (not sure if it's publically available), and while the credentials are no longer in plain-text there are a few things you lose the ability to do.

Namely to tell if any given used is logged into a device, and secondly to sign in/out as a user on any given device.

I've provided my feedback to Yealink and hope to hear back soon. Neither of the above 2 issues are deal breakers, as the bigger goal is to be able to set configuration options, screensavers, time servers etc and have the user deal with the login.

Especially since the "Web Sign in" functionality is so simple, there is little reason to need the ability to sign in for a user.

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

github updated. files renamed a bit. Still a work in progress, but things working much better.

0_1533163657304_1cb7dbcf-38f3-48da-a102-fc1f7348fe17-image.png

The downside to this is that the FreePBX team simply implemented the no reboot flag to the existing reboot-yealink command. unlike the multiple commands for the Sangoma phones.

0_1543282841223_bc79c9df-ec75-492b-a23b-d976e99dd85a-image.png

So this means, you have no way to reboot Yealink phones at all with a built in sip notify command.

@dustinb3403 said in CentOS 7 Telnet Port Change:

Cockpit isn't included in CentOS 7 by default (is it?. . . .)

Not with a minimal install. With the problem you are having, I was assuming the issue was with port 9090.

@dustinb3403 said in CentOS 7 enabling Telnet:

And I got the port forwarding to work.

firewall-cmd --zone=public --add-forward-port=port=9090:proto=tcp:toport=23

I can now telnet to my server on port 9090 (which forward to 23).

Nice!

selinux is disabled, and I have all of the ports listed in their documentation added to firewalld. . .