a85d SMS Gateway - Database user, Keywords

                

Search the manual:

Overview Quick start Download Manual How to buy FAQ Contact Us
OZEKI NG SMS Gateway - Product Guide

Connection string builder Contents | SearchBatch processing

Home > Product Manual > Installation Guide > Users and applications > Database user > Keywords

SMS Gateway SMS Gateway Home

  Product Manual
  Introduction
  SMS technology
  Installation Guide
  Prerequisites
  Download Information
  Installation Steps
  Service Provider Connections
  Users and applications
  Standard user
  SMPP user
  Database user
  MSSQL
  MySQL
  Oracle
  Sybase SQL Anywhere
  PostgreSQL
  Pervasive SQL
  Date Format Strings
  Scheduled SMS
  SQL templates
  Informix
  Access
  Video
  Connection string builder
  Keywords
  Batch processing
  SQL statements
  Polling technology
  Dynamic Keywords
  Dynamic SMPP parameters
  AutoreplyDatabase user
  Autoreply user
  AutoReplyEasy user
  File user
  E-mail user
  HTTP Client user
  Colour SMS user
  Appstarter user
  SMS Voting
  Outlook Mobile Service
  FTP user
  PDF user
  WCF Client User
  Forwarder user
  Linux
  User Guide
  Developers Guide
  Examples and Solutions
  Appendix
  FAQ
  Feature list
  Commercial Information
  Search
 

Contact Us!
If you wish to get further information, do not hesitate to contact us!

E-mail: info@ozekisms.com

If you have a technical question, please submit a support request on-line.


Callcenter developers
If you are working on telephone solutions, please check out the Ozeki VoIP SIP SDK.
It can be used to create:

Webphone solutions:
- Adobe Flash video phone
- Silverlight video phone
- Web to web calls
- Web to VoIP calls

Custom SIP clients:
- Silverlight SIP VoIP client
- Flash SIP VoIP client
- C# .net SIP VoIP client
- ASP .net SIP VoIP client
- Web based SIP VoIP client

Custom VoIP solutions:
- VoIP SIP softphones
- VoIP call center clients
- VoIP IVR systems
- VoIP predictive dialer systems
- VoIP auto dialer systems
- VoIP call assistant
- VoIP call recording systems
- VoIP intercom solutions

Keywords in the SQL templates


KeywordValue Incoming (insert) Outgoing polling (select) Outgoing sending (update) Outgoing sent (update) Outgoing not sent (update) Outgoing delivered (update) Outgoing undelivered (update)
$idMessage ID + + + + + + +
$senttimeSent time in the format specified on the confguration form +     + +    
$receivedtimeReceived time in the format specified on the confguration form +       +    
$messagedataMessage text + + + + + + +
$decodedmessagedataThe 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. +   + + + + +
$senderSender address + + + + + + +
$originatorSame as $sender + + + + + + +
$receiverRecipient address + + + + + + +
$recipientSame as $receiver + + + + + + +
$messagetypeOzeki message type + + + + + + +
$operatornamesThe 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.   +          
$operatorThe name of the service provider connection to use + +   +      
$subjectThe message subject (for SMS messages, the first 1024 characters of the message text) +            
$callbackidThe message submission reference number       +      
$costThe cost of a message (the number of PDUs used to submit it)       +      
$reasonThe error reason         +   +
$currentdatetimeCurrent date and time in the format specified on the confguration form +   + + + + +
$currentdateCurrent date in the format yyyy-MM-dd +   + + + + +
$currenttimeCurrent time in the format HH:mm:ss +   + + + + +
$1The first word in the message. You can use $2 to refer to the second word, $3 to refer to the third word, etc... +            
$U1The 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
$dcshexThe data coding scheme (DCS) byte of the PDU in hexadecimal format +     +      
$dcsThe data coding scheme (DCS) byte of the PDU in decimal format +     +      
$pidhexThe protocol identifier (PID) byte of the PDU in hexadecimal format +     +      
$pidThe protocol identifier (PID) byte of the PDU in decimal format +     +      
$udhplusudThe user data header and the user data in hexadecimal string format of the first pdu +     +      
$udhThe user data header in hexadecimal string format of the first pdu +     +      
$udThe user data in hexadecimal string format of the first pdu +     +      
$scaService center address +     +      
$tp_mmsThe TP_MMS flag of the first byte of the PDU. (true or false) +     +      
$tp_mtThe TP_MT flag of the first byte of the PDU. (true or false) +     +      
$tp_rpThe TP_RP flag of the first byte of the PDU. (true or false) +     +      
$tp_srrThe TP_SRR flag of the first byte of the PDU. (true or false) +     +      
$tp_udhiThe TP_UDHI (User data header inidication) flag of the first byte of the PDU. (true or false) +     +      
$messageclassThe message class value is a decimal number +     +      
Multipart SMS messages
$pducountThe number of PDUs in the message +     +      
$pdu1_udhudThe 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_udhThe user data header in hexadecimal string format of the first pdu. For the second pdu this would be $pdu2_udh, etc... +     +      
$pdu1_udThe user data in hexadecimal string format of the first pdu. For the second pdu this would be $pdu2_ud, etc... +     +      
$pdu1_rawheaderThe pdu header in hexadecimal string format of the first pdu. For the second pdu this would be $pdu2_rawheader, etc... +     +      
$pdu1_rawbodyThe same as $pdu1_udhud. For the second pdu this would be $pdu2_rawpdu, etc... +     +      
$pdu1_rawpduThe first pdu in hexadecimal format. For the second pdu this would be $pdu2_rawpdu, etc... +     +      
$rawpdusContains all pdus separated by a semi colon; +     +      
Optional fields
$fieldnameField 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.   + + + + + +


Dig deeper!
People who read this also read...





Next page: Batch processing
Copyright © 2000 - 2013 Ozeki Informatics Ltd.
All rights reserved

Software PBX for Windows | VoIP SDK   |   Legal information   |   Privacy policy   |   Terms of use
Please, address your inquiries to info@ozekisms.com


0