Side Car buttons

I was already told no. apparently the code used has to manually create 24 buttons and then hide the ones that you don't see so that when you choose 'add a button' it lets you see what was already in the form. So all those form rows already exist and are just hidden with their hidden values. If anyone knows of some universal javascript that is more dynamic and doesn't require the creation of pre-made tables and forms (must also be written in perl using webmin plugins) speak up now or forever hold your peace :)

it should be able to be done.. I'm not following the request for universal JavaScript since with out the code or being able to see what your talking about its not possible to answer your question.

Since this is all encrypted Alex is the one that needs to take care of this..

ALEX ..?

George

Anyone working on getting this to work for ALL buttons..?

This will require some work. Is 32 a magic number?

for that particular sidecar.. then you have aastra's 3 page sidecar which can be stacked up to 3 bringing the total button count to 180. polycom phones let you stack 3 14button sidecars.

no more like 76 to cover all options.. the 509 is a 12 line phone and can handle 2 side cars at 32 buttons each..

Thanks
George

you wont be able to template that 2nd sidecar due to linksys' completely stupid way of implementing it. Instead of making the first button of sidecar #2 be button 33, they do something completely moronic which makes a universal template impossible.

the first sidecar is called UNIT_1_BUTTON_1 through button 32
the second sidecar is called UNIT_2_BUTTON_1

which means that the second sidecar would have to be programmed manually on that phone. Its impossible to template this .. and before someone suggests 'make it so that if the phone is a linksys phone it knows to do UNIT_2 on buttons greater than 32'.. understand that the phone models themselves are also variables derived from models.txt.

Its an impossible arrangement they created...

oh forgot to mention that the buttons actually on the phone do BLF in yet a completely different manner than the expansion module too.

nearly all the other manufactures (including cisco proper) just keep increasing the button number as expansion modules are stacked on.

the sidecars use the UNIT_1_BUTTON_1 approach
while the buttons on the phone themselves do it Extended_Function_3_

as a 'workaround' I created a 'speeddial' template for the sidecar that really was still more BLF's that wrote out UNIT_2 instead of UNIT_1 but you're in a situation where people have to be told how to cludge this out by setting all the car2 buttons to type speeddial. its clearly not self-explanatory or intuitive.

Its probably less confusing to program it through the phones web interface if theres 2 modules instead of just 1.

no that's not exactly true.. it can be done simply enough by added a drop down for a second sidecar and pulling a script to write to UNIT_2

>> as a 'workaround' I created a 'speeddial' template for the sidecar that really was still more BLF's that wrote out UNIT_2 instead of UNIT_1

I did the same, so you can BLF to car 1 and SP to car 2..

>> Its probably less confusing to program it through the phones web interface if there's 2 modules instead of just 1

lol like that's going to happen... better if you noticed if you provision for side car 1, and then provision for sidecar 2 the settings for 1 remain.

So again the real problem is the limitation of MTE to be able to do the minimum of 44. Then again it can be done if MTE had the ability to set sidecar 1 and 2 as stated above.

Its really a matter of someone with the code taking the time to write it..

George