SMS Component is designed for Windows developers (VB, VB .NET, VC++, VC#.NET, ASP, ASP .NET, Delphi, etc.). It's an ActiveX COM component, without user interface. By integrating the control in a development project, a developer can send/receive SMS messages without any knowledge of SMS. SMS Component has no integrated database support
ActiveXperts SMS Messaging Server is a complete suite to send, receive and process SMS messages. It is database oriented, and has a VBScript engine to process incoming messages. Use ActiveXperts SMS Messaging Server to have your SMS applications running within a few hours.
With ActiveXperts SMS Messaging Server, you can configure your project for virtually any scenario that requires (bulk) SMS sending, receiving and processing. For a short list of projects that were implemented with SMS Messaging Server, click here. ActiveXperts SMS Messaging Server supports GSM modems, SMPP providers, HTTP providers to send/receive SMS messages.
ActiveXperts SMS Messaging Server supports the following protocols:
It's recommended to use the international number format. Use a '+' character and country prefix followed by the number, stripping a leading '0'. For example, the local Dutch number: 0711223344 would be formatted as: '+31711223344'.
If you are sending an SMS message to a specific application use can specify the destination port number in the 'To' address as well. The destination port number need to be seperated from the phone number by a colon ':'. For example, to send an SMS message to the vCard application on mobile phone nr. '+31611223344' use: '+31611223344:9204'.
In addition you can use a number of formatting characters that will be ignored: ' ' (space), ',' (comma), '-' (hyphen), '(' and ')' (open and close parentheses).
A standard SMS message is can contain up to 160 7-bit characters. Some characters count as two (7-bit) characters instead of one character. Example: the EURO character;
To send messages longer than 160 characters, you must enable set the 'Large Messages' option in the Channel properties to: 'Send as Multi-part'. By default, large messages are NOT send as multi-part but are truncated to 160 characters maximum.
Yes, Unicode is supported.
No, the messaging server only supports SMS and Email. However, you can send advanced messages like flash, Unicode and WAP Push messages.
No, it does not, to send these kind of messages, you have to use MMS which is not part of the SMS Messaging Server.
Yes it does. ActiveXperts SMS Messaging Server has a multi-threaded architecture; each communication Channel runs as a separate thread (i.e. sub-process). This allows messages to go come in and go out simultaneously.
No, it doesn't. Dial-up providers are too slow; an SMS message takes up to 1 minute, or even more, because it uses a normal modem to dial-up to a provider, and deliver the message. Therefore, it is not integrated in SMS Messaging Server.
If you want to use a dial-up anyway, you can use ActiveXperts SMS Component.
Yes this is possible, but ONLY by the use of an SMPP or HTTP channel. Gsm modems/providers simple don't support this feature.
For more information, see also Q8300100
Sure, in fact a sample project to setup this is already included in the product, just go to Projects and select the 'SmsToEmail' project for more information.
Yes, that's possible. However, by design of SMS messaging Server, you cannot communicate directly through a modem or SMPP/HTTP interface from the command line. Instead, you insert new messages in the Message Database from the command line. The service (running in the background) will pick-up the message and send it out.
Receiving from the command line is similar; you cannot receive directly but only fetch received messages from the message database.
There are samples included with the product, written in VBScript. The VBScript samples are located here:
C:\Program Files\ActiveXperts\SMS Messaging Server\API Samples\VBScript\Messages\Create
To use a batch file, simply invoke the VBScript program, like this:
@echo off cscript.exe createsms.vbs
Most probably, you don't have administrative privileges on the machine where you install the product. You must have local administrator rights to install ActiveXperts SMS Messaging Server on the computer.
Uninstall the software using the 'Add/Remove' applet in the control panel: Select 'ActiveXperts SMS Messaging Server' and click on 'Remove'.
You cannot install the product in an existing directory.
Upon un-installation, the original directory (default: C:\Program Files\ActiveXperts\SMS Messaging Server) is NOT deleted in case there are files created/modified after the previous installation. You must delete these files/directories manually.
Once the directory (C:\Program Files\ActiveXperts\SMS Messaging Server) is deleted, you can re-install it in that directory.
In previous versions of the product, it was possible to install in an existing directory, but this often lead to interference with previous installations.
ActiveXperts SMS Messaging Server supports the following hardware:
ActiveXperts uses the InstallShield product for its installations. Only on very rare occasions, InstallShield doesn't update its registry key after uninstall, so it will ask you to uninstall the next time you start the installation. You can use this workaround:
Now, InstallShield won't ask to uninstall anymore.
You can do it in the following way:
Local System credentials will usually suffice. It is important that the SMS Messaging Server has Read/Write access to all files located in its installation directory.
There's one situation where Domain Administrator credentials are required: if you use MS SQL database on a remote computer, and MS SQL requires Windows Authentication, then Domain Administrator credentials are required for the SMS Messaging Server service.
Please do the following:
Do the following:
SMS Messaging Server is now configured to connect to the central SMS Messaging Server computer.
To install the Web Interface on a separate IIS machine, with SMS Messaging Server Engine (service) installed on another machine, do the following:
Then, create a new virtual web site in IIS, and let the home directory point to the local <INSTALL-DIR>\Asp directory.
SMS Messaging Server is now configured to connect to the central SMS Messaging Server computer.
There's no need to migrate the configuration to MS SQL. Only when there are changes, the database is accessed by the service. However, if you prefer to have the configuration database in MS SQL, you can do so.
ActiveXperts supports any modem that is compliant with both ETSI GSM 07.05 and ETSI GSM 07.07 standards.
Please note this doesn't necessarily mean that a modem that is compliant to these standards is automatically a good modem. There are many cheap modems around, with different firmware versions etc. For a list of recommended modems, please click here.
For more information on recommended modems for ActiveXperts SMS Messaging Server, click here.
SMS Messaging Server supports both GSM Modems and GSM Phones. The GSM Phone can basically be any business cellular phone that supports the AT+C command set and that has a serial-, Bluetooth or Infrared interface.
For a list of raccomended GSM Modems, click here..
Please make sure you have correctly installed the drivers for your GSM device (modem, mobile phone) and that the GSM device is correctly connected to it. Then verify that the device is working fine under Windows, otherwise you won't get it to work with ActiveXperts.
To verify that the device is working fine under Windows, make sure you can connect to your phone through HyperTerminal. On Windows XP/2003 you can install Hyper Terminal through:
Start > (Settings) > Control Panel > Add or Remove Programs > Add/Remove Windows Components > Accessories and Utilities > Communications
Make sure HyperTerminal is checked.
On Windows 8/Windows 7/Windows Vista/2008/2012 Hyper Terminal is no more available. If you previously used HyperTerminal to troubleshoot modem problems, use Phone and Modem Options instead. Open Phone and Modem Options by clicking the Start button , clicking Control Panel, clicking Hardware and Sound, and then clicking Phone and Modem Options.
First, you should check the GSM Modem Channel properties. Make sure that a SIM card is inserted and that a PIN code is provided (if required).
To see real-time communication details, use the ActiveXperts SMS Messaging Server Monitor. A shortcut is located in the Start Menu.
To get more detailed information, you can enable logging for a GSM Channel. To enable logging, start the Registry Editor (REGEDIT.EXE or REGEDT32.EXE), and set the following Registry entry:
HKLM\Software\ActiveXperts\SMS Messaging Server\Trace\GSM Modem 1xxx\LogFile
You must restart the SMS Messaging Server service before changes take effect.
Please note that logging can decrease the performance of the service, especially when the log files becomes several Megabytes or more.
You can send/receive only 1 messages per 5 seconds using GSM. It's 10-12 messages per minute. This throughput basically applies to all available GSM modems, and is limited by the GSM protocol.
Because it is not possible to read the SMS number from the SIM card. In fact, the SMS number of the SIM card is not really required by the software, but is used for displaying and logging purposes.
It means that the GSM modem is hanging. You need to restart the GSM modem manually.
By default, the maximum number of GSM Modem channels is set to 4. To increase this number, change the following registry key: HKLM\Software\ActiveXperts\SMS Messaging Server\Performance\ThreadsGsm. Please note that the engine will consume more resources when this number is increased, because it needs to create additional threads to handle these channels.
This means that the COM port does not exist. You only get this error if you use a COM port (like COM1) rather than a Windows Telephony device (like 'Standard 9600 bps Modem'). Error 30102 does NOT mean that the port is already in use. If the port would already be in use, you would get another error: 30103.
This means that the port you are attempting to open is already in use by another application. You only get this error if you use a COM port (like COM1) rather than a Windows Telephony device (like 'Standard 9600 bps Modem').
Check if there's another application that is already using the COM port. In some situations, you may want to benefit from a thing called 'port sharing', where one port can be shared by multiple applications. To benefit from 'port sharing', you must use Windows Telephony devices (like 'Standard 9600 bps Modem').
This means that the Windows Telephony Device you are using, is NOT defined on the computer. You may have made a typing mistake. Error 11201 does NOT mean that the port is already in use (you would get error 11202).
You will never get this error when using direct COM ports (like 'COM1'), but only when using Windows Telephony devices.
This error only occurs when using Windows Telephony devices (like 'Standard 9600 bps Modem'). The error implies that the Windows Telephony device is valid, but that the associated COM port is either already in use, or does not exist. The error does NOT imply that the Windows Telephony device is invalid (that would give error 30201); it neither implies that the Windows Telephony device is already used (that would give error 30204).
This error only occurs when using Windows Telephony devices (like 'Standard 9600 bps Modem'). The Windows Telephony device name is valid,. There can be two reasons for this error:
First of all, you need a modem that supports GPRS. You also need a provider that supports GPRS (not all providers support GRPS!)
To send an SMS over GPRS, add the following to your modem initialization string:
AT+CGATT=1;AT+CGSMS=0
The first command enables GPRS (disabled by default); the second command specifies to send SMS over GPRS instead of GSM.
You can now send SMS messages over GSM. However, if the provider does NOT support GPRS, you will receive the following error:
+CMS ERROR: 47 or +CMS ERROR: 69
You can switch it back using the following command:
AT+CGATT=0;AT+CGSMS=1
You can set the service center address with AT+CSCA in two ways:
The syntax for the AT+CSCA command:
AT+CSCA=""
You won't lose the message. The new message are simply not accepted by your GSM modem, and the provider will queue the messages for a couple of days until there is free space on the memory card again.
Yes, you can see all commands using a trace file. By default, tracing is NOT switched on. Tracing is enabled/disabled per channel.
You can enable tracing for your modem by specifying a log file for the particular channel in the registry:
HKLM\Software\ActiveXperts\SMS Messaging Server\Trace\GSM MODEM.xxxx ,
where xxxx is the actual channel number.
After you change this registry value, you MUST restart the SMS Messaging Server engine (service) for the changes to take effect.
Most probably, you are using a GSM phone running on the Symbian OS. This phone does not allow you to receive messages through the built in GSM modem. The only solution is to use another phone or a GSM modem (recommended). Some phones which cannot be used to receive SMS are:
Most probably, the baud rate causes the problem: COM port and modem are not sending/receiving at the same speed. We strongly recommend to use 9600bps. Two things you need to do:
GSM modem consume power when receiving and sending messages, because signals have to be transmitted to the network.
USB modems get the power from the USB port of the PC, sometimes this is not enough and the modem will restart due to power loss.
Please try the following:
With an HTTP channel, you can send up to 20 message per second or faster. It all depends on the (connection to the) HTTP provider and the performance of your database.
With an HTTP channel, you cannot receive SMS message, you can only send SMS messages.
When sending SMS messages using HTTP POST you have to use the following international dialing format: use a + character and country prefix followed by the number, stripping a leading 0 :
By default, the maximum number of HTTP channels is set to 4. To increase this number, change the following registry key: HKLM\Software\ActiveXperts\SMS Messaging Server\Performance\ThreadsHttp. Please note that the engine will consume more resources when this number is increased, because it needs to create additional threads to handle these channels.
The SMS Messaging Server should work with most SMPP providers, however there are so many different SMPP providers in the world, that we cannot guarantee that our software works with all SMPP providers. You should test the ActiveXperts SMS Messaging Server software with your prefered SMPP provider before you purchase to ensure that the software/provider combination works without any problems.
Please check out our SMPP compliant provider list here.
With an SMPP channel, you can receive up to 20 messages per second or faster. It all depends on the (connection to the) SMPP provider and the performance of your database. See also FAQ #8300005.
If you use triggers to process incoming messages, it is strongly recommended to use MS SQL as message database instead of MS Access. See also FAQ #8800100.
Yes you can. Please send an e-mail to support@activexperts.com with subject: SMS Messaging Server SMPP credits.
Please mention the SystemID you are using in your email.
Our support desk is happy to provide you with more credits.
ActiveXperts SMS Messaging Server supports SMPP versions:
You must sign-up with a public SMPP SMSC provider. There are hundreds of SMPP providers around the world. ActiveXperts SMS Messaging Server supports all SMPP v3.x compliant providers.
A sign-up usually requires a small sign-up fee and a monthly SMS bundle.
Most probably, your provider only supports SMPP v3.3. Transceiver mode (send and receive simultaneously) can only be used for providers that support SMPP v3.4 or higher. To send and receive simultaneously, just create two channels: enable Send-only for the first one and Receive-only for the second one.
Please check the following:
If this does not help, please contact your SMPP provider to ask if they can help debugging your connection.
You can also monitor the SMPP protocol on TCP/IP level as described in the following document.
This error can have the following causes:
If this does not help, please contact your SMPP provider to ask if they can help debugging your connection.
You can also monitor the SMPP protocol on TCP/IP level as described in the following document.
The 'Address Range' parameter is used in the bind_receiver and bind_transceiver command to specify a set of SME addresses serviced by the ESME client. A single SME address may also be specified in the address_range parameter. UNIX Regular Expression notation should be used to specify a range of addresses.
Messages addressed to any destination in this range shall be routed to the ESME.
Note: It is likely that the addr_range field is not supported or deliberately ignored on most Message Centers. The reason for this is that most carriers will not allow an ESME control the message routing as this can carry the risk of mis-routing messages. In such circumstances, the ESME will be requested to set the field to NULL.
For more information on UNIX regular expressions, click here.
By default, the maximum number of SMPP channels is set to 4. To increase this number, change the following registry key: HKLM\Software\ActiveXperts\SMS Messaging Server\Performance\ThreadsSmpp. Please note that the engine will consume more resources when this number is increased, because it needs to create additional threads to handle these channels.
Yes, you can see all commands using a trace file. By default, tracing is NOT switched on. Tracing is enabled/disabled per channel.
You can enable tracing for SMPP by specifying a log file for the particular channel in the registry:
HKLM\Software\ActiveXperts\SMS Messaging Server\Trace\SMPP.xxxx ,
where xxxx is the actual channel number.
After you change this registry value, you MUST restart the SMS Messaging Server engine (service) for the changes to take effect.
Your SMPP provider does not convert these chars to the GSM alphabet automatically. You have to convert the messages to GSM alphabet. To do this, go o Configuration=> Channels, select the SMPP channel and click on the pencil to modify the properties. The Charset setting can be found in the "Advanced Settings" section of the SMPP channel properties. Set this value to "GSM".
The main difference between these SMPP versions is that version 3.4 supports the use of optional parameters, also called TLV's (Tag-Length-Value ). These TLV parameters enable SMSC vendors to add custom functionality to the SMPP protocol.
Most probably, the provider that is used by the ActiveXperts gateway does not cover your provider's network.
Please contact support and tell them to which cellphone number in which country you are trying to send messages. Support will then try to create a route to your mobile number.
Yes. We offer a freeware utility that simulates an SMSC. This is a very usefull tool for troubleshoot and (stress) testing application. Find it here.
Yes it is possible. This is also called an 'Alphanumeric Source Address'. This text can be eleven characters long. To use an alphanumeric source address, you need to assign the display string to the SMPP Channel's Source Address property. It is recommended to set the Source TON property to 5 when using alphanumeric displaynames, because it is required by some providers.
You can change the above properties in the SMPP Channel's Advanced Settings box.
SMPP uses a link keep alive timer. Once in every x seconds the client should send an enquire_link packet to the SMPP server, if this packet is not received the SMPP server will close the connection. This will also happen if your enquire_link timer is set to high. Please try to set the keep alive timer to a lower value. This can be done from the SMPP channel properties window in the channel view of the SMS Messaging Server Manager application.
Not all settings can be entered in the channel wizard. To setup a channel, just let all checks fail and select 'Continue Anyway'.
You can modify the advanced settings later in the manager application.
To set the required TLV's or optional parameters for mBlox ("mblox_tariff" and "mblox_operator"), you have to perform the following steps:
mblox_tariff: The mblox tariff is a 5 digit number which should be entered encoded as OCTET data. This means that you will need the hexadecimal values of the ASCII codes that represent the numbers. For example, the number: 12345 will should be entered as "3132333435". To convert your tariff id to OCTET data simply take every digit of your id and put a '3' in front of it.
Follow these steps to add your converted tariff value:
mblox_operator: The mblox operator is a 5 digit number which should be entered encoded as OCTET data. This means that you will need the hexadecimal values of the ASCII codes that represent the numbers. For example, the number: 12345 will should be entered as "3132333435". To convert your operator id to OCTET data simply take every digit of your id and put a '3' in front of it.
Follow these steps to add your converted operator value:
By default, the maximum number of SMTP channels is set to 4. To increase this number, change the following registry key: HKLM\Software\ActiveXperts\SMS Messaging Server\Performance\ThreadsSmtp. Please note that the engine will consume more resources when this number is increased, because it needs to create additional threads to handle these channels.
Yes, you can see all commands using a trace file. By default, tracing is NOT switched on. Tracing is enabled/disabled per channel.
You can enable tracing for SMTP by specifying a log file for the particular channel in the registry:
HKLM\Software\ActiveXperts\SMS Messaging Server\Trace\SMTP.xxxx ,
where xxxx is the actual channel number.
After you change this registry value, you MUST restart the SMS Messaging Server engine (service) for the changes to take effect.
Yes it can be done, from the manager application, paste the HTML code into the messagebody field, and set the message format to HTML.
No, at this moment, email attachments are not supported. When receiving emails with attachments, they will be ignored.
By default, the maximum number of POP3 channels is set to 4. To increase this number, change the following registry key: HKLM\Software\ActiveXperts\SMS Messaging Server\Performance\ThreadsPop3. Please note that the engine will consume more resources when this number is increased, because it needs to create additional threads to handle these channels.
Yes, you can see all commands using a trace file. By default, tracing is NOT switched on. Tracing is enabled/disabled per channel.
You can enable tracing for POP3 by specifying a log file for the particular channel in the registry:
HKLM\Software\ActiveXperts\SMS Messaging Server\Trace\POP3.xxxx ,
where xxxx is the actual channel number.
After you change this registry value, you MUST restart the SMS Messaging Server engine (service) for the changes to take effect.
By default, the maximum number of File Pickup channels is set to 4. To increase this number, change the following registry key: HKLM\Software\ActiveXperts\SMS Messaging Server\Performance\ThreadsFile. Please note that the engine will consume more resources when this number is increased, because it needs to create additional threads to handle these channels.
Yes, you can. Execute a SQL command like this:
INSERT INTO Messages( Body, ToAddress, TypeID, DirectionID, StatusID) VALUES( 'Hello world!', '+316112233445566', 1, 2, 1 );
Please note that'TypeID=1' means: SMS, 'DirectionID=1' means: Outgoing, 'StatusID=1' means: Pending For an explanation of these fields, please check the manual, chapter Message Database Tables).
I depends on the SMS/e-mail traffic. An MS SQL database performs much better than MS Access, especially when the database is large (i.e. 50.000 messages or more). With low/medium databases (up to 50.000 messages) an MS Access database will suffice.
Yes, MS SQL Express Edition is supported.
Migration to MS SQL Server Express Edition can be done in the same way as migrating to MS SQL Server, with only one difference: you MUST specify the instance ID of the SQL Server Express Edition database in the 'Host' field.
For example, if the name of the database server is named 'DbServer01', and the instance id of the database is named 'SQLExpress', then specify 'DbServer01\SQLExpress'.
There's no performance difference between MS SQL Server and MS SQL Server Express. See also FAQ #8380015.
No, there's no performance difference between MS SQL Server and MS SQL Server Express Edition. It is strongly recommended to migrate your Message Database to either MS SQL Server or MS SQL Server Express Edition to boost the performance of the Message Database.
It is not a built-in feature of SMS Messaging Server. You should use ActiveXperts Network Monitor to monitor the SMS Messaging Server message database, and to failover to a secondary message database in case the primary message database fails.
Click here for more information about this topic.
Yes you can. Please read the following article for more information: Create a new SMS or e-mail Message directly without using the API.
Yes you can. Please read the following article for more information: Create a new SMS or e-mail Message directly without using the API.
Yes, MS SQL Express Edition is supported.
Migration to MS SQL Server Express Edition can be done in the same way as migrating to MS SQL Server, with only one difference: you MUST specify the instance ID of the SQL Server Express Edition database in the 'Host' field.
For example, if the name of the database server is named 'DbServer01', and the instance id of the database is named 'SQLExpress', then specify 'DbServer01\SQLExpress'.
There's no performance difference between MS SQL Server and MS SQL Server Express. See also FAQ #8380015.
The SMS Messaging Server stores all message data to the database as Unicode. Please check the following:
Yes, you can. Execute a SQL command like this:
INSERT INTO Messages( Body, ToAddress, TypeID, DirectionID, StatusID) VALUES( 'Hello world!', '+316112233445566', 1, 2, 1 );
Please note that'TypeID=1' means: SMS, 'DirectionID=1' means: Outgoing, 'StatusID=1' means: Pending For an explanation of these fields, please check the manual, chapter Message Database Tables).
Select the message, and click on 'View...' from the Context Menu.
The Message status has changed from Scheduled into Pending; this means that it is time to send the message. The message has been delivered to the channel that is responsible for sending the message. The status will soon change into a value indicating that the message was delivered, or - in case of a failure - the message failed.
Yes you can. It is a good practice to archive message to a separate database when you have a lot of message in your Message Database.
Make sure that archiving is enabled in the 'Options' view of the Configuration, and set a proper value for the 'Archive After' field. There's no recommended value for it, it depends on the number of messages you have and how often your view is refreshed.
Yes, this is possible. You can limit the number of outgoing SMS messages in the channels properties (GSM Modem Channel, Http Channel and Smpp Channel only). You can only set a daily limit.
Use the MS SQL Migration Wizard. You can launch the wizard from the 'Tools and Utilities' Folder in the Manager application.
Yes you can. Please read the following article for more information: Create a new SMS or e-mail Message directly without using the API.
Yes you can. Please read the following article for more information: Create a new SMS or e-mail Message directly without using the API.
This cannot be configured in the Manager. You can run a script for that. This script can also be scheduled, for instance once every minute, to automatically resubmit messages continueously.
You can find the script here: http://www.activexperts.com/support/sms-messaging-server/online/resubmit/resubmit.vbs
Please note that the scripts contains two constants that need to be changed:
Simply double click on the message in the Message View, it will show the 'Trace' field of the message. It tells you exactly what went wrong. Most probably, there was an error in your VBScript program. Line and character position will be shown to indicate the exact location where the error occurred in the script.
The SMS messaging Server engine can process up to 30 messages per second, i.e. 900 messages per minute. Processing speed depends on the processing speed of the server where SMS Messaging Server is running.
A condition is ALWAYS FALSE if the status of the incoming message indicates that the message has already been processed. So, if you define three triggers (all enabled), and the first trigger sets the message status to PROCESSED, the other triggers will NEVER match the conditions and the associated scripts will never be called.
Apparantly, the first script sets the status of the message to True, and the other two scripts are not executed.
Yes this is possible, you can use the following script to do this:
Dim WshShell
set WshShell = CreateObject ("wscript.Shell")
WshShell.Run "path to your application goes here", 3
If this application has to interact with the desktop (i.e. it has a GUI) you have to enable this.
To do this, go to the 'Control Panel'=>'Administrative Tools'=>'Services' and double click the SMS messaging server service. Select the 'Log On' tab, and select the 'Allow service to interact with the desktop option'.
The SMS Messaging Server API is described in the Online Manual. For samples about how to use the API from various development platforms, click here.
There are instructions available for Visual C++ v.6 and Visual Basic v.6. For Visual C++ 6.x instructions, click here. For Visual Basic 6.x instructions, click here.
For instructions for other development platforms, click here.
The demo project can be accessed through smslive.activexperts.com/gpstracker. In order to host this web application on your own hardware, please contact ActiveXperts via sales@activexperts.com and apply for this project, and we will get back to you. The project is only available for licensed users.
The project is accessible through smslive.activexperts.com/gpstracker. You can use a wide variety of modems for this project. However, we recommand the Blumax GPS Tracker in particular. It supports tracking by SMS and GPRS. For more information on this GPS Tracker, see blu-max.com.
It depends on the type of channel.
With an SMPP channel, you can send out up to 20 messages per second or faster. It all depends on the (connection to the) SMPP provider and the performance of your database. See also FAQ #8300005.
With a GSM channel, you're limited to max. 10-12 messages per minute. This is limited by the GSM protocol. See also FAQ #8200025.
With an HTTP channel, you can send up to 20 message per second or faster. It all depends on the (connection to the) HTTP provider and the performance of your database. See also FAQ #8250010. Note that with HTTP, you can only send, not receive.
It depends on the type of channel.
With an SMPP channel, you can send out up to 20 messages per second or faster. It all depends on the (connection to the) SMPP provider and the performance of your database. See also FAQ #8300005.
With a GSM channel, you're limited to max. 10-12 messages per minute. This is limited by the GSM protocol. See also FAQ #8200025.
With an HTTP channel, you can not receive messages.
For best performance, make sure that your messages are in MS SQL or MySQL.
With VBScript triggers, you can process with a speed of up to 15 messages per second or faster, depending on the performance of your database.
If you need higher performance, you should not use VBScript triggers, but our High Volume Processing technique. Therefore, you need to disable Triggers in the General Options, and use our High Volume Processing sample (written in C#) as a base. Using this High Volume Processing technique, you can process 50 messages per second or faster, depending on the performance of your database.
Most important is to use a fast SMS communication protocol, and a fast database. The SMPP protocol is the fastest SMPP protocol supported by SMS Messaging Server. With SMPP, you can send/receive at up to 20 messages per second or faster. See also FAQ #8300005.
If you use SMPP, it is strongly recommended to use a faster database than MS Access, for instance, MySQL, MS SQL or MS SQL Express Edition. This is definitely required if you use triggers to process incoming messages. Triggers open the database, read the message and usually generate a reply message in the database. MS Access cannot keep up with the speed of processing incoming messages.
If you stick to MS Access, it is strongly recommended to keep the Message Database small, i.e. to keep a maximum of 1.000.000 messages. You can control the size of the message database by specifying a short Archive Period value. To do so, select 'Options' from the Manager, enable 'Archiving' and set a short Archive Period frequency (for instance: 3 days).
With MS Access, it is also recommended to perform a 'Compact and Repair' action to purge deleted records from the Message Database. This keeps the message Database small and compact.
It is always a good practice to write logging information to a different drive to optimize speed. Especially when the log files grow large, you may want to benefit from a fast drive or fast RAID system.
You must take a closer look at the trace information. Trace information is part of the message, you can see this trace information by double clicking on the message from the Manager application.
The Monitor application can only show real-time information. To view a full trace, you must enable 'tracing' for the particular modem.. There's tracing possible for the following items:
To enable tracing for a particular channel or thread, you must enable it through the registry, by assigning a Log File to it:
When an error occurred the service will stop automatically. Possible causes are:
For the exact cause, you can have a look at the log's in the Windows Eventlog.
There can be two reasons for that:
To learn about the different license options for ActiveXperts SMS Messaging Server, click here.
You only need one license. Licensing is based on the number of installations of the product. Since you only install it once, you need one license.
No you don't. The SMS Messaging Server indeed uses SMS, but a license of SMS Messaging Server automatically allows you to use the SMS Component. No additional license is required. The same thing for ActiveXperts Email Component: ActiveXperts Email Component is used by SMS Messaging Server to send out e-mail messages, but you do not need a separate license.
ActiveXperts' Maintenance Agreement entitles customers to use ActiveXperts' technical support services, and to receive all product upgrades, free of charge, during a specified Agreement duration. The Maintenance Agreement applies to all ActiveXperts products.
With the purchase, you get 1 year Maintenance for free. After this free Maintenance period, Licensee may renew Maintenance. The price for the Maintenance Agreement is 15% of the price that was paid for the product.
Read our Maintenance Agreement in PDF format.
No, SMS messages are NOT for free. ActiveXperts does not offer commercial SMS messaging services; ActiveXperts only offers the software.
If you want to use GSM, you need a GSM modem and a SIM card, just like the one you use in your mobile GSM phone. You can buy a SIM card from any telecom operator. Princing depends on the type of telecom operator and the SMS volume.
If you want to use SMPP, you need to subscribe to an SMPP service provider. For a short list of reliable SMPP providers, click here. There are many SMPP providers all over the world. Pricing depends on type of operator and SMS volume. Most of the SMPP providers also offer HTTP-Post services.
TAP/UCP dial-up is getting less- and less popular, but you can still find a lot of TAP/UCP providers all over the world. With this protocol, you can only send. Pricing depends on type of operator.
You can't. The ftp.activexperts-labs.com SMPP gateway is only available for testing purposes. It is not a commercial SMPP service. The server is hosted by ActiveXperts Software. ActiveXperts does not offer any commercial SMS services; it only supplies the software (and occasionaly: hardware).
After 30 days of evaluation, functionality will be reduced: all outgoing messages will be blocked. Open the 'About' window to see how many days are still remaining.
For detailed sales information, check the Sales webpage.
It's very simple: just launch the ActiveXperts SMS Messaging Server Manager application, go to the Help menu and select the Registration menu item. Here, you can enter the registration code. You'll be asked to activate the registration; you'll be automatically redirected to the ActiveXperts web page to continue activation.
Your security settings do not allow to store the license key. Please do the following:
Once you've completed the above steps, the key is stored on the system.
Yes, you are allowed to use the API on any workstation or server; you do not need additional licenses.
During the first (1) year after purchase, Maintenance is free.
After this free Maintenance year, Licensee may purchase Maintenance. The price for the Maintenance Agreement is 15% of the price that was paid for the product.
Customers choose between one-, two- and three years Maintenance Agreement renewal. Please read the Maintenance Agreement document for more details.
Renewals that come in after the maintenance has expired will be backdated to start from the old expiry date. Also, you are only able to get Technical Support and Software Maintenance when your support contract is valid.
No, we do not ship or sell the sourcecode of our products.
The only sourcecode that is included with our products, are the code samples shipped with toolkits or API's.
| Error codes |
|---|
| Click here to view the full list of error codes |