Table Of Contents
Using VPIM Networking
Setting Up Cisco Unity Connection to Use VPIM Networking
Prerequisites
Task List: Setting Up Cisco Unity Connection to Use VPIM Networking
Procedures for Setting Up Cisco Unity Connection to Use VPIM Networking
Making Design Decisions and Gathering Needed Information
Determining the Domain Name
Domain Name Requirements
Resolving Names with IP Addresses
Verifying Connectivity with the Remote Voice Messaging System
Creating VPIM Locations
Customizing VPIM Locations
Creating VPIM Contacts
Using Cisco Unity Connection Administration to Create VPIM Contacts
After Creating VPIM Contacts
Customizing VPIM Contact Directory Update Settings
Before Configuring VPIM Contact Creation Settings
Using Cisco Unity Connection Administration to Configure VPIM Contact Creation Settings
Adding Alternate Names for Each VPIM Location
Gathering Information About Cisco Unity Connection to Configure Another Voice Messaging System for VPIM
Deleting VPIM Contacts
VPIM Concepts
VPIM Messages
VPIM Addresses
Message Addressing Options
Messaging Similarities and Limitations
Audio Format Considerations
Using VPIM Networking
Cisco Unity Connection supports the Voice Profile for Internet Mail (VPIM) protocol, which is an industry standard that allows different voice messaging systems to exchange voice and text messages over the Internet or any TCP/IP network. VPIM is based on the Simple Mail Transfer Protocol (SMTP) and the Multi-Purpose Internet Mail Extension (MIME) protocols.
VPIM Networking can be used for messaging between Cisco Unity Connection 2.x servers, or between Cisco Unity Connection 2.x servers and other VPIM-compatible voice messaging systems such as Cisco Unity 4.0 and later.
VPIM Networking is a licensed feature. If your organization has multiple Cisco Unity Connection servers, each server needs to be licensed and configured for VPIM Networking. For more information on obtaining licenses for Connection features, see the "Managing Licenses" chapter.
See the following sections:
•
Setting Up Cisco Unity Connection to Use VPIM Networking
•Procedures for Setting Up Cisco Unity Connection to Use VPIM Networking
•Deleting VPIM Contacts
•VPIM Concepts
Setting Up Cisco Unity Connection to Use VPIM Networking
This section describes the prerequisites for setting up VPIM Networking, and provides a task list containing a high-level view of all of the tasks you need to complete for the setup, and the order in which they should be completed.
See the following topics:
•Prerequisites
•Task List: Setting Up Cisco Unity Connection to Use VPIM Networking
Prerequisites
Before starting the setup, verify that the following prerequisites have been met:
•Cisco Unity Connection is already installed and connected to the network.
•The remote voice messaging system that Connection will be networked with is listed in the "Support Policy for VPIM Voice Messaging Systems" section of Supported Hardware and Software, and Support Policies for Cisco Unity Connection, available at http://www.cisco.com/en/US/products/ps6509/prod_installation_guides_list.html.
•A license file with a VPIM license has been obtained and installed on each Connection server.
Task List: Setting Up Cisco Unity Connection to Use VPIM Networking
Use the task list that follows to set up VPIM Networking in Cisco Unity Connection. The cross-references take you to detailed procedures for the setup.
1. Make decisions about your numbering plan and gather information needed to configure VPIM Networking. See the "Making Design Decisions and Gathering Needed Information" section.
2. Determine the domain name that will be used for messaging between the remote voice messaging system and Connection. See the "Determining the Domain Name" section.
3. As applicable, configure DNS files. See the "Resolving Names with IP Addresses" section.
4. Verify network and SMTP connectivity with the remote voice messaging system. See the "Verifying Connectivity with the Remote Voice Messaging System" section.
5. Create the VPIM locations for each remote voice messaging system. See the "Creating VPIM Locations" section.
6. Create VPIM contacts for each VPIM location. See the "Creating VPIM Contacts" section.
7. Optionally, customize the contact creation settings for each VPIM location. See the "Customizing VPIM Contact Directory Update Settings" section.
8. Optionally, add an alternate name for each VPIM location. See the "Adding Alternate Names for Each VPIM Location" section.
9. Set up the remote voice messaging system for VPIM. Precisely how this is done depends on the voice messaging system. However, you will need to provide the remote system with information about Connection. See the "Gathering Information About Cisco Unity Connection to Configure Another Voice Messaging System for VPIM" section.
10. Test the setup to verify that Connection can exchange messages with the remote voice messaging system.
Procedures for Setting Up Cisco Unity Connection to Use VPIM Networking
This section contains all of the procedures necessary to set up Connection for VPIM Networking. See the following topics:
•Making Design Decisions and Gathering Needed Information
•Determining the Domain Name
•Resolving Names with IP Addresses
•Verifying Connectivity with the Remote Voice Messaging System
•Creating VPIM Locations
•Customizing VPIM Locations
•Creating VPIM Contacts
•Customizing VPIM Contact Directory Update Settings
•Adding Alternate Names for Each VPIM Location
•Gathering Information About Cisco Unity Connection to Configure Another Voice Messaging System for VPIM
Making Design Decisions and Gathering Needed Information
Before you begin setting up Cisco Unity Connection for VPIM Networking, be sure to plan for the following, and gather the applicable information:
•Review your numbering plan strategy to determine whether you will need to enter prefixes on the VPIM location and to determine which numbers to assign as DTMF Access IDs for the VPIM locations.
We recommend the following policies:
–Establish a fixed length for DTMF Access IDs and, if possible, a fixed length for extensions.
–Assign unique DTMF Access IDs. DTMF Access IDs should not be the same as other DTMF Access IDs or extensions.
–Assign DTMF Access IDs that have at least three digits.
–Use a different number range for DTMF Access IDs than for extensions. Do not use DTMF Access IDs that conflict with extensions, such as 001 or 002.
–If you use variable-length DTMF Access IDs, the first digits of each ID should be unique with respect to other DTMF Access IDs.
•Decide for each remote voice messaging system whether you will allow Connection to automatically create, modify, and delete VPIM contact records for users on that system, based on information received from incoming VPIM messages. Also decide how you will map the source information to VPIM contact display names and extensions.
•Make note of the following information about the remote voice messaging system: the mailbox range, the server name, the domain name, and the IP address.
Determining the Domain Name
VPIM messages are addressed in the format <Mailbox Number>@<Domain Name>. In order for messages to be exchanged between the remote voice messaging system and Cisco Unity Connection, you will need to decide on the domain name that the remote voice messaging system will use when addressing messages to Connection users. The domain name will be configured as follows:
•On the remote voice messaging system, the domain name will be configured on the location or node profile that corresponds to Connection. (For additional information, see the documentation for the remote voice messaging system.)
•In the SMTP Domain field, on the System Settings > SMTP Server Configuration page in Cisco Unity Connection Administration.
If the remote voice messaging system location or node profile that corresponds to Connection has already been configured with a domain name, use that domain name in the procedures that follow.
Domain Name Requirements
The domain name uniquely identifies the voice messaging system. When choosing domain names used by Connection and the remote voice messaging system, keep the following in mind:
•Connection and the remote voice messaging system cannot use the same domain name. Each system must use a unique domain name.
•The complete domain name used by Connection cannot be a subset of the domain name used by the remote voice messaging system. For example, if Connection is using the domain name cisco.com, the remote voice messaging system cannot use names like london.cisco.com, paris-cisco.com, or romecisco.com. However, you could use europe.cisco.com for Connection, and then use the names london.cisco.com, paris-cisco.com, and romecisco.com for the remote voice messaging systems.
Caution Choosing a domain name that does not meet these requirements will result in message delivery failure.
Resolving Names with IP Addresses
VPIM messages are sent over the Internet or any TCP/IP network via SMTP. Therefore, a mechanism for name resolution is required for the remote voice messaging server. The supported method for name resolution is through a Domain Name System (DNS).
You will need to know the fully qualified domain name (FQDN) and IP address of the remote voice messaging server. The FQDN is displayed on the System Settings > SMTP Server Configuration page.
Add a host address resource (A) record and a mail exchange (MX) record in DNS for the remote voice messaging server, if they do not already exist.
For more information about adding A and MX records in DNS, see the documentation for the DNS server.
Verifying Connectivity with the Remote Voice Messaging System
Verify that the servers that handle outgoing and incoming SMTP messages has network connectivity with the remote voice messaging server, and vice versa.
For networking with another voice messaging server, you may need to install and configure an SMTP service or gateway on that server. See the documentation of the other voice messaging system for information on installing the SMTP service or gateway. Before proceeding, verify that the SMTP service or gateway has been installed on the other voice messaging server.
To Verify Network Connectivity with the Remote Voice Messaging Server
Step 1 By using a computer on the same local network segment as the Connection server, open a command prompt window.
Step 2 Enter ping <IP address>, where <IP address> is the IP address of the remote voice messaging server, then press Enter.
If you receive no reply, troubleshoot the network connectivity problem until the problem is resolved. Then continue with Step 3.
Step 3 Enter ping <Domain name> where <Domain name> is the domain name that will be used to address messages to the remote voice messaging server. The domain name in this step is the domain name that will be entered for the VPIM location in Cisco Unity Connection Administration when setting up VPIM Networking.
Step 4 If you received a reply when pinging the IP address in Step 2, but no replies when pinging the domain name in Step 3, refer back to the "Resolving Names with IP Addresses" section. When the problem is resolved, continue with Step 5.
Step 5 Test network connectivity in the opposite direction. For systems other than Connection, see the documentation for information on how to conduct the test, and continue with Step 6. Note that the remaining steps in this procedure may not exactly match the steps necessary for your system, so you may need to make adjustments.
Step 6 On the remote server, ping the IP address of the local server that handles incoming SMTP messages.
If you receive no reply, troubleshoot the network connectivity problem until the problem is resolved. Then continue with Step 7.
Step 7 On the remote server, ping the domain name, where the domain name is the one that you decided on in the "Determining the Domain Name" section.
Step 8 If pinging by domain name fails, refer back to the "Resolving Names with IP Addresses" section.
Note Optionally, you can verify network connectivity by using the "utils network ping" CLI command.
Creating VPIM Locations
Create a VPIM location on Connection for each remote voice messaging system to which users will send messages. If Connection will be messaging with a large number of voice messaging systems, you may prefer to configure only a few delivery locations at this time and proceed with the rest of the setup. After verifying that messaging works correctly between Connection and the voice messaging systems for which VPIM locations have been configured, you can create the rest of the VPIM locations.
To Create VPIM Locations
Step 1 In Cisco Unity Connection Administration, expand System Settings, then click VPIM Locations.
Step 2 On the Search VPIM Locations page, click Add New.
Step 3 On the New VPIM Location page, enter the following settings and click Save.
Table 27-1 Settings for the New VPIM Location Page
Field
|
Setting
|
Display Name
|
Enter a descriptive name for the location.
|
DTMF Access ID
|
Enter the DTMF keys (or dial ID) that identifies the location for Connection.
|
Domain Name
|
Enter the Internet-addressable SMTP domain name of the system on the TCP/IP network that handles messages for the remote voice messaging system.
|
IP Address
|
Enter the IP address of the remote voice messaging system at this VPIM location.
|
Step 4 On the Edit VPIM Location page, enter the following settings and click Save.
Table 27-2 Settings for the Edit VPIM Location Page
Field
|
Setting
|
Voice Name
|
Click Play/Record to record a voice name for the VPIM location.
|
Remote Phone Prefix
|
If needed to accommodate your numbering plan, or if there is more than one VPIM location with the same domain name, enter a number that will be inserted before the recipient extension (for outgoing messages) or that will be removed from the recipient extension (for incoming messages).
Note that users do not enter this prefix when addressing messages.
|
Cisco Connection Phone Prefix
|
If needed to accommodate your numbering plan, enter a number that will be inserted before the Connection user extension (for outgoing messages) or that will be removed from the Connection user extension (for incoming messages).
|
Enable AGC
|
Check this check box so that Cisco Unity Connection will automatically adjust the recording volume of voice messages and voice names for this VPIM location to match the AGC target setting on the System Settings > General Configuration page.
|
Incoming Messages
|
Click an option for converting the audio format of messages that will arrive from the remote voice messaging system:
•Do Not Convert Incoming Messages—Connection will not transcode the audio format.
•System Codec—Connection will transcode the audio format to the codec that is used for recording messages. To see this setting, expand System Settings, then click General Configuration; the system codec is in the Recording Format field.
|
Outbound Messages
|
Click an option for converting the audio format of messages that will be sent to the remote voice messaging system:
•Do Not Convert Incoming Messages—Connection will not transcode the audio format. We recommend this setting when the remote voice messaging system is Connection or Cisco Unity.
•G.726—Connection will transcode the audio format to the G.726 codec. Typically, this setting is used when the remote voice messaging system is not Connection or Cisco Unity.
|
Sender's Recorded Name
|
Check this check box to enable each incoming message to add or update the recorded voice name of the sender.
|
Use Smart SMTP Host for Delivery
|
Check this check box when one of the following conditions exists:
•The remote voice messaging system is outside the corporate firewall.
•Some other smart host SMTP server will be used to deliver the message to the remote voice messaging system.
|
Enable Outgoing Private Messages
|
Check this check box so that messages marked as private (cannot be forwarded) will be sent to the VPIM location.
Uncheck this check box so that messages marked as private will not be sent to the VPIM location.
|
Enable Outgoing Secure Messages
|
Check this check box so that messages marked as secure will be sent to the VPIM location.
Uncheck this check box so that messages marked as secure will not be sent to the VPIM location. (The sender will receive an NDR.)
|
Push Directory
|
Click this button to update the VPIM contacts for the local Connection server on all remote voice messaging systems.
|
Customizing VPIM Locations
You can customize a VPIM location by using Cisco Unity Connection Administration for each remote voice messaging system to which users send messages.
To Customize VPIM Locations
Step 1 In Cisco Unity Connection Administration, expand System Settings, then click VPIM Locations.
Step 2 On the Search VPIM Locations page, click the display name for the VPIM location that you want to customize.
Step 3 On the Edit VPIM Location page, change the applicable settings and click Save.
Table 27-3 Settings for the Edit VPIM Location Page
Field
|
Setting
|
Display Name
|
Enter a descriptive name for the location.
|
DTMF Access ID
|
Enter the DTMF keys (or dial ID) that identifies the location for Connection.
|
Remote VPIM Domain Name
|
Enter the Internet-addressable SMTP domain name of the system on the TCP/IP network that handles messages for the remote voice messaging system.
|
IP Address
|
Enter the IP address of the remote voice messaging server.
|
Voice Name
|
Click Play/Record to record a voice name for the VPIM location.
|
Remote Phone Prefix
|
If needed to accommodate your numbering plan, or if there is more than one VPIM location with the same domain name, enter a number that will be inserted before the recipient extension (for outgoing messages) or that will be removed from the recipient extension (for incoming messages).
Note that users do not enter this prefix when addressing messages.
|
Cisco Connection Phone Prefix
|
If needed to accommodate your numbering plan, enter a number that will be inserted before the Connection user extension (for outgoing messages) or that will be removed from the Connection user extension (for incoming messages).
|
Enable AGC
|
Check this check box so that Cisco Unity Connection will automatically adjust the recording volume of voice messages and voice names for this VPIM location to match the AGC target setting on the System Settings > General Configuration page.
|
Incoming Messages
|
Click an option for converting the audio format of messages that will arrive from the remote voice messaging system:
•Do Not Convert Incoming Messages—Connection will not transcode the audio format.
•System Codec—Connection will transcode the audio format to the codec that is used for recording messages. To see this setting, expand System Settings, then click General Configuration; the system codec is in the Recording Format field.
|
Outbound Messages
|
Click an option for converting the audio format of messages that will be sent to the remote voice messaging system:
•Do Not Convert Incoming Messages—Connection will not transcode the audio format. We recommend this setting when the remote voice messaging system is Connection or Cisco Unity.
•G.726—Connection will transcode the audio format to the G.726 codec. Typically, this setting is used when the remote voice messaging system is not Connection or Cisco Unity.
|
Sender's Recorded Name
|
Check this check box to enable each incoming message to add or update the recorded voice name of the sender.
|
Use Smart SMTP Host for Delivery
|
Check this check box when one of the following conditions exists:
•The remote voice messaging system is outside the corporate firewall.
•Some other smart host SMTP server will be used to deliver the message to the remote voice messaging system.
|
Enable Outgoing Private Messages
|
Check this check box to enable outgoing messages to sent be as private messages (cannot be forwarded).
|
Enable Outgoing Secure Messages
|
Check this check box so that messages marked as secure will be sent to the VPIM location.
Uncheck this check box so that messages marked as secure will not be sent to the VPIM location. (The sender will receive an NDR.)
|
Push Directory
|
Click this button to update the VPIM contacts for the local Connection server on all remote voice messaging systems.
|
Creating VPIM Contacts
Revised April 2009
You may prefer to create only a few VPIM contacts at this point, for testing purposes, until you verify that Cisco Unity Connection and the remote voice messaging system can successfully exchange messages. After you have confirmed that messaging between Connection and the remote voice messaging system is working correctly, you can finish creating the VPIM contacts. Note that you must first create VPIM locations before creating VPIM contacts.
See the following sections:
•Using Cisco Unity Connection Administration to Create VPIM Contacts
•After Creating VPIM Contacts
Using Cisco Unity Connection Administration to Create VPIM Contacts
You can create VPIM contacts one at a time by using Cisco Unity Connection Administration.
To Create VPIM Contacts by Using Cisco Unity Connection Administration
Step 1 In Cisco Unity Connection Administration, expand Contacts, then click Contacts.
Step 2 On the Search Contacts page, on the Contact menu, click New Contact.
Step 3 On the New Contact page, enter the following settings and click Save.
Table 27-4 Settings for the New Contact Page
Field
|
Setting
|
Alias
|
Enter the alias of the VPIM contact.
|
First Name
|
Enter the first name of the VPIM contact.
|
Last Name
|
Enter the last name of the VPIM contact.
|
Display Name
|
Enter the display name of the VPIM contact.
|
Extension
|
Enter the extension of the VPIM contact.
|
Delivery Location
|
Click the VPIM location for the VPIM contact.
|
Remote Mailbox ID
|
Enter the mailbox number for the VPIM contact on the remote voice messaging system.
|
Step 4 On the Edit Contact Basics page, enter the following settings and click Save.
Table 27-5 Settings for the New Contact Page
Field
|
Setting
|
Transfer Extension
|
The extension that Connection dials to make a transfer.
|
Transfer Enabled
|
Check this check box so that Connection will make a transfer.
|
List in Directory
|
Check this check box to list the VPIM contact in the Connection directory.
|
Voice Name
|
Click Play/Record to record a voice name for the VPIM contact.
|
Step 5 Repeat Step 2 through Step 4 for all remaining VPIM contacts that you want to create.
After Creating VPIM Contacts
After creating VPIM contacts, consider the following:
•It takes a few minutes for the newly-created VPIM contact to be available to receive messages.
•You can make changes to settings for individual VPIM contacts in Cisco Unity Connection Administration.
•When you want to modify unique VPIM contact settings—such as the extension—for multiple users at once, you can run the Bulk Administration Tool. (Note that you cannot set or modify the delivery location by using the Bulk Administration Tool.)
•When a VPIM contact no longer needs a Connection account, you can delete the VPIM contact. For details, see the "Deleting VPIM Contacts" section.
Customizing VPIM Contact Directory Update Settings
In addition to manually creating, modifying, and deleting VPIM contacts, you can configure Cisco Unity Connection to automatically update records in the VPIM contact directory based on information contained in incoming VPIM messages. The settings that control whether or not the creation, modification, and deletion actions occur automatically, and how the incoming information is used to create or modify a record, can be individually configured for each delivery location. By default, no automatic directory updates will occur for any VPIM locations.
Depending on the Contact Creation settings that you choose for each delivery location, Connection will use information from the header of an incoming VPIM message. If a VPIM message is received from a sender on a delivery location that is configured to allow automatic VPIM contact creation, and no existing VPIM contact matches the information of the sender, a new VPIM contact record will be created, provided that the VPIM message contains:
•A phone number
•A text name
•A domain name
•A recorded voice name (when required, based on the delivery location configuration)
Additional Contact Creation settings allow you to specify how to map the parsed text name of the VPIM contact to a first name, last name, and display name, and how to map the phone number to an extension.
Note Changes to the Map VPIM Contact Extensions setting on the Contact Creation page for a VPIM location will affect only VPIM contacts that are created after the setting is saved. VPIM contacts that already existed before the Map VPIM Contact Extensions setting is changed will not be automatically updated. You must manually change the extension for each previously existing VPIM contact for that VPIM location.
If a VPIM message is received from a sender on a delivery location that is configured to allow automatic VPIM contact modification, and an existing VPIM contact matches the sender information, the VPIM contact may be updated. You can choose whether VPIM contact information is updated each time a message is received from a VPIM contact, or only when a message is received from a VPIM contact whose text name has changed since the directory entry was created. You can also decide whether or not to allow an update to the display name when a modification is made.
If a message from a Connection user to a VPIM contact results in a non-delivery receipt (NDR), indicating that the message was undeliverable because the intended recipient does not exist (SMTP 5.1.1), and if the delivery location is configured to allow automatic VPIM contact deletion, the VPIM contact will be deleted.
You can update the VPIM location contact creation settings by using the Cisco Unity Connection Administration. See the following sections:
•Before Configuring VPIM Contact Creation Settings
•Using Cisco Unity Connection Administration to Configure VPIM Contact Creation Settings
Before Configuring VPIM Contact Creation Settings
Before configuring the VPIM location contact creation settings, consider the following:
•If you have pre-populated VPIM contacts with specific display names that should not be changed, but want to allow automatic modification of other fields in the contact record, you may choose to keep the Allow VPIM Contact Display Name Updates check box unchecked. In this case, the first name, last name, and spoken name of a contact may be modified during an automatic update. This may result in a mismatch if the spoken name is updated and the display name is not.
•When the Allow VPIM Contacts Without Recorded Voice Names check box is unchecked, new VPIM contacts will not be created for incoming messages that do not contain an Originator-Spoken-Name attachment. In addition, if automatic modification of VPIM contacts is enabled, and if the sender of an incoming message matches an existing VPIM contact, the VPIM contact will be deleted if the attachment is not present in the message.
•When the Allow VPIM Contacts Without Recorded Voice Names check box is checked, and automatic modification of VPIM contacts is enabled, if the sender of an incoming message that does not include an Originator-Spoken-Name attachment matches an existing VPIM contact, the existing recorded voice name will be deleted.
•If the phone number in an incoming message cannot be successfully mapped to an extension by using the option selected for the Map VPIM Contact Extensions To field, a VPIM contact will not be created for the sender.
Using Cisco Unity Connection Administration to Configure VPIM Contact Creation Settings
After you create a delivery location, you can configure the settings that control automatic directory updates for that specific delivery location by using Cisco Unity Connection Administration.
To Configure VPIM Contact Creation Settings by Using Cisco Unity Connection Administration
Step 1 In Cisco Unity Connection Administration, expand System Settings, then click VPIM Locations.
Step 2 On the Search VPIM Locations page, click the name of the VPIM location for which you want to configure contact creation settings.
Step 3 On the Edit VPIM Location page, on the Edit menu, click Contact Creation.
Step 4 On the Contact Creation page, enter the following settings for the contacts at this VPIM location, and click Save.
Table 27-6 Settings for the Contact Creation Page
Field
|
Setting
|
Automatically Create VPIM Contacts
|
Check this check box to enable automatic creation of a VPIM contact record for this location when a VPIM message arrives and the sender does not already have a corresponding VPIM contact record.
|
Automatically Modify VPIM Contact
|
Click one of the following to apply to VPIM contacts for this location:
•No Automatic Update of Contacts—The VPIM contact record will not be updated with the sender information in a VPIM message when an incoming message has changed sender information.
•Only When the Text Name Changes—The VPIM contact record is updated only when the text name received in the VPIM message does not match the name of the VPIM contact.
•With Each VPIM message—Every incoming VPIM message from a VPIM contact at this location will result in an update to the corresponding VPIM contact record.
|
Automatically Delete VPIM Contact
|
Check this check box to enable automatic deletion of a VPIM contact for this location when a VPIM message is returned as undeliverable.
|
Allow VPIM Contact Display Name Updates
|
Check this check box to enable automatic updates to the VPIM contact display name when an incoming message from this location has a changed display name for the sender.
|
Allow VPIM Contacts Without Recorded Voice Names
|
Check this check box to enable automatic updates for this location to records for VPIM contacts that do not have a recorded voice name.
|
Mapping Text Names
|
Click one of the following options to indicate how text names in incoming messages from this location will be mapped to the display names for automatically created VPIM contact records:
•Directly to VPIM Contact Display Names—The display names for VPIM contacts will match the corresponding text names.
•Custom—Enter the rule that defines how test names will be mapped to display names for VPIM contacts. You can enter the tokens <FN>, <LN>, or <TN> (respectively first name, last name, or text name) in any combination, along with any additional text. Always precede <FN>, <LN>, or <TN> 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.
|
Map VPIM Contact Extensions To
|
Click one of the following settings to indicate how the phone number on incoming messages from this location will be mapped to the extension for automatically created VPIM contact records:
•Phone Number—Extensions will be the same as the phone numbers that are parsed from incoming VPIM messages.
•Phone Number - Remote Phone Prefix—Extensions will be formed by removing the remote phone prefix from the beginning of the phone numbers.
•Location Dial ID + Phone Number—Extensions will be formed by adding the location Dial ID in front of the phone numbers.
•Location Dial ID + Phone Number - Remote Phone Prefix—Extensions will be formed by removing the remote phone prefix from the beginning of the phone number, and adding the location Dial ID in front of the resulting number.
|
Step 5 On the Location menu, click Search VPIM Locations.
Step 6 Repeat Step 2 through Step 5 for all remaining VPIM locations.
Adding Alternate Names for Each VPIM Location
You can create an alternate name for a VPIM location.
To Add an Alternate Name for VPIM Locations
Step 1 In Cisco Unity Connection Administration, expand System Settings, then click VPIM Locations.
Step 2 On the Search VPIM Locations page, click the name of the VPIM location for which you want to add an alternate name.
Step 3 On the Edit VPIM Location page, on the Edit menu, click Alternate Names.
Step 4 On the Edit Alternate Names page, click Add New.
Step 5 In the Display Name field, enter the alternate name that you want for the VPIM location and click Save.
Step 6 On the Location menu, click Search VPIM Locations.
Step 7 Repeat Step 2 through Step 6 for all remaining VPIM locations for which you want to add alternate names.
Gathering Information About Cisco Unity Connection to Configure Another Voice Messaging System for VPIM
Configuring another voice messaging system to exchange VPIM messages with Connection may require the following information:
•The server name and domain name of the SMTP server that handles incoming SMTP messages.
•The Connection phone prefix (if any) and Remote phone prefix (if any) entered on the corresponding VPIM location page.
•The mailbox number range for Connection users.
Incoming VPIM messages must be routed to the SMTP server. When defining a location for Connection on the remote voice messaging system, use the domain name that you entered for the SMTP server.
Connection expects incoming VPIM messages to be formatted as follows:
<ConnectionPhonePrefix+ConnectionUserExtension@PrimaryLocationSMTPDomainName>
These specific properties are configured in Connection, but similar information will need to be configured in the other voice messaging system.
Deleting VPIM Contacts
To Delete VPIM Contacts
Step 1 In Cisco Unity Connection Administration, expand Contacts, then click Contacts.
Step 2 On the Search Contacts page, check the check boxes next to the VPIM contacts that you want to delete.
Step 3 Click Delete Selected.
Step 4 When prompted to confirm the deletion, click OK.
VPIM Concepts
The following sections explain VPIM concepts in detail:
•VPIM Messages
•VPIM Addresses
•Message Addressing Options
•Messaging Similarities and Limitations
•Audio Format Considerations
VPIM Messages
VPIM messages are made up of one or more MIME-encoded parts. The VPIM specification allows for optional MIME parts for spoken name and for forwarded and text messages. Connection does not, however, support sending or receiving a vCard (an electronic business card that includes phone number, text name, and e-mail address). If a vCard is attached to an outgoing or incoming message, Connection removes the vCard data. In addition, any attachments to messages other than the voice message and embedded messages are removed from outgoing and incoming messages.
Connection allows you to specify whether the voice name of the sender will be sent with outgoing messages. If incoming messages include a voice name, it is played as part of the message. Connection can also be configured to update the directory with information from the header from incoming messages.
Figure 27-1 shows a sample VPIM message. Only a portion of the MIME encoding of the spoken name and voice message parts are shown because they are very long.
Figure 27-1 Sample VPIM Message
VPIM Addresses
A VPIM address is in the same format as a typical SMTP e-mail address: localpart@hostpart. The right-hand side of the address is the domain name of the system on the TCP/IP network that handles messages. The left-hand side of the address is a unique identifier for the user. Typically, the left-hand side is the user mailbox number or the mailbox number with a prefix.
For example, an outgoing VPIM message to Terry Campbell with the remote mailbox ID 2233 could be addressed:
To: 2233@remotevoicemailsystem.com
If it is necessary to accommodate the numbering plan for your organization, the address can also contain a prefix:
To: 8882233@remotevoicemailsystem.com
VPIM addresses are created by Connection when sending VPIM messages; they are not entered by users when addressing messages.
Message Addressing Options
Connection provides the following ways to address messages to individuals on a remote voice messaging system:
•Connection directory—When the List in Directory check box is checked for VPIM contacts, the Connection directory has the names and extensions for the VPIM contacts. Users can address messages to VPIM contacts the same way that they address messages to regular Connection users—by extension or by spelling the name of the recipient. Note that spoken name confirmation is available when a recorded name exists for the VPIM contact.
•Distribution lists—Users can address messages to a private or system distribution list that includes VPIM contacts so the VPIM contact will receive the message.
Messaging Similarities and Limitations
For the most part, messaging between Connection users and individuals on a remote voice messaging system is the same as messaging among Connection users. For example:
•Messages marked urgent when they are sent are marked urgent when they are retrieved by the recipient.
•Messages marked private when they are sent are marked private when they are retrieved by the recipient.
•Users can send messages to Connection distribution lists that include VPIM contacts.
Note the following exceptions:
•Requests for read receipts and delivery receipts are both returned as delivery receipts.
•Messages sent to Connection distribution lists from users on the remote voice messaging system are not delivered, and an NDR is returned to the sender. Incoming VPIM messages to Connection are delivered to user mailboxes only, and cannot be delivered to public distribution lists.
•Incoming messages must be addressed to the primary extension of the user; messages addressed to an alternate extension will not be delivered.
Audio Format Considerations
The Audio Format Conversion settings for the VPIM location (on the System Settings > Edit VPIM Location page in Cisco Unity Connection Administration) allow you to control the audio format of outgoing and incoming VPIM messages, as follows:
•Incoming Messages—You can set whether incoming VPIM messages are stored in the format in which they were sent, or converted to the audio format that Connection uses for recording messages.
•Outbound Messages—You can set whether outbound VPIM messages are sent in the format in which they were recorded, or converted to the G.726 codec.
To make decisions about these settings, consider the following:
•The audio format that the local Connection server uses for recording and playing voice messages.
•The audio format in which the remote voice messaging system can send and receive VPIM messages. Some voice messaging systems support only the G.726 format for VPIM messages, but you must consult the documentation of the remote voice messaging server to be sure.
•The network bandwidth.
We recommend that incoming VPIM messages be stored in the same audio format that the local Connection server uses for recording and playing messages.
Feedback
