|
|
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 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 onuOne 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]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.
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.
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 |
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. | |
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. | |
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. | |
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:
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 passwords should not be trivial. | |
Consider disconnecting the maintenance port when not in use. | |
Regularly backup system data to ensure a timely recover, should it be required. | |
Check logs for "lockout", password problems, etc. | |
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. |
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Tue Jun 20 13:09:39 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.