|
|
In order to ensure that the uOne system is operating properly, and to obtain information you need from the system, several operations tasks need to be performed. This chapter explains how to perform the following uOne operations tasks:
The uOne install script adds four service entries to the NT registry:
These four services can be controlled from the Services panel of NT.
The uTel service is started automatically when the system boots. The uPilot service creates multiple instances of the uOne application and is dependent upon uTel running. The uLite service is dependent upon the Messaging Server running and notifier mailbox being present on the Messaging Server. The uLogRemover periodically cleans the log files on your system.
When the system is running, the task manager should show the following processes:
To start uOne from the Windows Control Panel, follow these steps.
Step 2 Select Settings, then Control Panel.
Step 3 Select the Services icon.
Step 4 Select the uTel process first.
Step 5 Click Start.
Step 6 Then select each of the remaining processes one at a time in the following order and click Start after each.
a. uPilot
b. uLite
c. uLogRemover
You define the number of uOne sessions that are running at runtime, and this information is added to the NT registry. These uOne sessions start when NT is started. You can also start additional uOne sessions from the command line. The uOne sessions started from a command line are in addition to those already started.
The uOne sessions started manually are associated with the user that started them. Therefore, the uOne processes started manually are terminated when the user logs out. To start a uOne session from the command line, follow these steps.
Step 2 In the Open command line, enter the following:
<uOne directory>\bin\uPilot -debug <instances> uOne.exeStep 3 Click OK.
By stopping the uTel process first, you will receive a message stating that by stopping the uTel process, the uPilot, uLite, and uLogRemover processes will also be stopped. Follow these steps to stop the processes.
Step 2 Select Settings, then Control Panel.
Step 3 Select the Services icon.
Step 4 Select the uTel process first, and click Stop.
Step 5 At the confirmation prompt for Stopping Services, confirm that all of the following processes will be stopped: uTel, uLite, uLogRemover, and uPilot.
Step 6 Click OK to stop these processes.
If you find that you must stop the uOne processes separately, follow these steps. The uPilot process should be stopped before you stop uTel.
Step 2 Select Settings, then Control Panel.
Step 3 Select the Services icon.
Step 4 Select the uLogRemover process first.
Step 5 Click Stop.
Step 6 Then select each of the remaining processes one at a time in the following order and click Stop after each.
a. uPilot
b. uLite
c. uTel
 |
Note After stopping the uPilot process, open the Windows NT Task Manager to be sure that there are no uOne sessions still running before stopping the uTel process. |
You can check on an LDAP entry by using the following steps.
Step 2 In the Open command line, enter the following:
ldapsearch -h localhost -p <LDAP Server Port> -b "o=Organization" "(|(telephonenumber=<User tel. no>)(billingnumber=<User tel. no>))"|moreStep 3 Click OK.
|
Note Note: The LDAP Server port is 389 for Netscape Messaging Server implementations. |
To check for the version number of any uOne component, follow these steps.
Step 2 Select Settings, then Control Panel.
Step 3 Select the Services icon.
Step 4 Locate the executable for the specific uOne component to obtain a version (uTel, uOne, uLite, uPilot, etc.)
Step 5 The version information for the particular component displays in parentheses next to the name of the executable.
uOne is designed to be secure. However, some action is required on your part to ensure the necessary security precautions are set up 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 uPower/Admin 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. 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 uPower/Admin. 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 changed periodically based on the need. | |
Administration passwords should not be trivial. | |
Consider disconnecting the maintenance port when not in use. | |
Regularly back up system data to ensure a timely recover, in case it is required. | |
Check logs for lockout, password problems, and so forth. | |
You can administer addressing and dialing rules to limit outdialing capability on the system. By configuring the DialMap.ini file, Route Pattern and Dial-Peer, and your IP-PBX appropriately, you can minimize toll fraud. |
Posted: Thu Jun 29 06:16:14 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.