|
|
This case study demonstrates how to add Communities of Interest to the uOne system. Communities of Interest (COI) allow multiple organizations to share the same services, software and equipment while providing each organization with a separate appearance. An organization cannot access information outside its COI.
This case study makes the following assumptions:
Before adding one or more Communities of Interest to uOne, the following tasks must be completed:
During the Netscape Directory Server initial installation, the following information is set up:
During the GateServer initial installation, the following information is set up:
A Service Provider purchased the uOne product. They are offering voice mail, e-mail, fax, single number reach (SNR), and paging services to their customers bundled in various packages. Their customers are Resellers or Corporations.
The Resellers who purchase the unified messaging services from the Service Provider will offer services to their customers. The Resellers customers are Corporations, Small Businesses and Consumers. Services will be offered in various bundled packages.
The Corporations (whether through the Service Provider or the Reseller) will offer services to their employees. The employees will require various services based on their function (e.g., executives, road warriors, secretaries, branch offices, etc).
The Consumers obtain services directly from the Resellers. Consumers will have the option of various types of packages of service.
In this case model, the Service Provider will add Communities of Interest for two new customers. Figure A-1 illustrates the organizational structure of these new customers.
On the Netscape Directory Server:
On the GateServer:
Figure A-2 illustrates the organizational units that will be created for the case model COIs. The top level organizational unit (o=serviceprovider) and the root organizational unit were created during the initial Directory Server installation. The new organizational units are in bold.
Step 1 Using your browser, go to the Netscape Directory Server Host <hostname:2500>
Step 2 Log in to the Directory Server as admin.
Step 3 Create a new organizational unit called reseller1 under o=serviceprovider.
Step 4 Create a new organizational unit called corporation1 under ou=reseller1, o=serviceprovider.
Step 5 Create a new organizational unit called smallbusiness2 under ou=reseller1, o=serviceprovider.
Step 6 Create a new organizational unit called corporationa under o=serviceprovider.
Step 7 Create a new organizational unit called eastcoast under ou=corporationa, o=serviceprovider.
Step 8 Create a new organizational unit called westcoast under ou=corporationa, o=serviceprovider.
Figure A-3 illustrates the organizational unit groups that will be created for the case model COIs
Step 1 Using your browser, go to the Netscape Directory Server Host <hostname:2500>
Step 2 Log in to the Directory Server as admin.
Step 3 Create a new organizational group called reseller1group under ou=reseller1, o=serviceprovider.
Step 4 Create a new organizational unit called corporation1group under ou=corporation1, ou=reseller1, o=serviceprovider.
Step 5 Create a new organizational unit called smallbusiness2group under ou=smallbusiness2, ou=reseller1, o=serviceprovider.
Step 6 Create a new organizational unit called corporationagroup under ou=corporationa, o=serviceprovider.
Step 7 Create a new organizational unit called eastcoastgroup under ou=eastcoast, ou=corporationa, o=serviceprovider.
Step 8 Create a new organizational unit called westcoastgroup under ou=westcoast, ou=corporationa, o=serviceprovider.
The Netscape Directory Server provides controlled access to directories by using access control lists (ACLs). Directory ACLs contains access control information (ACIs) that will allow or deny read, write, search and compare permissions.
Three ACIs are created for you during the initial Netscape Directory Server installation for the top level organizational unit (o=serviceprovider). These ACIs consist of:
Each organizational unit that you create will also need these three ACI statements in order to provide proper access rights.
Step 1 Using your browser, go to the Netscape Directory Server Host <hostname:2500>
Step 2 Log in to the Directory Server as admin.
Step 3 Bind to the server: cn=Directory Manager, o=serviceprovider
Step 4 Establish ACIs for each organizational unit:
Class of Service identifies specific bundles of services or various feature options available. Multiple COSs can exist within each organizational unit based on the variety of feature packages that organizational unit will offer to it's customer base.
Step 1 Using your browser, go to <GateServer host>:280/MSGAdmin
Step 2 Log in as umsaadmin
Step 3 Click on COS Administration.
Step 4 Click on Add a COS.
Step 5 Add a COS using the followings as an example:
Accept default values where appropriate. For more information about COS attributes, see "Setting Up Classes of Service" in this manual.
Step 6 Click Submit to add this COS.
Step 7 Repeat steps 4 to 6 for each COS in each organizational unit.
Each Organizational Unit requires it's own Greeting Administrator and Fax accounts. The Greeting Administrator is a special mailbox that stores personal greetings and distribution list recorded names for subscribers in their particular organizational unit. The Fax Administrator is a special mailbox that stores faxes waiting to be printed for the subscribers within the organizational unit.
Cisco recommends that each organizational unit's Greeting Administrator and Fax Administrator accounts have unique names for clear identification. For our example, a Greeting Administrator can be named msgadminreseller1 and a Fax Administrator can be named faxadminreseller1.
Step 1 Using your browser, go to <GateServer host>:280/MSGAdmin
Step 2 Log in as umsaadmin
Step 3 Click on Global Configuration.
Step 4 To add a Greeting Administrator, click on Add an Administrator.
Step 5 Add a Greeting Administrator using the followings as an example:
Accept default values where appropriate. For more information about Greeting Administrator attributes, see "Setting Up Greeting Administrators" in this manual.
Step 6 Click Submit to add this administrator.
Step 7 To add a Fax Administrator, click on Add an Administrator.
Step 8 Add a Fax Administrator using the followings as an example:
Accept default values where appropriate. For more information about Fax Administrator attributes, see "Administering Outbound Fax" in this manual.
Step 9 Click Submit to add this administrator.
Step 10 Repeat steps 4 to 9 for:
Each organizational unit requires at least one UMSA Administrator that will manage its COI. This UMSA Administrator will have privileges to add, change, and delete subscribers' accounts and COSs within the organizational unit's COI. Cisco recommends that each organizational unit's UMSA Administrator have unique names for clear identification.
You perform the following tasks to add an organizational unit UMSA Administrator:
Step 1 Using your browser, go to <GateServer host>:280/MSGAdmin
Step 2 Log in as umsaadmin
Step 3 Click on Subscriber Administration.
Step 4 To add an organizational UMSA Administrator, click on Add a Subscriber.
Step 5 Add an organizational UMSA Administrator using the followings as an example:
Accept default values where appropriate. For more information about Subscriber attributes, see "Administering Subscriber Accounts" in this manual.
Step 6 Click Submit to add this administrator as a subscriber.
Step 7 Repeat steps 3 to 6 for:
Adding the Organizational Unit UMSA Administrator to the Organizational Group
Step 1 Using your browser, go to the Netscape Directory Server Host <hostname:2500>
Step 2 Log in to the Directory Server as admin.
Step 3 Add reselleradmin as a member under cn=reseller1group, ou=reseller1, o=serviceprovider.
Step 4 Add each organizational unit's UMSA Administrator to the appropriate organizational group.
Adding the Organizational Unit UMSA Administrator to the UM Administrators Group
Step 1 Using your browser, go to the Netscape Directory Server Host <hostname:2500>
Step 2 Log in to the Directory Server as admin.
Step 3 Add reselleradmin as a member under cn=UM Administrator, o=serviceprovider.
Step 4 Add each organizational unit's UMSA Administrator as a member under cn=UM Administrator, o=serviceprovider.
Each organizational unit UMSA Administrator will manage their own COI. Organizational unit UMSA Administrator have privileges to add, change and delete subscribers and COSs within their individual COIs.
Refer to "Administering Subscriber Accounts" in this manual for the procedure to add subscribers.
Posted: Mon Sep 25 19:39:28 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.