Security Violations Notification - Avaya Communication Manager Administrator's Manual

Feature Reference

Security violations notification

Interactions
•
Automatic Callback
If Ringer Cutoff is active, an Automatic Callback call returns to the user's telephone with the
normal 3-burst ring.
•
Bridging
A bridging user is not affected by a primary extension's activation of Ringer Cutoff. Nor is the
primary extension affected by the bridging user's activation of Ringer Cutoff.
•
Call Forwarding All Calls
If Ringer Cutoff and Call Forwarding All Calls are active, the user receives redirect notification, if
you set Redirection Notification to y for the extension.
•
Distinctive Ringing
Ringer Cutoff turns off only the distinctive ringing of internal and external calls. Intercom
ringing, priority ringing, redirect notification, and manual signaling are not turned off.
•
Intercom
If Ringer Cutoff is active, intercom calls still ring the user's telephone.
•
Manual Signaling
If Ringer Cutoff is active, Manual Signaling still rings the user's telephone.
•
Ringback Queuing
If Ringer Cutoff is active, the return call for Ringback Queuing still rings the user's telephone
with a 3-burst alerting signal.
•
Priority Calling
If Ringer Cutoff is active, priority calls still ring at the user's telephone.
•
Send All Calls
When Ringer Cutoff and Send All Calls are both active, the user receives redirect notification,
when Redirection Notification is set to y for that extension.
Security violations notification
When a security violation occurs, security violations notification (SVN) notifies a designated referral
point. This can be an attendant console, a display-equipped phone, or a phone without display for SVN
referral calls with announcements.
The system monitors and reports on the following types of security violations:
•
Login violations
•
Remote access barrier code violations
•
Authorization code violations
•
Station security code violations
Avaya Communication Manager provides the option to log a major alarm if a security violation occurs
involving an Avaya services login ID. Avaya is responsible for retiring the alarm.
1654 Administrator's Guide for Avaya Communication Manager
November 2003