- Product Manual
- Introduction
- SMS technology
- Installation Guide
- Prerequisites
- Download Information
- Installation Steps
- GSM Modem Setup
- Service Provider Connections
- Users and applications
- Standard user
- SMPP user
- SMS from or to database
- MSSQL
- MySQL
- Oracle
- Sybase SQL Anywhere
- PostgreSQL
- Pervasive SQL
- Date Format Strings
- Scheduled SMS
- SQL templates
- Informix
- Access
- Video
- Connection string builder
- Keywords
- MS SQL high speed
- Oracle High Speed
- SQL statements
- Polling technology
- Dynamic Keywords
- Dynamic SMPP parameters
- Autoreply SMS from database
- Autoreply SMS using a script
- Simple autoreply SMS
- SMS from/to file
- SMS through E-mail
- SMS via HTTP Request
- SMS via colour protocol
- Application starter SMS
- SMS Voting
- SMS from MS Outlook
- SMS from/to FTP server
- PDF Request in SMS
- SMS to WCF service
- SMS Forwarder
- RSS to SMS
- Linux
- User Guide
- Developers Guide
- Examples and Solutions
- Appendix
- SMS FAQ
- Feature list
- Commercial Information
- Search
Ozeki NG SMS Gateway
Keywords in the SQL templates
Keyword | Value | Incoming (insert) | Outgoing polling (select) | Outgoing sending (update) | Outgoing sent (update) | Outgoing not sent (update) | Outgoing delivered (update) | Outgoing undelivered (update) |
$id | Message ID | + | + | + | + | + | + | + |
$senttime | Sent time in the format specified on the confguration form | + | + | + | ||||
$receivedtime | Received time in the format specified on the confguration form | + | + | |||||
$messagedata | Message text | + | + | + | + | + | + | + |
$decodedmessagedata | The decoded text for text messages and a hex string for binary messages. This is different then $messagedata since the $messagedata field will try to decode all data as text. | + | + | + | + | + | + | |
$sender | Sender address | + | + | + | + | + | + | + |
$originator | Same as $sender | + | + | + | + | + | + | + |
$receiver | Recipient address | + | + | + | + | + | + | + |
$recipient | Same as $receiver | + | + | + | + | + | + | + |
$messagetype | Ozeki message type | + | + | + | + | + | + | + |
$operatornames | The names of the service provider connections, that can be used to send this message. The names can be separated by a semicolon or a colon. | + | ||||||
$operator | The name of the service provider connection to use | + | + | + | ||||
$subject | The message subject (for SMS messages, the first 1024 characters of the message text) | + | ||||||
$callbackid | The message submission reference number | + | ||||||
$cost | The cost of a message (the number of PDUs used to submit it) | + | ||||||
$reason | The error reason | + | + | |||||
$errormessage | The error message | + | + | |||||
$currentdatetime | Current date and time in the format specified on the confguration form | + | + | + | + | + | + | |
$currentdate | Current date in the format yyyy-MM-dd | + | + | + | + | + | + | |
$currenttime | Current time in the format HH:mm:ss | + | + | + | + | + | + | |
$1 | The first word in the message. You can use $2 to refer to the second word, $3 to refer to the third word, etc... | + | ||||||
$U1 | The first word in the message in upper case format. You can use $U2 to refer to the second word in upper case format, etc... | + | ||||||
SMS message related fields | ||||||||
$dcshex | The data coding scheme (DCS) byte of the PDU in hexadecimal format | + | + | |||||
$dcs | The data coding scheme (DCS) byte of the PDU in decimal format | + | + | |||||
$pidhex | The protocol identifier (PID) byte of the PDU in hexadecimal format | + | + | |||||
$pid | The protocol identifier (PID) byte of the PDU in decimal format | + | + | |||||
$udhplusud | The user data header and the user data in hexadecimal string format of the first pdu | + | + | |||||
$udh | The user data header in hexadecimal string format of the first pdu | + | + | |||||
$ud | The user data in hexadecimal string format of the first pdu | + | + | |||||
$sca | Service center address | + | + | |||||
$tp_mms | The TP_MMS flag of the first byte of the PDU. (true or false) | + | + | |||||
$tp_mt | The TP_MT flag of the first byte of the PDU. (true or false) | + | + | |||||
$tp_rp | The TP_RP flag of the first byte of the PDU. (true or false) | + | + | |||||
$tp_srr | The TP_SRR flag of the first byte of the PDU. (true or false) | + | + | |||||
$tp_udhi | The TP_UDHI (User data header inidication) flag of the first byte of the PDU. (true or false) | + | + | |||||
$messageclass | The message class value is a decimal number | + | + | |||||
Multipart SMS messages | ||||||||
$pducount | The number of PDUs in the message | + | + | |||||
$pdu1_udhud | The user data header and the user data in hexadecimal string format of the first pdu. For the second pdu this would be $pdu2_udhud, etc... | + | + | |||||
$pdu1_udh | The user data header in hexadecimal string format of the first pdu. For the second pdu this would be $pdu2_udh, etc... | + | + | |||||
$pdu1_ud | The user data in hexadecimal string format of the first pdu. For the second pdu this would be $pdu2_ud, etc... | + | + | |||||
$pdu1_rawheader | The pdu header in hexadecimal string format of the first pdu. For the second pdu this would be $pdu2_rawheader, etc... | + | + | |||||
$pdu1_rawbody | The same as $pdu1_udhud. For the second pdu this would be $pdu2_rawpdu, etc... | + | + | |||||
$pdu1_rawpdu | The first pdu in hexadecimal format. For the second pdu this would be $pdu2_rawpdu, etc... | + | + | |||||
$rawpdus | Contains all pdus separated by a semi colon; | + | + | |||||
Optional fields | ||||||||
$fieldname | Field name is the name of a database column that was included in the select statement used to originally pick up the message. This keyword will hold the value of this column in all subsequent updates. | + | + | + | + | + | + |
More information