Digital Security Controls Ltd. 163G4005 User Manual

3. The Communicator waits for a response from the number called for a period of up to 60 seconds. If the outcome is positive,

the Communicator moves on to step 4; otherwise the call will end and step 1 will be attempted again, up to a maximum of 8
times (depending on the programmed value). After 8 attempts the call cycle will be considered complete.

4. The Communicator plays the message corresponding to the channel where the alarm is taking place, the call is considered

completed only once the message has been received, or when the 



 key is pressed (if “Call Confirmation” has been

selected, see the Communicator->Call Confirmation) on the phone receiving the message. In any case, the call is consid-
ered successful after the message has been repeated up to a maximum of 8 times (depending on the programmed value). If,
at the selection stage, several events occurred causing several different messages to be sent to the same telephone number,
these messages are reproduced (each for a maximum of 8 times, depending on the programmed value) in sequence during
the same telephone communication, thus avoiding calls being made to the same number several times. If at the end of the
call cycle, the line which caused the Communicator to be activated is still in alarm mode, the procedure described above will
not be repeated again. In fact, the line that caused a call cycle must return to standby mode before a new cycle is activated.



The Communicator is able to do:


Voice call;



Alarm event transmission over GSM voice channel;



Voice message transmission;



SMS message transmission;



Internal report event (CID/SIA);



Incoming SMS management;



Heartbeat transmission.

For all events type the priority will be programmable through SW DLS 5 console. Default configuration is shown in the table below.



If the device is transmitting an event and a different event type with higher priority occur, the device will stop the current event
transmission and push it in queue.



After event transmission with higher priority the device will try again to delivery previous message stopped.



If more events with the same priority occur simultaneously, they will pushed in queue and transmitted sequentially.



Voice dialler message has less programmable priority than event from. In case panel event have more priority, if an event
from panel occurs while the device is making a voice message transmission, the device will close the call. When the panel
takes the line (off hook detected) an ATH command will be performed. After panel transmission (on hook detected) the device
will try again to delivery previous voice message stopped (get from queue). Otherwise in case of voice dialler has the most
priority, if an event from panel occurs while the device is making a voice message transmission, the device should provide the
busy tone to the panel and continue to transmit the messages.



SMS message has less fixed priority then LI Line and Voice Dialler. If it takes the resource then it cannot be released on demand,
because the SMS sending cannot be interrupted by AT command, but it will give the resource at the SMS sending end.



Heartbeat has the least priority.

1

LI off-hook (voice call and CID/SIA digital transmission).

0 (Highest)

Yes

2

Internal report event (CID/SIA on input trigger) over Cellular Data Network. 1

Yes

3

Voice/SMS dialler message (input or internal even).

2

Yes

4

Incoming SMS command message management.

3

Yes

5

Heartbeat over Cellular Data Network.

4 (Lowest)

Yes

Table 8: Priority events management.