|
|
This chapter will review the architecture of uOne Corporate Edition 4.1E, including the following topics:
The goal of this release of uOne Corporate Edition 4.1E is to provide:
The following section describes the primary components of uOne illustrated in Figure 2-1.
The telephony server communicates with CallManager and handles all voice messaging session traffic on behalf of applications.
The application controller manages multiple instances of uOne. Every time a call is made, uTel transfers control to an application instance. After the user hangs up, a new instance is started by uPilot.
This application is responsible for turning the lights on. Whenever a message is left for a user, this application interacts with uTel to turn on the message waiting light (MWI) for the user. When the user listens to all the messages, uOne turns the MWI light off.
![]() |
Note uOne turns off the MWI light after the user listens to all messages. |
There are two web-based HTTP administration tools: the uPower/Admin (previously known as Unified Messaging Systems Administration or UMSA) tool, and the uPower/Personal tool for Personal Message Administration.
uPower/Admin is a web-based tool that simplifies systems administration tasks. It is designed to make the complexities of adding information to the Directory Server and Messaging Server seamless.
uPower/Personal is a web-based tool for users to change their personal settings and modify their profiles in the Directory Server. Whenever new users are created, they are given default values for all the parameters. Any changes must be administered by the users via uPower/Personal or over the telephone through User Services.
The Unified Messaging application contains the logic to interact with uTel, directory, and messaging servers.
The LDAP Directory Server stores the uOne User profile data. uOne uses an extension of the LIPS LDAP Object Class. The current version of uOne supports the Netscape Directory Server.
The schema files necessary for Directory Server to work with uOne are included in this component.
The IMAP Messaging Server stores uOne user messages, recorded greetings, and distribution list names.
CallManager is a business telephone PBX that uses IP (Internet Protocol) to transmit sound. The CallManager 3.0 software is installed on a separate Windows 2000 system.
With the introduction of uOne Corporate Edition 4.1E, the uOne platform of services is structured on a separate system from CallManager. This dual-box platform also prepares both CallManager and uOne for better performance and preparation for future software enhancements. The following diagram shows the different scenarios for Entry and corporate editions.
| Entry Edition 100 users/4 to 8 ports | Corporate Edition 500 users/20 ports | |
CallManager 2.4 uOne Entry Edition 4.1E LDAP IMAP |
| CallManager 3.0 |
| uOne Corporate Edition 4.1E LDAP IMAP | |
| ||
|
The first scenario represents the uOne Entry Edition 4.1E utilizing the single-box platform for voice mail. The uOne Entry platform allows the uOne components to reside on the same system as CallManager. This provides a single-box solution for an IP-based messaging system, allowing four to eight uOne sessions on an NT server, along with CallManager, Directory Server, and Messaging Server. This platform was designed to work with the MCS-7830 system, and is designated as the Entry Edition.
In uOne Corporate Edition 4.1E, the uOne platform is configured to run the uOne components on a separate system from CallManager. This dual-box platform uses a MCS-7835 system for uOne, allowing the number of sessions to increase to 20, and the ability to support up to 500 users.
Because uOne Corporate Edition 4.1E automatically configures the MCS-7835 system to use the maximum of 20 sessions, no additional purchases should be made to upgrade the system for additional sessions. The initial purchase of the uOne Corporate Edition 4.1E product includes 20 sessions of uOne and a license for 100 users. Additional user licenses for the uOne product can be purchased in increments of 10.
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Thu Jun 29 04:01:48 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.