Considerations for Security Violation Notification

Last Updated : Oct 30, 2012 |

This section provides information about how the Security Violation Notification feature behaves in certain circumstances. Use this information to ensure that you receive the maximum benefits of Security Violation Notification under all conditions. The following considerations apply to Security Violation Notification:

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

  • Use caution when you administer 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 that does not have a display to provide an indication of the nature of the call.

  • An authorization code violation with remote access generates two SVNs. One displays authorization code violation and the second SVN displays 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, and not an attempt to place an outgoing call to an ARS trunk.