SMS Defence User Tutorial

Copyright Cellusys 2011
SMS Defence User Tutorial

User Tutorial Aims
The tutorial will teach you how to:
Create User Rules.
Use criteria correctly with User Rules.
Configure actions of User Rules.
Create and use filter lists with User Rules.
Change priorities of User Rules.
Follow est practice when adding User Rules.

User Tutorial Aims
The tutorial will teach you how to use the:
Message Type report.
Message Action report.
Top !" Cg#A report.
User Rule report.
$nline Message Chec% report.
Audit &ogs.

User Rules
A User Rule is comprised of three parts:
Basic Information is used for the users that

will e maintaining the rule set. This
information will e used to identify rules.
Criteria are used to identify messages as they

pass through the Message #rocessors.
Actions are the instruction to SMS Defence

on what to do once the rule criteria are met.

'asic (nformation
)ame: This is the name gi*en to the Rule.
Description: +hat is this Rule trying to

accomplish,
Message Type: M$ - SR(.SM - MT.

Criteria / Time
Start date-time and end date-time.
+hat days of the wee% will this rule e acti*e,
+hat hours of the day will this rule e acti*e,

Criteria / SCC# layer
Cd#A 0loal Title - Cd#A SS)
Cg#A 0loal Title - Cg#A SS)

The *alue can e a full SCC# address or a
wildcard entry 1*alue ended with a 23.

Criteria / MA# layer
M$ ForwardSM Re4
SM R#.$A 1MS(SD)3
SM R#.DA 1Ser*ice Centre Address3
MT ForwardSM Re4
SM R#.$A 1Ser*ice Centre Address3
SM R#.DA 1(MS(3

Criteria / MA# layer
SR(.SM Re4
Ser*ice Centre Address 1SMSC3
MS(SD)

Criteria / SM.T# layer
This criteria is for M$ - MT ForwardSM Re4

only.
Destination Address
Destination Address T$)
Destination Address )#(
#rotocol (D
Data Coding Scheme

Criteria / SM.T# layer
For the T#UD of the SM.T# layer:
5eyword - Rege6
7e6 86act Match
7e6 #artial Match
7e6 UD7 $nly 1not including payload3

Criteria / Throttling
Throttling is limiting the amount of messages

that are sent within a gi*en time period. (f a
message arri*es that e6ceeds the configured
limit then the action on the rule is ta%en.
Time #eriods: 9":;" secs . 9:!:9":;" mins .

9:< hours . 9day.

Actions / Message Action
A message action must e chosen for e*ery

rule that is defined.
This is the action that SMS Defence will ta%e

when the criteria of a rule is matched.
Continue: #ass: Drop: Drop.Ac%: Drop.)ac%.

Actions / Alert
$ptional action that will send an alert to a user

- group - S)M# ser*er when the rule criteria is
matched.
The se*erity of the alert must e configured.

Actions / Sample Messages
SMS Defence will store messages matching

the rule criteria.
8ither 9" or 9"" sample messages stored.
These messages are then *iewale through

the frontend.

Filter lists
Filter lists can e defined for use with criteria

on rules.
(nstead of a criteria matching on a single

*alue: a criteria can match on a list of *alues.
Filter list types: Address String: T# Address:

Su System )umer: 5eyword: 78=.

Filter lists

Rule priorities

Rule priorities
Rules can e *iewed under >Configuration? @

>User Rules? @ >Aiew Rules?
Rules are displayed in a paged tale.
Rules higher on the tale ha*e a higher

priority than rules lower on the tale.
Messages are chec%ed against rules in order

of priority 1highest to lowest3.
Rule priorities can e changed y clic%ing and

dragging rules up and down the tale.

Adding rules / 'est #ractice
Set action of newly added rule to >Continue?.
+ait for messages to pass through the

Message #rocessor.
Chec% the User Rule Report to see the

numer of matched messages.
Sample Messages as a Message Action.
Set desired action of rule once satisfied.

Message Type report
Aolume and type of messages e6amined y

the SMS Defence system during rule
processing.
Aiewed as a graph - downloaded as 86cel

document.



Message Action report
Actions ta%en y the SMS Defence system on

the messages e6amined during rule
processing.

document.



Top !" Cg#A report
(dentifies the networ% nodes 1SCC# Cg#A3

responsile for the highest le*els of message
traffic for M$ Re4: MT Re4: and SR(.SM Re4
messages.
Report in taular form.


User Rule report
Shows the *olume of messages which

matched a particular user.defined rule in the
SMS Defence system as well as the action
ta%en on those messages.

document.



$nline Message Chec% report
Aolume of messages which triggered the uilt.

in rules of the SMS Defence system as well as
the action ta%en on those messages.

document.



Audit &ogs
Trac%s changes to the SMS Defence system:
+hen the change occured.
+ho made the change.
+here was the change made from.
+hat change was made.
$nly administrators ha*e access.


SMS Defence User Tutorial

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SMS Defence User Tutorial

Uploaded by

Copyright:

Available Formats

Copyright Cellusys 2011

SMS Defence User Tutorial

The tutorial will teach you how to:

Create User Rules.

Use criteria correctly with User Rules.

Configure actions of User Rules.

Create and use filter lists with User Rules.

Change priorities of User Rules.

Follow est practice when adding User Rules.

The tutorial will teach you how to use the:

Message Type report.

Message Action report.

Top !" Cg#A report.

User Rule report.

$nline Message Chec% report.

A User Rule is comprised of three parts:

Basic Information is used for the users that

Criteria are used to identify messages as they

Actions are the instruction to SMS Defence

)ame: This is the name gi*en to the Rule.

Description: +hat is this Rule trying to

Message Type: M$ - SR(.SM - MT.

Start date-time and end date-time.

+hat days of the wee% will this rule e acti*e,

+hat hours of the day will this rule e acti*e,

Cd#A 0loal Title - Cd#A SS)

Cg#A 0loal Title - Cg#A SS)

SM R#.DA 1Ser*ice Centre Address3

SM R#.$A 1Ser*ice Centre Address3

Ser*ice Centre Address 1SMSC3

This criteria is for M$ - MT ForwardSM Re4

Destination Address T$)

Destination Address )#(

Data Coding Scheme

For the T#UD of the SM.T# layer:

7e6 86act Match

7e6 #artial Match

7e6 UD7 $nly 1not including payload3

Throttling is limiting the amount of messages

Time #eriods: 9":;" secs . 9:!:9":;" mins .

A message action must e chosen for e*ery

This is the action that SMS Defence will ta%e

Continue: #ass: Drop: Drop.Ac%: Drop.)ac%.

$ptional action that will send an alert to a user

The se*erity of the alert must e configured.

SMS Defence will store messages matching

8ither 9" or 9"" sample messages stored.

These messages are then *iewale through

Filter lists can e defined for use with criteria

(nstead of a criteria matching on a single

Filter list types: Address String: T# Address:

Rules can e *iewed under >Configuration? @

Rules are displayed in a paged tale.

Rules higher on the tale ha*e a higher

Messages are chec%ed against rules in order

Rule priorities can e changed y clic%ing and

Set action of newly added rule to >Continue?.

+ait for messages to pass through the

Chec% the User Rule Report to see the

Sample Messages as a Message Action.

Set desired action of rule once satisfied.

Aolume and type of messages e6amined y

Aiewed as a graph - downloaded as 86cel

Actions ta%en y the SMS Defence system on