Differenze tra le versioni di "AdminGuide:Service:Blacklist/en"

Da Kalliope Wiki.
Jump to navigation Jump to search
(Creata pagina con "You can also reorder the blacklists within the inbound lines, so as to implement both blacklist and whitelist mechanisms.")
(Aggiornamento come da nuova versione della pagina di origine)
Riga 21: Riga 21:




1. The service can be configured in the PBX -> [[AdminGuide:GUI:Gateway&VoIPDomains/en|Gateways and VoIP domains]] -> List of blacklists page.  
The blacklist configuration can be set in the PBX -> [[AdminGuide:GUI:Gateway&VoIPDomains/en|Gateways and VoIP domains]] -> List of blacklists page.  


[[File:Listablacklist.png|centro]]
[[File:Listablacklist.png|centro]]
Riga 31: Riga 31:
[[File:Listablacklistdettaglio.png|centro]]
[[File:Listablacklistdettaglio.png|centro]]


The blacklist form contains the following fields:
I campi principali del form per la definizione della blacklist sono i seguenti:


* '''Enabled''': the enable flag for the blacklist. If this flag is disabled, the blacklist rules will not be taken into account even if the blacklist is included in one or more inbound lines.
* Abilitazione
* '''Name''': a unique name to assign to the blacklist.
* Nome
* '''Play "in progress" messages''': if enabled, this flag causes the audio file selected in the failover action in a 183 Session Progress to play.
* Trabocco
* '''Failover''': the failover action to carry out when there is a match with one of the rules of the blacklsit. The blacklists also include a "Continue to DID" action with which you can implement a "whitelist" and continue to routing towards the DIDs upon a match.
* Regole
* '''Rules''': the rules that dictate the manipulation rule logic, with caller and called number type selection and the insrtion numberings for matches. You can also add a note to each rule. These notes are purely for organizational purposes and have no effect on the matching. Each rule has an enable flag. Disabled rules will not be taken into account when the blacklist is applied.
 
[[File:Nuovablacklist.png|centro]]


Rules can be ordered, but, as with the notes, this is purely for organizational purposes. Since they all have the same failover action, the first match will trigger the action.
Rules can be ordered, but, as with the notes, this is purely for organizational purposes. Since they all have the same failover action, the first match will trigger the action.




<div class="mw-translate-fuzzy">
2. BLacklists can be associated to inbound lines in the PBX -> [[AdminGuide:GUI:Gateway&VoIPDomains/en|Gateways and VoIP domains]] -> Inbound/outbound lines page.
2. BLacklists can be associated to inbound lines in the PBX -> [[AdminGuide:GUI:Gateway&VoIPDomains/en|Gateways and VoIP domains]] -> Inbound/outbound lines page.
</div>


'''''N.B.:''''' In multi-tenant systems, this can be configured in the PBX -> Assigned line management -> Assigned lines page.
'''''N.B.:''''' In multi-tenant systems, this can be configured in the PBX -> Assigned line management -> Assigned lines page.
Riga 50: Riga 49:
In either type of system, you can assign blacklists by clikcing on "Add blacklist" and adding all necessary blacklists.
In either type of system, you can assign blacklists by clikcing on "Add blacklist" and adding all necessary blacklists.


[[File:Assegnazioneblacklist.png|centro]]


You can also disable all association of the blacklist with the inbound line so that its rules will not be applied.
You can also disable all association of the blacklist with the inbound line so that its rules will not be applied.


You can also reorder the blacklists within the inbound lines, so as to implement both blacklist and whitelist mechanisms.
You can also reorder the blacklists within the inbound lines, so as to implement both blacklist and whitelist mechanisms.

Versione delle 10:57, 17 feb 2022

Altre lingue:

Return to AdminGuide:Service


Blacklist

  • Introduced in version 4.5.17

Description

This service lets you define specific routings for inbound calls based on the calling and called numbers.

For each pair of numbers, you can choose whether or not to play an audio file (even "in progress") and define the failover action to carry out (among the routing actions available on KPBX).

The pairs of numbers to which the same routing policy should apply can be grouped in blacklists to use on different inbound lines.

The blacklists are applied to inbound calls, so in a single-tenant system they can be linked to the gateways and VoIP domains. In multi-tenant systems, the blacklists are managed by the tenant admins and are linked to the assigned lines.

You can also link a list of blacklists to each inbound line. These blacklists will be applied in a cascade after the manipulation rules and before the DID rules associated to the line.

Configuration

To configure the service, you must first define the blacklist and then associate it to an inbound line.


The blacklist configuration can be set in the PBX -> Gateways and VoIP domains -> List of blacklists page.

Listablacklist.png

N.B.: In multi-tenant systems, the service can be configured in the PBX -> Assigned line management -> List of blacklists page.

In this page you can create new blacklists by clicking on "Add blacklist" or edit and existing one.

Listablacklistdettaglio.png

I campi principali del form per la definizione della blacklist sono i seguenti:

  • Abilitazione
  • Nome
  • Trabocco
  • Regole

Rules can be ordered, but, as with the notes, this is purely for organizational purposes. Since they all have the same failover action, the first match will trigger the action.


2. BLacklists can be associated to inbound lines in the PBX -> Gateways and VoIP domains -> Inbound/outbound lines page.

N.B.: In multi-tenant systems, this can be configured in the PBX -> Assigned line management -> Assigned lines page.

In either type of system, you can assign blacklists by clikcing on "Add blacklist" and adding all necessary blacklists.


You can also disable all association of the blacklist with the inbound line so that its rules will not be applied.

You can also reorder the blacklists within the inbound lines, so as to implement both blacklist and whitelist mechanisms.