GSM Modem How To Guide
From Swivel Knowledgebase Wiki
Contents |
GSM Modem How To Guide
Overview
PINsafe can send SMS messages in a variety of ways including;
- SMS Gateway by HTTP/HTTPS, SMTP or SMPP communication
- GSM Modem
The use of a SMS gateway such as AQL or Clickatell is the recommended method for delivery of SMS messages.
This document covers the use of the GSM modem.
Currently only Serial port modems are supported and not USB modems.
Advantages/Disadvantages of GSM Modems
Advantages
Control over hardware
Free sms, contracts, subject to reasonable usage
100% Dual channel communications
Disadvantages
Needs a signal, ensure install location has a carrier signal
Additional hardware device often with own power
Often no rack mount available
Can be a point of failure
SIM card needs to have contract
One Time Code sent by SMS should have additional protection (such as PINsafe PIN protected security string)
Company policy may need to be modified to allow a GSM device
Requirements
PINsafe server
GSM Modem
For a software install of PINsafe the Java Comm API is required to communicate with the GSM Modem.
Additional Considerations
The number used for the GSM modem may need to be redirected to a help desk in case anyone tries to contact the source phone number for support.
The GSM modem should be configured to only send messages and thus will not be able to receive incoming calls or messages.
SMS Overwriting
What is SMS Message Replacement?
This is where a new text message overwrites, replacing an older text message. This is supported by GSM modems but not by all SMS service providers. Only the security strings can be overwritten. Alerts that are sent out are not overwritten.
When this is set 0x41 is set for the protocol id (PID) for the message.
Supported Modems
Serial Modems
- FASTRACK XTEND FXT003 EDGE W-CDMA HSxPA MODEM R7.4aEx 3G http://www.sierrawireless.com Note: Ensure a power supply is ordered if required. For the User Guide see [1]
http://www.linkwave.co.uk/products/sierra-wireless/3G-Modems
http://www.westbaseuk.com/sierra-wireless-airlink-fastrack-xtend-gprs-programmable-m2m-gateway.html
http://www.2k1.co.uk/wireless/SW_modules5.asp
http://www.acaltechnology.com/index.php?page=series&id=3216
- Multitech MTCBA-G-F4
- Siemens TC35i
USB Modems
None currently supported
Supported Serial Modems that are now End of Life
Multitech MTCBA-G-F1 (Now End of Life) http://www.multitech.com
Wavecom Fastrack
Unsupported/Untested Modems
These may work
Nokia Mobile Phone connected by data cable
Testing
Firstly the message should be added to the message queue:
Message added to message queue for user: <username>, destination <Mobile number>
The message is then sent:
Security String message sent to user: <username>, destination <Mobile number>
Troubleshooting
SMS not being sent from GSM modem?
Check the logs as they will contain message transport information.
What do the lights on the modem indicate? A solid TR light would indicate that the modem is locked by a process that has not disconnected. Other solid status lights could also indicate that the modem is not registered on the cellular network.
Check the flow control, hardware or software.
Check that the SIM is installed.
Check that you have paid the phone bill/SMS providers bill.
Is the ‘On Demand Delivery:’ Set to Yes under Dual Channel, if so an SMS will only be sent when requested.
Are more than 11 numbers being used or spaces or special characters in the number, if so try removing them.
Try turning off SMS message Replacement.
If the Transport Queue becomes locked, Tomcat may have to be restarted.
Is there a GSM signal to send an SMS message.
Has the Java Comm API been installed.
Try different number formats, remove the + or use 00 instead
GSM settings not being saved? Check that the GSM settings are correct after Tomcat is restarted. Verify that the GSM settings in the config.xml file reflect those in the PINsafe Administration console.
A monitoring tool such as wireshark may be used to look at the data which is sent to the GSM modem
If an error message is reported check to see if the SMS message is still sent
restart the modem by powering off and then on
Intermittent Problems with GSM Modem
Ensure that the baud rate is set correctly, usually this will be 9600.
Use Hyperterminal and Blackbox software, Note: that this program cannot use Ctrl-Z and therefore cannot be used to send messages. Blackbox will check the Java Comm installation.
Start hyperterminal and connect to the GSM modem, the connection settings are normally as below, but may vary:
Serial Port: Com1
Bit Rate: 9600
Bits: 8
Parity: N
Stop Bits: 1
Flow Control: Software (XON/OFF settings)
Connection to the GSM modem can be tested by using atz and at+csms=1 commands as below
atz expected response ‘Ok’
atz+csms=1 expected response ‘+csms: 1,1,1 Ok’
Error Messages
Exception occurred: org.marre.sms.SmsException: javax.comm.PortInUseException: Port currently owned by SMSJ
SMSJ is the library used by PINsafe and may indicate that a PINsafe process is still using the modem.
GSM transport is locked?
Restart Tomcat
'admin:Loading transport class "com.swiveltechnologies.pinsafe.server.transport.GsmTransport" failed, error: java.lang.reflect.InvocationTargetException
Install the Java Comm class
LOG_HTTP_TRANSPORT_ERROR, 503 Service Unavailable, Message added to message queue for user: xxxxxx, destination nnnnnnnnnn, Message send failed for user xxxx, destination nnnnnnnnnn message will be retried later, VODAFONE ERROR: 13 An internal error occurred.
GSM using Vodafone, error due to mobile network issue
LOG_GSM_FAIL, org.marre.sms.SmsException: Send failed: Unexpected response Last Response:
Message send failed for user: XYZ123, destination: <<MOBILENUMBER>>. Message will be retried later.
Message has been retried too many times, being removed from message queue, user: XYZ123, destination: <<MOBILENUMBER>>.
This is the sequence of events associated with a failure to send a SMS message. The Unexpected response message indicates a failure to communicate with the GSM modem. A common cause of this is incorrect Flow Control settings, try software Flow Control.
PINsafe Appliance GSM Troubleshooting
Check to see if the operating system has recognized the hardware
dmesg | grep tty (display hardware info)
E.G ttyS0 at 0x03f8 (irq = 4) is a 16550A
port available
or setserial –g /dev/ttyS0
list of active connections to serial processes and waiting connections.
ps -ef | grep tty
compare output before and after the power cycle of the modem.
Use minicom –s
running the minicom -s command from the command line
Config correct port parameters
(9600,8,n,1)
Turn off autobaud (our recommended command string)
a. AT (make sure you get OK back first)
b. AT&F
c. AT (make sure you get OK back first)
d. AT+IPR=9600
e. AT+ICF=3,4
f. AT+IFC=2,2
g. AT&W
Save settings and exit
Press Enter to leave the Serial Port screen Select - Save setup as dfl - should say "Configuration Saved"
Select - Exit
Press Ctrl-A
Press Shift-x
Modem Status Lights
a. LED ON Permanent = Modem is switched on but not registered on the network.
b. LED Flashing slowly = Modem is switched on and registered to the network, and it’s activity status is idle.
c. LED Flashing rapidly = Modem is switched on and registered on the network and a communication is in progress.
Check symbolic links
Check too see if the symbolic link files are correct using this command line
(Note symbolic link versions may vary according to build version)
ls -l /usr/java/jre1.5.0_06/lib/i386/librxtxS*
Results: /usr/java/jre1.5.0_06/lib/i386/librxtxSerial-2.0.7pre2.so
/usr/java/jre1.5.0_06/lib/i386/librxtxSerial.la
/usr/java/jre1.5.0_06/lib/i386/librxtxSerial.so -> librxtxSerial-2.0.7pre2.so If the symbolic link files are missing use this command to re-create
cd /usr/java/jre1.5.0_06/lib/i386
ln -sf librxtxSerial-2.0.7pre2.so librxtxSerial.so
• Check to see if a port exists use: “setserial -g /dev/ttyS0”
• List open ports: “lsof /dev/ttyS*”
