Table of Contents
Before You Begin
uOne is a messaging service that consists of voice mail, fax services, e-mail, text-to-speech services (TTS), and other services. The system is implemented in a distributed software architecture. The main components that support this architecture are:
- Distributed Agent Platform (DAP—also referred to as middleware)
- Cisco applications software
- Backend servers and Network Management stations
Note To receive an overview of these areas, refer to the uOne Gateserver Installation and Configuration Manual manual.
The successful deployment of uOne involves the following issues. Items are listed in the order they should be addressed:
Furthermore, uOne supports outbound Simplified Message Station Interface (SMSI). Throughout these manuals, the terms SMDI, Simplified Message Desk Interface, and SMSI will be used interchangeably. uOne supports the Bellcore (Telcordia) specification TR-NWT-000283 SMDI, Generic Performance Requirements and Generic Requirements. uOne also supports inbound call data in the H.225.0 setup message.
The first thing you need to do is plan and gather information. The following outlines an approach to planning to include general considerations as well as user and system requirements. Then take your requirements and create a set of designs including—application, switch, system hardware/software, configuration, billing, legacy system integration, operations, user administration, etc. These and other topics should be discussed with your Account Manager and/or Sales Engineer.
- Are you migrating users from an existing voice, fax, email or unified messaging system? If so, what interoperability is required between old and new systems?
- Do you require interoperability with the existing system? If yes, what interfaces are available (AMIS-A, VPIM, etc.)?
- What legacy systems are required for integration?
- What are your billing requirements?
- Is there an existing directory server?
- Are any of the following currently in operation—directory, messaging, paging, streaming servers, and/or SNMP manager?
- Is this integration project part of a switch/PBX upgrade?
You need to layout what type of services you will be providing and to whom. This information will affect your LDAP directory structure. The application features you require will determine what types of gateway boards you will need, what Cisco software is required (middleware and applications), the switch interface requirements, administration requirements, etc. The types of questions you need to ask include:
- How many Communities of Interest (COI) do you want to create? What is the structure?
Note See the COI Business Diagram provided below (Figure 1-1). Also, please refer to the uOne Gateserver Installation and Configuration Manual for further explanation of COI.
- What capabilities do you require per COI? How many subscribers do you require per community?
- What administrators do you want to create and what kind of privileges do you want to provide?
- What bundles of services are required for each community? These may include voice, fax, or email.
- What access devices will you support? These may include a PC, and/or telephone, and/or fax.
- How many Classes of Service will be required? What are the attribute values for each COS?
Figure 1-1: Sample COI Business Diagram
- How will subscribers using the telephone be accessing services such as Personal Access, Call Forward Access, and Shared Access?
- What kind of Notification will be required? Paging? Stutter dial-tone? MWI light?
- If Personal Access is enabled, is paging required?
- If paging is required, who are the paging providers you will be accessing?
- What kind of Addressing and Dialing Rules are required?
- What special accounts are required?
- What are your broadcast message needs?
- What are the Switch and SMSI requirements?
- What are the traffic requirements?
- What are the storage requirements?
- How many Gateway servers will be deployed and where?
- How many Gatekeeper servers will be deployed and where?
- How many Messaging Servers and where?
- How many Directory Servers and where?
- How many Notification Servers and where (one per Messaging Server)?
- How many AMIS-A Servers and where?
- How many Paging Servers and where?
- How many Streaming Servers and where?
- Where is the SNMP Manager?
After you have taken the requirements and engineered a solution, you will have a set of designs:
- Application Design.
- Switch Design.
- System Design - defined hardware and software required on each system, including the definition of all configuration files.
- Addressing and Dialing Rules Design for each GateWay Server.
- Schema Design.
- Logging and Billing Design.
- AMIS-A Design.
- SNMP Design.
- Operations Plan.
- Administration Plan.
Posted: Mon Sep 25 19:13:07 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.
