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 Component on the computer.
This is not a problem of the ActiveXperts component, but is related to the security settings of your Windows computer.
Please try the following:
To start the command prompt, start it from the start menu by locating the "Command Prompt" in the start menu. Then, right-click on this item and select "Run as Administrator".
Then, issue the following command from the command prompt:
REGSVR32.EXE AxSms64.dll
or
REGSVR32.EXE AxSms32.dll
You can also try to turn off UAC (User Account Control)
Yes it can. To install the ActiveXperts SMS Component DLL on another machine, simply copy either the AxSms64.dll (for 64-bit applications) or AxSms32.dll (for 32-bit applications) to the target machine and issue the REGSVR32 registration command on that machine.
To register the 64-bit component, issue the following command:
REGSVR32 AxSms64.dll
To register the 32-bit component, issue the following command:
REGSVR32 AxSms32.dll
Please note that on 64-bit systems, you can register both the 64-bit component (for 64-bit applications) and the 32-bit component (for 32-bit applications).
Yes, on 64-bit systems, you can register both the 64-bit component (for 64-bit applications) and the 32-bit component (for 32-bit applications). You can use the same REGSVR32.EXE command for that:
REGSVR32 AxSms64.dll REGSVR32 AxSms32.dll
You are right: you cannot install the product in an existing directory.
At uninstall, the original directory (default: C:\Program Files\ActiveXperts\SMS Component\) 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 Component\) is deleted, you can re-install it in that directory.
If you used the regular ActiveXperts SMS Component Setup (AxSmsSetup.exe) to install the software, you can simple uninstall the software by using the 'Add/Remove' applet in the control panel.
If you copied the AxSms64.dll and/or AxSms32.dll file(s) manually to your system and registered manually, you should first unregister the component(s) by running 'REGSVR32 -u AxSms64.dll' and/or 'REGSVR32 -u AxSms32.dll' from the command-line, and then delete the AxSms64.dll and/or AxSms32.dll file(s).
To uninstall the 64-bit component, issue the following command from the command prompt:
REGSVR32 -u <path>\AxSms64.dll
To uninstall the 32-bit component, issue the following command from the command prompt:
REGSVR32 -u <path>\AxSms32.dll
ActiveXperts SMS Component supports the following SMS protocols:
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.
In this case you have to uninstall the software manually. You can do it in the following way:
ActiveXperts 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.
For normal phone numbers it's recommended to use the international format that is prefixed with a '+' sign. For example, to send to mobile number: 0622334455 in the Netherlands (+31) use: '+31622334455'.
Short codes can be used as is, without a '+' sign. For example: '1200' is a valid number.
In addition, it's possible to use these characters in the phone nr as well: ' ()-', they will be stripped and ignored by the SMS Component.
It's important to note that every phone number has a TON (Type of Number) and a NPI (Number Plan Indicator) to go with it. These are used by the provider to find out how the number should be read and routed.
With the SMS Component, for GSM and SMPP , it's possible to include an application port number in the phone number to automatically add an application port header to the SMS message. Find more information about these here.
It's easy to send to an application port. Just append the port number to the 'ToAddress' of the message. For example, to send a message to port '1000' on mobile '+31622334455' use the following number: '+31622334455:1000'.
This works on both GSM and SMPP.
For sending WAP Push messages, these are specially formatted message to application port 2948, it's possible to use a template: 'TemplateWapPush'.
Yes, ActiveXperts SMS Component is thread-safe. This means that the component can be used by multiple applications simultaneously, and each application can have multiple threads running the ActiveXerts SMS Component code at the same time. Please note that each thread should load the component in its own context, as a separate instance.
Yes this is possible. Both GSM and SMPP will, by default, automatically split up or re-assemble SMS messages when appropriate. For more information about the supported multipart options for each protocol please check the manual pages. The exception is the SMPP Server protocol. This will automatically split up messages but received multipart messages will not be re-assembled.
For most HTTP providers splitting up an SMS message is not an issue so the ActiveXperts SMS Component takes no action there.
It's not possible to send multipart messages through the Dialup protocol.
ActiveXperts SMS Component does not return this value before sending out the messages. Use the following formula to approximate the number of parts before sending:
For text messages:
Number of messages = ( Number of Characters / 153 ) + 1
For unicode messages:
Number of messages = ( Number of Characters / 67 ) + 1
For data messages:
Number of message = ( Number of Bytes / 134 ) + 1
Yes it is possible to use an alphanumeric source address with a maximum length of 11 characters. Such feature can only be used with the Smpp object or Http object, not with the Gsm object. Gsm modems/providers simple don't support this feature.
For more information, see also Q4240070.
To find the carrier associated with a mobile number, you have to perform a so called HLR lookup. Some HTTP or SMPP providers offer this service. HTTP providers will have specific HTTP 'GET' or 'POST' queries to retrieve this information. SMPP providers may send additional information about the carrier as TLV values.
When using HTTP, use the Get or Post function to make custom queries to a provider.
When using SMPP use the SmppGetFirstTlv and SmppGetNextTlv function to inspect Message objects to see if the provider was able to provide extra information.
This is determined by the DataCoding property of a message. On a Unicode message this property should be set to DATACODING_UNICODE.
Yes. For both GSM and SMPP it's possible to request a delivery report to be sent back to you when an SMS message reaches a final state. For GSM modem this is sometimes called a 'Status Report'.
To request a delivery report, or status report, you will need to enable the 'RequestDeliveryReport' property on a 'Message' object before sending it.
After sending the SMS message check the 'Reference' property of the message you just sent to get a reference that was returned by the provider. This reference will be used to reference this message in the delivery report as well.
On a GSM modem a delivery report is a special message. You can find delivery reports that you have received by iterating over them after calling 'Receive' by calling 'GetFirstReport' and 'GetNextReport'.
On an SMPP connection a delivery report is just an ordinary SMS message with the property 'SmppIsDeliveryReport' enabled. On SMPP you can either parse the message to find the reference and ultimate message status or check for optional TLV values. Some providers use 'SMPP_TLV_RECEIPTED_MESSAGE_ID' tag and the 'SMPP_TLV_MESSAGE_STATE' TLV's to convey this information as well.
Download the trial version of the ActiveXperts Component to find some examples on how to receive delivery reports.
No, CDMA modems do not support the PDU mode and AT commands used by the SMS Component, therefore we do not support this protocol. The only network protocols supported are GSM with its extensions GPRS and/or EDGE and WCDMA (UMTS).
For more information on recommended modems for ActiveXperts SMS Component, click here.
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.
The use of cell phones is not recommended since there's a lot of difference in quality between cell phones make and model. But still most cell phones should work, as long as the phone has a build in modem which supports AT commands (GSM 07.05 and GSM 07.07 specification). Some older Nokia phones don't work, as they use the older F-bus protocol.
NOTE: a lot of modern cellphones running on operating systems such as iOS, Symbian or Android are not or not fully supported, because they cannot be used as an external GSM modem.
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 Visa and higher, and Windows 2008 and higher, 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.
The SMS throughput when using GSM is approx. 10 - 15 messages per minute per connected GSM modem or GSM phone.
Most phones display the messages that are on both phone and SIM card. The SMS Component reads one message storage at a time. You can indicate which storage to read from in the Receive function of the Gsm object. To read from all supported storage locations in one call use the 'GSM_STORAGETYPE_ALL' constant.
Yes, ActiveXperts SMS Component supports USB modems. Usually, USB modems ship with a modem driver, so the modem can be accessed as it were a serial COM device. If the modem does NOT come with a modem driver, you'll need a USB to Serial converter, for example a 'FTDI UC232R' adapter.
This depends on the DCE (Data Carrier Equipment), the device to which you are connected. If this device requires hardware flow control, you'll need it too. In most cases, hardware flow control is required; that's why it is enabled by default.
NOTE: when using a Windows Telephony device, hardware flow control settings are inherited from the device settings and do not need to be set.
Software flow control is only used for data transfer. To send or receive SMS messages, the modem is in command mode, and therefore the software flow control settings are ignored.
a GSM modem is a dedicated device that you can connect to your PC or server to send and receive SMS messages. It works similar to a GSM phone connected to you PC, but it is faster and much more reliable.
here is a list of GSM modems that are recommended by ActiveXperts.
Yes it can be done, by using the 'SendCommand' function. The SendCommand function is member function of the Gsm object. The following sample (VBScript) shows how to achieve this:
Dim objGsm, objSmsMessage, strCmdResponse, strBuffer
Set objGsm = CreateObject("AxSms.Gsm")
Set objSmsMessage = CreateObject("AxSms.Message")
objGsm.LogFile = "log.txt"
' Open the first TAPI device
sDevName = objGsm.FindFirstDevice
Wscript.Echo "Opening: " & sDevName
objGsm.Open sDevName
If objGsm.LastError <> 0 Then
Wscript.Echo "Error: " & objGsm.GetErrorDescription(objGsm.LastError)
Wscript.Quit
End If
objSmsMessage.ToAddress = "+31122334455"
objSmsMessage.Body = "Hello, world"
' Query the GSM modem for its signal strength; the output (strCmdResponse) is
' something like "+CSQ: 30,0"
' where 30 indicates the signal strength (0 is lowest strength, 31 is highest), and 0 is
' an error code (0 means: no error)
objGsm.SendCommand "AT+CSQ"
If objGsm.LastError <> 0 Then
Wscript.Echo "Error: " & objGsm.GetErrorDescription(objGsm.LastError)
Wscript.Quit
End If
While strBuffer <> "OK"
strBuffer = objGsm.ReadResponse
If strBuffer <> "" And strBuffer <> "OK" Then
strCmdResponse = strCmdResponse & strBuffer
End If
Wend
' Split up the response and store it in arrCmdResponse;
' arrCmdResponse(0): "+CSQ:";
' arrCmdResponse(1): "30,0"
arrCmdResponse = Split(strCmdResponse)
' Split up the string and store it in arrSignal; arrSignal(0): "30"; arrSignal(1): "1"
arrSignal = Split(arrCmdResponse(1), ",")
' Store Signal strneght [0..31] in numSignal as an Integer value
numSignal = Cint(arrSignal(0))
Wscript.Echo "Signal strength: " & numSignal
' If the signal strength is poor (less than 20) then quit
If numSignal < 20 Then
Wscript.Echo "Singal strength too low."
Wscript.Quit
End If
Wscript.Echo "Singal strength ok, send message."
objGsm.SendSms objSmsMessage ' Send the message
If objGsm.LastError <> 0 Then
Wscript.Echo "Error: " & objGsm.GetErrorDescription(objGsm.LastError)
Wscript.Quit
End If
objGsm.Close
Make sure that your GSM modem is operating at 115200 bps. To change the baud rate of your GSM modem, setup a connection to the modem using HyperTerminal and type the following command:
AT+IPR=115200 <ENTER>
Then, close the HyperTerminal sessions and open it again using the new baudrate (115200 in this case) Type the following command to save the new baudrate in the modem :
AT&W <ENTER>
NOTE 1: When the modem is connected through Bluetooth or Infrared, we recommend 115200 bps (modem speed and driver).
NOTE 2: Most Siemens cell phones are optimized for 19200 bps.
WaveCom Fastrack modems do not ship with a Windows Telephony driver. You should use the Standard 56000 bps modem.
The Gsm object has properties to return the manufacturer, model, revision and the serial number of an open device. Use the 'SerialNr' property to distinguish between multiple identical modems.
No, this is not a bug. On the web server, the IUSR_<computername> credentials are used for all SMS operations. The IUSR_<computername> is only member of the Guests group by default, and has no privileges to list the TAPI devices. By adding the IUSR_<computername> account to the Local Administrator group, you will be able to see all telephony devices.
It means that the GSM modem is hanging. You need to reset (power-off/power-on) the GSM modem manually.
Unfortunately, this is not possible. This is not a restriction of the software, but a security restriction of SIM cards.
No this cannot be done. This is not a limitation of ActiveXperts SMS Component, but the network accepts only one message at a time. You need to set the ToAddress property and call the SendSms function for each recipient.
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 through 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 won't loose the message. The new message is simply not accepted by your GSM modem, and the provider will queue the messages (usually for a few days) until there is free space on the memory card again.
There can be various reasons for this problem, depending on the phone or modem model you are using:
If the above does not solve the issue, please send the logfile of your attempt to our support desk.
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:
Yes you can. If you set the BodyFormat property of a Message object to BODYFORMAT_HEX, it is possible to fill the Body property with HEX encoded data.This can be send though all supported SMS protocol (GSM, SMPP, HTTP).
Don't forget to set the DataCoding property to DATACODING_DATA if required.
Yes, it is possible. You can let the modem dial to a phone number by sending an AT dial command to the modem. You should to use the SendCommand function. For example:
Dim objGsm Set objGsm = CreateObject( "AxSms.Gsm" ) objGsm.SendCommand( "ATD+31638740161", 20000 )
It is not always possible to check whether the call was successful, the response can be different on various modem models, some reply with "OK" when the connection is setup, while others only return an error when the call has failed.
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 115200bps. Two things you need to do:
1. Make sure that your COM port is configured to use 115200bps. To do so, open the Windows Device manager and click on COM1-properties. There you can set it to 115200bps.
2. Set the modem to 115200bps. The following FAQ item describes how to set your modem to a different speed: FAQ#Q4200075.
Yes, It's possible to send USSD (Unstructured Supplementary Service Data) commands. These messages are different from standard SMS messages, and such requests are usually not charged by the provider. These messages can be sent using the SMS Component by using the "SendCommand" function of the Gsm object.
The trial version of the SMS Component also contains a number of samples which illustrate the use of USSD over GSM
By setting the PreferredSmsc property, you can specify which SMSC should be used to send out SMS messages.
Yes, ActiveXperts offers a free SMPP service. It allows you to send out a few free messages through the ActiveXperts SMPP service.
Use the following URL:
| URL: | smpp.activexperts-labs.com | |
| SystemID: | Provided during installation of ActiveXperts SMS Component | |
| Password: | Provided during installation of ActiveXperts SMS Component |
Find more information about the ActiveXpert SMPP server here.
Please check out our SMPP compliant provider list here.
There are many different SMPP providers around the world. Although they should be compatible with our software, we cannot guarantee because we haven't tested them all. You should test the ActiveXperts SMS Component software with your prefered SMPP provider yourself before you purchase, just to ensure that the software/provider combination works without problems.
Approx. 5000 - 12000 messages per minute per active SMPP connection. The value depends on the performance of the SMPP provider and your network connection.
Yes you can. Please send an e-mail to support@activexperts.com with subject: ActiveXperts SMS Component SMPP credits.
Please do not forget to mention your SystemID in your message. Our support desk is happy to provide you with extra credits.
Most probably, your provider only supports SMPP v3.3. Transceiver mode can only be used for providers that support SMPP v3.4 or higher.
To send and receive simultaneously, just create two instances; connect to the first one as Transmitter, and to the second one as Receiver.
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.
Your SMPP provider does not convert these chars to the GSM alphabet automatically. You need to set the UseGsmEncoding property to 'True' to get the message encoded correctly.
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.
ActiveXperts SMS Component connects to SMPP providers using SMPP version 3.3, 3.4 and 5.0.
ActiveXperts offers a free SMPP Simulator. Download SmppSim.exe and run it to start the installation.
Most probably, the provider that is used by the ActiveXperts gateway does not cover your provider's network, and a different route must be selected. The ActiveXperts gateway can use different SMPP providers to route the SMS messages.
To receive SMS messages via a commercial SMPP provider, they have to setup a virtual number (IMSI) where the messages can be sent to.
This can be an international number, national number or a short code. When using a national number or short code, your service can only be reached from within the same country.
When using an international virtual number, users can also access your service from other countries.
When someone sends an SMS message to this virtual number, the messages are routed automatically to your SMPP client.
Some providers advertise with SIM-hosting. This means that they host a SIM card with associated phone number in one of their GSM modems.
When a message is received it is forwarded to your SMPP client.
When using the ActiveXperts SMPP gateway however, you can also route messages sent by your own mobile phone without having to setup a virtual number.
You can receive an unlimited number of messages through our gateway free of charge..
No it is not supported, only the bind_transceiver, bind_receiver and bind_transmitter pdu's are supported to establish a SMPP connection.
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 EnquireInterval to a value of '30'.
If this does not help, please ask your provider to assist you solving this issue.
Yes this is possible. The ActiveXperts SMS Component is not needed for this. Receiving through HTTP is normally just a matter of setting up a web page, using IIS for instance, in ASP or ASP.NET.
The HTTP provider should be directed to this page to post it's received SMS messages to.
No; dial-up SMS messaging only allows plain-text SMS messages. Use a GSM modem or an SMPP or HTTP provider to send Unicode messages.
No. ActiveXperts only supports a PSTN or ISDN line for UCP dialup connections. To use TCP/IP, you should use SMPP.
No. ActiveXperts only supports a PSTN or ISDN line for TAP dialup connections. To use TCP/IP, you should use SMPP.
A standard singlepart SMS message can have up to 160 7-bit characters, with the following restrictions:
Each part will be sent as a separate SMS message and re-assembled on the recipients mobile phone as one SMS message. Please note that each part will be billed as one singlepart SMS message by your provider.
Yes, Unicode is supported by ActiveXperts SMS Component. You can send virtually any character set when sending messages as Unicode.
Set the DataCoding property of an SMS message to DATACODING_UNICODE to send the message using a Unicode character set.
Please read the following item: How to use ActiveXperts SMS Component in Visual Basic
Please read the following item: How to use ActiveXperts SMS Component with VBScript. This document describes how to refer to the ActiveXperts SMS Component, and how to declare, create and use the objects.
Please read the following document: How to use ActiveXperts SMS Component with VBA (Visual Basic for Applications). This document describes how to refer to the ActiveXperts SMS Component library, and how to declare, create and use the objects.
You must refer to the object before you can declare and create it. Go to the 'Project' menu, choose 'References...' and put the checkbox near 'ActiveXperts SMS Component Type Library'.
You have not installed and registered the ActiveXperts SMS Component ActiveX component. This component can be installed and registered automatically by running the ActiveXperts SMS Component installation. You can download the installation file from the ActiveXperts download site.
To install the component manually, see the manual, chapter Installation (Manual).
Please read the following section in the manual: How to Use ActiveXperts SMS Component with HTML. This section describes how to refer to the ActiveXperts SMS Component library in your project, and how to declare, create and use the objects.
There are basically three ways to avoid prompting:
Please read the following article: How to digitally sign an ActiveXperts software component.
You need Microsoft Visual Studio 2008 or higher. All sample projects are created in Visual Studio 2008. If you use a newer version of Visual Studio, then Visual Studio will prompt you to convert the project file.
If you use an older version of Visual Studio, you must recreate the sample projects yourself and add the source files.
In all C++ files that make use of an ActiveXperts SMS Component object, you must include 'AxSms.tlb' and 'AxSmsConstants.h'. No files need to be added to the project.
Yes, you can, but you can only compile the Console Applications. The Forms applications make use of the Microsoft MFC framework, which is not supported by Microsoft Visual Studio Express.
In all C++ files that make use of an ActiveXperts SMS Component object, you must include 'AxSms.tlb' and 'AxSmsConstants.h'. No files need to be added to the project.
You need Microsoft Visual Studio 2008 or higher. All sample projects are created in Visual Studio 2008. If you use a newer version of Visual Studio, then Visual Studio will prompt you to convert the project file.
All .NET samples make use of .NET framework 2.0
The samples require .NET Framework 2.0 or higher.
Please read the following document: Using ActiveXperts SMS Component with Visual Basic .NET. This document describes how to refer to the SMS Component library, and how to declare, create and use the objects.
Please read the following document: Using ActiveXperts SMS Component with Visual C# .NET. This document describes how to refer to the SMS Component library, and how to declare, create and use the objects.
You haven't installed and registered the ActiveXperts SMS Component ActiveX component properly. This component can be installed and registered automatically by running the ActiveXperts SMS Component installation, or by registring manually (see also FAQ Q4000015).
You haven't installed and registered the ActiveXperts SMS Component ActiveX component properly. This component can be installed and registered automatically by running the ActiveXperts SMS Component installation, or by registring manually (see also FAQ Q4000015).
See FAQ 4600002.
See FAQ 4600003.
See FAQ 4600005.
See FAQ 4600025.
See FAQ 4600030.
Please read the following document: Using ActiveXperts SMS Component with ASP. This document describes how to refer to ActiveXperts SMS Component library, and how to declare, create and use the objects.
On an ASP webserver, the IUSR_<computername> credentials are used for all SMS operations. The IUSR_<computername> is only member of the Guests group by default. By adding the IUSR_<computername> account to the Local Administrator group, you will be able to see all telephony devices.
On the webserver, the IUSR_<computername> credentials are used for all SMS operations. The IUSR_<computername> is only member of the Guests group by default; it doesn't have sufficient permissions to query the Windows Telephony Devices. By making the IUSR_<computername> account member of the Local Administrators group, you will be able to see all Windows Telephony Devices.
Please read the following document: Using ActiveXperts SMS Component with Delphi. This document describes how to refer to the ActiveXperts SMS Component library, and how to declare, create and use the objects.
Click here to see the list of all ActiveXperts error codes.
This means that the COM port does not exist. Error 30102 does NOT mean that the port is already in use. Error: 30103 indicates the port is already in use.
This means that the port you are attempting to open is already in use by another application.
Please check the following:
This means that the Windows Telephony Device you specified, is NOT defined on the computer. You may have made a typing mistake. Error 30201 does NOT mean that the port is already in use (you would get error 30204).
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'). There can be multiple reasons for this error:
This error only occurs when using Windows Telephony devices (like 'Standard 9600 bps Modem'). There can be two reasons for this error:
When you encounter this error, please check the following:
If the above does not help, most probably your modem or phone does not have a built in modem which supports hayes AT commands, and is therefore not supported by the SMS Component.
This is an equipment related error code from the GSM device. This error code is likely to be related to your GSM device hardware or embedded software. Find a description of the GSM error codes here.
Although most of the error codes are standardised, some manufacturers give their own meaning to these error codes. It's always a good idea to double check with your GSM modem manual.
This is a network related error code from the GSM device. This error is likely to be related to your operator. Find a description of the GSM error codes here.
Although most of the error codes (up to 512) are standardised, some manufacturers give their own meaning to these error codes. It's always a good idea to double check with your GSM modem manual.
To learn about the different license options for ActiveXperts SMS Component, click here.
After 30 days of evaluation, the ActiveXperts SMS Component will no longer connect to any device. When calling these functions, LastError shows: Evaluation Expired (Error# 35995).
Click here for more information about the ActiveXperts SMS Component licensing options.
The 'Distribution License' allows you to 'bundle' the component with your own software. It allows you to ship the product to an unlimited number of customers for an unlimited period of time. There are no limitations to functionality of the software.
Click here for more information about the ActiveXperts SMS Component licensing options.
Once you have obtained a Distribution License, you receive a key that you can use on the target computers. Click here to read more about how to distribute this key with the core product DLL on the target computers.
Once you have obtained a Distribution License, you will receive a key that you can use on the target computers.
Please read manual, chapter: Purchase and Product Activation for more info about distributing this license key.
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.
After purchase, you get 1 year Maintenance for free
After this free Maintenance period, Licensee may purchase Maintenance. The price for the Maintenance Agreement is 15% of the price that was payed for the product.
Read our Maintenance Agreement in PDF format.
No, ActiveXperts does not offer commercial SMS messaging services; ActiveXperts only offers the software.
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. Pricing depends on the type of telecom operator and the SMS volume.
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.
The smpp.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 occasionally: hardware).
You can purchase the product online, by proforma invoice (bank or cheque) or through a reseller. For more information, check the Sales webpage.
Please read the manual, chapter: Purchase and Product Activation.
During the first (1) year after purchase, Maintenance is free.
After this free Maintenance year, Licensee may purchase Maintenance.
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 source code of our products.
The only source code that is included with our products are code samples shipped, to show how to use the component in various programming languages.
| Error codes |
|---|
| Click here to view the full list of error codes |