Cisco Systems 5.x manual Subscriber Addressing Considerations with Automatic Updates

Chapter 7 VPIM Networking

VPIM Concepts and Definitions

Subscriber Addressing Considerations with Automatic Updates

The information contained in a VPIM subscriber account can be used to aid subscribers in addressing messages to remote mailboxes (by providing spell-by-name and spoken name confirmation, for example). However, note that regardless of whether blind addressing or VPIM subscriber information is used by the sender to indicate the desired recipient of a VPIM message, ultimately the message is addressed and sent to a numerical mailbox ID on the remote system. As such, there is no mechanism for confirmation that the name information that the local subscriber uses to address an outgoing message matches the actual current owner of the remote mailbox.

Even with automatic updates in place, situations may arise where a subscriber believes he or she is sending a message to one person at a remote site, but the mailbox has changed hands since the VPIM subscriber account was created, and the new owner of the mailbox actually receives the message. Because of the usage-based nature of the updates, if no VPIM message has been received from the new owner of the remote mailbox before a local subscriber attempts to address to it, the subscriber will encounter the outdated name information belonging to the original mailbox owner (including the spoken name of the original owner), with no indication that the mailbox has changed hands.

Another situation may arise in which two VPIM subscriber accounts exist for the same person on the remote system. In the case where a subscriber on a remote VPIM system changes mailbox numbers, and a VPIM subscriber account exists for that sender on Cisco Unity, the existing account will not be updated to change the mailbox number. Instead, when a Cisco Unity subscriber addresses a message to the VPIM subscriber with the outdated mailbox number, if an NDR is received from the remote system indicating that the mailbox no longer exists, the original VPIM subscriber account will be deleted. Then, at whatever point the remote subscriber sends a message to a Cisco Unity subscriber, a new VPIM subscriber account is created for the remote subscriber. Note that these two events can happen in either order; if the remote subscriber sends a message before the local subscriber attempts to send an outgoing message to the outdated mailbox number, VPIM subscriber accounts will exist for the remote subscriber with both the old and new mailbox numbers. A local subscriber who attempts to address a message to that remote subscriber by using spell-by-name will hear both matches at this point, with different extensions. The outdated VPIM subscriber account will not be deleted unless a subscriber addresses a message to it and receives an NDR.

If the events occur in the opposite order—if a subscriber sends a message to a VPIM subscriber that results in an NDR and the deletion of the VPIM subscriber account before an incoming message is received from the new mailbox number of the remote subscriber—the sender will receive the NDR but will not have updated VPIM subscriber information to use in readdressing the message. In this case, the sender would need to use blind addressing to address further messages to the recipient, until an incoming message is received from the recipient, which will result in the creation of a new VPIM subscriber account.

CsVPIMConnector Logging

Both micro and macro traces are available for the CsVPIMConnector service. If detailed logging is required for troubleshooting purposes, these traces can be enabled and collected using the Cisco Unity Diagnostic tool (UDT). Otherwise, the CsVPIMConnector logs summary information by default for each directory message that it processes. This information is logged to a data file named data_CsVPIMConnector_<date>_<time>.txt, in the Cisco Unity trace logs directory. The default location of the trace logs is the CommServer\Logs directory.

The data is written to the file in comma-separated format. Table 7-2 describes the fields in the order that they are written to the data file.

	Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)
7-50	OL-13844-01