Calling Party Category

Calling Party Category

The CallingPartyCategory operation selects an exit according to the caller category. The caller category is determined by mapping protocol-specific netwok information to categories within platform configuration.

For INAP and CAMEL networks, the mapping uses InitialDP callingPartysCategory information element values. For example, calls with callingPartysCategory value 15 are generally recognised as payphone calls.

For SIP networks, the mapping uses calling party number prefixes. For example, all New Zealand telephone numbers that start with 022 are generally recognised as mobile telephone numbers.

The CallingPartyCategory operation must have at least one exit. The CallingPartyCategory operation is only useful when it has more than one exit, although this is not enforced by the operation definition.

Config Parameters

The CallingPartyCategory operation config attributes are as follows.

Config Rules

The attributes for each CallingPartyCategory operation rules Object are as follows.

Note that if the caller category matches more than one rule, the following priority order will apply: international, landline, mobile, payphone, default.

Exit index 0 will be followed if the caller category does not match any of the rules.

Example Operation

Here is an example CallingPartyCategory operation in JSON representation.

    {
        "id": 5,
        "type": "CallingPartyCategory",
        "config": {
            "rules": [
                { "type": "payphone", "exit_idx": 1 },
            ]
        },
        "exits": [ 4, 17 ]
    }

In this example, calls from payphones will proceed via exit index 1 to the operation with ID 17, while all other calls will proceed via exit index 0 to the operation with ID 4.

Exits

The first exit is always the “Default” exit.