cc/td/doc/product/voice/uone/entrpris/41e
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

uOne Logs

uOne Logs

At runtime uTel, uLite, uPilot, and uOne create log files in the <uOne directory>/logs directory. You should clean up log files by moving or deleting files periodically. Over a period of time these files can fill up your disk space if they are not monitored and managed correctly.

uLite

uLite logs can be found at: <uOne directory>\logs. The files are listed as uLite.XXX.out and can be viewed using Notepad. When reading uLite logs you should be aware that:

Here is a sample uLite log file:

14:07:01.812000|NOTIFY|LOG| [* OK Netscape IMAP4rev1 Service 3.62 on

estfeat3.cisco.com at Wed, 8 Dec 1999 14:07:01 -0500 (Eastern Standard

Time)]

14:07:01.812000|NOTIFY|LOG| [00000000 CAPABILITY]

14:07:01.812000|NOTIFY|LOG| [* CAPABILITY IMAP4 IMAP4rev1 SCAN QUOTA

LITERAL+ AUTH=LOGIN XSENDER X-NETSCAPE]

14:07:01.968000|NOTIFY|LOG| [00000000 OK CAPABILITY completed]

14:07:01.968000|NOTIFY|LOG| [00000001 LOGIN notifier 1234]

14:07:01.984000|NOTIFY|LOG| [00000001 OK LOGIN completed]

14:07:01.984000|NOTIFY|LOG| [00000002 SELECT INBOX]

14:07:01.984000|NOTIFY|LOG| [* 0 EXISTS]

14:07:02.171000|NOTIFY|LOG| [* OK [UIDVALIDITY 944145963] UID validity

status]

14:07:02.171000|NOTIFY|LOG| [* FLAGS (\Answered \Flagged \Deleted \Draft

\Seen)]

14:07:02.171000|NOTIFY|LOG| [* OK [PERMANENTFLAGS (\Answered \Flagged

\Deleted \Draft \Seen)] Permanent flags]

...

14:13:29.109000|NOTIFY|LOG| [0000000a NOOP]

14:13:29.109000|NOTIFY|LOG| [* 1 EXISTS]

14:13:29.250000|NOTIFY|LOG| [* 1 RECENT]

14:13:29.250000|NOTIFY|LOG| [0000000a OK NOOP completed]

14:13:29.250000|NOTIFY|LOG| [0000000b FETCH 1 (ENVELOPE

BODY.PEEK[HEADER.FIELDS (X-Priority X-Sensitivity X-AmtevaBcast

X-AmtevaExp)] BODYSTRUCTURE UID INTERNALDATE RFC822.SIZE FLAGS)]

14:13:29.453000|NOTIFY|LOG| [* 1 FETCH (ENVELOPE ("Wed, 8 Dec 1999

14:13:26 -0500 (Eastern Standard Time)" "Voice Message From Test Phone"

(("Test Phone" NIL "tphone" "estfeat3.cisco.com")) (("Test Phone" NIL

"tphone" "estfeat3.cisco.com")) (("Test Phone" NIL "tphone" "e]

14:13:29.453000|NOTIFY|LOG| [ BODYSTRUCTURE (("AUDIO" "WAV" NIL NIL

"Amteva Voice Message (1 seconds)" "BASE64" 16708 NIL ("INLINE" ("VOICE"

"Voice-Message" "FILENAME" "message.wav")) NIL)("AUDIO" "WAV" NIL NIL

"Originator's Spoken Name" "BASE64" 7450 NIL ("INLINE" ("VOI]

...

17:31:11.515000|NOTIFY|LOG| [Set MWI ON for 8047625641]

uOne

uOne can be found at: <uOne directory>\logs. The files are listed as uOneXXXXXXXXX.out and can be viewed using Notepad. There is a separate uOne.out file for every instance of uOne. The log file shows the client/server interaction between the uOne application and uTel, the directory server, and the messaging server.
Time Stamp Server Sent/Response Log Data

The time stamp from the NT server of the log message.

The server the uOne application is interacting with for the log message.

The servers include: uTel, directory server, or messaging server.

It is tagged as "Sent" if uOne is sending to the server.

It is tagged as "Resp" if uOne is receiving a response from the server.

Any information that is being sent between servers is logged. It includes: API calls, commands, queries, acknowledgements, error messages, etc.

Here is a sample uOne log file:

14:13:00.859000|TEL|SENT| [1 LOGIN UM4 pass]

14:13:00.875000|TEL|SENT| [2 CREATESESSION]

14:13:00.890000|TEL|RESP| [2 OK CREATESESSION Complete|{SesId6}]

14:13:00.890000|TEL|SENT| [3 SesId6 {REQUESTGROUP UM4 INCREMENT}]

14:13:00.890000|TEL|RESP| [3 OK REQUESTGROUP

Complete|{SCR_UNRECEIVEDCOUNT 1} ]

14:13:00.890000|TEL|SENT| [4 NOOP]

14:15:30.203000|TEL|SENT| [5 DESTROYSESSION SesId6]

uPilot

uPilot can be found at: <uOne directory>\logs. The files are listed as uPilotXXXXXXXXX.XXX.out and can be viewed using Notepad. More information will be supplied at a later date on uPilot.out.

Third Party Tools

NT

Event Viewer-Select Programs, Administrative Tools(Common), Event Viewer

Event Viewer is the tool you can use to monitor NT events, in your system. You can use Event Viewer to view and manage System Security and Application event logs.

Task Manager-Simultaneously enter Control, Alt, and Delete, select Task Manager

Task Manager enables you to monitor and control your computer and what's running on it.

The Application tab show the status of the programs (also known as tasks) that are currently running on your computer. From this window you can end, switch to, or start a program.

The Processes tab shows information about the processes that are currently running on your computer. From this window, you can end a process.

The Performance tab displays a dynamic overview of your computer's performance including Graphs for CPU and memory usage. The number of items running includes handles, threads, and processes. Information about physical, kernel, and commit memory is also included.

Directory Server Logs

Error logs are used to record error messages generated by ns-slapd. These messages can describe error conditions, but more often they will contain informative conditions such as: server startup and shutdown times, and the port number the server uses. This log will contain differing amounts of information depending on the current setting of the Log Level parameter. The error log is located at:

C:\Netscape\SuiteSpot\slapd-<Server ID>\logs\errors

Access Logs are used to record each database access. The following information is recorded in the log file: IP of the client machine that accessed the database, operations performed (for example, search, add, modify), result of the access (for example, the number of entries returned). The access log is located at:

C:\Netscape\SuiteSpot\slapd-<Server ID>\logs\access

Security

uOne is designed to be secure. However, some action is required on your part to ensure the necessary security precautions are made and implemented. Maximum security is assured by the following factors:
Feature Description

Password Length

The system allows fixed length and variable length passwords from 4 to 8 digits. The system default is a fixed length of 4 digits. You should change it through Unified Messaging System Administration (UMSA) to variable length of 5 to 8 digits.

Failed Entries in a Single Session

The system disconnects a user after a configurable number of failed login attempts in a single session. You can change that number by updating the MaxLoginAttempts attribute in the UM.ini file. The default is 3.

Failed Entries Across Multiple Sessions/Lockout

The system locks out a user after the maximum number of consecutive failed login attempts across multiple sessions. You can change this number by updating the Class of Service in UMSA. The default is 6.

User Password/PINs

Users are responsible for their own Passwords/PINs. It is your responsibility to tell them the importance of password security.

Make these recommendations to users:

  • Change their password immediately after the service is assigned to them.

  • Don't use trivial passwords, such as ascending, descending, or the same digits (such as "1111" or "1234").

  • Don't use the current year.

  • Don't use their phone numbers, extensions, or the reverse of their extensions as passwords.

  • Don't use their names, initials, or other identifying name (such as department).

Passwords should be as long as possible, with a minimum of five digits.

Passwords should not be posted, shared, or printed in an obvious place.

Passwords should not be coded in programmable-function keys or speed-dialing keys that allow ready access by unauthorized persons.

Passwords should be periodically changed based on the need.

Administration Password/PINs

Administration passwords should not be trivial.

Maintenance Port

Consider disconnecting the maintenance port when not in use.

Backup

Regularly backup system data to ensure a timely recover, should it be required.

Logs

Check logs for "lockout", password problems, etc.

Addressing and Dialing Rules

You can administer addressing and dialing rules to limit outdialing capability on the system. By administering the Rules.<host name> file and your PBX appropriately, you can minimize toll fraud.


hometocprevnextglossaryfeedbacksearchhelp
Posted: Tue Jun 20 13:09:39 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.