SQLBOX and Kannel 1.4.1

[Cavit Dolgun]

I tried using sqlbox stand alone with the cvs version of kannel (2006-07-23)
and it works fine.

The only thing that I couldn't manage to do was to send Unicode messages
(Arabic).

You can download the standalone version from:

http://www.kannel.org/~mconte/sqlbox/sqlbox-standalone.tar.gz

Quick compile:

# ./bootstrap
# ./configure
# make

I remember saving some extra information about the database fields in
sqlbox.

 Here it is:


momt:
  Description:
    Indicates whether the SMS is a Mobile Originated (from mobile user
    to an sms-service) or Mobile Terminated (from your application to
    the mobile user).
  Supported Values:
    'mt', 'mo'
  Kannel SMS Msg structure equivalent:
    Not Applicable (specific to the sqlbox)

sender:
  Description:
    The origination address.
  Supported Values:
    Any alphanumeric value.
  Kannel SMS Msg structure equivalent:
    sms.sender

receiver:
  Description:
    The destination address.
  Supported Values:
    Any alphanumeric value.
  Kannel SMS Msg structure equivalent:
    sms.receiver

udhdata:
  Description:
    The User Data Header that will be prefixed to the SMS message content.
  Supported Values:
    Hexadecimal values
  Kannel SMS Msg structure equivalent:
    sms.udhdata

msgdata:
  Description:
    The SMS message payload
  Supported Values:
    140 8-bit values. If a UDH is also specified for the SMS, then the
    maximum length of the msgdata is 140-length(udhdata).
  Kannel SMS Msg structure equivalent:
    sms.msgdata

time:
  Description:
    The GMT time when the SMS was placed into the sqlbox.  This value
    represents the number of seconds since the UNIX EPOCH (Jan 1, 1970).
  Supported Values:
    Any decimal value.
  Kannel SMS Msg structure equivalent:
    sms.time

smsc_id:
  Description:
    The SMSC ID that should or did handle the SMS.
  Supported Values:
    Any alphanumeric value.
  Kannel SMS Msg structure equivalent:
    sms.smsc_id

service:
  Description:
    The sms-service name that was executed on behave of the SMS.
  Supported Values:
    Any alphanumeric value.
  Kannel SMS Msg structure equivalent:
    sms.service

account:
  Description:
    The auxiliary account name or number associated with the SMS
    (mustly seen in HTTP relays).
  Supported Values:
    Any alphanumeric value.
  Kannel SMS Msg structure equivalent:
    sms.account

id:
  Description:
    The unique ID assigned to each SMS handled by the Kannel system.
  Supported Values:
    Format is: dddddddd-dddd-dddd-xxxx-xxxxxxxxxxxx
    dddddddd -> time_low
    dddd -> time_mid
    dddd -> time_hi_and_version
    xxxx -> clock_sequence
    xxxxxxxxxxxx -> node_id (usually interface ethernet address that this
      SMS was received from)
  Kannel SMS Msg structure equivalent:
    sms.id

sms_type:
  Description:
    The Kannel type of the SMS (MO or DLR)
  Supported Values:
    0 = MO (coming from the operator on behave of a mobile user)
    1 = MT_REPLY (coming from an sms-service)
    2 = MT_PUSH (coming from an application external from Kannel)
    3 = REPORT_MO (DLR from the operator)
    4 = REPORT_MT (DLR from Kannel to the operator)
  Kannel SMS Msg structure equivalent:
    sms.sms_type

mclass:
  Description:
    The Message Class of the SMS as defined in the Data Coding Scheme
    (DCS) Field.
  Supported Values:
    0 = sends the message directly to display.
    1 = sends to mobile
    2 = sends to SIM
    3 = sends to SIM Toolkit.
  Kannel SMS Msg structure equivalent:
    sms.mclass

mwi:
  Description:
    The Message Wait Indicate of the SMS as defined in the DCS field.
  Supported Values:
    0 = Voice indicator
    1 = Fax indicator
    2 = Email indicator
    3 = Other inidicator
    4 = Deactivate voice indicator
    5 = Deactivate fax indicator
    6 = Deactivate email indicator
    7 = Deactivate other indicator
  Kannel SMS Msg structure equivalent:
    sms.mwi

coding:
  Description:
    The Kannel encoding value of the SMS
  Supported Values:
    0 = default/GSM 7 encoding
    1 = Binary 8-bit encoding
    2 = UCS-2 Double-byte encoding
  Kannel SMS Msg structure equivalent:
    sms.coding

compress:
  Description:
    The sets or unsets the compression bit of the DCS field.
  Supported Values:
    0 = compression bit unset
    1 = compression bit set
  Kannel SMS Msg structure equivalent:
    sms.compress

validity:
  Description:
    The lifetime of the SMS in minutes.
  Supported Values:
    Any numeric value.
  Kannel SMS Msg structure equivalent:
    sms.validity

deferred:
  Description:
    The number of minutes the SMSC should wait before attemping to
    deliver the SMS.
  Supported Values:
    Any numeric value.
  Kannel SMS Msg structure equivalent:
    sms.deferred

dlr_mask:
  Description:
    A mask specifying the types of Delivery Reports of interest.
  Supported Values:
    1 = Delivered to mobile device
    2 = Not delivered to mobile device
    4 = Queued on SMSC
    8 = Delivered to SMSC
   16 = Not delivered to SMSC
  Kannel SMS Msg structure equivalent:
    sms.dlr_mask

dlr_url:
  Description:
    The URL fetched via HTTP_GET when Kannel receives an DLR.
  Supported Values:
    Any alphanumeric value in the form of a URL. The URL must be
url-encoded.
  Kannel SMS Msg structure equivalent:
    sms.dlr_url

pid:
  Description:
    The higher-layer Protocol ID associated with the SMS payload. This
    can be used for indication of telematics, replacement of similar SMS,
    etc. Consult Section 9.2.3.9 of 3GPP TS 23.40.
  Supported Values:
    Any decimal between 0 and 127, inclusive.
  Kannel SMS Msg structure equivalent:
    sms.pid

alt_dcs:
  Description:
    Indicates an alternative DCS setting method.
  Supported Values:
    -1 = Uses the alt-dcs defined on smsc configuration (if any)
    0 = 0X.
    1 = FX.
    2 = Force 0X (regardless of smsc configuration).
  Kannel SMS Msg structure equivalent:
    sms.alt_dcs

rpi:
  Description:
    Set or unset the Return Path Indicator.
  Supported Values:
    0 = unset
    1 = set
  Kannel SMS Msg structure equivalent:
    sms.rpi

charset:
  Description:
    The message payload character set.
  Supported Values:
    Any valid character set as defined in RFC.
    Some commons ones are: ISO-88590-1, UTF-8, UTF-16BE.
  Kannel SMS Msg structure equivalent:
    sms.charset

boxc_id:
  Description:
    The name of the bearbox which handles this SMS.
  Supported Values:
    Any alphanumeric value.
  Kannel SMS Msg structure equivalent:
    sms.boxc_id

binfo:
  Description:
    Billing identifier/information proxy field used to pass arbitrary
    billing transaction IDs or information to the specific SMSC modules.
    For EMI2 this is encapsulated into the XSer 0c field, for SMPP this
    is encapsulated into the service_type of the submit_sm PDU.
  Supported Values:
    Any alphanumeric value.
  Kannel SMS Msg structure equivalent:
    sms.sender





If anyone has any idea on how to send Unicode message using sqlbox please
let me know.

Ragards,

Cavit





-----Original Message-----
From: Mi Reflejo [mailto:reflejo at gmail.com] 
Sent: Saturday, October 28, 2006 10:16
To: info.ubichip at free.fr
Cc: users at kannel.org
Subject: Re: SQLBOX and Kannel 1.4.1

try sqlbox standalone module and share your experience!

M

On 10/27/06, info.ubichip at free.fr <info.ubichip at free.fr> wrote:
>
> Hi all,
>
> Is SQLBOX is still compatible with the new version of Kannel ?
> Is it any new patch to run it ?
>
> Does someone has a procedure to install it ?
>
> I would like to still have the table sent_sms when I send/receive SMS
through
> kannel.
>
> Thanks for answer
>
>