4.15.
BATTERY
MONITORING
call.
Another approach can to accept a voice call is to turn off the caller-id
restriction:
>
SXAVI0
<
Now,
e-track
TM
will take calls from any number. This is not rec-
ommended as voice calls can delay GPRS communications.
A voice call is hung up by pressing the button.
To have the unit generate a call, an event-based configuration must
be done. For example, to have the unit call a pre-set number when-
ever the button is pressed twice, define the number on a phone-type
destination:
>
SXADP11103051234567
<
Create a silent event that triggers with the double-click-button-press
signal (P01) and has the voice-call user-action :
>
SED00SV0;P01+;ACT=SXAVC11
<
4.15
Battery
monitoring
To monitor the internal battery refer to the
XABS
message.
To generate events according to charge level changes use the battery
signals (
Bxx
) and their definition with the
XAGB
message.
4.16
Using a TCP/UDP keep-alive
Refer to the
XAKA
message.
4.17
IMEI as ID
e-track
TM
can be programmed to use its International Mobile Equip-
ment Identity (IMEI) as ID instead of a user-set value. This is useful
for managing units without worrying of duplicate or changed IDs. It
also eases the programming task as this number is already stored on
every unit.
To instruct the unit to use its IMEI as ID instead of the ID set by the
user with the
ID
command, use the
XAID
command in the following
way:
>
SXAID1
<
89