Instruction manual

Large business communications systems
5-26 Issue 9 May 2003
The feature has a pre-administered security feature regarding input entry by the
user. Once the user enters his or her extension at the appropriate time, a “no
response” feedback is provided whether or not the entered extension is valid. For
an invalid extension, the system simply waits, without responding, until it reaches
a timeout threshold. As such, an unauthorized user does not know that input entry
is the cause of the error. The same security feature is in effect whenever the user
enters the SSC at the appropriate time.
The dissociate function within PSA allows a user to restrict the features available
to a voice terminal. Whenever a terminal is dissociated via PSA, it can be used
only to call an attendant, accept a TTI merge request, or accept a PSA associate
request.
Security tips
PSA/TTI transactions are recorded in the history log, which can be accessed by
entering the list history command at the prompt. If there is a concern about
unauthorized PSA/TTI usage, refer to the history log for verification. To enable
recording PSA/TTI transactions, access the Feature-Related System Parameters
screen by entering the change system-parameters features command at the
prompt. Then ensure that the
Record CTA/PSA/TTI Transactions in
History Log
field is set to y. (Sometimes this flag is set to n if CTA/PSA/TTI
entries tend to flood the history log, therefore making it difficult to find other
entries.) The default for the field is y.
A COS for the user’s extension must be administered to have access to PSA.
However, be sure to limit PSA COS assignments to stations that need to access
PSA.
Once a PSA station is associated with a terminal, anyone using that terminal has
all the privileges and capabilities of that station. Therefore, use of the dissociate
facility access code is recommended whenever the terminal is not in use.
If PSA and DCP extenders are used to permit remote DCP access, the security
provided may not be adequate. A user connecting via DCP extenders must
provide a password. However, once the user is connected, the remote DCP
station has the capabilities and permissions of whatever station is associated or
merged with the local DCP extender port unless the station has been dissociated
or separated. Therefore, PSA users should dissociate before they disconnect
from a DCP extender.
PSA security violations are recorded by SVN software, if enabled. Refer to the
SVN feature description and to the following two documents for security report
information:
■ Hardware Guide for Avaya™ Communication Manager,
■ Administrator’s Guide for Avaya™ Communication Manager, 555-233-506