Ticket #3881 (new Bugs)

Opened 4 years ago

Last modified 3 years ago

FOP support for do-not-disturb on ZAP/DAHDI channels

Reported by: Nick_Lewis Assigned to: asternic
Priority: trivial Milestone: Undetermined
Component: Flash Operator Panel Version: 2.6-branch
Keywords: Cc:
Confirmation: Unreviewed Distro:
Backend Engine: All Distro Ver:
Backend Ver: SVN Revision (if applicable):

Description

ZAP/DAHDI channels contain native support for do-not-disturb (rather than the usual dialparties.agi support) and send manager events when there is a change in the DND state. Other types of channel do not provide this. The FOP server detects the DNDState events and emulates the result of an astdb lookup.

The astdb family in the emulation is set to "dnd" but the actual family in the database is "DND"

Change History

09/09/09 04:58:26 changed by Nick_Lewis

To properly resolve this issue I suggest that op_server.pl be modified to use a configurable family name for its zapdnd handling rather than the hardcoded "dnd". For example if op_server.cfg contained a setting zapdnd_family=DND then (with the usual initialisation and parsing) op_server.pl could have the following change:

- $fake_bloque[$fakecounter]{Family} = "dnd"; + $fake_bloque[$fakecounter]{Family} = $zapdnd_family;

A workaround is to have in op_astdb.cfg an additional family [dnd] with the same settings as the family [DND]. The additional family must be before [DND] in the cfg file or it will cause FOP to show the wrong DND state at startup. However this workaround is not very satisfactory and an enhancement to op_server.pl is preferable

09/09/09 04:59:20 changed by Nick_Lewis

To properly resolve this issue I suggest that op_server.pl be modified to use a configurable family name for its zapdnd handling rather than the hardcoded "dnd". For example if op_server.cfg contained a setting zapdnd_family=DND then (with the usual initialisation and parsing) op_server.pl could have the following change: 

- $fake_bloque[$fakecounter]{Family} = "dnd"; 
+ $fake_bloque[$fakecounter]{Family} = $zapdnd_family;

A workaround is to have in op_astdb.cfg an additional family [dnd] with the same settings as the family [DND]. The additional family must be before [DND] in the cfg file or it will cause FOP to show the wrong DND state at startup. However this workaround is not very satisfactory and an enhancement to op_server.pl is preferable

01/28/10 10:59:29 changed by p_lindheimer

  • milestone changed from 2.7 to 2.8.