|
|
AMIS-A allows subscribers of uOne to send messages to non-uOne subscribers through the record and send a message, forward, and reply features. The system recognizes two types of non-uOne subscribers.
![]() |
Note The tasks presented in this section are required only if you implement AMIS-A Outbound Services. AMIS-A Outbound Service is an optional feature that is run on a UM 3.0 system but uses uOne backend servers and is administered with uOne Administration. Since UM 3.0 does not support internationalization, the uOne AMIS-A Outbound feature does not support internationalization either. Please contact your Account Representative for more information. |
Before you start administering AMIS-A Outbound Services, ensure that the following tasks have been completed:
You perform the following tasks to manage AMIS-A Outbound Services:
There is a one-to-one relationship between an amisaout application, an AMIS-A dial-up connection to a remote voice messaging system, and an AMIS-A Administrator Account.
Multiple amisaout applications can run on a UM 3.0 Telephony Access Server. Configuring multiple amisaout applications improves performance through load balancing.
Use the following steps to add the AMIS-A Administrator Account. This account is the special AMIS-A mailbox used to hold messages destined for a remote voice messaging system.
![]() |
Note When you name the AMIS-A Administrator account, you should consider making it descriptive (e.g., include the name or telephone number of the remote voice messaging system). A descriptive name will be helpful when you are choosing the appropriate AMIS-A Administrator account as you add subscribers in uOne Administration. |
Step 2 Click on the Global Configuration button.
Step 3 Click on Add an Administrator.
Step 4 Enter the appropriate data in the input fields (Table 13-1).
Step 5 Click on Submit.
Step 6 To add another administrative account, repeat steps 3 through 5.
| Field | Description | Valid Values | ||
|---|---|---|---|---|
Directory Server | The current directory server. System-generated entry. | This field cannot be modified. | ||
Entry DN | Indicates where in the LDAP database this entry resides. The entry distinguished name (dn) to which the administrator account belongs. | Select a dn from the drop-down menu. | ||
Full Name | A name for this administrator account. Should indicate what is unique about this account (e.g., name or number of the remote voice messaging system). | Up to 60 characters. Should not use spaces. | ||
Given Name | You can use any name. Consider using the Full Name for consistency. This field is required for the LIP entry. | Up to 60 characters. Should not use spaces. | ||
Last Name | You can use any name. Consider using the Full Name for consistency. This field is required for the LIP entry. | Up to 60 characters. Should not use spaces. | ||
Telephone Number | Enter the 10-digit AMIS-A destination telephone number for the remote voice messaging system. This field must be unique. This field is required because it is typically used as a key when searching for a particular mailbox. | 10-digit number. | ||
E-mail Address | An e-mail address for this administrator. This field is required, but not used for AMIS-A. | The format is: <user name>@<domain name>
| ||
E-mail Password | A password.
| The default password = abcd | ||
Mail Server | Identifies the messaging server that contains this AMIS-A Administrator mailbox. | Select the appropriate messaging server from the drop-down list box. Default= The messaging server set up as the system default during configuration. | ||
Title | Identifies the type of special administrator account. | Select AMIS-A Administrator title from the drop-down list box. | ||
AMIS-A Alternate E-mail Address | This is the alternate e-mail address of the mailbox that holds AMIS-A messages that are destined for a remote voice messaging system. | The format is: <user name>@<domain name> The <user name> should be: AMISA_ADMaaaxxxssss, The <domain name> should be the same as the domain in the mail server field. | ||
Mail Quota | The maximum amount of disk space in bytes that will be available for this administrative account. This amount depends on the volume of mail handled and the amount of free disk space that is available on the messaging server. | Default=0 0 bytes = unlimited disk space | ||
Class of Service DN | Identifies the Class of Service and distinguished name (dn) for the Class of Service to which this account belongs. | Select the appropriate COS DN from the drop-down menu. |
Step 2 Click on the Global Configuration button.
Step 3 Click on Modify an Administrator.
Step 4 Select a search option from the drop-down list box. The options correspond to fields in LDAP entries.
Step 5 Enter the data in the input field.
Step 6 Click on Search.
Step 7 Click on the appropriate AMIS-A Administrator account, if necessary.
Step 8 Enter the appropriate data in the input fields (Table 13-1).
Step 9 Click on Submit.
Step 10 To modify another administrative account, repeat steps 3 through 9.
![]() |
Note You cannot delete an AMIS-A Administrator that has EVMUs assigned to it. Before you delete the AMIS-A Administrator, you must delete the EVMUs first. Then, you can create new EVMU entries and reassign those EVMUs to another AMIS-A Administrator, if necessary. |
Step 2 Click on the Global Configuration button.
Step 3 Click on Delete an Administrator.
Step 4 Select a search option from the drop-down list box. The options correspond to fields in LDAP entries.
Step 5 Enter the data in the input field.
Step 6 Click on Search.
Step 7 Click on the appropriate AMIS-A Administrator account, if necessary.
Step 8 Click on Delete.
Step 9 To delete another administrative account, repeat steps 3 through 8.
The following steps will add the required amisaout parameters to the UM.ini and schemaConfig.ini files for handling External Users who are not provisioned on uOne.
Step 2 Type: cd $PARMLIB/apps/UM
Step 3 Edit the UM.ini file and set the following parameter (Table 13-2).
[UMConfig]
AMISADomain=
![]() |
Note You must configure this parameter for amisaout to work. |
Step 4 Go to the Gateserver where the schemaConfig file resides for uOne Administration and log in as spmaster.
Step 5 Type: cd ADMIN/cgi-bin/MSGadmin/MSGdata
Step 6 Edit the schemaConfig.ini file and set the following parameter (Table 13-2).
[amisaDomain]
domain=
| Parameter | Description | Valid Values | ||
|---|---|---|---|---|
In UM.ini file: AMISADomain In schemaConfig.ini file: domain | Used for external users who are not provisioned in the uOne LDAP database, that is, they are not EVMUs. When a message is being addressed or a distribution list is being defined upon determining that a phone number does not match either a subscriber or an EVMU, uOne will repeat the full number, tell the user that it is not for a subscriber on this system and ask if they want to add it anyway. If the user doesn't want to add it, uOne will proceed normally. Otherwise, an e-mail address is added to the list in the form of PhoneNumber@AMISADomainValue. | Valid e-mail domain name format. For example, AMISADomain.com Default = N/A
|
The following steps will add required information on the messaging server for the AMIS-A Administrator account that handles External Users who are not provisioned on uOne.
Step 2 From the Netscape console screen, select Messaging Server.
Step 3 Select Configuration.
Step 4 Select Services / SMTP.
Step 5 Select Address.
Step 6 On the Address screen, check the Search for custom domain box.
You add the External Voice Mail Users (EVMUs) to the LDAP directory using uOne Administration. For detailed information see "Administering AMIS-A External Users" in this manual.
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Mon Sep 25 20:10:22 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.