|
|
The following are some of the architectural goals of uOne:
Single Box Solution---The goal of this release is to be able to provide a single box solution for uOne including running uOne, the Directory, Messaging, and HTTP Server on a single NT server.
IP Based Solution---The goal of this release is to have a completely IP based messaging system to supply voice/unified messaging services for IP based telephony services.
Support Standards and Off-the-Shelf components---This provides you with flexibility and choices. You can choose the products and vendors your company wants to use. You may be looking for the best-in-class products or the best value or the least cost.
Simply Another Client/Server Application---Voice/unified messaging doesn't need to be thought of as a "special" standalone "switch adjunct". You should consider it as simply another application you rely on to run your business. It should run on the same computers, networks, and e-mail messaging systems you are already purchasing, deploying, and maintaining, thereby saving you money, resources, and training.
Simplified Administration---Your team is already well positioned to support this new environment. If you think of uOne as adding value to your existing e-mail environment and extending it for voice through standard MIME attachments, your e-mail administrators are already well positioned to support uOne. Now you do not have to support two disparate environments. Additionally, our goal is to provide you with a simplified installation, administration, and operations environment.
Interoperability with other CISCO Messaging Solutions---This allows you to mix and match Messaging Solutions and still share the same set of backend servers and data. You can deploy uOne for branch offices, and uOne 4.1S for large Service Providers, and they will all interoperate.
The following section describes the different components of uOne with the help of Figure 5-1:
The telephony server communicates with CallManager and handles all the voice messaging session traffic on behalf of applications.
The application controller manages multiple instances of uOne. Every time a call is made an application instance is handed the control by uTel. After the user hangs up, a new instance is started by the uPilot.
This application is responsible for turning the lights on. Whenever a message is left for a user, this application will interact with uTel to turn the light on for the user. When the user listens to all the messages, uOne turns the light off.
There are two web based administration tools, namely, the Unified Messaging Systems Administration (uPower/UMSA) tool and the Personal Message Administration (uPower/PMA) tool.
uPower/UMSA is a web-based tool that simplifies systems administration tasks. It is designed to hide the complexities of adding information to the Directory Server and Messaging Server.
uPower/PMA is a web-based tool that can be used by users to change the personal settings/modify the profile 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/PMA or over the telephone through User Services.
The Unified Messaging application contains the logic to interact with uTel, directory, and messaging servers.
The schema files necessary for Directory Server to work with uOne are included in this component.
The LDAP Directory server stores the uOne User profile data. uOne uses an extension of the LIPS LDAP Object Class. uOne 1.0.6 supports the Netscape Directory Server.
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.
Posted: Wed Jun 21 04:00:40 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.