8-11
Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)
OL-13844-01
Chapter 8 Using VPIM for Networking with Cisco Unity Express or Other Cisco Unity Systems
Additional Functionality
• Any members of the public distribution list that are not VPIM subscribers will receive the message
as a regular voice message rather than as a system broadcast message, and the message properties
such as start and end date will not be respected. For Cisco Unity subscribers, this also means that
the message will be delivered to the subscriber mailbox and will be included in the total mailbox
size for the subscriber. For these reasons, we do not recommend that you add non-VPIM subscribers
to the distribution list.
• Including any VPIM subscriber at a remote Cisco Unity delivery location that supports networked
system broadcast messages in the public distribution list will cause the system broadcast message
to be directed to all subscribers on all Cisco Unity servers that are digitally networked with the
remote VPIM bridgehead server. It is not possible to restrict the system broadcast message to a
particular server or set of servers on the remote network.
• For Cisco Unity Express delivery locations, a VPIM subscriber must be created specifically for each
Cisco Unity Express server. The remote mailbox number configured on the VPIM subscriber
account in Cisco Unity must match the number configured for the system broadcast mailbox on the
Cisco Unity Express server.
• Only one system broadcast message should be sent as a VPIM networked message to each remote
location. In other words, only one VPIM subscriber per remote Cisco Unity Express system or
Cisco Unity domain needs to be included in the public distribution list being used. The receiving
system will distribute the message to all local users. However, if for some reason the remote location
receives more than one copy of the same system broadcast message, only the first one will be
processed and subsequent ones received with the same message ID will be discarded.
• To include specific digitally networked Cisco Unity servers in the distribution list along with VPIM
locations, you can manually add the system broadcast mailbox of each desired server in the public
distribution list. Because the Cisco Unity Administrator does not allow you to select a subscriber for
these mailboxes, you must use Exchange tools to add the mailbox to the distribution list. The system
broadcast mailbox is named USBms_<Servername>, and is automatically created in the default
directory container for Cisco Unity during installation.
Sending Networked System Broadcast Messages
To allow one or more Cisco Unity subscriber(s) to send networked broadcast messages, you first set up
and offer the subscriber(s) access to the Cisco Unity Broadcast Message Administrator, and then create
one or more public distribution list(s) that can be used to network system broadcast messages. For
information on setting up the Cisco Unity Broadcast Message Administrator to address and send
messages to the distribution list you create, see the “Sending System Broadcast Messages” section in the
“Cisco Unity Conversation” chapter of the System Administration Guide for Cisco Unity, at
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_list.html.
Note that any subscribers who will send networked system broadcast messages must be configured such
that they are allowed to send broadcast messages to subscribers on multiple servers.
Setting up Public Distribution Lists for Addressing Networked System Broadcast Messages
To set up a public distribution list for use in sending system broadcast messages, do the following tasks.
1. Create one VPIM subscriber to represent each Cisco Unity Express server or each remote
Cisco Unity domain. Depending on the type of the remote location, do one of the following: