Integriti GSM Communications Task

Version 1

Inner Range Recommendation

INNER RANGE recommends that all Inner Range systems be installed & maintained by FACTORY CERTIFIED TECHNICIANS.

For a list of Accredited Dealers in your area refer to the Inner Range Website: http://www.innerrange.com

Table of Contents

Description of the Integriti GSM Communications Task

The Integriti Controller's GSM Communications Task is used to communicate reportable events to a Central Monitoring Station, to send reportable events via SMS message and/or to receive SMS control messages.

Normal Alarm Reporting

When the "Enable Alarms" option of the GSM Communications Task is set, the GSM Communications Task waits for an event to transfer to the FE3000. When an event is detected the GSM Communications Task sends the event to the FE3000 to be reported to the Central Monitoring Station. The FE3000 will attempt to report the event via one of its many communication paths. The FE3000 reports back to the GSM Communications Task whether or not it was successful with its attempt to communicate the event(s). If the FE3000 could not successfully communicate the event(s) to the Central Monitoring Station then the GSM Communications Task can pass the event(s) to its programmed Backup Communications Task.

SMS Alarm Reporting

When the "Enable SMS" option of the GSM Communications Task is set, the GSM Communications Task waits for an event to transfer to the FE3000 as an SMS. When an event is detected the GSM Communications Task sends the event to the FE3000 to be sent as an SMS to the Telephone Number, or Telephone Number List, that is defined in “SMS number 1” (if "SMS number 1" is not qualified then the GSM Communications Task will attempt to use “SMS number 2"). The FE3000 will attempt to send the SMS message(s) and will reports back to the GSM Communications Task whether or not it was successful. If the FE3000 could not successfully send the SMS message(s) no further action is taken by the GSM Communications Task. When there is an SMS message pending to be sent, if the FE3000 takes longer than 30 seconds to be free to accept the next SMS message then the pending SMS message will be discarded.

SMS Control

The GSM Communications Task can be used to turn Areas on/off, turn Auxiliaries on/off and to trigger Named Actions via SMS control commands. Inputs can also be Isolated or de-Isolated. The GSM Communications Task can be configured to authenticate an SMS command either via a Telephone Number or via a User PIN.

If only the Telephone Number is used as the authentication method then there is no restrictions applied to the SMS control command. This means that as long as the command syntax is correct the SMS control action is carried out (E.g. any Area can be turned ON/OFF or any Input can be Isolated/de-Isolated etc.).

If a User PIN is provided as part of the SMS control command then the User's permissions governs the level of control that the SMS control command can execute. If the User does not have access to control the entity type in their Remote Access Permissions of their Menu Group, then they cannot control the entity. Some SMS control commands also have additional checks, for example:

When a valid SMS control command has been received and processed, an SMS reply will be sent back to the original SMS phone number. In most cases the SMS reply will be the review associated with the action that was performed, however in some exception circumstances an error reply may be sent or even no reply will be sent. An example of these exception circumstance are things like SMS Alarms are being sent instead of SMS replies (SMS Alarms are a higher priority than SMS replies), the review for the executed action was not detected or the FE3000 was full and unable to accept additional SMS messages. As with SMS Alarms, if there is an SMS reply message pending to be sent and the FE3000 takes longer than 30 seconds to be free, then the pending SMS reply message will be discarded.

SMS Control Command Syntax and Examples

Command Syntax Command Description Example Example Description
[<PIN>] ? Display SMS Help 01? 01=User PIN, ?=Display the SMS Help message
[<PIN>] A <Area ID> <N/F> Control an Area using its ID 01A001N 01=User PIN, A=Area Control, 001=Area #001, N=Turn ON
[<PIN>] A <Area Name> <N/F> Control an Area using its Name AHouseF A=Area Control, House=Area Name, N=Turn OFF
[<PIN>] A <Area ID> L List 4 Area Names starting at Area ID A1L A=Area Control, 1=Area #1, L=List 4 Area Names starting at 1
[<PIN>] A <Area Name> L List 4 Area Names starting at Area Name AHouseL A=Area Control, 1=Area #1, L=List 4 Area Names starting at House
[<PIN>] A? Display Area Help A? A=Area Control, ?=Display the Area Help message
[<PIN>] I <Input Address> <I/D> Isolate an Input using its ID 01IC01:Z05I 01=User PIN, I=Isolate Control, C01:Z05=Input C01:Z05, I=Isolate
[<PIN>] I <Input Name> <I/D> Isolate an Input using its Name IEntry PIRD I=Isolate Control, Entry PIR=Input (E.g. C01:Z05), D=Delsolate
[<PIN>] I <Input ID> <L> List 4 Input Names starting at Input ID IC01:205L I=Isolate Control, C01:Z05=Input C01:Z05, L=List 4 Input Names starting at C01:Z05
[<PIN>] I <Input Name> <L> List 4 Input Names starting at Input Name IEntry PIRL I=Isolate Control, Entry PIR=Input (E.g. C01:Z05), L=List 4 Input Names starting at Entry PIR
[<PIN>] I? Display Isolate Help I? I=Isolate Control, ?=Display the Isolate Help message
[<PIN>] P <Named Action Address> <N/F> Trigger a Named Action using its ID 01P001N 01=User PIN, P=Named Action Control, 001=Named Action #001, N=Trigger ON
[<PIN>] P <Named Action Name> <N/F> Trigger a Named Action using its Name PUnlockF P=Named Action Control, Unlock=Named Action Name, F=Trigger OFF
[<PIN>] P <Named Action ID> <L> List 4 Named Actions starting at Named Action ID P1L P=Named Action Control, 1=Named Action #1, L=List 4 Named Action Names starting at 1
[<PIN>] P <Named Action Name> <L> List 4 Named Actions starting at Named Action Name PUnlockL P=Named Action Control, Unlock=Named Action Name, L=List 4 Named Action Names starting at Unlock
[<PIN>] P? Display Named Action Help P? P=Named Action Control, ?=Display the Named Action Help message
[<PIN>] X <AUX Address> <N/F> Control an Auxiliary using its ID 01XC01:X07N 01=User PIN, X=Auxiliary Control, C01:X07=Auxiliary C01:X07, N=ON
[<PIN>] X <AUX Name> <N/F> Control an Auxiliary using its Name XStrobeF X=Auxiliary Control, Strobe=Auxiliary (E.g. C01:X07), F=OFF
[<PIN>] X <AUX ID> List 4 Auxiliary Names starting at Auxiliary ID XC01:X07L X=Auxiliary Control, C01:X07=Auxiliary C01:X07, L=List 4 Auxiliary Names starting at C01:X07
[<PIN>] X <AUX Name> <L> List 4 Auxiliary Names starting at Auxiliary Name XStrobel X=Auxiliary Control, Strobe=Auxiliary (E.g. C01:X07), L=List 4 Auxiliary Names starting at Strobe
[<PIN>] X? Display Auxiliary Help X? X=Auxiliary Control, ?=Display the Auxiliary Help message
[<PIN>] R Reset the SMS buffer to the latest review 01R 01=User PIN, R=Reset SMS command
[<PIN>] R? Display Reset SMS Help R? R=Reset SMS, ?=Display the Reset SMS Help message

Interface between Integriti and an FE3000

The connection between the Integriti Controller and the FE3000 is made via a serial interface, by connecting one of the Integriti Controller's UARTs to the FE3000. FE3000s are capable of communicating at 600, 1200 or 2400 BAUD. The recommended port configuration for communications between the Integriti Controller and an FE3000 is 1200,N,8,1 (as per Figure 1: GSM Communications Task configuration from the Integriti System Designer).

Figure 1: GSM Communications Task configuration from the Integriti System Designer.

Notes for the GSM Communications Task

PDF preview unavailable. Download the PDF instead.

Programming Manual-Integriti Comms Tasks GSM Microsoft Word 2010 Microsoft Word 2010

Related Documents

Preview Integriti UniBus 2-Door Expander Installation Manual
Comprehensive installation manual for the Integriti UniBus 2-Door Expander (P/N: 996535PCB&K) by Inner Range, detailing specifications, wiring, and setup for access control systems.
Preview Integriti Entra ID Integration Manual
This manual provides comprehensive guidance on integrating Inner Range's Integriti system with Microsoft Entra ID (formerly Azure Active Directory) for seamless user synchronization and identity management.