Table Of Contents

Network Settings

Overview: Network Settings

Primary Location Profile Settings

Primary Location Addressing Option Settings

Delivery Locations Profile Settings

AMIS Delivery Options Settings

AMIS Schedule Settings

Bridge Subscriber Creation Options Settings

Bridge Synchronization Options Settings

Network Settings

---

Overview: Network Settings

You use the network settings to set up and administer Cisco Unity for networking with other Cisco Unity servers and other voice messaging systems. The term networking has a broad definition and encompasses the following ideas:

•Subscribers associated with one Cisco Unity server can use the phone to send voice messages to:

–Subscribers associated with another Cisco Unity server.

–Individuals who use a voice messaging system other than Cisco Unity.

–Individuals with access to a computer connected to the Internet.

•Outside callers can find any subscriber in the phone directory and leave a voice message. Depending on the phone system and network configuration, outside callers who reach the Cisco Unity automated attendant or directory assistance can be transferred to any subscriber phone, even to the phone of a subscriber who is not associated with the local server. (Note there are limitations to this functionality. For more information, refer to the "Limitations" section in the "Digital Networking" chapter of the Networking in Cisco Unity guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/net/index.htm.

Cisco Unity provides the following networking options:

•Digital Networking—Allows messaging among multiple Cisco Unity servers connected to a single, global directory. The message transport agent (MTA) is the message transport mechanism between servers. You use this option when the Cisco Unity servers access a shared voice mail directory.

•SMTP Networking—Allows messaging among Cisco Unity servers that are on separate networks. You use this option when the Cisco Unity servers have separate voice mail directories.

•AMIS Networking—Allows messaging to and from other voice messaging systems that support the AMIS protocol.

•Cisco Unity Bridge Networking—Allows messaging between a Cisco Unity system and an Octel system on an Octel analog network by using the Cisco Unity Bridge.

With the SMTP, AMIS, and Bridge networking options, you may choose blind addressing and/or create Internet, AMIS, or Bridge subscribers.

No matter which networking option you use, you always customize the primary location settings for your Cisco Unity server. If setting up Cisco Unity to communicate with another voice messaging system, you also need to create a delivery location on your local Cisco Unity server that corresponds to the other voice messaging system.

Refer to the following sections in this chapter for more information about network settings:

•Primary Location Profile Settings—This section provides information about the profile settings for the primary location.

•Primary Location Addressing Option Settings—This section provides information about the settings that allow you to select the scope of a search performed when a subscriber uses the phone to address a message by name or extension.

•Delivery Locations Profile Settings—This section provides information about the profile settings for delivery locations that you create.

•AMIS Delivery Options Settings—This section provides information about the settings that control AMIS message transmissions.

•AMIS Schedule Settings—This section provides information about the AMIS schedule settings, which in conjunction with the AMIS restriction table, controls when AMIS messages are transmitted.

•Bridge Subscriber Creation Options Settings—This section provides information on the settings that affect auto-created Bridge subscribers.

•Bridge Synchronization Options Settings—This section provides information about the settings related to synchronizing the subscriber directory on the Bridge with the subscriber directory on Cisco Unity.

For more information about networking, refer to the Networking in Cisco Unity guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/net/index.htm.

Primary Location Profile Settings

Each Cisco Unity server has a primary location, which is created during installation and which cannot be deleted. The primary location identifies the Cisco Unity server and contains the networking information needed to communicate with other locations, which can be Cisco Unity servers or other voice messaging systems. With the exception of public distribution lists, all subscribers and other Cisco Unity objects (such as call handlers) created on your Cisco Unity server are associated with the primary location.

If you change the Domain Name or the Dial ID on the primary location after creating subscriber accounts, extension addresses are not automatically updated. You should run the Extension Address utility to generate new extension addresses for subscribers. For more information, refer to the "Extension Address Utility" section in the "SMTP Networking" chapter of the Networking in Cisco Unity guide. This guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/net/index.htm.

No matter which networking option Cisco Unity uses to send and receive voice messages, you need to customize the primary location of your Cisco Unity server. For more information, refer to the "Primary Location Profile Settings" section in the "Primary Location Settings" chapter of the Networking in Cisco Unity guide.

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

Table 22-1 Network > Primary Locations > Profile Page 

Field	Considerations
Display Name	This displays the name of the primary location. To change the name, enter a new name here, and then click the Save icon.
Dial ID	Enter the ID that identifies the primary location. Enter numbers only, up to a maximum of 10 digits. The minimum length for a Dial ID is one digit. The following policies are recommended: •Establish a fixed length for Dial IDs and if possible, a fixed length for extensions. •Assign unique Dial IDs. •If you use variable-length Dial IDs and extensions, the Dial IDs should be in a different numbering range than extensions. •If you use variable-length Dial IDs, the first digits of each ID should be unique with respect to other Dial IDs. If you change the Dial ID after creating subscriber accounts, the extension addresses are not automatically updated. You should run the Extension Address utility to generate new extension addresses for subscribers. To run the utility, on the Windows Start menu, click Programs > Unity > Extension Address Utility, and then click Update.
Recorded Name	Record a name for the primary location. The subscriber conversation plays the recorded name for this primary location when: •Subscribers associated with a Cisco Unity server in a different dialing domain address a message to subscribers associated with this location. (For example, assuming that "New York" is the recorded name for this location: "There are two matches. For John Smith, at New York, press 1. For Mary Smith press 2.") •Subscribers associated with a Cisco Unity server in a different dialing domain listen to messages from subscribers associated with this location. (For example: "Message 1, a voice message, from John Smith at New York....") •The setting "Play Location to Subscriber as Part of Search Results" on the Network > Primary Location > Addressing Options page is enabled on another primary location. When subscribers at the other location address a message, the recorded name for this primary location may be played in the message addressing search results along with subscriber names. (For example: "There are two matches. For Chris Newton, press 1. For New York, press 2.") To record the name here, use the Media Master control bar. (Note that the Media Master is not available across a firewall.) Use the Options menu in the Media Master control bar to set recording and playback devices, if applicable, and to use other sound files.
Dialing Domain	Select from the list or enter the name of the dialing domain of which this location is a member. A dialing domain is a collection of Cisco Unity servers that are integrated with the same phone system or phone system network. Extensions within a dialing domain must be unique. The dialing domain allows Cisco Unity to handle overlapping extensions on Cisco Unity servers that are outside of the dialing domain. A dialing domain provides a means to scope message address and directory handler searches so that Cisco Unity does not search the entire global directory. The default setting is None. Use the default when: •Your installation consists of only one Cisco Unity server. •Your installation consists of two or more Cisco Unity servers and each server is integrated with a separate phone system. That is, subscribers associated with one Cisco Unity server must dial a trunk access code or prefix and a full phone number rather than an extension when calling a subscriber associated with another Cisco Unity server. There is no limit to the number of Cisco Unity servers that can be assigned to a single dialing domain, and there is no limit to the number of dialing domains. However, a Cisco Unity server can be a member of only one dialing domain.
SMTP Domain Name (for SMTP blind addressing only)	Enter the Internet domain name for the Cisco Unity server. This is the right half of an e-mail address after the @ symbol (for example, london@cisco.com). Do not enter the @ symbol; Cisco Unity automatically inserts it. The domain name is used only in SMTP blind addressing to construct extension e-mail addresses for subscribers on the local Cisco Unity server. If you change the domain name after creating subscriber accounts, you should run the Extension Address utility to generate new extension addresses for subscribers.
AMIS Node ID: Country Code, Area Code, Phone Number (displayed only when the system key is licensed for AMIS)	Enter the numbers that are transmitted by Cisco Unity to identify itself to other voice messaging systems during outgoing AMIS calls. Because Node IDs must be unique, AMIS defines the Node ID as a country code, area code, and phone number. However, the Node ID is an identifier transmitted during the AMIS call; it is not the number that is dialed to connect to the remote voice messaging system. Therefore, the Node ID numbers do not have to correspond to a real country code, area code, and phone number. If desired, the Country Code and Area Code fields may be left blank; however, the Phone Number field must contain a number. The maximum number of digits for each field is: •Country Code—4 digits •Area Code—3 digits •Phone Number—8 digits
Unity Bridge: Node ID Server Address (displayed only when the system key is licensed for the Bridge)	Enter information that identifies this Cisco Unity server to the Bridge and the Bridge to this Cisco Unity server. •Node ID—Enter the Node ID that this Cisco Unity server represents. If this Cisco Unity server and the associated Bridge server are replacing an existing Octel Node, enter the Node ID of the Octel Node that is being replaced. The Node ID must match the Serial Number of the Unity Node that is displayed on the Unity Nodes page in the Bridge Administrator. •Server Address—Enter the fully qualified domain name of the Bridge server with which this Cisco Unity server is associated. This is the name displayed in the Windows System Control Panel on the Network Identification tab in the Full Computer Name field on the Bridge server. The Server Address must match the Cisco Unity Bridge Domain Name that is displayed on the Digital Networking page in the Bridge Administrator.

Primary Location Addressing Option Settings

The primary location addressing options allow you to control the scope of the search that Cisco Unity performs when searching for a matching extension in the following cases:

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

•When subscribers add members to private lists by using the phone or the ActiveAssistant.

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

•When Cisco Unity looks up the recipient for an incoming AMIS message.

You can set the scope to the local Cisco Unity server, to the dialing domain that the local Cisco Unity server is a member of, or to the entire global directory.

The addressing options also allow you to enable blind addressing searches for a matching delivery location Dial ID. You can set the blind addressing scope to those delivery locations created on the local Cisco Unity server, to delivery locations within the dialing domain, or to the entire directory.

For more information, refer to the "Primary Location Addressing Option Settings" section in the "Primary Location Settings" chapter of the Networking in Cisco Unity guide. This guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/net/index.htm.

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

Table 22-2 Network > Locations > Addressing Options Page 

Field	Considerations
Subscriber Searches: Limit Searches To	Select the scope of the search that Cisco Unity performs when searching for a matching subscriber extension: •Local Server—Limits the search to those subscribers associated with the local Cisco Unity server. •Dialing Domain—If a match is not found while searching the local Cisco Unity server, the search expands to include those subscribers created on other Cisco Unity servers that are in the same dialing domain as the local Cisco Unity server. •Global Directory—After searching the local Cisco Unity server and then the dialing domain (if there is one), the search expands to include every subscriber created on other Cisco Unity servers in the global directory.
Play Location to Subscriber as Part of Search Results (not applicable to blind addressing)	Check this box to have primary and delivery locations included in the search results. When checked, this setting allows subscribers to address a message in two steps. First subscribers select a particular location (either by spelling the name or by entering the Dial ID). If Cisco Unity finds a matching location, subscribers are prompted to select the extension for the recipient at that location (either by spelling the name or by entering the extension). This allows subscribers to limit a search to a specific location. This option is useful when the global directory is large and addressing a message by name results in many matches.
Blind Addressing: Allowed Locations	Select the scope of the blind addressing search for a matching delivery location that Cisco Unity performs when a subscriber addresses a message by using the phone. Select one of the following: •None—Do not allow blind addressing searches. •Local Server—Limits the search to delivery locations that were created on your Cisco Unity server. •Dialing Domain—If a match is not found while searching the local Cisco Unity server, the blind addressing search expands to include those delivery locations created on other Cisco Unity servers that are in the same dialing domain as the local Cisco Unity server. •Global Directory—After searching the local Cisco Unity server and then the dialing domain (if there is one), the search expands to include every delivery location created on other Cisco Unity servers in the global directory.

By default, setting the subscriber and blind addressing search scope to either Dialing Domain or Global Directory means that the search will find only those subscribers, locations, and distribution lists created on Cisco Unity servers within the same Exchange 5.5 site as the local Cisco Unity server. To allow messaging among all the Cisco Unity servers in the entire Exchange 5.5 organization, you also have to change three registry keys, as described in the following procedure. (Note that you do not need to do this procedure if your organization uses Exchange 2000.)

---

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.

---

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.

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\DirSynchEx55\1.00\Locations

Step 5 Double-click SearchRoot to display the Edit String dialog box.

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

o=OrganizationName

(Substitute the name of your Exchange organization for OrganizationName.)

Step 7 Click OK.

Step 8 Expand the following key:

HKEY_LOCAL_MACHINE\Software\ActiveVoice\DirSynchEx55\1.00\MailUsers

Step 9 Double-click SearchRoot to display the Edit String dialog box.

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

o=OrganizationName

(Substitute the name of your Exchange organization for OrganizationName.)

Step 11 Click OK.

Step 12 Expand the following key:

HKEY_LOCAL_MACHINE\Software\ActiveVoice\DirSynchEx55\1.00\Distribution
Lists

Step 13 Double-click SearchRoot to display the Edit String dialog box.

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

o=OrganizationName

(Substitute the name of your Exchange organization for OrganizationName.)

Step 15 Click OK and then close Regedit.

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

---

Delivery Locations Profile Settings

Delivery locations are Cisco Unity objects that contain the addressing information that Cisco Unity needs to send messages to and receive messages from other voice messaging systems—which may or may not be Cisco Unity. You create a delivery location that corresponds to each remote messaging system that the local Cisco Unity server communicates with.

When creating a delivery location, you specify a Destination Type—either SMTP, AMIS, or Bridge. The Destination Type determines which fields are displayed on the delivery locations page.

If you change the Domain Name or the Dial ID on a delivery location after creating subscriber accounts, extension addresses are not automatically updated. You should run the Extension Address utility to generate new extension addresses. For more information, refer to the following sections in the Networking in Cisco Unity guide: "Extension Address Utility" in the "SMTP Networking" chapter, "Extension Addresses" in the "AMIS Networking" chapter, and "Extension Addresses" in the "Bridge Networking" chapter. The Networking in Cisco Unity guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/net/index.htm.

Use the following table to learn more about the profile settings for delivery locations.

Table 22-3 Network > Delivery Locations > Profile Page 

Field	Considerations
Name	This displays the name of the delivery location. To change the name, enter a new name here, and then click the Save icon.
Dial ID	Enter the ID that identifies the location to Cisco Unity. Enter numbers only, up to a maximum of 10 digits. The minimum length for a Dial ID is one digit. When addressing a message to another location by using blind addressing, subscribers dial a number that is made up of the Dial ID and the extension (or the remote mailbox number) of the recipient. When setting up blind addressing for SMTP networking, the ID that you enter here must match the Dial ID of the primary location at the corresponding remote Cisco Unity server. The following policies are recommended: •Establish a fixed length for Dial IDs and if possible, a fixed length for extensions. •Assign unique Dial IDs. Dial IDs should not be the same as other Dial IDs or extensions. •Use a different numbering range for Dial IDs than for extensions. •If you use variable-length Dial IDs, the first digits of each ID should be unique with respect to other Dial IDs. If you change the Dial ID after creating subscriber accounts, run the Extension Address utility to generate new extension addresses. To run the utility, on the Windows Start menu, click Programs > Unity > Extension Address Utility, and then click Update.
Recorded Name	Record a name for the delivery location. The subscriber conversation plays this recorded name when the setting "Play Location to Subscriber as Part of Search Results" on the Network > Primary Location > Addressing Options page is enabled. When subscribers address a message, the recorded name for this delivery location is played in the message addressing search results along with subscriber names. (For example: "There are two matches. For Chris Newton, press 1. For New York, press 2.") Additionally, the subscriber conversation plays this recorded name when subscribers address messages by using blind addressing to this delivery location. To record the name here, use the Media Master control bar. (Note that the Media Master is not available across a firewall.) Use the Options menu in the Media Master control bar to set recording and playback devices, if applicable, and to use other sound files.
Destination Type	Displays the message transport mechanism used to send messages to the location. The Destination Type is specified when the delivery location is created, and it cannot be changed. The Destination Type is one of the following: •SMTP—Indicates that messages are sent over the Internet by using a standard SMTP gateway. Typically, the destination is another Cisco Unity server. •AMIS—Indicates that messages are sent to a voice messaging system other than Cisco Unity by using the AMIS analog protocol. •Bridge—Indicates that messages are sent to an Octel system by using the Bridge. Cisco Unity sends messages to the Bridge in Voice Profile for Internet Mail (VPIM) format (with proprietary extensions) using a standard SMTP gateway. The Bridge converts the message format and sends it to the appropriate Octel server by using the OctelNet analog protocol.
Domain Name (for SMTP locations only)	Enter the Internet domain name for the Cisco Unity server that corresponds to this delivery location. This is the right half of an e-mail address after the @ symbol (for example, london@cisco.com). Do not enter the @ symbol; Cisco Unity automatically inserts it. This Domain Name is used only in SMTP blind addressing. To address a message by using blind addressing, subscribers enter the Dial ID followed by the extension. Cisco Unity uses the specified Dial ID to look up the delivery location to obtain the Domain Name. Then Cisco Unity constructs the blind address in the following format: <Dial ID>_<Extension>@<Domain Name>. For blind addressing to work, this Domain Name must match the Domain Name in the corresponding remote primary location. Additionally, extension addresses need to be generated for the subscribers at the remote location.
Delivery Phone Number (for AMIS locations only)	Enter the phone number, including trunk access code, that Cisco Unity dials for outgoing AMIS calls to the remote voice messaging system that corresponds to this delivery location.
Node ID: Country Code, Area Code, Phone Number (for AMIS locations only)	Enter the numbers used to identify the remote voice messaging system that corresponds to this delivery location. This Node ID must match the Node ID that the corresponding remote voice messaging system transmits during incoming calls. Cisco Unity accepts messages only from known AMIS nodes, so the Node ID entered here must exactly match the Node ID that the remote voice messaging system transmits. Because Node IDs must be unique, AMIS defines the Node ID as a country code, area code, and phone number. However, the Node ID is an identifier transmitted during the AMIS call; it is not the number that is dialed to connect to the remote voice messaging system. Therefore, the Node ID numbers do not have to correspond to a real country code, area code, and phone number. If desired, the Country Code and Area Code fields may be left blank; however, the Phone Number field must contain a number. The maximum number of digits for each field is: •Country Code—4 digits •Area Code—3 digits •Phone Number—8 digits
Disable Outbound Message Delivery to This AMIS Location (for AMIS locations only)	By default, this box is unchecked. This box is checked automatically when an outbound AMIS call to this delivery location is answered by a person, a non-AMIS compliant voice messaging system, or an answering machine. Checking the box automatically prevents Cisco Unity from repeatedly attempting to deliver messages to an incorrect Delivery Phone Number. If the call is answered by a person, Cisco Unity plays a prompt that instructs the person to prevent further calls by pressing a touchtone. If the person presses the touchtone, Cisco Unity checks this box and disables outbound calls to this location. If the person simply hangs up, or if a non-AMIS compliant voice messaging system answers, then Cisco Unity retries the delivery phone number according to the settings on the Network > AMIS Options > Delivery Options page before disabling the location. Any messages that could not be delivered to this location remain in the UAmis mailbox until you confirm the delivery phone and then uncheck this box. An error is logged in the Windows Application Event log when messages remain in the UAmis mailbox for more than 24 hours. Note that when two or more Cisco Unity servers are networked together, you can view the contents of delivery locations created on other Cisco Unity servers, and edit this field from your local server.
Bridge Server Address (for Bridge locations only)	Displays the address of the Bridge server. You set the Bridge server address on the Primary Location page.
Octel Node ID (for Bridge locations only)	Enter the number of the OctelNet node that corresponds to this delivery location. This number must match the Serial Number of one of the nodes displayed on the Octel Nodes page in the Bridge Administrator. In turn, the Serial Number of an Octel node in the Bridge Administrator must match the number of a node in OctelNet. You create a Bridge delivery location for each Octel node that is listed on the Octel Nodes page on the Bridge.

AMIS Delivery Options Settings

The AMIS delivery options settings control attributes of outgoing AMIS calls. These settings apply to messages sent to all AMIS delivery locations and AMIS subscribers created on your Cisco Unity server.

One of the settings that you specify here is the Local Dial Restriction Table. This restriction table and the AMIS schedule together determine when outgoing AMIS calls are made. See the "Overview: Restriction Tables" section on page 20-1 for basic information about restriction tables.

For more information, refer to the "AMIS Networking" chapter in the Networking in Cisco Unity guide. This guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/net/index.htm.

Use the following table to learn more about AMIS delivery options settings.

Table 22-4 Network > AMIS Options> Delivery Options Page 

Field	Considerations
Deliver Urgent Messages Immediately	Check this box to allow messages marked as urgent to be delivered immediately. Checking this box overrides both the Local Dial Restriction Table and the AMIS schedule. When the box is unchecked, Cisco Unity handles urgent messages the same as non-urgent messages.
Local Dial Restriction Table	Select a restriction table that determines which AMIS delivery numbers can be processed immediately. If an AMIS delivery number is allowed by the restriction table, messages to this number are delivered immediately. If the delivery number is not allowed by the restriction table, messages are queued in the UAmis mailbox until the AMIS schedule becomes active. By default, the Local Dial Restriction Table field is set to the predefined Default AMIS restriction table. You can modify the Default AMIS restriction table or select another restriction table. For example, you may want to modify this restriction table to disallow long distance delivery numbers and adjust the AMIS schedule to become active when the long distance phone rates are lower.
If the Remote System Does Not Answer: Hang Up After This Many Rings	Specify the number of rings that Cisco Unity waits for the remote node to answer when making an AMIS call. After the specified number of rings, Cisco Unity hangs up. The default value is 4.
If the Remote System Does Not Answer: Try Calling This Many Times	Specify the number of times that Cisco Unity makes AMIS redelivery attempts when the remote system did not answer the initial call. The default value is 4. When the schedule that allows AMIS deliveries becomes inactive, the count that Cisco Unity maintains for this setting is reset to 0.
If the Remote System Does Not Answer: Retry After This Many Minutes	Specify the number of minutes that Cisco Unity waits after an AMIS call is not answered before attempting the call again. The default value is 5 minutes.
If the Remote System Is Busy: Try Calling This Many Times	Specify the number of times that Cisco Unity makes AMIS redelivery attempts when the initial attempt resulted in a busy signal. The default value is 4. When the schedule that allows AMIS deliveries becomes inactive, the count that Cisco Unity maintains for this setting is reset to 0.
If the Remote System Is Busy: Retry After This Many Minutes	Specify the number of minutes that Cisco Unity waits after receiving a busy signal before attempting the AMIS call again. The default value is 5 minutes.

AMIS Schedule Settings

The AMIS schedule and the AMIS restriction table together determine when outgoing AMIS calls are made. If a delivery number for an outgoing AMIS message is allowed by the AMIS restriction table, then the message is sent immediately—the schedule settings do not apply. If the delivery number is not allowed by the AMIS restriction table, then the schedule determines when the message is sent. In other words, the schedule determines when messages are sent for delivery numbers that are disallowed by the AMIS restriction table.

Cisco Unity batches messages to a delivery location, with a maximum of nine messages per batch. If an AMIS transmission is in progress when the schedule becomes inactive, the transmission of the entire batch of messages is completed. However, any other messages remaining in the queue, but not in the batch that was in the process of being transmitted, are queued until the next active time in the schedule. Queued messages are placed in the Inbox for the UAmis account.

Because the transmission of AMIS messages may tie up voice ports for long periods of time, you may want to schedule outgoing AMIS calls during closed hours or at times when Cisco Unity is not processing many calls. Additionally, if most or all of your AMIS delivery numbers are long distance, you may want to schedule the AMIS calls to be transmitted when the long distance phone rates are lower.

For more information, refer to the "AMIS Networking" chapter in the Networking in Cisco Unity guide. This guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/net/index.htm.

Use the following table to learn more about AMIS schedule settings.

Table 22-5 Network > AMIS > Schedule Page 

Field	Considerations
Click Individual Blocks to Set Hours	Click the blocks in the grid to change from inactive to active hours. Click the block again to undo your change. Messages queued in the UAmis mailbox are sent only during the active hours on the schedule. Note that you can set active and inactive hours for one day, then use the Copy Day's Schedule box to copy the settings to other days.
Copy Day's Schedule	To avoid clicking the same blocks for more than one day, use the Copy Day's Schedule and >> functions. Select a day to copy, then select which days to copy the schedule setting to.

Bridge Subscriber Creation Options Settings

The creation option settings are applied only to the Bridge subscribers that are automatically created by Cisco Unity when it receives an "Add User" request from the Bridge. These settings allow you to select the subscriber template and to choose whether the auto-created Bridge subscribers are shown in the global address list.

The Bridge acts as a networking gateway between Cisco Unity and an existing Octel system on an Octel analog network. In addition to the settings here, you also configure settings on the Bridge server itself. For more information, refer to the "Bridge Networking" chapter in the Networking in Cisco Unity guide. The Networking in Cisco Unity guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/net/index.htm.

Use the following table to learn more about Bridge subscriber options settings.

Table 22-6 Network > Bridge Options> Bridge Subscriber Creation Options Page 

Field	Considerations
Subscriber Template	Select the template on which to base new Bridge subscriber accounts. The template affects most subscriber settings. You may want to select the predefined {Bridge Subscriber} Template, because it does not add new Bridge subscribers to the All Subscribers distribution list.
Show Created Subscribers in Your E-Mail Server Address Book	Specify whether the auto-created Bridge subscribers should be listed in the global address list. Depending on your installation, the users of the remote voice messaging system may already have Windows accounts and Exchange mailboxes on your local network. Therefore, when Bridge subscriber accounts are created for these people, the global address list will contain duplicate listings—the existing user account and a contact for Exchange 2000 users (or custom recipient for Exchange 5.5 users). Both listings are viewable in Outlook. The default setting is to hide the Bridge subscribers. To show the Bridge subscribers in the global address list, check the box.

Bridge Synchronization Options Settings

The Bridge synchronization options allow you to control the scope when synchronizing the subscriber directory on the Bridge with the subscriber directory on Cisco Unity. Additionally, it provides an option for forcing a full synchronization.

The Bridge acts as a networking gateway between Cisco Unity and an existing Octel system on an Octel analog network. In addition to the settings here, you also configure settings on the Bridge server itself. For more information, refer to the "Bridge Networking" chapter in the Networking in Cisco Unity guide. The Networking in Cisco Unity guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/net/index.htm.

Use the following table to learn more about Bridge synchronization options settings.

Table 22-7 Network > Bridge Options> Bridge Synchronization Options Page 

Field	Considerations
Synchronize Subscribers From The	Specify the scope for the synchronization of the subscriber directory on the Bridge with subscribers on Cisco Unity. Choose one of the following: •Local Server—Subscriber information for subscribers on this Cisco Unity server is sent to the Bridge. Information about subscribers on other Cisco Unity servers is not synchronized. Choose this option when each Cisco Unity server is connected to a separate Bridge server. •Dialing Domain—Subscriber information is sent to the Bridge for subscribers in the dialing domain of which this Cisco Unity server is a member. Information about subscribers outside of the dialing domain is not synchronized. Choose this option when this server acts as the bridgehead server for the other Cisco Unity servers in the dialing domain. •Global Directory—Subscriber information for all subscribers in the global directory is sent to the Bridge. Choose this option when this server acts as the bridgehead server for the other networked Cisco Unity servers. Whenever a subscriber account in the selected scope is added, deleted, or modified, Cisco Unity sends the account information to the Bridge.
Synchronize	Click this button to force a full synchronization of subscriber data on Cisco Unity with the subscriber directory on the Bridge, according to the synchronization scope. During the setup of Cisco Unity and the Bridge for networking, the Bridge sends a full directory synchronization request to Cisco Unity when the Unity Node information is first entered in the Bridge Administrator. This full directory synchronization request is sent by the Bridge only once. If everything on the Cisco Unity side has been properly set up (the Voice Connector has been installed, the UOmni mailbox is set up, and the primary location on the Cisco Unity server contains the Bridge Node ID and Server Address), then the initial full synchronization happens automatically. If everything was not in place prior to the request from the Bridge, then the Synchronize button should be used to initiate the first synchronization. During normal operation, Cisco Unity automatically synchronizes subscriber information with the Bridge on a regular basis. Therefore, you usually do not need to force synchronization. However, you may want to force synchronization if the Cisco Unity server, the Bridge, or the network connection to the Bridge has been down for a long period of time, and if there have been numerous changes to subscriber information in Cisco Unity. When connectivity is restored, directory synchronization with the Bridge resumes automatically, but in this case, forcing a full synchronization may be preferable. Directory synchronization does not impact messaging. Subscribers can still send and receive messages when the directories are not synchronized. If Cisco Unity subscriber information is missing from the Bridge directory, Octel users will not receive a voice name confirmation when they address a message, but the message is still delivered. The time necessary for a full synchronization depends on many factors, such as the network connection to the Bridge, the size of the directory, and whether subscribers have recorded voice names. (Voice name data is large in comparison with the other subscriber information that is sent to the Bridge.)