Solved FreePBX 13 Endpoint Manager problem
-
@DustinB3403 said in FreePBX 13 Endpoint Manager problem:
Do you know what model firmware is on these phones?
"Starting with firmware V70, Yealink has changed the way configuration files must be generated. If you are using V70 or newer firmware on your devices set Config Style to v70 Style. T4XG and W52P devices will automatically use V70 style configs regardless of what you set here, since they only support Firmware V70."
This one shows you did not even comprehend the issue.
Next.
-
@JaredBusch I'm asking you for detail, as your OP on the FreePBX forums doesn't provide enough information.
If you're not willing to provide an answer, then I'm done responding to you.
-
-
The peanut gallery above aside, on to the problem at hand.
making changes in the GUI seems to be not working.
Has anyone else purchased the EPM and have a minute to make a new Yealink template and try to modify the basefile for it?
Now back to the peanut gallery, I could actually program all the config files by hand. it is quite easy. I have done it many times in the past on Elastix distros because that EPM sucks. But the point of using the commercial EPM inside FreePBX is to get everything in a GUI so the users can make basic changes themselves. It is not something that IT should be doing once in production.
-
@JaredBusch This still ignores the detail I was asking you for, configuring by hand I get is not the goal, hence the point in purchasing the EPM software.
The config settings have an issue accepting the changes from the GUI if the phones profiles aren't confirmed for v70 style.
Hence, what firmware is on the phones?
-
@DustinB3403 said in FreePBX 13 Endpoint Manager problem:
@JaredBusch This still ignores the detail I was asking you for, configuring by hand I get is not the goal, hence the point in purchasing the EPM software.
The config settings have an issue accepting the changes from the GUI if the phones profiles aren't confirmed for v70 style.
Hence, what firmware is on the phones?
Again, if you had any clue what you were trying to dis me about you would already know the relevant answer.
Yealink released the v70 firmware in 2012. The T4X series has never had firmware less than v70+.
And again that has nothing to do with the GUI not working. As the example posted on the FreePBX community clearly shows, I clicked on an existing config option and changed the value. There is nothing else to do or specially configure. The GUI then did not apply said change.
Hence the reason to verify my result with someone else on the same or similar version prior to calling it a bug and opening an official issue.
Keep trying.
-
-
-
@JaredBusch Agreed, from what's been discovered I honestly think logging a ticket/bug with FreePBX is your best bet. I personally have never used it.
-
@zuphzuph said in FreePBX 13 Endpoint Manager problem:
@JaredBusch Agreed, from what's been discovered I honestly think logging a ticket/bug with FreePBX is your best bet. I personally have never used it.
Oh, I agree. But I was driving for 4 hours and thought to cross post for more eyes on the issue.
The misguided butthurt just made the last hour of my drive more fun is all.
-
And bingo. User error. This is why i post before complaining about bugs.
Somehow the config style option was not selected for either style. I clicked it to current style and now everything updates.
-
FreePBX issue created for the actual problem.
http://issues.freepbx.org/browse/FREEPBX-13040 -
And the issue is now resolved
-
@JaredBusch said in FreePBX 13 Endpoint Manager problem:
And the issue is now resolved
Glad to hear it. No better way to kick off a weekend!
