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 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.

The following guidelines take into account how Cisco Unity searches for a matching extension or Dial ID when a subscriber addresses a message. For more information about the search process, see the "How Cisco Unity Searches for a Matching Number" section.

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

In Cisco Unity 3.1(5) and 3.1(6), the default minimum length of both primary and delivery location Dial IDs is three digits. (In Cisco Unity 3.1(1) through 3.1(4), the default minimum length is one digit.) If necessary to accommodate the numbering plan for your organization, the minimum length for Dial IDs can be reduced to one or two digits by changing a registry key, as described in the following procedure "To change the minimum length of a location Dial ID." 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 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 6-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 ten digits. In Cisco Unity 3.1(5) and 3.1(6), the default minimum length is three digits. In Cisco Unity 3.1(1) through 3.1(4), although the default minimum length is one digit, it recommended that you assign a Dial ID that has at least three digits to avoid potential conflicts with priviat distribution list IDs during an address search. Although in Cisco Unity 3.1(5) and 3.1(6) 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.
Recorded Name	Record a name for the primary location. The 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 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.) 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. Extensions within a dialing domain must be unique. The dialing domain allows Cisco Unity to handle overlapping extensions on Cisco Unity servers that are outside of the dialing domain. 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. The default setting is None. Use the default when: •Your installation consists of only one Cisco Unity server. •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 SMTP and VPIM networking only)	Enter the Internet-addressable SMTP 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 required for the SMTP and VPIM networking options. Both of these networking options use the Simple Mail Transfer Protocol (SMTP) for messaging between the local Cisco Unity server and the remote voice messaging system. When a subscriber on the local Cisco Unity server addresses a message to a remote user, the Voice Connector uses the SMTP Domain Name to construct a From address, which is required by SMTP. Messages that are missing the domain name in the From address will not be delivered. Additionally, a valid From address allows the remote recipient to reply to the message.
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
Unity Bridge: Node ID Server Address (displayed only when licensed for the Bridge)	Enter information that identifies this Cisco Unity server to the Bridge and identifies the Bridge to the Cisco Unity server. •Node ID—Enter the Node ID that this Cisco Unity server represents. If this Cisco Unity server and the associated Bridge server are replacing an existing Octel Node, enter the Node ID of the Octel Node that is being replaced. The Node ID must match the Serial Number of the Unity Node that is displayed on the Unity Nodes page in the Bridge Administrator. •Server Address—Enter the fully qualified domain name of the Bridge server with which this Cisco Unity server is associated. This is the name displayed in the Windows System Control Panel on the Network Identification tab in the Full Computer Name field on the Bridge server. The Server Address must match the Cisco Unity Bridge Domain Name that is displayed on the Digital Networking page in the Bridge Administrator.

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 ActiveAssistant.

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

•In Cisco Unity 3.1(3) and later, when Cisco Unity looks up the recipient for an incoming AMIS message.

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 the recipient phone extension. 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 ActiveAssistant. While addressing messages, subscribers can switch between spelling the name and entering the extension 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 subscriber and public distribution list extensions. Only one search at the specified maximum scope level is performed. The scope of the search is dictated by the setting Subscriber Searches: Limit Searches To. 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 distribution list created on another Cisco Unity server.

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 subscriber extension, a public distribution list extension, or a number that is made up of a location Dial ID and the extension of the recipient. For example, a subscriber presses 3335678 on the phone to address a message. Table 6-2 shows possible matches:

Table 6-2 Possible Matches for the Number 3335678 

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

To accommodate a variety of numbering plans, 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 setting Subscriber Searches: Limit Searches To. If a matching number is found at any scope level, the search stops and does not continue to the next scope level. If a match is found, the recorded voice name is played to the subscriber for confirmation. (At the global directory search scope level, it is possible for duplicate extensions to exist. In this case, a list of matching names is reported back to the subscriber from which to choose.)

Cisco Unity Searches for a Matching Distribution List or Extension on the Local Server

Cisco Unity first searches for a match on the local server. 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 of the subscriber. If a match is found, the search stops.

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. If a match is found, the search stops.

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.

Cisco Unity Searches for a Matching 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 still has not been found, and if allowed by the search scope setting, the search expands to subscriber extensions in the global directory.

At each scope level, if a match is found, Cisco Unity stops the search and plays the voice name to the subscriber for confirmation.

Cisco Unity Searches for a Matching Location and Subscriber Extension

In Cisco Unity 3.1(3) and later, if a matching distribution list or subscriber extension has not been found, Cisco Unity parses the number to find a matching primary location Dial ID of a networked Cisco Unity server and a subscriber extension at that location. (In Cisco Unity 3.1(1) and 3.1(2), the search continues as described in the "Finally, Cisco Unity Searches for a Matching Delivery Location" section.)

For example, a subscriber addresses a message to 3335678. If there is a location Dial ID 333, and a subscriber at that location with the extension 5678, the sender gets voice name confirmation, and the search stops. Both primary and delivery locations are included in the search. 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. The search continues to the next level only if a match has not been found. If a match is found, Cisco Unity plays the voice name to the subscriber for confirmation.

Assuming that the minimum length for Dial IDs is set to 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 the location for an extension that matches the remaining digits in the number. If a match has not been found, and the number of remaining digits in the dialed number is more than three (which is the minimum extension length), 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 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 and stops either when a match is found or when the number of the remaining digits is three.

If you have changed the minimum number of digits in Dial IDs (as described in the "Changing the Minimum Length of Dial IDs" section), 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.

Finally, Cisco Unity Searches for a Matching Delivery Location

If a match has not been found, and depending on the search options, Cisco Unity continues with a 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.

At each scope level, Cisco Unity first searches for a delivery location Dial ID that matches the first digit entered by the subscriber. If a match is not found, and the number of remaining digits in the dialed number is more than three (which is the minimum extension length), Cisco Unity continues the search by looking for a delivery location with a Dial ID that matches the first two digits entered by the subscriber. The search for a matching location continues in this manner and stops either when a matching location is found or when the number of the remaining digits is three.

At each scope level, if one or more delivery locations are found, Cisco Unity gives voice name confirmation for the delivery location(s) only. The message is sent without confirming that the recipient exists.

Figure 6-1 illustrates the search that Cisco Unity performs when both the subscriber and blind addressing searches are set to the global directory. Note that the search for a matching location Dial ID and extension happens in Cisco Unity 3.1(3) and later.

Figure 6-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 6-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 in Cisco Unity 3.1(3) and later, 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. For this setting to be useful 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 (either 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), and subscribers are prompted to select the extension for the recipient at that location (either by spelling the name or by entering the extension). This allows subscribers to limit a search to a specific location. This option is useful when the global directory is large and addressing a message by name results in many matches. For example, assume there are two Cisco Unity servers that use Digital Networking to exchange messages. Assume 100 is the Dial ID for the primary location of the remote Cisco Unity server, and that a voice name for the location has been recorded. •A subscriber enters 100# to address a message to someone on the other Cisco Unity server. •When the primary location 100 is found, the conversation plays, "For location <Recorded voice name>, press #." •When the sender presses # to confirm, the conversation plays, "Enter the extension followed by #." •The subscriber enters 12345#. If Cisco Unity finds a matching subscriber extension at location 100, the conversation plays, "For <Subscriber recorded voice name> at extension 12345, press #." •When the sender presses # to confirm, the conversation plays, "Added. To add another name, press 1. To record the message, press #." When subscribers address a message by using blind addressing, Cisco Unity provides voice name confirmation for the delivery location to which the message is addressed. For example, assume there is a delivery location with the Dial ID 200 and that a voice name for the location has been recorded. •A subscriber enters 20056789# to blind address a message to someone at delivery location 200 with the remote mailbox number 56789. •When delivery location 200 is found, Cisco Unity plays, "For location, <Recorded voice name>, press #." •When the sender presses # to confirm, Cisco Unity plays, "Extension 56789 at location <Recorded voice name>, 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.