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#Q5200075.

Most phones display the messages that are on both phone and SIM card. The SMS and MMS toolkit reads one message storage at a time. You can indicate the message storage by assigning the MessageStorage property of the SmsProtocolGsm object.

The SMS throughput when using GSM is approx. 10 - 15 messages per minute per connected GSM modem or GSM phone.

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 or MMS:

• Nokia 6600
• Nokia 7200
• Nokia N-series

When using a Windows Telephony device (also called TAPI device), SMS and MMS toolkit will inherit DeviceSpeed, hardware flow control and the initialization string from the Windows Telephony device, and the DeviceFlowControl, DeviceSpeed and DeviceInitString properties will be 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.

ActiveXperts recommends the Falcom Samba 75 GSM/GPRS modem.

ActiveXperts recommends using 115200 speed for all GSM modems (and GSM 07.05 and GSM 07.07 phones). Use a 'Standard 56000 bps driver to control your modem.

Make sure that your GSM modem is communicating 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.

Almost every cell phone is supported, 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 are not supported, 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 2012/2008 and Windows 10/8/7, 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.

Yes it can be done, by using the 'SendCommand' function. The SendCommand function is member function of the SmsProtocolGsm object. The following sample (VBScript) shows how to achieve this:

  
Dim objGsmProtocol, objSmsMessage, strCmdResponse, arrCmdResponse, arrSignal, numSignal

Set objGsmProtocol         = CreateObject( "AxSms.Gsm" )
Set objSmsMessage          = CreateObject( "ActiveXperts.SmsMessage" )

objGsmProtocol.Device      = "COM1"

objSmsMessage.Recipient    = "+31611223344"
objSmsMessage.Data         = "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)
strCmdResponse = objGsmProtocol.SendCommand( "AT+CSQ", 5000 )

' 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

objGsmProtocol.Send( objSmsMessage )    ' Send the message

No, this is not a bug. 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. By adding the IUSR_<computername> account to the Local Administrator group, you will be able to see all telephony devices.

For more information on recommended modems for ActiveXperts SMS and MMS Toolkit, click here.

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.

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:

• Have a look at this KB item first;
• Try another USB port;
• Connect the modem via an USB hub;
• Make sure the signal strength is okay; Move the modem to another location;
• Use an USB Y cable, which takes power from two USB ports.

No this cannot be done. This is not a limitation of the product, but the network accepts only one message at once. You have to change the Recipient property and call the Send function for each recipient.

Please read the following document: SMS Delivery Reports with GSM.

Software flow control is only used for data transfer. To send SMS messages, the modem is in command mode, and therefore software flow control is not required.

It means that the GSM modem is hanging. You need to restart the GSM modem manually.

WaveCom Fastrack modems are not shipped with a Windows Telephony driver. You should use the Standard 56000 bps modem.

You can use the "SendCommand" function to read the modems serial number :

  
Dim strSerial
strSerial = objGsmProtocol.SendCommand "AT+GSN"

Yes you can, using a z-text fixed line SMS modem. This modem is fully compatible with the SmsProtocolGsm object.

Z-text is suitable for use with worldwide networks that have implemented Fixed Line SMS Protocol 1. These include the UK, Europe, Asia, South Africa, and Australia.

Yes you can. For more information, please check the following document: Sending SMS Data Messages using GSM.

For a list of raccomended GSM Modems, click here.

Unfortunately, this is not possible. This is not a restriction in the software, but a security restriction of SIM cards.

You won't loose the message. The new message is 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.

To send a message to a specific application or port on the remote mobile phone, you can add a port to the recipient number.
Use the following format:

<+mobilenumber>:<port>

For instance, to send a message to an application that is listening on port 1234 on user's mobile phone +31624896641, set the Recipient property as follows:

objSmsMessage.Recipient    = "+31624896641:1234"

Application ports can be used with GSM modems and with SMPP providers.

For more information, click here.

Yes, SMS and MMS Toolkit supports USB modems, as long as the modem is shipped with a serial to USB, or a TAPI modem driver.

Use a + character and country prefix followed by the number, stripping a leading 0 :

• +  : Default number format. For instance, to send to 01234567 in the UK, use +441234567

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

SMPP

ActiveXperts SMS and MMS Toolkit has its own message references, i.e. independent from the provider. However, it is still possible to obtain the provider's message reference of a message.

To read more on message references, click here.

Yes, SMS and MMS Toolkit is capable of checking the status of a message to see whether the message was delivered or not. The Send function returns a message reference that can be used in the QueryStatus function to check the status.

To read more on message delivery and message references, click here.

Your SMPP provider does not convert these chars to the GSM alphabet automatically. You need to set the SystemCharSet property to asSMPPCHARSET_GSM to get the message encoded correctly.

Please read the following document: SMS Delivery Reports with SMPP.

Our SMPP implementation can only be used to connect to a SMPP server, therefore the toolkit can only be used as a SMPP client to send and receive SMS messages to and from a SMPP provider. It is not possible to create a server application using this toolkit.

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.

Yes you can. For more information, please check the following document: Sending SMS Data Messages using SMPP. Q5240070: I want to send SMS messages to my recipients, but I don't want the GSM telephone number be displayed on their mobile phones. Instead, the name of our company should be displayed. Is this possible?

Yes it is possible, but only through the SMPP protocol and HTTP protocol. It is not possible using a GSM modem (limited by the GSM protocol).

The feature 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 SystemSourceAddress property. It is recommended to set the SystemSourceTON property to '5' when using alphanumeric displaynames, because it is required by some providers.

Approx. 5000 - 12000 messages per minute per active SMPP connection. The value depends on the performance of the SMPP provider and your network connection.

There are 2 ways to setup multiple shortcodes:

Solution A:

You can setup a separate SMPP channel for each shortcode to be handled. For each channel, fill in the shortcode to be handled in the AddressRange field in the Advanced Settings dialog. This is not supported by al providers, because some providers only accept a single connection per customer.

solution B:

It is also possible to handle all shortcodes on a single channel. Just create a single SMPP channel and fill in the shortcodes separated with semi columns in the AddressRange field, for instance: "2222;3333;4444". When creating a trigger that handles messages from these shortcodes, you can retrieve the shortcode by using the FromAddress property of the SmsMessage object.

To send a message to a specific application or port on the remote mobile phone, you can add a port to the recipient number.
Use the following format:

<+mobilenumber>:<port>

For instance, to send a message to an application that is listening on port 1234 on user's mobile phone +31624896641, set the Recipient property as follows:

objSmsMessage.Recipient    = "+31624896641:1234"

Application ports can be used with GSM modems and with SMPP providers.

For more information, click here.

You need a so called "SIM hosting" contract with your SMPP provider. This means that the SMPP provider associates a GSM modem (including a SIM card) with their SMPP server.

All messages received on this GSM Modem are forwarded to your account.

Alternatively, you can set up such a configuration yourself using the SMS Messaging Server.

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.

You can select another route by setting the SMPP SystemType value to 'AX1001', 'AX1101' and 'AX1103'. If this does not work, 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.

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 shortcode. When using a national number or shortcode, your service can only be reached from within the same country.

When using an internation 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 only use one sender address per SMPP connection, for instance, if you want to receive SMS messages from +31638740161 on your SMPP client, you have to set the 'AddressRange' property to S+31638740161.

You can receive an unlimited number of messages through our gateway free of charge..

Yes, you can send so called 'multi-part' messages through SMPP using the SMS and MMS Toolkit, unless it is not supported by the SMPP provider.

Please check out our SMPP compliant provider list here.

Yes this is possible. The parameters is used to request delivery reports from the provider. To enable this, just set the RequestStatusReport property to 'True'.

No it is not supported, only the bind_transceiver, bind_receiver and bind_transmitter pdu's are supported to establish a SMPP connection.

The following versions of SMPP are implemented in the SMS and MMSToolkit:

• SMPP V 3.3
• SMPP V 3.4
• SMPP V 5.0

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 ServerKeepalive to a value of '30'.
If this does not help, please ask your provider to assist you solving this issue.

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 paramters enable SMSC vendors to add custom functionality to the SMPP protocol.

To read more on TLV parameters, please click here.

Please check the following:

• Is the hostname or ip address correct?
• Is theTCP portnumber correct?
• Are outbound connections on this port allowed by your firewal?
• ry to increase the SMPP command timeout value.
• Make sure you registered your IP address with the provider, some providers need to setup your ip in their firewall
• Is it possible to ping the SMPP server?
• What happens when you try telnet from the command prompt: telnet 'hostname' 'portnumber', is there any connection?

This error can have the following causes:

• The systemid is incorrect;
• The password is incorrect;
• The systemtype is incorrect;
• The selected SMPP version is not supported by the provider;
• You are trying to setup a transceiver connection, but the provider only supports transmitter or receiver;
• The client application is unable to connect to the SMPP server because of an invalid hostname, portnumber or blocking firewall;
• The server takes to long to respond. In this case please increase the SMPP timeout value.

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 1: For IP addresses, it is only possible to specify a single IP address. A range of IP addresses are not allowed. IP version 6.0 is not currently supported in this version of the protocol.

Note 2: 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.

Yes, ActiveXperts offers a free SMPP service, which allows you to send out a couple of free messages through the ActiveXperts SMPP service.

Use the following URL:

This ActiveXperts SMPP server is not a commercial SMPP server. With commercial SMPP servers, you need to sign up. The costs usually consists of a small sign-up fee and costs per SMS.

By default, the SMPP follows the international dialing format: use a + character and country prefix followed by the number, stripping a leading 0 :

+  : Default number format. For instance, to send to 01234567 in the UK, use +441234567

No, you can't. 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 and MMS Toolkit software with your prefered SMPP provider before you purchase to ensure that the software/provider combination works without any problems.

Yes you can. Please send an e-mail to support@activexperts.com with subject: SMS and MMS Toolkit SMPP credits.

Please do not forget to mention your SystemID in your message. Our support desk is happy to provide you with some extra credits.

Please check the following:

• Is the hostname or ip address correct?
• Is theTCP portnumber correct?
• Are outbound connections on this port allowed by your firewal?
• Try to increase the SMPP command timeout value.
• Make sure you registered your IP address with the provider, some providers need to setup your ip in their firewall
• Is it possible to ping the SMPP server?
• What happens when you try telnet from the command prompt: telnet 'hostname' 'portnumber', is there any connection?

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.

There are two different formats of deliveryreports used by SMPP providers. Some providers return the message id in this report in HEX format, while others return it in decimal format.

To change this format you have to use the 'DeliveryReportFormat' property.

ActiveXperts itself does not offer this software, but there are some good SMPP simulators available. For instance, the SMPP Client Test Tool for Linux and SMPP SIM.

HTTPPOST

This functionality is not included in the SMS and MMS Toolkit.To be able to process messages posted back by the provider, you have to create either a PHP, ASP or ASP.NETwebpage that parses the HTTP post data from the provider.

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 :

• +  : Default number format. For instance, to send to 01234567 in the UK, use +441234567

DIALUP

Please check out our compliant dial-up SMSC provider list here.

No; dial-up SMS messaging is only restricted to a maximum of 160 characters. To allow SMS messages longer than 160 characters, you should use a GSM modem or an SMPP provider.

No, at this moment we only support TAP protocol over a dialup connection using a PSTN or ISDN line. You have to use SMPP instead which is an IP based SMS protocol designed for bulk SMS messaging.

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, currently we only support the sending of SMS messages over an UCP dialup connection using a PSTN or ISDN line. You have to use SMPP instead which is an IP based SMS protocol designed for bulk SMS messaging.

When using a dial-up SMSC provider, the number format depends on that particular provider. Suppose you want to send an SMS message to 01234567 in the UK (+44), most common formats are: 01234567, 441234567 and 00441234567.

When using a medium other than a dial-up provider, the requirements are different.

SMS MESSAGE FORMATS

Yes this is possible. You can set this in two ways:

1. Using the registry, using this way, the setting applies for any instance of the object created:
   • Start the registry editor ( REGEDIT.EXE )
   • Open the following key: HKLM\SOFTWARE\SMS and MMS Toolkit\
   • Create a new string "AdvancedSettings" with Value: "ForcePduMode=1"
2. Using the "AdvancedSettings" property of the object, using this way, the setting only applies for the current instance of the object:
   • Set the value of the "AdvancedSettings" property to "ForcePduMode=1"

Yes, it does. You can send almost any character set when sending messages as Unicode. You can send 70 Unicode characters per SMS message. The receiving party must support Unicode messages. Most mobile phones do.

A standard SMS message is can contain up to 160 7-bit characters. However, there are some restrictions:

• Some characters count as two (7-bit) characters instead of one character. Example: the EURO character;
• When using Unicode, you can only send 70 Unicode (16-bit) characters;
• When sending binairy data, you can send 140 (8-bit) bytes.

However, when using multi-part messages, you can send thousands of characters. To use multi-part messages, set the SmsMessage:Format property to asMESSAGEFORMAT_TEXT_MULTIPART.

Flash messages are messages that appear on the mobile phone's display as soon as they are received (without user interaction).

Flash is only supported through the SmsProtocolGsm object and SmsProtocolSmpp object.

To allow an SMS message larger than 160 characters, you must send it as a multi-part message (each part is sent as an individual SMS). The receiver will collect these parts and show the message as a single SMS message.

Please note that the costs for a multi-part messages are based on the number of parts (each part of max. 160 characters is one SMS).

Multi-part SMS is only supported by the SmsProtocolGsm and SmsProtocolSmpp objects.

Yes, multi-part is support, but only when using a GSM Modem or an SMPP or HTTP provider. Multi-part is NOT supported for Dial-up providers.

Yes this is possible. You can set this in two ways:

Using the registry

• Start the registry editor ( REGEDIT.EXE )
• Open the following key: HKLM\SOFTWARE\SMS and MMS Toolkit\
• Create a new string "AdvancedSettings" with Value: "ForceTextMode=1"

Using the "AdvancedSettings" property of the object

Using the "AdvancedSettings" property of the object, using this way, the setting only applies for the current instance of the object:

• Set the value of the "AdvancedSettings" property to "ForceTextMode=1"

SMS MESSAGE FORMATS WAP

Use the built-in WapBookmark encoder to encode messages as WAP Bookmark.

Yes you can. You can do it with a single text SMS. This messages is encoded as SCKL format and works with most mobile phones. Enter the following data in the text field:

   //SCKL23F5 BEGIN:VCALENDAR<CR><LF>
   VERSION:1.0<CR><LF>
   BEGIN:VTODO<CR><LF>
   SUMMARY:meeting at Hengelo<CR><LF>
   DUE: 20061030 T083000<CR><LF>
   STATUS:NEEDS ACTION<CR><LF>
   END:VTODO<CR><LF>
   END:VCALENDAR<CR><LF>

Use the built-in WapPush encoder to encode messages as WAP Push.
For more information, click here.

Yes you can. You can do it with a single text SMS. This messages is encoded as SCKL format and works with most mobile phones. Enter the following data in the text field:

 //SCKL23F4 BEGIN:VCARD<CR><LF>
 N:John Doe<CR><LF>
 TEL:+31647134225<CR><LF>
 END:VCARD

Please have a look at your logfile. If there is a CMS ERROR: 304 in the logfile, your GSM mode does not support an user data header. This is a known problems with Motorola GSM phone and modems.

To send picture messages, you have to use MMS. Various images formats are supported including: JPEG, GIF, PNG, BMP and WBMP. Sending picture messages using SMS is no longer supported.

To send picture messages, you have to use MMS. Various images formats are supported including: JPEG, GIF, PNG, BMP and WBMP. Sending picture messages using SMS is no longer supported.

MM1

When the operator is not sure whether a GSM phone of modem is able to handle MMS messages, it will send a link to their website where you can view the message.
The solution is very simple, just send out a MMS message with this phone or modem and the SIM card you want to use. After this MMS messages will be delivered directly to your GSM modem.

The error means that the software was able to connect to the data network, but wasn't able to connect the MMSC through the specified WAP Gateway or Proxy. There are several factors that might cause this problem:

• There is a problem with the GPRS/UMTS modem; Try another modem;
• You specified an incorrect WAP gateway address; Contact your operator to doublecheck this value;
• The APN specified is incorrect;
• You specified an invalid APN account or password;
• The firewall is blocking traffic to the dialup connection. Try to temporary shutdown any virusscanners and firewalls;
• The IP address assigned to the data connection conflicts with your existing LAN network. Try to disable the LAN network card.
• Try using to send MMS by using WAP version 2.0, there are some providers known to not support version 1.0 any longer. You can switch to WAP2.0 simply, by changing the WAP Gateway IP Address to the WAP proxy (HTTP) address. for instance:
  10.10.200.10 => http://10.10.200.10:8080 (Most providers use port 8080 for WAP proxy server).

This error means: 'The PPP link control protocol was terminated'. When this error occurs, you probably specified an incorrect APN name, APN account or APN password.

MM4

This depends on the provider you are going to use. There are no free MM4 providers around, so you have to subscribe to a commercial MM4 provider or MM4 connection to your local telecom provider.

No, you can't. There are so many different MM4 providers in the world, that we cannot guarantee that our software works with all MM4 providers. You should test the ActiveXperts SMS and MMS Toolkit software with your prefered MM4 provider before you purchase to ensure that the software/provider combination works without any problems.

No we do not have such a list, because this information is not on the internet, because most providers do not advertise for this service, but most operators have a MM4 gateway, so the best is to ask your local network operator.

MM7

This error can have many causes:

• The ProviderAccountName is not correctly set;
• The ProviderAccountPassword is not correctly set;
• The VASPID is not correctly set;
• The VASID is not correctly set;
• The number format is incorrect;
• One of the attachments is rejected.

This depends on the provider you are going to use. There are no free MM7 providers around, so you have to subscribe to a commercial MM7 provider or MM7 connection to your local telecom provider.

No, you can't. There are so many different MM7 providers in the world, that we cannot guarantee that our software works with all MM7 providers. You should test the ActiveXperts SMS and MMS Toolkit software with your prefered MM7 provider before you purchase to ensure that the software/provider combination works without any problems.

No we do not have such a list, because this information is not on the internet, because most providers do not advertise for this service, but most operators have a MM7 gateway, so the best is to ask your local network operator

MMS MESSAGE FORMATS

No, when sending text using an MMS message, the length of the text is only limited by the maximum messagesize set by the provider.3

MMS Toolkit supports the following sound formats: AMR, WAV, MP3, MIDI, AC3.

MMS Toolkit supports the following image formats: JPG, GIF, PNG, BMP, WBMP, TIF.

When a phone does not support MMS, a SMS notification is displayed, indicating where the user can download the MMS contents using its PC.

Yes, it is possible to encode the MMS messagebody as Unicode. The ActiveXperts MMS Toolkit supports Unicode by default, you can directly set the Unicode text when sending an message.

It is possible to send video files using the MM1, MM4 and MM7 protocols. All video formats are supported, but not all phones are able to play these formats. It is always recommended to convert all movies files to 3GPP format (.3GP file extension). For more information on this format, please visit: wikipedia.

This depends on the MMS message size, which is 50K or higher, so there is space enough to type any text you want.
The MMS bodysize is not limited to a couple of characters like SMS.

MMS Toolkit supports the following video formats: 3GP, AVI, MPG, MP4.

MMS works just like email, you can add multiple email or phone numbers to the To, Cc and Bcc address list. Just call the AddRecipient function of the 'MmsMessag' object for each number or email address to be added.

This depends on the provider, but most providers support this feature, instead of specifying the recipient's mobile number, you specifyg the email address.

VISUAL BASIC AND VBSCRIPT

Most probably, you did not install and/or register the ActiveXperts SMS and MMS Toolkit ActiveX component. This component can be installed and registered automatically by running the ActiveXperts SMS and MMS Toolkit installation, or can be downloaded from our website and registered manually by running the command REGSVR32 AXMSCTRL.DLL

Please read the following document: Using SMS and MMS Toolkit with VBScript. This document describes how to refer to the SMS and MMS Toolkit library, and how to declare, create and use the objects.

Please read the following document: Using SMS and MMS Toolkit with Visual Basic 5.x/6.x. This document describes how to refer to the SMS and MMS Toolkit library, and how to declare, create and use the objects.

This is due to the fact that Windows uses the 64bit VBScript intepreter (C:\WINDOWS\SYSTEM32\CSCRIPT.EXE or C:\WINDOWS\SYSTEM32\WSCRIPT.EXE) by default. Since the SMS and MMS Toolkit control is a 32bit control, you should invoke the WOW64 subsystem. This means C:\WINDOWS\SYSTEM32\WOW64\CSCRIPT.EXE or C:\WINDOWS\SYSTEM32\WOW64\WSCRIPT.EXE.

The problem is, that 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 and MMS Toolkit Type Library'.

HTML AND JAVASCRIPT

Please read the following document: Using SMS and MMS Toolkit with HTML. This document describes how to refer to the SMS and MMS Toolkit library, and how to declare, create and use the objects.

Please read the following article: How to digitally sign an ActiveXperts software component.

There are basically three ways to avoid prompting:

1. Add the website that hosts the ActiveX component to the trusted sites of all Internet Explorers. This would need some automatic configuration on your LAN's Internet Explorers, for instance through Group Policy (recommended) or through logon script. This way you only decrease Internet Explorer security for that particular site. Security for all other sites remains the same. This solution only works as long as the SMS and MMS Toolkit users are part of your network.
2. You can sign the component (the actual AXmsCtrl.dll). If you only use the component for internal use (i.e. in your network), you can use the standard Windows Certificate Server (part of Win2000 and higher). For more more information on signing an ActiveX component yourself, see activexperts.com/support/toolkits/sign. If the component is used outside your network, you should use a public Certificate Authority, for instance Verisign.
   ActiveXperts Software does not offer facilities to sign ActiveX COM/OLE components.
3. From the Internet Explorer menu, select "Tools" -> "Internet Options"; dlick the security tab, and click the 'Custom level…' button.
   In the list of options, change the 'Initialize and script ActiveX controls not marked as safe for scripting' setting from disable to prompt. When you restart Internet explorer and run the page again, Internet Explorer will ask you whether to run the control or not. When asked click 'Yes' and the page should work correctly.

VISUAL C++

Please read the following document: Using SMS and MMS Toolkit with Visual Studio C++. This document describes how to refer to the SMS and MMS Toolkit library, and how to declare, create and use the objects.

Yes you can. Visual Studio .NET supports Visual C++ projects. When you open a Visual C++ project for the first time, Visual Studio .NET will first convert the project to the current project format. After conversion, you'll be able to use the project.

NOTE: Visual Studio Express Edition does NOT support Visual C++ MFC projects. See also FAQ#Q4580030.

No you can't. Microsoft Visual Studio Express Edition is a free, lightweight and easy-to-use tool, and has no support for Visual C++ MFC projects.

VISUAL BASIC .NET AND VISUAL C# .NET

You haven't installed and registered the ActiveXperts SMS and MMS Toolkit ActiveX component. This component can be installed and registered automatically by running the ActiveXperts SMS and MMS Toolkit installation, or can be downloaded from our website and registered manually by running the command REGSVR32 AXMSCTRL.DLL

You haven't installed and registered the ActiveXperts SMS and MMS Toolkit ActiveX component properly. This component can be installed and registered automatically by running the ActiveXperts SMS and MMS Toolkit installation, or can be downloaded from our website and registered manually by running the command REGSVR32 AXMSCTRL.DLL.

There are basically two ways to avoid prompting:

1. Add the website that hosts the ActiveX component to the trusted sites of all Internet Explorers. This would need some automatic configuration on your LAN's Internet Explorers, for instance through Group Policy (recommended) or through logon script. This way you only decrease Internet Explorer security for that particular site. Security for all other sites remain the same. This solution only works as long as the SMS and MMS Toolkit users are part of your network.
2. You can sign the component (the actual AXmsCtrl.dll). If you use the component for internal use only(i.e. in your network), you can use the standard Windows Certificate Server (part of Win2000 and higher). For more more information on signing an ActiveX component yourself, see activexperts.com/support/toolkits/sign. If the component is used outside your network, you should use a public Certificate Authority, for instance Verisign.
   ActiveXperts Software does not offer facilities to sign ActiveX COM/OLE components.

In the 'New' dialog, start the MFC AppWizard. When you are asked for compound document support, select 'Container', and choose for 'Automation' support. Don't forget to include AXmsCtrl.h, AXmsConstants.h and AXmsCtrl_i.c (see manual)

This is because of the security in .net which does not allow you to run software from a share.

Please read the following document: Using SMS and MMS Toolkit with Visual C# .NET. This document describes how to refer to the SMS and MMS Toolkit library, and how to declare, create and use the objects.

SMS and MMS Toolkit is compatible with .NET Framework 1.1, 2.0 and 3.x. The .NET samples are created with Visual Studio 2003, and can be used with Visual Studio 2003, Visual Studio 2005 and Visual Studio 2008.

Yes, the ActiveXperts SMS and MMS Toolkit component can be used in .NET development environments like Visual C# .NET, Visual Basic .NET and ASP .NET. During installation, samples for Visual Basic .NET and Visual C# .NET are installed (together with samples for VBScript, Visual C++, Visual Basic and ASP).

Please read the following document: Using SMS and MMS Toolkit with Visual Basic .NET. This document describes how to refer to the SMS and MMS Toolkit library, and how to declare, create and use the objects.

ASP .NET

SMS and MMS Toolkit is compatible with .NET Framework 1.1, 2.0 and 3.0. The .NET samples are created with Visual Studio 2003, and can be used with Visual Studio 2003, Visual Studio 2005 and Visual Studio 2008.

Users of ASP .NET (Visual Basic) should read the following document: Using SMS and MMS Toolkit with ASP .NET (VB). This document describes how to refer to the SMS and MMS Toolkit library, and how to declare, create and use the objects.
Users of ASP .NET (C#) should read the following doucment: Using SMS and MMS Toolkit with ASP .NET (VB).

You need to setup IIS first to be able to use the ASP .NET samples. This applies to both the ASP .Net VB samples as well as the ASP .NET C# samples:

• Open the Control Panel, and select the 'IIS Manager' from the 'Administrative Tools' Folder;
• Righ-click on the 'Default Website' in the tree-view, and choose New->Virtual Directory from the context-menu;
• Click 'Next'; in the 'Alias field', type: 'SendSms' (other names won't work);
• Click Next and select the path to your ASP.NET sample directory ( i.e. "C:\Program Files\ActiveXperts\SMS and MMS Toolkit\Samples\ASP.NET\XmsVb\" );
• Click 'Next' and check the 'Read' and 'Run Scripts' boxes;
• Click 'Next' and 'Finish', your ASP.Net application has been setup now;
• Type http://localhost/xmsvb in the explorer's address bar to start the application;

ASP

Please read the following document: Using SMS and MMS Toolkit with ASP. This document describes how to refer to the SMS and MMS Toolkit library, and how to declare, create and use the objects.

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.

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.

DELPHI

Please read the following document: Using SMS and MMS Toolkit with Borland Delphi. This document describes how to refer to the SMS and MMS Toolkit library, and how to declare, create and use the objects.

COLDFUSION

Please read the following document: Using SMS and MMS Toolkit with ColdFusion. This document describes how to refer to the SMS and MMS Toolkit library, and how to declare, create and use the objects.

ERRORS

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.

CMS ERROR: 512 indicate 'MM establishment failure'. This error occurs when you try to send a message and the module is receiving another one at the same time. This causes a collision in the message transfer protocol resulting in failure in sending the SMS and hence, +CMS ERROR: 512. Sometimes, +CMS ERROR: 512 may also occur when the module is receiving weak signal and is loosing connection.

Some GSM phones and modems support a virtual message storage which allows you to read the SIM and phone memory simultaneously in one read operation. This is supported on most Siemens Phones and Siemens GSM modems.

ERROR: 33150 literally means: Preferred message storage not supported by this device', i.e. the combined message storage is not supported on your device. Please read all SIM (SM) reports first, and change the 'Storage' property to read all Phone (ME) memory messages.

When you encounter this error, please check the following:

• Is the GSM modem or phone correctly connected to the PC?
• Did you select the correct COMxx port numbe or device namer?
• In case of using the direct COM port: Is the correct speed selected?The speed most used for GSM modems is 115200bps.
• In case of a modem driver (like 'Standard 9600 bps Modem'), please check the baudrate selected in the modem properties (from the control panel).
• Restart the GSM phone or modem
• Restart your PC

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 and MMS Toolkit.

You probably did not supply a correct recipient number or the number is rejected by the provider. It is recommended to use international number format when sending SMS or MMS messages. For instance, to send to 0778961234 in the U.K., use the following format: +4478961234.

The 'CMS ERROR 515' is received in the following cases:

• Sending a SMS when the SIM initialization is going on (after rebooting the module).
• Reading a SMS immediately after booting the module when SIM initialization is not yet over.
• Writing a SMS to the memory before SIM initialization is complete.
• Sending more than one SMS at a time or sending a SMS when the response (OK or ERROR) for a previously sent SMS has not been received.

This error only occurs when using Windows Telephony devices (like 'Standard 9600 bps Modem'). There can be multiple reasons for this error:

1. The modem is not connected correctly;
2. The modem does not respond to hayes AT commands;
3. The baudrate selected in the modem propertie dialog from the control panel is invalid;l
4. There is a problem with the driver, please restart the PC.

“+CEER: ERROR 254” means ‘Call impossible’. This error is commonly received when an attempt to make a call fails ("NO CARRIER" indication) because the module is not registered to the network (in low coverage area, or trying to make a call before "+CREG: 1" indication). This error can also be received if the signal strength is very poor (AT+CSQ first value lower than 7) or if the BER is too high (AT+CSQ second value greater than 2).

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).

You will never get this error when using direct COM ports (like 'COM1'), but only when using Windows Telephony devices.

In this case, the '+CEER: Error 42' is due to repeated sending of SMS which has cause congestion in the network. The AT+CMMS command can be used to keep the MM Channel opened while sending several SMS.

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').

Please check the following:

• Is another application using this por?
• Is Microsoft ActiveSync installe? If yes disable it.
• Is Nokia PC Suite installed?If yes disable or temporary uninstall it.
• Is there an incoming RAS connection defined on this port?
• Please try to reboot the PC

The name of this error is ESME_RTHROTTLED, which means, throttling error. You are sending messages too fast. Insert a delay between the send calls, or set the SystemThroughput property of the SMPP interface.

Click here to view the list of all ActiveXperts error codes.

CMS ERROR: 513 means 'lower layer failure'. This error indicates a logical link failure or a RR sub-layer failure to the GMM sub-layer. The failure indicates an error that cannot be corrected by the lower layers. There could be three possible reasons for getting a +CMS ERROR: 513.

• The MS loses the radio link (or the network requests an RR disconnect).
• The MS does not receive an acknowledgement from the network for 28s after the transmission of the Short Message data and times out.
• The MS does not receive an acknowledgement from the network for 42s after the channel establishment request and times out.

Please have a look at your logfile. If there is a CMS ERROR: 304 in the logfile, your GSM mode does not support an user data header. This is a known problems with Motorola GSM phone and modems.

This error means "Protocol Error". It sometimes appears when sending bulk SMS over GSM phones that are not designed to send much SMS messages at a time. Please use a GSM modem like WaveCom, Samba or Siemens instead.

To allow long messages (i.e. > 160 characters), you must set the SmsMessage::Format property to asMESSAGEFORMAT_TEXT_MULTIPART (or when using Unicode: asMESSAGEFORMAT_UNICODE_MULTIPART). This applies to the SmsProtocolGsm object and SmsProtocolSmpp object.

When this property is set, SMS and MMS Toolkit will send long messages as multiple SMS messages. These messages are collected and shown as one single message on the remote user's mobile phone.

See FAQ #Q5200115.

See FAQ #Q5200115.

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.

Following are the reasons for +CMS ERROR: 514 (CP Error).

• Network failure.
• Congestion in the network.
• Invalid transaction identifier value.
• Semantically incorrect message.
• Invalid mandatory information (for example: invalid service center address or invalid destination address).
• Message type non-existent and not implemented.
• Message not compatible with the short message protocol stage.
• Information element non-existent and not implemented.
• Protocol error.

This error only occurs when using Windows Telephony devices (like 'Standard 9600 bps Modem'). There can be two reasons for this error:

1. The Windows Telephony device is already in use by another application;
2. There is a PIN code on the SIM card. When TAPI tries to initialize this modem, it receives an error from the modem because the PIN Code has to be entered before any other command can be send to the modem. Removing the PIN code from the SIM card will solve this problem. The PIN code can be removed via the security settings of a cellphone.

CMS ERROR 302 means "Operation not allowed". Possible reasons for this error are:

• The service may be unavailable during that time
• Service provider has locked the service
• Corporate lock is active
• Module was powered off by +CPOF, CFUN=0, unplug, or Low battery level
• Service not correctly loaded
• SIM does not support SMSCB

'+CMS ERROR: 96' means: "Invalid mandatory information". This error indicates that the equipment sending SMS has received a message where a mandatory information element is missing and/or has a content error.

SMS is composed of message and mandatory information elements. If the information element received by the network is syntactically incorrect or some part is missing or information element is unknown, network sends error "Invalid mandatory information".

There can be two reasons:

1. You are sending in Unicode mode; you can only send 70 bytes per Unicode SMS message. If you want to send messages longer than 70 character, you must enable 'multi-part' (a property of the SmsMessage object);
2. You are sending the message as non-Unicode (default) but the message includes some characters that are send as two characters. These characters are : ^ { } [ ] / ' ~ | and the Euro sign.
   When using these characters, you may exceed the standard 160 character limit without even be aware of it.

Most probably you have a slow connection to the provider, the provider is busy or the provider does not support the asynchronous protocol. Please try to increase the value of the ServerTimeout property.
If this does not help, please contact your provider to help you debug the connection.

It is very important to use the right format for the recipient. The syntax of the recipient number is different for SMPP providers, HTTP providers, GSM modems and Dial-up numbers. Check it out on the according page.

LICENSING, PURCHASING, PRODUCT ACTIVATION AND SUPPORT

The 'Distribution License' allows you to 'bundle' the toolkit 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 restrictions in functionality of the software, and includes multiline send and receive as well as SMPP.

Click here for more information about the ActiveXperts SMS and MMS Toolkit Licensing Scheme.

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.

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.

The 'Professional License' supports the SMPP, MM4 and MM7 protocols; the Standard license doesn't. The 'Professional License' allows you to use multiple devices/connections simultaneously.

Click here for more information about the ActiveXperts SMS and MMS Toolkit Licensing Scheme.

You can purchase the product online, by proforma invoice (bank or cheque) or through a reseller. For more information, check the Sales webpage.

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.

After 30 days of evaluation, you cannot use the 'SendMessage' and 'Receive' functions anymore. When calling these functions this function, nothing happens and LastError will be set to asERR_EVALUATIONEXPIRED (value: 1001).

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.

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 payed for the product.

Customers choose between one-, two- and three years Maintenance Agreement renewal. Please read the Maintenance Agreement document for more details.

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.

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).

There are three ways to activate the product:

1. By running the Setup program - it will ask for the key;
2. By calling the Activate function;
3. By entering the key in the registry manually.

A detailed description is provided in the manual, in chapter Purchase and Product Activation.