7-47
Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)
OL-13844-01
Chapter 7 VPIM Networking
VPIM Concepts and Definitions
Directory Update Processing That Occurs on the Cisco Unity VPIM Bridgehead Server
The CsVPIMConnector service running on the VPIM bridgehead server monitors the
UVPIM_<Servername> mailbox for directory messages. When the CsVPIMConnector service receives
a directory message indicating that a new VPIM subscriber should be created, it also checks additional
Subscriber Creation settings on the delivery location to determine:
• Which template to use when creating VPIM subscribers
• How to map the parsed text name of the VPIM subscriber to a first name, last name, and display
name
• How to map the phone number to an extension
• Whether or not VPIM subscribers with no recorded voice names are allowed
The service uses SQL Server to create or update the VPIM subscriber on the VPIM bridgehead server.
From the SQL Server database, the subscriber information is replicated to Active Directory, where a
mail-enabled contact is created.
When the CsVPIMConnector service receives a directory message indicating that an existing VPIM
subscriber should be modified, it checks to see whether the delivery location is configured to have the
subscriber information updated with every incoming VPIM message, or only on messages where the text
name has changed. The service takes the text name from the incoming message and applies the rules that
have been configured to map the text name to a display name. If the option is selected that allows updates
only when the text name has changed, the service compares this new display name to the display name
on the VPIM subscriber record to determine whether the subscriber record should be modified. If the
modification is allowed, the CsVPIMConnector service also checks to determine whether the delivery
location is configured to allow display name updates. If so, the service will modify the first and last name
fields and the recorded voice name, but will leave the display name unchanged. Otherwise, all of these
fields will be updated.
For example, you can configure a location as follows:
• Display names will be created as “Firstname Lastname - Seattle”
• Updates are allowed only when the text name changes
• Display name updates are allowed
In this circumstance, if a VPIM subscriber exists with the display name “Jessie Smith - Seattle” and an
incoming message is received from Jessie Smith, no action will be taken. If the display name for Jessie
Smith on the remote system is changed to “Jess Smith,” a modification will be triggered the next time
Cisco Unity receives an incoming message, and the first name and display name will be updated
accordingly.
In other cases, a last name may change or a given mailbox number may be reassigned to a new person,
so it is not recommended that modifications be allowed while display names updates are disallowed, as
this could result in a first and last name contradicting the display name. The rule for mapping display
names can be configured so that most desired display name conventions can be maintained when VPIM
subscribers are automatically created or modified.
When the CsVPIMConnector service receives a directory message indicating that an existing VPIM
subscriber should be deleted, it checks the reason code included in the message. If the reason code
indicates that the mailbox does not exist (SMTP error code 5.1.1), the CsVPIMConnector service will
delete the VPIM subscriber record. All associated objects and properties, including public and private
distribution list membership, will be deleted from the SQL Server database on the VPIM bridgehead
server. From the SQL Server database, the change will be replicated so that the Active Directory contact
is removed.