Telephony Interface Hardware:

The telephony interface hardware for this project is the ‘PC Voice’ PCV100 ISA PCB. This PCB is a prototype of a product that one of our team members developed as an extension to a 1992 computer interface class project here at GT. This particular prototype has been in storage for over a decade and did require some TLC to get going again. The design files and original DOS driver software files are long gone. However, given that this class is primarily about using Windows CE, it seemed reasonable to bring this PCB out of storage and bring it back to life under a Windows CEPC environment.

Alarm Sensor Hardware:

For our project, the alarm sensor hardware is simulated. Were this product to be deployed, the alarm sensor hardware would consist of an internal or external interface card that monitors dry contact closures. An alarm state could be represented by either closed or open contacts. Upon detection of an alarm state, the alarm sensor hardware driver software would set an event and associate that event with data representing the particular set of alarm contacts that caused the alarm. To demo the project, we have a console application that simulates the action of the alarm sensor hardware driver.

Software: The RemoTeASyst software is divided into three components. Device Driver: The device driver communicates directly with the PCV100 hardware. The device driver must: • setup and manage DMA for the recording and playback audio data • detect and manage interrupts from the telephony interface, DTMF transceiver, and DMA hardware • expose a WAV type interface for easy playback of the WAV files containing the alarm messages

Alarm Service:

The alarm service runs in the background waiting for alarm events from the alarm sensor hardware driver. When signaled, the alarm service activates and begins the process of dialing a phone number, playing alarm messages, and waiting for DTMF acknowledgement. This is accomplished by communicating with PCV100 device driver using the WAV API. Custom control messages are sent to the PCV100 driver using the WAV API. A log of events is maintained by the alarm service as well. The service is also controlled by the GUI using service routine commands.

RemoTeASyst Graphical User Interface:

The final component of the RemoTeASyst software is a GUI for updating the phone number and alarm wave file lists as well as installing, starting and stopping the alarm service. When ever the user updates changes to the phone or wave file lists the GUI writes them to a configuration INI file. It then sends a command to the alarm service informing it that changes have been made and it needs to read the configuration file. The GUI also sends commands to the service routine to tell it to install, start, or stop itself.