-
Networking Guide for Cisco Unity Bridge Release 3.1 (For Cisco Unity Release 5.x with Microsoft Exchange)
-
Index
-
Preface
-
About Bridge Networking
-
Setting Up Cisco Unity and the Bridge for Networking
-
Upgrading Bridge 3.x Software to the Shipping Version
-
Upgrading from Cisco Unity 4.0(3) or Later with Bridge 3.x
-
Upgrading from Windows 2000 Server to Windows Server 2003 on a Bridge 3.1 or Later Server
-
Monitoring and Maintaining Bridge Networking
-
Troubleshooting Bridge Networking
-
Advanced Troubleshooting
-
Uninstalling Bridge Networking Components
-
Reference: Settings on the Bridge Server
-
Primary Location Settings
-
Cisco Unity Bridge and Avaya Interchange
-
Glossary
-
Table Of Contents
Overview: Primary Location Settings
Primary Location Profile Settings
Guidelines for Assigning Dial IDs and Extensions
Changing the Minimum Length of Primary Location Dial IDs
Primary Location Addressing Option Settings
How Cisco Unity Searches for a Matching Name
How Cisco Unity Searches for a Matching Number
Location Addressing Options Settings
Primary Location Settings
Overview: Primary Location 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 directly or indirectly with the primary location.
No matter which networking option Cisco Unity uses to send and receive voice messages, you need to customize the primary location of your Cisco Unity server.
See the following sections in this chapter for more information about the settings for the primary location:
•
Primary Location Profile Settings—This section provides information about the settings that identify the Cisco Unity server to other Cisco Unity servers or to other voice messaging systems, and provides guidelines for assigning location Dial IDs.
•
Primary Location Profile Settings
The primary location profile settings contain the network information needed to identify the Cisco Unity server to other Cisco Unity servers or to other messaging systems.
Assigning Dial IDs
The primary location profile settings contain a Dial ID, which Cisco Unity uses as an identifier for the location. You need to carefully plan the numbers that you choose as Dial IDs—for both the primary location and for any delivery locations—particularly when your organization has multiple Cisco Unity servers networked together. Without careful planning, it is possible to assign Dial IDs that have the effect of preventing Cisco Unity from finding a message recipient at another location.
In installations with multiple Cisco Unity servers networked together, be sure to consult with the administrators of the other Cisco Unity servers about the numbers that you can use for the Dial IDs of the primary location and for any delivery locations that you create. You need to verify that the Dial IDs on the local Cisco Unity server do not conflict with the Dial IDs and extensions used on other Cisco Unity servers.
Guidelines for Assigning Dial IDs and Extensions
The numbering plan for assigning Dial IDs and extensions can affect how easily Cisco Unity matches the number that a subscriber enters when addressing a message. We recommend the following guidelines:
•
•
•
•
•
If you do not follow these guidelines, subscribers may encounter the following problems when addressing a message:
•
•
•
Changing the Minimum Length of Primary Location Dial IDs
If necessary to accommodate the numbering plan for your organization, the minimum length for primary location Dial IDs can be reduced to one or two digits by changing a registry key, as described in the following "To Change the Minimum Length of a Location Dial ID" procedure. Note, however, that one- and two-digit Dial IDs may conflict with private distribution list IDs during an address search. When a subscriber addresses a message by entering a one- or two-digit number, Cisco Unity first searches for a matching private distribution list. If a match is found, the search stops. Therefore, when a subscriber addresses a message by entering a location Dial ID in order to narrow down the search scope to a particular location, if the number entered matches a private distribution list ID, the conversation offers only the private distribution list as a destination. If subscribers do not address messages to other locations by first entering a Dial ID, there is no conflict, and the minimum length for Dial IDs can be reduced to accommodate complex numbering plans.
Note
To Change the Minimum Length of a Location Dial ID
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
For detailed information about the Primary Location Profile settings page, see the "Primary Locations Profile Page" section in the "Network Settings" chapter of the Interface Reference Guide for the Cisco Unity Administrator. The guide is available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_list.html.
Primary Location Addressing Option Settings
The primary location addressing options allow you to control the scope of the search that Cisco Unity performs when searching for a matching extension in the following cases:
•
•
•
•
You can set the scope to the local Cisco Unity server, to the dialing domain that the local Cisco Unity server is a member of, or to the entire global directory.
The addressing options also allow you to enable blind addressing searches for a matching delivery location Dial ID. You can set the blind addressing scope to those delivery locations created on the local Cisco Unity server, to delivery locations within the dialing domain, or to the entire directory.
Subscriber Addressing Options
Depending on how Cisco Unity is set up, subscribers can address messages to other subscribers by spelling the recipient name or entering a number. If desired, you can disable addressing by spelled name for all subscribers on each Cisco Unity server by unchecking the Enable Spelled Name Search in the Cisco Unity Administrator on the System > Configuration > Settings page.
If addressing by spelled name is enabled, subscribers spell the name or part of the name of the recipient by using the letters on the phone keypad. The Address Messages to Other Subscribers field in the Cisco Unity Administrator on the Subscribers > Subscriber Template > Conversation page, and on the Subscribers > Subscribers > Conversation page, allows you to set the default method of addressing. Subscribers can also set this option in the Cisco Unity Assistant. While addressing messages, subscribers can switch between spelling the name and entering a number by pressing # twice (##).
How Cisco Unity Searches for a Matching Name
When a subscriber addresses a message by spelling the recipient name, Cisco Unity searches for a match or partial matches among subscribers and public distribution lists. Only one search at the specified maximum scope level is performed. The scope of the search is dictated by the Subscriber Searches: Limit Searches To setting. For example, if searches are limited to the dialing domain, one search that includes both the local server and dialing domain is performed, and a list of matching names is reported back to the subscriber.
Public distribution lists, whether created on the local Cisco Unity server or not, are always considered local in scope for addressing purposes. Thus, if the scope is set to Local Server, subscribers can still address to a public distribution list created on another Cisco Unity server.
If the Include Locations in Searches setting is enabled, then primary locations from networked Cisco Unity servers and delivery locations are included in the search. If the subscriber selects a location from the list of names returned from the search, the conversation prompts the subscriber to spell the name of the recipient at that location. This allows subscribers to limit a search for a recipient to a specific location.
How Cisco Unity Searches for a Matching Number
When subscribers address a message by entering a number, the number can be:
•
•
•
•
•
•
•
•
•
For example, a subscriber presses 3335678 on the phone to address a message. Table 11-1 shows some of the possible matches:
To accommodate a variety of numbering plans, Cisco Unity searches for a match in stages, as the following sections describe:
1.
2.
3.
4.
5.
Search for a Distribution List or Subscriber Extension on the Local Server
Cisco Unity searches for a matching number by expanding the search scope in stages, starting with the local server, then expanding to search the dialing domain, and finally searching the global directory. The scope of the search is dictated by the setting Subscriber Searches: Limit Searches To. If a match is found at any scope level, the search stops and does not continue to the next scope level.
If the subscriber enters a one- or two-digit number, the Cisco Unity begins the search by looking for a match among the private distribution lists owned by the subscriber. If a match is found, the search stops, and the matched list is returned for confirmation.
If a match has not been found, or if the subscriber entered three or more digits, Cisco Unity searches for a matching subscriber extension on the local server. The search includes extensions for regular Cisco Unity subscribers and external subscribers. Both primary extensions and alternate extensions are searched. If a match is found, the search stops.
When a match is found to a subscriber extension, the subscriber will hear a confirmation (the conversation will play the recorded voice name and extension of the matched subscriber) depending on whether the conversation is configured to do so, and whether the recorded voice name exists. You can customize how the conversation confirms subscriber message addressing matches by using the Advanced Settings tool in Tools Depot to change the setting for Subscriber Addressing Confirm Match Mode.
If a match has not been found, Cisco Unity searches for a matching public distribution list extension. Public distribution lists, whether created on the local Cisco Unity server or not, are always considered local in scope for addressing purposes. Thus, if the scope is set to Local Server, subscribers can still address to a distribution list created on another Cisco Unity server. If a match is found, the search stops, and the matched list is returned for confirmation.
Search for a Subscriber Extension in the Dialing Domain and Then the Global Directory
If a match has not been found on the local server, and if allowed by the search scope setting, the search expands to subscriber extensions in the dialing domain (if it exists). If a match is found, the search stops, and the name is returned for confirmation. If a match still has not been found, and if allowed by the scope setting, the search expands to subscriber extensions in the global directory. The search at each scope level includes extensions and alternate extensions for regular Cisco Unity subscribers and external subscribers.
It is possible for duplicate extensions to exist in the global directory. If the entered number matches more than one extension, a list of matching names is reported back to the subscriber from which to choose. However, if there is a match on an extension in the dialing domain, the search stops. For example, assume that Kelly has extension 3047 and is associated with a Cisco Unity server in the dialing domain. Joe also has extension 3047, but he is associated with another networked Cisco Unity server that is outside of the dialing domain. When a subscriber on the local server enters 3047 to address a message, the match is for Kelly, who is in the dialing domain. After finding a match at the dialing domain scope, the search stops and does not continue to the global directory; thus, the extension for Joe is not found. To address messages to Joe, Kelly would need to enter the primary location dial ID of the Cisco Unity that Joe is associated with followed by his extension.
Search for a Location Dial ID and Subscriber Extension at the Matching Location
If a matching distribution list, location dial ID, or subscriber extension has not been found, the search continues.
Cisco Unity parses the number to find a matching location dial ID and a subscriber extension at that location. Cisco Unity searches for a match by expanding the search scope in stages, starting with the local server, then the dialing domain, and finally the global directory. The scope of the search is dictated by the setting Subscriber Searches: Limit Searches To. If a match is found at any scope level, the search stops and does not continue to the next scope level. When a match is found, the conversation will confirm the match, if configured to do so.
Assuming that the minimum length for dial IDs is set to the default (three digits), at each scope level Cisco Unity first searches for a location dial ID that matches the first three digits entered by the subscriber. If a match is found, Cisco Unity searches subscribers associated with the location for an extension that matches the remaining digits in the entered number. Cisco Unity continues the search by looking for a location with a dial ID that matches the first four digits entered by the subscriber. If a match is found, Cisco Unity searches subscribers associated with the location for an extension that matches the remaining digits in the number. The search for a matching location and extension continues in this manner. Note that the search is for the primary extension of the subscriber; alternate extensions are not included in the search.
For example, a subscriber addresses a message to 3335678. Cisco Unity searches for a location with the dial ID 333. If a match is found, Cisco Unity searches for a subscriber at that location who has extension 5678. Next (regardless of whether a match was found), Cisco Unity searches for a location with the dial ID 3335. If a match is found, Cisco Unity searches for a subscriber at that location who has extension 678.
At the local scope level, only the delivery locations created on the local server are included in the search. At the dialing domain level, primary locations from other networked Cisco Unity servers and delivery locations are included in the search, if they are in the dialing domain. At the global directory level, all locations are included in the search.
If a delivery location is matched, Cisco Unity searches for an external subscriber associated with the delivery location who has an extension that matches the remaining numbers. Note that extensions are searched, and not the remote mailbox numbers.
If you have changed the minimum number of digits in location dial IDs, Cisco Unity first searches for a matching dial ID according to the minimum that you set. For example, if you reduced the minimum length of a dial ID to one, Cisco Unity begins the search at each scope level by looking for a matching dial ID that matches the first digit entered by the subscriber. (Reducing the minimum dial ID length to one or two is not recommended because of the potential conflict with private distribution list IDs.)
Blind Addressing Search for a Bridge Delivery Location Prefix
If a match has not been found, Cisco Unity will continue with a blind addressing search if the setting Blind Addressing: Allowed Locations is set to something other than the default (which is None). The search starts on the local Cisco Unity server, and then expands to the dialing domain, and then to the global directory, as applicable. If a match is found at any scope level, the search stops and does not continue to the next scope level.
At each scope level Cisco Unity first searches for a Bridge delivery location prefix that matches the first digit entered by the subscriber. If a match is found, Cisco Unity searches among the Bridge subscribers associated with the location for a matching remote mailbox number. To determine the mailbox number, Cisco Unity starts at the end of the entered number, and keeps including digits until the number of digits equals the remote mailbox length defined for the location. Note that the search is for a matching remote mailbox number and not an extension. Cisco Unity continues the search by looking for a Bridge delivery location with a prefix that matches the first two digits entered by the subscriber. If a match is found, Cisco Unity searches among the Bridge subscribers associated with the location for a matching remote mailbox number. The search for a matching Bridge delivery location prefix and remote mailbox number continues in this manner and stops when the number of the remaining digits is one.
Because this is a blind addressing search, if a matching Bridge delivery prefix is found, the matched location will be returned for confirmation even if a matching Bridge subscriber is not found. For example, assume that there is a Bridge delivery location with the following settings:
Dial ID = 100
Prefix = 256
Remote Mailbox Length = 5
Recorded Name = "Paris"A subscriber logs on to Cisco Unity and addresses a message to 2564321, where 64321 is the mailbox number of an Octel subscriber on a remote Octel node with which Cisco Unity communicates. When the search reaches the stage of looking for a Bridge delivery location prefix, Cisco Unity first searches for a Bridge delivery location with a prefix of 2, then searches for the prefix 25, and then searches for the prefix 256. Because the subscriber entered a prefix, Cisco Unity uses the remote mailbox length to determine the remote mailbox number from the entered number: 2563452. In this example, the last digit in the prefix overlaps with the first digit of the mailbox number. Assume that the search does not find a Bridge subscriber with a remote mailbox of 64321. The matched delivery location is returned for confirmation, and the conversation plays "For extension 64321 at Paris, press #." If the sending subscriber confirms the match, Cisco Unity addresses the message and sends it on its way to the Octel subscriber.
Blind Addressing Search for a Delivery Location Dial ID
If a match has not been found, Cisco Unity continues with the blind addressing search. The number is parsed to find a matching delivery location dial ID. The scope of the blind addressing search is determined by the setting Blind Addressing: Allowed Locations. The search starts on the local Cisco Unity server, and then expands to the dialing domain, and then to the global directory, as applicable.
Assuming that the minimum length for dial IDs is set to the default (three digits), at each scope level Cisco Unity first searches for a delivery location dial ID that matches the first three digits entered by the subscriber. Cisco Unity continues the search by looking for a delivery location with a dial ID that matches the first four digits entered by the subscriber. The search for a matching location continues in this manner. If the match is on a delivery location, the matched location is returned, along with the remaining digits entered as the mailbox for confirmation. If the match is on a Bridge delivery location, Cisco Unity searches among the Bridge subscribers associated with the location for a remote mailbox number that matches the remaining digits in the entered number. Note that because the match is on a location dial ID, the mailbox length is not used to construct the remote mailbox number; the remote mailbox number is presumed to be the remaining digits in the entered number. Because this is a blind addressing search, if a matching Bridge delivery dial ID is found, the matched location will be returned for confirmation.
Figure 12-1 illustrates the search that Cisco Unity performs when both the subscriber search and the blind addressing search (if enabled) are set to the global directory.
Figure 11-1 Subscriber Addressing Search for a Matching Number
Location Addressing Options Settings
When considering the address search scope settings for Cisco Unity servers in the network, keep in mind that Bridge Networking is based on a bridgehead topology. To ensure that Cisco Unity subscribers on any Cisco Unity server can address network messages to Octel subscribers, the address search scope on each server must encompass the bridgehead server because that is the server on which Bridge delivery locations and Bridge subscribers are created. Typically, you should set the address search scopes on all Cisco Unity servers to global scope. In circumstances where all Cisco Unity servers are configured to be in the same dialing domain, you can set the address search scope on all servers to the dialing domain, which in effect is the same as setting it to a global scope.
For detailed information about the Primary Location Profile settings page, see the "Location Addressing Options Page" section in the "Network Settings" chapter of the Interface Reference Guide for the Cisco Unity Administrator. The guide is available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_list.html.
