Skip to main content

Control a GSM Device with SMS

For installations where Device-side Internet connectivity is unavailable or unreliable, an eligible product can use a GSM module and AirNgin SMS transport.

How it works​

  1. The user issues a command in the AirNgin application.
  2. AirNgin receives the command through the normal cloud path.
  3. The platform sends an SMS to the target Device when the SMS capability is selected/required.
  4. The Device validates and executes the SMS command.
  5. The Device can send its response/state back through SMS.
  6. AirNgin analyzes the response and updates the logical Device state.

When both MQTT and SMS are supported, MQTT remains the normal Internet path. A command received through SMS should preferably report its corresponding response through the SMS path, while MQTT-originated commands preferably report through MQTT. This is routing preference, not a bypass of AirNgin authorization/security rules.

Current Iran gateway number​

90003497

Treat sender-number checking only as an additional filter; it is not equivalent to cryptographic authentication. Do not execute SMS that appears to be an AirNgin command when it comes from an unauthorized sender.

Device-to-server SMS framing​

The current framing prefix is:

CC:Data
  • CC is the fixed uppercase prefix.
  • Data is the manufacturer payload that the SMS Analyzer maps to the same AirNgin operationName/Command model used by MQTT.