Endpoint Manager will not change basefile for Yealink phones

configuration
Tags: #<Tag:0x00007f702af51f58>

(Jared Busch) #1

I have a newly installed system that I am trying to setup the endpoints for and I am having problems with EPM. The basefile edits are not doing anything.

I can click a linked item that I want to change such as this.

But nothing changes. Previous installations have always shown the changed items in red once the change is made. This is like nothing is ever happening.


(Jared Busch) #2

I have now tried with multiple bowsers and rolled the version back with now change in behavior.

I really need to set these options.

Any recommendations?


(Tony Lewis - https://bit.ly/2SbDAyc) #3

Open a bug report at issues.freepbx.org


(Jared Busch) #4

@tonyclewis i certainly will but simply opening an issue for every little thing is silly.

This is why i post first. This issue is resolved and there is a bug, but not with the basefile edit.

The bug is that i was able to create the template without selecting new style or old style config. so the basefile had no idea how to save things.

Somehow the config style option was not selected for either style. I clicked it to current style and now everything updates.
0_1472588599372_upload-70a596e4-39dd-4fbd-9cfd-5f928035bb4c


(Tony Lewis - https://bit.ly/2SbDAyc) #5

OK well if you do not open a ticket for things then they wont ever get fixed. We do not scan forum post for bug reports. That is why we have a public bug tracker.


(Rob Thomas) #6

And that’s excellent, and we thank you for it. But, as @tonyclewis said, we really need a ticket open in the bug tracker, so it can actually get fixed. A lot of people just go and open tickets without posting in the forums, and that just causes extra load as we go through them going ‘Ummmm, that’s not a bug, they should have posted in the forums first’.


(Jared Busch) #7

The point was to post an issue now that we know what the issue is. Because it was human error (me missing the click on the firmware style) that caused it to happen.


(Jared Busch) #8

And issue created.
http://issues.freepbx.org/browse/FREEPBX-13040


(Todd Lee) #9

Thanks for posting what the underlying issue was and how to fix. This caused me lots of grief yesterday while onsite at one of my clients.


(Jared Busch) #10

And the issue is fixed! Thanks to the team for working it.