Home » Forums » Vendor Forums - Certified » Aastra endpoints

Red LEDs not lighting on 57i for new XML scripts

robeerski
Posts: 70
 Member Since:
2008-01-30
Submitted by robeerski on Tue, 10/07/2008 - 11:36pm.

I just installed the new Aastra XML scripts version 2.1.1 and firmware 2.3.1.26. Under the old XML scripts there would be a red led lit when night mode, DND or call forwarding is activated. The red light still works on 55i phones but it dies not light on 57i phones. The phone is also supposed to rename the day/night mode button to day mode or night mode depending on the current state. This too does not work all I ever see on a 57i id the label "day/night" as listed in my CFG file. All these features work wonderfully on my 55i but fail on the 57i. I have a feeling that what ever tells the php script on th 57i to light the red LED is failing to execute. I am also wondering if others have had this same problem

‹ Aastra 57i and topsoftkey limitations aastra-xml-scripts ›

&nbsp

hhmcpas
Posts: 24
 Member Since:
2008-03-24
Me to...
Wed, 10/08/2008 - 1:01pm

I'm having a similar issue but is intermittent between 57i's Most of them work but 2 of the just won't light up. Anyone else having this issue?

HHMCPAS


&nbsp

SkykingOH
Posts: 9541
 Member Since:
2007-12-17
Hey guys, how about trying
Wed, 10/08/2008 - 1:50pm

Hey guys, how about trying to troubleshoot this?

Log on to the CLI and use the command 'show hints' Are the phones subscribing to the hints?

If you look at the log 'grep hint /var/log/asterisk/full' you can troubleshoot subscription errors. Remember that the Astraa's subscribe to the hint based on the first line registration unless you use the line variable in the button config.

You also have to reboot the phones if for some reason you have rebooted the server or restarted Asterisk. There is an outofordersip (or something like this) variable that can be set that attempts to solve this problem. It's still best practice to reset the phones after an Asterisk restart.

--

Scott

aka "Skyking"


&nbsp

hhmcpas
Posts: 24
 Member Since:
2008-03-24
I don't think they use hints for this function...
Wed, 10/08/2008 - 2:02pm

Someone correct me if I'm wrong but I think there is a portion of dnd.php that lights the light. I only have 20 phones that are hinting. For example, my station isn't hinting/subscribing and the light works fine.

# Change LED if supported
if(Aastra_is_ledcontrol_supported())
{
if($dnd==1) $object->addEntry('Led: '.$key.'=on');
else $object->addEntry('Led: '.$key.'=off');

Since the firmware upgrade/script upgrade there are a handfull of phones that won't light the button up. I have 90 stations and 85 of them are working just fine. There are maybe 5 that just won't light up...

HHMCPAS


&nbsp

SkykingOH
Posts: 9541
 Member Since:
2007-12-17
I was actually responding to
Wed, 10/08/2008 - 2:16pm

I was actually responding to the second post that did not have any troubleshooting info in it.

The day/night XML script does not use hints.

I wish I could give you some XML troubleshooting tips however I have never used the Aastra day/night script. Dev-state can do the same thing and is endpoint agnostic.

--

Scott

aka "Skyking"


&nbsp

robeerski
Posts: 70
 Member Since:
2008-01-30
Fixed my problem
Thu, 10/09/2008 - 7:15pm

I made an entry to an action URI that caused my day/night mode to not light red.

at the end of my "action uri poll:" setting I had &index=0. I thought this was supposed to be the day/night index 1-9 of the day/night function this phone is supposed to activate when pressing the day/night button. I guess the new scripts put the day/ night index in a conf file. I removed the &index=0 from the end of this line and my day/night button started functioning as expected.

This now brings me to another question. there are 9 possible day night functions. under the old Aastra scripts I beleive you would specify which day0night function this phone is supposed to activate by the variable index=XXX where XXX = 1-9 or the day/night index this button is supposed to trigger. On this system I only need one day/night function but in a system I plan to build in the future I will want a different day/night function for each department. Now that Aastra has put the day/night index in a conf file it looks like the day/night feature activated by this xml button is a system wide setting. I'll bet I can't have some phones activating day/night - 1 where others activate day/night - 2. I may do some investigation but this is what I have found so far.


&nbsp

hhmcpas
Posts: 24
 Member Since:
2008-03-24
Fixed my problme
Fri, 10/10/2008 - 8:10am

I fixed my problem by deleting all the .context files and replacing them with a known good file. They're stored in /var/cache/aastra/

This seemed to crop up after I did an upgrade to the XML scripts I think. Or maybe it was the firmware update. Both of them happened about the same time.

HHMCPAS


&nbsp

daftech
Posts: 34
 Member Since:
2007-08-06
robeerski - Any update
Wed, 11/19/2008 - 3:18pm

Have you determined how to get the functionality you described with the day/night button?

Thanks


&nbsp

robeerski
Posts: 70
 Member Since:
2008-01-30
No solution yet but I sort
Wed, 11/19/2008 - 4:59pm

No solution yet but I sort of got off track on this issue as the 57i's still report that DND, CFD, or Nightmode is activated in the display in the center so It was not a priority issue for me. I may look into this a little more over this week as I would still like to get the LEDs lit when in these different modes.

Does anyone know when these .session & .context files in /var/cache/aastra/ get created? or how to cause them to get refreshed or recreated?


&nbsp

necits
Posts: 419
 Member Since:
2008-02-23
It looks like there is a
Wed, 11/19/2008 - 10:12pm

It looks like there is a race condition in the new XML scripts. http://trixbox.org/forums/vendor-forums-certified/aastra-endpoints/context-files-losing-parameters

--

Michael Mathewson CCNA,MCSE
Owner/Consultant
Northeast CT IT Solutions


&nbsp

robeerski
Posts: 70
 Member Since:
2008-01-30
Fixed my problem
Wed, 01/20/2010 - 10:12pm

I asked an expert to fix this problem and he ended up giving me the very simple answer to fix this that nobody up till now has been able to figure out.

This line is needed in either the MAC.cfg file or the aastra.cfg file:

sip xml notify event: 1

I searchd for this in the documentation and it is only listed once under the setup for the do not disturb script on a 6751i. I don't have any 6751s so I never even read this section. After adding this line to my cfg file the Blinking LED for calls on park work great. I Hope Aastra makes this a little more clear in future releases or upgrades to the documentation.


&nbsp

robeerski
Posts: 70
 Member Since:
2008-01-30
another part of the fix.
Wed, 01/20/2010 - 10:15pm

to make the BLFs for DND, forwarding and day/night buttons etc. work correctly they need to be defined in the MAC.cfg files. If you define these buttons in the aastra.cfg file they do not work correctly. They must be configured in the MAC.cfg


&nbsp

Comment viewing options

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