Feedback
Table Of Contents
Requirements for Setting Up Digital Networking
Identified Subscriber Messaging
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 the Addressing, Directory Handler, and Automated Attendant Search Scopes
Setting the Addressing Search Scope
Setting the Directory Handler Search Scope
Setting the Automated Attendant Search Scope
Enabling Identified Subscriber Messaging
Testing the Digital Networking Setup
Testing Identified Subscriber Messaging (Cisco Unity 3.1(6) and Later)
Digital Networking Concepts and Definitions
Locations and Digital Networking
Dialing Domains Shield Against Overlapping Numbering Plans
Networked Phone Systems and Dialing Domains
Addressing Options for Non-Networked Phone Systems
When Numbering Plans Do Not Overlap
Cisco Unity Administrator Scope
Browsing to Another Cisco Unity Administrator from the Local Cisco Unity Administrator
Searching for Subscriber Accounts Created on Another Cisco Unity Server
Using Global Subscriber Manager to Browse to Another Cisco Unity Administrator
Cisco Unity Administrator Accounts
About the Accounts That Can Be Used to Administer Cisco Unity
Creating Subscriber Accounts That Can Be Used to Access the Cisco Unity Administrator
Granting Administrative Rights to Other Cisco Unity Servers
Hiding Voice-Messaging-Only Subscribers
Limitations and Notable Behavior
Call Transfer Settings Unavailable
Digital Networking in an Exchange Mixed-Mode Environment
Limitations Subscribers Can Encounter
Leaving a Message Versus Sending a Message: Limitations with Identified Subscriber Messaging
Mapping Subscribers to Cisco Unity Servers
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. With Digital Networking, subscribers can use the phone to log on to Cisco Unity and send messages to 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 "Limitations and 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.
Requirements for Setting Up Digital Networking
The key to Digital Networking is that all of 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.
•
•
Additionally:
•
•
Note that Cisco Unity servers licensed for Unified Messaging (UM) and Cisco Unity servers licensed for Voice Messaging (VM) can use Digital Networking to exchange messages, as long as the above requirements are met. There are no licensing issues associated with VM and UM existing in the same Exchange organization or Active Directory forest, as long as the VM subscribers access voice and fax messages only over the phone interface or with the separately licensed Cisco Unity Visual Messaging Interface.
Licenses
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, note that Digital Networking is a separate add-on for the Cisco Integrated Communications System (ICS) 7750 platform. For more information about the ICS 7750 platform, refer to http://www.cisco.com/en/US/products/hw/voiceapp/ps967/ps968/index.html.)
Identified Subscriber Messaging
When a subscriber calls another subscriber who is associated with a different Cisco Unity server, and when the call is forwarded to voice mail (because the recipient phone is busy or is not answered), Cisco Unity may not be able to identify who left the message. The ability of Cisco Unity to identify that a subscriber left the message is referred to as identified subscriber messaging. Identified subscriber messaging is fully functional across Cisco Unity servers in version 3.1(6). For identified subscriber messaging to work, all the Cisco Unity servers must be running 3.1(6). Note that identified subscriber messaging between Cisco Unity servers is by default not enabled. See the "Enabling Identified Subscriber Messaging" section.
For more information about the limitations that subscribers encounter when identified subscriber messaging is limited to a single server, see the "Leaving a Message Versus Sending a Message: Limitations with Identified Subscriber Messaging" section.
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:
•
•
•
•
Related Documentation
•
•
•
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.
1.
2.
3.
4.
5.
6.
Note
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 according to the instructions in your Microsoft documentation. Verify that the site connectors function properly before proceeding.
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
Step 2
Caution
Step 3
Step 4
HKEY_LOCAL_MACHINE\Software\ActiveVoice\Directory Connectors\DirSynchEx55\1.00\Locations
Step 5
Step 6
o=OrganizationName
Substitute the name of your Exchange organization for OrganizationName.
Step 7
Step 8
HKEY_LOCAL_MACHINE\Software\ActiveVoice\Directory Connectors\DirSynchEx55\1.00\MailUsers
Step 9
Step 10
o=OrganizationName
Substitute the name of your Exchange organization for OrganizationName. Verify that o=OrganizationName is the only value in the box.
Step 11
Step 12
HKEY_LOCAL_MACHINE\Software\ActiveVoice\Directory Connectors\DirSynchEx55\1.00\DistributionLists
Step 13
Step 14
o=OrganizationName
Substitute the name of your Exchange organization for OrganizationName. Verify that o=OrganizationName is the only value in the box.
Step 15
Step 16
HKEY_LOCAL_MACHINE\Software\ActiveVoice\Directory Connectors\DirSynchEx55\1.00
Step 17
Step 18
Step 19
Step 20
Customizing the Primary Location
See Table 6-1 on page 6-3 for detailed information about the primary location profile settings.
To Customize the Primary Location
Step 1
Step 2
Step 3
Step 4
Step 5
•
•
Note
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
Setting the Addressing, Directory Handler, and Automated Attendant Search Scopes
Do the following procedures to set up the addressing, directory handler, and automated attendant search scopes:
•
•
•
In Cisco Unity 3.1(6), the automated attendant search scope must be set to search the dialing domain in order for identified subscriber messaging between Cisco Unity servers to work.
Setting the Addressing Search Scope
For detailed information about the addressing search options, see the "Primary Location Addressing Option Settings" section on page 6-6.
To Set the Addressing Search Scope
Step 1
•
•
Step 2
Step 3
Setting the Directory Handler Search Scope
For detailed 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.)
To Set the Directory Handler Search Scope
Step 1
Step 2
Step 3
Setting the Automated Attendant Search Scope
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.
In Cisco Unity 3.1(6), the automated attendant search scope must be set to search the dialing domain in order for identified subscriber messaging between Cisco Unity servers to work.
Note
To Set the Automated Attendant Search Scope
Step 1
Step 2
Step 3
Step 4
Step 5
You do not need to restart Cisco Unity to enable the change.
Step 6
Enabling Identified Subscriber Messaging
In Cisco Unity 3.1(6), two different settings control whether identified subscriber messaging is enabled:
•
•
To Enable Identified Subscriber Messaging in the Cisco Unity Administrator
Step 1
Step 2
Step 3
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 to add alternate extensions.
To Add Alternate Extensions
Step 1
Step 2
Step 3
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:
•
•
•
Step 4
Step 5
Step 6
Step 7
To Modify or Delete Alternate Extension(s)
Step 1
Step 2
•
•
•
Step 3
Step 4
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
Step 2
Step 3
Step 4
•
•
•
•
•
•
•
Step 5
Step 6
To Modify or Disable MWIs
Step 1
Step 2
•
•
Step 3
Step 4
Testing the Digital Networking Setup
To test the Digital Networking setup, create test subscriber accounts or use existing subscriber accounts on each Cisco Unity server. When setting up subscriber accounts in the Cisco Unity Administrator to be used in the tests, be sure to:
•
•
•
•
Do the following tests to make sure Digital Networking is functioning properly:
1.
–
–
–
2.
3.
Testing Identified Subscriber Messaging (Cisco Unity 3.1(6) and Later)
In Cisco Unity 3.1(6), test that identified subscriber messaging is functioning properly. Verify that the following have been set correctly:
•
•
Do the following tests to make sure identified subscribing messaging is functioning properly:
1.
2.
–
–
Digital Networking Concepts and Definitions
The following sections explain Digital Networking concepts in detail:
•
•
•
•
•
•
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 will cause problems in locating message recipients at another location. See the "Assigning Dial IDs" section on page 6-1 and the "How Cisco Unity Searches for a Matching Number" section on page 6-7 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 numbering plans. Within the dialing domain, subscriber extensions in Cisco Unity must be unique just as the phone extensions in the phone system must be unique. (Typically, a subscriber extension and phone extension are the same number.) With a networked phone system, subscribers dial a phone 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 enter a subscriber extension when sending 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 the directory handler and automated attendant search scopes 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:
•
•
•
•
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 at any 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 has found a matching extension, conflicts with extensions outside of the dialing domain are avoided.
Although subscriber extensions are supposed to be unique within a dialing domain, it is possible that you could inadvertently create a subscriber account with a non-unique extension, due to directory replication lag time. If Cisco Unity finds more than one matching extension (at any scope level), it returns a list to the subscriber sending the message. ("There are two matching names. For Terry Campbell at extension 3047, press 1. For Kelly Bader at extension 3047, press 2.") For more information, see the "How Cisco Unity Searches for a Matching Number" section on page 6-7.
Dialing Domains Shield Against Overlapping Numbering Plans
Grouping the Cisco Unity servers that are integrated with a networked phone system into a dialing domain allows Cisco Unity to handle overlapping numbering 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 the subscribers on the other 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:
•
•
•
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:
•
•
•
Note the limitations described in the "Limitations and Notable Behavior" section.
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. When subscribers log on to Cisco Unity to send messages to subscribers on another Cisco Unity server, the number they enter when addressing the message depends on whether the Cisco Unity numbering plans overlap across locations, as described in the following sections.
When Numbering Plans Do Not Overlap
When Cisco Unity numbering plans do not overlap across locations—that is, when subscriber 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 subscriber 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. When Chris logs on to Cisco Unity to send a message to Kelly, he has to remember not to dial the prefix, 456, when addressing the message. However, you could assign Kelly the alternate extension 4564060 so that Chris enters the same number when addressing a message as when calling. When an alternate extension has been set up, Chris can enter either 4060 or 4564060 when addressing a message to Kelly.
Figure 2-3
No Overlapping Extensions
If the numbering 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 Numbering Plans Overlap
When numbering plans overlap across locations, you have the following options:
•
•
•
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. However, when one of the options described above is set up, subscribers on the local server will be able to 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, if you want to access the subscriber accounts and other objects created on another server, you need to 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.
The following sections provide information about accessing the Cisco Unity Administrator on other servers:
•
•
•
Browsing to Another Cisco Unity Administrator from the Local Cisco Unity Administrator
The Cisco Unity Administrator on the local server provides links to the Cisco Unity Administrator of other 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.
To Browse to Another Cisco Unity Administrator on a Networked Cisco Unity Server
Step 1
Step 2
Step 3
Another instance of the Cisco Unity Administrator appears in a separate browser window. This is the Cisco Unity Administrator of the server that you selected.
Searching for Subscriber Accounts Created on Another Cisco Unity Server
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 applicable Cisco Unity Administrator is launched. Do the following procedure to use the Cisco Unity Administrator on your local Cisco Unity server to search for subscriber accounts on other Cisco Unity servers in the network.
To Search for Subscriber Accounts Created on a Cisco Unity Server Other than Your Local Cisco Unity Server
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
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.
Using Global Subscriber Manager to Browse to Another Cisco Unity Administrator
You can also use the Global Subscriber Manager (GSM) from Tools Depot to launch the Cisco Unity Administrator on another server. 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 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
Step 2
Double-click the subscriber account that you want to edit. The applicable Cisco Unity Administrator will be displayed in a browser window. Refer to the GSM Help file for more information.
Cisco Unity Administrator Accounts
See the following sections:
•
•
•
About the Accounts That Can Be Used to Administer Cisco Unity
To access the Cisco Unity Administrator, administrators can use one of the following accounts:
Until you create a Cisco Unity subscriber account specifically for the purpose of administering each Cisco Unity server, you must use the administration account that was selected when each Cisco Unity server was installed to log on to the Cisco Unity Administrator.
Consider using an alternative to the administration account, if you want to do the following:
•
•
The Cisco Unity subscriber accounts that are used to access the Cisco Unity Administrator must have the appropriate COS rights. COS rights specify which tasks, if any, administrators can do in the Cisco Unity Administrator. For example, some subscriber accounts can be associated with a COS that provides read-only access, or restricts administrators to accessing specific pages in the Cisco Unity Administrator for the purpose of unlocking accounts or changing passwords.
In addition to COS rights, subscriber accounts that are used to access the Cisco Unity Administrator must be associated with a Windows domain account.
To create additional subscriber accounts for the purposes of accessing the Cisco Unity Administrator, complete the procedures in the "Creating Subscriber Accounts That Can Be Used to Access the Cisco Unity Administrator" section. If you prefer not to create a specific subscriber account for each administrator who needs to access the Cisco Unity Administrator, you can use the GrantUnityAccess utility to associate one or more Windows domain accounts with a single subscriber account. For more information about using the GrantUnityAccess utility, see the "Granting Administrative Rights to Other Cisco Unity Servers" section.
As a best practice, it is recommended that Cisco Unity administrators not use the same subscriber account to log on to the Cisco Unity Administrator that they use to log on to the ActiveAssistant to manage their own Cisco Unity accounts. In addition, they should not use Unity service accounts to administer Cisco Unity.
Creating Subscriber Accounts That Can Be Used to Access the Cisco Unity Administrator
To create additional subscriber accounts for the purposes of accessing the Cisco Unity Administrator, complete the following tasks on each Cisco Unity server:
1.
2.
3.
4.
5.
–
–
Until this task is done, administrators can access the Cisco Unity Administrator only from another computer.
To Add the Windows Domain Account to the Local Administrators Group (When the Cisco Unity Server Is a Member Server)
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
To Add the Windows Domain Account to the Domain Admins Group (When the Cisco Unity Server Is a Domain Controller)
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Granting Administrative Rights to Other Cisco Unity Servers
Rather than create subscriber accounts on each server for each person who needs to administer Cisco Unity, you can use the GrantUnityAccess utility to associate any number of Windows domain accounts with a single Cisco Unity subscriber account. GrantUnityAccess maintains a table of the associated Windows domain accounts and Cisco Unity subscriber accounts, which Cisco Unity references when someone tries to access the Cisco Unity Administrator. This table is used to determine whether to permit someone access to the Cisco Unity Administrator.
Before you use GrantUnityAccess, consider the following:
•
•
•
•
•
Use the following procedure to run GrantUnityAccess. Note that you cannot run GrantUnityAccess remotely across a network, so you will need to run it on each Cisco Unity server that you want to make accessible, and for each account that you want to map. See the "Sample GrantUnityAccess Arguments" section for an example of how this utility is used, and for argument syntax details.
To Use the GrantUnityAccess Utility
Step 1
Step 2
Step 3
Step 4
GrantUnityAccess -u <Domain>\<UserAlias> -s <UnitySubscriberAlias>To obtain a list of accounts that have been associated with Cisco Unity subscriber accounts, enter:
GrantUnityAccess -lTo delete an association made previously using GrantUnityAccess, enter:
GrantUnityAccess -u <Domain>\<UserAlias> -s <UnitySubscriberAlias> -dTo display information about GrantUnityAccess arguments, enter:
GrantUnityAccess -?Sample GrantUnityAccess Arguments
For example, assume that JSmith and KChen are the aliases of administrators who need access to the Cisco Unity Administrator on another Cisco Unity server, and that their Windows domain accounts are in a domain called NewYorkDomain. To associate their Windows domain accounts with the administration account that was selected when Cisco Unity was installed, run GrantUnityAccess two times as follows:
GrantUnityAccess -u NewYorkDomain\JSmith -s <UnitySubscriberAlias for administration account>GrantUnityAccess -u NewYorkDomain\KChen -s <UnitySubscriberAlias for administration account>Rather than specifying the administration account, you could associate the Windows domain account for Neil Jones with the subscriber account for Kelly Bader instead:
GrantUnityAccess -u NewYorkDomain\NJones -s KBaderDistribution 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:
•
•
•
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.
Tip
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. For more information, see the "Primary Location Addressing Option Settings" section on page 6-6.
Hiding Voice-Messaging-Only Subscribers
In some Voice Messaging installations, the subscribers already have Exchange mailboxes intended for e-mail. If your Exchange configuration is such that both the Voice Messaging 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 Messaging 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
Limitations and Notable Behavior
This section provides information about notable expected behavior associated with Digital Networking. See the following sections for more information:
•
•
•
•
Call Transfer Settings Unavailable
When calls are transferred from the automated attendant or directory assistance to subscribers who are 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 that are normally available with supervised transfers will not be available on these calls. If the discrepancy in behavior is a concern to subscribers, you may want to consider limiting directory handler searches to the local server by adjusting the setting on the Directory Handler Search Options page in the Cisco Unity Administrator.
Digital Networking in an Exchange Mixed-Mode Environment
To use Digital Networking in an Exchange mixed-mode environment, all the Cisco Unity servers must use Exchange 2000 for a partner server. When migrating from Exchange 5.5 to Exchange 2000 in stages, all Cisco Unity servers must be reconfigured to use an Exchange 2000 partner server. Digital Networking is not supported between a Cisco Unity server with a partner Exchange 5.5 server and a Cisco Unity server with a partner Exchange 2000 server.
Limitations Subscribers Can Encounter
When a Cisco Unity/Exchange 5.5 server is networked with a Cisco Unity/Exchange 2000 server, primary locations, delivery locations, and other Cisco Unity-specific attributes needed for messaging do not replicate correctly through the Microsoft Active Directory Connector (ADC). Therefore, subscribers with mailboxes on Exchange 5.5 servers are not able to send messages to subscribers with mailboxes on Exchange 2000 servers and vice versa. However, when all of the Cisco Unity servers have Exchange 2000 for a partner server, subscriber messaging in an Exchange mixed-mode environment functions properly.
This limitation also exists when Digital Networking is combined with AMIS, Bridge, SMTP, and VPIM Networking because delivery locations do not replicate through the ADC. For example, if AMIS delivery locations are created in Cisco Unity/Exchange 5.5, only those subscribers on Cisco Unity/Exchange 5.5 are able to send messages to the remote voice messaging system represented by the AMIS delivery location. Similarly, if the AMIS delivery locations are created in Cisco Unity/Exchange 2000, only those subscribers on Cisco Unity/Exchange 2000 are able to send messages to the remote voice messaging system represented by the AMIS delivery location. However, when all the Cisco Unity servers have Exchange 2000 for a partner server, AMIS messaging in an Exchange mixed-mode environment functions properly.
Leaving a Message Versus Sending a Message: Limitations with Identified Subscriber Messaging
The limitations with identified subscriber messaging described in this section exist in all Cisco Unity versions prior to 3.1(6), and in 4.0(1) and 4.0(2). Identified subscriber messaging is fully functional in Cisco Unity 3.1(6). In installations with servers running different versions of Cisco Unity, in order for identified subscriber messaging to be fully functional, all Cisco Unity servers must be running version 3.1(6). (Note that identified subscriber messaging between Cisco Unity servers is by default not enabled. See the "Enabling Identified Subscriber Messaging" section for information.)
When a subscriber on one Cisco Unity server calls a subscriber on a different Cisco Unity server and leaves a message, Cisco Unity does not identify the message as being from a subscriber. That is, identified subscriber messaging does not work, and instead, the call is handled as though it came from an unidentified caller. This means that:
•
•
•
However, Cisco Unity can identify the message as being from a subscriber when a subscriber calls another subscriber who is on the same Cisco Unity server and leaves a message (in which case the above limitations do not apply). If the discrepancy in behavior is a concern to subscribers, you may want to consider disabling identified subscriber messaging on each Cisco Unity server. To disable identified subscriber messaging, do not check the check box Subscribers Are Identified as Message Senders Only if They Log On in the Cisco Unity Administrator on the Configuration > Settings page.
It is important to note the difference when a subscriber first logs on to Cisco Unity, and then records and sends a message (as opposed to placing a phone call, and then leaving a message because the intended recipient does not answer the call). When the subscriber has logged on to Cisco Unity, Cisco Unity can identify the message sent as being from the subscriber, regardless of which Cisco Unity server the message recipient is homed on. In this case, the phone system is not involved and the recipient phone does not ring. Instead, the message is sent via Digital Networking. Thus, when the recipient listens to the message, Cisco Unity plays the recorded name of the sending subscriber, and allows the recipient to record a reply.
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:
•
•
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.)
