4.22. SCENARIOS AND EXAMPLES (SCRIPTS)
as we would like the Phone Number to have TAIP-console and voice
access.
Create a new
Destination Address
For now we only have
DA 4
that associates only
DP 00
. We need to
create another
DA
that includes our Tracking Server (
DP 00
) and the
recently created Phone Number (
DP 10
). For no particular reason we
choose
DA 5
to do the job:
>
SDA5;P00,P10
<
Now
Destination Address
5
holds
Destination Points
00
and
10
. We
can point any event to
DA 5
making any report generated by the
event to be routed to our Tracking Server an to the Telephone Num-
ber
912345678
at the same time.
Change the button-press report event definition
Our previous button-press report event was defined on event
05
. We
are going to use the same definition but as you will notice we are
going to change on the event’s
DA
from
4
to
5
:
>
SED05NV5;P00+
<
Now any time the button is pressed, (
P00+
), an event report is going
to be generated to both the Tracking Server and the Phone Number
912345678
.
Create a SMS custom message
The only thing left to do is create a user-defined text to be sent to
the Phone-Number-type destination whenever event
03
occurs. For
this we use the
XATM
message which allows to create up to 100 user-
messages, one for each event. Refer to the
XATM
message on the TAIP
reference for more information. Let’s use the text
Button pressed!
:
>
SXATM05Button pressed!
<
The underlined
05
indicates that the message we are defining is for
event
05
.
Check the reported message
The following text message should be arriving to the Phone Number
912345678
any time the button is pressed:
e-track:EXAMPLE
Event:05
Button pressed!
101
