how kannel matched the received DLR

2010-01-26 Thread hafez ahmad
Dears,

Please can anyone help me to know how kannel matched the received DLR with
the stored DLR, I get sometimes the error got DLR but could not find message
or was not interested in it id1983706424 dst955342324564, type1  , I
checked the msg-id-type and it is set correct but as you note that I add the
DLR with MSISDN start with +

 SMSC[MT_BILLING]: DLR =
http://HOST/PATH/dlr_script.php?delivery_val=%dact_val=%Amsisdn_val=+955342324564

but wen I receive the DLR I get the msisdn without + like this 955342324564

is the ton /npi  setting important for the DLR matching ?

Any Idea please?

Please find my setting and log below:

group = smsc
smsc = smpp
smsc-id = MT_BILLING
host = XXX.XXX.XXX.XXX
port = X
transceiver-mode = 1
smsc-username = 
smsc-password = xxx
system-type = x
allowed-smsc-id = MT_BILLING
interface-version = 34
reconnect-delay = 30
source-addr-ton = 5
source-addr-npi = 0
dest-addr-ton = 1
dest-addr-npi = 1
bind-addr-ton = 1
bind-addr-npi = 1
wait-ack = 1
wait-ack-expire = 0x02
msg-id-type = 0x00
log-file = /var/log/my.log
log-level = 0


2010-01-23 22:20:43 [31246] [8] DEBUG: SMPP[MT_BILLING]: Sending enquire
link:
2010-01-23 22:20:43 [31246] [8] DEBUG: SMPP PDU 0x7f178c16cbf0 dump:
2010-01-23 22:20:43 [31246] [8] DEBUG:   type_name: enquire_link
2010-01-23 22:20:43 [31246] [8] DEBUG:   command_id: 21 = 0x0015
2010-01-23 22:20:43 [31246] [8] DEBUG:   command_status: 0 = 0x
2010-01-23 22:20:43 [31246] [8] DEBUG:   sequence_number: 13348 = 0x3424
2010-01-23 22:20:43 [31246] [8] DEBUG: SMPP PDU dump ends.
2010-01-23 22:20:55 [31246] [8] WARNING: SMPP: PDU NULL terminated string
(message_id) has no NULL.
2010-01-23 22:20:55 [31246] [8] DEBUG: SMPP[MT_BILLING]: Got PDU:
2010-01-23 22:20:55 [31246] [8] DEBUG: SMPP PDU 0x7f178c16cbf0 dump:
2010-01-23 22:20:55 [31246] [8] DEBUG:   type_name: submit_sm_resp
2010-01-23 22:20:55 [31246] [8] DEBUG:   command_id: 2147483652 = 0x8004
2010-01-23 22:20:55 [31246] [8] DEBUG:   command_status: 69 = 0x0045
2010-01-23 22:20:55 [31246] [8] DEBUG:   sequence_number: 13346 = 0x3422
2010-01-23 22:20:55 [31246] [8] DEBUG:   message_id: NULL
2010-01-23 22:20:55 [31246] [8] DEBUG: SMPP PDU dump ends.
2010-01-23 22:20:55 [31246] [8] ERROR: SMPP[MT_BILLING]: SMSC returned error
code 0x0045 (Submit failed) in response to submit_sm.
2010-01-23 22:20:55 [31246] [8] DEBUG: SMSC[MT_BILLING]: creating DLR
message
2010-01-23 22:20:55 [31246] [8] DEBUG: SMSC[MT_BILLING]: DLR =
http://HOST/PATH/dlr_script.php?delivery_val=%dact_val=%Amsisdn_val=+955342324564
2010-01-23 22:20:55 [31246] [8] DEBUG: SMPP[MT_BILLING]: Got PDU:
2010-01-23 22:20:55 [31246] [8] DEBUG: SMPP PDU 0x7f178c16cbf0 dump:
2010-01-23 22:20:55 [31246] [8] DEBUG:   type_name: enquire_link_resp
2010-01-23 22:20:55 [31246] [8] DEBUG:   command_id: 2147483669 = 0x8015
2010-01-23 22:20:55 [31246] [8] DEBUG:   command_status: 0 = 0x
2010-01-23 22:20:55 [31246] [8] DEBUG:   sequence_number: 13347 = 0x3423
2010-01-23 22:20:55 [31246] [8] DEBUG: SMPP PDU dump ends.
2010-01-23 22:20:55 [31246] [8] DEBUG: SMPP[MT_BILLING]: Got PDU:
2010-01-23 22:20:55 [31246] [8] DEBUG: SMPP PDU 0x7f178c16cbf0 dump:
2010-01-23 22:20:55 [31246] [8] DEBUG:   type_name: enquire_link_resp
2010-01-23 22:20:55 [31246] [8] DEBUG:   command_id: 2147483669 = 0x8015
2010-01-23 22:20:55 [31246] [8] DEBUG:   command_status: 0 = 0x
2010-01-23 22:20:55 [31246] [8] DEBUG:   sequence_number: 13348 = 0x3424
2010-01-23 22:20:55 [31246] [8] DEBUG: SMPP PDU dump ends.
2010-01-23 22:20:55 [31246] [8] DEBUG: Optional parameter tag (0x000e)
2010-01-23 22:20:55 [31246] [8] DEBUG: Optional parameter length read as 1
2010-01-23 22:20:55 [31246] [8] WARNING: SMPP: Unknown TLV(0x000e,0x0001,01)
for PDU type (deliver_sm) received!
2010-01-23 22:20:55 [31246] [8] DEBUG: Optional parameter tag (0x0006)
2010-01-23 22:20:55 [31246] [8] DEBUG: Optional parameter length read as 1
2010-01-23 22:20:55 [31246] [8] WARNING: SMPP: Unknown TLV(0x0006,0x0001,01)
for PDU type (deliver_sm) received!
2010-01-23 22:20:55 [31246] [8] DEBUG: Optional parameter tag (0x001e)
2010-01-23 22:20:55 [31246] [8] DEBUG: Optional parameter length read as 9
2010-01-23 22:20:55 [31246] [8] DEBUG: Optional parameter tag (0x0427)
2010-01-23 22:20:55 [31246] [8] DEBUG: Optional parameter length read as 1
2010-01-23 22:20:55 [31246] [8] DEBUG: SMPP[MT_BILLING]: Got PDU:
2010-01-23 22:20:55 [31246] [8] DEBUG: SMPP PDU 0x7f178c16cbf0 dump:
2010-01-23 22:20:55 [31246] [8] DEBUG:   type_name: deliver_sm
2010-01-23 22:20:55 [31246] [8] DEBUG:   command_id: 5 = 0x0005
2010-01-23 22:20:55 [31246] [8] DEBUG:   command_status: 0 = 0x
2010-01-23 22:20:55 [31246] [8] DEBUG:   sequence_number: 26 = 0x001a
2010-01-23 22:20:55 [31246] [8] DEBUG:   service_type: NULL
2010-01-23 22:20:55 [31246] [8] DEBUG:   source_addr_ton: 1 = 0x0001
2010-01-23 22:20:55 [31246] [8] DEBUG:   source_addr_npi: 1 = 0x0001

Re: Problem launching with /etc/init.d/kannel

2010-01-26 Thread CHRONIS, N.

Hi Niko,

When I try to launch kannel with
user kannel -c /usr/sbin/bearerbox -P -v 4 -d /etc/kannel/kannel.conf

IT DOESN'T WORK
but as 'root' user, it works.

Please notify that kannel user has a /bin/false console login

Any idea?

Best Regards,
Nikos
- Original Message - 
From: Nikos Balkanas nbalka...@gmail.com

To: CHRONIS, N. ni...@chronis.be
Cc: users@kannel.org
Sent: Tuesday, January 26, 2010 8:00 AM
Subject: Re: Problem launching with /etc/init.d/kannel


The scripts are not part of kannel and it is your responsibility from now 
on. Don't occupy the list about them. You have not done the most important 
thing:


Download and compile latest CVS.

BR,
Nikos
- Original Message - 
From: CHRONIS, N. ni...@chronis.be

To: Nikos Balkanas nbalka...@gmail.com
Cc: users@kannel.org
Sent: Tuesday, January 26, 2010 8:43 AM
Subject: Re: Problem launching with /etc/init.d/kannel



Hello Niko,

After trying your script, I have a segmentation fault by launching:

Here is the script:

#!/bin/sh

# Source function library.
if [ -f /etc/init.d/kannel ] ; then
 . /etc/init.d/kannel
elif [ -f /etc/rc.d/init.d/kannel ] ; then
 . /etc/rc.d/init.d/kannel
else
 exit 1
fi
user=kannel

umask 0022

case $1 in
'start')
   echo 'Starting Kannel daemons...'
   su $user -c /usr/sbin/bearerbox -P -v 4 -d 
/etc/kannel/kannel.conf

   sleep 2
   su $user -c /usr/sbin/smsbox -P -v 4 -d /etc/kannel/kannel.conf
   echo /tmp/cores/core.%e  /proc/sys/kernel/core_pattern
   touch /var/lock/subsys/Kannel
   ;;
'stop')
   echo 'Stopping Kannel daemons...'
   killproc bearerbox
   rm -f /var/lock/subsys/Kannel
   ;;
'restart')
   echo 'Restarting Kannel daemons...'
   $0 stop
   $0 start
   ;;
'status')
   pgrep -fl box
   ;;
*)
   echo Usage: $0 { start | stop | restart | status }
   ;;
esac
exit 0

- Original Message - 
From: Nikos Balkanas nbalka...@gmail.com

To: CHRONIS, N. ni...@chronis.be
Cc: users@kannel.org
Sent: Tuesday, January 26, 2010 6:28 AM
Subject: Re: Problem launching with /etc/init.d/kannel



Small correction to script:


'status')
   pgrep -fl kannel | grep local
   ;;


'status')
   pgrep -fl box | grep local
  ;;

Nikos
- Original Message - 
From: Nikos Balkanas nbalka...@gmail.com

To: CHRONIS, N. ni...@chronis.be
Cc: users@kannel.org
Sent: Tuesday, January 26, 2010 6:12 AM
Subject: Re: Problem launching with /etc/init.d/kannel



No. If in doubt check from terminal:

gw/bearerbox -d conffile

You get no output, though.

I can see 2 problems:

1) You are using a very old outdated kannel version. Please upgrade to 
latest CVS.
2) Do NOT use start-stop-daemon. Use an init script. The folowing will 
setup a corefile environment for the Linux kernel. Make sure you create 
a 777 /tmp/cores directory for the cores.


BR,
Nikos

#!/bin/sh

# Source function library.
if [ -f /etc/init.d/functions ] ; then
 . /etc/init.d/functions
elif [ -f /etc/rc.d/init.d/functions ] ; then
 . /etc/rc.d/init.d/functions
else
 exit 1
fi
user=kannel

umask 0022

case $1 in
'start')
   echo 'Starting Kannel daemons...'
   su $user -c /usr/local/sbin/bearerbox -P -v 4 -d /etc/hlr.conf
   sleep 2
   su $user -c /usr/local/sbin/smsbox -P -v 4 -d /etc/hlr.conf
   echo /tmp/cores/core.%e  /proc/sys/kernel/core_pattern
   touch /var/lock/subsys/Kannel
   ;;
'stop')
   echo 'Stopping Kannel daemons...'
   killproc bearerbox
   rm -f /var/lock/subsys/Kannel
   ;;
'restart')
   echo 'Restarting Kannel daemons...'
   $0 stop
   $0 start
   ;;
'status')
   pgrep -fl kannel | grep local
   ;;
*)
   echo Usage: $0 { start | stop | restart | status }
   ;;
esac
exit 0


- Original Message - 
From: CHRONIS, N. ni...@chronis.be

To: Nikos Balkanas nbalka...@gmail.com
Cc: users@kannel.org
Sent: Tuesday, January 26, 2010 4:12 AM
Subject: Re: Problem launching with /etc/init.d/kannel



Hi Niko,

I just achieve a test:
And when i launch the processes from console

root 27442  0.0  0.0 272488  4348 pts/2Sl   03:09   0:00 
/usr/sbin/bearerbox /etc/kannel/kannel.conf
root 27563  0.0  0.0 116340  3596 pts/2Sl   03:09   0:00 
/usr/sbin/smsbox /etc/kannel/kannel.conf


This is working, I can send SMS, and everything is working properly.
I think there is a problem with the launch as daemon ?

Any Idea?
Nikos

- Original Message - 
From: Nikos Balkanas nbalka...@gmail.com
To: CHRONIS, N. ni...@chronis.be; Jovan Kostovski 
chomb...@gmail.com

Cc: users@kannel.org
Sent: Monday, January 25, 2010 11:15 PM
Subject: Re: Problem launching with /etc/init.d/kannel



Hi Niko,

From a console type:

gw/bearerbox conffile

And post output. If not output is created check /var/log/messages for 
any segfaults. If that fails try:


ldd gw/bearerbox

to see if you are linking to a wrong (32bit) library.

BR,
Nikos
- Original Message - 
From: 

Re: sending WAPPush for IMPS client

2010-01-26 Thread Latitude Berlin
Hi Nikos,

Please go through the  following logs:


SMPP log
-
[11723] [7] DEBUG: SMPP[smppacc]: Sending PDU:
[11723] [7] DEBUG: SMPP PDU 814a158 dump:
[11723] [7] DEBUG:   type_name: submit_sm
[11723] [7] DEBUG:   command_id: 4 = 0x0004
[11723] [7] DEBUG:   command_status: 0 = 0x
[11723] [7] DEBUG:   sequence_number: 122797 = 0x0001dfad
[11723] [7] DEBUG:   service_type: NULL
[11723] [7] DEBUG:   source_addr_ton: 5 = 0x0005
[11723] [7] DEBUG:   source_addr_npi: 0 = 0x
[11723] [7] DEBUG:   source_addr: TestServer
[11723] [7] DEBUG:   dest_addr_ton: 1 = 0x0001
[11723] [7] DEBUG:   dest_addr_npi: 1 = 0x0001
[11723] [7] DEBUG:   destination_addr: xxx
[11723] [7] DEBUG:   esm_class: 67 = 0x0043
[11723] [7] DEBUG:   protocol_id: 0 = 0x
[11723] [7] DEBUG:   priority_flag: 0 = 0x
[11723] [7] DEBUG:   schedule_delivery_time: NULL
[11723] [7] DEBUG:   validity_period: NULL
[11723] [7] DEBUG:   registered_delivery: 1 = 0x0001
[11723] [7] DEBUG:   replace_if_present_flag: 0 = 0x
[11723] [7] DEBUG:   data_coding: 4 = 0x0004
[11723] [7] DEBUG:   sm_default_msg_id: 0 = 0x
[11723] [7] DEBUG:   sm_length: 42 = 0x002a
[11723] [7] DEBUG:   short_message:
[11723] [7] DEBUG:Octet string at 8126ad8:
[11723] [7] DEBUG:  len:  42
[11723] [7] DEBUG:  size: 1024
[11723] [7] DEBUG:  immutable: 0
[11723] [7] DEBUG:  data: 06 05 04 0b 84 23 f0 05 06 03 46 af 0a 57 56
43   .#F..WVC
[11723] [7] DEBUG:  data: 49 20 31 2e 31 20 66 61 35 34 36 30 63 34 78
63   I 1.1 fa5460c4xc
[11723] [7] DEBUG:  data: 32 65 39 78 40 67 74 61 6c
6b 2...@gtalk
[11723] [7] DEBUG:Octet string dump ends.
[11723] [7] DEBUG: SMPP PDU dump ends.
[11723] [6] DEBUG: SMPP[smppacc]: Sending enquire link:
[11723] [6] DEBUG: SMPP PDU 814a158 dump:
[11723] [6] DEBUG:   type_name: enquire_link
[11723] [6] DEBUG:   command_id: 21 = 0x0015
[11723] [6] DEBUG:   command_status: 0 = 0x
[11723] [6] DEBUG:   sequence_number: 122788 = 0x0001dfa4
[11723] [6] DEBUG: SMPP PDU dump ends.
[11723] [6] DEBUG: SMPP[smppacc]: Got PDU:
[11723] [6] DEBUG: SMPP PDU 814a158 dump:
[11723] [6] DEBUG:   type_name: enquire_link_resp
[11723] [6] DEBUG:   command_id: 2147483669 = 0x8015
[11723] [6] DEBUG:   command_status: 0 = 0x
[11723] [6] DEBUG:   sequence_number: 122788 = 0x0001dfa4
[11723] [6] DEBUG: SMPP PDU dump ends.
[11723] [7] DEBUG: SMPP[smppacc]: Got PDU:
[11723] [7] DEBUG: SMPP PDU 814a158 dump:
[11723] [7] DEBUG:   type_name: submit_sm_resp
[11723] [7] DEBUG:   command_id: 2147483652 = 0x8004
[11723] [7] DEBUG:   command_status: 0 = 0x
[11723] [7] DEBUG:   sequence_number: 122797 = 0x0001dfad
[11723] [7] DEBUG:   message_id: DDA1F481
[11723] [7] DEBUG: SMPP PDU dump ends.
[11723] [7] DEBUG: DLR[internal]: Adding DLR smsc=smppacc, ts=3718378625,
src=TestServer, dst=xx, mask=7, boxc=dlrbox
[11723] [7] DEBUG: SMPP[smppacc]: Got PDU:
[11723] [7] DEBUG: SMPP PDU 814a158 dump:
[11723] [7] DEBUG:   type_name: deliver_sm
[11723] [7] DEBUG:   command_id: 5 = 0x0005
[11723] [7] DEBUG:   command_status: 0 = 0x
[11723] [7] DEBUG:   sequence_number: 57807 = 0xe1cf
[11723] [7] DEBUG:   service_type: NULL
[11723] [7] DEBUG:   source_addr_ton: 1 = 0x0001
[11723] [7] DEBUG:   source_addr_npi: 1 = 0x0001
[11723] [7] DEBUG:   source_addr: xx
[11723] [7] DEBUG:   dest_addr_ton: 0 = 0x
[11723] [7] DEBUG:   dest_addr_npi: 0 = 0x
[11723] [7] DEBUG:   destination_addr: TestServer
[11723] [7] DEBUG:   esm_class: 4 = 0x0004
[11723] [7] DEBUG:   protocol_id: 0 = 0x
[11723] [7] DEBUG:   priority_flag: 0 = 0x
[11723] [7] DEBUG:   schedule_delivery_time: NULL
[11723] [7] DEBUG:   validity_period: NULL
[11723] [7] DEBUG:   registered_delivery: 0 = 0x
[11723] [7] DEBUG:   replace_if_present_flag: 0 = 0x
[11723] [7] DEBUG:   data_coding: 0 = 0x
[11723] [7] DEBUG:   sm_default_msg_id: 0 = 0x
[11723] [7] DEBUG:   sm_length: 103 = 0x0067
[11723] [7] DEBUG:   short_message:
[11723] [7] DEBUG:Octet string at 814a340:
[11723] [7] DEBUG:  len:  103
[11723] [7] DEBUG:  size: 104
[11723] [7] DEBUG:  immutable: 0
[11723] [7] DEBUG:  data: 69 64 3a 33 37 31 38 33 37 38 36 32 35 20 73
75   id:3718378625 su
[11723] [7] DEBUG:  data: 62 3a 30 30 31 20 64 6c 76 72 64 3a 30 30 31
20   b:001 dlvrd:001
[11723] [7] DEBUG:  data: 73 75 62 6d 69 74 20 64 61 74 65 3a 31 30 30
31   submit date:1001
[11723] [7] DEBUG:  data: 32 36 31 33 31 38 20 64 6f 6e 65 20 64 61 74
65   261318 done date
[11723] [7] DEBUG:  data: 3a 31 30 30 31 32 36 31 33 31 39 20 73 74 61
74   :1001261319 stat
[11723] [7] DEBUG:  data: 3a 44 45 4c 49 56 52 44 20 65 72 72 3a 30 30
30   :DELIVRD err:000
[11723] [7] DEBUG:  data: 20 54 65 78 74 3a
00   Text:.
[11723] [7] DEBUG:Octet string dump ends.
[11723] 

Send but not receive SMS

2010-01-26 Thread carachi83

Hello,
I've this problem: I'm able to send SMSes but I'm not able to receive 
them. Why?

In the log file of the modem and smsbox  I don't see any error!
I've  read the user manual and I've searched on the net, but i didn't 
find anything!

Can you help me?

Below my log and settings file!

Thank you
Bye


---KANNEL.CONF 
--


include = /etc/kannel/modems.conf

group = core
admin-port = 13000
smsbox-port = 13001
admin-password = bar
#status-password = foo
#admin-deny-ip = 
#admin-allow-ip = 
log-file = /etc/kannel/kannel.log
log-level = 1
box-deny-ip = *.*.*.*
box-allow-ip = 127.0.0.1
#unified-prefix = +358,00358,0;+,00
#access-log = /tmp/access.log
#store-file = kannel.store
#ssl-server-cert-file = cert.pem
#ssl-server-key-file = key.pem
#ssl-certkey-file = mycertandprivkeyfile.pem
#dlr-storage = internal

#-
# SMSC CONNECTIONS
#
# SMSC connections are created in bearerbox and they handle SMSC specific
# protocol and message relying. You need these to actually receive and send
# messages to handset, but can use GSM modems as virtual SMSCs


# This is a fake smsc connection, _only_ used to test the system and 
services.

# It really cannot relay messages to actual handsets!

group = smsc
smsc = fake
smsc-id = FAKE
port = 1
connect-allow-ip = 127.0.0.1

#-
# SMSBOX SETUP
#
# Smsbox(es) do higher-level SMS handling after they have been received from
# SMS centers by bearerbox, or before they are given to bearerbox for 
delivery


group = smsbox
bearerbox-host = 127.0.0.1
sendsms-port = 13013
global-sender = 13013
#sendsms-chars = 0123456789 +-
log-file = /etc/kannel/smsbox.log
log-level = 1
#access-log = /tmp/access.log

#-
# SEND-SMS USERS
#
# These users are used when Kannel smsbox sendsms interface is used to
# send PUSH sms messages, i.e. calling URL like
# 
http://kannel.machine:13013/cgi-bin/sendsms?username=testerpassword=foobar...
# 
http://127.0.0.1:13013/cgi-bin/sendsms?username=testerpassword=foobarto=3921776text=ciccio


group = sendsms-user
username = tester
password = foobar
#user-deny-ip = 
#user-allow-ip = 

#-
# SERVICES
#
# These are 'responses' to sms PULL messages, i.e. messages arriving from
# handsets. The response is based on message content. Only one 
sms-service is

# applied, using the first one to match.

group = sms-service
keyword =
#keyword-regex = .*
catch-all = true
#max-messages = 10
get-url = http://localhost/sms?phone=%ptext=%a;




#penna usb
group = smsc
smsc=at
modemtype = auto
#speed = 19200
device=/dev/ttyUSB0
#device=/dev/ttyACM0
my-number=3453361361
log-level=1
log-file = /etc/kannel/modem.log


---MODEM.LOG 
--


2010-01-26 19:11:54 [7919] [7] INFO: AT2[/dev/ttyUSB0]: opening device
2010-01-26 19:11:55 [7919] [7] INFO: AT2[/dev/ttyUSB0]: speed set to 115200
2010-01-26 19:12:09 [7919] [7] INFO: AT2[/dev/ttyUSB0]: Closing device
2010-01-26 19:12:09 [7919] [7] INFO: AT2[/dev/ttyUSB0]: opening device
2010-01-26 19:12:10 [7919] [7] INFO: AT2[/dev/ttyUSB0]: speed set to 57600
2010-01-26 19:12:10 [7919] [7] INFO: AT2[/dev/ttyUSB0]: Closing device
2010-01-26 19:12:10 [7919] [7] INFO: AT2[/dev/ttyUSB0]: detect speed is 
57600

2010-01-26 19:12:10 [7919] [7] INFO: AT2[/dev/ttyUSB0]: opening device
2010-01-26 19:12:11 [7919] [7] INFO: AT2[/dev/ttyUSB0]: speed set to 57600
2010-01-26 19:12:12 [7919] [7] INFO: AT2[/dev/ttyUSB0]: Phase 2+ is 
supported

2010-01-26 19:12:12 [7919] [7] INFO: AT2[/dev/ttyUSB0]: Closing device
2010-01-26 19:12:12 [7919] [7] INFO: AT2[/dev/ttyUSB0]: opening device
2010-01-26 19:12:12 [7919] [7] INFO: AT2[/dev/ttyUSB0]: Logging in
2010-01-26 19:12:12 [7919] [7] INFO: AT2[/dev/ttyUSB0]: init device
2010-01-26 19:12:12 [7919] [7] INFO: AT2[/dev/ttyUSB0]: speed set to 57600
2010-01-26 19:12:13 [7919] [7] INFO: AT2[/dev/ttyUSB0]: Phase 2+ is 
supported
2010-01-26 19:12:13 [7919] [7] INFO: AT2[/dev/ttyUSB0]: AT SMSC 
successfully opened.


---KANNEL.LOG 
--


2010-01-26 19:11:54 [7919] [0] INFO: Added logfile 
`/etc/kannel/kannel.log' with level `1'.

2010-01-26 19:11:54 [7919] [0] INFO: HTTP: Opening server at port 13000.
2010-01-26 19:11:54 [7919] [0] INFO: BOXC: 'smsbox-max-pending' not set, 
using default (100).

2010-01-26 19:11:54 [7919] [0] INFO: Set SMS resend frequency to 60 seconds.
2010-01-26 19:11:54 [7919] [0] INFO: SMS resend retry set to unlimited.
2010-01-26 19:11:54 [7919] [0] INFO: DLR rerouting for smsc id FAKE 
disabled.
2010-01-26 19:11:54 [7919] [0] INFO: DLR rerouting for smsc id (null) 
disabled.
2010-01-26 19:11:54 [7919] [0] INFO: Added logfile 

Re: Send but not receive SMS

2010-01-26 Thread Alvaro Cornejo
You need to either config your modem to send messages to kannel (CNMI
command) or configure kannel to seek for the messages sim-buffering =
true

Read the manual for details

Hope helps

Alvaro
|-|
Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier
celular y Nextel
en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via
SMS y GPRS online
  Visitenos en www.perusms.NET www.smsglobal.com.mx y
www.pravcom.com



On Tue, Jan 26, 2010 at 1:40 PM, carachi83 carach...@gmail.com wrote:
 Hello,
 I've this problem: I'm able to send SMSes but I'm not able to receive them.
 Why?
 In the log file of the modem and smsbox  I don't see any error!
 I've  read the user manual and I've searched on the net, but i didn't find
 anything!
 Can you help me?

 Below my log and settings file!

 Thank you
 Bye


 ---KANNEL.CONF
 --

 include = /etc/kannel/modems.conf

 group = core
 admin-port = 13000
 smsbox-port = 13001
 admin-password = bar
 #status-password = foo
 #admin-deny-ip = 
 #admin-allow-ip = 
 log-file = /etc/kannel/kannel.log
 log-level = 1
 box-deny-ip = *.*.*.*
 box-allow-ip = 127.0.0.1
 #unified-prefix = +358,00358,0;+,00
 #access-log = /tmp/access.log
 #store-file = kannel.store
 #ssl-server-cert-file = cert.pem
 #ssl-server-key-file = key.pem
 #ssl-certkey-file = mycertandprivkeyfile.pem
 #dlr-storage = internal

 #-
 # SMSC CONNECTIONS
 #
 # SMSC connections are created in bearerbox and they handle SMSC specific
 # protocol and message relying. You need these to actually receive and send
 # messages to handset, but can use GSM modems as virtual SMSCs


 # This is a fake smsc connection, _only_ used to test the system and
 services.
 # It really cannot relay messages to actual handsets!

 group = smsc
 smsc = fake
 smsc-id = FAKE
 port = 1
 connect-allow-ip = 127.0.0.1

 #-
 # SMSBOX SETUP
 #
 # Smsbox(es) do higher-level SMS handling after they have been received from
 # SMS centers by bearerbox, or before they are given to bearerbox for
 delivery

 group = smsbox
 bearerbox-host = 127.0.0.1
 sendsms-port = 13013
 global-sender = 13013
 #sendsms-chars = 0123456789 +-
 log-file = /etc/kannel/smsbox.log
 log-level = 1
 #access-log = /tmp/access.log

 #-
 # SEND-SMS USERS
 #
 # These users are used when Kannel smsbox sendsms interface is used to
 # send PUSH sms messages, i.e. calling URL like
 #
 http://kannel.machine:13013/cgi-bin/sendsms?username=testerpassword=foobar...
 #
 http://127.0.0.1:13013/cgi-bin/sendsms?username=testerpassword=foobarto=3921776text=ciccio

 group = sendsms-user
 username = tester
 password = foobar
 #user-deny-ip = 
 #user-allow-ip = 

 #-
 # SERVICES
 #
 # These are 'responses' to sms PULL messages, i.e. messages arriving from
 # handsets. The response is based on message content. Only one sms-service
 is
 # applied, using the first one to match.

 group = sms-service
 keyword =
 #keyword-regex = .*
 catch-all = true
 #max-messages = 10
 get-url = http://localhost/sms?phone=%ptext=%a;




 #penna usb
 group = smsc
 smsc=at
 modemtype = auto
 #speed = 19200
 device=/dev/ttyUSB0
 #device=/dev/ttyACM0
 my-number=3453361361
 log-level=1
 log-file = /etc/kannel/modem.log


 ---MODEM.LOG
 --

 2010-01-26 19:11:54 [7919] [7] INFO: AT2[/dev/ttyUSB0]: opening device
 2010-01-26 19:11:55 [7919] [7] INFO: AT2[/dev/ttyUSB0]: speed set to 115200
 2010-01-26 19:12:09 [7919] [7] INFO: AT2[/dev/ttyUSB0]: Closing device
 2010-01-26 19:12:09 [7919] [7] INFO: AT2[/dev/ttyUSB0]: opening device
 2010-01-26 19:12:10 [7919] [7] INFO: AT2[/dev/ttyUSB0]: speed set to 57600
 2010-01-26 19:12:10 [7919] [7] INFO: AT2[/dev/ttyUSB0]: Closing device
 2010-01-26 19:12:10 [7919] [7] INFO: AT2[/dev/ttyUSB0]: detect speed is
 57600
 2010-01-26 19:12:10 [7919] [7] INFO: AT2[/dev/ttyUSB0]: opening device
 2010-01-26 19:12:11 [7919] [7] INFO: AT2[/dev/ttyUSB0]: speed set to 57600
 2010-01-26 19:12:12 [7919] [7] INFO: AT2[/dev/ttyUSB0]: Phase 2+ is
 supported
 2010-01-26 19:12:12 [7919] [7] INFO: AT2[/dev/ttyUSB0]: Closing device
 2010-01-26 19:12:12 [7919] [7] INFO: AT2[/dev/ttyUSB0]: opening device
 2010-01-26 19:12:12 [7919] [7] INFO: AT2[/dev/ttyUSB0]: Logging in
 2010-01-26 19:12:12 [7919] [7] INFO: AT2[/dev/ttyUSB0]: init device
 2010-01-26 19:12:12 [7919] [7] INFO: AT2[/dev/ttyUSB0]: speed set to 57600
 2010-01-26 19:12:13 [7919] [7] INFO: AT2[/dev/ttyUSB0]: Phase 2+ is
 supported
 2010-01-26 19:12:13 [7919] [7] INFO: AT2[/dev/ttyUSB0]: AT SMSC successfully
 opened.

 

Re: Send but not receive SMS

2010-01-26 Thread Carachi

Hello Alvaro,

Thank you for your advise!
I added sim-buffering in smsc and the init-string and now
I receive the sms in sim memory and  ONLY the first sms, after my modem 
give me this error:


01-26 23:08:45 [10931] [0] INFO: 
2010-01-26 23:08:45 [10931] [0] INFO: Kannel bearerbox II version 1.4.3 
starting

2010-01-26 23:08:45 [10931] [0] INFO: MAIN: Start-up done, entering mainloop
2010-01-26 23:08:46 [10931] [7] INFO: AT2[/dev/ttyUSB0]: speed set to 115200
2010-01-26 23:08:51 [10931] [5] INFO: Client connected from 127.0.0.1
2010-01-26 23:08:52 [10931] [7] INFO: AT2[/dev/ttyUSB0]: Closing device
2010-01-26 23:08:52 [10931] [7] INFO: AT2[/dev/ttyUSB0]: detect speed is 
115200

2010-01-26 23:08:52 [10931] [7] INFO: AT2[/dev/ttyUSB0]: opening device
2010-01-26 23:08:53 [10931] [7] INFO: AT2[/dev/ttyUSB0]: speed set to 115200
2010-01-26 23:08:53 [10931] [7] INFO: AT2[/dev/ttyUSB0]: Phase 2+ is 
supported

2010-01-26 23:08:53 [10931] [7] INFO: AT2[/dev/ttyUSB0]: Closing device
2010-01-26 23:08:53 [10931] [7] INFO: AT2[/dev/ttyUSB0]: opening device
2010-01-26 23:08:53 [10931] [7] INFO: AT2[/dev/ttyUSB0]: Logging in
2010-01-26 23:08:54 [10931] [7] INFO: AT2[/dev/ttyUSB0]: init device
2010-01-26 23:08:54 [10931] [7] INFO: AT2[/dev/ttyUSB0]: speed set to 115200
2010-01-26 23:08:55 [10931] [7] INFO: AT2[/dev/ttyUSB0]: Phase 2+ is 
supported
2010-01-26 23:08:55 [10931] [7] INFO: AT2[/dev/ttyUSB0]: AT SMSC 
successfully opened.*

2010-01-26 23:10:05 [10931] [7] INFO: AT2[/dev/ttyUSB0]: Closing device
2010-01-26 23:10:05 [10931] [7] ERROR: AT2[/dev/ttyUSB0]: Couldn't 
connect (retrying in 10 seconds).

2010-01-26 23:10:15 [10931] [7] INFO: AT2[/dev/ttyUSB0]: opening device
2010-01-26 23:10:15 [10931] [7] INFO: AT2[/dev/ttyUSB0]: Logging in
2010-01-26 23:10:15 [10931] [7] INFO: AT2[/dev/ttyUSB0]: init device
2010-01-26 23:10:15 [10931] [7] INFO: AT2[/dev/ttyUSB0]: speed set to 115200
2010-01-26 23:10:19 [10931] [7] ERROR: AT2[/dev/ttyUSB0]: Wrong or no 
answer to ATZ, ignoring
2010-01-26 23:10:23 [10931] [7] ERROR: AT2[/dev/ttyUSB0]: Wrong or no 
answer to AT. Trying again
2010-01-26 23:10:27 [10931] [7] ERROR: AT2[/dev/ttyUSB0]: Second attempt 
to send AT failed
2010-01-26 23:10:27 [10931] [7] ERROR: AT2[/dev/ttyUSB0]: Initialization 
of device failed.

2010-01-26 23:10:27 [10931] [7] INFO: AT2[/dev/ttyUSB0]: Closing device*
2010-01-26 23:10:27 [10931] [7] ERROR: AT2[/dev/ttyUSB0]: Couldn't 
connect (retrying in 10 seconds).

2010-01-26 23:10:37 [10931] [7] INFO: AT2[/dev/ttyUSB0]: opening device
2010-01-26 23:10:37 [10931] [7] INFO: AT2[/dev/ttyUSB0]: Logging in
2010-01-26 23:10:37 [10931] [7] INFO: AT2[/dev/ttyUSB0]: init device
2010-01-26 23:10:37 [10931] [7] INFO: AT2[/dev/ttyUSB0]: speed set to 115200

Why?
How I can solve it?

Thank you
Bye

My configuration files are:

--modem.conf

group = modems
id = generic
name = Generic Modem
reset-string = AT+CFUN=1
keepalive-cmd = AT
init-string = AT+CNMI=1,2,0,0,0

--kannel.conf

#
# Sample configuration file for Kannel bearerbox on Debian.
# See the documentation for explanations of fields.
#

# HTTP administration is disabled by default. Make sure you set the
# password if you enable it.

# group = core
# admin-port = 13000
# admin-password = bar
# admin-deny-ip = *.*.*.*
# admin-allow-ip = 
# wapbox-port = 13002
# wdp-interface-name = *
# log-file = /var/log/kannel/bearerbox.log
# box-deny-ip = *.*.*.*
# box-allow-ip = 127.0.0.1

# group = wapbox
# bearerbox-host = localhost
# log-file = /var/log/kannel/wapbox.log






include = /etc/kannel/modems.conf

group = core
admin-port = 13000
smsbox-port = 13001
admin-password = bar
#status-password = foo
#admin-deny-ip = *.*.*.*
admin-allow-ip = 
log-file = /etc/kannel/log/kannel.log
log-level = 1
box-deny-ip = *.*.*.*
box-allow-ip = 127.0.0.1
#unified-prefix = +358,00358,0;+,00
#access-log = /tmp/access.log
#store-file = kannel.store
#ssl-server-cert-file = cert.pem
#ssl-server-key-file = key.pem
#ssl-certkey-file = mycertandprivkeyfile.pem
#dlr-storage = internal

#-
# SMSC CONNECTIONS
#
# SMSC connections are created in bearerbox and they handle SMSC specific
# protocol and message relying. You need these to actually receive and send
# messages to handset, but can use GSM modems as virtual SMSCs


# This is a fake smsc connection, _only_ used to test the system and 
services.

# It really cannot relay messages to actual handsets!

group = smsc
smsc = fake
smsc-id = FAKE
port = 1
connect-allow-ip = 127.0.0.1

#-
# SMSBOX SETUP
#
# Smsbox(es) do higher-level SMS handling after they have been received from
# SMS centers by bearerbox, or before they are given to bearerbox for 
delivery


group = smsbox
bearerbox-host = 127.0.0.1
sendsms-port = 13013
global-sender = 13013
#sendsms-chars 

Re: Send but not receive SMS

2010-01-26 Thread Alvaro Cornejo
use log-level=0 for maximum verbose
use cmee=1 or 2 to get maximum verbose from modem

repost logs


|-|
Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier
celular y Nextel
en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via
SMS y GPRS online
  Visitenos en www.perusms.NET www.smsglobal.com.mx y
www.pravcom.com



On Tue, Jan 26, 2010 at 5:24 PM, Carachi carach...@gmail.com wrote:
 Hello Alvaro,

 Thank you for your advise!
 I added sim-buffering in smsc and the init-string and now
 I receive the sms in sim memory and  ONLY the first sms, after my modem give
 me this error:

 01-26 23:08:45 [10931] [0] INFO: 
 2010-01-26 23:08:45 [10931] [0] INFO: Kannel bearerbox II version 1.4.3
 starting
 2010-01-26 23:08:45 [10931] [0] INFO: MAIN: Start-up done, entering mainloop
 2010-01-26 23:08:46 [10931] [7] INFO: AT2[/dev/ttyUSB0]: speed set to 115200
 2010-01-26 23:08:51 [10931] [5] INFO: Client connected from 127.0.0.1
 2010-01-26 23:08:52 [10931] [7] INFO: AT2[/dev/ttyUSB0]: Closing device
 2010-01-26 23:08:52 [10931] [7] INFO: AT2[/dev/ttyUSB0]: detect speed is
 115200
 2010-01-26 23:08:52 [10931] [7] INFO: AT2[/dev/ttyUSB0]: opening device
 2010-01-26 23:08:53 [10931] [7] INFO: AT2[/dev/ttyUSB0]: speed set to 115200
 2010-01-26 23:08:53 [10931] [7] INFO: AT2[/dev/ttyUSB0]: Phase 2+ is
 supported
 2010-01-26 23:08:53 [10931] [7] INFO: AT2[/dev/ttyUSB0]: Closing device
 2010-01-26 23:08:53 [10931] [7] INFO: AT2[/dev/ttyUSB0]: opening device
 2010-01-26 23:08:53 [10931] [7] INFO: AT2[/dev/ttyUSB0]: Logging in
 2010-01-26 23:08:54 [10931] [7] INFO: AT2[/dev/ttyUSB0]: init device
 2010-01-26 23:08:54 [10931] [7] INFO: AT2[/dev/ttyUSB0]: speed set to 115200
 2010-01-26 23:08:55 [10931] [7] INFO: AT2[/dev/ttyUSB0]: Phase 2+ is
 supported
 2010-01-26 23:08:55 [10931] [7] INFO: AT2[/dev/ttyUSB0]: AT SMSC
 successfully opened.*
 2010-01-26 23:10:05 [10931] [7] INFO: AT2[/dev/ttyUSB0]: Closing device
 2010-01-26 23:10:05 [10931] [7] ERROR: AT2[/dev/ttyUSB0]: Couldn't connect
 (retrying in 10 seconds).
 2010-01-26 23:10:15 [10931] [7] INFO: AT2[/dev/ttyUSB0]: opening device
 2010-01-26 23:10:15 [10931] [7] INFO: AT2[/dev/ttyUSB0]: Logging in
 2010-01-26 23:10:15 [10931] [7] INFO: AT2[/dev/ttyUSB0]: init device
 2010-01-26 23:10:15 [10931] [7] INFO: AT2[/dev/ttyUSB0]: speed set to 115200
 2010-01-26 23:10:19 [10931] [7] ERROR: AT2[/dev/ttyUSB0]: Wrong or no answer
 to ATZ, ignoring
 2010-01-26 23:10:23 [10931] [7] ERROR: AT2[/dev/ttyUSB0]: Wrong or no answer
 to AT. Trying again
 2010-01-26 23:10:27 [10931] [7] ERROR: AT2[/dev/ttyUSB0]: Second attempt to
 send AT failed
 2010-01-26 23:10:27 [10931] [7] ERROR: AT2[/dev/ttyUSB0]: Initialization of
 device failed.
 2010-01-26 23:10:27 [10931] [7] INFO: AT2[/dev/ttyUSB0]: Closing device*
 2010-01-26 23:10:27 [10931] [7] ERROR: AT2[/dev/ttyUSB0]: Couldn't connect
 (retrying in 10 seconds).
 2010-01-26 23:10:37 [10931] [7] INFO: AT2[/dev/ttyUSB0]: opening device
 2010-01-26 23:10:37 [10931] [7] INFO: AT2[/dev/ttyUSB0]: Logging in
 2010-01-26 23:10:37 [10931] [7] INFO: AT2[/dev/ttyUSB0]: init device
 2010-01-26 23:10:37 [10931] [7] INFO: AT2[/dev/ttyUSB0]: speed set to 115200

 Why?
 How I can solve it?

 Thank you
 Bye

 My configuration files are:

 --modem.conf

 group = modems
 id = generic
 name = Generic Modem
 reset-string = AT+CFUN=1
 keepalive-cmd = AT
 init-string = AT+CNMI=1,2,0,0,0

 --kannel.conf

 #
 # Sample configuration file for Kannel bearerbox on Debian.
 # See the documentation for explanations of fields.
 #

 # HTTP administration is disabled by default. Make sure you set the
 # password if you enable it.

 # group = core
 # admin-port = 13000
 # admin-password = bar
 # admin-deny-ip = *.*.*.*
 # admin-allow-ip = 
 # wapbox-port = 13002
 # wdp-interface-name = *
 # log-file = /var/log/kannel/bearerbox.log
 # box-deny-ip = *.*.*.*
 # box-allow-ip = 127.0.0.1

 # group = wapbox
 # bearerbox-host = localhost
 # log-file = /var/log/kannel/wapbox.log






 include = /etc/kannel/modems.conf

 group = core
 admin-port = 13000
 smsbox-port = 13001
 admin-password = bar
 #status-password = foo
 #admin-deny-ip = *.*.*.*
 admin-allow-ip = 
 log-file = /etc/kannel/log/kannel.log
 log-level = 1
 box-deny-ip = *.*.*.*
 box-allow-ip = 127.0.0.1
 #unified-prefix = +358,00358,0;+,00
 #access-log = /tmp/access.log
 #store-file = kannel.store
 #ssl-server-cert-file = cert.pem
 #ssl-server-key-file = key.pem
 #ssl-certkey-file = mycertandprivkeyfile.pem
 #dlr-storage = internal

 #-
 # SMSC CONNECTIONS
 #
 # SMSC connections are created in bearerbox and they handle SMSC specific
 # protocol and message relying. You need these to 

pict sms in parts

2010-01-26 Thread Manoj B
Hi,

When I am sending picture sms using kannel its receives in parts (boxes),
AlsoI have tried with and without coding=1, parameter too.

Regards,
Manoj

Kannel logs:
2010-01-27 12:11:00 [21639] [6] DEBUG: SMPP[SMSC-NAME]: Got PDU:
2010-01-27 12:11:00 [21639] [6] DEBUG: SMPP PDU 0xb38006a8 dump:
2010-01-27 12:11:00 [21639] [6] DEBUG:   type_name: enquire_link_resp
2010-01-27 12:11:00 [21639] [6] DEBUG:   command_id: 2147483669 = 0x8015
2010-01-27 12:11:00 [21639] [6] DEBUG:   command_status: 0 = 0x
2010-01-27 12:11:00 [21639] [6] DEBUG:   sequence_number: 22466 = 0x57c2
2010-01-27 12:11:00 [21639] [6] DEBUG: SMPP PDU dump ends.
2010-01-27 12:11:18 [21639] [9] DEBUG: boxc_receiver: sms received
2010-01-27 12:11:18 [21639] [9] DEBUG: new split_parts created 0x90b3170
2010-01-27 12:11:18 [21639] [6] DEBUG: SMPP[SMSC-NAME]: Manually forced
source addr ton = 1, source add npi = 1
2010-01-27 12:11:18 [21639] [6] DEBUG: SMPP[SMSC-NAME]: Manually forced dest
addr ton = 1, dest add npi = 1
2010-01-27 12:11:18 [21639] [6] DEBUG: SMPP[SMSC-NAME]: Sending PDU:
2010-01-27 12:11:18 [21639] [6] DEBUG: SMPP PDU 0xb38006a8 dump:
2010-01-27 12:11:18 [21639] [9] DEBUG: send_msg: sending msg to box:
127.0.0.1
2010-01-27 12:11:18 [21639] [6] DEBUG:   type_name: submit_sm
2010-01-27 12:11:18 [21639] [6] DEBUG:   command_id: 4 = 0x0004
2010-01-27 12:11:18 [21639] [6] DEBUG:   command_status: 0 = 0x
2010-01-27 12:11:18 [21639] [6] DEBUG:   sequence_number: 22467 = 0x57c3
2010-01-27 12:11:18 [21639] [6] DEBUG:   service_type: NULL
2010-01-27 12:11:18 [21639] [6] DEBUG:   source_addr_ton: 5 = 0x0005
2010-01-27 12:11:18 [21639] [6] DEBUG:   source_addr_npi: 0 = 0x
2010-01-27 12:11:18 [21639] [6] DEBUG:   source_addr: 5X
2010-01-27 12:11:18 [21639] [6] DEBUG:   dest_addr_ton: 1 = 0x0001
2010-01-27 12:11:18 [21639] [6] DEBUG:   dest_addr_npi: 1 = 0x0001
2010-01-27 12:11:18 [21639] [6] DEBUG:   destination_addr: 919X
2010-01-27 12:11:18 [21639] [6] DEBUG:   esm_class: 67 = 0x0043
2010-01-27 12:11:18 [21639] [6] DEBUG:   protocol_id: 0 = 0x
2010-01-27 12:11:18 [21639] [6] DEBUG:   priority_flag: 0 = 0x
2010-01-27 12:11:18 [21639] [6] DEBUG:   schedule_delivery_time: NULL
2010-01-27 12:11:18 [21639] [6] DEBUG:   validity_period: NULL
2010-01-27 12:11:18 [21639] [6] DEBUG:   registered_delivery: 0 = 0x
2010-01-27 12:11:18 [21639] [6] DEBUG:   replace_if_present_flag: 0 =
0x
2010-01-27 12:11:18 [21639] [6] DEBUG:   data_coding: 8 = 0x0008
2010-01-27 12:11:18 [21639] [6] DEBUG:   sm_default_msg_id: 0 = 0x
2010-01-27 12:11:18 [21639] [6] DEBUG:   sm_length: 140 = 0x008c
2010-01-27 12:11:18 [21639] [6] DEBUG:   short_message:
2010-01-27 12:11:18 [21639] [6] DEBUG:Octet string at 0xb38018d8:
2010-01-27 12:11:18 [21639] [6] DEBUG:  len:  140
2010-01-27 12:11:18 [21639] [6] DEBUG:  size: 1024
2010-01-27 12:11:18 [21639] [6] DEBUG:  immutable: 0
2010-01-27 12:11:18 [21639] [6] DEBUG:  data: 0b 05 04 15 8a 15 8a 00 03
06 03 01 30 00 00 02   0...
2010-01-27 12:11:18 [21639] [6] DEBUG:  data: 20 20 02 01 00 00 48 1c 01
80 01 7f c0 00 20 01 H... .
2010-01-27 12:11:18 [21639] [6] DEBUG:  data: ff c0 80 02 ff e0 00 38 00
7f e0 80 01 7f e0 00   ...8
2010-01-27 12:11:18 [21639] [6] DEBUG:  data: 60 00 bf e0 ac 0e bf f0 00
70 00 7f f0 82 19 ff   `p..
2010-01-27 12:11:18 [21639] [6] DEBUG:  data: f8 00 70 00 bf f0 b8 21 ff
f8 00 60 00 5f f0 2c   ..p!...`._.,
2010-01-27 12:11:18 [21639] [6] DEBUG:  data: 27 7f fc 00 60 00 bf f8 28
4f ff f8 00 60 00 5f   '...`...(O...`._
2010-01-27 12:11:18 [21639] [6] DEBUG:  data: f8 08 57 ff fc 00 6b 03 af
fc 00 47 ff fe 00 60   ..W...kG...`
2010-01-27 12:11:18 [21639] [6] DEBUG:  data: 86 7f fe 00 22 bf fe 00 ee
08 7f fe 00 41 7f fe   A..
2010-01-27 12:11:18 [21639] [6] DEBUG:  data: 00 4b 09 df ff 00 20 3f ff
00 ca 13   .K ?
2010-01-27 12:11:18 [21639] [6] DEBUG:Octet string dump ends.
2010-01-27 12:11:18 [21639] [6] DEBUG:   more_messages_to_send: 1 =
0x0001
2010-01-27 12:11:18 [21639] [6] DEBUG: SMPP PDU dump ends.
2010-01-27 12:11:18 [21639] [6] DEBUG: SMPP[SMSC-NAME]: Manually forced
source addr ton = 1, source add npi = 1
2010-01-27 12:11:18 [21639] [6] DEBUG: SMPP[SMSC-NAME]: Manually forced dest
addr ton = 1, dest add npi = 1
2010-01-27 12:11:18 [21639] [6] DEBUG: SMPP[SMSC-NAME]: Sending PDU:
2010-01-27 12:11:18 [21639] [6] DEBUG: SMPP PDU 0xb38006a8 dump:
2010-01-27 12:11:18 [21639] [6] DEBUG:   type_name: submit_sm
2010-01-27 12:11:18 [21639] [6] DEBUG:   command_id: 4 = 0x0004
2010-01-27 12:11:18 [21639] [6] DEBUG:   command_status: 0 = 0x
2010-01-27 12:11:18 [21639] [6] DEBUG:   sequence_number: 22468 = 0x57c4
2010-01-27 12:11:18 [21639] [6]