SPAM Detection

What is a nuisance in email for many years recently has become a problem also for telephone system: Unwanted calls. Such calls do not In order to address the problem, the PBX offers several mechanisms depending on the type of call. Before taking any action, the PBX needs to determine if a call is a suspected SPAM call. For that the PBX has the following rules:

• Anonymous calls are always considered SPAM calls;
• Internal calls from another extension are never considered SPAM calls (even though sometimes it could make sense);
• For tagging calls that have a caller-ID there are several methods: You can use TrueCNAM or Tellows as external SPAM provider or you can use the address book to mark a specific caller-ID for blocking.

For calls directly to an extension, the PBX offers the following options:

• No special treatment means that the call is processed normally.
• Reject call means that the call gets outright rejected.
• Send to mailbox sends the call to the mailbox.
• Pretend to be busy applies the rules for a busy extension, which could for example trigger redirection on busy.
• Ask for name triggers the call screening process where the caller first needs to leave the name. This name will be read out to the extension before that user can make a decision on how to proceed.
• You can also select that the screening process should be performed for all calls, even if they are not considered SPAM.

For calls to the ACD and to the hunt group you can specify a destination where calls should be redirected. This destination can be another ACD or hunt group, a mailbox, an auto attendant or anything else.