ActiveSMS V5.0
User Manual
IntelliSoftware Ltd
Contents
1.1 Email->SMS and SMS->Email
Gateway
4.3 Email -> ActiveSMS Settings
5 ActiveSMS System Health Monitoring
7 SendSMS Command Line Utility
10.1 Email->SMS Gateway - Forcing
Transport
11 Appendix A – COM Component
Reference
ActiveSMS supports 2-way text messaging using various SMS transport methods. Messages can be sent and received in two ways:
§ COM Component Interface - an easy to use COM interface allows messages to be sent and received using any language that supports COM (e.g. ASP, JScript, VBScript, C++, VB).
§ 2-way Email to SMS gateway – Send and receive SMS text message as emails.
ActiveSMS can integrate with your current mail server to provide 2-way SMS messaging from your standard email clients (e.g. Microsoft Outlook).
SmartRouting
SmartRouting
is technology that allows 2-way conversations between a mobile user and an
email user within your organisation. ActiveSMS will attempt to route SMS
replies back to the email user that initiated the conversation.
ActiveSMS can be configured to forward Emails to SMS. The body of the email will be sent in the SMS text message and can optional include 'From' address and Subject field.
There are two ways to connect ActiveSMS (for Email->SMS) to your mail system:
POP3 Mailbox Polling
ActiveSMS can be configured to periodically check a POP3
mailbox/account for outgoing messages. By default, the destination number will
be extracted from the subject field, separate numbers by commas or semi-colons
(e.g. Subject: 447710123456, 447710654321). The destination phone number must
be supplied in international format unless the international dialling rules
have been set (see section 4.1.4)
SMTP Server
ActiveSMS can be configured to run as an SMTP Server, you will need to make sure your mail server is configured to forward Emails to the ActiveSMS Server. By default, the destination number will be extracted from the To address (e.g. To: 447710123456@mygateway.com). The destination phone number must be supplied in international format unless the international dialling rules have been set (see section 4.1.4)
ActiveSMS can be configured to forward received SMS messages to email. By default, the subject will contain the sender’s phone number and the email body will contain the SMS text message.
See section 4.1.4 for more information.
ActiveSMS consist of three parts:
§ ActiveSMS Server – Sends and receives SMS messages using the available SMS Transports. The ActiveSMS Server runs as a NT Service.
§ Message Queues – Incoming and outgoing SMS Messages are stored here whilst waiting to be processed.
§ Client Components – COM components used by your application to send and receive SMS text messages.
A typical installation will install all three parts. However, you can use ActiveSMS Server remotely from another PC (on the same LAN) by installing the Client Only Components.
For technical support on this product please send an email to support@intellisoftware.co.uk. Please provide information about your operating system and the devices you are using. We will make every effort to reply to your support questions within 24hrs.
When you install ActiveSMS you choose from the following installation types.
|
Installation |
Description |
|
ActiveSMS Basic |
Installs the ActiveSMS Server Basic version and the Client COM Components. The Basic version supports outgoing messages only on 1 transport. |
|
ActiveSMS Professional |
Installs the ActiveSMS Server Professional version and the Client COM Components. The Professional version supports incoming and outgoing messages on 1 transport. |
|
ActiveSMS Advanced |
Installs the ActiveSMS Server Advance version and the Client COM Components. The Advance version supports incoming and outgoing messages on 8 transports. |
|
Client Only Components |
Installs Client COM Components that allow connection to a remote ActiveSMS Server running on another computer. Does not require a Server Licence. |
NOTE: Licence only works for the installation type you have purchased. The Client Only installation does not require a licence.
Installing ActiveSMS starts the 30-day trial period. When the trail period expires the ActiveSMS Server will not send or receive any SMS messages.
To continue using the ActiveSMS you will need to purchase a licence from http://www.intellisoftware.co.uk. You must purchase a licence for the same product type (Basic/Profession/Advanced) as you have installed.
NOTE: A separate licence must be purchased for each server installation. The Client Only installation does not require a licence.
To send and/or receive SMS messages you need to consider which transports you are going to use. The following transports are supported:
§ Mobile Handset or GSM Modem (Send and Receive)
§ HTTP Protocol, Internet->SMS Gateway (Sending only)
§ TAP Protocol (Sending only)
Mobile Handset or GSM Modem
SMS messages are sent and received using a GSM device(s) directly connected to the PC. ActiveSMS is compatible with most mobile phones (with a built in modem) and most GSM Modems. Here is a list of devices with which ActiveSMS is known to be compatible:
Maestro GSM/GPRS
Wavecom WMOD2,
Fastrack M1206B
Falcom A2D-3
Nokia 22, Nokia
Premicell
Multi-Tech Systems GSM
Modem
Siemens M20 Terminal,
Siemens TC35, Siemens TC65
FirstFone Radio Card
XACOM Audiotel GSM
Modem
DigiCom Pocket GMS
modem
Psitek Fusion 1000
Nokia
6210/6250/6310/6310i/7110/7160/7190/8310 mobile phone with DLR-3 cable
Nokia
5110/5130/6110/6150 mobile phone with Nokia Data Suite 2.0/3.0 (NT only)
Ericsson
R300/R320/R380/R520/T39/T60/T62/T65/T68/T68i with DRS-11 cable
Siemens M55 Handset
Motorola Timeport 260
Samsung S300 GSM
Any AT-Compatible device (e.g. GSM Modems, other makes of mobile phones)
HTTP Protocol
SMS Messages can be sent via the IntelliSoftware Internet->SMS Gateway. Connection to the SMS Gateway is made using the HTTP Protocol over an Internet connection.
TAP Protocol
SMS messages can be sent using a standard Modem and telephone line (i.e. PSTN). ActiveSMS will dial-up a TAP service on demand to send SMS messages. TAP services are available in must countries and do not require registration, you normally only pay for the cost of the phone call.
For a list of TAP numbers please see:
http://www.intellisoftware.co.uk/redir?page=tapnumbers.
Intel Pentium I 100Mhz or equivalent
Windows NT4, Windows 2000 and Windows XP
10Mbytes of free Disk Space
To configure ActiveSMS open Start Menu > Program Files > ActiveSMS > ActiveSMS Console.
See section 3.3 for a description of SMS Transports.
This page allows configuration of the transports used to send and/or receive SMS messages. This page also shows the real-time status of each transport.
If you have purchase the Advanced version you will be able to configure 8 transports, otherwise only 1 transport will be available.
Each transport can be individual configured to be either:
§ Mobile Handset
§ GSM Modem
§ HTTP Protocol (Internet->SMS Gateway)
§ TAP Protocol (Sending only)
Each GSM Device can be individual configured to support text messaging in one or both directions (Basic version supports outgoing messages only).
Select the ‘Handset’ transport if you are using a mobile phone, or select ‘GSM Modem’ transport if you are using a GSM Modem. To set-up the transport click the ‘Configure’ button, you will be prompted for the following information:
|
|
Selected the comms port that the GSM device is connected to. |
|
Comms Settings |
You may need to change the comms settings if the default settings are not compatible with your GSM Device. |
|
Concat. Msgs. Max. |
Maximum number of concatenation messages that will be sent for long messages. Set to 1 to disable message concatenation. |
|
PIN Number |
(Optional) If you are using a GSM Modem then ActiveSMS can automatically unlock the Modem using this PIN number. |
|
SMSC Number |
(Optional) SMS Service Centre Number. Set this to override the default SMCS Number set in the SIM card. You will need to sent this item if you SIM card is not configured with an SMSC Number. |
|
Log Errors To File |
When checked, ActiveSMS will log comms activity to a log file. This feature should be normally disabled to prevent disk space usage. |
|
Log Filename |
Path and filename of the log file (e.g. ‘C:\GSMLog.txt’) |
Select the ‘HTTP’ transport and then click ‘Configure’. You will be prompted for the following information:
|
Primary Server |
This is the Internet Address of the Internet->SMS
Gateway. |
|
Backup Server |
This is the backup Internet->SMS Gateway |
|
Username |
This is the Username for your account. You will need to register on the www.intellisoftware.co.uk website before you can send messages. |
|
Password |
This is the Password for your account. |
|
Sender’s ID |
The receiver of the SMS message will see this as the
sender of the SMS message. |
|
Use HTTP Proxy |
If you require a proxy server to access the internet then select this checkbox. |
|
Proxy Server |
Address of your proxy server |
Select the ‘TAP’ transport and then click ‘Configure’. You will be prompted for the following information:
|
Modem |
ActiveSMS will use this Modem to dial out to the TAP service. |
|
Dial-up Number |
This is the telephone number of the TAP service. |
|
Min Baudrate |
Minimum baudrate for the connection |
|
Max Baudrate |
Maximum baudrate for the connection |
|
Msgs Per Connection |
Maximum number of messages that should be sent during one dial-up connection. Most TAP services will limit the number of messages that can be sent in one connection. |
|
Retry Delay After Error |
Time period (in secs) that ActiveSMS should wait before retrying after a connection error has occurred. |
|
Log Errors To File |
When checked ActiveSMS will log TAP activity to a log file. This feature should be normally disabled to prevent disk space usage. |
|
Log Filename |
Path and filename of the log file (e.g. ‘C:\TAPLog.txt’) |
By default,
ActiveSMS will expect all phone numbers to start with the international
dialling code. For example, a
Click on