Networking in Cisco Unity Guide (With Microsoft Exchange), Release 4.0(1) - Digital Networking [Cisco Unity]

Table Of Contents

Digital Networking

Overview: Digital Networking

Requirements for Setting Up Digital Networking

In this Chapter

Task List: Setting Up Digital Networking

Procedures for Setting Up Cisco Unity To Use Digital Networking

Enabling Messaging Among Cisco Unity Servers in Different Exchange 5.5 Sites

Customizing the Primary Location

Setting Search Options

Adding Alternate Extensions

Setting Up Automated Attendant Transfers to Networked Cisco Unity Servers

Digital Networking Concepts and Definitions

Locations and Digital Networking

Dialing Domains

Dialing Domains Shield Against Overlapping Dial Plans

Networked Phone Systems and Dialing Domains

Addressing Options for Non-Networked Phone Systems

When Dial Plans Do Not Overlap

When Dial Plans Overlap

Cisco Unity Administrator Scope

Mapping Subscribers to Cisco Unity Servers

Granting Administrative Rights to Other Cisco Unity Servers

Distribution Lists

Hiding Voice-Mail-Only Subscribers

Notable Behavior

Call Transfer Settings Unavailable

Subscriber ID Unavailable

Digital Networking

Overview: Digital Networking

In organizations with multiple Cisco Unity servers connected to a network with a single, global directory, each Cisco Unity installation serves a distinct group of subscribers. Cisco Unity Digital Networking is the feature that allows subscribers associated with one Cisco Unity server to exchange voice messages with subscribers associated with other Cisco Unity servers.

Digital Networking also provides the means to transfer calls from the automated attendant or directory assistance to subscribers who are not associated with the local server. (Note there are limitations to this functionality. See the "Notable Behavior" section for more information.) If your organization also has the FaxMail and Text-to-Speech E-mail features, subscribers can use the phone to forward fax and e-mail messages to any subscriber in the organization.

Although Cisco Unity stores information about subscribers (and other Cisco Unity objects such as call handlers) in a SQL database on the Cisco Unity server, a small subset of information about subscribers, distribution lists, and locations is also stored in the directory to enable Digital Networking. When subscriber and location data from other Cisco Unity servers replicates in the directory, Cisco Unity detects the data and updates the SQL database. Because of directory replication, each Cisco Unity server has the information that it needs to address voice messages to subscribers associated with the other Cisco Unity servers.

The directory in which Cisco Unity stores data is determined when Cisco Unity is set up. During setup, you specify one Exchange server (the partner Exchange server) through which Cisco Unity communicates with other Exchange servers in the network. If the partner server is Exchange 2000, Cisco Unity uses Active Directory. If the partner server is Exchange 5.5, Cisco Unity uses the Exchange 5.5 directory.

Digital Networking is enabled on every Cisco Unity server. There are no additional licenses that you need to obtain to set up Digital Networking. However, you may want to add a licensed feature called license pooling. License pooling allows Cisco Unity servers that are set up for Digital Networking to pool licenses for subscribers and the Cisco Unity Inbox. (Note that in version 3.1 and earlier, the Cisco Unity Inbox was known as the Visual Messaging Interface or VMI.)

With license pooling, if total utilization across all the Cisco Unity servers does not exceed total licenses for the feature, the Cisco Unity server is in compliance with licensing restrictions. For example, suppose two Cisco Unity servers each have 500 licenses for subscribers. With license pooling, one of the servers can use 501 or more licenses as long as the total used by both servers does not exceed 1000.

For each Cisco Unity server, you can choose whether it will participate in the pool. To place a Cisco Unity server in the pool, install a license file containing the license pooling feature on the server. If the license pooling feature is not installed on a Cisco Unity server, the server does not participate in the pool, and compliance for all features is measured on a per-machine basis.

For all other licensed features, licensing is on a per-machine basis. Licensing information is stored with the primary location for each Cisco Unity server. Because location data is stored in the directory, each Cisco Unity server has the information that it needs to keep track of license usage in the pool.

For more information about adding licensed features, refer to the "Obtaining License Files" section in the "Upgrading or Modifying a Cisco Unity 4.0 System" chapter of the Cisco Unity Installation Guide. (The Cisco Unity Installation Guide is available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_guides_books_list.html.

Requirements for Setting Up Digital Networking

The key to Digital Networking is that all the Cisco Unity servers access a common directory. To use Digital Networking, the Cisco Unity servers must be in one of the following configurations:

•The same Active Directory forest.

•The same Exchange 5.5 site.

•Different sites within the same Exchange 5.5 organization, but with Exchange message and directory replication connectors installed. (Without the message and directory replication connectors, Digital Networking does not work.)

Additionally:

•The Cisco Unity servers that are networked together can be any combination of Cisco Unity version 3.1(2) or later. If you have an existing Cisco Unity server version 2.4(6) through 3.1(1), and you want to add another Cisco Unity server for Digital Networking, the existing server must be upgraded.

•To use Digital Networking in a mixed Exchange environment, all the Cisco Unity servers must use Exchange 2000 for a partner server. Digital Networking between a Cisco Unity server with a partner Exchange 5.5 server and a Cisco Unity server with a partner Exchange 2000 server is not supported, because the required Cisco Unity-specific attributes do not replicate correctly through the Microsoft Active Directory Connector (ADC).

In this Chapter

In this chapter, you will find procedures for setting up Digital Networking, followed by detailed discussions of the concepts and terminology you need to understand. See the following sections:

•Task List: Setting Up Digital Networking—This task list provides a high-level overview of all of the tasks you need to complete, and the order in which they should be completed.

•Procedures for Setting Up Cisco Unity To Use Digital Networking—This section contains all of the procedures necessary to set up Cisco Unity for Digital Networking.

•Digital Networking Concepts and Definitions—This section explains Digital Networking concepts in detail. Be sure to read this section prior to completing the setup procedures.

•Notable Behavior—This section contains information about notable behavior related to Digital Networking.

Related Documentation

•"Accessing Voice Mail in Multiple Unity Server Environments"—available on Cisco.com at http://www.cisco.com/warp/public/788/AVVID/one_message_button_two_unity_servers.html.

•"White Paper: Cisco Unity Data and the Directory"— available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_technical_reference_list.html.

Task List: Setting Up Digital Networking

Use this task list to set up Digital Networking on each Cisco Unity server. The list assumes that Cisco Unity is already installed on the servers and that they are connected to the network. The cross-references take you to detailed procedures for the setup.

1. If the partner Exchange servers are in different sites within the same Exchange 5.5 organization, you need to change registry keys on each Cisco Unity server. You should also verify that site connectors are installed and functioning properly. See the "Enabling Messaging Among Cisco Unity Servers in Different Exchange 5.5 Sites" section.

2. Customize the primary location. See the "Customizing the Primary Location" section.

3. Set the search options. See the "Setting Search Options" section.

4. Optionally, add alternate extensions to each subscriber account. See the "Adding Alternate Extensions" section.

5. Optionally, if the Cisco Unity servers are integrated with a networked phone system, set up automated attendant transfers to subscribers associated with other Cisco Unity servers in the same dialing domain. See the "Setting Up Automated Attendant Transfers to Networked Cisco Unity Servers" section.

Skip this task if each Cisco Unity server is integrated with a separate phone system.

6. Test the Digital Networking setup.

Note Each Cisco Unity server stores the primary location data and a subset of the data about subscriber accounts and distribution lists in the directory. The time that it takes for data from other Cisco Unity servers to be reflected on the local server depends on your Active Directory or Exchange 5.5 network configuration and replication schedule. You need to wait for the Cisco Unity data to replicate to the other servers before testing the Digital Networking setup.

Procedures for Setting Up Cisco Unity To Use Digital Networking

This section contains all of the procedures necessary to set up Cisco Unity for Digital Networking.

Enabling Messaging Among Cisco Unity Servers in Different Exchange 5.5 Sites

If the partner Exchange servers are in different sites within the same Exchange 5.5 organization, Exchange message and directory replication connectors (also called site connectors) must be installed. If the site connectors are not already installed, install them now. Verify that the site connectors function properly before proceeding. Refer to your Microsoft Exchange documentation for more information.

Do the following procedure only if the partner Exchange servers are in separate sites in an Exchange 5.5 organization. Skip this procedure if the partner Exchange servers are in the same Exchange 5.5 site, or if the partner Exchange server is running Exchange 2000.

To allow messaging among Cisco Unity servers in the entire Exchange 5.5 organization

Step 1 Stop the AvDSEx55 service. (On the Windows Start menu, click Programs > Administrative Tools > Services. Right-click AvDSEx55, and select Stop.)

Step 2 Start Regedit.

Caution Changing the wrong registry key or entering an incorrect value can cause the server to malfunction. Before you edit the registry, confirm that you know how to restore it if a problem occurs. (Refer to the "Restoring" topics in Registry Editor Help.) Note that a typical backup of the Cisco Unity server does not back up the registry. Also note that 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. If you have any questions about changing registry key settings, contact Cisco TAC.

Step 3 If you do not have a current backup of the registry, click Registry > Export Registry File, and save the registry settings to a file.

Step 4 Expand the following key:
HKEY_LOCAL_MACHINE\Software\ActiveVoice\Directory Connectors\DirSynchEx55\1.00\Locations
Step 5 Double-click SearchRoot to display the Edit String dialog box.

Step 6 Replace the entire string in the Value Data box with the following:

o=OrganizationName

Substitute the name of your Exchange organization for OrganizationName. Verify that the value in the box is only o=OrganizationName.

Step 7 Click OK.

Step 8 Expand the following key:
HKEY_LOCAL_MACHINE\Software\ActiveVoice\Directory Connectors\DirSynchEx55\1.00\MailUsers
Step 9 Double-click SearchRoot to display the Edit String dialog box.

Step 10 Replace the entire string in the Value Data box with the following:

o=OrganizationName

Substitute the name of your Exchange organization for OrganizationName. Verify that the value in the box is only o=OrganizationName.

Step 11 Click OK.

Step 12 Expand the following key:
HKEY_LOCAL_MACHINE\Software\ActiveVoice\Directory 
Connectors\DirSynchEx55\1.00\DistributionLists
Step 13 Double-click SearchRoot to display the Edit String dialog box.

Step 14 Replace the entire string in the Value Data box with the following:

o=OrganizationName

Substitute the name of your Exchange organization for OrganizationName. Verify that the value in the box is only o=OrganizationName.

Step 15 Click OK.

Step 16 Expand the following key:
HKEY_LOCAL_MACHINE\Software\ActiveVoice\Directory Connectors\DirSynchEx55\1.00
Step 17 Double-click LastUSN to display the Edit DWORD Value dialog box.

Step 18 Replace the value in the Value data box with 0.

Step 19 Click OK and then close Regedit.

Step 20 Start the AvDSEx55 service. (On the Windows Start menu, click Programs > Administrative Tools > Services. Right-click AvDSEx55, and select Start.)

Customizing the Primary Location

See Table 7-1 on page 7-3 for detailed information about the primary location profile settings.

To customize the primary location

Step 1 In the Cisco Unity Administrator, go to the Network > Primary Location > Profile page.

Step 2 Enter a meaningful name for the location.

Step 3 Enter a Dial ID. The Dial ID identifies this location to Cisco Unity.

Step 4 Record a voice name for the location.

Step 5 Do one of the following:

•If the location does not belong to a dialing domain, click None.

•If the location does belong to a dialing domain, enter the Dialing Domain name only on one Cisco Unity server that is in the dialing domain, and wait for the name to replicate to the other Cisco Unity servers.

Note When setting up the primary location of the other Cisco Unity servers that are members of the dialing domain, select the Dialing Domain name from the list instead of entering a name.

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.

Step 6 Click the Save icon.

Setting Search Options

For detailed information about the search option settings, see the "Primary Location Addressing Option Settings" section on page 7-5, and the "Directory Handler Search Options Settings" section in the "Directory Handler Settings" chapter of the Cisco Unity System Administration Guide. (The Cisco Unity System Administration Guide is available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_administration_guide_books_list.html.)

To set search options

Step 1 In the Cisco Unity Administrator, go to the Network > Primary Location > Addressing Options page and set the addressing options as needed.

•To allow subscribers created on the local Cisco Unity server to address messages to subscribers on other Cisco Unity servers (that access the same directory), select Dialing Domain or Global Directory, as appropriate.

•If you are using blind addressing to a Cisco Unity server in a separate directory, or to another voice messaging system, set the Blind Addressing Allowed Locations setting to something other than None, as appropriate.

Step 2 If you want locations included in address searches, check Include Locations in Searches. The location name is played only when a subscriber enters the location dial ID when addressing a message.

Step 3 Go to the Call Management > Directory Handlers > Search Options page, and modify the search options for an existing directory handler, or create a new directory handler for unidentified callers who use directory assistance.

To allow subscribers on other Cisco Unity servers to be located in directory assistance, select Dialing Domain. (The Cisco Unity servers must be in the same dialing domain as the local Cisco Unity server.)

Adding Alternate Extensions

The procedures in this section are optional for setting up Digital Networking. If all the extensions across locations are unique, you probably do not need to set up alternate extensions. See the "Dialing Domains" section and the "Addressing Options for Non-Networked Phone Systems" section to determine whether you need alternate extensions.

To add alternate extensions

Step 1 In the Cisco Unity Administrator, go to any Subscribers > Alternate Extensions page.

Step 2 Click the Add button.

Step 3 In the Alternate Extensions table, enter an extension up to 30 characters in length in the field provided.

Each alternate extension that you add must be unique; Cisco Unity will not accept an extension that is already assigned to another subscriber (either as a primary or alternate extension), or to a public distribution list, call handler, directory handler, or interview handler. If your site has multiple Cisco Unity servers that are grouped together, this restriction applies to extensions used throughout the dialing domain.

When entering characters in the Alternate Extensions table, consider the following:

•Enter digits 0 through 9.

•Enter letters a through z (SIP integrations only).

•Do not use spaces, dashes, or parentheses.

Step 4 Click the Save icon. Alternate extensions are enabled for all rows in the table.

Step 5 Repeat Step 2 through Step 4 as necessary.

Step 6 To modify or delete an alternate extension, do the procedure, To modify or delete alternate extension(s).

Step 7 To enable MWIs for one or more alternate extensions, do the procedure, To enable MWIs.

To modify or delete alternate extension(s)

Step 1 In the Cisco Unity Administrator, go to any Subscribers > Alternate Extensions page.

Step 2 Do any of the following:

•To modify an extension, change the extension in the Alternate Extensions table as appropriate.

•To delete extensions, check the boxes next the alternate extensions that you want to delete, and then click the Delete button.

•To remove all alternate extensions listed in the table, click the Select All button, and then click the Delete button.

Step 3 Click the Save icon.

Step 4 Repeat Step 2 through Step 3 as necessary.

To enable MWIs

Cisco Unity can use the MWI on the phone to alert the subscriber to new voice messages. MWIs are not used to indicate the receipt of new e-mail, fax, or return receipt messages.

Step 1 In the Cisco Unity Administrator, go to the appropriate Subscribers > Subscribers > Messages page.

Step 2 Confirm that the Use MWI for Message Notification check box is checked.

Step 3 Click the Add button located beneath the MWI Extensions table to add a row to the table. By default, one row in the table contains an "X" to indicate the primary extension assigned to a subscriber. If necessary, you can also modify this row.

Step 4 Enter the appropriate extension in the Extension field of the table. When entering characters in the MWI Extensions table, consider the following:

•Enter digits 0 through 9.

•Enter letters a through z (SIP integrations only).

•Do not use spaces, dashes, or parentheses.

•Enter , (comma) to insert a one-second pause.

•Enter # and * to correspond to the # and * keys on the phone.

•If the extension that you enter is intended to light an MWI on a phone that requires a different lamp code than the phone associated with the primary extension, verify that your phone system is programmed to support multiple lamp codes.

•MWIs are enabled for all rows in the table.

Step 5 Click the Save icon.

Step 6 Repeat Step 3 through Step 5 as necessary.

To modify or disable MWIs

Step 1 In the Cisco Unity Administrator, go to the appropriate Subscribers > Subscribers > Messages page.

Step 2 Do either of the following:

•To modify an extension, change the extension in the MWI Extensions table as appropriate.

•To delete extensions, check the boxes next the rows that you want to delete in the MWI Extensions table, and then click the Delete button.

Step 3 Click the Save icon.

Step 4 Repeat Step 2 through Step 3 as necessary.

Setting Up Automated Attendant Transfers to Networked Cisco Unity Servers

By default, outside callers who reach the opening greeting for your organization can be transferred only to subscribers associated with the local Cisco Unity server. If you want to set up the automated attendant so that callers can be transferred to subscribers associated with other Cisco Unity servers in the same dialing domain, change a registry setting as described in the following procedure.

Note A typical backup of the Cisco Unity server does not back up the registry. Also note that 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 set the auto attendant search scope

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 Auto Attendant Search Scope.

Step 4 In the New Value list, click 1, and then click Set so that Cisco Unity searches for subscribers within the dialing domain.

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

Step 6 Click Exit.

Note that to allow callers who use directory assistance to be able to locate and transfer to callers associated with other Cisco Unity servers in a dialing domain, you use a search options setting on the Directory Handler page in the Cisco Unity Administrator. For more information, refer to the "Directory Handler Search Options Settings" section in the "Directory Handler Settings" chapter of the Cisco Unity System Administration Guide. (The Cisco Unity System Administration Guide is available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_administration_guide_books_list.html.)

Digital Networking Concepts and Definitions

The following sections explain Digital Networking concepts in detail:

•Locations and Digital Networking

•Dialing Domains

•Networked Phone Systems and Dialing Domains

•Addressing Options for Non-Networked Phone Systems

•Cisco Unity Administrator Scope

•Hiding Voice-Mail-Only Subscribers

Locations and Digital Networking

Central to how Digital Networking works is a Cisco Unity object called a location. Each Cisco Unity server is associated with one location—referred to as the default or primary location—which is created during installation and which cannot be deleted. 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.

Each primary location contains the addressing information that Cisco Unity needs to route messages between Cisco Unity servers. Because Cisco Unity stores location and subscriber addressing information in the directory, the addressing information replicates to other Cisco Unity servers on the network.

The primary location also contains a Dial ID, which Cisco Unity uses as an identifier for the location. Carefully plan the numbers that you choose as Dial IDs for the primary location (and for any delivery locations that you create). Without careful planning, it is possible to inadvertently assign Dial IDs that cause problems in locating message recipients at another location. See the "Assigning Dial IDs" section on page 7-1 and the "How Cisco Unity Searches for a Matching Number" section on page 7-6 for more information.

Dialing Domains

A dialing domain—a collection of Cisco Unity servers that are integrated with the same phone system or phone system network—is a grouping scheme that allows Cisco Unity to handle overlapping dial plans. Within the dialing domain, subscriber extensions must be unique. With a networked phone system, subscribers 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. In the same way, when grouped in a dialing domain, subscribers associated with one Cisco Unity server can dial an extension to address messages to subscribers associated with another Cisco Unity server.

Dialing domains can encompass multiple Exchange 5.5 sites or Exchange 2000 routing groups.

If you group the Cisco Unity servers that are integrated with a networked phone system into a dialing domain, you can set up automated attendant transfers so that outside callers can be transferred to subscribers associated with other Cisco Unity servers in the same dialing domain.

A dialing domain provides a means to set the scope for searches that Cisco Unity performs in the following cases:

•When a subscriber addresses a message

•When members are being added to a public or private distribution list

•When callers reach the opening greeting for your company

•When callers use directory assistance

For example, when a subscriber addresses a message by entering a number, Cisco Unity first searches the local Cisco Unity server for a matching extension. If a match is not found, Cisco Unity searches in the dialing domain for a matching extension. When Cisco Unity finds a matching extension (or extensions) at each scope level, the search is stopped and voice name confirmation is provided to the subscriber sending the message. Because Cisco Unity searches by expanding the search scope in stages—starting with the local server, then the dialing domain, and then the global directory—and because Cisco Unity does not continue the search to the next scope level when it finds a matching extension (or extensions), conflicts with extensions outside of the dialing domain are avoided. For more information, see the "How Cisco Unity Searches for a Matching Number" section on page 7-6.

Dialing Domains Shield Against Overlapping Dial Plans

Grouping the Cisco Unity servers that are integrated with a networked phone system into a dialing domain allows Cisco Unity to handle overlapping dial plans when there are other Cisco Unity servers in the same global directory that are integrated with another phone system. The scenario of separate phone systems with a shared directory is illustrated in Figure 2-1. In this scenario, it is possible that subscribers associated with the Cisco Unity server outside of the dialing domain could have extensions that are the same as extensions used by subscribers associated with the servers within the dialing domain. The dialing domain allows the subscribers within the dialing domain to use extensions to address messages without conflicting with the extensions of another phone system.

Figure 2-1

Dialing Domain

Assume that subscriber extensions on Unity 3 in Figure 2-1 overlap with extensions in dialing domain A. To allow subscribers associated with Unity 3 to use the phone to address messages to subscribers in the dialing domain, and vice-versa, you have the following choices:

•Instruct subscribers to enter a number that consists of the primary location Dial ID of the destination Cisco Unity server and the extension of the recipient.

•Set up alternate extensions for each subscriber account. With alternate extensions, subscribers can address messages by using the same number that they use when calling. See the "Addressing Options for Non-Networked Phone Systems" section for more information.

•Enable the Include Locations in Searches setting. When this setting is enabled, subscribers address a message in two steps: they first enter the location Dial ID (or spell the name of the location) and then enter the extension (or spell the recipient name). See Table 7-1 on page 7-3 for more information.

Networked Phone Systems and Dialing Domains

With a networked phone system, subscribers dial an extension rather than a full phone number when calling someone who is at another location on the phone network. To allow Cisco Unity to make use of this feature, the Cisco Unity servers that are integrated with the networked phone system must be added to a dialing domain. (See the "Dialing Domains" section for more information.) Subscriber extensions must be unique within the dialing domain. As Figure 2-2 illustrates, dialing domains provide a way to segment the global directory.

Figure 2-2

Dialing Domains Segment the Global Directory

When dialing domains are used:

•Subscribers can address messages to subscribers associated with other Cisco Unity servers in the dialing domain by dialing the same number that they use when calling those subscribers.

•The automated attendant on a Cisco Unity server can transfer calls to subscribers associated with any Cisco Unity server within the dialing domain.

•Callers can use directory assistance to search for subscribers associated with any of the Cisco Unity servers within the dialing domain, and then be transferred. (However, note that you can restrict the directory assistance search to the local Cisco Unity server, if desired.)

When calls are transferred from the automated attendant or directory assistance to subscribers not associated with the local server, the transfers are automatically handled by the phone system rather than by Cisco Unity, even if these subscribers are set up for supervised transfers. When this occurs, the call screening, call holding, and announce features will not be available on these calls.

Note that identified subscriber messaging, if enabled, does not work across Cisco Unity servers. When identified subscriber messaging is enabled, Cisco Unity automatically identifies a message left during an internal call as originating from the extension from which the call was made. However, when a subscriber calls another subscriber who is associated with a different Cisco Unity server, and the call is forwarded to voice mail, Cisco Unity cannot identify who left the message. Instead, the message is handled as though it came from an unidentified caller. Because of this inconsistency, you may want to disable identified subscriber messaging system-wide. Refer to the "Configuration Settings" section in the "System Settings" chapter of the Cisco Unity System Administration Guide for more information. (The Cisco Unity System Administration Guide is available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_administration_guide_books_list.html.)

Addressing Options for Non-Networked Phone Systems

If your organization has a separate phone system for each location, subscribers at one location dial a complete phone number, not just an extension, when calling someone at another location. How subscribers address messages to subscribers on another Cisco Unity server depends on whether the dial plans overlap across locations.

When Dial Plans Do Not Overlap

When dial plans do not overlap across locations—when extensions are unique across locations—subscribers enter an extension when addressing a message to a subscriber associated with another Cisco Unity server.

As a convenience for subscribers, you may choose to add alternate extensions to each subscriber account. With alternate extensions, the number that a subscriber enters when addressing a message to someone at another location can be the same number that the subscriber dials when calling. When set up this way, subscribers do not need to remember two different numbers—one for calling a subscriber directly, and one for addressing a message.

For example, a subscriber, Kelly Bader, has extension 4060, as illustrated in Figure 2-3. Suppose that Chris, a subscriber at a remote location, dials 456-4060 to reach Kelly by phone. You could assign Kelly the alternate extension 4564060 so that Chris enters the same number when addressing a message as when calling.

Figure 2-3

No Overlapping Extensions

If the dial plans for each location do not overlap, setting up alternate extensions is optional because they are simply a convenience for subscribers. However, if you do not set up alternate extensions, be sure to tell subscribers to use the extension instead of the full phone number when addressing messages to subscribers associated with another location.

Note that alternate extensions have other purposes beyond their use in Digital Networking, such as handling multiple line appearances on subscriber phones. Subscribers can have up to nine alternate extensions. For more information, refer to the "Subscriber Alternate Extension Settings" section in the "Subscriber Settings" chapter of the Cisco Unity System Administration Guide. (The Cisco Unity System Administration Guide is available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_administration_guide_books_list.html.)

When Dial Plans Overlap

When dial plans overlap across locations, you have the following options:

•Instruct subscribers to enter a number that consists of the primary location Dial ID of the destination Cisco Unity server and the extension of the recipient.

•Set up alternate extensions for each subscriber account. With alternate extensions, subscribers address messages by using the same number that they use when calling.

•Enable the setting Include Locations in Searches. When this setting is enabled, subscribers address a message in two steps: they first dial the location Dial ID and then dial the extension when prompted. See Table 7-1 on page 7-3 for more information.

When a subscriber addresses a message, Cisco Unity searches for a matching extension on the local Cisco Unity server first. If a match is found, Cisco Unity ends the search and never looks for a matching extension at another location. Therefore, if a local subscriber and a subscriber on another Cisco Unity server have the same extension, Cisco Unity will find only the subscriber on the local Cisco Unity server. With one of the above options, subscribers on the local server can address messages to subscribers on other Cisco Unity servers.

Cisco Unity Administrator Scope

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 of your server. Because of this association, in order to access the subscriber accounts and other objects created on another server, you run the Cisco Unity Administrator of the server that the object was created on. Note that though you can view information about the primary locations of other servers and the delivery locations created on other servers, you cannot modify or delete them.

To make accessing the Cisco Unity Administrator on other servers easier, the Cisco Unity Administrator on the local server provides links to the Cisco Unity Administrator pages of other servers. Additionally, within the local Cisco Unity Administrator, you can search for subscribers on other Cisco Unity servers, and when you select a subscriber account to edit settings, the appropriate Cisco Unity Administrator is launched.

You can also use the Global Subscriber Manager (GSM) from the Tools Depot. The GSM shows your entire Cisco Unity network broken down by dialing domains and servers. The GSM allows you to quickly locate individual subscribers and launch the Cisco Unity Administrator pages for the subscribers regardless of which server they are homed on. You can select any scope you want and see all of the subscribers at that level. Searching can be done by dialing domain, by server, or globally across the entire Cisco Unity network.

To use the GSM

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

Step 2 In the left pane, double-click Global Subscriber Manager.

Double-click the subscriber account that you want to edit to display the appropriate Cisco Unity Administrator. Refer to the GSM Help file for more information.

To access subscriber accounts created on a Cisco Unity server other than your local Cisco Unity server

Step 1 In the Cisco Unity Administrator, 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.

Note When you perform wildcard (*) searches, Cisco Unity may take several minutes to display results in the Cisco Unity Administrator. This is particularly true if your site has a large number of subscribers (approximately 1000 users or more) and/or dozens of servers. For this reason, it is important that you narrow the scope of wildcard searches.

Step 5 Check the Search All Cisco Unity Servers check box.

Step 6 Click Find.

Step 7 On the list of matches, click the name of the subscriber to display the record.

Step 8 If prompted, enter the appropriate credentials to gain access to the Cisco Unity Administrator that you want to access.

Another instance of the Cisco Unity Administrator appears in a separate browser window. This is the Cisco Unity Administrator website of the Cisco Unity server on which the subscriber account was created. The subscriber profile page is displayed in the new browser window.

To access the data of objects created on other Cisco Unity servers

To access the data of any object that was created on another Cisco Unity server, you need to know the name of the server on which the object was created.

Step 1 In the Cisco Unity Administrator, go to the Unity Servers page.

Step 2 On the Server Chooser page, click the server that you want to access from the list.

Another instance of the Cisco Unity Administrator appears in a separate browser window. This is the Cisco Unity Administrator website of the Cisco Unity server that you selected.

Note You can also view the contents of delivery locations created on other Cisco Unity servers.

Mapping Subscribers to Cisco Unity Servers

Each Cisco Unity server handles a distinct group of subscribers. In large organizations, it is possible that more than one Cisco Unity server will be in use at the same physical location. In this case, you need to determine which subscribers to associate with each of the Cisco Unity servers, and to keep a record of the mapping. This record is needed for the following reasons:

•When a call forwards from an extension to Cisco Unity, the Attempt Forward to Greeting routing rule searches for the forwarding number only among subscriber extensions (and alternate extensions) on the local Cisco Unity server. For this reason, each subscriber phone must forward to the Cisco Unity server with which the subscriber is associated.

•To check their messages, subscribers must dial the Cisco Unity server that they are associated with. You need to tell subscribers the correct number to dial when calling into Cisco Unity. Additionally, if you use easy message access, each subscriber phone must be set to call the Cisco Unity server with which the subscriber is associated.

To create a record of the mapping, run the Subscribers report on each Cisco Unity server. The information in this report includes the subscriber name and primary location. Refer to the "Subscribers Report" section in the "Reports" chapter of the Cisco Unity System Administration Guide for more information. (The Cisco Unity System Administration Guide is available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_administration_guide_books_list.html.)

Granting Administrative Rights to Other Cisco Unity Servers

To access the Cisco Unity Administrator on another server, the administrators on the local Cisco Unity server need the appropriate class of service (COS) rights. The easiest way to set this up is to run the GrantUnityAccess utility. Refer to the "Cisco Unity Administrator" chapter in the Cisco Unity System Administration Guide for instructions. The Cisco Unity System Administration Guide is available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_administration_guide_books_list.html.

Distribution Lists

Public distribution lists are not associated with a specific primary location. If a list has a recorded voice name, an extension, or both, subscribers can address messages to it—if allowed by their class of service—regardless of which location created the list.

New Lists

When you create a new public distribution list, keep in mind the following:

•The extension for the list must be unique among locations in the entire directory. Therefore, you need to know which extensions are in use at other locations before assigning an extension to the new list.

•In the Cisco Unity Administrator, you can add members from multiple locations, if allowed by the Addressing Options settings for the default location on your Cisco Unity server. See the "Primary Location Addressing Option Settings" section on page 7-5 for more information.

•In the Cisco Unity Administrator, you can view all members of a list regardless of the location with which the member is associated.

Predefined Public Distribution Lists

Cisco Unity includes the following predefined public distribution lists: All Subscribers, Unaddressed Messages, and System Event Messages. Each Cisco Unity server in your organization has a distinct version of each of these lists. When you view these lists in the Cisco Unity Administrator, the Cisco Unity server name is appended to the list name.

Private Lists

When creating private lists, subscribers can add members from other locations if allowed by the Addressing Options settings for your default location. The location addressing options allow you to control the search that Cisco Unity performs when a subscriber adds members to a private list and when a subscriber addresses a message.

Hiding Voice-Mail-Only Subscribers

In some voice-mail only installations, the subscribers already have Exchange mailboxes intended for e-mail. If your Exchange configuration is such that both the voice mail subscriber mailboxes and the e-mail subscriber mailboxes are in the same global address list, having both listings viewable in Outlook may be confusing for subscribers.

To prevent voice mail subscribers from being listed in the Exchange global address list, you will need to hide them by using the Microsoft Exchange 5.5 Administrator or Windows Active Directory for Users and Computers. (To access either tool, click View > Advanced Features, and then make changes on the Exchange Advanced property page.)

Note Even when recipients are hidden, Cisco Unity is able to deliver messages to them.

Notable Behavior

This section provides information about notable expected behavior associated with Digital Networking.

Call Transfer Settings Unavailable

When calls are transferred from the automated attendant or directory assistance to subscribers not associated with the local server, the transfers are automatically handled by the phone system (release to switch)—rather than by Cisco Unity (supervised transfer)—even if these subscribers are set up for supervised transfers. In this case, the call screening, call holding, and announce features will not be available on these calls. Because of this limitation, you may want to limit directory handler searches to the local server by adjusting the setting on the directory handler search options page.

Subscriber ID Unavailable

Identified subscriber messaging does not work between Cisco Unity servers. When a subscriber places a phone call to another subscriber who is associated with a different Cisco Unity server, and if the call is forwarded to voice mail, Cisco Unity cannot identify who left the message. Instead, the message is handled as though it came from an unidentified caller, which means that the recipient cannot press the reply key and record a reply to the sender. You may want to disable identified subscriber messaging system-wide. Refer to the "Configuration Settings" section in the "System Settings" chapter of the Cisco Unity System Administration Guide for more information. (The Cisco Unity System Administration Guide is available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_administration_guide_books_list.html.)

This behavior is caused by MAPI limitations, and there is no workaround.

	Networking in Cisco Unity Guide (With Microsoft Exchange), Release 4.0(1)
	Digital Networking
Networking in Cisco Unity Guide (With Microsoft Exchange), Release 4.0(1) Index Preface Networking in Cisco Unity Digital Networking SMTP Networking AMIS Networking Bridge Networking VPIM Networking Primary Location Settings Upgrade and Uninstall Information	Download this chapter Digital Networking Download the complete book PDF Version of the Entire Book (PDF - 2 MB) Feedback Table Of Contents Digital Networking Overview: Digital Networking Requirements for Setting Up Digital Networking In this Chapter Task List: Setting Up Digital Networking Procedures for Setting Up Cisco Unity To Use Digital Networking Enabling Messaging Among Cisco Unity Servers in Different Exchange 5.5 Sites Customizing the Primary Location Setting Search Options Adding Alternate Extensions Setting Up Automated Attendant Transfers to Networked Cisco Unity Servers Digital Networking Concepts and Definitions Locations and Digital Networking Dialing Domains Dialing Domains Shield Against Overlapping Dial Plans Networked Phone Systems and Dialing Domains Addressing Options for Non-Networked Phone Systems When Dial Plans Do Not Overlap When Dial Plans Overlap Cisco Unity Administrator Scope Mapping Subscribers to Cisco Unity Servers Granting Administrative Rights to Other Cisco Unity Servers Distribution Lists Hiding Voice-Mail-Only Subscribers Notable Behavior Call Transfer Settings Unavailable Subscriber ID Unavailable Digital Networking Overview: Digital Networking In organizations with multiple Cisco Unity servers connected to a network with a single, global directory, each Cisco Unity installation serves a distinct group of subscribers. Cisco Unity Digital Networking is the feature that allows subscribers associated with one Cisco Unity server to exchange voice messages with subscribers associated with other Cisco Unity servers. Digital Networking also provides the means to transfer calls from the automated attendant or directory assistance to subscribers who are not associated with the local server. (Note there are limitations to this functionality. See the "Notable Behavior" section for more information.) If your organization also has the FaxMail and Text-to-Speech E-mail features, subscribers can use the phone to forward fax and e-mail messages to any subscriber in the organization. Although Cisco Unity stores information about subscribers (and other Cisco Unity objects such as call handlers) in a SQL database on the Cisco Unity server, a small subset of information about subscribers, distribution lists, and locations is also stored in the directory to enable Digital Networking. When subscriber and location data from other Cisco Unity servers replicates in the directory, Cisco Unity detects the data and updates the SQL database. Because of directory replication, each Cisco Unity server has the information that it needs to address voice messages to subscribers associated with the other Cisco Unity servers. The directory in which Cisco Unity stores data is determined when Cisco Unity is set up. During setup, you specify one Exchange server (the partner Exchange server) through which Cisco Unity communicates with other Exchange servers in the network. If the partner server is Exchange 2000, Cisco Unity uses Active Directory. If the partner server is Exchange 5.5, Cisco Unity uses the Exchange 5.5 directory. Digital Networking is enabled on every Cisco Unity server. There are no additional licenses that you need to obtain to set up Digital Networking. However, you may want to add a licensed feature called license pooling. License pooling allows Cisco Unity servers that are set up for Digital Networking to pool licenses for subscribers and the Cisco Unity Inbox. (Note that in version 3.1 and earlier, the Cisco Unity Inbox was known as the Visual Messaging Interface or VMI.) With license pooling, if total utilization across all the Cisco Unity servers does not exceed total licenses for the feature, the Cisco Unity server is in compliance with licensing restrictions. For example, suppose two Cisco Unity servers each have 500 licenses for subscribers. With license pooling, one of the servers can use 501 or more licenses as long as the total used by both servers does not exceed 1000. For each Cisco Unity server, you can choose whether it will participate in the pool. To place a Cisco Unity server in the pool, install a license file containing the license pooling feature on the server. If the license pooling feature is not installed on a Cisco Unity server, the server does not participate in the pool, and compliance for all features is measured on a per-machine basis. For all other licensed features, licensing is on a per-machine basis. Licensing information is stored with the primary location for each Cisco Unity server. Because location data is stored in the directory, each Cisco Unity server has the information that it needs to keep track of license usage in the pool. For more information about adding licensed features, refer to the "Obtaining License Files" section in the "Upgrading or Modifying a Cisco Unity 4.0 System" chapter of the Cisco Unity Installation Guide. (The Cisco Unity Installation Guide is available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_guides_books_list.html. Requirements for Setting Up Digital Networking The key to Digital Networking is that all the Cisco Unity servers access a common directory. To use Digital Networking, the Cisco Unity servers must be in one of the following configurations: •The same Active Directory forest. •The same Exchange 5.5 site. •Different sites within the same Exchange 5.5 organization, but with Exchange message and directory replication connectors installed. (Without the message and directory replication connectors, Digital Networking does not work.) Additionally: •The Cisco Unity servers that are networked together can be any combination of Cisco Unity version 3.1(2) or later. If you have an existing Cisco Unity server version 2.4(6) through 3.1(1), and you want to add another Cisco Unity server for Digital Networking, the existing server must be upgraded. •To use Digital Networking in a mixed Exchange environment, all the Cisco Unity servers must use Exchange 2000 for a partner server. Digital Networking between a Cisco Unity server with a partner Exchange 5.5 server and a Cisco Unity server with a partner Exchange 2000 server is not supported, because the required Cisco Unity-specific attributes do not replicate correctly through the Microsoft Active Directory Connector (ADC). In this Chapter In this chapter, you will find procedures for setting up Digital Networking, followed by detailed discussions of the concepts and terminology you need to understand. See the following sections: •Task List: Setting Up Digital Networking—This task list provides a high-level overview of all of the tasks you need to complete, and the order in which they should be completed. •Procedures for Setting Up Cisco Unity To Use Digital Networking—This section contains all of the procedures necessary to set up Cisco Unity for Digital Networking. •Digital Networking Concepts and Definitions—This section explains Digital Networking concepts in detail. Be sure to read this section prior to completing the setup procedures. •Notable Behavior—This section contains information about notable behavior related to Digital Networking. Related Documentation •"Accessing Voice Mail in Multiple Unity Server Environments"—available on Cisco.com at http://www.cisco.com/warp/public/788/AVVID/one_message_button_two_unity_servers.html. •"White Paper: Cisco Unity Data and the Directory"— available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_technical_reference_list.html. Task List: Setting Up Digital Networking Use this task list to set up Digital Networking on each Cisco Unity server. The list assumes that Cisco Unity is already installed on the servers and that they are connected to the network. The cross-references take you to detailed procedures for the setup. 1. If the partner Exchange servers are in different sites within the same Exchange 5.5 organization, you need to change registry keys on each Cisco Unity server. You should also verify that site connectors are installed and functioning properly. See the "Enabling Messaging Among Cisco Unity Servers in Different Exchange 5.5 Sites" section. 2. Customize the primary location. See the "Customizing the Primary Location" section. 3. Set the search options. See the "Setting Search Options" section. 4. Optionally, add alternate extensions to each subscriber account. See the "Adding Alternate Extensions" section. 5. Optionally, if the Cisco Unity servers are integrated with a networked phone system, set up automated attendant transfers to subscribers associated with other Cisco Unity servers in the same dialing domain. See the "Setting Up Automated Attendant Transfers to Networked Cisco Unity Servers" section. Skip this task if each Cisco Unity server is integrated with a separate phone system. 6. Test the Digital Networking setup. Note Each Cisco Unity server stores the primary location data and a subset of the data about subscriber accounts and distribution lists in the directory. The time that it takes for data from other Cisco Unity servers to be reflected on the local server depends on your Active Directory or Exchange 5.5 network configuration and replication schedule. You need to wait for the Cisco Unity data to replicate to the other servers before testing the Digital Networking setup. Procedures for Setting Up Cisco Unity To Use Digital Networking This section contains all of the procedures necessary to set up Cisco Unity for Digital Networking. Enabling Messaging Among Cisco Unity Servers in Different Exchange 5.5 Sites If the partner Exchange servers are in different sites within the same Exchange 5.5 organization, Exchange message and directory replication connectors (also called site connectors) must be installed. If the site connectors are not already installed, install them now. Verify that the site connectors function properly before proceeding. Refer to your Microsoft Exchange documentation for more information. Do the following procedure only if the partner Exchange servers are in separate sites in an Exchange 5.5 organization. Skip this procedure if the partner Exchange servers are in the same Exchange 5.5 site, or if the partner Exchange server is running Exchange 2000. To allow messaging among Cisco Unity servers in the entire Exchange 5.5 organization Step 1 Stop the AvDSEx55 service. (On the Windows Start menu, click Programs > Administrative Tools > Services. Right-click AvDSEx55, and select Stop.) Step 2 Start Regedit. Caution Changing the wrong registry key or entering an incorrect value can cause the server to malfunction. Before you edit the registry, confirm that you know how to restore it if a problem occurs. (Refer to the "Restoring" topics in Registry Editor Help.) Note that a typical backup of the Cisco Unity server does not back up the registry. Also note that 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. If you have any questions about changing registry key settings, contact Cisco TAC. Step 3 If you do not have a current backup of the registry, click Registry > Export Registry File, and save the registry settings to a file. Step 4 Expand the following key: HKEY_LOCAL_MACHINE\Software\ActiveVoice\Directory Connectors\DirSynchEx55\1.00\Locations Step 5 Double-click SearchRoot to display the Edit String dialog box. Step 6 Replace the entire string in the Value Data box with the following: o=OrganizationName Substitute the name of your Exchange organization for OrganizationName. Verify that the value in the box is only o=OrganizationName. Step 7 Click OK. Step 8 Expand the following key: HKEY_LOCAL_MACHINE\Software\ActiveVoice\Directory Connectors\DirSynchEx55\1.00\MailUsers Step 9 Double-click SearchRoot to display the Edit String dialog box. Step 10 Replace the entire string in the Value Data box with the following: o=OrganizationName Substitute the name of your Exchange organization for OrganizationName. Verify that the value in the box is only o=OrganizationName. Step 11 Click OK. Step 12 Expand the following key: HKEY_LOCAL_MACHINE\Software\ActiveVoice\Directory Connectors\DirSynchEx55\1.00\DistributionLists Step 13 Double-click SearchRoot to display the Edit String dialog box. Step 14 Replace the entire string in the Value Data box with the following: o=OrganizationName Substitute the name of your Exchange organization for OrganizationName. Verify that the value in the box is only o=OrganizationName. Step 15 Click OK. Step 16 Expand the following key: HKEY_LOCAL_MACHINE\Software\ActiveVoice\Directory Connectors\DirSynchEx55\1.00 Step 17 Double-click LastUSN to display the Edit DWORD Value dialog box. Step 18 Replace the value in the Value data box with 0. Step 19 Click OK and then close Regedit. Step 20 Start the AvDSEx55 service. (On the Windows Start menu, click Programs > Administrative Tools > Services. Right-click AvDSEx55, and select Start.) Customizing the Primary Location See Table 7-1 on page 7-3 for detailed information about the primary location profile settings. To customize the primary location Step 1 In the Cisco Unity Administrator, go to the Network > Primary Location > Profile page. Step 2 Enter a meaningful name for the location. Step 3 Enter a Dial ID. The Dial ID identifies this location to Cisco Unity. Step 4 Record a voice name for the location. Step 5 Do one of the following: •If the location does not belong to a dialing domain, click None. •If the location does belong to a dialing domain, enter the Dialing Domain name only on one Cisco Unity server that is in the dialing domain, and wait for the name to replicate to the other Cisco Unity servers. Note When setting up the primary location of the other Cisco Unity servers that are members of the dialing domain, select the Dialing Domain name from the list instead of entering a name. 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. Step 6 Click the Save icon. Setting Search Options For detailed information about the search option settings, see the "Primary Location Addressing Option Settings" section on page 7-5, and the "Directory Handler Search Options Settings" section in the "Directory Handler Settings" chapter of the Cisco Unity System Administration Guide. (The Cisco Unity System Administration Guide is available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_administration_guide_books_list.html.) To set search options Step 1 In the Cisco Unity Administrator, go to the Network > Primary Location > Addressing Options page and set the addressing options as needed. •To allow subscribers created on the local Cisco Unity server to address messages to subscribers on other Cisco Unity servers (that access the same directory), select Dialing Domain or Global Directory, as appropriate. •If you are using blind addressing to a Cisco Unity server in a separate directory, or to another voice messaging system, set the Blind Addressing Allowed Locations setting to something other than None, as appropriate. Step 2 If you want locations included in address searches, check Include Locations in Searches. The location name is played only when a subscriber enters the location dial ID when addressing a message. Step 3 Go to the Call Management > Directory Handlers > Search Options page, and modify the search options for an existing directory handler, or create a new directory handler for unidentified callers who use directory assistance. To allow subscribers on other Cisco Unity servers to be located in directory assistance, select Dialing Domain. (The Cisco Unity servers must be in the same dialing domain as the local Cisco Unity server.) Adding Alternate Extensions The procedures in this section are optional for setting up Digital Networking. If all the extensions across locations are unique, you probably do not need to set up alternate extensions. See the "Dialing Domains" section and the "Addressing Options for Non-Networked Phone Systems" section to determine whether you need alternate extensions. To add alternate extensions Step 1 In the Cisco Unity Administrator, go to any Subscribers > Alternate Extensions page. Step 2 Click the Add button. Step 3 In the Alternate Extensions table, enter an extension up to 30 characters in length in the field provided. Each alternate extension that you add must be unique; Cisco Unity will not accept an extension that is already assigned to another subscriber (either as a primary or alternate extension), or to a public distribution list, call handler, directory handler, or interview handler. If your site has multiple Cisco Unity servers that are grouped together, this restriction applies to extensions used throughout the dialing domain. When entering characters in the Alternate Extensions table, consider the following: •Enter digits 0 through 9. •Enter letters a through z (SIP integrations only). •Do not use spaces, dashes, or parentheses. Step 4 Click the Save icon. Alternate extensions are enabled for all rows in the table. Step 5 Repeat Step 2 through Step 4 as necessary. Step 6 To modify or delete an alternate extension, do the procedure, To modify or delete alternate extension(s). Step 7 To enable MWIs for one or more alternate extensions, do the procedure, To enable MWIs. To modify or delete alternate extension(s) Step 1 In the Cisco Unity Administrator, go to any Subscribers > Alternate Extensions page. Step 2 Do any of the following: •To modify an extension, change the extension in the Alternate Extensions table as appropriate. •To delete extensions, check the boxes next the alternate extensions that you want to delete, and then click the Delete button. •To remove all alternate extensions listed in the table, click the Select All button, and then click the Delete button. Step 3 Click the Save icon. Step 4 Repeat Step 2 through Step 3 as necessary. To enable MWIs Cisco Unity can use the MWI on the phone to alert the subscriber to new voice messages. MWIs are not used to indicate the receipt of new e-mail, fax, or return receipt messages. Step 1 In the Cisco Unity Administrator, go to the appropriate Subscribers > Subscribers > Messages page. Step 2 Confirm that the Use MWI for Message Notification check box is checked. Step 3 Click the Add button located beneath the MWI Extensions table to add a row to the table. By default, one row in the table contains an "X" to indicate the primary extension assigned to a subscriber. If necessary, you can also modify this row. Step 4 Enter the appropriate extension in the Extension field of the table. When entering characters in the MWI Extensions table, consider the following: •Enter digits 0 through 9. •Enter letters a through z (SIP integrations only). •Do not use spaces, dashes, or parentheses. •Enter , (comma) to insert a one-second pause. •Enter # and * to correspond to the # and * keys on the phone. •If the extension that you enter is intended to light an MWI on a phone that requires a different lamp code than the phone associated with the primary extension, verify that your phone system is programmed to support multiple lamp codes. •MWIs are enabled for all rows in the table. Step 5 Click the Save icon. Step 6 Repeat Step 3 through Step 5 as necessary. To modify or disable MWIs Step 1 In the Cisco Unity Administrator, go to the appropriate Subscribers > Subscribers > Messages page. Step 2 Do either of the following: •To modify an extension, change the extension in the MWI Extensions table as appropriate. •To delete extensions, check the boxes next the rows that you want to delete in the MWI Extensions table, and then click the Delete button. Step 3 Click the Save icon. Step 4 Repeat Step 2 through Step 3 as necessary. Setting Up Automated Attendant Transfers to Networked Cisco Unity Servers By default, outside callers who reach the opening greeting for your organization can be transferred only to subscribers associated with the local Cisco Unity server. If you want to set up the automated attendant so that callers can be transferred to subscribers associated with other Cisco Unity servers in the same dialing domain, change a registry setting as described in the following procedure. Note A typical backup of the Cisco Unity server does not back up the registry. Also note that 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 set the auto attendant search scope 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 Auto Attendant Search Scope. Step 4 In the New Value list, click 1, and then click Set so that Cisco Unity searches for subscribers within the dialing domain. Step 5 When prompted, click OK. You do not need to restart Cisco Unity to enable the change. Step 6 Click Exit. Note that to allow callers who use directory assistance to be able to locate and transfer to callers associated with other Cisco Unity servers in a dialing domain, you use a search options setting on the Directory Handler page in the Cisco Unity Administrator. For more information, refer to the "Directory Handler Search Options Settings" section in the "Directory Handler Settings" chapter of the Cisco Unity System Administration Guide. (The Cisco Unity System Administration Guide is available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_administration_guide_books_list.html.) Digital Networking Concepts and Definitions The following sections explain Digital Networking concepts in detail: •Locations and Digital Networking •Dialing Domains •Networked Phone Systems and Dialing Domains •Addressing Options for Non-Networked Phone Systems •Cisco Unity Administrator Scope •Hiding Voice-Mail-Only Subscribers Locations and Digital Networking Central to how Digital Networking works is a Cisco Unity object called a location. Each Cisco Unity server is associated with one location—referred to as the default or primary location—which is created during installation and which cannot be deleted. 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. Each primary location contains the addressing information that Cisco Unity needs to route messages between Cisco Unity servers. Because Cisco Unity stores location and subscriber addressing information in the directory, the addressing information replicates to other Cisco Unity servers on the network. The primary location also contains a Dial ID, which Cisco Unity uses as an identifier for the location. Carefully plan the numbers that you choose as Dial IDs for the primary location (and for any delivery locations that you create). Without careful planning, it is possible to inadvertently assign Dial IDs that cause problems in locating message recipients at another location. See the "Assigning Dial IDs" section on page 7-1 and the "How Cisco Unity Searches for a Matching Number" section on page 7-6 for more information. Dialing Domains A dialing domain—a collection of Cisco Unity servers that are integrated with the same phone system or phone system network—is a grouping scheme that allows Cisco Unity to handle overlapping dial plans. Within the dialing domain, subscriber extensions must be unique. With a networked phone system, subscribers 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. In the same way, when grouped in a dialing domain, subscribers associated with one Cisco Unity server can dial an extension to address messages to subscribers associated with another Cisco Unity server. Dialing domains can encompass multiple Exchange 5.5 sites or Exchange 2000 routing groups. If you group the Cisco Unity servers that are integrated with a networked phone system into a dialing domain, you can set up automated attendant transfers so that outside callers can be transferred to subscribers associated with other Cisco Unity servers in the same dialing domain. A dialing domain provides a means to set the scope for searches that Cisco Unity performs in the following cases: •When a subscriber addresses a message •When members are being added to a public or private distribution list •When callers reach the opening greeting for your company •When callers use directory assistance For example, when a subscriber addresses a message by entering a number, Cisco Unity first searches the local Cisco Unity server for a matching extension. If a match is not found, Cisco Unity searches in the dialing domain for a matching extension. When Cisco Unity finds a matching extension (or extensions) at each scope level, the search is stopped and voice name confirmation is provided to the subscriber sending the message. Because Cisco Unity searches by expanding the search scope in stages—starting with the local server, then the dialing domain, and then the global directory—and because Cisco Unity does not continue the search to the next scope level when it finds a matching extension (or extensions), conflicts with extensions outside of the dialing domain are avoided. For more information, see the "How Cisco Unity Searches for a Matching Number" section on page 7-6. Dialing Domains Shield Against Overlapping Dial Plans Grouping the Cisco Unity servers that are integrated with a networked phone system into a dialing domain allows Cisco Unity to handle overlapping dial plans when there are other Cisco Unity servers in the same global directory that are integrated with another phone system. The scenario of separate phone systems with a shared directory is illustrated in Figure 2-1. In this scenario, it is possible that subscribers associated with the Cisco Unity server outside of the dialing domain could have extensions that are the same as extensions used by subscribers associated with the servers within the dialing domain. The dialing domain allows the subscribers within the dialing domain to use extensions to address messages without conflicting with the extensions of another phone system. Figure 2-1 Dialing Domain Assume that subscriber extensions on Unity 3 in Figure 2-1 overlap with extensions in dialing domain A. To allow subscribers associated with Unity 3 to use the phone to address messages to subscribers in the dialing domain, and vice-versa, you have the following choices: •Instruct subscribers to enter a number that consists of the primary location Dial ID of the destination Cisco Unity server and the extension of the recipient. •Set up alternate extensions for each subscriber account. With alternate extensions, subscribers can address messages by using the same number that they use when calling. See the "Addressing Options for Non-Networked Phone Systems" section for more information. •Enable the Include Locations in Searches setting. When this setting is enabled, subscribers address a message in two steps: they first enter the location Dial ID (or spell the name of the location) and then enter the extension (or spell the recipient name). See Table 7-1 on page 7-3 for more information. Networked Phone Systems and Dialing Domains With a networked phone system, subscribers dial an extension rather than a full phone number when calling someone who is at another location on the phone network. To allow Cisco Unity to make use of this feature, the Cisco Unity servers that are integrated with the networked phone system must be added to a dialing domain. (See the "Dialing Domains" section for more information.) Subscriber extensions must be unique within the dialing domain. As Figure 2-2 illustrates, dialing domains provide a way to segment the global directory. Figure 2-2 Dialing Domains Segment the Global Directory When dialing domains are used: •Subscribers can address messages to subscribers associated with other Cisco Unity servers in the dialing domain by dialing the same number that they use when calling those subscribers. •The automated attendant on a Cisco Unity server can transfer calls to subscribers associated with any Cisco Unity server within the dialing domain. •Callers can use directory assistance to search for subscribers associated with any of the Cisco Unity servers within the dialing domain, and then be transferred. (However, note that you can restrict the directory assistance search to the local Cisco Unity server, if desired.) When calls are transferred from the automated attendant or directory assistance to subscribers not associated with the local server, the transfers are automatically handled by the phone system rather than by Cisco Unity, even if these subscribers are set up for supervised transfers. When this occurs, the call screening, call holding, and announce features will not be available on these calls. Note that identified subscriber messaging, if enabled, does not work across Cisco Unity servers. When identified subscriber messaging is enabled, Cisco Unity automatically identifies a message left during an internal call as originating from the extension from which the call was made. However, when a subscriber calls another subscriber who is associated with a different Cisco Unity server, and the call is forwarded to voice mail, Cisco Unity cannot identify who left the message. Instead, the message is handled as though it came from an unidentified caller. Because of this inconsistency, you may want to disable identified subscriber messaging system-wide. Refer to the "Configuration Settings" section in the "System Settings" chapter of the Cisco Unity System Administration Guide for more information. (The Cisco Unity System Administration Guide is available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_administration_guide_books_list.html.) Addressing Options for Non-Networked Phone Systems If your organization has a separate phone system for each location, subscribers at one location dial a complete phone number, not just an extension, when calling someone at another location. How subscribers address messages to subscribers on another Cisco Unity server depends on whether the dial plans overlap across locations. When Dial Plans Do Not Overlap When dial plans do not overlap across locations—when extensions are unique across locations—subscribers enter an extension when addressing a message to a subscriber associated with another Cisco Unity server. As a convenience for subscribers, you may choose to add alternate extensions to each subscriber account. With alternate extensions, the number that a subscriber enters when addressing a message to someone at another location can be the same number that the subscriber dials when calling. When set up this way, subscribers do not need to remember two different numbers—one for calling a subscriber directly, and one for addressing a message. For example, a subscriber, Kelly Bader, has extension 4060, as illustrated in Figure 2-3. Suppose that Chris, a subscriber at a remote location, dials 456-4060 to reach Kelly by phone. You could assign Kelly the alternate extension 4564060 so that Chris enters the same number when addressing a message as when calling. Figure 2-3 No Overlapping Extensions If the dial plans for each location do not overlap, setting up alternate extensions is optional because they are simply a convenience for subscribers. However, if you do not set up alternate extensions, be sure to tell subscribers to use the extension instead of the full phone number when addressing messages to subscribers associated with another location. Note that alternate extensions have other purposes beyond their use in Digital Networking, such as handling multiple line appearances on subscriber phones. Subscribers can have up to nine alternate extensions. For more information, refer to the "Subscriber Alternate Extension Settings" section in the "Subscriber Settings" chapter of the Cisco Unity System Administration Guide. (The Cisco Unity System Administration Guide is available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_administration_guide_books_list.html.) When Dial Plans Overlap When dial plans overlap across locations, you have the following options: •Instruct subscribers to enter a number that consists of the primary location Dial ID of the destination Cisco Unity server and the extension of the recipient. •Set up alternate extensions for each subscriber account. With alternate extensions, subscribers address messages by using the same number that they use when calling. •Enable the setting Include Locations in Searches. When this setting is enabled, subscribers address a message in two steps: they first dial the location Dial ID and then dial the extension when prompted. See Table 7-1 on page 7-3 for more information. When a subscriber addresses a message, Cisco Unity searches for a matching extension on the local Cisco Unity server first. If a match is found, Cisco Unity ends the search and never looks for a matching extension at another location. Therefore, if a local subscriber and a subscriber on another Cisco Unity server have the same extension, Cisco Unity will find only the subscriber on the local Cisco Unity server. With one of the above options, subscribers on the local server can address messages to subscribers on other Cisco Unity servers. Cisco Unity Administrator Scope 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 of your server. Because of this association, in order to access the subscriber accounts and other objects created on another server, you run the Cisco Unity Administrator of the server that the object was created on. Note that though you can view information about the primary locations of other servers and the delivery locations created on other servers, you cannot modify or delete them. To make accessing the Cisco Unity Administrator on other servers easier, the Cisco Unity Administrator on the local server provides links to the Cisco Unity Administrator pages of other servers. Additionally, within the local Cisco Unity Administrator, you can search for subscribers on other Cisco Unity servers, and when you select a subscriber account to edit settings, the appropriate Cisco Unity Administrator is launched. You can also use the Global Subscriber Manager (GSM) from the Tools Depot. The GSM shows your entire Cisco Unity network broken down by dialing domains and servers. The GSM allows you to quickly locate individual subscribers and launch the Cisco Unity Administrator pages for the subscribers regardless of which server they are homed on. You can select any scope you want and see all of the subscribers at that level. Searching can be done by dialing domain, by server, or globally across the entire Cisco Unity network. To use the GSM Step 1 On the Cisco Unity server desktop, double-click the Cisco Unity Tools Depot icon. Step 2 In the left pane, double-click Global Subscriber Manager. Double-click the subscriber account that you want to edit to display the appropriate Cisco Unity Administrator. Refer to the GSM Help file for more information. To access subscriber accounts created on a Cisco Unity server other than your local Cisco Unity server Step 1 In the Cisco Unity Administrator, 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. Note When you perform wildcard () searches, Cisco Unity may take several minutes to display results in the Cisco Unity Administrator. This is particularly true if your site has a large number of subscribers (approximately 1000 users or more) and/or dozens of servers. For this reason, it is important that you narrow the scope of wildcard searches. Step 5* Check the Search All Cisco Unity Servers check box. Step 6 Click Find. Step 7 On the list of matches, click the name of the subscriber to display the record. Step 8 If prompted, enter the appropriate credentials to gain access to the Cisco Unity Administrator that you want to access. Another instance of the Cisco Unity Administrator appears in a separate browser window. This is the Cisco Unity Administrator website of the Cisco Unity server on which the subscriber account was created. The subscriber profile page is displayed in the new browser window. To access the data of objects created on other Cisco Unity servers To access the data of any object that was created on another Cisco Unity server, you need to know the name of the server on which the object was created. Step 1 In the Cisco Unity Administrator, go to the Unity Servers page. Step 2 On the Server Chooser page, click the server that you want to access from the list. Another instance of the Cisco Unity Administrator appears in a separate browser window. This is the Cisco Unity Administrator website of the Cisco Unity server that you selected. Note You can also view the contents of delivery locations created on other Cisco Unity servers. Mapping Subscribers to Cisco Unity Servers Each Cisco Unity server handles a distinct group of subscribers. In large organizations, it is possible that more than one Cisco Unity server will be in use at the same physical location. In this case, you need to determine which subscribers to associate with each of the Cisco Unity servers, and to keep a record of the mapping. This record is needed for the following reasons: •When a call forwards from an extension to Cisco Unity, the Attempt Forward to Greeting routing rule searches for the forwarding number only among subscriber extensions (and alternate extensions) on the local Cisco Unity server. For this reason, each subscriber phone must forward to the Cisco Unity server with which the subscriber is associated. •To check their messages, subscribers must dial the Cisco Unity server that they are associated with. You need to tell subscribers the correct number to dial when calling into Cisco Unity. Additionally, if you use easy message access, each subscriber phone must be set to call the Cisco Unity server with which the subscriber is associated. To create a record of the mapping, run the Subscribers report on each Cisco Unity server. The information in this report includes the subscriber name and primary location. Refer to the "Subscribers Report" section in the "Reports" chapter of the Cisco Unity System Administration Guide for more information. (The Cisco Unity System Administration Guide is available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_administration_guide_books_list.html.) Granting Administrative Rights to Other Cisco Unity Servers To access the Cisco Unity Administrator on another server, the administrators on the local Cisco Unity server need the appropriate class of service (COS) rights. The easiest way to set this up is to run the GrantUnityAccess utility. Refer to the "Cisco Unity Administrator" chapter in the Cisco Unity System Administration Guide for instructions. The Cisco Unity System Administration Guide is available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_administration_guide_books_list.html. Distribution Lists Public distribution lists are not associated with a specific primary location. If a list has a recorded voice name, an extension, or both, subscribers can address messages to it—if allowed by their class of service—regardless of which location created the list. New Lists When you create a new public distribution list, keep in mind the following: •The extension for the list must be unique among locations in the entire directory. Therefore, you need to know which extensions are in use at other locations before assigning an extension to the new list. •In the Cisco Unity Administrator, you can add members from multiple locations, if allowed by the Addressing Options settings for the default location on your Cisco Unity server. See the "Primary Location Addressing Option Settings" section on page 7-5 for more information. •In the Cisco Unity Administrator, you can view all members of a list regardless of the location with which the member is associated. Predefined Public Distribution Lists Cisco Unity includes the following predefined public distribution lists: All Subscribers, Unaddressed Messages, and System Event Messages. Each Cisco Unity server in your organization has a distinct version of each of these lists. When you view these lists in the Cisco Unity Administrator, the Cisco Unity server name is appended to the list name. Private Lists When creating private lists, subscribers can add members from other locations if allowed by the Addressing Options settings for your default location. The location addressing options allow you to control the search that Cisco Unity performs when a subscriber adds members to a private list and when a subscriber addresses a message. Hiding Voice-Mail-Only Subscribers In some voice-mail only installations, the subscribers already have Exchange mailboxes intended for e-mail. If your Exchange configuration is such that both the voice mail subscriber mailboxes and the e-mail subscriber mailboxes are in the same global address list, having both listings viewable in Outlook may be confusing for subscribers. To prevent voice mail subscribers from being listed in the Exchange global address list, you will need to hide them by using the Microsoft Exchange 5.5 Administrator or Windows Active Directory for Users and Computers. (To access either tool, click View > Advanced Features, and then make changes on the Exchange Advanced property page.) Note Even when recipients are hidden, Cisco Unity is able to deliver messages to them. Notable Behavior This section provides information about notable expected behavior associated with Digital Networking. Call Transfer Settings Unavailable When calls are transferred from the automated attendant or directory assistance to subscribers not associated with the local server, the transfers are automatically handled by the phone system (release to switch)—rather than by Cisco Unity (supervised transfer)—even if these subscribers are set up for supervised transfers. In this case, the call screening, call holding, and announce features will not be available on these calls. Because of this limitation, you may want to limit directory handler searches to the local server by adjusting the setting on the directory handler search options page. Subscriber ID Unavailable Identified subscriber messaging does not work between Cisco Unity servers. When a subscriber places a phone call to another subscriber who is associated with a different Cisco Unity server, and if the call is forwarded to voice mail, Cisco Unity cannot identify who left the message. Instead, the message is handled as though it came from an unidentified caller, which means that the recipient cannot press the reply key and record a reply to the sender. You may want to disable identified subscriber messaging system-wide. Refer to the "Configuration Settings" section in the "System Settings" chapter of the Cisco Unity System Administration Guide for more information. (The Cisco Unity System Administration Guide is available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_administration_guide_books_list.html.) This behavior is caused by MAPI limitations, and there is no workaround.
	Terms & Conditions \| Privacy Statement \| Cookie Policy \| Trademarks