Yealink Device Management Platform
-
@scottalanmiller said in Yealink Device Management Platform:
@dustinb3403 said in Yealink Device Management Platform:
@scottalanmiller it's free.
How do you get it? On their website they just say to contact sales.
http://support.yealink.com/documentFront/forwardToDocumentFrontDisplayPage
DIRECT LINK
http://support.yealink.com/documentFront/forwardToDocumentDetailPage?documentId=243
-
My devices are never local so I have never bothered with this.
-
I guess I could attempt some type of magic to point to a hosted system with DHCP options.
-
@jaredbusch said in Yealink Device Management Platform:
My devices are never local so I have never bothered with this.
That's the big thing that never made me spend time looking into it, I wonder if it could be good enough to overcome the pain of setting it up.
-
So the setup is pretty straightforward, but some of the naming of files is a bit weird.
On the CentOS7 server, ports 22,25,443,3001,3306 and 9090 are open. Which apparently are the same ports required for the phones and this server to find each other.
-
@dustinb3403 said in Yealink Device Management Platform:
So the setup is pretty straightforward, but some of the naming of files is a bit weird.
On the CentOS7 server, ports 22,25,443,3001,3306 and 9090 are open. Which apparently are the same ports required for the phones and this server to find each other.
Weird. You are running it on premises, I assume?
-
@scottalanmiller in this case, yes, all on the same subnet as well.
Just trying to simplify the provisioning process a bit, update firmware etc.
-
@dustinb3403 said in Yealink Device Management Platform:
@scottalanmiller in this case, yes, all on the same subnet as well.
Just trying to simplify the provisioning process a bit, update firmware etc.
Yeah, I get it, just wondering what the use case experience is to tell if it is worth putting more effort into.
-
@scottalanmiller well setting up the server was the easy bit, it's determining why the phones and server aren't communicating that is the challenge.
Corrected as I realized I hadn't completed my thought. . .
-
So I'm still trying to figure this out, and I'm thinking im losing it.
This is in the documentation:
Deploying the Devices
- Connect devices into the network.
- The devices perform mutual TLS authentication using default certificates.
- The devices obtain the provisioning server address from the DHCP option 66, 43, 160 or 161.
The DHCP option value must meet following format:
http://<IP address>:<28443>/dm.cfg (for example: http://10.2.62.12:28443/dm.cfg)
Based on that, I would assume I can use anyone 1 of the four DHCP options listed, is there any reason I would need all four?
-
The deployment guide can be found here.
-
@DustinB3403 ,
I know you got this all working. How is it now that oyu have used it more?From reading the Skype for Business pages of hte Yealink site, it seems that this is needed to customize the phones.
-
@JaredBusch said in Yealink Device Management Platform:
@DustinB3403 ,
I know you got this all working. How is it now that oyu have used it more?From reading the Skype for Business pages of hte Yealink site, it seems that this is needed to customize the phones.
So in terms of a solution, it works well enough. We had a trial for a year (the license something really cheap we were quote $122 / ~30 phones / 1 time).
It's mostly a convenient way login to a phone, pull performance stats from it as well as push some configuration options too it.
-
@DustinB3403 said in Yealink Device Management Platform:
@JaredBusch said in Yealink Device Management Platform:
@DustinB3403 ,
I know you got this all working. How is it now that oyu have used it more?From reading the Skype for Business pages of hte Yealink site, it seems that this is needed to customize the phones.
So in terms of a solution, it works well enough. We had a trial for a year (the license something really cheap we were quote $122 / ~30 phones / 1 time).
It's mostly a convenient way login to a phone, pull performance stats from it as well as push some configuration options too it.
Ah, well if you dump the config of a Yealink phone with the Skype for Business firmware, there are almost no options in the dump and settings made manually apparently get reset with the device resyncs.
So looks like it iwll have to be that thingor nothing unless I can find some settings in Office 365 for it.
-
@JaredBusch said in Yealink Device Management Platform:
@DustinB3403 said in Yealink Device Management Platform:
@JaredBusch said in Yealink Device Management Platform:
@DustinB3403 ,
I know you got this all working. How is it now that oyu have used it more?From reading the Skype for Business pages of hte Yealink site, it seems that this is needed to customize the phones.
So in terms of a solution, it works well enough. We had a trial for a year (the license something really cheap we were quote $122 / ~30 phones / 1 time).
It's mostly a convenient way login to a phone, pull performance stats from it as well as push some configuration options too it.
Ah, well if you dump the config of a Yealink phone with the Skype for Business firmware, there are almost no options in the dump and settings made manually apparently get reset with the device resyncs.
So looks like it iwll have to be that thingor nothing unless I can find some settings in Office 365 for it.
Yeah, this worked well enough. I had no complaints with it. And since we're going full tilt with SfB I'll be looking to purchase a license for this.
-
@DustinB3403 said in Yealink Device Management Platform:
Yeah, this worked well enough. I had no complaints with it. And since we're going full tilt with SfB I'll be looking to purchase a license for this.
Oh you were using it because of SfB? I guess I missed that part.
How hard was it to get a trial license?
-
@JaredBusch said in Yealink Device Management Platform:
@DustinB3403 said in Yealink Device Management Platform:
Yeah, this worked well enough. I had no complaints with it. And since we're going full tilt with SfB I'll be looking to purchase a license for this.
Oh you were using it because of SfB? I guess I missed that part.
How hard was it to get a trial license?
You get a trial when you install it.
-
@DustinB3403 said in Yealink Device Management Platform:
@JaredBusch said in Yealink Device Management Platform:
@DustinB3403 said in Yealink Device Management Platform:
Yeah, this worked well enough. I had no complaints with it. And since we're going full tilt with SfB I'll be looking to purchase a license for this.
Oh you were using it because of SfB? I guess I missed that part.
How hard was it to get a trial license?
You get a trial when you install it.
Well hopefully I won't be too drunk after D&D tonight to get something going.
-
So for a SfB phone with no Yealink Device Management set up, this is all the phone has when dumped.
### This file is the exported MAC-all.cfg. ### For security, the following parameters with password haven't been display in this file. ###static.account.1.password = ###static.account.sfb.1.password = features.power_saving.off_hour.idle_timeout = 5 features.power_saving.office_hour.idle_timeout = 15 phone_setting.inter_digit_time = 5 sfb.hot_desking.enable = 0 sip.btoe.enable = 0 sip.btoe.pairing_mode = 1 voice.handfree.spk_vol = 15 voice.handfree.tone_vol = 9 voice.ring_vol = 2 ### Static Configuration ### static.account.1.auth_name = [email protected] static.account.1.codec.pcmu.priority = 1 static.account.1.codec.pcma.priority = 2 static.account.1.codec.g729.priority = 3 static.account.1.codec.g722.priority = 0 static.account.1.display_name = User Full Name static.account.1.enable = 1 static.account.1.label = User Full Name static.account.1.sip_server.1.address = domain.com static.account.1.user_name = username static.account.sfb.1.server = [email protected] static.account.sfb.1.user_name = [email protected] static.auto_provision.server.username = PlcmSpIp static.features.device_update_auto.enable = 1 static.network.internet_port.gateway = 192.168.100.1 static.network.internet_port.ip = 192.168.100.222 static.network.internet_port.mask = 255.255.255.0 static.network.internet_port.type = 2 static.network.primary_dns = 192.168.1.200 static.phone_setting.phone_lock.lock_key_type = 10 static.voice_mail.number.1 = sip:[email protected];opaque=app:voicemail -
This thing requires 8 cores and 16GB RAM on CentOS 7.
My home KVM box doesn't have enough.. so look how bad it runs.
Constantly puking out of memory errors.
