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.
•Unidentified callers can find any subscriber in the phone directory and leave a voice message. Depending on the phone system and network configuration, unidentified 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.
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.
•Internet Subscribers—Allows messaging between Cisco Unity subscribers and individuals with access to a computer connected to the Internet.
•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 between Cisco Unity and other voice messaging systems that support the AMIS protocol.
•Bridge Networking—Allows messaging between a Cisco Unity system and an Octel system on an Octel analog network by using the Cisco Unity Bridge.
•VPIM Networking—Allows messaging between Cisco Unity and other voice messaging systems that support the VPIM protocol.
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.
See the following sections in this chapter for more information about network settings:
Each Cisco Unity server has a primary location, which is created during installation and which cannot be deleted. The primary location identifies the Cisco Unity server and contains the networking information needed to communicate with other locations, which can be Cisco Unity servers or other voice messaging systems. With the exception of public distribution lists, all subscribers and other Cisco Unity objects (such as call handlers) created on your Cisco Unity server are associated with the primary location.
No matter which networking option Cisco Unity uses to send and receive voice messages, you need to customize the primary location of your Cisco Unity server.
Use the following table to learn more about the profile settings for the primary location.
This displays the name of the primary location. To change the name, enter a new name here, and then click the Save icon.
Dial ID
Enter the ID that identifies the primary location. Enter numbers only, up to a maximum of 10 digits. The default minimum length is 3 digits.
Although the minimum length for Dial IDs can be reduced by using the Advanced Settings Tool, one- and two-digit Dial IDs may conflict with private distribution list IDs during an address search. When a subscriber addresses a message by entering a one- or two-digit number, Cisco Unity first searches for a matching private distribution list. If a match is found, the search stops. Therefore, when a subscriber addresses a message by entering a location Dial ID to narrow down the search scope to a particular location, if the number entered matches a private distribution list ID, the conversation offers only the private distribution list as a destination. If subscribers do not address messages to other locations by first entering a Dial ID, there is no conflict and the minimum length for Dial IDs can be reduced to accommodate complex dial plans.
The following policies are recommended:
•Establish a fixed length for Dial IDs and if possible, a fixed length for extensions.
•Assign unique Dial IDs.
•If you use variable-length Dial IDs and extensions, the Dial IDs should be in a different numbering range than extensions.
•If you use variable-length Dial IDs, the first digits of each ID should be unique with respect to other Dial IDs. (For example, do not create Dial IDs like 432 and 4325.)
•Even if the Dial ID will never be used by subscribers when they address messages, enter a number that does not conflict with extensions, such as 001 or 002.
Recorded Name
Record a name for the primary location. The recorded name for the location is played in the subscriber conversation in a number of places, including when:
•Subscribers associated with a Cisco Unity server in a different dialing domain address a message to subscribers associated with this location. (For example, assuming that New York is the recorded name for this location: "There are two matches. For John Smith, at New York, press 1. For Mary Smith press 2.")
•Subscribers associated with a Cisco Unity server in a different dialing domain listen to messages from subscribers associated with this location. (For example: "Message 1, a voice message, from John Smith at New York....")
•The setting Include Locations in Searches on the Network > Primary Location > Addressing Options page is enabled on another primary location. When subscribers at the other location address a message, the recorded name for this primary location may be played in the message addressing search results along with subscriber names. (For example: "There are two matches. For Chris Newton, press 1. For New York, press 2.")
To record the name here, use the Media Master control bar. (Note that the Media Master is not available across a firewall that blocks DCOM communications.) Use the Options menu in the Media Master control bar to set recording and playback devices, if applicable, and to use other sound files.
Dialing Domain
Select from the list or enter the name of the dialing domain of which this location is a member. The list contains dialing domain names already configured on at least one other Cisco Unity server in the network that have replicated to the local server. Add the Cisco Unity server to a dialing domain when it is integrated with the same phone system or phone system network as other Cisco Unity servers that access the same directory.
Note that the dialing domain name is case sensitive and must be entered exactly the same on all of the servers. To ensure that all servers are correctly added to the same dialing domain, enter the dialing domain name on one Cisco Unity server and wait for the name to replicate to the other Cisco Unity servers. By doing so, you also confirm that replication is working correctly among the servers. The time that it takes for the primary location data from other Cisco Unity servers to be reflected on the local server depends on your network configuration and replication schedule.
A dialing domain provides a means to set the search scope for message addressing and for call transfers from the auto attendant and directory handler(s). You must add the Cisco Unity server to a dialing domain before you enable the following features:
•Cross-server log in.
•Cross-server transfers from the auto attendant and directory handler(s)
•Live reply ("call the sender") to another Cisco Unity subscriber on another networked Cisco Unity server.
•Live reply to a user on another voice messaging system who has a corresponding AMIS, Bridge, or VPIM subscriber account on another networked Cisco Unity server.
•Identified subscriber messaging for Cisco Unity subscribers on different networked Cisco Unity servers.
•Identified subscriber messaging for AMIS, Bridge, and VPIM subscribers, even when your installation consists of only one Cisco Unity server.
The default setting is None. Use the default when:
•Your installation consists of only one Cisco Unity server, and the server is not configured for AMIS, Bridge, or VPIM Networking.
•Your installation consists of two or more Cisco Unity servers, but each server is integrated with a separate phone system.
There is no limit to the number of Cisco Unity servers that can be assigned to a single dialing domain, and there is no limit to the number of dialing domains. However, a Cisco Unity server can be a member of only one dialing domain.
SMTP Domain Name
(for SMTP and VPIM networking only)
Enter the Internet-addressable SMTP domain name for the Cisco Unity server. This is the right half of an e-mail address after the @ symbol (for example, london.cisco.com). Do not enter the @ symbol; Cisco Unity automatically inserts it.
The domain name is required for the SMTP and VPIM networking options. Both of these networking options use the Simple Mail Transfer Protocol (SMTP) for messaging between the local Cisco Unity server and the remote voice messaging system. When a subscriber on the local Cisco Unity server addresses a message to a remote user, the Voice Connector uses the SMTP Domain Name to construct a From address, which is required by SMTP. Messages that are missing the domain name in the From address will not be delivered. Additionally, a valid From address allows the remote recipient to reply to the message.
AMIS Node ID:
Country Code, Area Code, Phone Number
(displayed only when licensed for AMIS)
Enter the numbers that are transmitted by Cisco Unity to identify itself to other voice messaging systems during outgoing AMIS calls.
During an outgoing AMIS call (when Cisco Unity is the originating system), the Node ID becomes the system number in the system number frame. The system number is used by the destination voice messaging system to dial out to send reply messages, or optionally to screen and reject incoming AMIS calls.
The Node ID should contain all the information necessary for the destination system to send a reply message. The numbers that you enter depend on the physical location of the voice messaging system with which Cisco Unity communicates. If the country code and area code are not needed by the other voice messaging system to send a reply message, you do not need to enter them here.
The maximum number of digits for each field is:
•Country Code—4 digits
•Area Code—3 digits
•Phone Number—8 digits
Primary Location Addressing Option Settings
The primary location addressing options allow you to control the scope of the search that Cisco Unity performs when searching for a matching extension in the following cases:
•When a subscriber addresses a message by using the phone.
•When subscribers add members to private lists by using the phone or the Cisco Unity Assistant. (Note that in version 3.1 and earlier, the Cisco Unity Assistant was known as the ActiveAssistant, or AA.)
•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.
Use the following table to learn more about location addressing option settings.
Select the scope of the search that Cisco Unity performs when a subscriber addresses a message by using the phone, when members are being added to a public or private distribution list, and for incoming AMIS messages.
•Local Server—Limits the search to subscribers created on the local Cisco Unity server.
•Dialing Domain—If a match is not found while searching the local Cisco Unity server, the search expands to include subscribers created on other Cisco Unity servers that are in the same dialing domain as the local Cisco Unity server.
•Global Directory—After searching the local Cisco Unity server and then the dialing domain (if there is one), the search expands to include every subscriber created on other Cisco Unity servers in the directory.
Include Locations in Searches
Check this check box to have locations included in searches. This option is useful when the global directory is large and addressing a message by spelling the name results in many matches. For this setting to be helpful to subscribers, locations need to have recorded voice names.
When checked, this setting allows subscribers to address a message in two steps. First subscribers select a particular location (by spelling the name or by entering the Dial ID). If Cisco Unity finds a matching location, the recorded voice name for the location is played (assuming one has been recorded). At this point, subscribers can spell the name of the recipient to limit the search to the specified location. Note that if the subscriber selected the location by entering the Dial ID, the subscriber needs to switch to spelling mode (by pressing # twice) to search for the subscriber.
For example, assume there are two Cisco Unity servers configured for Digital Networking. Assume 100 is the Dial ID of the primary location for the Paris Cisco Unity server, and that a voice name ("the Paris sales office") for the location has been recorded. John, a subscriber on the local Cisco Unity server, wants to send a message to Kelly Bader at the Paris location, but he does not know the correct extension.
•John logs on to Cisco Unity and presses 2 to send a message.
•John enters 100# to select the Paris Cisco Unity server.
•When the primary location 100 is found, the conversation plays, "For the Paris sales office, press #."
•John presses # to confirm; the conversation plays, "Enter the extension followed by #."
•John presses ##; the conversation plays, "Spell the name of a person or distribution list."
•John enters 22337#. Cisco Unity searches for a matching subscriber name at location 100, and matches on Kelly Bader. The conversation plays, "For Kelly Bader at extension 3047, press #."
•John presses # to confirm; the conversation plays, "Added. To add another name, press 1. To record the message, press #."
Blind Addressing: Allowed Locations
Select the scope of the blind addressing search for a matching delivery location that Cisco Unity performs when a subscriber addresses a message by using the phone. Select one of the following:
•None—Do not allow blind addressing searches.
•Local Server—Limits the search to delivery locations that were created on your Cisco Unity server.
•Dialing Domain—If a match is not found while searching the local Cisco Unity server, the blind addressing search expands to include those delivery locations created on other Cisco Unity servers that are in the same dialing domain as the local Cisco Unity server.
•Global Directory—After searching the local Cisco Unity server and then the dialing domain (if there is one), the search expands to include every delivery location created on other Cisco Unity servers in the global directory.
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, Bridge, or VPIM. The Destination Type determines which fields are displayed on the delivery locations page.
When more than one Cisco Unity server is networked together via Digital Networking, information about the primary locations on other Cisco Unity servers is displayed on the Delivery Location page. This information is display only.
Use the following tables to learn more about the profile settings for delivery locations.
Table 25-3 Profile Settings Applicable to All Types of Delivery Locations
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 ten digits. The default minimum length is three digits.
Although the minimum length for Dial IDs can be reduced by using the Advanced Settings Tool, one- and two-digit Dial IDs may conflict with private distribution list IDs during an address search. When a subscriber addresses a message by entering a one- or two-digit number, Cisco Unity first searches for a matching private distribution list. If a match is found, the search stops. Therefore, when a subscriber addresses a message by entering a location Dial ID (to narrow down the search scope to a particular location), if the number entered matches a private distribution list ID, the conversation offers only the private distribution list as a destination. If subscribers do not address messages to other locations by first entering a Dial ID, there is no conflict, and the minimum length for Dial IDs can be reduced to accommodate complex dial plans.
When sending messages to a remote location, subscribers can dial a number that is made up of the Dial ID and the Remote mailbox number of the recipient.
When setting up SMTP networking with a Cisco Unity server in a different directory, 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.
•Assign Dial IDs that have at least three-digits.
•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.
•Even if the Dial ID will never be used by subscribers when they address messages, enter a number that does not conflict with extensions, such as 001 or 002.
Recorded Name
Record a name for the delivery location. The subscriber conversation plays this recorded name in a number of places. For example, assume that the setting Include Locations in Searches on the Network > Primary Location > Addressing Options page is enabled. When subscribers address a message by spelling the name, 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.")
To record the name here, use the Media Master control bar. (Note that the Media Master is not available across a firewall that blocks DCOM communications.) Use the Options menu in the Media Master control bar to set recording and playback devices, if applicable, and to use other sound files.
Destination Type
Display only. Indicates the type of delivery 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 the delivery location corresponds to a remote Cisco Unity server that accesses a directory different than the local Cisco Unity server. Messages between the local and remote Cisco Unity servers are encoded in a proprietary format and delivered over the Internet or a private TCP/IP network by using the standard Simple Mail Transfer Protocol (SMTP).
•AMIS—Indicates that the delivery location corresponds to an AMIS-compliant voice messaging system. Messages are sent by using the industry-standard Audio Messaging Interchange Specification analog (AMIS-a) protocol.
•Bridge—Indicates that the delivery location corresponds to an Octel node in an Octel analog network. Messages are exchanged between Cisco Unity and the Octel system by using the Cisco Unity Bridge. Cisco Unity sends messages to the Bridge in Voice Profile for Internet Mail (VPIM) format with proprietary extensions. The Bridge converts the message format and sends it to the appropriate Octel server by using the Octel Analog Networking protocol.
•VPIM—Indicates that the delivery location corresponds to a VPIM-compliant voice messaging system. Messages are sent by using the industry-standard VPIM protocol over the Internet or a private TCP/IP network.
Table 25-4 Profile Settings Specific to AMIS Delivery Locations
Field
Considerations
Delivery Phone Number
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
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.
Although the Node ID numbers should contain all the information necessary for Cisco Unity to send a reply message to the originating system, this is not enforced because of the different ways in which voice messaging systems implement the AMIS protocol. Therefore, the only requirement is that the numbers entered here match the Node ID that the corresponding remote voice messaging system transmits.
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
By default, this check box is unchecked. When an outbound AMIS call to this delivery location is answered by a person or a voice messaging system that is not AMIS-compliant (such as an answering machine), this check box is checked automatically. Checking the check 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 check box and disables outbound calls to this location. If the person simply hangs up, or if a voice messaging system that is not AMIS-compliant answers (such as an answering machine), Cisco Unity retries the delivery phone number according to the settings on the Network > AMIS Options > Delivery Options page. When the maximum number of retries has been reached, Cisco Unity checks this check box to disable further calls to this number.
Any messages that could not be delivered to this location remain in the UAmis mailbox until you confirm the delivery phone number and then uncheck this check 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 multiple 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.
Table 25-5 Profile Settings Specific to Bridge Delivery Locations
Field
Considerations
Bridge Server Full Computer Name
Enter the fully qualified domain name of the Bridge server used for messaging with the Octel node represented by this delivery location. This is the name displayed on the Bridge server in the Windows System Control Panel on the Network Identification tab in the Full Computer Name field. The name entered here must also match the name entered in the Bridge Server Full Computer Name field on the Digital Networking page in the Bridge Administrator.
Octel Node Serial Number
Enter the serial number of the Octel 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. The number entered here must also match the serial number of a corresponding Octel node.
The Octel Node Serial Number and the Remote Mailbox Length as a pair must be unique within the global directory. In the rare case that this is needed, you can create more than one Bridge delivery location with the same Octel Node Serial Number but with different Remote Mailbox Length values.
Remote Mailbox Length
Enter the number of digits required for mailboxes as specified in Octel for the node that corresponds to this delivery location.
You create at least one Bridge delivery location for each remote Octel node in the Octel analog network. Typically, there is a one-to-one correspondence of Bridge delivery locations and Octel nodes. However, it is possible (though rare) that an Octel server may be configured to have mailboxes with different lengths. In this case, you must create separate Bridge delivery locations that have the same Octel Node Serial Number but with a different number in the Remote Mailbox Length field.
For example, assume that an Octel server with the serial number 45678 has been configured to allow mailboxes of length 4 and 5. When configuring the Cisco Unity bridgehead server, you create two Bridge delivery locations with the Octel Node Serial Number 45678; one delivery location has the Remote Mailbox Length set to 4, and the other has the Remote Mailbox Length set to 5.
If you specify a prefix (or prefixes) for the location, then the value that you entered for the remote mailbox length is used to determine the recipient mailbox number. To determine the mailbox number when addressing a message, Cisco Unity starts at the end of the entered number, and keeps including digits until the number of digits equals the remote mailbox length.
Encrypt Incoming Private Messages
Check this check box to encrypt incoming private voice messages that are sent by subscribers at this delivery location.
Private voice messages are not encrypted and secure until they reach the Exchange server on which the Voice Connector is installed.
Default: Check box not checked.
Decrypt Outgoing Private Messages
Check this check box to decrypt outgoing private secure voice messages sent to subscribers at this delivery location.
Enabling the decryption of outgoing private secure messages for a delivery location allows voice messages marked private and secure to be delivered from this location to subscribers at other locations. These voice messages are decrypted when they leave the Voice Connector, and therefore are no longer secure after that point. When a subscriber receives a decrypted private secure voice message, the message is marked and played as a private message.
Default: Check box not checked.
Table 25-6 Profile Settings Specific to SMTP Delivery Locations
Field
Considerations
Domain Name
Enter the Internet-addressable SMTP 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 field must match the SMTP Domain Name in the corresponding remote primary location. When subscribers on the local Cisco Unity server address messages to subscribers on the remote Cisco Unity server, the Voice Connector obtains the Domain Name to construct the To address in the following format:
Table 25-7 Profile Settings Specific to VPIM Delivery Locations
Field
Considerations
SMTP Domain Name
Enter the Internet-addressable SMTP domain name that is used to construct addresses for individuals who use the voice messaging system 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.
The Voice Connector accepts VPIM messages only from addresses with a domain name that corresponds to an SMTP Domain Name in a VPIM Delivery Location. Therefore, the domain name entered here must exactly match the domain name that the remote voice messaging system uses when sending messages to Cisco Unity.
Remote Phone Prefix
Enter the number that is used to construct addresses for individual who use the voice messaging system that corresponds to this delivery location. The maximum allowable digits in the prefix is 64.
Subscribers do not enter the prefix when addressing messages. On outgoing messages from Cisco Unity to the remote system, the Voice Connector adds the prefix to the beginning of the recipient mailbox number to form the To address.
On incoming messages to Cisco Unity from the remote system, the Voice Connector removes the prefix from the beginning of the sender mailbox number to form the From address.
If all delivery locations have a unique domain name, this field is optional. This field is required to be a unique number if you have multiple delivery locations with the same domain name.
Unity Phone Prefix
Enter the number that is used to construct addresses for Cisco Unity subscribers who send messages to individuals who use the voice messaging system that corresponds to this delivery location. The maximum allowable digits in the prefix is 64.
On outgoing messages from Cisco Unity subscribes to subscribers at this VPIM location, the Voice Connector adds the prefix to the beginning of the sender mailbox number to form the From address.
On incoming messages to Cisco Unity subscribers from subscribers at this VPIM location, the Voice Connector removes the prefix from the beginning of the recipient mailbox number to form the To address.
Audio Format Conversion: Incoming Messages
Indicate whether incoming messages from the remote system that corresponds to this VPIM location should be converted to another audio format. Messages and voice names (if included) from the remote system will be stored in the selected audio format. Choose from the following:
•Do Not Convert Incoming Messages—Incoming messages are not converted to another audio format. Choose this option if you want the messages to be stored in the same format in which they were sent. Typically, you only choose this option when the remote system is another Cisco Unity server, which can send message in formats other than G.726. For other voice messaging systems, consult the documentation to determine the audio formats that the system supports for VPIM messages.
•G.711 (mu-law)—Incoming messages are converted to G.711 format. This audio format is fully supported by Cisco Unity and Cisco CallManager, and the codec is installed automatically by Windows.
•GSM 6.10—Incoming messages are converted to GSM 6.10 format. This audio format is fully supported by Cisco Unity and Cisco CallManager, and the codec is installed automatically by Windows.
•G.729a—Incoming messages are converted to G.729a format. This audio format is fully supported by Cisco Unity and Cisco CallManager, and the codec is installed automatically by Cisco Unity.
We recommend that incoming VPIM messages be stored in the same audio format that the local Cisco Unity server(s) use for recording and playing messages. However, if you want incoming VPIM messages to be stored in some other audio format, you will need to verify that the applicable codec is installed on all Cisco Unity servers, and other computers that access these messages. In particular:
•If your organization has multiple Cisco Unity servers networked together, all of the Cisco Unity servers must have the codec installed.
•If subscribers use ViewMail for Microsoft Outlook or the Cisco Unity Inbox to listen to messages, the codec may need to be installed on each subscriber workstation.
If incoming messages are converted from a format other than G.711, G.729a, GSM 6.10, or G.726, the applicable codec must be installed on the Exchange server on which the Voice Connector is installed.
Audio Format Conversion: Outbound Messages
Indicate whether outbound messages from Cisco Unity to the remote system that corresponds to this VPIM location should be converted to another audio format. Messages and voice names (if included) will be sent in the selected audio format. Choose from the following:
•Do Not Convert Outgoing Messages—Outbound messages are not converted to another audio format. Choose this option if you want the messages to be sent in the same format in which they were recorded. Typically, you only choose this option when the remote system is another Cisco Unity server. For other voice messaging systems, consult the documentation to determine the audio formats that the system supports for VPIM messages.
•G.726—Outbound messages are converted to G.726 format. This is the format required by the VPIM Version 2 specification and supported by all VPIM-compliant voice messaging systems.
If outbound messages are converted to G.726 from a format other than G.711, G.729a, GSM 6.10, the applicable codec must be installed on the Exchange server on which the Voice Connector is installed.
When Sending Messages from Cisco Unity Include the Sender's Recorded Name
Check this check box to have the voice name of the sending Cisco Unity subscriber added to the beginning of each message sent to this VPIM location.
Some legacy systems can create directory entries using the recorded name and vCard of the sender. If the remote system is Cisco Unity with Microsoft Exchange, the recorded name and vCard may be used to create or update directory entries. If the remote system does not have directory entries that correspond to local Cisco Unity subscribers, you may want to send the recorded voice name so that the sender is identified when recipients listen to messages.
When Sending Messages from Cisco Unity Include the Sender's vCard
Check this check box to have the Voice Connector attach a vCard that contains information about the sending Cisco Unity subscriber to each outgoing message to this VPIM location. The vCard will contain the following information about the sender:
•Name
•Phone Number
•E-mail Address
Some legacy systems can create directory entries by using the recorded name and vCard of the sender. If the remote system is Cisco Unity with Microsoft Exchange, the data may be used for creating or updating directory entries, if the remote system is configured to allow automatic creation, updates, and deletion of VPIM subscribers for the delivery location corresponding to this system.
Encrypt Incoming Private Messages
Check this check box to encrypt incoming private voice messages that are sent by subscribers at this delivery location.
Private voice messages are not encrypted and secure until they reach the Exchange server on which the Voice Connector is installed.
Default: Check box not checked.
Decrypt Outgoing Private Messages
Check this check box to decrypt outgoing private secure voice messages sent to subscribers at this delivery location.
Enabling the decryption of outgoing private secure messages for a delivery location allows voice messages marked private and secure to be delivered from this location to subscribers at other locations. These voice messages are decrypted when they leave the Voice Connector, and therefore are no longer secure after that point. When a subscriber receives a decrypted private secure voice message, the message is marked and played as a private message.
Default: Check box not checked.
Bridge Delivery Location Prefixes
Use the following table to learn more about prefixes for Bridge delivery locations.
Enter a prefix or prefixes for the Octel node that corresponds to this delivery location. Prefixes are optional, but you may enter as many prefixes as required by your numbering plan. Enter numbers only, up to a maximum of 21 digits. The minimum length is 1 digit. Each prefix must be unique with respect to other prefixes within the global directory.
When Octel subscribers send messages to subscribers on other nodes in the Octel analog network, they enter a network address as the message destination. A network address consists of a node prefix, which identifies the remote server, and the mailbox number of the recipient. In many cases, the prefix is the same as either the area code where the destination node is located, or the prefix(es) defined in the phone system dialing plan. This allows subscribers to use the same number when addressing a network message as they do when calling.
In Cisco Unity, prefixes are optional, depending on your numbering plan. Prefixes are not needed when Cisco Unity subscribers can send messages to Octel subscribers by entering the dial ID of the location followed by the recipient mailbox number.
Assigned Location Prefixes
This displays prefixes that are in use for all delivery locations.
Delivery Location Subscriber Creation Settings
Use the following table to learn more about settings for auto-created Bridge subscribers that can be set on a delivery location basis.
Indicate how Octel text names that do not contain commas should be parsed into first and last names for auto-created Bridge subscribers. Select one of the following:
•Treat as FirstName LastName
•Treat as LastName FirstName
In Cisco Unity, the first and last names of subscribers are stored as distinct fields in the directory, which allows directory lookups to be configured by either the last or the first name. However, Octel subscriber names are stored as one single name. When the Bridge sends a request to create a new Bridge subscriber, the CsBridgeConnector service parses the single Octel text name by the rule you have selected here.
For example, when Treat as FirstName LastName is selected, the Octel text name "Terry Campbell" is parsed such that "Terry" is the first name, and "Campbell" is the last name.
When Treat as LastName FirstName is selected, the Octel text name "Bader Kelly" is parsed such that "Kelly" is the first name, and "Bader" is the last name.
Default: Treat as LastName FirstName.
Mapping Text Names
Indicate how Octel text names should be mapped to the display names for auto-created Bridge subscribers. These settings control how Bridge subscriber names appear in the Outlook address book. Typically, you will want to use a custom mapping and add text such as "- Voice Mail" to the display name so that subscribers can distinguish a Bridge subscriber from an e-mail user account when they use Outlook to address a message. Select one of the following.
•Map Octel Text Names Directly to Cisco Unity Bridge Subscriber Names: Click this option to have the display names for Bridge subscribers be the same as their corresponding Octel text names.
•Custom Mapping: Click this option and enter a rule that defines how Octel text names are mapped to Bridge subscriber display names. Enter the tokens <FirstName>, <LastName>, or <TextName> in any combination along with any additional text. Always precede <FirstName>, <LastName>, or <TextName> with a space, comma, or semicolon unless it appears at the beginning of the rule. In addition, always follow one of these tokens with a space, comma or semicolon unless it appears at the end of the rule. No additional characters are required at the beginning or end of a rule.
For example, assume that the Octel text name is "Bader, Kelly."
–The rule <TextName> produces the display name Bader, Kelly.
–The rule <FirstName> <LastName> produces the display name Kelly Bader.
–The rule <TextName> (Voice mail) produces the display name Bader, Kelly (Voice mail).
Unless hidden, Bridge subscriber display names are shown in the address books for Microsoft Outlook and the Cisco Personal Communications Assistant. To help prevent others from sending e-mail to Bridge subscribers, you may want to append a term such as "(Voice mail)" to the names of Bridge subscribers.
Default: Map Octel Text Names Directly to Cisco Unity Bridge Subscriber Display Names.
Include Location Dial ID in Primary Extension on Auto-Created Bridge Subscribers
Check the box to have the primary extension consist of the delivery location dial ID added to the beginning of the remote mailbox number when the CsBridgeConnector service creates Bridge subscribers.
Use the following table to learn more about settings you can configure per delivery location to control whether VPIM subscriber creation, modification, and deletion actions occur automatically, and if automatic updates are enabled, how the information in incoming messages is used to create or modify a record.
Check this check box to allow the CsVPIMConnector service to automatically create a VPIM subscriber and associated Active Directory contact when an Add-New-Subscriber request is received from the Voice Connector.
When the check box is unchecked, the Voice Connector does not generate Add-New-Subscriber requests when messages are received from senders at this delivery location.
Default: Check box not checked.
Automatically Modify VPIM Subscribers
Check this check box to allow the CsVPIMConnector service to automatically modify a VPIM subscriber and associated Active Directory contact when a Modify-Subscriber request is received from the Voice Connector.
When the check box is checked, indicate when the Voice Connector should generate Modify-Subscriber requests:
•Only When the Text Name Changes—The VPIM subscriber record will be updated only when the text name received in the VPIM message does not match the display name of the VPIM subscriber.
•With Each VPIM Message—Every incoming VPIM message from a remote sender at this delivery location will result in an update to the corresponding VPIM subscriber.
When the check box is unchecked, the Voice Connector does not generate Modify-Subscriber requests when messages are received from senders at this delivery location.
Default: Check box not checked.
Automatically Delete VPIM Subscribers
Check this check box to allow the CsVPIMConnector service to automatically delete a VPIM subscriber, the associated Active Directory contact, and all other associated properties such as public and private distribution list membership, when a Delete-Subscriber request is received from the Voice Connector.
When the check box is unchecked, the Voice Connector does not generate Delete-Subscriber requests when nondelivery receipts (NDRs) are received.
Default: Check box not checked.
Obtain VPIM Subscriber Information From
Indicate the source from which to derive text name and extension information for creating or updating VPIM subscriber records. Choose one of the following:
•Sender's vCard—Use the vCard (an electronic business card) attachment. Only the vCard in the most recent portion of the message will be processed. If an incoming message does not contain a vCard, no directory update will be made.
•VPIM Message Header—Use information from the fields in the VPIM message header. If the header does not contain all fields required for the directory change, no update will occur.
Default: Sender's vCard.
VPIM Subscriber Template
Select the template on which to base new VPIM subscriber accounts. The template chosen affects most subscriber settings.
By default, the predefined {Default Subscriber} Template will be used for auto-created VPIM subscribers, but you may select any other template.
Allow VPIM Subscriber Display Name Updates
Check this check box to allow the CsVPIMConnector service to automatically modify the display name for a VPIM subscriber and associated Active Directory contact when a Modify-Subscriber request is received from the Voice Connector.
When the check box is unchecked, the CsVPIMConnector service will modify the first and last name fields and the recorded voice name when a Modify-Subscriber request is received, but will leave the display name unchanged. This could result in a mismatch between the display name shown in the address book and the first and last names used for spell-by-name, or a mismatch in the recorded name played as confirmation when a message is addressed to this subscriber. This is particularly true if the mailbox number has been reassigned to a different owner on the remote messaging system.
Default: Check box checked.
Allow VPIM Subscribers Without Recorded Voice Names
Check this check box to allow the CsVPIMConnector service to create or modify VPIM subscribers when the incoming VPIM message used as the basis for a directory update does not include a recorded voice name.
When the check box is unchecked, new VPIM subscribers will not be created for incoming messages that do not contain an Originator-Spoken-Name attachment. If the sender of an incoming message matches an existing VPIM subscriber, and if automatic modification of VPIM subscribers is enabled, the VPIM subscriber will be deleted if the recorded voice name is not present in the message.
When the check box is checked, if the sender of an incoming message that does not include an Originator-Spoken-Name attachment matches an existing VPIM subscriber, and if automatic modification of VPIM subscribers is enabled, the existing recorded voice name will be deleted.
Default: Check box checked.
If the Text Name Has No Comma
Indicate how text names that do not contain commas should be parsed into first and last names for auto-created entries. Select one of the following:
•Treat as FirstName LastName
•Treat as LastName FirstName
In Cisco Unity, the first and last names of subscribers are stored as distinct fields in the directory, which allows directory lookups to be configured by either the last or the first name. However, text names sent by remote messaging systems may be transmitted as one single name. The single text name field is parsed by the rule that you select here.
For example, when Treat as FirstName LastName is selected, the text name "Terry Campbell" is parsed such that "Terry" is the first name, and "Campbell" is the last name.
When Treat as LastName FirstName is selected, the text name "Bader Kelly" is parsed such that "Kelly" is the first name, and "Bader" is the last name.
Default for VPIM locations: Treat as FirstName LastName.
Mapping Text Names
Indicate how text names on incoming messages should be mapped to the display names for auto-created entries. Select one of the following:
•Directly to VPIM Subscriber Display Names—Click this option to have the display names for VPIM subscribers match their corresponding text names.
•Custom Mapping—Click this option and enter a rule that defines how text names will be mapped to VPIM subscriber display names. Enter the tokens <FirstName>, <LastName>, or <TextName> in any combination, along with any additional text. Always precede <FirstName>, <LastName>, or <TextName> with a space, comma, or semi-colon if not at the beginning of the rule, and always follow one of these tokens with a space, comma or semi-colon unless it comes at the end of the rule. In other words, you must enter a space, comma, or semi-colon separator between tokens and additional text, except at the beginning or end of a rule.
For example, assume that the text name is "Bader, Kelly."
The rule <TextName> produces the display name Bader, Kelly.
The rule <FirstName> <LastName> produces the display name Kelly Bader.
The rule <TextName> (Voice mail) produces the display name Bader, Kelly (Voice mail).
Unless hidden, VPIM subscriber display names are shown in the address books for Microsoft Outlook and the Cisco Personal Communications Assistant. To help prevent others from sending e-mail to VPIM subscribers, you may want to append a term such as "(Voice mail)" to the names of VPIM subscribers.
Default: Map Text Names Directly to VPIM Subscriber Display Names.
Map VPIM Subscriber Extensions To
Indicate how the phone number on incoming messages should be mapped to the extension for auto-created VPIM subscribers. Select one of the following:
•Phone Number—Click this option to have the extensions for VPIM subscribers be the same as the phone numbers that are parsed from incoming VPIM messages.
•Phone Number - Remote Phone Prefix—Click this option to have extensions for VPIM subscribers be formed by removing the remote phone prefix from the beginning of the phone number.
•Location Dial ID + Phone Number—Click this option to have the extensions for VPIM subscribers be formed by adding the location Dial ID in front of the phone number.
•Phone Number + Location Dial ID - Remote Phone Prefix—Click this option to have the extensions for VPIM subscribers be formed by removing the remote phone prefix from the beginning of the phone number, and then adding the location Dial ID in front of the resulting number.
This mapping is only applied to create the extension for the VPIM subscriber; it is not applied to the remote mailbox number. In addition, the extension mapping is only applied when the subscriber is created, and will not be changed by an automatic modification, even if the rule for mapping extensions has changed. If you wish to change the rule after subscribers have been created, extensions for existing VPIM subscribers can be updated manually using the Cisco Unity Administrator or the Bulk Edit tool, or the existing subscribers can be deleted, and when they are automatically created again, their extensions will follow the new mapping rule.
Note that if the phone number in the incoming message cannot be successfully mapped to an extension by using the option selected, the creation of the VPIM subscriber will fail.
Default: Phone Number.
Dialing Domain Options
The dialing domain options allow you to enable the following features for networked Cisco Unity servers belonging to the same dialing domain:
•Cross-server log on (available only with Cisco CallManager integrations).Cross-server logon allows you to provide subscribers with one number that they can call to log on to Cisco Unity from outside the organization. Subscribers call the pilot number for one Cisco Unity server and are transferred to the applicable home Cisco Unity server to log on.
Note that the intended use of this feature is limited to subscribers calling in from outside your organization, and that:
–Subscriber phones must still forward calls to the Cisco Unity server that is home to the subscriber.
–When calling from their extensions, subscribers should still dial the number of their home Cisco Unity server. If subscriber phones have a "Messages" or a speed-dial button that dials the number to access Cisco Unity, the buttons must still be configured to call the Cisco Unity server that is home to the subscriber.
•The transfer method for calls transferred from auto attendant and directory handlers to Cisco Unity subscribers on other Cisco Unity servers. You choose one of the following transfer methods:
–Release Calls to the Phone System
–Cross-Server Transfer (available only with Cisco CallManager integrations)
•The transfer method for live reply calls to Cisco Unity subscribers on other Cisco Unity servers. This allows subscribers to reply to messages from Cisco Unity subscribers on another Cisco Unity server by calling them. Note that whether subscribers have access to the live reply feature is controlled by the class of service message settings. See the "Class of Service Messages Settings" section on page 11-9 for details. You choose one of the following transfer methods for the live reply call:
–Release Calls to the Phone System
–Cross-Server Live Reply (available only with Cisco CallManager integrations)
Use the following table to learn more about the dialing domain settings.
Subscribers Dial the Same Number to Log On to Cisco Unity
(available only with Cisco CallManager integration)
Check this check box so that all subscribers in the dialing domain—no matter which server is their home Cisco Unity server—can use the pilot number of this Cisco Unity server to log on to Cisco Unity. You will also need to enter the pilot numbers of all of the other Cisco Unity servers in the dialing domain in the Pilot Numbers section. When a subscriber homed on another Cisco Unity server calls this server to log on, the home Cisco Unity server is called, and the call is handed off to the home Cisco Unity server so that the subscriber can log on.
By default the check box is unchecked.
Note that subscriber phones must still be configured to forward calls to the home Cisco Unity server. Also, voice mail speed-dial or "Messages" buttons on subscriber phones must be configured to call the home Cisco Unity server.
Transfer Options for Calls Transferred from Auto Attendant and Directory Handlers to Cisco Unity Subscribers on Other Cisco Unity Servers
Indicate how calls from the automated attendant or a directory handler on this Cisco Unity server will be transferred to subscribers on other Cisco Unity servers in the dialing domain. Choose one of the following:
•Release Calls to the Phone System—On a release to phone system transfer, Cisco Unity dials the subscriber call transfer number and hangs up. Note the following limitations:
–Call screening, call holding, and announce features are not available for the called subscriber.
–Only the call transfer number for a subscriber is replicated among the Cisco Unity servers, the other call transfer settings are not. If a subscriber call transfer setting is set to "No (send directly to subscriber's greeting)," Cisco Unity sets the call transfer number to the subscriber extension. If the subscriber extension is a valid extension on the phone system that Cisco Unity is integrated with, then the subscriber phone rings. If the subscriber extension is not a valid phone extension, what happens to the call after that depends on the phone system and how it is configured. If you do not configure the phone system to handle calls to the subscriber extensions, the caller may be disconnected.
•Cross-Server Transfer: Pass Control to the Called Subscriber's Cisco Unity Server (Available only with Cisco CallManager integrations)—With this option, a call is first transferred to the Cisco Unity server that is home to the called subscriber. The home Cisco Unity then checks the call transfer settings of the called subscriber before transferring the call to the subscriber. To use this option, you will also need to enter the pilot numbers of all the other Cisco Unity servers in the dialing domain in the Pilot Numbers section.
Subscribers Can Call Back a Cisco Unity Subscriber on a Different Cisco Unity Server
Indicate whether subscribers homed on this Cisco Unity server who have the applicable class of service rights are allowed to respond to a message from another subscriber on a different Cisco Unity server in the dialing domain by calling them. In other words, indicate whether live reply between subscribers on different Cisco Unity servers in the dialing domain is allowed. If the box is checked, then indicate the transfer mechanism for the live reply call. Choose one of the following:
•Release Calls to the Phone System—On a release to phone system transfer, Cisco Unity dials the subscriber call transfer number and hangs up. Note the following limitations:
–Call screening, call holding, and announce features are not available for the called subscriber.
–Only the call transfer number for a subscriber is replicated among the Cisco Unity servers, the other call transfer settings are not. If a subscriber call transfer setting is set to "No (send directly to subscriber's greeting)," Cisco Unity sets the call transfer number to the subscriber extension. If the subscriber extension is a valid extension on the phone system that Cisco Unity is integrated with, then the subscriber phone rings. If the subscriber extension is not a valid phone extension, what happens to the call after that depends on the phone system and how it is configured. If you do not configure the phone system to handle calls to the subscriber extensions, the caller may be disconnected.
•Cross-Server Live Reply: Pass Control to the Called Subscriber's Cisco Unity Server (Available only with Cisco CallManager integrations)—The live reply call is first transferred to the home Cisco Unity server, which then checks the call transfer settings of the replied-to subscriber before transferring the call. To use this option, you will also need to enter the pilot numbers of all the other Cisco Unity servers in the dialing domain in the Pilot Numbers section.
With live reply, subscribers listening to messages by phone can reply to a subscriber message by pressing 4-4 to have Cisco Unity call the subscriber directly. (Subscribers using Optional Conversation 1 press 8-8 for live reply.) Note that whether subscribers have access to the live reply feature depends on their class of service settings. (Live reply is enabled on the Subscribers > Class of Service > Messages page.)
By default, the check box is not checked, and subscribers cannot live reply to messages from Cisco Unity subscribers on other servers. Note that when subscribers use the live reply option to call back AMIS, Bridge, or VPIM subscribers with accounts on other Cisco Unity servers in the dialing domain, the live reply call is transferred through the phone system (release to switch) and does not use the cross-server transfer functionality.
Play Prompt During Cross-Server Logon, Transfer, and Live Reply so That Callers Know Something Is Happening
Check this check box so that callers hear a prompt during logons, transfers, and live replies to another Cisco Unity server. Depending on your phone system, it may take a few seconds for Cisco Unity to look up the home Cisco Unity server, dial the pilot number, and hand off control of the call to the home Cisco Unity server. You may want to have Cisco Unity play a "Please wait" prompt that lets callers know that something is happening.
Server Name
Display only. Displays the name of another Cisco Unity server in the dialing domain.
Dial String
Enter the phone number that the local Cisco Unity server dials when calling the Cisco Unity server named in the Server Name field in this row. Enter numbers only.
Number of Rings
Specify the number of rings that the local Cisco Unity server waits for the destination Cisco Unity server to answer. If the destination server does not answer after the specified number of rings, a prompt is played that says that the Cisco Unity server could not be reached, and the call is transferred to the opening greeting of the local Cisco Unity server.
The default is 4.
Timeout
Specify how long the local Cisco Unity server will wait for a response from the destination Cisco Unity server after the destination server has answered the call. If the destination server does not respond within the specified time period, a prompt is played that says that the Cisco Unity server could not be reached, and the call is transferred to the opening greeting of the local Cisco Unity server.
The default is 5000 milliseconds.
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 23-1 for basic information about restriction tables.
Use the following table to learn more about AMIS delivery options settings.
Check this check box to allow messages marked urgent to be delivered immediately. Checking this check box overrides both the Local Dial Restriction Table and the AMIS schedule. When the check 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, the message is sent immediately—the schedule settings do not apply. If the delivery number is not allowed by the AMIS restriction table, the schedule determines when the message is sent. Therefore, 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 UAmis mailbox.
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 when the long distance phone rates are lower.
Use the following table to learn more about AMIS schedule settings.
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 subscriber creation options are applied to all auto-created Bridge subscribers created on the bridgehead server.
Use the following table to learn more about Bridge subscriber options settings.
Select the template on which to base new Bridge subscriber accounts. The template affects most subscriber settings.
By default, the predefined {Bridge Subscriber} Template will be used for auto-created Bridge subscribers, but you may select another template. By default, Bridge subscribers created by using the {Bridge Subscriber} Template are not added to the All Subscribers distribution list and are not listed in the Cisco Unity phone directory.
Allow Automatic Creation of Bridge Subscribers
Check the box to allow the CsBridgeConnector service to automatically create a Bridge subscriber and associated Active Directory contact when an Add-New-Subscriber request is received from the Bridge.
When the box is unchecked, Add-New-Subscriber requests that do not match existing Bridge subscribers are discarded without processing.
This setting supersedes the Allow Automatic Modification of Bridge Subscriber Names and Allow Automatic Modification of Bridge Subscriber Recorded Voice Name settings. If the Allow Automatic Creation of Bridge Subscribers box is checked, and an Add-New-Subscriber request is received that does not match a remote address of an existing Bridge Subscriber, then the Bridge Subscriber will be created based on the text name and voice name (if applicable) received in the request, regardless of the Modification settings below.
Default: Check box not checked.
Allow Automatic Deletion of Bridge Subscribers
Check the box to allow the CsBridgeConnector service to automatically delete a Bridge subscriber and associated Active Directory contact when a Delete-Subscriber request is received from the Bridge.
When the box is unchecked, Delete-Subscriber requests received from the Bridge are discarded without processing.
Default: Check box not checked.
Allow Automatic Modification of Bridge Subscriber Names (First, Last, Display)
Check the box to allow the CsBridgeConnector service to automatically modify the first, last and display name for a Bridge subscriber and associated Active Directory contact when a Change-Text-Name request is received from the Bridge. Additionally, the CsBridgeConnector service will modify the first, last and display name for a Bridge subscriber and associated Active Directory contact when an Add-New-Subscriber request is received from the Bridge that matches an existing Bridge subscriber.
When the box is unchecked, Change-Text-Name requests and Add-New-Subscriber requests that match existing Bridge subscribers are discarded without processing.
Default: Check box not checked.
Allow Automatic Modification of Bridge Subscriber Recorded Voice Name
Check the box to allow the CsBridgeConnector service to automatically modify the recorded voice name for a Bridge subscriber when a Change-Spoken-Name request is received from the Bridge.
Also allows the CsBridgeConnector service to automatically modify the recorded voice name for a Bridge subscriber when an Add-New-Subscriber request is received from the Bridge that matches an existing Bridge subscriber.
When the box is unchecked, Add-New-Subscriber requests that match existing Bridge subscribers and Change-Spoken-Name requests and are discarded without processing.
Default: Check box not checked.
Bridge Synchronization Options Settings
The Bridge synchronization options allow you to force a full directory synchronization of Cisco Unity subscriber data with the directory on the selected Bridge server(s). Note that only Cisco Unity subscriber data is sent to the Bridge; Cisco Unity never sends information about Bridge subscribers.
Use the following table to learn more about Bridge synchronization options settings.
Displays a list of the serial numbers that have been defined on Cisco Unity subscribers. These are the serial numbers of nodes that the Cisco Unity bridgehead and Bridge servers represent in the Octel analog network.
Cisco Unity Bridge Servers: Select
Check the box next to each Bridge server address to which Cisco Unity subscriber information should be sent. Verify that the Bridge server(s) to which directory information will be sent is configured with a Unity Node for each serial number listed in the Unity Node ID table.
Synchronize
Click this button to force a full synchronization of subscriber data on Cisco Unity with the subscriber directory on the selected Bridge server(s).
For directory data about newly-created subscribers to be automatically sent to the Bridge, you first create the subscribers in Cisco Unity, and then create corresponding Unity Node(s) on the Bridge. If you do the reverse and create a Unity Node on the Bridge before creating any subscribers with the same serial number, you will have to force a synchronization. You can click Synchronize to force a full synchronization of the entire selected Bridge server, or you can delete and then add back the Unity Node on the Bridge server to force a synchronization of a specific Unity Node.
During normal operation, Cisco Unity automatically synchronizes subscriber information with the Bridge on a regular basis. When a subscriber account is added, deleted, or modified, Cisco Unity sends the account information to the Bridge. The Bridge makes this information available to other Octel nodes when they make an administrative call to retrieve the voice and text names of Cisco Unity subscribers.
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.
Directory synchronization does not impact messaging. Subscribers can still send and receive messages when the directories are not synchronized.
The time necessary for a full synchronization depends on many factors, such as the network connection to the Bridge, the size of the directory, whether subscribers have recorded voice names, and the codec used to record the voice names. (Voice name data is large in comparison with the other subscriber information that is sent to the Bridge.)
To get an idea of how long full synchronization from Cisco Unity to the Bridge may take, here are a few examples obtained during testing:
•1000 subscribers with 5-second voice names recorded with the G.711 codec—approximately 5 hours
•1000 subscribers with no recorded voice names—approximately 3 minutes
•1000 subscribers with 2.5-second voice names recorded with the G.711 codec—approximately 2.5 hours
•1000 subscribers with 2.5-second voice names recorded with the G.729a codec—approximately 1 hour
Bridge Unknown Caller Options Settings
When unknown callers (that is, unidentified or outside callers) reach the automated attendant of your organization, they can dial the extension of a Bridge subscriber or look up a Bridge subscriber in the phone directory (if the Bridge subscriber is listed) and leave a message. In order for messages from unknown callers to reach the recipient on the Octel system, the message header must include a "from" address in the format that the Octel expects. The Unknown Caller options allow you to specify the Node ID (that is, the serial number) and the Legacy Mailbox ID that Cisco Unity uses for the "from" address for unidentified caller messages to Bridge subscribers.
In organizations with multiple Cisco Unity servers digitally networked together, the Unknown Caller settings are only set on the bridgehead server. The settings apply for all unidentified caller messages sent to delivery locations created on the bridgehead server.
Use the following table to learn more about Unknown Caller options settings.
Enter the mailbox number to be used for messages left for Bridge subscribers from unidentified callers. For messages to be delivered to an Octel node, Octel analog networking requires that the message sender has a mailbox number and a serial number.
Enter any combination of digits from 0 to 9. Do not include any spaces. Typical mailbox numbers contain 3 to 10 digits (although a maximum of 64 digits is accepted).
Node ID
Select from the list or enter the serial number to be used for messages left for Bridge subscribers from unidentified callers. Choose a serial number from among those assigned to Unity Node(s) on the Bridge server(s).
Enter any combination of digits from 0 to 9. Do not include any spaces. Typical serial numbers contain 4 or 5 digits (although a maximum of 64 digits is accepted).
Feedback
Subscribers associated with one Cisco Unity server can use the phone to send voice messages to: