@akiliss said in Auto provisioning server for yealink T21P: Hi @JaredBusch, Thank you very much for your reply, I tested a same configuration on Friday and it worked fine with TFTP. Now Im trying to configure this with HTTP or HTTPS. Thanks again You can use tftp if you want. It works just fine. My issue with it is the lack of security.

Nope. ####################################################################################### ## Network Internet ## ####################################################################################### static.network.ip_address_mode = static.network.span_to_pc_port = static.network.vlan.pc_port_mode = static.network.static_dns_enable = static.network.pc_port.enable = static.network.primary_dns = static.network.secondary_dns = static.network.internet_port.gateway = static.network.internet_port.mask = static.network.internet_port.ip = static.network.internet_port.type = ##V83 Add static.network.preference =

I just found this. I guess it is called "Camp" or "Call Back" https://en.wikipedia.org/wiki/Automatic_callback Not I can start researching how to do it with VitalPBX. The conversation here, on this topic was instrumental in getting me on the right path for a solution. Thank you all! We can keep talking about it too, if you want

@JaredBusch said in Prerequisites for Yealink YDMP Install: @DustinB3403 worked with this I believe... I did, but the install process was pretty easy. https://drive.google.com/open?id=1-2hh-5N-vg-s2w8MS3GVaqDRVetLmbpp

@JaredBusch said in Server 2012R2 DHCP reservations problem with my VOIP equipment?: I never use reservations for phones. Specifically with Yealink phones, I set the DHCP hostname value in the config file. So when I am on the network, I can easily just ping ext103.domain.local and shit.. Or If I look at the DHCP server lease list, I see the hostnames listed as ext101, ext103, etc. Love this idea

The IT benefit to this entire thing is, by enabling this feature, IT will now have a backup of the configuration of all the phones. Even if a user changes a button. Now a phone can die and IT will simply change the MAC on the provisioning server and put the new phone on the desk. To the business, the benefit is to let users control their own buttons without IT getting involved. Buttons can easily be programmed by a user simply holding it down until the menu pops up. It takes very little instruction to teach users to pick Speed Dial or BLF and enter the number or extension. For most small shops, this doesn't matter in the first place. They rarely change anything. But for an organization over 20, it is very common to have users all needing different configurations on their phone buttons. Their Boss, their Queue Pause, their specific parking lots, etc.

@JaredBusch said in FreePBX / Yealink t42s / call park configuration best practice ...: The best use of parking is simply blind transfer via DSS key directly to a specific slot. No one wants to waste time and a button with a park key that you then need to wait for an announcement to know where the call went. That makes much more sense. I think I put the blinders on and focused too much on replicating the old system without thinking if there was a better way.

@scottalanmiller said in Yealink t27g vs t42s: @BraswellJay said in Yealink t27g vs t42s: Do you generally use the Endpoint Manager or any of the other commercial modules? There is no commercial module that we use regularly. But we've got some clients that use many. There are pretty much zero reasons not to add SysAdmin Pro for $25. Getting the email config in the GUI and the ability to tell the web server to use authentication for the config files saves more time than the cost to do it yourself manually.

@JaredBusch said in Yealink T46S Missing Opus Codec in 66.84.0.15 Firmware: @Dashrender said in Yealink T46S Missing Opus Codec in 66.84.0.15 Firmware: It sounds like @lansalot might have been pushing an old config file to Yealink phones with newer firmware, and that old style config MIGHT have been slightly incompatible - and caused the issue. which @lansalot was able to resolve, not by completely modernizing his config files, but instead by adding a few lines to expressly bring OPUS back into the config. That should not matter. If the config is old and does not have the setting specified at all, it should go to the default value. Sure, of course you'd like to think so - but bugs do happen... and it appears that it is in this case.

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

Yeah, outdoor speakerphones arent a popular item.

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

@mgbolts said in FreePBX Contact Manager to Yealink Address Book: Another update to the script. https://github.com/mgbolts/fpbx-yealink-xmlcontacts/blob/master/cm_to_yl_ab_L2.php Updates are as follows: a) I have added the ability to customise your own number labels. eg. I did not like cell or internal being the default label from fpbx. I wanted Mobile and Extension. b) I wanted the ability to choose the display order for the set of numbers for each name. The issue was that it was random and I also wanted my chosen number to be the default number displayed against the name. This was particularly where I pulled in to the internal contact list. In this case, I wanted the extension to be the default and not some random number like cell etc. c) It now has the ability to use the number as input (the default) or use the auto generated E164 format from FPBX. This may not be useful for most users, but is helpful where you have users in more than jurisdiction and each country has its own int dialing prefix, eg. AU is 0011 and other countries use different prefixes. It does require you to select the correct country when creating the contact number in fpbx. Further instructions in the code. I have also updated my original script to handle most of this. The sub sort by label order is not yet impelmented.

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

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

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