Database Systems Corp.
Home  |   Contact Us  |   About Us  |   Sign Up  |   FAQ

predictive dialers and crm software
computer telephony software predictive dialer

Emergency Notification
Automatic Call Distribution
Predictive Dialer
Business Phone Systems
Emergency Communications
Community Notification Systems
Emergency Phone Dialer
Emergency Alert System EAS
Emergency Broadcast Systems
Emergency Dialer

predictive dialers and crm software
Information

Emergency Main Menu School Closing Alert
School Announcement

emergency notification systems


DSC Tech Library

Emergency Alert Systems

Emergency Notification Systems This section of our technical library presents information and documentation relating to Emergency Broadcasting Systems and Disaster Recovery Applications. Should an emergency arise in your community, our 911 broadcast service can deliver large volumes of calls quickly using thousands of phone lines simultaneously. In the event of a blizzard, wild fire or devastating flood, your community can be notified quickly given specific instructions if an evacuation is required using our emergency broadcasting service. If a dangerous chemical spill occurs in your community, you can target specific areas to call. If a severe snow storm hits your area, your community can be notified of school closings or event cancellations.

Emergency Broadcast Network Call Distribution System

The Autonomous Call Center Server (DscACS)

DscACS can be used to fully automate a Voice Blast server. See the AcsApi32 routines for exposed functionality. It is a service, and must have an entry in the “services” file.

DscACS is in communication with the DialerInterface & PDialerPlus (via internal RspApi32 routines) and a daemon (cmpapid – via internal CmpApi32 routines) on the linux (or cmpapidsvc on Windows), which handles DBASE Campaign & List Manager Issues. Fig. 1 indicates the location and name of the DialerInterface, and Fig. 2 is for the location of the cmpapid service (always called “cmpapid”). An entry in the “services” file is required for cmpapid.

(Note: The connection to the cmpapid service is confirmed by a “ping” to that service, while the DialerInterface connection is a true “login.”)




The main screen for DscACS indicates the status of its connections, and provides a controls to enable/disable remote emergency and non-emergency blast requests, and remote Associate alert and user ping timers. There is a “Details” view available which provides more information.


If a Pacer (DscACS) installation is to be used for fulfilling remote blast requests (from other Pacers), then the site can indicate whether it is positioned to handle emergency requests, non-emergency requests, both, or neither.

Disabling the timers is useful during testing. Alert timers are used during emergency broadcast distributions, in order to ensure timely responses from Associates. Timeouts here will trigger a variety of behaviors, including searches for other Associates, or local dialing. DscACS “pings” clients logged into it on a regular basis, and they must “pong” back or risk being dropped from the server.

The LEDs indicate the status of the connections and options – green for active/logged on/on, red for inactive/not-logged on/off. One condition – yellow – may be shown for the status of remote Pacer blast requests – if it is enabled, but DscACS is not logged into DialerInterface or getting successful ping responses from cmpapid, then these LEDs will indicate a “yellow” condition.

Under the Edit menu, administrators may maintain Password & Associate records, as well as configure the Email trace notifications and other general preferences.

The following sections describe the operation of each of the DSCAcs Menu Items: