AQL SMS Gateway How to Guide
- 1 AQL
- 2 Overview
- 3 Trial Account with 50 free SMS messages
- 4 Prerequisites
- 5 Configuring the AQL transport
- 6 Expected Results
- 7 Troubleshooting
- HTTP on port 80 (supported by Swivel)
- HTTPS on port 80 (supported by Swivel)
Trial Account with 50 free SMS messages
Mobile Phone on which to receive SMS text messages
Configuring the AQL transport
Configuring one or more AQL transports for Swivel 3.x
On the Swivel Administration Console select Transport/General, locate the AQL transport. Enter the required group name and the number of security strings to be sent. Ensure that the transport attribute phone is selected.
Identifier: Default: AQL, the name of the transport, must be unique
Class: Default: com.swiveltechnologies.pinsafe.server.transport.AqlTransport, the name of the java class used. To create multiple copies of a transport, copy this to a blank field at the bottom of the transport section.
Strings per message: Default: 1, the number of security strings that are sent.
Group: Default: ---NONE--- The group where security strings are sent to
Alert repository group: Default: ---NONE--- The group where Alert messages are sent to
Destination attribute: Default: phone, the attributes that is read from the data source to determine a users telephone number
Click apply to save the settings. For further information see: Transport Configuration
Configuring the AQL details for Swivel 3.x
Username: Default: blank, AQL account name
Password: Default: blank, AQL account password
Message Overwrite Default: No, Options Yes/No, this option allows the overwriting of previous text messages sent from PINsafe
transport aql timeout: Default 180000, timeout value for connection to gateway in milliseconds
When a message is sent it is added to the message queue and then sent to the SMS gateway:
Message added to message queue for user: graham, destination: 12345678901
Message sent to user: graham, destination: 12345678901
Try sending a security string or alert and check the Swivel log.
Do you have an AQL account with username and password?
Also see SMS messages are not being sent
Check the connection, use TCP Dump, Wireshark, ethereal or similar to view the connection from Swivel to the SMS gateway. Look for outbound traffic of HTTP, on port 80, or HTTPS on port 80 to the SMS Gateway https://gw.aql.com.
From the Swivel server can you Telnet to the gateway: telnet gw1.aql.com 443 Press enter and it should return an HTTP header, (Note the gateway to be used in the Swivel AQL configuration is https://gw.aql.com/sms/sms_gw.php).
Test ports using Telnet
Service IP: gw.aql.com Service Port: 443 Trying 18.104.22.168... Connected to gw1.aql.com (22.214.171.124). Escape character is '^]'.
From the Swivel server can you do an nslookup to gw1.aql.com
nslookup gw.aql.com Server: google-public-dns-a.google.com Address: 126.96.36.199 Non-authoritative answer: Name: gw1.aql.com Address: 188.8.131.52
IP address change
The IP address for gw1.aql.com changed in October 2014. If the IP address is used for Firewall entries etc then it may need to be re-entered.
AQL SMS logs
login to http://www.aql.com using your account details and view SMS history from the Account Navigation, SMS, SMS history to see if SMS messages have reached AQL are attempting to be sent.
AQL_TRANSPORT_ERROR0 Authentication error
The AQL gateway authentication has failed, verify the username and password for the account is correct. This can also be seen if the From field is incorrectly populated, try using a blank value.
This error can be seen where the Swivel Appliance or server has no DNS configuration. Ensure that DNS is functioning. If DNS is updated a restart of Tomcat may be required.
AQL_TRANSPORT_ERROR0 Insufficient credit or invalid number of msg/destination
Either the account does not have enough credit to send an SMS and new credits must be purchased or the phone number is incorrect and the message cannot be sent.
AQL_TRANSPORT_ERROR0 Authentication error LOG_NO_USER_FOR_DEST, 441234567890 Inbound SMS: Multiple users have same destination 441234567890 No session for Inbound OTC received from user graham
This is a two way SMS authentication error message. An inbound SMS message has not been received.
LOG_HTTP_TRANSPORT_ERROR, No route to host
There is no network connection to the Gateway. Check that a network connection exists and that there are no firewall devices blocking the connection.