Table Of Contents

Primary Location Settings

Overview: Primary Location Settings

Primary Location Profile Settings

Assigning Dial IDs

Guidelines for Assigning Dial IDs and Extensions

Changing the Minimum Length of Dial IDs

Primary Location Addressing Option Settings

Subscriber Addressing Options

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 Addressing Option Settings—This section provides information about the settings that allow you to select the scope of the search performed when a subscriber uses the phone to address a message by name or extension.

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. No matter which networking option you use, the profile settings for the primary location need to be customized.

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. The following guidelines are recommended:

•Establish a fixed length for Dial IDs, and if possible, a fixed length for extensions.

•Assign unique Dial IDs. A Dial ID must not be the same as any other Dial ID or any extension assigned to a subscriber, call handler, interview handler, or public distribution list. (Note that in installations with multiple Cisco Unity servers networked together, it is unfortunately possible to assign a non-unique Dial ID due to directory replication lag time.)

•Assign a numbering range for Dial IDs that extensions do not use. For example, you can assign Dial IDs with leading zeros—001, 002, and so on.

•If you use variable-length Dial IDs and extensions, the Dial IDs should be in a different numbering range than the range for extensions. For example, if there is a local extension 750123, do not assign a location the Dial ID of 750 if there is a possibility that this location will have the extension 123.

•If you use variable-length Dial IDs, the first digits of each ID should be unique with respect to other Dial IDs. For example, if you have a location with an ID of 750, do not assign another location the ID of 7503. In this example, during a blind addressing search, Cisco Unity would always match the blind address entered by the subscriber to location 750 and fail to find location 7503.

If you do not follow these guidelines, subscribers may encounter the following problems when addressing a message:

•A delay while Cisco Unity searches for a match

•Multiple matches for the number

•Failure to find the recipient at another location 

Changing the Minimum Length of 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 For Cisco Unity failover, registry changes on one Cisco Unity server must be made manually on the other Cisco Unity server, because registry changes are not replicated.

---

To Change the Minimum Length of a Location Dial ID

---

Step 1 On the Cisco Unity server desktop, double-click the Cisco Unity Tools Depot icon.

Step 2 In the left pane, under Administrative Tools, double-click Advanced Settings Tool.

Step 3 In the Unity Settings pane, click Administration - Set the Minimum Extension Length for Locations.

Step 4 In the New Value box, enter the number, and click Set.

Step 5 When prompted, click OK. You do not need to restart the Cisco Unity server to enable the registry change.

Step 6 Click Exit.

---

Use the following table to learn more about the primary location profile settings.

Table 9-1 Network > Primary Locations > Profile Page 

Field	Considerations
Display Name	This displays the name of the primary location. To change the name, enter a new name here, and then click the Save icon.
Dial ID	Enter the ID that identifies the primary location. Enter numbers only, up to a maximum of 10 digits. The default minimum length is 3 digits. Although the minimum length for Dial IDs can be reduced by using the Advanced Settings Tool, 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 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 dial plans. 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. (For example, do not create Dial IDs like 432 and 4325.) •Even if the Dial ID will never be used by subscribers when they address messages, enter a number that does not conflict with extensions, such as 001 or 002.
Recorded Name	Record a name for the primary location. The recorded name for the location is played in the subscriber conversation in a number of places, including 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 Include Locations in Searches 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 that blocks DCOM communications.) 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. The list contains dialing domain names already configured on at least one other Cisco Unity server in the network that have replicated to the local server. Add the Cisco Unity server to a dialing domain when it is integrated with the same phone system or phone system network as other Cisco Unity servers that access the same directory. Note that the dialing domain name is case sensitive and must be entered exactly the same on all of the servers. To ensure that all servers are correctly added to the same dialing domain, enter the dialing domain name on one Cisco Unity server and wait for the name to replicate to the other Cisco Unity servers. By doing so, you also confirm that replication is working correctly among the servers. The time that it takes for the primary location data from other Cisco Unity servers to be reflected on the local server depends on your network configuration and replication schedule. A dialing domain provides a means to set the search scope for message addressing and for call transfers from the auto attendant and directory handler(s). You must add the Cisco Unity server to a dialing domain before you enable the following features: •Cross-server log in. •Cross-server transfers from the auto attendant and directory handler(s) •Live reply ("call the sender") to another Cisco Unity subscriber on another networked Cisco Unity server. •Live reply to a user on another voice messaging system who has a corresponding AMIS, Bridge, or VPIM subscriber account on another networked Cisco Unity server. •Identified subscriber messaging for Cisco Unity subscribers on different networked Cisco Unity servers. •Identified subscriber messaging for AMIS, Bridge, and VPIM subscribers, even when your installation consists of only one Cisco Unity server. The default setting is None. Use the default when: •Your installation consists of only one Cisco Unity server, and the server is not configured for AMIS, Bridge, or VPIM Networking. •Your installation consists of two or more Cisco Unity servers, but each server is integrated with a separate phone system. 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.
SMTP Domain Name (for VPIM networking only)	Enter the name of the foreign domain used by the Interop Gateway.
AMIS Node ID: Country Code, Area Code, Phone Number (displayed only when licensed for AMIS)	Enter the numbers that are transmitted by Cisco Unity to identify itself to other voice messaging systems during outgoing AMIS calls. During an outgoing AMIS call (when Cisco Unity is the originating system), the Node ID becomes the system number in the system number frame. The system number is used by the destination voice messaging system to dial out to send reply messages, or optionally to screen and reject incoming AMIS calls. The Node ID should contain all the information necessary for the destination system to send a reply message. The numbers that you enter depend on the physical location of the voice messaging system with which Cisco Unity communicates. If the country code and area code are not needed by the other voice messaging system to send a reply message, you do not need to enter them here. The maximum number of digits for each field is: •Country Code—4 digits •Area Code—3 digits •Phone Number—8 digits

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:

•When a subscriber addresses a message by using the phone.

•When subscribers add members to private lists by using the phone or the Cisco Unity Assistant.

•When an administrator adds members to private distribution lists by using the Cisco Unity Administrator.

•When Cisco Unity looks up the recipient for an incoming AMIS message. Note that the search scope for incoming Bridge and VPIM messages is always global and is not controlled by the addressing settings.

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 could be:

•A private distribution list ID.

•A Cisco Unity subscriber, an Internet subscriber, or an external subscriber extension. (The external subscriber could be either an AMIS, Bridge, or VPIM subscriber.)

•A Cisco Unity subscriber, an Internet subscriber, or an external subscriber alternate extension.

•A public distribution list extension.

•A primary location dial ID from a networked Cisco Unity server or a delivery location dial ID.

•A primary location dial ID from a networked Cisco Unity server and an extension of a Cisco Unity subscriber at that location.

•A delivery location dial ID and the extension of an external subscriber associated with the delivery location.

Additionally, when Bridge delivery locations are defined, Cisco Unity searches for a matching Bridge delivery location prefix and the remote mailbox number of the recipient. For more information, see the "How Cisco Unity Searches for a Matching Number" section of the "Primary Location Settings" chapter of the Cisco Unity Bridge Networking Guide. The guide is available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guide_book09186a0080441976.html.

For example, a subscriber presses 3335678 on the phone to address a message. Table 9-2 shows some of the possible matches:

Table 9-2 Some of the Possible Matches for the Number 3335678 

Number	Possible Match
3335678	Extension 3335678
3335678	Location dial ID 333, extension 5678
3335678	Location dial ID 3335, extension 678

To accommodate a variety of numbering plans, Cisco Unity searches for a match in stages, as the following sections describe:

1. Search for a Distribution List or Subscriber Extension on the Local Server

2. Search for a Subscriber Extension in the Dialing Domain and Then the Global Directory

3. Search for a Location Dial ID and Subscriber Extension at the Matching Location

4. Blind Addressing Search for a Delivery Location Dial ID

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 the dialing domain, and finally the global directory. The scope of the search is dictated by the Subscriber Searches: Limit Searches To setting. If a match is found at any scope level, the search stops and does not continue to the next scope level.

If the subscriber entered a one- or two-digit number, the search begins with Cisco Unity 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 on a subscriber extension, whether or not the conversation plays the recorded voice name and extension of the matched subscriber for confirmation depends on if the conversation is configured to do so, and if the recorded voice name exists. You can customize how the conversation confirms subscriber message addressing matches by using the Advanced Settings tool, available 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, 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.

If the Include Locations in Searches setting is enabled, primary locations from networked Cisco Unity servers and delivery locations created on other Cisco Unity servers are included in the search at each scope level. If the entered number matches a location dial ID, after the subscriber confirms the matched location, the conversation prompts the subscriber to enter the extension of the recipient at that location.

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 Subscriber Searches: Limit Searches To setting. 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. For example, the conversation could play: "For Kelly Bader at extension 3037 at Chicago press pound."

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 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 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 Blind Addressing: Allowed Locations setting. 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 an AMIS, SMTP, or VPIM delivery location, the matched location is returned for confirmation.

Figure 9-1 illustrates the search that Cisco Unity performs when the subscriber search and blind addressing search (if enabled) are set to the global directory, and the Include Locations in Searches setting is disabled.

Figure 9-1 Subscriber Addressing Search for a Matching Number

Location Addressing Options Settings

Use the following table to learn more about location addressing option settings.

Table 9-3 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, when members are being added to a public or private distribution list, and for incoming AMIS messages. •Local Server—Limits the search to subscribers created on the local Cisco Unity server. •Dialing Domain—If a match is not found while searching the local Cisco Unity server, the search expands to include subscribers created on other Cisco Unity servers that are in the same dialing domain as the local Cisco Unity server. •Global Directory—After searching the local Cisco Unity server and then the dialing domain (if there is one), the search expands to include every subscriber created on other Cisco Unity servers in the directory.
Include Locations in Searches	Check this check box to have locations included in searches. This option is useful when the global directory is large and addressing a message by spelling the name results in many matches. For this setting to be helpful to subscribers, locations need to have recorded voice names. When checked, this setting allows subscribers to address a message in two steps. First subscribers select a particular location (by spelling the name or by entering the Dial ID). If Cisco Unity finds a matching location, the recorded voice name for the location is played (assuming one has been recorded). At this point, subscribers can spell the name of the recipient to limit the search to the specified location. Note that if the subscriber selected the location by entering the Dial ID, the subscriber needs to switch to spelling mode (by pressing # twice) to search for the subscriber. For example, assume there are two Cisco Unity servers configured for Digital Networking. Assume 100 is the Dial ID of the primary location for the Paris Cisco Unity server, and that a voice name ("the Paris sales office") for the location has been recorded. John, a subscriber on the local Cisco Unity server, wants to send a message to Kelly Bader at the Paris location, but he does not know the correct extension. •John logs on to Cisco Unity and presses 2 to send a message. •John enters 100# to select the Paris Cisco Unity server. •When the primary location 100 is found, the conversation plays, "For the Paris sales office, press #." •John presses # to confirm; the conversation plays, "Enter the extension followed by #." •John presses ##; the conversation plays, "Spell the name of a person or distribution list." •John enters 22337#. Cisco Unity searches for a matching subscriber name at location 100, and matches on Kelly Bader. The conversation plays, "For Kelly Bader at extension 3047, press #." •John presses # to confirm; the conversation plays, "Added. To add another name, press 1. To record the message, press #."
Blind Addressing: Allowed Locations	Select the scope of the blind addressing search for a matching delivery 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. •Local Server—Limits the search to delivery locations that were created on your Cisco Unity server. •Dialing Domain—If a match is not found while searching the local Cisco Unity server, the blind addressing search expands to include those delivery locations created on other Cisco Unity servers that are in the same dialing domain as the local Cisco Unity server. •Global Directory—After searching the local Cisco Unity server and then the dialing domain (if there is one), the search expands to include every delivery location created on other Cisco Unity servers in the global directory.