SendSMS Frequently Asked Questions

Why do I always get the error -23 althoughther is a device defined?
You have selected a provider which reuieres a different type of device. For example if you select select a provider with LINETYPE=ISDN and there is only a modem (LINETYPE=ANALOG) defined you will get this error.

What means the errornumber -10?
The service-computer has to send at the beginning of a TAP-session the string ID=. The errornumber -10 indicates that SendSMS didn't receive that string and thatswhy was not able to continue. Maybe the workload on the service-computer was too big at that time and it will work if you try it again at a later time. Maybe the service-computer doesn't support the TAP-protocol, then you have to edit the file sendsms.pro and change the protocol for the provider from TAP to UCP (this only happens if you specified a new provider-definition which wasn't preconfigured). When both doesn't work then there is a problem reading from the device. In that case try to set WAITAFTERWRITE and/or WAITAFTERCONNECT.

What means the errornumber -16?
SendSMS got a connection to the service-provider, but the provider didn't accept the message. This can be a temporary problem (too much workload on the service-computer) or you have specified the wrong protocol for the provider. If the provider uses UCP you have to set the MODEMINIT parameter to the command to switch your modem to V.42/LAPM. If theis isn't possible set WAITAFTERCONNECT to about 2 seconds (maybe more, you have to try).

What means the errornumber -34?
SendSMS didn't get a connection to the service-provider. Maybe your modem is blocked by another program, all incoming lines of the provder are busy or you have specified the wrong protocol (TAP) for the provider.

How can I use ISDN- and analog numbers in one configuration?
Specify in sendsms.cfg one device with TYPE=0 for the analog providers and one device with TYPE=1 for the ISDN-providers. In sendsms.pro you set for all providers which can be connected via ISDN TYPE=1, then the ISDN-device is automically used.

Why does SendSMS get a connection to the service-provider, but can't send the message?
This can be a temporary problem, so try it again. If the error still occurs check the settings for the provider and the modem-settings. If all is correct try differnet settings for the parameters WAITAFERCONNECT, RTSCTS and WAITAFTERWRITE.

What means WAITAFTERCONNECT?
For the UCP-protocol the modem has to use V.42/LAPM. If this isn't possible SendSMS has to wait after the modem got a CONNECT up to 15 seconds (protocol-specification).

Why are in sendsms.pro the additional parameters MODEMINIT, BAUD, ...?
In sendsms.cfg you specify the global settings for your devices, which are used for all providers. But some providers need special settings which you can specify in sendsms.pro and which are only used for the corresponding provider.

I can send messages to D1 and D2 but Scall and Skyper doesn't work
Using Scall and Skyper with a modem you have to set MODEMINIT in sendsms.pro in a manner to tell the modem not to filter XON/XOFF characters.

How can I send messages to Scall, Skyper or CityRuf using ISDN?
If you are using CAPI 2.0 you can use the predefined providers with the extension _ISDN. If you are using a ISDN terminaladapter or any device driver you have to define a MODEMINT-string (in sendsms.pro) to use the correct protocols (B2=X.75, B3=T.70NL/T.90NL).

Why can I not read received messages with my GSM-card?
You have to specify the memory from wich the messages should be read (AT+CPMS=""). You can do this in the INIT2-Parameter in the Device-chapter in sendsms.cfg.

How can I use mutiple ISDN-adapters with SendSMS?
Define multiple devices (DEVICETYPE=CAPI 2.0) in sendsms.cfg each with different values for the parameter CONTROLLER.

I'm using CAPI 2.0 and can't get any connection?
Maybe you haven't set the parameter ISDNPHONE in sendsms.cfg or you have set a wrong number. Some PBX doesn't allow to connect if you are using a wrong number.

I can send SMSs with my GSM-card, but I can't read incoming messages
Maybe you have to set a different memory address in the parameter INIT2 in the chapter [Device] in sendsms.cfg (for example: INIT2=AT+CPMS="SM").