7-38
Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)
OL-13844-01
Chapter 7 VPIM Networking
VPIM Concepts and Definitions
Figure 7-2 EXVPIM Networking Enables Messaging Between Cisco Unity Servers in Different
Directories
The VPIM specification defines the format of messages and message addresses, and how messages are
exchanged between mail servers. VPIM does not specify how the mail servers interact with client
applications, or how they interface with end users. This allows many different kinds of existing systems
to support VPIM. For more information about VPIM, refer to the Open Group VPIM website.
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, fax, and text messages. VPIM messages can
also include a vCard, an electronic business card that includes phone number, text name, and e-mail
address. Cisco Unity allows you to specify whether the voice name and vCard of the sender will be sent
with outgoing messages. If incoming messages include a voice name, it is played as part of the message.
If a vCard is attached to an incoming message, the recipient can look at the vCard data in Cisco Unity
ViewMail for Microsoft Outlook. Cisco Unity can also be configured to update the directory with
information from the header or vCard data from incoming messages. For more information, see the
“Automatic VPIM Subscriber Directory Updates” section on page 7-46.
VPIM fax encoding is based on the TIFF-F specification, and the vCard format is based on the Internet
adaptation of the Versit vCard specification.
Figure 7-3 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.
AD Forest 1 AD Forest 2
104946
Local
Cisco Unity
Internet
Remote
Cisco Unity