Each statistic displayed on the webSign has optional warning and critical threshold levels that are user defined. When these thresholds are passed, the webSign will show the statistic in a different color as well as play a sound that will immediately inform users when their attention is required.
Configuring the webSign to Play Audible Alarms
webSign sounds are configured through the Preferences area of the TASKE Contact web site. To configure webSign statistics to play sounds when warning or critical thresholds are breached, go to the Preferences area of TASKE Contact and select webSign. From the webSign Preferences page, click the Edit link for Colors and sounds to display the webSign Alarm Preferences page.
In the Alarm Sounds section of the page, select the frequency that the sounds will be played for the warning and critical alarms. The options are:
|Never:||disables audible alarms. No sound will play when a warning or critical threshold is breached.|
|Once:||plays the warning or critical sound once for each statistic that is in an alarm state.|
|Every 30 seconds:||plays the sound for the warning or critical alarm once every 30 seconds when one or more statistics is in an alarm state. If one statistic is in a warning state and another is in a critical state, the critical sound takes precedence.|
|Every 60 seconds:||plays the sound for the warning or critical alarm once every 60 seconds when one or more statistics is in an alarm state. If one statistic is in a warning state and another is in a critical state, the critical sound takes precedence.|
Next, select the warning sound and the critical sound. There are several audible (.au) sound files included by default with TASKE Contact. Custom sound files, including wave (.wav) and midi (.mid) sound files can be added, however, the ability of the webSign to play .wav and .mid files is dependant on the version of Java™ installed on the computer. Java 1.1, the minimum version supported by TASKE Contact, can only play .au sound files. As of Java 1.2 .wav and .mid sound files are supported.
Once the desired sound files are selected, save the changes. The sound files will play when any of the webSign statistics breach their warning or critical threshold levels.
Adding Custom Sound Files to the webSign
Custom webSign sound files can be added to TASKE Contact from the TASKE web server computer. The following types of files are supported:
|Audible (.au):||minimum Java 1.1 is required to play these sound files.|
|Wave (.wav):||minimum Java 1.2 is required to play these sound files. These sound files must be encoded using pulse-code modulation (PCM). Look at the Summary page of the file properties to determine the encoding method.|
|Midi (.mid):||minimum Java 1.2 is required to play these sound files.|
To add new sound files for webSign alarms, simply place the new files in the following folder of the TASKE web server computer:
%install directory%\webapps\sounds. By default this is
TASKE recommends using short sound files that are not more than 3 to 4 seconds in length. Longer sound files can be used, however, these files will need to be downloaded to the web client computer on the first play. Once a new sound file is placed in the appropriate folder of the TASKE web server computer, it is immediately available for selection on the webSign Alarm Preferences page of TASKE Contact.
Setting the volume of your webSign alarms
When using these alarms the computer’s volume controls are responsible for increasing or decreasing the alarm volume. For instruction on changing the computer volume, refer to the Microsoft® Windows documentation.