Protocol '[PROT]' not supported for this user. Check 'Type' settings in configuration file.

1111

ERROR_IFTCPCLIENT_SMPP_CLIENTTIMEOUT

Timeout. No response received for PDU '[PDUTYPE]'

1112

ERROR_IFTCPCLIENT_SMPP_FORCEOUT

Another SMPP client ([CLIENTNAME]) is logged in with this username and password. That client is going to be disconnected because only one client instance is allowed to connect with a single username and password. Use a different username to connect with a second instance! Configure your client to connect as SMPP transceiver!

Could not find message reference in submit response. Delivery reports will not be handled correctly.

1363

ERROR_DRIVER_ENVSUBMIT_ERROR_NOTACCEPTED_REASON

Envelope rejected by SMSC. [MSG]

1364

ERROR_DRIVER_ENVSUBMIT_ERROR_NOTDELIVERED

Delivery report received that sais could not deliver message to recipient. [ERRORMSG]

1365

ERROR_DRIVER_ENVSUBMIT_NOTSENT

Message could not be sent. Reason: [MSG]

1366

ERROR_DRIVER_ENVSUBMIT_ERROR_INVRESP

Envelope could not be sent by modem. [ERRORMSG]

1367

ERROR_DRIVER_ENVSUBMIT_NOTACCEPTED

The SMSC returned a not accepted response. [MSG]

1400

ERROR_DRIVER_GSMMODEM_BASE

1401

ERROR_DRIVER_GSMMODEM_SIM_SMSC_DIFFERENCE

The address of SIM SMSC ([SIMSMSC]) is different from the address of SMSC specified in the configuration form ([SETSMSC])

1402

ERROR_DRIVER_GSMMODEM_SIM_SMSC_AND_SET_SMSC_EMPTY

Both, the address of SIM SMSC and the address of SMSC specified in the configuration form are empty! You have to specify an SMSC to make SMS working. Check: http://www.ozekisms.com/index.php?owpn=199

1403

ERROR_DRIVER_GSMMODEM_SIM_SMSC_SET_SMSC_EMPTY

Cannot read SMSC from SIM and the SMSC specified on the configuration form is empty!

1404

ERROR_DRIVER_GSMMODEM_PINEMPTY

A PIN code needs to be entered to start the modem, but no PIN code is defined in the 'Pin code' field of the 'Port settings' tab of the configuration form. Please specify the PIN code in the configuration form!

1405

ERROR_DRIVER_GSMMODEM_CANNOTDECODE_DELIVERYREPORT

Cannot decode delivery report [PDU]

1406

ERROR_DRIVER_GSMMODEM_MMS_ CANNOTDOWNLOAD_NODOWNLOADURL

Cannot download MMS message, because no download URL was found in the MMS Indication message.

MMS download failed. We have tried to download this MMS message too many times from the MMSC without success. [URL]

1413

ERROR_DRIVER_GSMMODEM_CANNOTOPENPORT

Cannot connect to port [PORT]. [MSG]. The port you want to access might be used by another process. Please make sure that no other SMS or modem software is running, that uses this port. It might also be possible that an MMS sending/receiving procedure was unexpecdly interrupted. If you issue the following command in a windows command shell: rasdial /disconnect, the problem might be resolved. As a final option if you reboot your computer, there is a good chance this error will not occur.

1414

ERROR_DRIVER_GSMMODEM_NORESPONSE

Port has been successfully opened, but no response has been received from modem on [PORT].Check data cable, or try different baud rate! Is your GSM phone or modem powered on?

Cannot send response message. The response limit forbids sending more then [NUM] responses to the same number. For more information, please visit http://www3.ozekisms.com/index.php?owpn=203. Message: [MSG]

1610

ERROR_USERFILE_CLEANUP_EXCEPTION

Error wile deleteing lock files in '[FUNCTION]'. Exception: [MSG]

1611

ERROR_USERFILE_NOTFOUND

Could not find file [FILENAME]. It was probably deleted while beeing processed. [MSG]

The number format for the recipient phone number is a local number format. It does not start with a + sign. If you cannot submit this messages, please try to use international number format (plus sign + country code + number). It might be better to use '+[NUM]' instead of '[NUM]'.

2324

WARN_DRIVER_GSMMODEM_RESPONSE_TIMEOUT

Modem Timeout. The modem did not respond to the command. Is it plugged in?

No response received from SMSC to transaction [TRN], timeout value is [TIMEOUT].

2360

WARN_DRIVER_PARLAYX_CALLBACKNOTSUPPORTED

Callbacks are not available in ParlayX version 2.0. Disabling callback requests.

2361

WARN_DRIVER_PARLAYX_DELIVERYCALLBACK_NOT_SUPPORTED

Delivery report callbacks in ParlayX Version 2.0 are not supported

2500

WARN_USER_BASE

2501

WARN_USER_ALREADY_ENABLED

User has already been enabled.

2502

WARN_USER_ALREADY_DISABLED

User has already been disabled.

2510

WARN_USER_MESSAGESTORE_CANNOTDOWNLOAD_MESSAGELIST

Cannot read message from queue [QUEUE]. [REASON]

2511

WARN_USER_MESSAGESTORE_CANNOTREAD_MESSAGE

Error while reading message in outbox queue. [MSG]

2512

WARN_USER_MESSAGESTORE_CANNOTMOVE_MESSAGE

Cannot move file from [SOURCEFILE] to [DESTFILE]. [MSG]

2513

WARN_USER_MESSAGESTORE_CANNOTSAVE_ENVELOPE

Cannot save envelope [FILE]. Saving it to file [NEWFILE]. [MSG]

2514

WARN_USER_MESSAGESTORE_CANNOTDELETE_ENVELOPE

Cannot delete envelope [FILE]. Creating error file [ERRFILE]. [MSG]

2515

WARN_USER_MESSAGESTORE_MESSAGE_NOTFOUND

Message [MSGID] not found in queue. Removing reference

2530

WARN_USER_SQL_INVALIDCHAR_IN_SQLTEMPLATE

Invalid character(s) in SQL template. There is a (hidden) unicode character in the template. It is possible that you have used copy paste to insert it. Type your templates manually. If you want to use unicode characters, you must enable unicode template support on the Advanced tab of the confiugration form! Unicode characters are now removed from the template.

2531

WARN_USER_SQL_ODBCNOTSUPPORTED_FORMSSQLSERVER

This seems like an ODBC connection string for Microsoft SQL Server. We recommend to use OLEDb provider SQLNCLI for Microsoft SQL Server connections. ODBC can cause problems. More information is available at: http://www.ozekisms.com/index.php?owpn=167

2540

WARN_USER_EMAIL_MESSAGE_FILTERED

Can't send the following SMS, because e-mails are filtered: [SMS]

2541

WARN_USER_EMAIL_MESSAGELOOP_DANGER

This e-mail will be not sent as SMS to prevent SMS loops remove the SMS/REPORT tag from the subject line. [SMS]

Delivery report dropped, because no matching envelope found in system for callback ID '[CID]'. This error can happen in two cases: The message was sent more then 1 week ago or the message reference (callback ID) returned by the SMSC during sending does not match the callback ID in the delivery report. [ENV]

3200

INFO_ENCODING_BASE

3201

INFO_ENCODING_PDUCOUNT

Message will be sent using [COUNT] PDU(s).

3202

INFO_ENCODING_CHARSETINFO

Encoding information: Message length is [MSGLEN]. It is encoded as [CHARSET]. It will be sent in [PARTCOUNT] message(s).