Table of Contents
Before You Begin
The uOne system is implemented in a distributed software architecture. The main components that support this architecture are:
- ACB (Agent Communications Broker) and CMA (Call/Media Control) agents—also referred to as middleware.
- Cisco applications software.
- Back end servers.
- Gateways and gatekeepers.
 |
Note To receive an overview of these components, refer to the uOne Product Description manual. |
uOne deployment and configuration includes the following issues:
The first thing you need to do is plan and gather 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. The following list outlines general considerations.
- Are you migrating users from an existing voice, fax, e-mail 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 (Audio Messaging Interchange Specification—Analog), VPIM (Voice Profile for Internet Mail), etc.?
- What legacy systems are required for integration?
- What are your billing requirements?
- Is there an existing directory server?
- Are any directory, messaging, RADIUS (Remote Authentication Dial-In User Service), or paging servers currently in operation?
- Is this integration project part of a switch/PBX upgrade?
You will need to plan the types 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 Please refer to the uOne Product Description 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 does each community require? These may include voice, fax, or e-mail.
- 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?
- How will subscribers using the telephone be accessing services such as Personal Access, Call Forward Access, and Shared Access?
- What kind of notification services 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? In addition, what protocols—SMTP or SNPP—will you use?
- What kind of addressing and dialing rules are required?
- What special administrative accounts are required?
- What are your broadcast message needs?
System platform considerations include the following:
- What are the switch and SMSI requirements?
- What are the traffic requirements?
- What are the storage requirements?
Engineering issues that need to be considered include:
- How many gateways will be deployed and where?
- How many gatekeepers 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?
|
Note AMIS-A is not currently supported. |
- How many paging servers are there and where? In addition, what type of protocol—SMTP or SNPP—is used?
After you have defined the requirements and engineered a solution, you should have the following set of designs and plans:
- 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
- Schema design
- Logging and billing design
- AMIS-A design
- SNMP design
- Operations plan
- Administration plan
Posted: Mon Sep 25 20:19:46 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.
