|
|
uOne interfaces with the Directory Server using the LDAP protocol. The primary use of the Directory server is to store user profile information. Administration of the Directory server is accomplished through the vendor-supplied tools and Cisco's Web-based tools. Cisco tools include:
In addition, the Community of Interest (COI) feature is in large part a function of the Directory Server. This feature, similar in concept to a Virtual Private Network (VPN), allows the uOne application to provide a set of subscribers with the appearance of having their own service, even though they share the same Directory and Messaging servers with others. This feature will be discussed at the end of this chapter.
It is possible to administer the Directory server without using the Cisco tools, but it is not recommended. Cisco's tools coordinate the administration of multiple servers and apply rules and error checking.
| What | Description | Where to find it |
|---|---|---|
The fully qualified hostname of the server | | |
The LDAP distinguished name of the LDAP "superuser" | Rootdn entry in the | |
LDAP password for the LDAP "superuser" | Rootpw entry in the slapd.conf file.* (if not encrypted) | |
LDAP port number. Defaults to 389. | Port entry in the slapd.conf file.* |
* Assumes use of Netscape Directory Server
** Assumes use of a UNIX-like operating system.
The UMSA package must be installed on the Gateserver, or the Web Administration host.
Step 1 Copy the following files from the Gateserver (or Web Administration host) to your Directory Server. They are located at $HOME/ADMIN/htdocs/Ldap-Config.
amteva-schema.conf
amteva-umadmin.ldif
Step 2 Place amteva-schema.conf in the directory containing other schema configuration files (e.g., /home2/server4/slapd-<hostname>/config).
Step 3 Place amteva-umadmin.ldif in the directory containing other ldif files (e.g., /home2/server4/slapd-<hostname>/ldif).
Step 4 Incorporate the attributes and objectclass definitions from amteva-schema.conf into your existing schema definition. In the case of Netscape Directory Server 4.x, you can do this by using an include directive within the slapd.conf file to include amteva-schema.conf.
Step 5 Modify and add contents to the umadmin.ldif file, as needed.
The following table (Table 3-2) provides the requirements for Directory Server configuration.
Security | The userpassword attribute should be encrypted (preferably with Secure Hash Algorithm). Some Directory servers (e.g., Netscape Directory Server 4.x) automatically encrypt To ensure security, the directory should be configured to allow only the LDAP super user (sometimes referred to as the | |
Messaging Server Requirements | If using a directory-enabled messaging server, the directory must contain whatever entries are required for the directory-enabled messaging server used with it. For example, Netscape Messaging Server 4.x requires a SuiteSpot administrator entry, a Postmaster entry, and an entry for each subscriber. In the case of Netscape Directory Server 4.x, the SuiteSpot Administrator can be automatically added when you install the Directory Server using the Configure Directory for SuiteSpot checkbox. Use of UMSA to add subscribers will ensure that they contain the proper entries and parameters. Consult the Messaging server product documentation for details. Use of the Quick Configuration tool will automatically create initial directory content suitable for use with Netscape Messaging Server 4.x. See the uOne Gateserver Installation and Configuration Manual for more information. | |
Performance & Tuning |
| |
Indexing | Certain parameters must be indexed according to the LDAP attributes for uOne available in the "LDAP attributes" table. Lack of proper indexing will cause unacceptable search performance with a large database. On the other hand, setting up more indexing than necessary will create needless overhead on adds, deletes, and modifies, and will require extra Directory server cache space. | |
Cache | Directory server cache settings should be configured high enough for the number of entries in the Directory server and the total bytes contained in those entries. In the case of Netscape Directory Server 4.x, these settings can be found under Server Preferences - Performance Tuning. For a unified messaging system with 1,000 subscribers, we have found the following cache sizes to be appropriate:
| |
File Descriptors | If you need to support a large number of simultaneous LDAP sessions to your Directory server, it may be necessary to configure your operating system to allow a larger number of file descriptors in a process. Be sure to increase both hard and soft limits (if applicable) for file descriptors because some Directory servers require both limits to be raised. | |
Logging | Disable diagnostic trace logging in the Directory server (e.g., access logging in Netscape Directory server) to avoid processing overhead and disk overflow. | |
Certain Directory servers (e.g., Netscape Directory Server) provide configurable limits (e.g., look-through and size) on the number of LDAP entries that can be returned from an LDAP search. The broadcast message feature requires that these limits be configured to at least the number of recipients of the broadcast message list (this can be as large as the number of subscribers in the Directory server, less those that are administrative or AMIS-A). For example, if there are 100 uOne accounts, including two admin accounts and no AMIS-A, then the limits must be configured to at least 98. If the Netscape Messaging Server limits are configured too low, only a subset of the intended subscribers will receive the broadcast message. | ||
Certain directory entries are required for uOne. Most of these are automatically added via Unified Messaging System Administration (UMSA):
UMSA ensures that all the appropriate attributes are configured properly in each entry. The bulk add tool can also be used to add subscribers.
For additional information, see the uOne Administration Manual.
Access Control Instructions (ACI) include administrative groups, users, and permissions. There are several requirements for the ACIs that must be created in order to use Directory and Messaging Servers and the UMSA application. In Netscape Directory Server 4.x, groups and ACIs can be created and modified through the Directory Server Web Administration software. The SuiteSpot entries and ACIs shown below can be created automatically during the install by selecting the option to configure the directory for SuiteSpot. It is recommended as well that the installer be familiar with Netscape's Access Control List (ACL) and ACL tools provided by the Directory Server 4.x software. The ACL information can be found in the Netscape Directory Server Deployment Guide and Netscape Directory Server Administrator's Guide located at http://developer.netscape.com/docs.
Netscape Directory Server must be installed with a SuiteSpot Administrator entry and an Administrator's group entry at the base level of the hierarchy that has as a member the SuiteSpot Administrator entry DN.
The Administrator's group DN must be granted permission via a base-level ACI for all operations on the entire database.
In addition, self entry modification (i.e. write permission) should be granted via a base-level ACI. This allows users who bind and authenticate successfully as a DN to modify that DN.
By default, Netscape Messaging Server binds to the directory server anonymously. Unless you change this, you must configure the directory server to allow anonymous read, search, and compare access to subscriber entries (including the Postmaster entry). The sufficient anonymous access can be set up via the following ACI— (note that it does not allow access to the userpassword attribute).
If you change the bind DN used by the Messaging Server to not be anonymous, the bind DN you use must be allowed read, search, and compare access to subscriber entries (including Postmaster).
In order to use UMSA you must create a group with "cn=UM Administrators" having as members the LIP entry DNs of uOne subscribers or administrators who are allowed to access UMSA. For example, you could add the DN of your LIP entry to the UM Administrators group to allow yourself access to UMSA using your e-mail address and password. It is recommended that the UM Administrators group be placed at the base level.
You must also allow the appropriate UMSA users (i.e., member DNs in the "UM Administrators" group) to administer the appropriate communities of interest. This is so even if you are only using a single community. To accomplish this, you must create a group for each community subtree containing the LIP entry DNs of uOne subscribers or administrators who are allowed to administer that subtree.
Each of these group and LIP entries must be search and read accessible with anonymous access. (See above for an example of an anonymous access ACI.) You must allow each such group all forms of access to its community subtree for all parameters, and for the simple authentication method via an ACI.
To allow initial use of UMSA you must meet all of the above requirements. In preparation for initial UMSA use, you can not, of course, use UMSA to create the uOne users or administrators that are members of the above groups. Nor is it sufficient to create a user with a generic user creation tool (such as the one that is available on the Netscape Messaging Server) because certain critical parameters will not be present. In order to create an initial uOne administrator that can act as a member of "UM Administrators" and a community subtree administrator group, you can use the Quick Configuration tool (if using Netscape Directory server and Netscape Messaging server), or example LDIF file, amteva-umadmin.ldif (located in the UMSA package). To use this file, modify it to be appropriate to your site by filling in the content surrounded by arrow brackets, and perform an LDAP add of the file. (For Netscape Directory server 4.0, an LDAP add can be performed from the import dialog by using the append option.)
amteva-umadmin.ldif is ou=Root,o=Organization. Ensure that this is modified to conform to the directory structure at your location.
To allow a group of users access to the entire database, you can create a group whose members are also in "UM Administrators" and give the created group full access to the directory. In the case of Netscape Messaging Server, this can be accomplished by adding a uOne subscriber or administrator to the SuiteSpot Administrator's Group as well as to the "UM Administrators" Group. This is because the SuiteSpot Administrator's Group already has full access to the database.
In contrast to the above group with global access to the directory, you should limit community of interest (COI) specific groups to only their own community. That is, you should prevent administrators of one community subtree from accessing other community subtrees. For example, if you had both McDonald's and Burger King subtrees, you should prevent McDonald's administrators from accessing the Burger King subtree and vice-versa. An example ACI that prevents a group of subtree administrators from accessing other subtrees is:
To bring the above requirements together, the following example shows LDAP entries for a database with only one community, o=Amteva Technologies.
dn: o=Amteva Technologies
objectclass: top
objectclass: organization
o: Amteva Technologies aci: (target="ldap:///o=Amteva Technologies") (targetattr = "*")(version 3.0;
acl "Allow self entry modification"; allow (write) userdn = "ldap:///self";) aci: (target="ldap:///o=Amteva Technologies") (targetattr != "userPassword") (version 3.0; acl "Anonymous access"; allow (read, search, compare) userdn = "ldap:///anyone";) aci: (target="ldap:///o=Amteva Technologies") (targetattr = "*")(version 3.0; acl "Suitespot Adminstrators Group"; allow (all) groupdn = "ldap:///cn=Admin istrators,o=Amteva Technologies";) aci: (target ="ldap:///o=Amteva Technologies")(targetattr ="*")(version 3.0;acl "Allow Amteva Admins access to Amteva Technologies";allow (all)(groupdn = "ldap:///cn=Amteva Administrator Group,o=Amteva Technologies") and (authmethod = "simple");) aci: (target !="ldap:///o=Amteva Technologies")(targetattr ="*")(version 3.0;acl "Deny Amteva Admin from other subtrees";deny (all)(groupdn = "ldap:///cn=Amteva Administrator Group,o=Amteva Technologies") and (authmethod = "simple");) dn: cn=Administrators,o=Amteva Technologies
objectclass: top
objectclass: groupofuniquenames
cn: Administrators
uniquemember: uid=admin,o=Amteva Technologies dn: uid=admin,o=Amteva Technologies
objectclass: top
objectclass: person
objectclass: organizationalperson
objectclass: inetorgperson
cn: SuiteSpot Administrator
sn: Administrator
givenname: SuiteSpot
uid: admin
userpassword: {SHA}0DPiKuNIrrVmD8IUCuw1hQxNqZc= dn: cn=UM_Administrators,o=Amteva Technologies
objectclass: top
objectclass: groupOfUniqueNames
cn: UM_Administrators
description: UM Administrators
uniquemember: uniqueidentifier=Amteva#0000000000000046,o=Amteva Technologies
uniquemember: uniqueidentifier=Amteva#0000000000000001, o=Amteva Technologies dn: cn=Amteva Administrator Group,o=Amteva Technologies
objectclass: top
objectclass: groupOfUniqueNames
cn: Amteva Administrator Group description: Amteva Technologies Administrators
uniquemember: uniqueidentifier=Amteva#0000000000000046,o=Amteva Technologies
uniquemember: uniqueidentifier=Amteva#0000000000000001, o=Amteva Technologies dn: uniqueidentifier=Amteva#0000000000000001, o=Amteva Technologies objectclass: top objectclass: person objectclass: organizationalPerson objectclass: inetOrgPerson objectclass: nsLicenseUser objectclass: mailRecipient objectclass: LIP uniqueidentifier: Amteva#0000000000000001 postofficeid: pospgi9groupa mailhost: spsgi9.amteva.com nslicensedfor: slapd maildeliveryoption: mailbox xamtevatitle: GrtAdmin mailquota: 0 cn: vmadminspsgi9 givenname: vmadminspsgi9 sn: vmadminspsgi9 telephonenumber: 8047625500 uid: vmadminspsgi9 mail: vmadminspsgi9@systest4.amteva.com userpassword: {SHA}gf6L/odXbD7LIkJvjleEc4KRes8=l: 0 pagerenabled: no snrpagerenabled: no gender: F dn: BillingNumber=8047625500, uniqueidentifier=Amteva#0000000000000001, o=Amteva Technologies mboxname: 8047625500 objectclass: top objectclass: conf_msgbox objectclass: app_UM userlevel: 0 msghost: spsgi9.amteva.com password: 3Z191R240A0L472u umpassword: 6X1S0a273H3i1E75 cos: 0 cosdn: COS=0, o=Amteva Technologies billingnumber: 8047625500 version: 3.0 admininfo: uniqueidentifier=Amteva#0000000000000001 faxadmininfo: uniqueidentifier=Amteva#0000000000000099 playheaderformessage: no autoplayofmessages: no subscribertimezone: EST5EDT inhoursstart: 0800 inhoursend: 1700 inhoursdow: 12345 snrenabled: no badlogincount: 0 noforlastname: 86236467774498623646777449 noforfirstname: 86236467774498623646777449
Before delving further into the COI arena, a brief explanation of COI and how it can be implemented will be presented. Service Providers (SPs) may want to provide service to different customers and leverage the same equipment. These customers want the appearance that they are actually providing their own set of services, although in reality they have been provided by the SP, and the customers are, in effect, acting as a reseller of these services. This allows each reseller to provide their corporation's own greetings, directories, etc. SPs want to have administrative control over the entire system. However, they also want to be able to delegate administrative responsibilities to their customers (resellers) to control administration for these communities of users.
Additional Communities of Interest expand on the idea of providing a set of subscribers with the appearance of having their own services, even though they share the same set of systems with others. In effect, it appears as though each set of subscribers is on its own private system. When they dial into the system, the only subscribers they can see (interact with) are those administered in their own COI. When they call into the system, they will hear the Welcome Greeting for their COI. When they address messages to other subscribers, they will only see subscribers in their own COI. Broadcast messages only apply to their own COI as well.
The COI feature is based on the directory tree structure and features on the Directory Server. The directory is basically a tree structure with different levels. A COI will be defined by a specific point (node) in the tree. The COI will be allowed to interact with those at or below their node. Users within a COI are restricted from seeing outside this domain (community).
It is recommended that only after a single COI has been configured and tested that additional communities be added. These procedures are only an expansion of what is necessary for a single community, and include:
diskspaceremainingwarninglevel.
| Attribute Name | Attribute Meaning | Valid Values and Defaults | Index Setting |
|---|---|---|---|
Defines the actions for DTMP when a mailbox is set up as an autoattendant. Note AutoAttendant is not a supported feature of uOne 4.x. | Default = N/A | None | |
Whether uOne should accept messages for the subscriber while the subscriber is on vacation. | Yes/No
Default = N/A | None | |
The active greetings - Created and modified by uOne. | SpokenName, Extended_Absence, AllCalls, OutOfHours, Busy, NoAnswer, SNRGreeting.
Default = N/A | None | |
Whether to start playing new messages automatically after successful login. | Yes/No
Default = No | None | |
Pointer to the message admin account for the subscriber - used by uOne to get greeting/distlist related info. | The uniqueidentifier of the Greeting Administrator account for the subscriber.
Default = N/A | None | |
Authority name used to create the Uniqueidentifiers for the subscribers. | Any string.
Default = N/A | Equality | |
The alternative mail address. | Any RFC822 compliant mail address.
Default = N/A | Equality | |
Present only in the LIP entry for an EVMU. Subscribers, on the other hand, do not have this parameter present in their respective LDAP entries. | The remote system's four-, five-, seven-, or ten-digit ID for the EVMU.
Default = N/A | Presence | |
This mailbox is currently setup as an autoattendant. Note AutoAttendant is not a supported feature of uOne 4.x. | Default = N/A | None | |
Allows subscribers to set up their mailbox as an autoattendant. Note AutoAttendant is not a supported feature of uOne 4.x. | Default = N/A | None | |
Serves as a counter for the subscribers's consecutive failed login attempts. | Default=0 | None | |
This is the same as the primary telephonenumber of the subscriber and is associated with the mailbox. | Primary telephonenumber of the subscriber.
Default = N/A | Equality, Presence | |
When enabled, allows sender of broadcast message the ability to set expiration (in days). | On/Off
Default = N/A | None | |
When enabled, allows the sender to set MWI with a broadcast message. | Currently, can only be set to Off.
Default = Off | None | |
Country | Any string. Default = N/A | None | |
Enables a caller to transfer call to another subscriber. | yes/no
Default = no | None | |
Enables a caller to transfer to coverage (receptionist/attendant). | yes/no
Default = no | None | |
Common name of the subscriber. Typically it is the first name followed by the last name of the subscriber. | Any name that is used to identify a subscriber.
Default = N/A | Equality, Presence, Substring | |
The Class Of Service for the subscriber. | Used to get the COS parameter values for a subscriber.
Default = 0 | Equality, Presence | |
Contains the dn of the COS the subscriber belongs to. | A valid DN Default = N/A | None | |
Name of Class of Service. | String up to 60 characters.
Default = N/A | None | |
Coverage telephonenumber for the subscriber - if not created, can be created from uOne. | A valid 10 digit telephonenumber which will act as the coverage phonenumber for the subscriber.
Default = N/A | None | |
Member of the distribution list. uOne creates and maintains it. Note Non-Netscape Messaging server only. | For Netscape Messaging server: mgrpRPC822mailmember.
Default = N/A | None | |
Description of the distribution list. | Any string. Default = N/A | None | |
Percent setting for warning subscribers of the remaining disk space. | .01 - .99
Default = no warning | None | |
Maximum allowed number of entries in a distribution list. | A valid integer <= 150.
Default = 100 | None | |
Maximum allowed number of distribution lists for a subscriber. | A valid integer. Default = 10 | None | |
End of message warning threshold in seconds. When EOMsgWarning seconds of time remain, the warning is issued. Then the caller may record up to EOMsgWarning more seconds. | Valid time in sec.
Default = 30 sec. | None | |
The default outbound fax number. Can be a duplicate in the directory. | A valid 10 digit telephonenumber.
Default = N/A | None | |
Stores the uniqueidentifier of the Fax Administration user account for the subscriber. | The format of storage is the same as that for the admininfo field.
Default = None | None | |
Enables fax messages to be inventoried during the login process. | yes/no
Default = no | None | |
Gender of the subscriber. | M/F
Default = None | None | |
Maximum length of time allowed for a recorded greeting message.
Currently not in use. | Default = 60 | None | |
Defaults to the SMPP Center value if no value is present in the subscriber's SMS record. | An integer 0 -255. Default = N/A | None | |
Defaults to the SMPP Center value if no value is present in the subscriber's SMS record. | An integer 0 -255. Default = N/A | None | |
The inbound fax number used by uOne to "fax into" a mailbox - Has to be unique in the directory (aka phantom fax number). | A valid 10 digit telephonenumber.
Default = N/A | None | |
Include spoken name in messages. | yes/no Default = N/A | None | |
The valid days of the work week for the subscriber. | 0123456 for Sunday through Saturday.
Default = 12345. | None | |
The end of the business hour during the business days of the week. | 00-2400 (minutes on a 24- hr. clock).
Default = 1700. | None | |
The start of the business hours during the business days of the week. | 00-2400 (minutes on a 24- hr. clock)
Default = 0830 | None | |
The location code of a subscriber. Used in broadcast message LDAP filters. | By convention, any number in the form of X or XX.
Default = N/A | Equality | |
The email address of the subscriber. Should be unique in the whole directory. | <userid>@<domain_name>.
Default = N/A | Equality, Substring | |
Identifies an alternative e-mail address for a subscriber. Used in UMSA/PMA for processing faxes destined for a particular fax phone number. Those faxes will be forwarded to this address. Note This attribute is a Netscape extension used by the Messaging Server to match a mail address to a user. | Valid e-mail address. Default = N/A | None | |
Value of the maximum number of failed logins allowed across multiple sessions prior to locking subscriber's mailbox. | Default=6 | None | |
Maximum number of SNR numbers to try. | Default=3 | None | |
Whether to speak the inventory of messages at login.
Currently not in use | yes/no
Default = N/A | None | |
Links a subscriber's LIP record to a subscriber's SMS information record. | Subscriber's primary telephone number. | None | |
The messaging server holding the subscriber's messages. | A valid hostname with a fully qualified domain name.
Default = N/A | None | |
DTMF equivalent of the person's first name followed by the last name. | Sequence of digits
Default = N/A | Equality, Presence | |
DTMF equivalent of the person's last name followed by the first name. | Sequence of digits
Default = N/A | Equality, Presence | |
Notification expiration time in hours. | An integer 0 - 300. Default = N/A | None | |
Notification e-mail address. | A valid e-mail address. Default = N/A | None | |
Detailed message notification provides details about the specific message received. Message Count notification provides the number of "unread" messages by type. | Detailed, Message Count. Default = Detailed | None | |
A number for the device, whether it is a phone number or pager PIN. | Valid phone number or pager PIN.
Default = N/A | None | |
A number for the device, whether it is a phone number or pager PIN. | Valid phone number or pager PIN.
Default = N/A | None | |
A number for the device, whether it is a phone number or pager PIN. | Valid phone number or pager PIN.
Default = N/A | None | |
A number for the device, whether it is a phone number or pager PIN. | Valid phone number or pager PIN.
Default = N/A | None | |
A number for the device, whether it is a phone number or pager PIN. | Valid phone number or pager PIN.
Default = N/A | None | |
A number for the device, whether it is a phone number or pager PIN. | Valid phone number or pager PIN.
Default = N/A | None | |
Numbering Plan Indicator. Defaults to the SMPP Center value if no value is present in the subscriber's SMS record. | An integer 0 -255. Default = N/A | None | |
Organization | Any string. Default = N/A | None | |
Organizational Unit | Any string. Default = N/A | None | |
Subscriber's PIN number. Depending on the subscriber's paging service, the PIN number may be the last 7 digits of the subscriber's phone number or a unique PIN number provided by the paging service. | Valid PIN number.
Default = N/A | Equality | |
Determines whether the new message notification paging feature is on or off. See also SNRPager Enabled. | Yes or No
Default = No | None | |
Subscriber's pager password, if needed. Most pagers will not. | Valid password. | None | |
Type of pager that uOne will support. | Voice, numeric, or alphanumeric. | None | |
The provider of the subscriber's paging service. | Valid paging service provider name. Note Should match the values accepted by the SNPP paging server (e.g., Hylafax).Default = N/A | None | |
Maximum length for the uOne (DTMF) password. | Any number between 4 and 8.
Default = 4 | None | |
Mininmum length for the uOne (DTMF) password. | Any number between 4 and 8.
Default = 4 | None | |
The Cisco encrypted e-mail password. When encrypted, this matches the unencrypted value of the userpassword parameter. | Input range: 4 - 8 alphanumeric characters.
Default = N/A | None | |
Maximum length for the telephone password. | Any number between 4 and 8. Default = 4 | None | |
Minimum length for the telephone password. | Any number between 4 and 8. Default = 4 | None | |
Contains the section name within the Rules.<hostname> for dial string generation. | Any section name in Rules.<hostname> file, or blank. Default = N/A | None | |
When phone number input has the length as 4, 5, or 7 digits, the number is expanded to the 10-digit phone number according to the rules set up in this section of the Rules.<hostname> file. When the input length is 10 or 11 digits, the following rules apply: 10-digit - This will be the final 10-digit phone number 11-digit - Strip out the first digit from the phone, this will be the final 10-digit phone number. | Any section name in Rules.<hostname> file, or blank. Default = N/A | None | |
Whether to play the header information when playing messages. | Yes/no
Default = No | None | |
Preferred date format for notification. | mm/dd/yyyy, dd/mm/yyyy, yyyy/mm/dd Default = mm/dd/yyyy | None | |
Defines a subscriber's preferred written or spoken language. The value for this attribute should conform to the syntax for HTTP Accept-Language header values. This value is used as the prompt as well as the TTS language within uOne. | Default = eng | None | |
Preferred time format for notification. | Default = N/A | None | |
If the value is set to "no", whenever the user returns to the main menu (*1, *2), uOne skips playing the message. Inventory. When it is set to "yes", it plays the message inventory. | yes/no
Default = No. | None | |
SMPP Center Identifier. | List of available SMPP Centers. Default = None | None | |
SMPP IP Address in format xxx.xxx.xxx.xxx. | Valid IP address where xxx is 0 -255. Default = N/A | None | |
SMPP Port Address. | An integer between 0 - 32768. Default = N/A | None | |
SMSNumber | The phone number for the SMS service. Currently, this number is the same as the subscriber's primary telephone number. | Default = Subscriber's primary telephone number. | None |
Surname. Typically, the customer's last name. | Any string. Default = N/A | None | |
Contains the file name of a special .ini file for PA subscribers. | Any valid file name. | None | |
This is the Personal Access telephone number. | Any valid 10 digit telephone number.
Default = N/A | Equality | |
Single-number reach value - a telephonenumber value used by the application to reach the subscriber during business hours on business days. | A valid 10 digit telephone number.
Default = N/A | Presence | |
Single-number reach service enabled. | yes/no
Default = No | None | |
A telephone number similar to SNR, except for non business days. | A valid 10 digit telephone number.
Default = N/A | None | |
A telephone number similar to SNR, except for non-business hours. | A valid 10 digit telephone number
Default = N/A | None | |
Indicates the status of the subscriber's SNR paging service. | yes/no
Default = no | None | |
The number of rings SNR will allow before trying the next SNR telephone number - or lastly - a pager. | Range: 2-5
Default = 3 | None | |
Indicates whether a COS has the Single-number reach service feature. | SNR/NONE
Default = NONE | None | |
Indicates whether a COS has the RealAudio streaming feature. | yes/yes_premium/no | None | |
Subscriber's time zone setting. | Allowed time zones.
Default = EST5EDT | None | |
Enables subscribers to transfer calls. | yes/no
Default = no | None | |
LDAP search base uOne will use for its directory searches. This indicates the COI. | A valid DN. Default = N/A | None | |
Stores all the numbers for telephone devices associated with a particular message box. | Valid telephonenumber format - uOne currently handles only 10-digit phonenumbers. | Equality, Presence | |
Type of number. Defaults to the SMPP Center value if no value is present in the subscriber's SMS record. | An integer 0 - 255. Default = N/A | None | |
Enables the e-mail TTS feature. | yes/no Default = no | None | |
Contains the uOne (DTMF) password of a subscriber in encrypted form. | Input Range: 4-8 characters.
Default = 1234 | None | |
Concatenation of a handle issuing authority with a 16-digit unique number with # used to separate the two, and is persistent for the life of the entry in LDAP. This handle uniquely identifies the subscriber. | 16-digit number prefixed with an authority name and a #.
Default = N/A | Equality | |
A 16-digit number used in creating the uniqueidentifier. Incremented by 1 after being used. | Default = 1 | None | |
Used by uOne to track first time user password change and the initial greeting status. | 0 - 7
Default = 0. | None | |
The IMAP password for the user. Can not be modifed from uOne. PMA or UMSA allows for modification. Note Do not use vendor-supplied software to change the user password, since such software does not synchronize the password parameter to the new password. | Input format: An alphanumeric value - up to 8 characters long.
Default = No Default | None | |
Title for administrators. | GrtAdmin
Default = None | Equality, Presence, Substring |
Posted: Mon Sep 25 19:25:13 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.