Lucent Technologies 8.2 User Manual

Issue 1

April 2000

Features and technical reference 

1482

Security violations notification 

■

You may only administer one referral destination per system for each type 
of violation.

■

Exercise caution when administering bridged appearances for stations that 
are used as SVN referral destinations. SVN referral calls terminating to 
bridged appearances must be accompanied by an announcement message 
or must route to bridge appearances equipped with a display module. SVN 
referral calls that do not have an announcement and terminate to a bridged 
appearance not having a display will not provide an indication of the nature 
of the call.

■

An authorization code violation with remote access generates two SVNs -- 
one displaying “authorization code violation” and one displaying “barrier 
code violation,” even though the correct barrier code was input. These two 
displays help you determine that the violation took place in the context of a 
remote access attempt, not an attempt to place an outgoing call to an ARS 
trunk.

■

Call Coverage, Call Forwarding, and Call Pickup 

These items are supported for SVN only if you use recorded 
announcements.

■

Centralized Attendant Services (CAS)

CAS attendants cannot receive referral calls from branch locations.

■

Distributed Communications System (DCS)

SVN does not support referral calls across a DCS network. 

‘‘Monitoring the Access Security Gateway history log’’ on page 323

Refer to 

‘‘Login Administration’’ on page 804

 to disable a login following a 

security violation.

Refer to 

‘‘Setting up security violations notification’’ on page 328

 for instructions.

Refer to 

‘‘Recording announcements’’ on page 368

 to record announcements.