SMS Login

This manual describes how to provide a SMS login for guests on the IACBOX.

Hint

  • This module became free for all IACBOXes with valid Software Maintenance as of 1st December 2016.

  • The login by using a SMS is meant to be free, guests can not be charged.

  • In order to configure the SMS login a SMS Gateway is required. You can also create your own SMS Gateway on an external server and then use the generic HTTP GET/POST Interface in the IACBOX SMS configuration.

  • The SMS login requires at least one valid ticket template, configured as 0€ (free).

How it works

On the Login Page, a SMS tab will be displayed in which guests can enter a mobile phone number. After confirming the mobile phone number, first a request to the configured SMS Gateway will be sent. Then this SMS Gateway will send a SMS to the mobile phone number of the guest. The SMS will contain login credentials.

Example SMS:

1
2
3
4
Welcome to ExampleCompany!
Username: ticket1
Password: dbh3z
Status: http://logon.now

Attention

  • Please note that in order to keep the SMS limit under 160 characters, the Status line will only contain a short link which will be redirected to the IACBOX Client Login Page. If you want to add a link which automatically does log in guests with the added credentials, then replace the URL http://logon.now with $LINK:

1
2
3
4
Welcome to $COMPANY
Username: $USER
Password: $PASSWORD
Status: $LINK

Selecting a SMS Gateway

The IACBOX does support a few SMS Gateway providers and interfaces out of the box. These providers can be selected directly in the SMS configuration of the IACBOX.

International:

Austria:

Germany:

Switzerland:

Turkey:

  • Maradit Web Services

Alternatively it is possible to use a custom SMS Gateway. If you do have a Webserver or Email Server in your environment, you can also use the generic interfaces Generic via HTTP and Generic via Email.

Hint

  • By using one of the 2 generic interfaces, you must configure your servers to send a SMS which does contain the information provided by the IACBOX. This can be done by using a mobile phone network interface in the sending host or by using custom software which can interact with connected mobile phone devices.

  • Any solution developed upon this requirement must be evaluated and maintained by your team.

Configuration

The configuration of the SMS module can be found in the WebAdmin menu Login methods / SMS & email.

../_images/sms_messaging_1.png

For the fields Server, Username and Password refer to the documentation of your SMS gateway provider.

Hint

  • The SMS module requires at least one valid ticket template, configured as 0€ (free). If no template is available, a new example template will be created upon activation of this module.

Generic Interfaces

In addition to the supported SMS gateway providers there is also the possibility to use a generic interface. You can select between generic via HTTP and generic via Email. This also enables you to use SMS APIs of unlisted providers.

Generic via HTTP

Enter the target server with username and password for authentication. The input field user data from the WebAdmin configuration will be sent to the target server with the selected data transmission method (REST-POST, REST-GET, JSON).

Since the HTTP request can be customized in the input field Request, you can determine how the target server receives the data and further processes it.

The following data is transmitted regardless of the selected data transmission method:

  • Username The username of the SMS gateway

  • Password The password of the SMS gateway

  • Message The message which will be sent to the user

  • To The mobile number which was entered by the user

  • Timestamp Current timestamp

Twilio

New in version 19.0.14604-15842.

Twilio is supported via the Generic via HTTP method and can be configured with the following settings:

  • Choose type Generic via HTTP

  • Use the URL: https://api.twilio.com/2010-04-01/Accounts/<YOUR-SID>/Messages.json

  • As username set the SID (usually in the format ACxxxxxxxxxxxxxxxxxxxxxxx)

  • As password set your auth token (a 32 char Hex number)

  • Check Use HTTP Basic Auth

  • Use Method REST - POST

  • Request has to be Body=$MESSAGE&From=%2B<YOUR-TWILIO-SENDER-NUMBER-WITHOUT-PLUS>&To=$TO

  • Return Validation has to be "status": "queued"

  • Prefix Format is +

Attention

You need an active sender number in your twilio account for this to work. If your account is in trial mode the receiver number has to be whitelisted.

Generic via Email

Enter a sender (e.g. “iacbox”) and the target email server which should receive the data from the IACBOX as email. The mobile number which was given by the guest will be added to the configured target server address by which an unique email address is being used for each mobile number.

The user data (username, password, etc.) will then be sent to the generated email address. The target server which receives this email will then send an SMS which contains the Message to the users phone number.

Example: The configured target server is sms.ip-plus.net. When a guest enters a mobile phone number on the Client Login Page, it will be added to the configured target server, e.g. +43797979797@sms-ip-plus.net

WebAdmin Tickets with SMS

If the option Use for Ticket Create is active, ticket data (username, password) of newly created tickets from WebAdmin Users/Tickets / Create ticket can be directly sent via SMS.

../_images/sms_messaging_2.png

Client Logon Page

After all settings have been made, the result can be seen on the customer logon page.

../_images/sms_messaging_3.png

After confirming the number, a SMS with credentials will be sent. These credentials can then be entered by clicking on the I have credentials link.

../_images/sms_messaging_4.png

This will expand the section in which the received credentials can be entered to confirm this ticket and go online.

Stored Data

All used mobile phone numbers can then be found in the WebAdmin menu Reporting / Collected user data and are obtainable as csv and xls downloads.

../_images/sms_messaging_5.png