GENERAL antispoofing
- Editor
Abstract
Antispoofing offers a dynamic approach for filtering incoming calls.
To be effective, Antispoofing requires information about the last known entry point (gateway, route, PCV-orig). The TELCO should insert this information in the CDRs generated for katia.
Call blocking reason
SFPCV
Rule description
Sample rule
antispoofing.txt is a CSV file containing 3 columns.
reject,greyroute.test,0041*Fields description
# | name | description | mandatory |
|---|---|---|---|
1 | KEYWORD | Action to take if the rule matches. | YES |
2 | ORIGIN | Define if the rule apply to all ORIGIN or a specific ORIGIN. | YES |
3 | NUMBER | The rule should match the A_NUMBER. The * is a wildcard. If NUMBER ends with a * → NUMBER is considered as a PREFIX and can match all A_NUMBER starting with the same PREFIX. | YES |
the wildcard * should never be used alone
In this situation the rule is invalid and not processed.
Fields values
KEYWORD
VALUES | DESCRIPTION | PROCESS | MANDATORY |
|---|---|---|---|
allow | Number should not be blocked by the antispoofing check. |
| YES |
reject |
|
| YES |
processing order
allow
reject
ORIGIN
VALUES | DESCRIPTION |
|---|---|
ALL | Rule is valid for ALL ORIGIN. |
NULL | Rule is valid for an EMPTY or NULL ORIGIN. |
[ORIGINS_PROVIDED_BY_TELCO] | ORIGIN are detected by processing the CDRs provided by the TELCO. If the field ORIGIN is missing antispoofing.txt will only contain rules for ALL. |
NUMBER
VALUES | DESCRIPTION |
|---|---|
| processed as a NUMBER |
| processed as a PREFIX |