Cisco Systems 5.x manual Correspondence Between Locations

Chapter 8 Using VPIM for Networking with Cisco Unity Express or Other Cisco Unity Systems

Messaging Between Cisco Unity Servers in Different Directories

Correspondence Between Locations

As Figure 8-1illustrates, you create a VPIM delivery location on the local Cisco Unity server to correspond to each remote Cisco Unity Bridgehead server. Typically, the Domain Name that you enter on the delivery location matches the Domain Name for the corresponding primary location on the remote Cisco Unity server and vice versa. However, the domain names that you enter depend on your e-mail addresses/recipient policy. In addition, the Dial ID and Display Name on the local delivery location are typically the same as the Dial ID and Display Name on the remote primary location and vice versa (this is for convenience only and is not a requirement). If prefixes are needed to accommodate numbering plans and subscriber dialing habits, enter applicable prefixes on the local and/or remote delivery locations.

Figure 8-1 Correspondence Between Locations

Primary Location

Dial ID: 444

Display Name: NewYorkUnity

Domain Name: ny.cisco.com

Internet

NewYorkUnity

VPIM Delivery Location

Dial ID: 333

Display Name: NewYorkUnity

Domain Name: paris.cisco.com

Remote Phone Prefix: 333

Primary Location

Dial ID: 333

Display Name: ParisUnity

Domain Name: paris.cisco.com

ParisUnity

VPIM Delivery Location

Dial ID: 444

Display Name: ParisUnity

Domain Name: ny.cisco.com

Unity Phone Prefix: 333

104947

VPIM Subscribers Correspond to Remote Cisco Unity Subscribers

If you do not want to use blind addressing, you can create VPIM subscriber accounts on the local server that correspond to subscribers on the remote Cisco Unity server. On the remote Cisco Unity server, VPIM subscriber accounts can be created that correspond to the Cisco Unity subscribers on your local server. Figure 8-2illustrates the relationship of VPIM subscribers to remote Cisco Unity subscribers.

By creating VPIM subscribers, you manually duplicate the subscriber directory of the remote

Cisco Unity server on the local server, and vice versa. Such a setup provides the benefits listed in the “Subscriber Experience with VPIM Subscribers” section on page 7-45.

In addition to manually creating VPIM subscribers, you can configure Cisco Unity to automatically update the VPIM subscriber directory based on information contained in VPIM messages that are received from the remote Cisco Unity server. You configure the settings for automatic directory updates on the delivery location that corresponds to the remote Cisco Unity server. If the remote Cisco Unity server is configured to include the vCard of the sender in outgoing messages, you can specify that the vCard be used as the source of information for the directory update. Otherwise, the message headers can be used instead. By default, no automatic directory updates will occur. For further information about enabling automatic updates and configuring these settings, see the “Customizing VPIM Subscriber Directory Update Settings” section on page 7-28.

Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)

8-2 OL-13844-01