ADVANCED antispoofing



Abstract

Antispoofing advanced offers a dynamic approach for filtering incoming calls.

To be effective, this module requires information about the subscriber_Id, the last known entry point (gateway, route, PCV-orig) and the PAI number. The TELCO should insert this information in the CDRs generated for katia.

Operator should provide an unique subscriber_Id without exposing any confidential information for the real subscriber


Call blocking reason

SFSIF


CSV description

Example

antispoofing_advanced.txt is a five columns csv file

TARGET, KEYWORD, ORIGIN, FROM, PAI all,reject,orig.A,0041*,0041*

Fields

#

name

VALUES

description

mandatory

#

name

VALUES

description

mandatory

1

TARGET

 

Defines the scope of the rule

YES

 

 

  • all

  • all subscribers

 

 

 

  • subscriber_Id

  • valid for a specific subscriber

 

2

KEYWORD

 

Action to take if the rule matches.

YES

 

 

  • protect

 

 

 

  • allow

 

 

 

  • reject

  • reject the call

 

 

 

  • anonymize

  • experimental

    • remove the FROM

    • accept the call

    • all other check modules are skipped

 

3

ORIGIN

 

Define if the rule applies to all ORIGIN or a specific ORIGIN

YES

 

 

  • string

  • exact match

 

 

 

  • all

  • all ORIGIN

 

4

FROM

 

How the match is done

YES

 

 

  • string

  • exact match

 

 

 

  • string*

  • If FROM ends with *FROM is considered as a PREFIX and can match all incoming FROM starting with the PREFIX.

 

 

 

  • all

  • all FROM

 

 

 

  • self

  • Subscriber’s CLIP

    Used in the context for rules with a specific subscriber_id.

    Before the import, self is replaced by the subscriber’s clip.

    When the rule is processed it will check if the subscriber clip matches the incoming FROM

 

5

PAI

 

if not empty the rule should also matches the PAI

NO

 

 

  • string

  • exact match

 

 

 

  • string*

  • If PAI ends with *PAI is considered as a PREFIX and can match all incoming PAI starting with the PREFIX.

 

 

 

  • all

  • all PAI

 

 

 

  • self

  • Subscriber’s CLIP

    Used in the context for rules with a specific subscriber_id.

    Before the import, self is replaced by the subscriber’s clip.

    When the rule is processed it will check if the subscriber clip matches the incoming PAI

 

the wildcard * should never be used alone

In this situation the rule is invalid and not processed.

Processing order

  1. specific subscriber

    1. protect

    2. allow

    3. reject

    4. anonymize

  2. all subscribers

    1. protect

    2. allow

    3. reject

    4. anonymize


Rules examples

Example 1

subscriber.b,reject,orig.B,004179*,all # reject all mobile number from orig.B subscriber.b,allow,orig.B,004179*,0041* # allow mobile numbers from orig.B if they starts with a Swiss PAI

Example 2

subscriber.c,reject,all,all,all # subscriber.c rejects all calls subscriber.c,allow,orig.D,004179*,0041* # subscriber.c allows 004179* numbers from orig.D AND # with a PAI starting with 0041*

Example 3

Example 4

Example 5

Example 6

Example 7

Example 8

Example 9

Done !