|
|
Communities of Interest (COI) provides businesses and their subscribers with the appearance of having their own services within the uOne product, even though they might share the same set of servers with others. For example, different welcome greetings are played for each company to which a Service Provider offers services. By implementing COI, different communities (organizations) are allowed to interact with others at their own level, but are restricted from seeing outside their COI.
Before you set up a Community of Interest on the GateServer, ensure that the following tasks have been completed:
To set up a Community of Interest, you configure parameters on both the GateServer and the Directory Server. This chapter provides the configuration procedures performed on the GateServer.
The following tasks are performed on the GateServer:
Each organizational unit will need it's own Class of Service. There may be multiple COSs set up for each organizational unit, depending on the various groups of services offered.
Step 1 Access UMSA.
Step 2 Click on COS Administration button.
Step 3 Click on Add a COS
Step 4 Add a Class of Service for each Organizational Unit using the following example: 
Accept default values where appropriate. See Table 13-1 and Table 13-2 for information about COS attributes.
Step 5 Click Submit to add this COS.
Step 6 Repeat Step 2 through Step 5 for each different COS for each organizational unit.
Each organizational unit needs its own Greeting Administrator and Fax Administrator accounts. Make sure each organizational unit's Greeting Administrator and Fax Administrator accounts have unique names for clear identification. See "Setting Up Greeting Administrators" and "Administering Outbound Fax" for more information about Greeting and Fax Administrator accounts.
Step 1 Access UMSA.
Step 2 Click on the Global Configuration button.
Step 3 To add the Greeting Administrator, click on Add an Administrator. Use the following example a a guideline. 
Step 4 Click on Submit.
Step 5 To add the Fax Administrator click on add an Administrator.Use the following example a a guideline. 
Step 6 Click on Submit.
Step 7 Repeat Step 2 through Step 6 for each Organizational Unit.
Each organizational unit will have an UMSA Administrator that will manage their COI. They will have privileges to add, change, delete subscribers and COSs within their COI. These unique Administrators will be added as subscribers.
Step 1 Access UMSA.
Step 2 Click on the Subscriber Administration button.
Step 3 Click on Add a Subscriber. Use the following example a a guideline. 
Step 4 Click on Submit.
Step 5 Repeat Step 2 through Step 4 for each Organizational Unit.
Each organizational unit UMSA Administrator will add their own subscribers to their COI.
Step 1 Using your browser go to:
<GateServer Host>:280/MSGadmin
Step 2 Log in with an e-mail address as follows: (first level organization)admin@<host.com>.
Step 3 Click on Subscriber Administration.
Step 4 Click on Add Subscriber.
Step 5 Enter the correct information. See "Administering Subscriber Accounts".
Step 6 Click on Submit.
Step 7 Repeat steps Step 3 through Step 6 for each subscriber for their COI.
Step 8 Repeat steps Step 2 through Step 7 for each separate organization unit UMSA Administrator.
Different .ini files will be passed in accordance with the token that initializes the UM application. These tokens along with the associated .ini files need to be included in the Schedule.<hostname> file located in the $PARMLIB/parms/APP directory.
After the subscriber has been identified, UM will get the cosdn (a mailbox attribute that contains the dn of the COS to which the subscriber belongs) to locate the COS level attribute: SubSearchBase. From this point on, the SubSearchBase will be used for retrieving the subscriber's related information from LDAP. In this way, if the subscriber has been assigned to a particular group, e.g., ou=(first level organization)1,o=(top level organization) as the search base, even if there is more than one organization existing on the same LDAP, the administrator of that group will not be able to administer subscribers that belong to other organizations. System Administrators will be assigned to a higher level, e.g., o=(top level organization) as the search base. In this manner, the System Administrator will be able to see everyone under the o=(top level organization) level.
The UM application uses the UM.ini file. Within the LDAPConfig section there is an LDAPsearchbase field. UM uses this LDAPsearchbase as a starting point to retrieve the needed information from the LDAP server, such as identifying subscribers.
After making necessary changes to the UM.ini, ensure that the LDAP parameters are duplicated in the FaxPrint.ini file.
$PARMLIB/ADMIN/cgi-bin/MSGadmin/MSGdata/schemaConfig.ini
[hostname.com]
port=389
rootPasswd=xxxx
rootDN=cn=DirectoryManager,o=(top level organization)
searchBase=o=(top level organization)
authoritySearchBase=ou=root,o=(top level organization)
serverSearchBase=o=(top level organization)
[AdminFields]
UMAdmin=UM Administrators
SrchbaseFilter=((|c=*)(o=*)(ou=*)
Posted: Mon Sep 25 19:39:11 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.