Logging levels

Last Updated : Oct 29, 2012 |

Administers logging of SAT activities. Specifies that commands associated with specific actions shown on this screen are logged by the system. The amount of detail to be logged is the same for all enabled actions and is specified by the Log Data Values field.

Note:

The defaults on this screen provide the same amount and type of logging as in Communication Manager releases prior to 4.0.

Example command: change logging-levels

Logging Levels: page 1

Enable Command Logging

If enabled, SAT activity is logged for selected commands.

Log Data Values

Valid Entry

Usage

none

Only the object, the qualifier, and the command action are logged.

new

The new value of any field is logged. The old value is not logged.

both

Both the prior field value and the field value after the change are logged.

Logging Levels: page 2

Log All Submission Failures

Form submission failures due to a security violation are always logged and are unaffected by this field.

Valid Entry

Usage

y

Record submission failures on the history log. An event is logged when Avaya Communication Manager rejects a form submission for any reason, such as an invalid entry in a field or a missing value.

n

Submission failures are not recorded on the history log.

Log CTA/PSA/TTI Transactions

Enables or disables logging transactions when extensions and physical telephones move between ports without additional administration from the administrator of Communication Manager.

If enabled, the system records Customer Telephone Activation (CTA), Personal Station Activation (PSA), and TTI transactions in the system history log.

Available only if Terminal Translation Initialization (TTI) is enabled for the system.

Log IP Registrations and Events

If enabled, the IP registrations can be logged in the history log.

Log PMS/AD Transactions

If enabled, the system records Property Management System (PMS) and Abbreviated Dialing (AD) events to the log.

Related information
Log Data Values