Use the following guidelines to determine when you should disable broadcast messages between the local and one or more remote servers:
|
Disable broadcast messages |
When |
|
to the local server |
you observe a security breach, such as a hacker attempting to send messages to the local server. When you disable the receipt of broadcast messages on the local server, you can quickly and temporarily turn off broadcasts without modifying other CallPilot settings. You do not want to receive broadcast messages from remote servers. |
|
from the local server |
all users should not be allowed to send broadcast messages to other sites. Example A small sales office may not be permitted to send network broadcast messages, whereas the corporate head office site can send them. |
|
to a remote server |
the remote server does not support network and location broadcasts, or the content in the broadcast message. For more details, see Broadcasts between CallPilot and other messaging servers. The remote server does not want to receive broadcast messages from the local server. |
|
from a remote server |
you observe a security breach, such as a hacker attempting to send messages to the local server while pretending to be at the remote server. When you disable the receipt of broadcast messages from a remote server on the local server, you can quickly and temporarily turn off broadcasts from the remote server without modifying other CallPilot settings. You do not want to receive broadcast messages from the remote server. |
Another
reason to disable broadcast messages is when you want to prevent high
usage of network and CallPilot resources (network traffic, channel usage,
and CPU resource usage).