Yealink Phone Configuration
-
@jaredbusch said in Yealink Phone Configuration:
@dustinb3403 said in Yealink Phone Configuration:
Why would the common not work for that. . . grr.
It might. I simply didn't test there, and was looking for differences.
Moved it to the
y000000000028.cfg
and just defaulted my phone. -
Totally ignored all of the settings.scratch that... saved on wrong terminal window.. rebooting again.
-
Worked just fine
-
@jaredbusch said in Yealink Phone Configuration:
Worked just fine
Where are you setting this, for the model config?
-
@dustinb3403 said in Yealink Phone Configuration:
@jaredbusch said in Yealink Phone Configuration:
Worked just fine
Where are you setting this, for the model config?
I have used both the MAC.cfg (
001565abcdef.cfg
) and the common configy000000000028.cfg
(28 because it is a T46G). -
So I have the config templates from here
I guess it's not possible to upload a common template into their DMP software. . . ?
-
@dustinb3403 said in Yealink Phone Configuration:
So I have the config templates from here
You have SfB firmware? I do not have that anywhere. no way to test. My phones are all the normal firmware path.
@dustinb3403 said in Yealink Phone Configuration:
I guess it's not possible to upload a common template into their DMP software. . . ?
I have no idea what this means.
-
@jaredbusch said in Yealink Phone Configuration:
@dustinb3403 said in Yealink Phone Configuration:
So I have the config templates from here
You have SfB firmware? I do not have that anywhere. no way to test. My phones are all the normal firmware path.
@dustinb3403 said in Yealink Phone Configuration:
I guess it's not possible to upload a common template into their DMP software. . . ?
I have no idea what this means.
Yes, we use SfB. Yealink's Device Management Platform.
-
-
@dustinb3403 said in Yealink Phone Configuration:
@jaredbusch said in Yealink Phone Configuration:
@dustinb3403 said in Yealink Phone Configuration:
So I have the config templates from here
You have SfB firmware? I do not have that anywhere. no way to test. My phones are all the normal firmware path.
@dustinb3403 said in Yealink Phone Configuration:
I guess it's not possible to upload a common template into their DMP software. . . ?
I have no idea what this means.
Yes, we use SfB. Yealink's Device Management Platform.
I know what DMP was. I have no idea what you mean by upload a common file.
-
@jaredbusch oh, the common config file has the field waiting to be populated for custom screensavers.
-
@dustinb3403 said in Yealink Phone Configuration:
@jaredbusch oh, the common config file has the field waiting to be populated for custom screensavers.
Okay, seeing your screenshot, basically it does not matter where you put the info.
In the end, 100% of the config can be in the MAC file, or it can be split to the common and the MAC file.
That tool will likely generate 2 files, the common and the MAC. So simply putting it in the common means you will not have to re-enter it a million times.
-
The goal (in my head) would be to quickly and without having to edit every config file would be to have client branding quickly pushed to every phone (based on the model) so that it can rotate through a few stills that were made for the client.
Having to use the MAC config file (works) but it would require making changes to potentially lots of files for this.
Hence the hope the common config file supported this.
-
@dustinb3403 said in Yealink Phone Configuration:
The goal (in my head) would be to quickly and without having to edit every config file would be to have client branding quickly pushed to every phone (based on the model) so that it can rotate through a few stills that were made for the client.
Having to use the MAC config file (works) but it would require making changes to potentially lots of files for this.
Hence the hope the common config file supported this.
The tool has a group also, that does not actually relate to a specific config file. likely things there are put in the MAC file.
-
@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.