list history

Use list history with no options to generate a log of the most recently completed data-affecting administration and maintenance commands. This includes the history of ACTR moves, which can be used to track moves and help reduce fraud.


list history [ date | time | login x | action x | object x | qualifier x ][ schedule ] 




login x

Login ID

action x

Action performed

object x

Object acted upon

qualifier x

Extension, etc.


Specify a time to run the command.

list history feature interactions

The translation log is written to memory as translation data when save translation is executed. The translation data is time stamped when saved. This time stamp is noted when translation is loaded from memory and included in every recent change history report.

When a user requests a recent change history report, there could be other users concurrently issuing data commands and altering the contents of the transaction log. Therefore, if the user pages the entire way through the report, the oldest entries in the transaction log (maximum 250 commands) may have been overwritten by data commands issued by these other users. If this occurs, the final entries of the report show the data commands issued by the other users since the recent change history report was originally requested.

Also, using set time to alter the system clock could make it look as if the recent change history report is not in true LIFO order.

list history field descriptions




The date list history was issued (mm/dd).


The time list history was issued (hh:mm).


The port type to which the user was connected when list history was issued.

  • TTI, PSA, CTA and ACTR moves are recorded when the CTA/PSA/TTI Transactions in History Log field is y on the Feature-Related System Parameters screen. These transactions appear as two separate records: one recording the moved-from port, and the other one recording the moved-to port.

  • IP station registrations and unregistrations are recorded when the Record IP Registrations in History Log field is y on the Feature-Related System Parameters screen.


Shows the user login or the feature that caused the logged event, such as:

  • actr for ACTR moves

  • cta for Customer Telephone Activation transactions

  • psa for Personal Station Activation transactions

  • tti for TTI transactions

  • ip-a or ip-u for IP registrations and events

  • pms for Property Management System events

  • ad for Abbreviated Dialing events

  • reboot for when the system rebooted


The action part of the command, specifying the operation to be performed. This field is truncated after four characters to allow enough space for objects and qualifiers and to uniquely identify each action.


The qualifier (12 characters) specifying the object of the command. Where the object is multiple words in length, only the first word appears in the object field; every succeeding word is treated as a qualifier.


One or more qualifiers describing the characteristics of the Action/Object pair. This field is truncated after 31 characters to keep information for a command on a single line.

Communication Manager events are also logged in the Linux syslog. Syslog is a standard Linux service that supports storing event information in local files as well as sending events to an external syslog server. Syslog supports storing events in different files or ’logs’ depending on the nature of the event.

Access the Communication Manager web interface log pages through Select Diagnostics > System Logs. For more information on 'Communication Manager web interface System Logs', see Maintenance Procedures for Avaya Aura®Communication Manager, Branch Gateways and Servers (03–300432).

The following types of activities are logged:

  • Security-related events: Communication Manager logs all events related to security to the secure log. An administrator cannot disable or change parameters related to security events.

  • System Administration Terminal (SAT) interface logging: Administration changes are logged to the command history log with the date and time, the unique identify of the person making the change, the value of the parameter that is changing and the status of the operation (successful or not). The administrator can configure the level of detail that is logged.

    Communication Manager logs attempts by users to view information to which they are not permitted access or attempts to submit forms with invalid or non-acceptable values.

  • Web page logging: Attempts to access the Avaya server’s web pages and changes to a value in a web page are logged. Changes to a web page are logged only if the page is submitted, either successfully or unsuccessfully.