Audible error alerts
On a Windows server, for an audible beep to occur for error messages, Pragma must be configured to pass the ASCII bell control character over to the RF device. The screen mode should be set up for Advanced Console (see the Configuring a Pragma user section of the Installation above).
The parameter in the <install>\sce\scprd\rf\metarf\MetaRF.ini file called HH_NUMBEEPS should be set to configure the number of beeps that Meta RF emits on an error. For example, setting this value to a 3 causes these numbers of beeps for each message:
- Error messages = 3 beeps
- Warning messages = 2 beeps
- Informational messages = 1 beep
Error messages are defined by messages returned by the appserver with a rectype = 9.
RF device settings may vary by device model and manufacturer.
Intermec devices have an on and off and volume settings in .
Some devices have a setting for disabling non-printable characters in the telnet client. Do not use this setting since the beep is a non-printable ASCII character.
Some devices also require you to setup a tone for the beep, for example, a .wav file.
You must properly configure RF screens for the alert to be recognized. For an error message to be identified, the RF screen must have a rectype = 9. Many RF screens navigate the user to a screen with a single label on it, which does not have a rectype = 9. If this situation occurs, the RF client cannot distinguish between a plain label and an error, so the beep cannot sound.