When using Blueworx Voice Response, note:
- The setting for umask must be 022 during any
installation process, for example, installation of Blueworx Voice Response, applying
PTFs, or importing Blueworx Voice Response items
such as custom servers. If umask is not set to 022, this can
result in failures at runtime.
- Even if you are not using the dtuser AIX
account to run Blueworx Voice Response (see User ID), you must have a dtuser account
before you can install a PTF. If you do not already have
an account of this name, use smitty or the mkuser command
to create it.
- It is recommended that you only stop Blueworx Voice Response by selecting
one of the Shutdown options on the Administration menu
of the Welcome window (see Shutting down Blueworx Voice Response),
or by using the DT_shutdown utility (see Shutting down Blueworx Voice Response automatically on AIX shutdown). You should not stop the system,
for example, by pressing Ctrl+Alt+Backspace, without shutting Blueworx Voice Response down
first.
Although Ctrl+Alt+Backspace shuts down AIXwindows, it does
not stop the background processes. In addition, when you log on again,
at least one buffer is lost. If you continue to do this, it is possible
to use up the buffer pool. For these reasons, stopping the X server
without shutting down Blueworx Voice Response first
is not recommended.
- For correct operation of various Blueworx Voice Response windows,
the window manager should be set to use the click to focus policy.
This is the default policy for the Common Desktop Environment. If
you are using a different desktop GUI you might need to manually change
the focusing policy.
- On a production system,
it is recommended that you run Blueworx Voice Response from
an AIXwindows environment, rather than from the Common Desktop Environment
(CDE).
- On a production system, it is advisable to disable any screen
savers (otherwise known as screen blankers). A screen saver is an
application that is activated after a specified period during which
no user interaction with the mouse or keyboard occurs; the screen
saver is deactivated by a mouse movement. On deactivation, a significant
amount of X activity occurs at very high processor priority, causing
major disruption to Blueworx Voice Response telephony
activity. Calls in progress are interrupted because of trunks and
channels temporarily being disabled. Normally these effects occur
only after a long period of screen saving (an hour or more), but it
is sensible to disable any screen savers, such as the standard desktop
screen saver that comes with AIX, on a production system.
As an
alternative, if your display has a power-management feature, configure
that to switch off the screen after a period of no user interaction.