Examples of SAT log entries

Last Updated : Apr 27, 2014 |
  • Commands that do not change data only log the form invocation:

    module-name[98765]:sat 13533 778 login login 0 s display station 1000

    This log entry indicates that the user accessed the station form for extension 1000 but did not make any changes.

  • One log entry is created for the form invocation and one log entry is created for each field that was changed for commands that change one or more fields within a form:

    module-name[98765]: sat 13533 778 login login 0 s display station 1000
    module-name[98765]: sat 13533 778 login login 0 s change station 1000 Name | Joe Smith | Mary Jones
    module-name[98765]: sat 13533 778 login login 0 s change station 1000 Security Code | * | *
    module-name[98765]: sat 13533 778 login login 0 s change station 1000 Coverage Path 1 | 3 | 6
    module-name[98765]: sat 13533 778 login login 0 s change station 1000 Personalized Ringing Pattern 1 | 2 | 4
    These entries indicate the following:
    • The name associated with extension 1000 changed from Joe Smith to Mary Jones

    • The security code for extension 1000 changed, but the security codes (indicated by *) do not display in the log.

    • The Coverage Path 1 field for station 1000 changed from 3 to 6.

    • The Personalized Ringing Pattern 1 field for station 1000 changed from 2 to 4.

      Note:

      For commands that log new entries, only values that change from a default value are logged.

      Security alert:

      The values for authorization codes, PINs, encryption keys, and passwords never appear in the command history log.