55i LED not working with Day/Night XML script

vtofa
Posts: 39
Member Since:
2008-10-27

I have been battling the XML scripts to try to get the red indicator LED to work with my 55i when the phone is in Night mode. No go.
Any ideas as to how I could get it to work?
thanks
tim



aastra1
Posts: 287
Member Since:
2006-11-06
Check if the key attached to the script has been detected

Tim,

If you have upgraded the scripts from the previous version, the mechanism to find which key is attached to the script has changed, now it is automaticaly discovered during the self-configuration, so try to logout and login again on the same phone. It should work.
Also some users identified an issue with the synchronization mechanism at http://trixbox.org/forums/vendor-forums-certified/aastra-endpoint... which may be another reason why it does not work for you.

aastra1

--

---
aastra1
Aastra XML scripts 2.3.0 now available



vtofa
Posts: 39
Member Since:
2008-10-27
This is a new install. It

This is a new install. It likely isn't with the synch mechanism, either, as none of the buttons ever lights up, for any of the XML scripts, and this is a test system with just one phone. The only time the buttons light up is if they are locally set, such as local DND.

Its likely something simple that I am overlooking because of inexperience.

Thanks
Tim



vtofa
Posts: 39
Member Since:
2008-10-27
Works now

I had a copy of trixbox.prf on an other server. I copied the 55i section from there, and stuff started working.
I'm not sure what made it work, though.
Thanks for your help.
Tim



olivier
Posts: 11
Member Since:
2006-11-19
We have some important

We have some important problems as well with Aastra 2.2.1 patch2 XML scripts.

Most of them are coming from bugs in the phone firmware (latest 2.5.1.41 or .2000). it seems that 57i with Aastra scripts are not usable if the memory is loaded with keys config from a 560M extension module.

As soon as we try to logout with a half loaded extension module, the phone crash. deleting the keys from the extension module solve the problem.

There are other problems like no possibility to dial after a reboot, or lights not working if using an extension module.

When the 57i memory is loaded with a big setup, it seems that things begin to crash in the phone. Sometimes, the phone reboot himselft.

So at this moment, Aastra scripts have to be considerd experimental and used carefully, to avoid disasters at client sites. The 57i firmware needs to be considered beta stage, for xml scripts support.

I hope this will change fastly as we begin to deploy those scripts at end user sites.



robeerski
Posts: 70
Member Since:
2008-01-30
Indicator lights not functioning

I too am having a problem getting the indicator lights to light for Day/Night, Call Forward and Do Not Disturb. I am using the latest firmware 2.5.1.41 and I am also using the latest version of the XML scripts 2.2.1. Any ideas on how to fix this would be greatly appreciated. my BLF buttons do work fine though. I know that there was a race condition in the past but I think that was with the XML-Scripts ver 2.1.1 and I think it was fixed with ver 2.2.1 but I don't fully remember. Is this an incompatability with the new firmware possibly?



robeerski
Posts: 70
Member Since:
2008-01-30
The new scripts need buttons defined in MAC.cfg

I messed around with why the LEDs are not illuminating using the newest XML scripts from Aastra. The new scripts seem to require that you define all the xml buttons that are tied to a blinking light such as Day/Night, Call Forward, Do Not Disturb, etc using the MAC.cfg file. since I am not using auto-config I usually program these in the aastra.cfg file to save time. all I usually put in the MAC.cfg is some extension specific configuration settings. I moved the definition of these buttons over to the MAC.cfg and my LEDs all started working. Maybe this will help others.



Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.