User broadcast abilities

If Networking is installed on your CallPilot server, then users can send and receive both network-wide and location-specific broadcast messages, if broadcast capabilities are granted at both the user mailbox and CallPilot server level.

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

This topic describes

Mailbox capabilities

Each user must have one of the following mailbox capabilities:

Broadcast capability

Description

Local broadcast only

The user can send broadcast messages to users at

  • the local site

  • a specific switch location associated with the local site, if Network Message Service (NMS) has been installed

Local and network broadcasts

The user can send broadcast messages to users at

  • the local site (local broadcast)

  • a specific remote site (location broadcast)

  • a specific NMS location associated with either the local or a remote site, if Network Message Service has been installed (location broadcast)

  • all sites in the network (network broadcast)

Disabled

The user cannot send any type of broadcast message.

Note/Tip  If Networking is not installed, the only options available for broadcast capability are enabled and disabled. When broadcast capability is enabled on a site that does not have networking installed, local broadcast capability is provided.

Back to top

Distribution lists

Broadcast addresses cannot be added to shared distribution lists (SDLs).

Users can include broadcast addresses in their personal distribution lists (PDLs) according to their mailbox capability. If a user without broadcast capability attempts to add a broadcast address to his or her PDL, the user is informed by CallPilot that the address does not exist.

If a user wants to send a broadcast message to two or more NMS locations that are associated with a remote site, the user must address the message to each location, because each location has its own location prefix in the dialing plan. To simplify this task, the user can create a personal distribution list containing the location-specific broadcast address for each location.
Back to top

Mailbox class validation for phoneset users

For phoneset users, the mailbox class includes an option to "send messages via DTT if mailbox not found." This option determines the type of system prompt a user without broadcast capability hears, when attempting to address a broadcast message. The user may hear one of the following prompts:

For security reasons, the prompt does not state that the address is a broadcast address or that the user does not have permission to send the broadcast message. Indication that the address is a broadcast address is valuable information for a hacker.
Back to top

Mailbox class validation for desktop messaging and My CallPilot users

The desktop messaging or My CallPilot client cannot validate a user’s mailbox class while sending a message. The message must be sent from the user’s desktop to the CallPilot server before mailbox class validation can occur. If CallPilot determines that the user is not allowed to send the broadcast message, the user receives a non-delivery notification (NDN).

For security reasons, the NDN states that the address was not found. It does not state that the user did not have permission to send the broadcast message, or suggest that the address is a broadcast address. Indication that the address is a broadcast address is valuable information for a hacker.
Back to top

SMTP authentication

If SMTP authentication is used by the CallPilot server, then to send a location-specific or network-wide broadcast message, a desktop messaging or My CallPilot user must have the appropriate mailbox capability and be successfully SMTP-authenticated when attempting to send the message. If SMTP authentication fails while sending the message, the user receives an error message.

Back to top


Related Procedure    Overviews