Re: [Flash Operator Panel] ASTDB and DND Problems

[Nicolas <nicolas@xxxxxxxxxxxx>]

Hi Chris,

Chris Vaughan wrote:
> Hi guys. We're trying to use the DND recipe in .27 and I've come 
> across two problems and a question.
Please try with the latest snapshot or SVN version. It has lots of bugfixes.

> 1) When I use the setalpha=30|100 option in op_astdb.cfg, the button 
> changes correctly when the user goes DND, and changes back to an alpha 
> of 100 when they  initially turn off their DND status, but shortly 
> after, the alpha on their button goes to what appears a 50 value 
> without them turning their DND status back on.
That 50% value might be something else, like a lagged extension... or a 
muted meetme participant.. anyways, please try with fop snapshot to see 
if that is still happening. If so, run op_server.pl with debug level set 
to 15 capturing the output, and kill the process as soon as you notice a 
button that went to 50%.. the log will tell us why is that happening.
> 2) Some of our users rely on the yellow queue member LED to show them 
> who is logged in to the queue. If I use the fopledcolor option, there 
> is no way to revert to a saved LED color (say, yellow for queue 
> members and green for normal phones).  All leds get the second 
> parameter from op_astdb.cfg no matter what.

Yep, there is no way around it. Currently, the handling of led colors is 
limited.. you have 3 possible colors, ready, busy and 'special', that 
special is the agent or fopledcolor. A new feature would be to have more 
states and an easier way to manage colors as currently is a kludge.

> 3) Is there any way to save the state of the ASTDB settings in 
> op_server.pl between restarts? We generate our buttons configuration 
> with a script every night, but I don't want to lose people's DND 
> status when I restart op_server.pl

The state is supposed to be sabes in ASTDB (asterisk database related 
commands or functions). If done correctly, and using astdbkey in each 
button, when fop starts it queries the astdb, and if it finds a value 
set for the given key, it will activate the feature... so say you want 
DND and write to ASTDB something like DND/100 for extension 100, then 
use astdbkey=100 in the button you want, store something into astdb 
(database put DND 100 on), and when op_server.pl starts, it will find 
the value and take the actions configured in astdb.conf.

If that does not happen, you might have a misconfiguration somewhere, or 
maybe you forgot to save the proper values into astdb.

Best regards,


> Thanks for your help!
> Chris Vaughan