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

Disaster Planning Service
Emergency Management Service
Phone Call Alerts
Emergency Communications
Snow Storm Warning
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.

DSC Autonomous Call Center Acknowledgment Client

AcsAPI Library Routines - Upload list and message

    int ACSInitializeUploads(const char * _campaign);

    Use this routine to alert DscACS that wave & phone files are going to be uploaded for possible distribution to associates. This need not be called if ACSUploadWaveFile() and ACSUploadPhonesFile() are going to be called for local server dialing (ACSAPI_BT_LOCAL). However, if phones are uploaded with ACSAPI_BT_MIX/ACSAPI_DISTRIBUTE, and ACSUploadWaveFileProvisional() are being called, then this routine is necessary for correct operations.

    int ACSUploadWaveFile(const char * _targetIPAddr,

    const char * _campaign,

    const char * _inputWavePath,

    const char * _outputWaveName);

     

    int ACSUploadWaveFileProvisional(const char * _targetIPAddr,

    const char * _campaign,

    const char * _inputWavePath,

    const char * _outputWaveName);

     

    ACSUploadWaveFile() immediately loads the wave file into the dialer for processing ACSUploadWaveFileProvisional() stores the file(s) pending Associate distribution decision making. Call ACSInitializeUploads() before using the provisional routine.

     

    The sound files are untouched conversion to 8-bit mono is still a manual process at this point.

     

    int ACSUploadPhonesFile(const char * _targetIPAddr,

    const char * _campaign,

    const char * _inputPhonesPath,

    const int _blastType,

    const int _messageLength,

    const int _emergency);

    _blastType can be:

    • ACSAPI_BT_LOCAL Dialing will be performed by the local Pacer system only.
    • ACSAPI_BT_DISTRIBUTE DscACS will search the Associates file for appropriate destinations for outsourcing the dial. If none are found/available, then local Pacer system dialing will proceed, if possible.
    • ACSAPI_BT_MIX Similar to _DISTRIBUTE, except DscACS will check to see if the local dialer has the capacity to handle the blast before looking for Associates. This is the only type which uses the argument _messageLength, for blast length calculation purposes.

    The _targetIPAddr is returned after executing ACSConnect(), so this must be saved to use these routines.