Table Of Contents
Network Settings
Overview: Network Settings
Primary Location Profile Settings
Primary Location Addressing Option Settings
Delivery Locations Profile Settings
AMIS Delivery Options Settings
AMIS Schedule Settings
Starting the Cisco Unity Administrator on Another Server
Granting Administrative Rights to Other Cisco Unity Servers
Network Settings
Overview: Network Settings
You use network settings to set up and administer Cisco Unity for use with Digital Networking and the AMIS analog protocol, both of which allow subscribers to address voice messages—by using the phone—to subscribers at other locations. With Digital Networking, the locations can be other Cisco Unity servers or computers that do not use Exchange, including other voice messaging systems that have SMTP gateways. With AMIS, the locations are other voice messaging systems that support the AMIS protocol.
The network location settings provide a general, consistent interface for setting up Cisco Unity to use different message transport mechanisms. No matter which protocol Cisco Unity uses to send and receive messages, you must customize the default location for your Cisco Unity server. If you will be using blind addressing to another Cisco Unity server or another voice messaging system, you also need to create locations on your local Cisco Unity server that correspond to the remote locations.
Refer to the following sections in this chapter for more information about network settings:
•
Primary Location Profile Settings—This section provides information about the profile settings for the primary location.
•Primary Location Addressing Option Settings—This section provides information about the settings that allow you to select the scope of a search performed when a subscriber uses the phone to address a message by name or extension.
•Delivery Locations Profile Settings—This section provides information about the profile settings for delivery locations.
•AMIS Delivery Options Settings—This section provides information about the settings that control AMIS message transmissions.
•AMIS Schedule Settings—This section provides information about the AMIS schedule settings, which in conjunction with the AMIS restriction table, controls when AMIS messages are transmitted.
•Starting the Cisco Unity Administrator on Another Server—This section provides information about accessing the Cisco Unity Administrator on other networked servers.
For more information about networking, refer to the Networking in Cisco Unity guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/net/index.htm.
Primary Location Profile Settings
Each Cisco Unity server has a primary location, which is created during installation and which cannot be deleted. The primary location identifies the Cisco Unity server and contains the networking information needed to communicate with other locations, which can be Cisco Unity servers or other voice messaging systems. With the exception of public distribution lists, all subscribers and other Cisco Unity objects (such as call handlers) created on your Cisco Unity server are associated with the primary location.
Regardless of which networking alternative Cisco Unity uses to send and receive voice messages, you need to customize the primary location of your Cisco Unity server.
For more information, refer to the "Primary Location Profile Settings" section in the "Primary Location Settings" chapter of the Networking in Cisco Unity guide. This guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/net/index.htm.
Use the following table to learn more about the profile settings for the primary location.
Table 23-1 Network > Primary Locations > Profile Page
Field
|
Considerations
|
Display Name
|
This displays the name of the primary location. To change the name of the location, enter a new name here, and then click the Save icon.
|
Dial ID
|
Enter the ID that identifies the primary location. The minimum length for a Dial ID is one digit.
The following policies are recommended:
•Establish a fixed length for Dial IDs and if possible, a fixed length for extensions.
•Assign unique Dial IDs.
•If you use variable-length Dial IDs and extensions, the Dial IDs should be in a different numbering range than extensions.
•If you use variable-length Dial IDs, the first digits of each ID should be unique with respect to other Dial IDs.
If you change the Dial ID after creating subscriber accounts, you should run the Extension Address utility again to generate new extension addresses for subscribers. To run the utility, click Start > Programs > Unity > Extension Address Utility, and then click Update.
|
Recorded Name
|
Record a name for the primary location. The subscriber conversation plays the recorded name for this primary location when:
•Subscribers associated with a Cisco Unity server in a different dialing domain address a message to subscribers associated with this location. (For example, assuming that "New York" is the recorded name for this location: "There are two matches. For John Smith, at New York, press 1. For Mary Smith press 2.")
•Subscribers associated with a Cisco Unity server in a different dialing domain listen to messages from subscribers associated with this location. (For example: "Message 1, a voice message, from John Smith at New York....")
•The setting "Play Location to Subscriber as Part of Search Results" on the Network > Primary Location > Addressing Options page is enabled on another primary location. When subscribers at the other location address a message, the recorded name for this primary location may be played in the message addressing search results along with subscriber names. (For example: "There are two matches. For Chris Newton, press 1. For New York, press 2.")
To record the name here, use the Media Master control bar. (Note that the Media Master is not available across a firewall.) Use the Options menu in the Media Master control bar to set recording and playback devices, if applicable, and to use other sound files.
|
Dialing Domain
|
Select from the list or enter the name of the dialing domain of which this location is a member. A dialing domain is a collection of Cisco Unity servers that are integrated with the same phone system or phone system network. With a networked phone system, subscribers can dial an extension without having to dial a trunk access code or prefix when calling someone who is at another location on the phone network. Thus, subscriber extensions within a dialing domain must be unique.
A dialing domain is necessary if there are Cisco Unity servers in the global directory that are integrated with different phone systems and if extensions are not unique across locations.
A dialing domain provides a means to scope message address and directory handler searches so that Cisco Unity does not search the entire global directory.
Use the default setting, which is None, when:
•Your installation consists of only one Cisco Unity server.
•Your installation consists of two or more Cisco Unity servers and each server is integrated with a separate phone system. That is, subscribers associated with one Cisco Unity server must dial a trunk access code or prefix and a full phone number rather than an extension when calling a subscriber associated with another Cisco Unity server.
There is no limit to the number of Cisco Unity servers that can be assigned to a single dialing domain, and there is no limit to the number of dialing domains. However, a Cisco Unity server can be a member of only one dialing domain.
|
Domain Name
|
Enter the Internet domain name for the Cisco Unity server. This is the right half of an e-mail address after the @ symbol (for example, london@cisco.com). Do not enter the @ symbol; Cisco Unity automatically inserts it.
The domain name is used only in SMTP blind addressing to construct extension e-mail addresses for subscribers on the local Cisco Unity server. If you change the domain name after creating subscriber accounts, you should run the Extension Address utility again to generate new extension addresses for subscribers.
|
AMIS Node ID:
Country Code, Area Code, Phone Number
|
Enter the numbers that are transmitted by Cisco Unity to identify itself to other voice messaging systems during outgoing AMIS calls.
Because Node IDs must be unique, AMIS defines the Node ID as a country code, area code, and phone number. However, the Node ID is an identifier transmitted during the AMIS call; it is not the number that is dialed to connect to the remote voice messaging system. So the Node ID numbers do not have to correspond to a real country code, area code, and phone number. If desired, the Country Code and Area Code fields may be left blank; however, the Phone Number field is mandatory.
|
Primary Location Addressing Option Settings
The location addressing options allow you to control the search that Cisco Unity performs when a subscriber addresses a message by using the phone. Using these settings, you can control the scope of the search that Cisco Unity performs as it searches for a subscriber extension. The addressing options also allow you to enable and set the scope for blind addressing searches for a location Dial ID.
These settings are also applied when members are added to public or private distribution lists by using the Cisco Unity Administrator, and when subscribers add members to private lists by using the phone or the ActiveAssistant.
For more information, refer to the "Primary Location Addressing Option Settings" section in the "Primary Location Settings" chapter of the Networking in Cisco Unity guide. This guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/net/index.htm.
Use the following table to learn more about location addressing option settings.
Table 23-2 Network > Locations > Addressing Options Page
Field
|
Considerations
|
Subscriber Searches: Limit Searches To
|
Select the scope of the search that Cisco Unity performs when a subscriber addresses a message by using the phone, or when members are being added to a public or private distribution list:
•This Server—Limits the search to those subscribers associated with the local Cisco Unity server.
•This Server's Dialing Domain—After searching the local Cisco Unity server, if a match is not found, the search expands to include those subscribers associated with the dialing domain that the Cisco Unity server is a member of.
•The Global Address List—After searching the local Cisco Unity server and then the dialing domain (if there is one), the search expands to include every subscriber in the directory.
|
Play Location to Subscriber as Part of Search Results
(not applicable to blind addressing)
|
Check this box to allow subscribers to limit a search to a specific location. When checked, this setting allows subscribers to address a message in two steps. First subscribers select a particular location (either by spelling the name or by entering the Dial ID). If Cisco Unity finds a matching location, subscribers are prompted to select the extension for the recipient at that location (either by spelling the name or by entering the extension).
This option is useful when the numbers for extensions at different locations are of different lengths or are not unique.
|
Blind Addressing: Allowed Locations
|
Select the scope of the blind addressing search for a matching location that Cisco Unity performs when a subscriber addresses a message by using the phone. Select one of the following:
•None—Do not allow blind addressing searches.
•Locations on this Cisco Unity Server—Limits the search to locations that were created on your Cisco Unity server.
•Locations in this Cisco Unity Server's Dialing Domain—After searching the local Cisco Unity server, if a match is not found, the blind addressing search expands to include those locations included in the dialing domain that the Cisco Unity server is a member of.
•Locations in the Global Address List—After searching the local Cisco Unity server and then the dialing domain (if there is one), the search expands to include every location in the Exchange directory.
|
Delivery Locations Profile Settings
Delivery locations are Cisco Unity objects that contain the addressing information that Cisco Unity needs to send messages to other voice messaging systems—which may or may not be Cisco Unity. You create a delivery location that corresponds to each remote messaging system that the local Cisco Unity server communicates with.
When creating a delivery location, you specify a Destination Type—either SMTP or AMIS. The Destination Type determines which fields are displayed on the delivery locations page. For SMTP delivery locations, you specify the domain name portion of the e-mail addresses used in SMTP blind addressing to the corresponding remote Cisco Unity server. For AMIS delivery locations, you specify the Delivery Number and the AMIS Node ID required by the AMIS protocol.
For more information, refer to the "SMTP Networking" and the "AMIS Networking" chapters in the Networking in Cisco Unity guide. This guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/net/index.htm.
Use the following table to learn more about the profile settings for delivery locations.
Table 23-3 Network > Delivery Locations > Profile Page
Field
|
Considerations
|
Name
|
This displays the name of the location. To change the name of the location, enter a new name here, and then click the Save icon.
|
Dial ID
|
Enter the ID associated with the location. When addressing a message to another location by using blind addressing, subscribers dial a number that is made up of the Dial ID and the extension (or the remote mailbox number) of the recipient. The minimum length for a Dial ID is one digit.
When setting up blind addressing for Digital Networking, the ID that you enter here must match the Dial ID of the default location at the corresponding remote Cisco Unity server.
The following policies are recommended:
•Establish a fixed length for Dial IDs and if possible, a fixed length for extensions.
•Assign unique Dial IDs.
•If you use variable-length Dial IDs and extensions, the Dial IDs should be in a different numbering range than extensions.
•If you use variable-length Dial IDs, the first digits of each ID should be unique with respect to other Dial IDs.
|
Recorded Name
|
Record a name for the location. Cisco Unity plays this recorded name for subscribers addressing a message to another location and for recipients of messages from another location.
To record the name here, use the Media Master control bar. (Note that the Media Master is not available across a firewall.) Use the Options menu in the Media Master control bar to set recording and playback devices, if applicable, and to use other sound files.
|
Destination Type
|
Displays the message transport mechanism used to send messages to the location. The Destination Type is specified when the delivery location is created, and it cannot be changed. The Destination Type is one of the following:
•SMTP—Indicates that messages are sent over the Internet by using a standard SMTP gateway. Typically, the destination is another Cisco Unity server.
•AMIS—Indicates that messages are sent to a voice messaging system other than Cisco Unity by using the AMIS analog protocol.
|
Domain Name
(for SMTP locations only)
|
Enter the Internet domain name for the Cisco Unity server that corresponds to this delivery location. This is the right half of an e-mail address after the @ symbol (for example, london@cisco.com). Do not enter the @ symbol; Cisco Unity automatically inserts it.
This Domain Name is used only in SMTP blind addressing. To address a message by using blind addressing, subscribers enter the Dial ID followed by the extension. Cisco Unity uses the specified Dial ID to look up the delivery location to obtain the Domain Name. Then Cisco Unity constructs the blind address in the following format: <Dial ID>_<Extension>@<Domain Name>.
For blind addressing to work, this Domain Name must match the Domain Name in the corresponding remote primary location. Additionally, extension addresses need to be generated for the subscribers at the remote location.
|
Delivery Phone Number
(for AMIS locations only)
|
Enter the phone number, including trunk access code, that Cisco Unity dials for outgoing AMIS calls to the remote voice messaging system that corresponds to this delivery location.
|
Node ID:
Country Code, Area Code, Phone Number
(for AMIS locations only)
|
Enter the numbers used to identify the remote voice messaging system that corresponds to this delivery location. This Node ID must match the Node ID that the corresponding remote voice messaging system transmits during incoming calls. Cisco Unity accepts messages only from known AMIS nodes, so the Node ID entered here must exactly match the Node ID that the remote voice messaging system transmits.
Because Node IDs must be unique, AMIS defines the Node ID as a country code, area code, and phone number. However, the Node ID is an identifier transmitted during the AMIS call; it is not the number that is dialed to connect to the remote voice messaging system. So the Node ID numbers do not have to correspond to a real country code, area code, and phone number. If desired, the Country Code and Area Code fields may be left blank; however, the Phone Number field is mandatory.
|
Disable Outbound Message Delivery to This AMIS Location
(for AMIS locations only)
|
By default, this box is unchecked. However, when an outbound AMIS call to this delivery location is answered by a person or a non-AMIS compliant voice messaging system (such as an answering machine), this box is checked automatically. This prevents Cisco Unity from repeatedly attempting to deliver messages to an incorrect Delivery Phone Number.
If the call is answered by a person, Cisco Unity plays a prompt that instructs the person to prevent further calls by pressing a touchtone. If the person presses the touchtone, Cisco Unity checks this box and disables outbound calls to this location. Any messages that could not be delivered to this location remain in the UAmis mailbox until you uncheck this box. Any messages remaining in the UAmis mailbox longer than 24 hours are returned to sender with a Non-Delivery Receipt (NDR).
|
AMIS Delivery Options Settings
The AMIS delivery options settings control attributes of outgoing AMIS calls. You specify settings such as how many times Cisco Unity will retry a number when it gets a busy signal, and whether urgent messages override the AMIS schedule. A restriction table that you specify is used to control which delivery numbers are allowed and processed immediately. See the "Overview: Restriction Tables" section on page 21-1 for basic information about restriction tables.
For more information, refer to the "AMIS Networking" chapter in the Networking in Cisco Unity guide. This guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/net/index.htm.
Use the following table to learn more about AMIS profile settings.
Table 23-4 Network > AMIS Options> Delivery Options Page
Field
|
Considerations
|
Deliver Urgent Messages Immediately
|
Check this box to allow messages marked as urgent to be delivered immediately. Checking this box overrides both the Local Dial Restriction Table and the AMIS schedule. When the box is unchecked, Cisco Unity handles urgent messages the same as non-urgent messages.
|
Local Dial Restriction Table
|
Select a restriction table that determines which AMIS delivery numbers can be processed immediately. If an AMIS delivery number is allowed by the restriction table, messages to this number are delivered immediately. If the delivery number is not allowed by the restriction table, messages are queued in the UAmis mailbox until the AMIS schedule becomes active.
By default, the Local Dial Restriction Table field is set to the predefined Default AMIS restriction table. You can modify the Default AMIS restriction table or select another restriction table. You may want to modify this restriction table to disallow long distance delivery numbers and adjust the AMIS schedule to become active when the long distance phone rates are lower.
|
Hang Up After This Many Rings
|
Specify the number of rings that Cisco Unity waits for the remote node to answer when making an AMIS call. After the specified number of rings, Cisco Unity hangs up. The default value is 4.
|
Try Calling This Many Times
|
Specify the number of times that Cisco Unity attempts to make an AMIS call when the remote node did not answer the initial attempt. The default value is 4. When the schedule that allows AMIS deliveries becomes inactive, the count that Cisco Unity maintains for this setting is reset to 0.
|
Retry After This Many Minutes
|
Specify the number of minutes that Cisco Unity waits after an AMIS call is not answered before attempting the call again. The default value is 5 minutes.
|
Try Calling This Many Times
|
Specify the number of times that Cisco Unity attempts to make an AMIS call when the initial attempt resulted in a busy signal. The default value is 4. When the schedule that allows AMIS deliveries becomes inactive, the count that Cisco Unity maintains for this setting is reset to 0.
|
Retry After This Many Minutes
|
Specify the number of minutes that Cisco Unity waits after receiving a busy signal before attempting the AMIS call again. The default value is 5 minutes.
|
AMIS Schedule Settings
The AMIS schedule and the AMIS restriction table together determine when outgoing AMIS calls are made. If a delivery number for an outgoing AMIS message is allowed by the AMIS restriction table, then the message is sent immediately—the schedule settings do not apply. If the delivery number is not allowed by the AMIS restriction table, then the schedule determines when the message is sent. In other words, the schedule determines when messages are sent for delivery numbers that are disallowed by the AMIS restriction table.
Cisco Unity batches messages to an AMIS location or AMIS subscriber, with a maximum of nine messages per batch. If an AMIS transmission is in progress when the schedule becomes inactive, the transmission of the entire batch of messages is completed. However, any other messages remaining in the queue, but not in the batch that was in the process of being transmitted, are queued until the next active time in the schedule. Queued messages are placed in the Inbox for the UAmis account.
Because the transmission of AMIS messages may tie up voice ports for long periods of time, you may want to schedule outgoing AMIS calls during closed hours or at times when Cisco Unity is not processing many calls. Additionally, if most or all of your AMIS delivery numbers are long distance, you may want to schedule the AMIS calls to be transmitted when the long distance phone rates are lower.
For more information, refer to the "AMIS Networking" chapter in the Networking in Cisco Unity guide. This guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/net/index.htm.
Use the following table to learn more about AMIS schedule settings.
Table 23-5 Network > AMIS > Schedule Page
Field
|
Considerations
|
Click Individual Blocks to Set Hours
|
Click the blocks in the grid to change from inactive to active hours. Click the block again to undo your change. AMIS outgoing calls are allowed only during the active hours on the schedule. Note that you can set active and inactive hours for one day, then use the Copy Day's Schedule box to copy the settings to other days.
|
Copy Day's Schedule
|
To avoid clicking the same blocks for more than one day, use the Copy Day's Schedule and >> functions. Select a day to copy, then select which days to copy the schedule setting to.
|
Starting the Cisco Unity Administrator on Another Server
When two or more Cisco Unity servers are networked together in an installation, you can access subscriber accounts and the data for other Cisco Unity objects by running the Cisco Unity Administrator on the server that the object was created on. Each Cisco Unity Administrator provides links to the Cisco Unity Administrators on other networked servers.
To start the Cisco Unity Administrator on another server
Step 1 Near the bottom of the navigation bar on the left side of the Cisco Unity Administrator interface, click Unity Servers. The Server Chooser page appears.
Step 2 From the list, click the server that you want to access.
Another instance of the Cisco Unity Administrator appears in a separate browser window. This is the Cisco Unity Administrator Web site of the Cisco Unity server that you selected.
When you want to access a subscriber account created on another server, but do not know on which server the account was created, follow the steps in the following procedure.
To access subscriber accounts created on another Cisco Unity server
Step 1 Go to any Subscribers > Subscribers page.
Step 2 Click the Find icon.
Step 3 Indicate whether to search by alias, extension, first name, or last name.
Step 4 Enter the appropriate name, alias, or extension. You also can enter * to display a list of all subscribers, or enter one or more characters or values followed by * to narrow your search.
Step 5 Check Search All Cisco Unity Servers.
Step 6 Click Find.
Step 7 On the list of matches, click the name of the subscriber to display the record.
When you select a subscriber that was created on another Cisco Unity server, another instance of the Cisco Unity Administrator appears in a separate browser window. This is the Cisco Unity Administrator Web site of the Cisco Unity server on which the subscriber account was created. The subscriber profile page is displayed in the new browser window.
Granting Administrative Rights to Other Cisco Unity Servers
Administrators on the local Cisco Unity server need appropriate rights to access the Cisco Unity Administrator on another server. The easiest way to set this up is to run the GrantUnityAccess utility and associate the domain account of each administrator with a subscriber account that has class of service rights to the Cisco Unity Administrator on a particular server.
With GrantUnityAccess, you can associate multiple domain accounts with one subscriber account, so you do not need to create subscriber accounts on each server that an administrator needs to access. Use GrantUnityAccess to assign a domain account to Unity Installer_<server name> (a built-in account which is a member of the Cisco Unity Default Administrator class of service), to the predefined EAdministrator subscriber account, or to any subscriber account that has the appropriate class of service rights to the Cisco Unity Administrator.
GrantUnityAccess is a command line utility found in the folder in which Cisco Unity is installed (the default location is C:\CommServer). You cannot run the GrantUnityAccess utility remotely across a network, so you will need to run it on each Cisco Unity server that you want to make accessible, and for each domain account that you want to map. Make sure that these domain accounts already have the necessary administrative permissions on the Cisco Unity server, and that the account you use to access the utility is a member of the Local Administrators group on the Cisco Unity server. For further guidelines on allowing access to the Cisco Unity Administrator, see the "Class of Service System Access Settings" section on page 12-6. As a best practice, do not use Unity service accounts to administer Cisco Unity.
To run GrantUnityAccess
Step 1 On the Cisco Unity server, open a command prompt window (click Start > Programs > Accessories > Command Prompt, or click Start > Run and then enter cmd).
Step 2 Change to the directory in which Cisco Unity was installed. Assuming that Cisco Unity was installed in the CommServer directory, enter the following command:
Step 3 Run the utility with the following arguments:
GrantUnityAccess -u <Domain>\<UserAlias> -s <UnitySubscriberAlias>
For information about these and other arguments, enter:
For example, assume that JSmith, KChen, and NJones are the domain accounts of administrators who need access to another Cisco Unity server, and that their accounts are in a domain called NewYorkDomain. To associate these domain accounts with the predefined EAdministrator subscriber account, open a command prompt window, and change to the CommServer directory. Then run GrantUnityAccess three times as follows:
GrantUnityAccess -u NewYorkDomain\JSmith -s EAdministrator
GrantUnityAccess -u NewYorkDomain\KChen -s EAdministrator
GrantUnityAccess -u NewYorkDomain\NJones -s EAdministrator
If there are several servers that the administrators need access to, you can create a batch file that contains the commands to avoid entering the commands repeatedly.
The GrantUnityAccess utility has additional uses. See the "About Migrating Users from Windows NT to Windows 2000" section on page 13-3 for more information.
Feedback