|
|
Communities of Interest (COI) provides businesses and their subscribers with the appearance of having their own virtual uOne system, even though they might share the same set of servers with other businesses. For example, different welcome greetings can be played for each company to which a Service Provider offers services. By implementing COI, a community is allowed to interact with its members within the community, but is restricted from viewing the members of another community.
Before you set up a Community of Interest on the Gateserver, ensure that the following tasks have been completed:
To set up a new Community of Interest, you configure items via uOne Administration, the Gateserver, and the directory server. This chapter provides the administrative procedures performed on the Gateserver.
 |
Note When you are creating COIs, it is important to make a distinction between an Intermediate Level Node (ILN) and a COI. COIs are organizations that share the same services, software, and equipment, while each maintains their own separate appearance. ILNs are not synonymous with communities. An ILN is a node, not an organization, that lies within the directory subtree on a path between the top level node (e.g., service provider) and a COI. ILNs typically correspond to resellers. No subscriber COS should have an ILN or top level node as its search base. |
By convention, a community (COI) is rooted by an organizational unit entry. The ILN/COI name is the value of the "ou" attribute for the organizational unit. It should contain no spaces. It is used to identify the COI.
|
Note Procedures for administering the directory server for a new ILN/COI will vary depending on the type of directory server deployed in your system. You may find it helpful to refer to the case study in Appendix A, which illustrates how ILN/COIs were configured for a specific hardware and software configuration. |
The following tasks are performed via uOne Administration:
|
Note You must also add these ILN/COI Administrators to the ILN/COI administrator groups used for full ACI permissions for the ILN/COI and to the "UMSA Administrators" group on the directory server. You must create such groups and ACIs if they do not exist. Refer to the Backend Servers Reference Manual. |
Each ILN/COI will need its own Class of Service. There may be multiple COSs set up for each COI, depending on the various groups of services offered. The ILNs should have just one dummy COS to allow administrator creation.
Step 2 Click on COS Administration button.
Step 3 Click on Add a COS.
Step 4 Add a Class of Service for each ILN/COI based on the following example for COS number 1
| Entry DN: ou=<ILN/COI name>,o=<top level organization> Class of Service ID: 1 Class of Service Name: One Search Base: ou=<ILN/COI name>,o=<top level organization> Personal Access UM Ini File Name: UM.ini
|
Accept default values where appropriate. See Table 15-1 for information about COS attributes.
Step 5 Click Submit to add this COS.
Step 6 Repeat steps 2 through 5 for each different COS for a COI.
Each ILN/COI needs its own Greeting Administrator, Fax, and AMIS-A (optional) Administrator accounts. Make sure each ILN/COI's Greeting Administrator, Fax, and AMIS-A Administrator accounts have unique names for clear identification. See "Setting Up Greeting Administrators", "Administering Outbound Fax", and "Administering AMIS-A Outbound" for more information about Greeting, Fax, and AMIS-A Administrator accounts.
Step 2 Click on the Global Configuration button.
Step 3 To add the Greeting Administrator, click on Add an Administrator. Use the following example as a guideline
| Full Name: msgadmin<a unique name to identify the ILN/COI> Given Name: msgadmin<a unique name to identify the ILN/COI> Last Name: msgadmin<a unique name to identify the ILN/COI> Telephone Number: <a fictitious unique number> E-mail Address: msgadmin<a unique name to identify the ILN/COI>@<e-mail domain> E-mail password: <a password> Title: Greeting Administrator Mail Quota: 0 COS DN: COS=1,ou=<first level organization>,o=<top level organization>
|
Step 4 Click on Submit.
Step 5 To add the Fax Administrator click on Add an Administrator. Use the following example as a guideline.
| Full Name: faxadmin<a unique name to identify the ILN/COI> Given Name: faxadmin<a unique name to identify the ILN/COI> Last Name: faxadmin<a unique name to identify the ILN/COI> Telephone Number: <a fictitious unique number> E-mail Address: faxadmin<a unique name to identify the ILN/COI>@<e-mail domain> E-mail password: <a password> Title: Fax Administrator Mail Quota: 0 COS DN: COS=1,ou=<ILN/COI name>,o=<top level organization>
|
Step 6 Click on Submit.
Step 7 To add the AMIS-A Administrator (optional) click on Add an Administrator. Use the following example as a guideline.
| Full Name: amisaadmin<a unique name to identify the ILN/COI> Given Name: amisaadmin<a unique name to identify the ILN/COI> Last Name: amisaadmin<a unique name to identify the ILN/COI> Telephone Number: <AMIS-A destination number for remote voice messaging system> E-mail Address: amisaadmin<a unique name to identify the ILN/COI>@<e-mail domain> E-mail password: <password> Title: AMISA Administrator AMISA-A Alternate E-mail Address: <amisa_mailbox_ID>@<e-mail domain> Mail Quota: 0 COS DN: COS=1,ou=<ILN/COI name>,o=<top level organization>
|
Step 8 Click on Submit.
Step 9 Repeat steps 2 through 6 for each COI.
Each ILN/COI will have a uOne administrator that will manage that ILN/COI. This administrator will have privileges to add, change, delete subscribers and COSs within the ILN/COI to which the administrator belongs.
You add an ILN/COI administrator as a subscriber. You can add additional ILN/COI administrators for the ILN/COI, each with a different e-mail address.
|
Note After you have created ILN/COI administrators, always use them to administer subscribers and additional COSs, instead of using umsaroot. |
Step 2 Click on the Subscriber Administration button.
Step 3 Click on Add a Subscriber. Use the following example using COS 1 as a guideline.
| Entry DN: ou=<ILN/COI name>,o=<top level organization> Full Name: <ILN/COI name>admin Given Name: <ILN/COI name>admin Last Name: <ILN/COI name>admin Telephone Number: <a unique telephone number> User ID Options: <use the telephone number for User ID> E-mail Address: <ILN/COI name>admin@<e-mail domain> E-mail password: <a password> COS DN: COS=1,ou=<ILN/COI name>,o=<top level organization>
|
Step 4 Click on Submit.
Step 5 Repeat steps 2 through 4 for each ILN/COI.
As a matter of practice, you should only use a COI administrator to administer COI subscribers. Do not add the subscribers to an ILN.
Step 2 Log in with an e-mail address of a COI administrator for the COI. By convention, a COI administrator e-mail address is: <ILN/COI name>admin@<e-mail domain>.
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 3 through 6 for each subscriber for their COI.
Step 8 Repeat steps 2 through 7 for each COI.
Different .ini files can be passed as parameters to the UM application agent in accordance with the Schedule Table token that starts the uOne application. These tokens along with the associated .ini file parameters need to be included in the Schedule.<hostname> file located in the $PARMLIB/parms/APP directory.
After the subscriber has been identified, uOne 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 the directory server. In this way, if a subscriber has been assigned to a particular COI as the search base (e.g., ou=<COI name>,o=<top level organization>), the COI administrator of that COI will not be able to administer subscribers that belong to other COIs that exist on the same directory server. The umsaroot Administrator is assigned to a higher level, e.g., o=<top level organization> as the search base. In this manner, the umsaroot Administrator will be able to see everyone under the o=<top level organization> level.
The UM application agent uses the UM.ini file. Within the LDAPConfig section of that ini file there is an LDAPsearchbase parameter. The UM application agent uses this LDAPsearchbase parameter as a starting point to retrieve the needed information from the directory server, such as identifying subscribers. You can dedicate a UM entry in the Schedule.<hostname> file to a COI by giving it a file parameter for an ini file that has a search base of the form ou=<COI name>, ou=<top level organization>. That entry is used by dedicating a DNIS or RDNIS prefix to the UM entry. This scheme does not work well for Personal Access subscribers. So, the Personal Access uOne Ini File Name COS parameter exists to provide the UM.ini file name to use for Personal Access subscribers.
After making necessary changes to a UM.ini, ensure that the LDAP parameters are duplicated in any corresponding FaxPrint.ini files.
Ensure that the appropriate sections are setup for outdialing capabilities. Each COI may have COSs that refer to different DialMap section names. We recommend that you use a COI- specific prefix for the section names, by convention this is usually the COI name.
In contrast with UM.ini, the uOne Administration configuration needs to refer to a level of the LDAP hierarchy below which all ILN/COIs reside. The searchBase parameter of schemaConfig.ini must be set to such a dn.
[<fully qualified domain name of the host>]
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 of server subtree>
[AdminFields]
UMAdmin=UMSA Administrators
SrchbaseFilter=((|c=*)(o=*)(ou=*))
Posted: Mon Sep 25 20:01:16 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.