Broadcasts between CallPilot and other messaging servers

Network broadcasts are not supported on all voice messaging systems. The type of network broadcast supported between two specific servers in the messaging network is the lowest common denominator of what both servers support. For example, only network broadcast is supported between CallPilot 2.0 and Meridian Mail 11.

This topic identifies the types of

Broadcast support on your CallPilot server

If Networking is installed on your CallPilot server, then users can send and receive both network and location broadcast messages, provided that the broadcast capabilities are granted at both the user mailbox and CallPilot server level. (See User broadcast abilities and Controlling broadcasts to and from your server.)

If only Network Message Service is installed on your CallPilot server, then users can send only local and location broadcast messages, provided that the broadcast capabilities are granted at both the user mailbox and CallPilot server level. Location broadcast messages can be sent to any prime or satellite location in the local NMS network.
Back to top

Broadcast support for various types of messaging systems

Messaging
system type

Network
broadcast

Location
broadcast

CallPilot 2.0

yes

yes

CallPilot 1.0x

no

no

Meridian Mail 12

Meridian Mail 13

yes

yes

Meridian Mail 11

yes

no

Meridian Mail 11and later with
Meridian Mail Net Gateway

yes

no

Meridian Mail 10 and earlier

no

no

Norstar VoiceMail

no

no

Business Communications
Manager 2.5

no

no

Voice messaging systems
from other vendors

no

no

Back to top

Multimedia support between systems

All types of broadcast messages can contain voice, fax, or text. However, to successfully arrive at their destinations, the following conditions apply:

Example 1: VPIM Networking

VPIM Networking supports the transmission of voice, fax, and text messages. Therefore, broadcast messages can contain voice, fax, or text. However, if the receiving server does not support the content, a non-delivery notification may be returned to the sender.

Example 2: Enterprise Networking

Enterprise Networking supports the transmission of voice content only. Therefore, if a user composes a broadcast message containing fax or text, and the message is to be transmitted using the Enterprise Networking protocol, the message is rejected and the sender receives a non-delivery notification.

Example 3: AMIS Networking

AMIS Networking does not support network broadcast messages.

Back to top


Related Procedures    Overviews