Re: Opensmpp Plus Kannel Debian 11

[info]

Guys apologize for the noise the video helped (but I already figured it 
out after a couple more hours of reading) one of the errors was because 
I needed to compile ./configure source with --with-mysql and second 
issue with opensmpp after reading the --help in ./configure  (in all 
debian install actually) from source or apt install package the source 
for kannel directory is /usr/include/kannel so once I added that option 
to ./configure opensmpp addon compiled normally and could see the 
/usr/local/sbin/opensmppbox. In other words the key for the addons with 
Debian = --with-kannel-dir=/usr/local/include/kannel.


You don't happen to have a video like posted for configuring opensmpp 
addon I am having a difficult time getting the config correct with this 
kannel addon.


Thank to all those that responded appreciate the effort.

-

J

On 2023-10-16 11:31, i...@mail.jeaholding.com wrote:

Hello to all:

Debian Bulleye 11 (NO GUI bare-bones).
Kannel bearerbox version `1.4.5'. Compiler `10.1.0'. System Linux,
release 5.10.0-26-amd64,

I was successful in installing Kannel via the apt packages with no
problem, I was able to setup a fake SMSC to test and I saw the admin
panel showcase sent sms from the fake smsc I setup.

I continued reading and wanted to install opensmpp  and here is where
the problem occurs. It seems I am not able to setup opensmpp without
having the source kannel compile meaning (apt package might not be
good option).

I checkout svn both the gateway/trunk and opensmpp/trunk and I am not
able to compile either of them on the debian box.

gateway when ./configure complaints that:
===
sed: can't read ./ltmain.sh: No such file or directory
mv: cannot stat 'libtoolT': No such file or directory
cp: cannot stat 'libtoolT': No such file or directory
chmod: cannot access 'libtool': No such file or directory
(After it completes)
License information 

Thank you for using Kannel.


opensmpp when ./configure complaints:
=
gwlib is not installed (this is with apt install kannel kannel-extra).


Also, I looked at the config.log of both and it doesn't seem like
anything major showing I had an issue with some missing library which
I solved by installing libxml++2.6-dev and libtool libtool-bin (I
installed thinking something was missing).

I saw this in the config.log (nothing stands out) and glance the
libtool bash script with 7000+ lines of code.

Am I missing something here? Can anyone point me to documentation,
blog, and/or write their experience installing opensmpp addon with the
Debian package kannel kannel-extra?

-

Thank you in advance.

Re: Opensmpp Plus Kannel Debian 11

[Mesbahuddin Malik]

Check your gcc version may be it is not matching with kannel.

Regards
Mesbah

On Mon, Oct 16, 2023 at 10:32 PM  wrote:

> Hello to all:
>
> Debian Bulleye 11 (NO GUI bare-bones).
> Kannel bearerbox version `1.4.5'. Compiler `10.1.0'. System Linux,
> release 5.10.0-26-amd64,
>
> I was successful in installing Kannel via the apt packages with no
> problem, I was able to setup a fake SMSC to test and I saw the admin
> panel showcase sent sms from the fake smsc I setup.
>
> I continued reading and wanted to install opensmpp  and here is where
> the problem occurs. It seems I am not able to setup opensmpp without
> having the source kannel compile meaning (apt package might not be good
> option).
>
> I checkout svn both the gateway/trunk and opensmpp/trunk and I am not
> able to compile either of them on the debian box.
>
> gateway when ./configure complaints that:
> ===
> sed: can't read ./ltmain.sh: No such file or directory
> mv: cannot stat 'libtoolT': No such file or directory
> cp: cannot stat 'libtoolT': No such file or directory
> chmod: cannot access 'libtool': No such file or directory
> (After it completes)
> License information 
>
> Thank you for using Kannel.
>
>
> opensmpp when ./configure complaints:
> =
> gwlib is not installed (this is with apt install kannel kannel-extra).
>
>
> Also, I looked at the config.log of both and it doesn't seem like
> anything major showing I had an issue with some missing library which I
> solved by installing libxml++2.6-dev and libtool libtool-bin (I
> installed thinking something was missing).
>
> I saw this in the config.log (nothing stands out) and glance the libtool
> bash script with 7000+ lines of code.
>
> Am I missing something here? Can anyone point me to documentation, blog,
> and/or write their experience installing opensmpp addon with the Debian
> package kannel kannel-extra?
>
> -
>
> Thank you in advance.
>
>

RE: OpenSMPP+Kannel: DLR: (dst & src) are expected INVETED in the deliver_sm (but remains as in submit_sm)

[Mario Noboa]

Hi list,

I'm a newbie with opensmpp, i found this thread, I think I have the same
problem.

I'm woking with http-based smsc  and opensmpp, and when i send a dlr, dst
and src doesn't INVETED.

I send the opensmppbox logs in the attachment

Do you have any ideas?

Thanks a lot!


- Original Message -

From: Rene Kluwen
To: 'Didac Royo'
Cc: users at kannel.org <http://www.kannel.org/mailman/listinfo/users>
Sent: Wednesday, March 02, 2011 4:56 PM
Subject: RE: OpenSMPP+Kannel: DLR: (dst & src) are expected INVETED in the
deliver_sm (but remains as in submit_sm)


Viewing this log, it seems that your sms gateway is doing things right.
Somewhere along the line, bearerbox OR opensmppbox reverses the addresses.
Looking at the code, I cannot see which one is doing things wrong. Both seem
to be doing things allrighty…

Judging from your bearerbox log:

Ψ  2011-03-01 16:50:04 Receive DLR [SMSC:GMS] [SVC:ismsad] [ACT:sit2]
[BINF:] [FID:110301S00d1a44c] [META:?smpp?dlr_err=000&] [from:Info]
[to:+34695839615] [flags:-1:-1:-1:-1:1] [msg:111:id:110301S00d1a44c sub:000
dlvrd:000 submit date:1103011650 done date:1103011650 stat:DELIVRD err:000
text:] [udh:0:]

It seems that smsc smpp is doing things wrong. On line 1487 and line 1545 of
smsc_smpp.c, where the function handle_dlr() is called, this function
replaces source_addr with destination_address.
Or maybe otherwise: dlr_find is called and returns the msg structure with
the original source_addr and dest_addr still in place.
Maybe somebody with some more knowledge of the smpp driver can shed a light
on this?

== Rene








*Mario Noboa C.*  | IT Development Specialist
Teamsourcing
www.teamsourcing.com.ec | mno...@teamsourcing.com.ec


opensmpp.log
Description: Binary data

Re: opensmpp failing to install

[christopher kamutumwa]

Hello
I am getting below error\\root@ubuntu:/etc/kannel/trunk# ./bootstrap.sh
-bash: ./bootstrap.sh: No such file or directory
root@ubuntu:/etc/kannel/trunk# ls
acinclude.m4  bootstrap COPYING  INSTALL  README  VERSION
aclocal.m4ChangeLog doc  Makefile.am  rpm
AUTHORS   configure example  Makefile.in  sb-config.h.in
autotools configure.in  gw   NEWS UPGRADE

On Tue, Apr 12, 2022 at 8:18 PM Loyc Cossou  wrote:

> Hi,
>
> Have you done * ./bootstrap.sh* before ./configure?
>
> --
> loyc Cossou
>
> [image: Mailtrack]
> 
>  Sender
> notified by
> Mailtrack
> 
>  12/04/22,
> 19:17:25
>
> Le mar. 12 avr. 2022 à 15:56, christopher kamutumwa <
> chriskamutu...@gmail.com> a écrit :
>
>>
>>
>> -- Forwarded message -
>> From: christopher kamutumwa 
>> Date: Sun, Apr 10, 2022 at 4:18 AM
>> Subject: opensmpp failing to install
>> To: users 
>>
>>
>> Hello Support,
>> Need help with installing opensmpp on ubuntu server below is error i
>> receive when installing
>>
>> root@ubuntu:~/trunk# make
>> make  all-recursive
>> make[1]: Entering directory `/root/trunk'
>> Making all in gw
>> make[2]: Entering directory `/root/trunk/gw'
>> if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../gw -I../gw-g -O2
>> -D_XOPEN_SOURCE=600 -D_BSD_SOURCE -I/usr/include/kannel -Wall -g -O2
>> -D_XOPEN_SOURCE=600 -D_BSD_SOURCE -D_LARGE_FILES= -I/usr/include/libxml2
>>  -Wall -Wmissing-prototypes -Wmissing-declarations -Wnested-externs
>> -Winline -Wformat -Wformat-security -Wmissing-format-attribute
>> -I/usr/include -I/usr/include/mysql -I/usr/include/postgresql -MT
>> opensmppbox.o -MD -MP -MF ".deps/opensmppbox.Tpo" -c -o opensmppbox.o
>> opensmppbox.c; \
>> then mv -f ".deps/opensmppbox.Tpo" ".deps/opensmppbox.Po"; else
>> rm -f ".deps/opensmppbox.Tpo"; exit 1; fi
>> opensmppbox.c:81:26: fatal error: gw/meta_data.h: No such file or
>> directory
>>  #include "gw/meta_data.h"
>>   ^
>> compilation terminated.
>> make[2]: *** [opensmppbox.o] Error 1
>> make[2]: Leaving directory `/root/trunk/gw'
>> make[1]: *** [all-recursive] Error 1
>> make[1]: Leaving directory `/root/trunk'
>> make: *** [all] Error 2
>>
>> thanks in advance
>>
>> chris
>>
>

Re: opensmpp failing to install

[Loyc Cossou]

Hi,

Have you done * ./bootstrap.sh* before ./configure?

--
loyc Cossou

[image: Mailtrack]

Sender
notified by
Mailtrack

12/04/22,
19:17:25

Le mar. 12 avr. 2022 à 15:56, christopher kamutumwa <
chriskamutu...@gmail.com> a écrit :

>
>
> -- Forwarded message -
> From: christopher kamutumwa 
> Date: Sun, Apr 10, 2022 at 4:18 AM
> Subject: opensmpp failing to install
> To: users 
>
>
> Hello Support,
> Need help with installing opensmpp on ubuntu server below is error i
> receive when installing
>
> root@ubuntu:~/trunk# make
> make  all-recursive
> make[1]: Entering directory `/root/trunk'
> Making all in gw
> make[2]: Entering directory `/root/trunk/gw'
> if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../gw -I../gw-g -O2
> -D_XOPEN_SOURCE=600 -D_BSD_SOURCE -I/usr/include/kannel -Wall -g -O2
> -D_XOPEN_SOURCE=600 -D_BSD_SOURCE -D_LARGE_FILES= -I/usr/include/libxml2
>  -Wall -Wmissing-prototypes -Wmissing-declarations -Wnested-externs
> -Winline -Wformat -Wformat-security -Wmissing-format-attribute
> -I/usr/include -I/usr/include/mysql -I/usr/include/postgresql -MT
> opensmppbox.o -MD -MP -MF ".deps/opensmppbox.Tpo" -c -o opensmppbox.o
> opensmppbox.c; \
> then mv -f ".deps/opensmppbox.Tpo" ".deps/opensmppbox.Po"; else rm
> -f ".deps/opensmppbox.Tpo"; exit 1; fi
> opensmppbox.c:81:26: fatal error: gw/meta_data.h: No such file or directory
>  #include "gw/meta_data.h"
>   ^
> compilation terminated.
> make[2]: *** [opensmppbox.o] Error 1
> make[2]: Leaving directory `/root/trunk/gw'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/root/trunk'
> make: *** [all] Error 2
>
> thanks in advance
>
> chris
>

Re: opensmpp configure issue

[Web Min]

Hi,

I'm still surprised how kannel didn't take care of the installation
problems.

Try to google on your problem, you will found that there are many and many
issues with kannel installation from source especially when installing
SQL-Box.

My experience with SQL-Box and kannel was too bad, I changed my core to use
the kannel with HTTP submission because I encountered problems in certain
steps.

I've collected the below commands, and still, the SQL-Box is not a success
for me

cd /usr/src/kannel-source && svn co https://svn.kannel.org/gateway/trunk

# check the automake version to match it with sqlbox/bootstrap

automake --version | sed -e '1s/[^0-9]*//' -e q

cd trunk

mv configure.in configure.ac

cat /usr/share/aclocal/libtool.m4 /usr/share/aclocal/ltoptions.m4
/usr/share/aclocal/ltsugar.m4 /usr/share/aclocal/ltversion.m4
/usr/share/aclocal/lt~obsolete.m4 >> aclocal.m4

echo  'AC_CONFIG_MACRO_DIRS([m4])' > configure.in

./bootstrap.sh

./configure --disable-docs --enable-start-stop-daemon --with-mysql
--with-mysql-dir=/var/lib/mysql

make

make bindir=/usr/local/kannel install

cd addons/sqlbox

mv configure.in configure.ac

cat /usr/share/aclocal/libtool.m4 /usr/share/aclocal/ltoptions.m4
/usr/share/aclocal/ltsugar.m4 /usr/share/aclocal/ltversion.m4
/usr/share/aclocal/lt~obsolete.m4 >> aclocal.m4

echo  'AC_CONFIG_MACRO_DIRS([m4])' > configure.in

./bootstrap

./configure --disable-docs --with-mysql --prefix=/usr/local/kannel
--with-kannel-dir=/usr/local/kannel

make

make install

/sbin/ldconfig -v


Finally, there are no straight-forward to setup the SQL-Box with kannel yet!

Best Regards

On Sun, Apr 21, 2019 at 8:14 PM Rene Kluwen  wrote:

> Did you make sure the path is where kannel is _*installed*_?
>
> Not the path where the folders are checked out.
>
>
>
> == Rene
>
>
>
> *Van:* users  *Namens *Rahul Mittal
> *Verzonden:* vrijdag 19 april 2019 19:39
> *Aan:* users@kannel.org
> *Onderwerp:* opensmpp configure issue
>
>
>
> Hi,
>
>
>
> I am trying to reconfigure opensmppbox but getting this error message:
>
> checking for "/usr/local/include/kannel/gw-config.h"... no
>
> configure: error: Unable to find gw-config.h, please provide a
> --with-kannel-dir=
>  location
>
>
>
> So, I added the  --with-kannel-dir= PATH  but still same error. Looks like
> its not picking up new path. Please suggest.
>
>
>
> Thanks,
>
> Rahul Mittal
>

RE: opensmpp configure issue

[Rene Kluwen]

Did you make sure the path is where kannel is _installed_?

Not the path where the folders are checked out.

 

== Rene

 

Van: users  Namens Rahul Mittal
Verzonden: vrijdag 19 april 2019 19:39
Aan: users@kannel.org
Onderwerp: opensmpp configure issue

 

Hi,

 

I am trying to reconfigure opensmppbox but getting this error message:

checking for "/usr/local/include/kannel/gw-config.h"... no

configure: error: Unable to find gw-config.h, please provide a 
--with-kannel-dir=
 location 

 

So, I added the  --with-kannel-dir= PATH  but still same error. Looks like its 
not picking up new path. Please suggest.

 

Thanks,

Rahul Mittal

Re: Opensmpp shuts down after panic twice a day

[Rene Kluwen]

Could you pass us the output, on your machine from:

addr2line -e /usr/local/kannel/sbin/opensmppbox 0x40ed03 0x413f3e 
0x44e7d9


== Rene

-- Origineel bericht --
Van: "Gorki Alfaro" 
Aan: users@kannel.org; chriskamutu...@gmail.com
Verzonden: 3-2-2017 21:56:38
Onderwerp: Opensmpp shuts down after panic twice a day


Hello my friends/Chris

Does anyone solve this situation? I am running `svn-r5141' and the same 
happens, crash after sending long messages.


Thanks in advance
Gorki

-


hello all , i have a problem with opensmpp it randomly shuts down after 
panic below is error from logs please advise whats causing this and 
solution
[root@smpp01 sbin]# 2016-11-09 09:44:12 [21810] [13] PANIC: 
/usr/local/kannel/sbin/opensmppbox() [0x46493c] 2016-11-09 09:44:12 
[21810] [13] PANIC: /lib64/libpthread.so.0(+0xf7e0) [0x7f04bbc667e0] 
2016-11-09 09:44:12 [21810] [13] PANIC: 
/usr/local/kannel/sbin/opensmppbox() [0x458deb] 2016-11-09 09:44:12 
[21810] [13] PANIC: 
/usr/local/kannel/sbin/opensmppbox(octstr_destroy+0x1d) [0x45b17d] 
2016-11-09 09:44:12 [21810] [13] PANIC: 
/usr/local/kannel/sbin/opensmppbox() [0x40ed03] 2016-11-09 09:44:12 
[21810] [13] PANIC: /usr/local/kannel/sbin/opensmppbox() [0x413f3e] 
2016-11-09 09:44:12 [21810] [13] PANIC: 
/usr/local/kannel/sbin/opensmppbox() [0x44e7d9] 2016-11-09 09:44:12 
[21810] [13] PANIC: /lib64/libpthread.so.0(+0x7aa1) [0x7f04bbc5eaa1] 
2016-11-09 09:44:12 [21810] [13] PANIC: /lib64/libc.so.6(clone+0x6d) 
[0x7f04baab5aad] regards chris

Re: Opensmpp shuts down after panic twice a day

[Stipe Tolj]

Am 14.11.2016 14:43, schrieb Rene Kluwen:

What's the output of:

addr2line -e /path/to/opensmppbox 0x40ed03 0x413f3e 0x44e7d9


since I need to mange a lot of these addr2line calls manually from time 
to time, SHOULD we add a facility in the backtrace calling of Kannel 
itself to check if addr2line is in $PATH, and if yes, simply use it to 
get the line information of the addresses?


Stipe

--
Best Regards,
Stipe Tolj

---
Düsseldorf, NRW, Germany

Kannel Foundation tolj.org system architecture
http://www.kannel.org/http://www.tolj.org/

stolj at kannel.org   st at tolj.org
---

Re: Opensmpp shuts down after panic twice a day

[Rene Kluwen]

What's the output of:

addr2line -e /path/to/opensmppbox 0x40ed03 0x413f3e 0x44e7d9

== Rene

-- Origineel bericht --
Van: "christopher kamutumwa" 
Aan: "users" 
Verzonden: 11-11-2016 7:36:48
Onderwerp: Opensmpp shuts down after panic twice a day


hello all ,

i have a problem with opensmpp it randomly shuts down after panic below 
is error from logs please advise whats causing this and solution


[root@smpp01 sbin]# 2016-11-09 09:44:12 [21810] [13] PANIC: 
/usr/local/kannel/sbin/opensmppbox() [0x46493c]
2016-11-09 09:44:12 [21810] [13] PANIC: /lib64/libpthread.so.0(+0xf7e0) 
[0x7f04bbc667e0]
2016-11-09 09:44:12 [21810] [13] PANIC: 
/usr/local/kannel/sbin/opensmppbox() [0x458deb]
2016-11-09 09:44:12 [21810] [13] PANIC: 
/usr/local/kannel/sbin/opensmppbox(octstr_destroy+0x1d) [0x45b17d]
2016-11-09 09:44:12 [21810] [13] PANIC: 
/usr/local/kannel/sbin/opensmppbox() [0x40ed03]
2016-11-09 09:44:12 [21810] [13] PANIC: 
/usr/local/kannel/sbin/opensmppbox() [0x413f3e]
2016-11-09 09:44:12 [21810] [13] PANIC: 
/usr/local/kannel/sbin/opensmppbox() [0x44e7d9]
2016-11-09 09:44:12 [21810] [13] PANIC: /lib64/libpthread.so.0(+0x7aa1) 
[0x7f04bbc5eaa1]
2016-11-09 09:44:12 [21810] [13] PANIC: /lib64/libc.so.6(clone+0x6d) 
[0x7f04baab5aad]



regards chris

RE: OpenSMPP Crashing after client's disconnect

[Rene Kluwen]

I remember it used to be an issue in an old version.

Are you using latest svn?

 

From: users [mailto:users-boun...@kannel.org] On Behalf Of igna...@gmail.com
Sent: vrijdag 22 november 2013 21:18
To: users@kannel.org
Subject: OpenSMPP Crashing after client's disconnect

 

Hello List,

 

I’m having an issue with OpenSMPPBOX. Basically the application crashes after 
the SMPP client disconnects.

 

I can send messages, and everything works fine, but at the moment the client 
disconnects, the app crashes.

 

If anybody could give me a hand on this, it would be very helpful.

 

Thank you very much in advance!

 

Here’s my log and config files:

 

2013-11-22 15:01:12 [27544] [0] INFO: Debug_lvl = -1, log_file = none, 
log_lvl = 0
2013-11-22 15:01:12 [27544] [0] DEBUG: Kannel opensmppbox version svn-r gwlib 
version `1.5.0'.
Build `Nov 21 2013 14:33:54', compiler `4.6.3'.
System Linux, release 3.8.0-29-generic, version #42~precise1-Ubuntu SMP Wed Aug 
14 15:31:16 UTC 2013, machine i686.
Hostname sm, IP 127.0.1.1.
Libxml version 2.7.8.
Compiled with MySQL 5.5.34, using MySQL 5.5.34.
Using native malloc.

 

2013-11-22 15:01:12 [27544] [0] INFO: Starting to log to file 
/var/log/kannel/smppbox.log level 0
2013-11-22 15:01:12 [27544] [0] INFO: Added logfile 
`/var/log/kannel/smppbox.log' with level `0'.
2013-11-22 15:01:12 [27544] [0] INFO: DLR using storage type: internal
2013-11-22 15:01:12 [27544] [0] WARNING: opensmmpbox: DLR: using default 
'internal' for storage type.
2013-11-22 15:01:12 [27544] [0] INFO: opensmppbox DLR storage using type: 
internal
2013-11-22 15:01:12 [27544] [0] INFO: Waiting for SMPP connections on port 2775.
2013-11-22 15:01:22 [27544] [0] DEBUG: Started thread 1 (opensmppbox.c:function)
2013-11-22 15:01:22 [27544] [1] DEBUG: Thread 1 (opensmppbox.c:function) maps 
to pid 27544.
2013-11-22 15:01:22 [27544] [1] INFO: Client connected from 181.31.246.81
2013-11-22 15:01:22 [27544] [1] DEBUG: Connecting to 127.0.0.1
2013-11-22 15:01:22 [27544] [1] INFO: Connected to bearerbox at 127.0.0.1 port 
13001.
2013-11-22 15:01:22 [27544] [1] DEBUG: Started thread 2 
(opensmppbox.c:smpp_to_bearerbox)
2013-11-22 15:01:22 [27544] [1] ERROR: opensmppbox: bearerbox_to_smpp: thread 
starts
2013-11-22 15:01:22 [27544] [2] DEBUG: Thread 2 
(opensmppbox.c:smpp_to_bearerbox) maps to pid 27544.
2013-11-22 15:01:22 [27544] [2] ERROR: opensmppbox: smpp_to_bearerbox: thread 
starts
2013-11-22 15:01:23 [27544] [2] DEBUG: SMPP[(null)]: Got PDU:
2013-11-22 15:01:23 [27544] [2] DEBUG: SMPP PDU 0xb5e008b8 dump:
2013-11-22 15:01:23 [27544] [2] DEBUG:   type_name: bind_transceiver
2013-11-22 15:01:23 [27544] [2] DEBUG:   command_id: 9 = 0x0009
2013-11-22 15:01:23 [27544] [2] DEBUG:   command_status: 0 = 0x
2013-11-22 15:01:23 [27544] [2] DEBUG:   sequence_number: 1 = 0x0001
2013-11-22 15:01:23 [27544] [2] DEBUG:   system_id: test
2013-11-22 15:01:23 [27544] [2] DEBUG:   password: test
2013-11-22 15:01:23 [27544] [2] DEBUG:   system_type: NULL
2013-11-22 15:01:23 [27544] [2] DEBUG:   interface_version: 52 = 0x0034
2013-11-22 15:01:23 [27544] [2] DEBUG:   addr_ton: 0 = 0x
2013-11-22 15:01:23 [27544] [2] DEBUG:   addr_npi: 0 = 0x
2013-11-22 15:01:23 [27544] [2] DEBUG:   address_range: NULL
2013-11-22 15:01:23 [27544] [2] DEBUG: SMPP PDU dump ends.
2013-11-22 15:01:23 [27544] [2] DEBUG: Client connected with id test
2013-11-22 15:01:23 [27544] [2] DEBUG: SMPP[test]: Sending PDU:
2013-11-22 15:01:23 [27544] [2] DEBUG: SMPP PDU 0xb5e00c78 dump:
2013-11-22 15:01:23 [27544] [2] DEBUG:   type_name: bind_transceiver_resp
2013-11-22 15:01:23 [27544] [2] DEBUG:   command_id: 2147483657 = 0x8009
2013-11-22 15:01:23 [27544] [2] DEBUG:   command_status: 0 = 0x
2013-11-22 15:01:23 [27544] [2] DEBUG:   sequence_number: 1 = 0x0001
2013-11-22 15:01:23 [27544] [2] DEBUG:   system_id: NetTalkSMPP
2013-11-22 15:01:23 [27544] [2] DEBUG: SMPP PDU dump ends.
2013-11-22 15:01:24 [27544] [2] DEBUG: SMPP[test]: Got PDU:
2013-11-22 15:01:24 [27544] [2] DEBUG: SMPP PDU 0xb5e009c8 dump:
2013-11-22 15:01:24 [27544] [2] DEBUG:   type_name: unbind
2013-11-22 15:01:24 [27544] [2] DEBUG:   command_id: 6 = 0x0006
2013-11-22 15:01:24 [27544] [2] DEBUG:   command_status: 0 = 0x
2013-11-22 15:01:24 [27544] [2] DEBUG:   sequence_number: 2 = 0x0002
2013-11-22 15:01:24 [27544] [2] DEBUG: SMPP PDU dump ends.
2013-11-22 15:01:24 [27544] [2] DEBUG: SMPP[test]: Sending PDU:
2013-11-22 15:01:24 [27544] [2] DEBUG: SMPP PDU 0xb5e00888 dump:
2013-11-22 15:01:24 [27544] [2] DEBUG:   type_name: unbind_resp
2013-11-22 15:01:24 [27544] [2] DEBUG:   command_id: 2147483654 = 0x8006
2013-11-22 15:01:24 [27544] [2] DEBUG:   command_status: 0 = 0x
2013-11-22 15:01:24 [27544] [2] DEBUG:   sequence_number: 2 = 0x0002
2013-11-22 15:01:24 [27544] [2] DEBUG: SMPP PDU dump ends.
2013-11-22 15:01:24 [27544] [2] ERROR: opensmppbox: smpp_to_bearerbox: thread 
terminates
2013-11-22 15:01:24 

Re: OpenSMPP Crashing after client's disconnect

[ignamun]

Thank you Rene!


I was following an old guide to install, with a wrong path.


It’s working fine, thank you!







From: Rene Kluwen
Sent: ‎Friday‎, ‎November‎ ‎22‎, ‎2013 ‎9‎:‎36‎ ‎PM
To: igna...@gmail.com, users@kannel.org






I remember it used to be an issue in an old version.

Are you using latest svn?

 



From: users [mailto:users-boun...@kannel.org] On Behalf Of igna...@gmail.com
Sent: vrijdag 22 november 2013 21:18
To: users@kannel.org
Subject: OpenSMPP Crashing after client's disconnect

 



Hello List,


 


I’m having an issue with OpenSMPPBOX. Basically the application crashes after 
the SMPP client disconnects.


 


I can send messages, and everything works fine, but at the moment the client 
disconnects, the app crashes.


 


If anybody could give me a hand on this, it would be very helpful.


 


Thank you very much in advance!


 


Here’s my log and config files:


 


2013-11-22 15:01:12 [27544] [0] INFO: Debug_lvl = -1, log_file = none, 
log_lvl = 0
2013-11-22 15:01:12 [27544] [0] DEBUG: Kannel opensmppbox version svn-r gwlib 
version `1.5.0'.
Build `Nov 21 2013 14:33:54', compiler `4.6.3'.
System Linux, release 3.8.0-29-generic, version #42~precise1-Ubuntu SMP Wed Aug 
14 15:31:16 UTC 2013, machine i686.
Hostname sm, IP 127.0.1.1.
Libxml version 2.7.8.
Compiled with MySQL 5.5.34, using MySQL 5.5.34.
Using native malloc.


 


2013-11-22 15:01:12 [27544] [0] INFO: Starting to log to file 
/var/log/kannel/smppbox.log level 0
2013-11-22 15:01:12 [27544] [0] INFO: Added logfile 
`/var/log/kannel/smppbox.log' with level `0'.
2013-11-22 15:01:12 [27544] [0] INFO: DLR using storage type: internal
2013-11-22 15:01:12 [27544] [0] WARNING: opensmmpbox: DLR: using default 
'internal' for storage type.
2013-11-22 15:01:12 [27544] [0] INFO: opensmppbox DLR storage using type: 
internal
2013-11-22 15:01:12 [27544] [0] INFO: Waiting for SMPP connections on port 2775.
2013-11-22 15:01:22 [27544] [0] DEBUG: Started thread 1 (opensmppbox.c:function)
2013-11-22 15:01:22 [27544] [1] DEBUG: Thread 1 (opensmppbox.c:function) maps 
to pid 27544.
2013-11-22 15:01:22 [27544] [1] INFO: Client connected from 181.31.246.81
2013-11-22 15:01:22 [27544] [1] DEBUG: Connecting to 127.0.0.1
2013-11-22 15:01:22 [27544] [1] INFO: Connected to bearerbox at 127.0.0.1 port 
13001.
2013-11-22 15:01:22 [27544] [1] DEBUG: Started thread 2 
(opensmppbox.c:smpp_to_bearerbox)
2013-11-22 15:01:22 [27544] [1] ERROR: opensmppbox: bearerbox_to_smpp: thread 
starts
2013-11-22 15:01:22 [27544] [2] DEBUG: Thread 2 
(opensmppbox.c:smpp_to_bearerbox) maps to pid 27544.
2013-11-22 15:01:22 [27544] [2] ERROR: opensmppbox: smpp_to_bearerbox: thread 
starts
2013-11-22 15:01:23 [27544] [2] DEBUG: SMPP[(null)]: Got PDU:
2013-11-22 15:01:23 [27544] [2] DEBUG: SMPP PDU 0xb5e008b8 dump:
2013-11-22 15:01:23 [27544] [2] DEBUG:   type_name: bind_transceiver
2013-11-22 15:01:23 [27544] [2] DEBUG:   command_id: 9 = 0x0009
2013-11-22 15:01:23 [27544] [2] DEBUG:   command_status: 0 = 0x
2013-11-22 15:01:23 [27544] [2] DEBUG:   sequence_number: 1 = 0x0001
2013-11-22 15:01:23 [27544] [2] DEBUG:   system_id: test
2013-11-22 15:01:23 [27544] [2] DEBUG:   password: test
2013-11-22 15:01:23 [27544] [2] DEBUG:   system_type: NULL
2013-11-22 15:01:23 [27544] [2] DEBUG:   interface_version: 52 = 0x0034
2013-11-22 15:01:23 [27544] [2] DEBUG:   addr_ton: 0 = 0x
2013-11-22 15:01:23 [27544] [2] DEBUG:   addr_npi: 0 = 0x
2013-11-22 15:01:23 [27544] [2] DEBUG:   address_range: NULL
2013-11-22 15:01:23 [27544] [2] DEBUG: SMPP PDU dump ends.
2013-11-22 15:01:23 [27544] [2] DEBUG: Client connected with id test
2013-11-22 15:01:23 [27544] [2] DEBUG: SMPP[test]: Sending PDU:
2013-11-22 15:01:23 [27544] [2] DEBUG: SMPP PDU 0xb5e00c78 dump:
2013-11-22 15:01:23 [27544] [2] DEBUG:   type_name: bind_transceiver_resp
2013-11-22 15:01:23 [27544] [2] DEBUG:   command_id: 2147483657 = 0x8009
2013-11-22 15:01:23 [27544] [2] DEBUG:   command_status: 0 = 0x
2013-11-22 15:01:23 [27544] [2] DEBUG:   sequence_number: 1 = 0x0001
2013-11-22 15:01:23 [27544] [2] DEBUG:   system_id: NetTalkSMPP
2013-11-22 15:01:23 [27544] [2] DEBUG: SMPP PDU dump ends.
2013-11-22 15:01:24 [27544] [2] DEBUG: SMPP[test]: Got PDU:
2013-11-22 15:01:24 [27544] [2] DEBUG: SMPP PDU 0xb5e009c8 dump:
2013-11-22 15:01:24 [27544] [2] DEBUG:   type_name: unbind
2013-11-22 15:01:24 [27544] [2] DEBUG:   command_id: 6 = 0x0006
2013-11-22 15:01:24 [27544] [2] DEBUG:   command_status: 0 = 0x
2013-11-22 15:01:24 [27544] [2] DEBUG:   sequence_number: 2 = 0x0002
2013-11-22 15:01:24 [27544] [2] DEBUG: SMPP PDU dump ends.
2013-11-22 15:01:24 [27544] [2] DEBUG: SMPP[test]: Sending PDU:
2013-11-22 15:01:24 [27544] [2] DEBUG: SMPP PDU 0xb5e00888 dump:
2013-11-22 15:01:24 [27544] [2] DEBUG:   type_name: unbind_resp
2013-11-22 15:01:24 [27544] [2] DEBUG:   command_id: 2147483654 = 0x8006
2013-11-22 15:01:24 [27544] [2] DEBUG:   command_status: 0 = 

RE: opensmpp

[Rene Kluwen]

Get a copy of the user guide in the doc directory of opensmppbox.

Maybe you need to do a make docs first.

 

== Rene

 

From: users [mailto:users-boun...@kannel.org] On Behalf Of Alok Srivastava
Sent: donderdag 31 oktober 2013 7:00
To: users@kannel.org
Subject: opensmpp

 

dear list

plz help, will i have to configure opensmpp for configuring kannel as a smpp
server.

plz share a tutorial for opensmpp.

thanks 

 

abhi 

RE: OPENSMPP LOGIN ISSUE

[Rene Kluwen]

The system type is case sensitive.

 

From: users [mailto:users-boun...@kannel.org] On Behalf Of michael osakede
Sent: woensdag 23 oktober 2013 13:41
To: users@kannel.org
Subject: OPENSMPP LOGIN ISSUE

 

Hi,

 

I am having issues login into my opensmppbox from a remote kannel gateway.

 

This is my smpplogin.txt

precin4 precin4 vma 208.109.186.98

 

 

Kannel Config(Remote Server)

# SMSC SMPP

group = smsc

smsc-id =  precin4

smsc = smpp

host = xx.xxx.xx.xxx

port = 2346

receive-port = 2346

smsc-username = precin4

smsc-password = precin4

system-type = VMA

interface-version = 52

keepalive = 50

allowed-smsc-id = precin4

transceiver-mode = true

msg-id-type =  0x00

throughput = 12

max-pending-submits = 10

wait-ack = 600

 

OPENSMPP LOG

2013-04-10 13:05:14 [20962] [2] DEBUG: SMPP[abcd]: Got PDU:

2013-04-10 13:05:14 [20962] [2] DEBUG: SMPP PDU 0x7fe1dd50 dump:

2013-04-10 13:05:14 [20962] [2] DEBUG:   type_name: bind_transceiver

2013-04-10 13:05:14 [20962] [2] DEBUG:   command_id: 9 = 0x0009

2013-04-10 13:05:14 [20962] [2] DEBUG:   command_status: 0 = 0x

2013-04-10 13:05:14 [20962] [2] DEBUG:   sequence_number: 1 = 0x0001

2013-04-10 13:05:14 [20962] [2] DEBUG:   system_id: precin4

2013-04-10 13:05:14 [20962] [2] DEBUG:   password: precin4

2013-04-10 13:05:14 [20962] [2] DEBUG:   system_type: VMA

2013-04-10 13:05:14 [20962] [2] DEBUG:   interface_version: 82 = 0x0052

2013-04-10 13:05:14 [20962] [2] DEBUG:   addr_ton: 0 = 0x

2013-04-10 13:05:14 [20962] [2] DEBUG:   addr_npi: 0 = 0x

2013-04-10 13:05:14 [20962] [2] DEBUG:   address_range: NULL

2013-04-10 13:05:14 [20962] [2] DEBUG: SMPP PDU dump ends.

2013-04-10 13:05:14 [20962] [2] DEBUG: SMPP[abcd]: Sending PDU:

2013-04-10 13:05:14 [20962] [2] DEBUG: SMPP PDU 0x7fe1d0001050 dump:

2013-04-10 13:05:14 [20962] [2] DEBUG:   type_name: bind_transceiver_resp

2013-04-10 13:05:14 [20962] [2] DEBUG:   command_id: 2147483657 = 0x8009

2013-04-10 13:05:14 [20962] [2] DEBUG:   command_status: 13 = 0x000d

2013-04-10 13:05:14 [20962] [2] DEBUG:   sequence_number: 1 = 0x0001

2013-04-10 13:05:14 [20962] [2] DEBUG:   system_id: NULL

2013-04-10 13:05:14 [20962] [2] DEBUG: SMPP PDU dump ends.

2013-04-10 13:05:15 [20962] [2] ERROR: Invalid SMPP PDU received.

2013-04-10 13:05:15 [20962] [2] DEBUG: Thread 2
(opensmppbox.c:smpp_to_bearerbox) terminates.

2013-04-10 13:05:16 [20962] [1] DEBUG: Thread 1 (opensmppbox.c:function)
terminates.

 

 

BEARERBOX LOG(remote server)

2013-10-23 12:15:31 [1433] [6] DEBUG: Connecting to xx.xx.xx.xxx

2013-10-23 12:15:31 [1433] [6] DEBUG: SMPP[precin4]: Sending PDU:

2013-10-23 12:15:31 [1433] [6] DEBUG: SMPP PDU 0x7f0f2c000a10 dump:

2013-10-23 12:15:31 [1433] [6] DEBUG:   type_name: bind_transceiver

2013-10-23 12:15:31 [1433] [6] DEBUG:   command_id: 9 = 0x0009

2013-10-23 12:15:31 [1433] [6] DEBUG:   command_status: 0 = 0x

2013-10-23 12:15:31 [1433] [6] DEBUG:   sequence_number: 36 = 0x0024

2013-10-23 12:15:31 [1433] [6] DEBUG:   system_id: precin4

2013-10-23 12:15:31 [1433] [6] DEBUG:   password: precin4

2013-10-23 12:15:31 [1433] [6] DEBUG:   system_type: 

2013-10-23 12:15:31 [1433] [6] DEBUG:   interface_version: 82 = 0x0052

2013-10-23 12:15:31 [1433] [6] DEBUG:   addr_ton: 0 = 0x

2013-10-23 12:15:31 [1433] [6] DEBUG:   addr_npi: 0 = 0x

2013-10-23 12:15:31 [1433] [6] DEBUG:   address_range: NULL

2013-10-23 12:15:31 [1433] [6] DEBUG: SMPP PDU dump ends.

2013-10-23 12:15:31 [1433] [6] DEBUG: SMPP[precin4]: Got PDU:

2013-10-23 12:15:31 [1433] [6] DEBUG: SMPP PDU 0x7f0f2c000a10 dump:

2013-10-23 12:15:31 [1433] [6] DEBUG:   type_name: bind_transceiver_resp

2013-10-23 12:15:31 [1433] [6] DEBUG:   command_id: 2147483657 = 0x8009

2013-10-23 12:15:31 [1433] [6] DEBUG:   command_status: 13 = 0x000d

2013-10-23 12:15:31 [1433] [6] DEBUG:   sequence_number: 36 = 0x0024

2013-10-23 12:15:31 [1433] [6] DEBUG:   system_id: NULL

2013-10-23 12:15:31 [1433] [6] DEBUG: SMPP PDU dump ends.

2013-10-23 12:15:31 [1433] [6] ERROR: SMPP[precin4]: SMSC rejected login to
transmit, code 0x000d (Bind Failed).

2013-10-23 12:15:31 [1433] [6] ERROR: SMPP[precin4]: Couldn't connect to SMS
center (retrying in 10 seconds).

 

What am I doing wrong?

 

Michael

 

 

Re: OPENSMPP User Based Routing

[michael osakede]

Hi,

How do I route sms based on login?

I can route the MO using smsbox-route,
know how do I route MT from the opensmppbox client?

Regards,
Michael



On Wednesday, November 6, 2013 1:00 PM, michael osakede ire...@yahoo.com 
wrote:
 
Hi,

How do I route sms based on login?


Regards,
Michael

Re: OpenSMPP Manual

[spameden]

You can build documentation from SVN repository at svn.kannel.org
config examples as well :)

2013/2/4 michael osakede ire...@yahoo.com:
 Hi,

 Can any one point me in the direction of a good opensmpp documentation with
 sample config files?

 Michael

Re: OpenSMPP Manual

[michael osakede]

Hi,

I was able to achieve the installation.
How can i setup a config file to do the following:


1. Subscriber  = Bearerbox(IP A) = OpenSMPPbox(IP A) = Bearerbox(IP B)
2. Bearerbox(IP B) = OpenSMPPbox(IP A) = Bearerbox(IP A)=Subscriber

Regards,
Michael



 From: spameden spame...@gmail.com
To: michael osakede ire...@yahoo.com 
Cc: users@kannel.org users@kannel.org 
Sent: Monday, February 4, 2013 6:29 PM
Subject: Re: OpenSMPP Manual
 
You can build documentation from SVN repository at svn.kannel.org
config examples as well :)

2013/2/4 michael osakede ire...@yahoo.com:
 Hi,

 Can any one point me in the direction of a good opensmpp documentation with
 sample config files?

 Michael

RE: openSMPP PANIC:

[Rene Kluwen]

1.   What are the steps to reproduce this error?

2.   Could you possbibly do a svup update -r63 and see if the problem
still persists?

 

 

== Rene

 

From: users-boun...@vm1.kannel.org [mailto:users-boun...@vm1.kannel.org] On
Behalf Of Ali Kashif
Sent: maandag 10 december 2012 12:03
To: us...@vm1.kannel.org
Subject: openSMPP PANIC:

 

Dear Users,

 

My open SMPP is giving me following PANIC and closes itself.

 

i have not clue what this this ?

 

 

can anyone help me in this?

2012-12-10 10:53:12 [21885] [2] DEBUG: assemble multi-part message.

2012-12-10 10:53:12 [21885] [2] DEBUG: received 2 of 2.

2012-12-10 10:53:12 [21885] [2] DEBUG: received all parts of multi-part
message.

2012-12-10 10:53:12 [21885] [2] DEBUG: multi-part message, length: 221.

2012-12-10 10:53:12 [21885] [2] PANIC: gwlib/octstr.c:2563:
seems_valid_real: Assertion `ostr-len + 1 = ostr-size' failed. (Called
from gwlib/octstr.c:1308:octstr_insert.)

2012-12-10 10:53:12 [21885] [2] PANIC:
/usr/local/sbin/opensmppbox(gw_backtrace+0xad) [0x80a5c6d]

2012-12-10 10:53:12 [21885] [2] PANIC:
/usr/local/sbin/opensmppbox(gw_panic+0xc8) [0x80a5d48]

2012-12-10 10:53:12 [21885] [2] PANIC: /usr/local/sbin/opensmppbox
[0x80a6583]

2012-12-10 10:53:12 [21885] [2] PANIC:
/usr/local/sbin/opensmppbox(octstr_insert+0x4c) [0x80a992c]

2012-12-10 10:53:12 [21885] [2] PANIC:
/usr/local/sbin/opensmppbox(octstr_append+0x24) [0x80a9a64]

2012-12-10 10:53:12 [21885] [2] PANIC:
/usr/local/sbin/opensmppbox(concat_msgids+0x7b) [0x805736b]

2012-12-10 10:53:12 [21885] [2] PANIC: /usr/local/sbin/opensmppbox
[0x8059507]

2012-12-10 10:53:12 [21885] [2] PANIC: /usr/local/sbin/opensmppbox
[0x809bfc1]

2012-12-10 10:53:12 [21885] [2] PANIC: /lib/i686/nosegneg/libpthread.so.0
[0xd41889]

2012-12-10 10:53:12 [21885] [2] PANIC:
/lib/i686/nosegneg/libc.so.6(clone+0x5e) [0xcab17e]

 

 

 

 

Thanks 

Ali

Re: openSMPP PANIC:

[Ali Kashif]

Hi Rene,

i tried to update the SVN and got this .

[root@vps svn]# svn update -r63
Skipped '.'
[root@vps svn]#


reproduce steps are .
I just download the latest source about 2 or 3 hours back using

svn co https://svn.kannel.org/gateway/trunk
cd trunk

~]#./configure --with-mysql --enable-start-stop-daemon --disable-docs
~]# Make
~]# Make install
~]#
~]# cd addons/opensmppbox/
~]#./configure --with-kannel-dir=/root/kannel/svn/trunk/
~]# Make
~]# Make install
~]#
~]#  cd addons/sqlbox/
~]#./configure --with-kannel-dir=/root/kannel/svn/trunk/
~]# Make
~]# Make install


##SMPP.CONF##
group = core
dlr-storage = mysql

group = mysql-connection
id = dlr-db
host = 127.0.0.1
username = sqlbox
password = password
database = kannel
max-connections = 20

group = dlr-db
id = dlr-db
table = dlr1
field-smsc = smsc
field-timestamp = ts
field-destination = destination
field-source = source
field-service = service
field-url = url
field-mask = mask
field-status = status
field-boxc-id = boxc_id

group = opensmppbox
opensmppbox-id = smppbox1
opensmppbox-port = 8999
bearerbox-host = 127.0.0.1
bearerbox-port = 13002
log-level = 0
log-file = /var/log/kannel/opensmppbox.log
our-system-id = MYID
route-to-smsc = smscr
use-systemid-as-smsboxid = 1
smpp-logins = /usr/local/kannel/clients.txt
##

please let me know if any thing else is needed.

Thanks
Ali




On Mon, Dec 10, 2012 at 3:04 PM, Rene Kluwen rene.klu...@chimit.nl wrote:

 svup update –r63

RE: openSMPP PANIC:

[Rene Kluwen]

When in your svn folder, type:

 

cd trunk/addons/opensmppbox

svn update -r63

 

and make and install again.

 

== Rene

 

From: Ali Kashif [mailto:syedalikas...@gmail.com] 
Sent: maandag 10 december 2012 14:14
To: Rene Kluwen
Cc: us...@vm1.kannel.org
Subject: Re: openSMPP PANIC:

 

Hi Rene,

 

i tried to update the SVN and got this .

 

[root@vps svn]# svn update -r63

Skipped '.'

[root@vps svn]#

 

 

reproduce steps are .

I just download the latest source about 2 or 3 hours back using 

 

svn co https://svn.kannel.org/gateway/trunk

cd trunk

 

~]#./configure --with-mysql --enable-start-stop-daemon --disable-docs

~]# Make

~]# Make install

~]#

~]# cd addons/opensmppbox/

~]#./configure --with-kannel-dir=/root/kannel/svn/trunk/

~]# Make 

~]# Make install

~]#

~]#  cd addons/sqlbox/

~]#./configure --with-kannel-dir=/root/kannel/svn/trunk/

~]# Make 

~]# Make install

 

 

##SMPP.CONF##

group = core

dlr-storage = mysql

 

group = mysql-connection

id = dlr-db

host = 127.0.0.1

username = sqlbox

password = password

database = kannel

max-connections = 20

 

group = dlr-db

id = dlr-db

table = dlr1

field-smsc = smsc

field-timestamp = ts

field-destination = destination

field-source = source

field-service = service

field-url = url

field-mask = mask

field-status = status

field-boxc-id = boxc_id

 

group = opensmppbox

opensmppbox-id = smppbox1

opensmppbox-port = 8999

bearerbox-host = 127.0.0.1

bearerbox-port = 13002

log-level = 0

log-file = /var/log/kannel/opensmppbox.log

our-system-id = MYID

route-to-smsc = smscr

use-systemid-as-smsboxid = 1

smpp-logins = /usr/local/kannel/clients.txt

##

 

please let me know if any thing else is needed.

 

Thanks 

Ali

 

 

 

 

On Mon, Dec 10, 2012 at 3:04 PM, Rene Kluwen rene.klu...@chimit.nl wrote:

svup update -r63

 

RE: OpenSMPP+Kannel: DLR: (dst src) are expected INVETED in the deliver_sm (but remains as in submit_sm)

[info.ubichip]

Hello,

is it possible to have your mysql trigger on the DLR table ?

thanks in advance

-Message d'origine-
De : users-boun...@kannel.org [mailto:users-boun...@kannel.org] De la part de 
Niel
Envoyé : mardi 20 mars 2012 07:54
À : users@kannel.org
Objet : Re: OpenSMPP+Kannel: DLR: (dst  src) are expected INVETED in the 
deliver_sm (but remains as in submit_sm)


Hi,

I know this is old, but, this issue still exists in the latest SVN.

My brearbox is set to use mysql storage for DLRs. As workaround I added a mysql 
trigger on the DLR table before insert that swaps the src and dest values.

Regards,



Dídac Royo wrote:
 
 Hi Users,
 
 I need your help.
 
  We have a problem in our Kannel + openSMPPbox. The values of parameters:
 dst  src are expected INVETED in the deliver_sm, I'm I correct?
 
 
 In the logs *source_addr*  *destination_addr* have the same in both *
 submit_sm* and *deliver_sm* operations (when we expect them inverted 
 in the
 deliver_sm)
 
 
This is our log for the submit_sm:
 
 
 *2011-03-01 16:50:00 [634] [6] DEBUG: SMPP[ISMSAD]: Got PDU:
 2011-03-01 16:50:00 [634] [6] DEBUG: SMPP PDU 0x73b700 dump:
 2011-03-01 16:50:00 [634] [6] DEBUG:   type_name: submit_sm
 2011-03-01 16:50:00 [634] [6] DEBUG:   command_id: 4 = 0x0004
 2011-03-01 16:50:00 [634] [6] DEBUG:   command_status: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   sequence_number: 1404 = 0x057c
 2011-03-01 16:50:00 [634] [6] DEBUG:   service_type: NULL
 2011-03-01 16:50:00 [634] [6] DEBUG:   source_addr_ton: 5 = 0x0005
 2011-03-01 16:50:00 [634] [6] DEBUG:   source_addr_npi: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   source_addr: Info
 2011-03-01 16:50:00 [634] [6] DEBUG:   dest_addr_ton: 1 = 0x0001
 2011-03-01 16:50:00 [634] [6] DEBUG:   dest_addr_npi: 1 = 0x0001
 2011-03-01 16:50:00 [634] [6] DEBUG:   destination_addr: 34695839615
 2011-03-01 16:50:00 [634] [6] DEBUG:   esm_class: 3 = 0x0003
 2011-03-01 16:50:00 [634] [6] DEBUG:   protocol_id: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   priority_flag: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   schedule_delivery_time: NULL
 2011-03-01 16:50:00 [634] [6] DEBUG:   validity_period: NULL
 2011-03-01 16:50:00 [634] [6] DEBUG:   registered_delivery: 1 = 0x0001
 2011-03-01 16:50:00 [634] [6] DEBUG:   replace_if_present_flag: 0 =
 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   data_coding: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   sm_default_msg_id: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   sm_length: 10 = 0x000a
 2011-03-01 16:50:00 [634] [6] DEBUG:   short_message: test 16:48
 2011-03-01 16:50:00 [634] [6] DEBUG: SMPP PDU dump ends.*
 
 
and this is our log for the deiver_sm:
 
 
  *2011-03-01 16:50:04 [634] [5] DEBUG: SMPP[ISMSAD]: Sending PDU:
 2011-03-01 16:50:04 [634] [5] DEBUG: SMPP PDU 0x73fd30 dump:
 2011-03-01 16:50:04 [634] [5] DEBUG:   type_name: deliver_sm
 2011-03-01 16:50:04 [634] [5] DEBUG:   command_id: 5 = 0x0005
 2011-03-01 16:50:04 [634] [5] DEBUG:   command_status: 0 = 0x
 2011-03-01 16:50:04 [634] [5] DEBUG:   sequence_number: 1 = 0x0001
 2011-03-01 16:50:04 [634] [5] DEBUG:   service_type: NULL
 2011-03-01 16:50:04 [634] [5] DEBUG:   source_addr_ton: 2 = 0x0002
 2011-03-01 16:50:04 [634] [5] DEBUG:   source_addr_npi: 1 = 0x0001
 2011-03-01 16:50:04 [634] [5] DEBUG:   source_addr: Info
 2011-03-01 16:50:04 [634] [5] DEBUG:   dest_addr_ton: 1 = 0x0001
 2011-03-01 16:50:04 [634] [5] DEBUG:   dest_addr_npi: 1 = 0x0001
 2011-03-01 16:50:04 [634] [5] DEBUG:   destination_addr: 34695839615
 2011-03-01 16:50:04 [634] [5] DEBUG:   esm_class: 4 = 0x0004
 2011-03-01 16:50:04 [634] [5] DEBUG:   protocol_id: 0 = 0x
 2011-03-01 16:50:04 [634] [5] DEBUG:   priority_flag: 0 = 0x
 2011-03-01 16:50:04 [634] [5] DEBUG:   schedule_delivery_time: NULL
 2011-03-01 16:50:04 [634] [5] DEBUG:   validity_period: NULL
 2011-03-01 16:50:04 [634] [5] DEBUG:   registered_delivery: 0 = 0x
 2011-03-01 16:50:04 [634] [5] DEBUG:   replace_if_present_flag: 0 =
 0x
 2011-03-01 16:50:04 [634] [5] DEBUG:   data_coding: 0 = 0x
 2011-03-01 16:50:04 [634] [5] DEBUG:   sm_default_msg_id: 0 = 0x
 2011-03-01 16:50:04 [634] [5] DEBUG:   sm_length: 0 = 0x
 2011-03-01 16:50:04 [634] [5] DEBUG:   short_message:
 2011-03-01 16:50:04 [634] [5] DEBUG:Octet string at 0x73a350:
 2011-03-01 16:50:04 [634] [5] DEBUG:  len:  112
 2011-03-01 16:50:04 [634] [5] DEBUG:  size: 1024
 2011-03-01 16:50:04 [634] [5] DEBUG:  immutable: 0
 2011-03-01 16:50:04 [634] [5] DEBUG:  data: 69 64 3a 33 30 37 32 30 66
 30 36 20 73 75 62 3a   id:30720f06 sub:
 2011-03-01 16:50:04 [634] [5] DEBUG:  data: 30 30 31 20 64 6c 76 72 64
 3a 30 30 31 20 73 75   001 dlvrd:001 su
 2011-03-01 16:50:04 [634] [5] DEBUG:  data: 62 6d 69 74 20 64 61 74 65
 3a 31 31 30 33 30 31   bmit date:110301
 2011-03-01 16:50:04 [634

RE: OpenSMPP+Kannel: DLR: (dst src) are expected INVETED in the deliver_sm (but remains as in submit_sm)

[Niel]

Yes, that is where the trigger should be. My kannel config has been set to
use the table kannel.dlr, and columns dest and src.

The MySQL command would look something like this:

delimiter $
CREATE TRIGGER `kannel`.`dlr_src_dest_swap_trigger`
  BEFORE INSERT ON `kannel`.`dlr`
  FOR EACH ROW
  BEGIN
DECLARE temp VARCHAR(100);
SET temp = NEW.src;
SET NEW.src = NEW.dest;
SET NEW.dest = temp;
  END
$

Other useful commands:

SHOW TRIGGERS;
DROP TRIGGER `dlr_src_dest_swap_trigger`;
SHOW CREATE TRIGGER `dlr_src_dest_swap_trigger`;

Regards,



info.ubichip wrote:
 
 Hello,
 
 is it possible to have your mysql trigger on the DLR table ?
 
 thanks in advance
 
 -Message d'origine-
 De : users-boun...@kannel.org [mailto:users-boun...@kannel.org] De la part
 de Niel
 Envoyé : mardi 20 mars 2012 07:54
 À : users@kannel.org
 Objet : Re: OpenSMPP+Kannel: DLR: (dst  src) are expected INVETED in the
 deliver_sm (but remains as in submit_sm)
 
 
 Hi,
 
 I know this is old, but, this issue still exists in the latest SVN.
 
 My brearbox is set to use mysql storage for DLRs. As workaround I added a
 mysql trigger on the DLR table before insert that swaps the src and dest
 values.
 
 Regards,
 
 
 
 Dídac Royo wrote:
 
 Hi Users,
 
 I need your help.
 
  We have a problem in our Kannel + openSMPPbox. The values of parameters:
 dst  src are expected INVETED in the deliver_sm, I'm I correct?
 
 
 In the logs *source_addr*  *destination_addr* have the same in both *
 submit_sm* and *deliver_sm* operations (when we expect them inverted 
 in the
 deliver_sm)
 
 
This is our log for the submit_sm:
 
 
 *2011-03-01 16:50:00 [634] [6] DEBUG: SMPP[ISMSAD]: Got PDU:
 2011-03-01 16:50:00 [634] [6] DEBUG: SMPP PDU 0x73b700 dump:
 2011-03-01 16:50:00 [634] [6] DEBUG:   type_name: submit_sm
 2011-03-01 16:50:00 [634] [6] DEBUG:   command_id: 4 = 0x0004
 2011-03-01 16:50:00 [634] [6] DEBUG:   command_status: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   sequence_number: 1404 = 0x057c
 2011-03-01 16:50:00 [634] [6] DEBUG:   service_type: NULL
 2011-03-01 16:50:00 [634] [6] DEBUG:   source_addr_ton: 5 = 0x0005
 2011-03-01 16:50:00 [634] [6] DEBUG:   source_addr_npi: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   source_addr: Info
 2011-03-01 16:50:00 [634] [6] DEBUG:   dest_addr_ton: 1 = 0x0001
 2011-03-01 16:50:00 [634] [6] DEBUG:   dest_addr_npi: 1 = 0x0001
 2011-03-01 16:50:00 [634] [6] DEBUG:   destination_addr: 34695839615
 2011-03-01 16:50:00 [634] [6] DEBUG:   esm_class: 3 = 0x0003
 2011-03-01 16:50:00 [634] [6] DEBUG:   protocol_id: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   priority_flag: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   schedule_delivery_time: NULL
 2011-03-01 16:50:00 [634] [6] DEBUG:   validity_period: NULL
 2011-03-01 16:50:00 [634] [6] DEBUG:   registered_delivery: 1 =
 0x0001
 2011-03-01 16:50:00 [634] [6] DEBUG:   replace_if_present_flag: 0 =
 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   data_coding: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   sm_default_msg_id: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   sm_length: 10 = 0x000a
 2011-03-01 16:50:00 [634] [6] DEBUG:   short_message: test 16:48
 2011-03-01 16:50:00 [634] [6] DEBUG: SMPP PDU dump ends.*
 
 
and this is our log for the deiver_sm:
 
 
  *2011-03-01 16:50:04 [634] [5] DEBUG: SMPP[ISMSAD]: Sending PDU:
 2011-03-01 16:50:04 [634] [5] DEBUG: SMPP PDU 0x73fd30 dump:
 2011-03-01 16:50:04 [634] [5] DEBUG:   type_name: deliver_sm
 2011-03-01 16:50:04 [634] [5] DEBUG:   command_id: 5 = 0x0005
 2011-03-01 16:50:04 [634] [5] DEBUG:   command_status: 0 = 0x
 2011-03-01 16:50:04 [634] [5] DEBUG:   sequence_number: 1 = 0x0001
 2011-03-01 16:50:04 [634] [5] DEBUG:   service_type: NULL
 2011-03-01 16:50:04 [634] [5] DEBUG:   source_addr_ton: 2 = 0x0002
 2011-03-01 16:50:04 [634] [5] DEBUG:   source_addr_npi: 1 = 0x0001
 2011-03-01 16:50:04 [634] [5] DEBUG:   source_addr: Info
 2011-03-01 16:50:04 [634] [5] DEBUG:   dest_addr_ton: 1 = 0x0001
 2011-03-01 16:50:04 [634] [5] DEBUG:   dest_addr_npi: 1 = 0x0001
 2011-03-01 16:50:04 [634] [5] DEBUG:   destination_addr: 34695839615
 2011-03-01 16:50:04 [634] [5] DEBUG:   esm_class: 4 = 0x0004
 2011-03-01 16:50:04 [634] [5] DEBUG:   protocol_id: 0 = 0x
 2011-03-01 16:50:04 [634] [5] DEBUG:   priority_flag: 0 = 0x
 2011-03-01 16:50:04 [634] [5] DEBUG:   schedule_delivery_time: NULL
 2011-03-01 16:50:04 [634] [5] DEBUG:   validity_period: NULL
 2011-03-01 16:50:04 [634] [5] DEBUG:   registered_delivery: 0 =
 0x
 2011-03-01 16:50:04 [634] [5] DEBUG:   replace_if_present_flag: 0 =
 0x
 2011-03-01 16:50:04 [634] [5] DEBUG:   data_coding: 0 = 0x
 2011-03-01 16:50:04 [634] [5] DEBUG:   sm_default_msg_id: 0 = 0x
 2011-03-01 16:50:04 [634] [5] DEBUG:   sm_length: 0 = 0x
 2011-03-01 16:50:04 [634] [5] DEBUG:   short_message

RE: OpenSMPP+Kannel: DLR: (dst src) are expected INVETED in the deliver_sm (but remains as in submit_sm)

[info.ubichip]

Thanks a lot, I will try it very soon.

one more question : does it change the way the dlr are coming back to the 
originator of the request through SMPP ?

-Message d'origine-
De : users-boun...@kannel.org [mailto:users-boun...@kannel.org] De la part de 
Niel
Envoyé : vendredi 15 juin 2012 13:25
À : users@kannel.org
Objet : RE: OpenSMPP+Kannel: DLR: (dst  src) are expected INVETED in the 
deliver_sm (but remains as in submit_sm)


Yes, that is where the trigger should be. My kannel config has been set to use 
the table kannel.dlr, and columns dest and src.

The MySQL command would look something like this:

delimiter $
CREATE TRIGGER `kannel`.`dlr_src_dest_swap_trigger`
  BEFORE INSERT ON `kannel`.`dlr`
  FOR EACH ROW
  BEGIN
DECLARE temp VARCHAR(100);
SET temp = NEW.src;
SET NEW.src = NEW.dest;
SET NEW.dest = temp;
  END
$

Other useful commands:

SHOW TRIGGERS;
DROP TRIGGER `dlr_src_dest_swap_trigger`; SHOW CREATE TRIGGER 
`dlr_src_dest_swap_trigger`;

Regards,



info.ubichip wrote:
 
 Hello,
 
 is it possible to have your mysql trigger on the DLR table ?
 
 thanks in advance
 
 -Message d'origine-
 De : users-boun...@kannel.org [mailto:users-boun...@kannel.org] De la 
 part de Niel Envoyé : mardi 20 mars 2012 07:54 À : users@kannel.org 
 Objet : Re: OpenSMPP+Kannel: DLR: (dst  src) are expected INVETED in 
 the deliver_sm (but remains as in submit_sm)
 
 
 Hi,
 
 I know this is old, but, this issue still exists in the latest SVN.
 
 My brearbox is set to use mysql storage for DLRs. As workaround I 
 added a mysql trigger on the DLR table before insert that swaps the 
 src and dest values.
 
 Regards,
 
 
 
 Dídac Royo wrote:
 
 Hi Users,
 
 I need your help.
 
  We have a problem in our Kannel + openSMPPbox. The values of parameters:
 dst  src are expected INVETED in the deliver_sm, I'm I correct?
 
 
 In the logs *source_addr*  *destination_addr* have the same in both 
 *
 submit_sm* and *deliver_sm* operations (when we expect them inverted 
 in the
 deliver_sm)
 
 
This is our log for the submit_sm:
 
 
 *2011-03-01 16:50:00 [634] [6] DEBUG: SMPP[ISMSAD]: Got PDU:
 2011-03-01 16:50:00 [634] [6] DEBUG: SMPP PDU 0x73b700 dump:
 2011-03-01 16:50:00 [634] [6] DEBUG:   type_name: submit_sm
 2011-03-01 16:50:00 [634] [6] DEBUG:   command_id: 4 = 0x0004
 2011-03-01 16:50:00 [634] [6] DEBUG:   command_status: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   sequence_number: 1404 = 0x057c
 2011-03-01 16:50:00 [634] [6] DEBUG:   service_type: NULL
 2011-03-01 16:50:00 [634] [6] DEBUG:   source_addr_ton: 5 = 0x0005
 2011-03-01 16:50:00 [634] [6] DEBUG:   source_addr_npi: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   source_addr: Info
 2011-03-01 16:50:00 [634] [6] DEBUG:   dest_addr_ton: 1 = 0x0001
 2011-03-01 16:50:00 [634] [6] DEBUG:   dest_addr_npi: 1 = 0x0001
 2011-03-01 16:50:00 [634] [6] DEBUG:   destination_addr: 34695839615
 2011-03-01 16:50:00 [634] [6] DEBUG:   esm_class: 3 = 0x0003
 2011-03-01 16:50:00 [634] [6] DEBUG:   protocol_id: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   priority_flag: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   schedule_delivery_time: NULL
 2011-03-01 16:50:00 [634] [6] DEBUG:   validity_period: NULL
 2011-03-01 16:50:00 [634] [6] DEBUG:   registered_delivery: 1 =
 0x0001
 2011-03-01 16:50:00 [634] [6] DEBUG:   replace_if_present_flag: 0 =
 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   data_coding: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   sm_default_msg_id: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   sm_length: 10 = 0x000a
 2011-03-01 16:50:00 [634] [6] DEBUG:   short_message: test 16:48
 2011-03-01 16:50:00 [634] [6] DEBUG: SMPP PDU dump ends.*
 
 
and this is our log for the deiver_sm:
 
 
  *2011-03-01 16:50:04 [634] [5] DEBUG: SMPP[ISMSAD]: Sending PDU:
 2011-03-01 16:50:04 [634] [5] DEBUG: SMPP PDU 0x73fd30 dump:
 2011-03-01 16:50:04 [634] [5] DEBUG:   type_name: deliver_sm
 2011-03-01 16:50:04 [634] [5] DEBUG:   command_id: 5 = 0x0005
 2011-03-01 16:50:04 [634] [5] DEBUG:   command_status: 0 = 0x
 2011-03-01 16:50:04 [634] [5] DEBUG:   sequence_number: 1 = 0x0001
 2011-03-01 16:50:04 [634] [5] DEBUG:   service_type: NULL
 2011-03-01 16:50:04 [634] [5] DEBUG:   source_addr_ton: 2 = 0x0002
 2011-03-01 16:50:04 [634] [5] DEBUG:   source_addr_npi: 1 = 0x0001
 2011-03-01 16:50:04 [634] [5] DEBUG:   source_addr: Info
 2011-03-01 16:50:04 [634] [5] DEBUG:   dest_addr_ton: 1 = 0x0001
 2011-03-01 16:50:04 [634] [5] DEBUG:   dest_addr_npi: 1 = 0x0001
 2011-03-01 16:50:04 [634] [5] DEBUG:   destination_addr: 34695839615
 2011-03-01 16:50:04 [634] [5] DEBUG:   esm_class: 4 = 0x0004
 2011-03-01 16:50:04 [634] [5] DEBUG:   protocol_id: 0 = 0x
 2011-03-01 16:50:04 [634] [5] DEBUG:   priority_flag: 0 = 0x
 2011-03-01 16:50:04 [634] [5] DEBUG:   schedule_delivery_time: NULL
 2011-03-01 16:50:04 [634] [5

RE: OpenSMPP+Kannel: DLR: (dst src) are expected INVETED in the deliver_sm (but remains as in submit_sm)

[info.ubichip]

Related to my last question, when a DLR is coming,  the mysql request is like :

SELECT `mask`, `service`, `url`, `source`, `
destination`, `boxc` FROM `dlr` WHERE `smsc`=? AND `ts`=? AND `destination` 
LIKE CONCAT(
'%', ?) LIMIT 1

so if the destination and source are swapped, it will never match ?



-Message d'origine-
De : users-boun...@kannel.org [mailto:users-boun...@kannel.org] De la part de 
info.ubichip
Envoyé : vendredi 15 juin 2012 13:28
À : 'Niel'; users@kannel.org
Objet : RE: OpenSMPP+Kannel: DLR: (dst  src) are expected INVETED in the 
deliver_sm (but remains as in submit_sm)

Thanks a lot, I will try it very soon.

one more question : does it change the way the dlr are coming back to the 
originator of the request through SMPP ?

-Message d'origine-
De : users-boun...@kannel.org [mailto:users-boun...@kannel.org] De la part de 
Niel Envoyé : vendredi 15 juin 2012 13:25 À : users@kannel.org Objet : RE: 
OpenSMPP+Kannel: DLR: (dst  src) are expected INVETED in the deliver_sm (but 
remains as in submit_sm)


Yes, that is where the trigger should be. My kannel config has been set to use 
the table kannel.dlr, and columns dest and src.

The MySQL command would look something like this:

delimiter $
CREATE TRIGGER `kannel`.`dlr_src_dest_swap_trigger`
  BEFORE INSERT ON `kannel`.`dlr`
  FOR EACH ROW
  BEGIN
DECLARE temp VARCHAR(100);
SET temp = NEW.src;
SET NEW.src = NEW.dest;
SET NEW.dest = temp;
  END
$

Other useful commands:

SHOW TRIGGERS;
DROP TRIGGER `dlr_src_dest_swap_trigger`; SHOW CREATE TRIGGER 
`dlr_src_dest_swap_trigger`;

Regards,



info.ubichip wrote:
 
 Hello,
 
 is it possible to have your mysql trigger on the DLR table ?
 
 thanks in advance
 
 -Message d'origine-
 De : users-boun...@kannel.org [mailto:users-boun...@kannel.org] De la 
 part de Niel Envoyé : mardi 20 mars 2012 07:54 À : users@kannel.org 
 Objet : Re: OpenSMPP+Kannel: DLR: (dst  src) are expected INVETED in 
 the deliver_sm (but remains as in submit_sm)
 
 
 Hi,
 
 I know this is old, but, this issue still exists in the latest SVN.
 
 My brearbox is set to use mysql storage for DLRs. As workaround I 
 added a mysql trigger on the DLR table before insert that swaps the 
 src and dest values.
 
 Regards,
 
 
 
 Dídac Royo wrote:
 
 Hi Users,
 
 I need your help.
 
  We have a problem in our Kannel + openSMPPbox. The values of parameters:
 dst  src are expected INVETED in the deliver_sm, I'm I correct?
 
 
 In the logs *source_addr*  *destination_addr* have the same in both
 *
 submit_sm* and *deliver_sm* operations (when we expect them inverted 
 in the
 deliver_sm)
 
 
This is our log for the submit_sm:
 
 
 *2011-03-01 16:50:00 [634] [6] DEBUG: SMPP[ISMSAD]: Got PDU:
 2011-03-01 16:50:00 [634] [6] DEBUG: SMPP PDU 0x73b700 dump:
 2011-03-01 16:50:00 [634] [6] DEBUG:   type_name: submit_sm
 2011-03-01 16:50:00 [634] [6] DEBUG:   command_id: 4 = 0x0004
 2011-03-01 16:50:00 [634] [6] DEBUG:   command_status: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   sequence_number: 1404 = 0x057c
 2011-03-01 16:50:00 [634] [6] DEBUG:   service_type: NULL
 2011-03-01 16:50:00 [634] [6] DEBUG:   source_addr_ton: 5 = 0x0005
 2011-03-01 16:50:00 [634] [6] DEBUG:   source_addr_npi: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   source_addr: Info
 2011-03-01 16:50:00 [634] [6] DEBUG:   dest_addr_ton: 1 = 0x0001
 2011-03-01 16:50:00 [634] [6] DEBUG:   dest_addr_npi: 1 = 0x0001
 2011-03-01 16:50:00 [634] [6] DEBUG:   destination_addr: 34695839615
 2011-03-01 16:50:00 [634] [6] DEBUG:   esm_class: 3 = 0x0003
 2011-03-01 16:50:00 [634] [6] DEBUG:   protocol_id: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   priority_flag: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   schedule_delivery_time: NULL
 2011-03-01 16:50:00 [634] [6] DEBUG:   validity_period: NULL
 2011-03-01 16:50:00 [634] [6] DEBUG:   registered_delivery: 1 =
 0x0001
 2011-03-01 16:50:00 [634] [6] DEBUG:   replace_if_present_flag: 0 =
 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   data_coding: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   sm_default_msg_id: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   sm_length: 10 = 0x000a
 2011-03-01 16:50:00 [634] [6] DEBUG:   short_message: test 16:48
 2011-03-01 16:50:00 [634] [6] DEBUG: SMPP PDU dump ends.*
 
 
and this is our log for the deiver_sm:
 
 
  *2011-03-01 16:50:04 [634] [5] DEBUG: SMPP[ISMSAD]: Sending PDU:
 2011-03-01 16:50:04 [634] [5] DEBUG: SMPP PDU 0x73fd30 dump:
 2011-03-01 16:50:04 [634] [5] DEBUG:   type_name: deliver_sm
 2011-03-01 16:50:04 [634] [5] DEBUG:   command_id: 5 = 0x0005
 2011-03-01 16:50:04 [634] [5] DEBUG:   command_status: 0 = 0x
 2011-03-01 16:50:04 [634] [5] DEBUG:   sequence_number: 1 = 0x0001
 2011-03-01 16:50:04 [634] [5] DEBUG:   service_type: NULL
 2011-03-01 16:50:04 [634] [5] DEBUG:   source_addr_ton: 2 = 0x0002
 2011-03-01 16:50:04 [634] [5] DEBUG

RE: OpenSMPP+Kannel: DLR: (dst src) are expected INVETED in the deliver_sm (but remains as in submit_sm)

[Niel]

Hi,

This is intended for swapping the src and dest for delivery report for
clients connected using opensmppbox. 

If you are using the same bearerbox for other purposes, such as http smsc
and/or proxy, the delivery reports src and dest will also be swapped around.
You might need to swap the fields in the get-url or via script.

Personally I use a different bearerbox for each gateway, and a separate one
for opensmppbox, due to smsbox not being able to deal with any form of real
load. Each bearerbox has it's own mysql dlr table, and I only apply the
trigger to the ones using opensmppbox.

Luckily, soon kannel will be past memory; a horror story to tell my kids
around the campfire :)

Regards,



info.ubichip wrote:
 
 Thanks a lot, I will try it very soon.
 
 one more question : does it change the way the dlr are coming back to the
 originator of the request through SMPP ?
 
 -Message d'origine-
 De : users-boun...@kannel.org [mailto:users-boun...@kannel.org] De la part
 de Niel
 Envoyé : vendredi 15 juin 2012 13:25
 À : users@kannel.org
 Objet : RE: OpenSMPP+Kannel: DLR: (dst  src) are expected INVETED in the
 deliver_sm (but remains as in submit_sm)
 
 
 Yes, that is where the trigger should be. My kannel config has been set to
 use the table kannel.dlr, and columns dest and src.
 
 The MySQL command would look something like this:
 
 delimiter $
 CREATE TRIGGER `kannel`.`dlr_src_dest_swap_trigger`
   BEFORE INSERT ON `kannel`.`dlr`
   FOR EACH ROW
   BEGIN
 DECLARE temp VARCHAR(100);
 SET temp = NEW.src;
 SET NEW.src = NEW.dest;
 SET NEW.dest = temp;
   END
 $
 
 Other useful commands:
 
 SHOW TRIGGERS;
 DROP TRIGGER `dlr_src_dest_swap_trigger`; SHOW CREATE TRIGGER
 `dlr_src_dest_swap_trigger`;
 
 Regards,
 
 
 
 info.ubichip wrote:
 
 Hello,
 
 is it possible to have your mysql trigger on the DLR table ?
 
 thanks in advance
 
 -Message d'origine-
 De : users-boun...@kannel.org [mailto:users-boun...@kannel.org] De la 
 part de Niel Envoyé : mardi 20 mars 2012 07:54 À : users@kannel.org 
 Objet : Re: OpenSMPP+Kannel: DLR: (dst  src) are expected INVETED in 
 the deliver_sm (but remains as in submit_sm)
 
 
 Hi,
 
 I know this is old, but, this issue still exists in the latest SVN.
 
 My brearbox is set to use mysql storage for DLRs. As workaround I 
 added a mysql trigger on the DLR table before insert that swaps the 
 src and dest values.
 
 Regards,
 
 
 
 Dídac Royo wrote:
 
 Hi Users,
 
 I need your help.
 
  We have a problem in our Kannel + openSMPPbox. The values of
 parameters:
 dst  src are expected INVETED in the deliver_sm, I'm I correct?
 
 
 In the logs *source_addr*  *destination_addr* have the same in both 
 *
 submit_sm* and *deliver_sm* operations (when we expect them inverted 
 in the
 deliver_sm)
 
 
This is our log for the submit_sm:
 
 
 *2011-03-01 16:50:00 [634] [6] DEBUG: SMPP[ISMSAD]: Got PDU:
 2011-03-01 16:50:00 [634] [6] DEBUG: SMPP PDU 0x73b700 dump:
 2011-03-01 16:50:00 [634] [6] DEBUG:   type_name: submit_sm
 2011-03-01 16:50:00 [634] [6] DEBUG:   command_id: 4 = 0x0004
 2011-03-01 16:50:00 [634] [6] DEBUG:   command_status: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   sequence_number: 1404 =
 0x057c
 2011-03-01 16:50:00 [634] [6] DEBUG:   service_type: NULL
 2011-03-01 16:50:00 [634] [6] DEBUG:   source_addr_ton: 5 = 0x0005
 2011-03-01 16:50:00 [634] [6] DEBUG:   source_addr_npi: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   source_addr: Info
 2011-03-01 16:50:00 [634] [6] DEBUG:   dest_addr_ton: 1 = 0x0001
 2011-03-01 16:50:00 [634] [6] DEBUG:   dest_addr_npi: 1 = 0x0001
 2011-03-01 16:50:00 [634] [6] DEBUG:   destination_addr: 34695839615
 2011-03-01 16:50:00 [634] [6] DEBUG:   esm_class: 3 = 0x0003
 2011-03-01 16:50:00 [634] [6] DEBUG:   protocol_id: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   priority_flag: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   schedule_delivery_time: NULL
 2011-03-01 16:50:00 [634] [6] DEBUG:   validity_period: NULL
 2011-03-01 16:50:00 [634] [6] DEBUG:   registered_delivery: 1 =
 0x0001
 2011-03-01 16:50:00 [634] [6] DEBUG:   replace_if_present_flag: 0 =
 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   data_coding: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   sm_default_msg_id: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   sm_length: 10 = 0x000a
 2011-03-01 16:50:00 [634] [6] DEBUG:   short_message: test 16:48
 2011-03-01 16:50:00 [634] [6] DEBUG: SMPP PDU dump ends.*
 
 
and this is our log for the deiver_sm:
 
 
  *2011-03-01 16:50:04 [634] [5] DEBUG: SMPP[ISMSAD]: Sending PDU:
 2011-03-01 16:50:04 [634] [5] DEBUG: SMPP PDU 0x73fd30 dump:
 2011-03-01 16:50:04 [634] [5] DEBUG:   type_name: deliver_sm
 2011-03-01 16:50:04 [634] [5] DEBUG:   command_id: 5 = 0x0005
 2011-03-01 16:50:04 [634] [5] DEBUG:   command_status: 0 = 0x
 2011-03-01 16:50:04 [634] [5] DEBUG:   sequence_number: 1 = 0x0001
 2011-03

RE: OpenSMPP+Kannel: DLR: (dst src) are expected INVETED in the deliver_sm (but remains as in submit_sm)

[info.ubichip]

Thanks for your answer again.

which opensmppbox are you using ? I just checked the svn repository, it looks 
some dlr source code is now inside the opensmppbox, perhaps there is a good way 
to make correction inside direclty ?

I'm not sure to understand kannel will be past memory, do you quit the 
telecom world or kannel is going to die ?

Best regards

-Message d'origine-
De : users-boun...@kannel.org [mailto:users-boun...@kannel.org] De la part de 
Niel
Envoyé : vendredi 15 juin 2012 13:58
À : users@kannel.org
Objet : RE: OpenSMPP+Kannel: DLR: (dst  src) are expected INVETED in the 
deliver_sm (but remains as in submit_sm)


Hi,

This is intended for swapping the src and dest for delivery report for clients 
connected using opensmppbox. 

If you are using the same bearerbox for other purposes, such as http smsc 
and/or proxy, the delivery reports src and dest will also be swapped around.
You might need to swap the fields in the get-url or via script.

Personally I use a different bearerbox for each gateway, and a separate one for 
opensmppbox, due to smsbox not being able to deal with any form of real load. 
Each bearerbox has it's own mysql dlr table, and I only apply the trigger to 
the ones using opensmppbox.

Luckily, soon kannel will be past memory; a horror story to tell my kids around 
the campfire :)

Regards,



info.ubichip wrote:
 
 Thanks a lot, I will try it very soon.
 
 one more question : does it change the way the dlr are coming back to 
 the originator of the request through SMPP ?
 
 -Message d'origine-
 De : users-boun...@kannel.org [mailto:users-boun...@kannel.org] De la 
 part de Niel Envoyé : vendredi 15 juin 2012 13:25 À : users@kannel.org 
 Objet : RE: OpenSMPP+Kannel: DLR: (dst  src) are expected INVETED in 
 the deliver_sm (but remains as in submit_sm)
 
 
 Yes, that is where the trigger should be. My kannel config has been 
 set to use the table kannel.dlr, and columns dest and src.
 
 The MySQL command would look something like this:
 
 delimiter $
 CREATE TRIGGER `kannel`.`dlr_src_dest_swap_trigger`
   BEFORE INSERT ON `kannel`.`dlr`
   FOR EACH ROW
   BEGIN
 DECLARE temp VARCHAR(100);
 SET temp = NEW.src;
 SET NEW.src = NEW.dest;
 SET NEW.dest = temp;
   END
 $
 
 Other useful commands:
 
 SHOW TRIGGERS;
 DROP TRIGGER `dlr_src_dest_swap_trigger`; SHOW CREATE TRIGGER 
 `dlr_src_dest_swap_trigger`;
 
 Regards,
 
 
 
 info.ubichip wrote:
 
 Hello,
 
 is it possible to have your mysql trigger on the DLR table ?
 
 thanks in advance
 
 -Message d'origine-
 De : users-boun...@kannel.org [mailto:users-boun...@kannel.org] De la 
 part de Niel Envoyé : mardi 20 mars 2012 07:54 À : users@kannel.org 
 Objet : Re: OpenSMPP+Kannel: DLR: (dst  src) are expected INVETED in 
 the deliver_sm (but remains as in submit_sm)
 
 
 Hi,
 
 I know this is old, but, this issue still exists in the latest SVN.
 
 My brearbox is set to use mysql storage for DLRs. As workaround I 
 added a mysql trigger on the DLR table before insert that swaps the 
 src and dest values.
 
 Regards,
 
 
 
 Dídac Royo wrote:
 
 Hi Users,
 
 I need your help.
 
  We have a problem in our Kannel + openSMPPbox. The values of
 parameters:
 dst  src are expected INVETED in the deliver_sm, I'm I correct?
 
 
 In the logs *source_addr*  *destination_addr* have the same in both
 *
 submit_sm* and *deliver_sm* operations (when we expect them inverted 
 in the
 deliver_sm)
 
 
This is our log for the submit_sm:
 
 
 *2011-03-01 16:50:00 [634] [6] DEBUG: SMPP[ISMSAD]: Got PDU:
 2011-03-01 16:50:00 [634] [6] DEBUG: SMPP PDU 0x73b700 dump:
 2011-03-01 16:50:00 [634] [6] DEBUG:   type_name: submit_sm
 2011-03-01 16:50:00 [634] [6] DEBUG:   command_id: 4 = 0x0004
 2011-03-01 16:50:00 [634] [6] DEBUG:   command_status: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   sequence_number: 1404 =
 0x057c
 2011-03-01 16:50:00 [634] [6] DEBUG:   service_type: NULL
 2011-03-01 16:50:00 [634] [6] DEBUG:   source_addr_ton: 5 = 0x0005
 2011-03-01 16:50:00 [634] [6] DEBUG:   source_addr_npi: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   source_addr: Info
 2011-03-01 16:50:00 [634] [6] DEBUG:   dest_addr_ton: 1 = 0x0001
 2011-03-01 16:50:00 [634] [6] DEBUG:   dest_addr_npi: 1 = 0x0001
 2011-03-01 16:50:00 [634] [6] DEBUG:   destination_addr: 34695839615
 2011-03-01 16:50:00 [634] [6] DEBUG:   esm_class: 3 = 0x0003
 2011-03-01 16:50:00 [634] [6] DEBUG:   protocol_id: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   priority_flag: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   schedule_delivery_time: NULL
 2011-03-01 16:50:00 [634] [6] DEBUG:   validity_period: NULL
 2011-03-01 16:50:00 [634] [6] DEBUG:   registered_delivery: 1 =
 0x0001
 2011-03-01 16:50:00 [634] [6] DEBUG:   replace_if_present_flag: 0 =
 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   data_coding: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   sm_default_msg_id: 0

RE: OpenSMPP+Kannel: DLR: (dst src) are expected INVETED in the deliver_sm (but remains as in submit_sm)

[Niel]

I'm using SVN dated about 4 months ago (not an option to update due to the
risk of breaking something else - the devil you know...)

I've started a project, guess you might call it a smpp proxy server of
sorts, replacing kannel completely. 

Regards,


info.ubichip wrote:
 
 Thanks for your answer again.
 
 which opensmppbox are you using ? I just checked the svn repository, it
 looks some dlr source code is now inside the opensmppbox, perhaps there is
 a good way to make correction inside direclty ?
 
 I'm not sure to understand kannel will be past memory, do you quit the
 telecom world or kannel is going to die ?
 
 Best regards
 
 -Message d'origine-
 De : users-boun...@kannel.org [mailto:users-boun...@kannel.org] De la part
 de Niel
 Envoyé : vendredi 15 juin 2012 13:58
 À : users@kannel.org
 Objet : RE: OpenSMPP+Kannel: DLR: (dst  src) are expected INVETED in the
 deliver_sm (but remains as in submit_sm)
 
 
 Hi,
 
 This is intended for swapping the src and dest for delivery report for
 clients connected using opensmppbox. 
 
 If you are using the same bearerbox for other purposes, such as http smsc
 and/or proxy, the delivery reports src and dest will also be swapped
 around.
 You might need to swap the fields in the get-url or via script.
 
 Personally I use a different bearerbox for each gateway, and a separate
 one for opensmppbox, due to smsbox not being able to deal with any form of
 real load. Each bearerbox has it's own mysql dlr table, and I only apply
 the trigger to the ones using opensmppbox.
 
 Luckily, soon kannel will be past memory; a horror story to tell my kids
 around the campfire :)
 
 Regards,
 
 
 
 info.ubichip wrote:
 
 Thanks a lot, I will try it very soon.
 
 one more question : does it change the way the dlr are coming back to 
 the originator of the request through SMPP ?
 
 -Message d'origine-
 De : users-boun...@kannel.org [mailto:users-boun...@kannel.org] De la 
 part de Niel Envoyé : vendredi 15 juin 2012 13:25 À : users@kannel.org 
 Objet : RE: OpenSMPP+Kannel: DLR: (dst  src) are expected INVETED in 
 the deliver_sm (but remains as in submit_sm)
 
 
 Yes, that is where the trigger should be. My kannel config has been 
 set to use the table kannel.dlr, and columns dest and src.
 
 The MySQL command would look something like this:
 
 delimiter $
 CREATE TRIGGER `kannel`.`dlr_src_dest_swap_trigger`
   BEFORE INSERT ON `kannel`.`dlr`
   FOR EACH ROW
   BEGIN
 DECLARE temp VARCHAR(100);
 SET temp = NEW.src;
 SET NEW.src = NEW.dest;
 SET NEW.dest = temp;
   END
 $
 
 Other useful commands:
 
 SHOW TRIGGERS;
 DROP TRIGGER `dlr_src_dest_swap_trigger`; SHOW CREATE TRIGGER 
 `dlr_src_dest_swap_trigger`;
 
 Regards,
 
 
 
 info.ubichip wrote:
 
 Hello,
 
 is it possible to have your mysql trigger on the DLR table ?
 
 thanks in advance
 
 -Message d'origine-
 De : users-boun...@kannel.org [mailto:users-boun...@kannel.org] De la 
 part de Niel Envoyé : mardi 20 mars 2012 07:54 À : users@kannel.org 
 Objet : Re: OpenSMPP+Kannel: DLR: (dst  src) are expected INVETED in 
 the deliver_sm (but remains as in submit_sm)
 
 
 Hi,
 
 I know this is old, but, this issue still exists in the latest SVN.
 
 My brearbox is set to use mysql storage for DLRs. As workaround I 
 added a mysql trigger on the DLR table before insert that swaps the 
 src and dest values.
 
 Regards,
 
 
 
 Dídac Royo wrote:
 
 Hi Users,
 
 I need your help.
 
  We have a problem in our Kannel + openSMPPbox. The values of
 parameters:
 dst  src are expected INVETED in the deliver_sm, I'm I correct?
 
 
 In the logs *source_addr*  *destination_addr* have the same in both
 *
 submit_sm* and *deliver_sm* operations (when we expect them inverted 
 in the
 deliver_sm)
 
 
This is our log for the submit_sm:
 
 
 *2011-03-01 16:50:00 [634] [6] DEBUG: SMPP[ISMSAD]: Got PDU:
 2011-03-01 16:50:00 [634] [6] DEBUG: SMPP PDU 0x73b700 dump:
 2011-03-01 16:50:00 [634] [6] DEBUG:   type_name: submit_sm
 2011-03-01 16:50:00 [634] [6] DEBUG:   command_id: 4 = 0x0004
 2011-03-01 16:50:00 [634] [6] DEBUG:   command_status: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   sequence_number: 1404 =
 0x057c
 2011-03-01 16:50:00 [634] [6] DEBUG:   service_type: NULL
 2011-03-01 16:50:00 [634] [6] DEBUG:   source_addr_ton: 5 = 0x0005
 2011-03-01 16:50:00 [634] [6] DEBUG:   source_addr_npi: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   source_addr: Info
 2011-03-01 16:50:00 [634] [6] DEBUG:   dest_addr_ton: 1 = 0x0001
 2011-03-01 16:50:00 [634] [6] DEBUG:   dest_addr_npi: 1 = 0x0001
 2011-03-01 16:50:00 [634] [6] DEBUG:   destination_addr: 34695839615
 2011-03-01 16:50:00 [634] [6] DEBUG:   esm_class: 3 = 0x0003
 2011-03-01 16:50:00 [634] [6] DEBUG:   protocol_id: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   priority_flag: 0 = 0x
 2011-03-01 16:50:00 [634] [6] DEBUG:   schedule_delivery_time: NULL
 2011-03-01 16:50:00 [634] [6] DEBUG

Re: OpenSMPP+Kannel: DLR: (dst src) are expected INVETED in the deliver_sm (but remains as in submit_sm)

[Nikos Balkanas]

Interesting...I am surprised this hasn't come up before. I can see a 
possible reason for doing things this way, i.e. to match dlrs with original 
submission in access long and dlr_url, but it is not necessary to do so, and 
infact it is an error. This doesn't matter as long as you don't have an 
smppbox in line, but it also means that all traffic through smppbox has this 
reversion, which would lead to mismatched dlrs upstream...


Smsbox will need to have this reversion fixed as well...

How come *ever* dlrs got matched upstream through smppbox? Nobody noticed 
before?


BR,
Nikos
- Original Message - 
From: Rene Kluwen

To: 'Didac Royo'
Cc: users@kannel.org
Sent: Wednesday, March 02, 2011 4:56 PM
Subject: RE: OpenSMPP+Kannel: DLR: (dst  src) are expected INVETED in the 
deliver_sm (but remains as in submit_sm)



Viewing this log, it seems that your sms gateway is doing things right. 
Somewhere along the line, bearerbox OR opensmppbox reverses the addresses.
Looking at the code, I cannot see which one is doing things wrong. Both seem 
to be doing things allrighty…


Judging from your bearerbox log:

Ψ  2011-03-01 16:50:04 Receive DLR [SMSC:GMS] [SVC:ismsad] [ACT:sit2] 
[BINF:] [FID:110301S00d1a44c] [META:?smpp?dlr_err=000] [from:Info] 
[to:+34695839615] [flags:-1:-1:-1:-1:1] [msg:111:id:110301S00d1a44c sub:000 
dlvrd:000 submit date:1103011650 done date:1103011650 stat:DELIVRD err:000 
text:] [udh:0:]


It seems that smsc smpp is doing things wrong. On line 1487 and line 1545 of 
smsc_smpp.c, where the function handle_dlr() is called, this function 
replaces source_addr with destination_address.
Or maybe otherwise: dlr_find is called and returns the msg structure with 
the original source_addr and dest_addr still in place.
Maybe somebody with some more knowledge of the smpp driver can shed a light 
on this?


== Rene


From: Dνdac Royo [mailto:gdi...@gmail.com]
Sent: Wednesday, 02 March, 2011 12:35
To: Rene Kluwen
Cc: users@kannel.org
Subject: Re: OpenSMPP+Kannel: DLR: (dst  src) are expected INVETED in the 
deliver_sm (but remains as in submit_sm)


Hi Rene,

I think this is the log you are looking for. Can you see what is happening 
from this log snipped? thanks


2011-03-01 16:50:00 [608] [7] DEBUG: SMPP[PROVIDER]: Sending PDU:
2011-03-01 16:50:00 [608] [7] DEBUG: SMPP PDU 0x797cf0 dump:
2011-03-01 16:50:00 [608] [7] DEBUG:   type_name: submit_sm
2011-03-01 16:50:00 [608] [7] DEBUG:   command_id: 4 = 0x0004
2011-03-01 16:50:00 [608] [7] DEBUG:   command_status: 0 = 0x
2011-03-01 16:50:00 [608] [7] DEBUG:   sequence_number: 12 = 0x000c
2011-03-01 16:50:00 [608] [7] DEBUG:   service_type: NULL
2011-03-01 16:50:00 [608] [7] DEBUG:   source_addr_ton: 5 = 0x0005
2011-03-01 16:50:00 [608] [7] DEBUG:   source_addr_npi: 0 = 0x
2011-03-01 16:50:00 [608] [7] DEBUG:   source_addr: Info
2011-03-01 16:50:00 [608] [7] DEBUG:   dest_addr_ton: 1 = 0x0001
2011-03-01 16:50:00 [608] [7] DEBUG:   dest_addr_npi: 0 = 0x
2011-03-01 16:50:00 [608] [7] DEBUG:   destination_addr: 34695839615
2011-03-01 16:50:00 [608] [7] DEBUG:   esm_class: 3 = 0x0003
2011-03-01 16:50:00 [608] [7] DEBUG:   protocol_id: 0 = 0x
2011-03-01 16:50:00 [608] [7] DEBUG:   priority_flag: 0 = 0x
2011-03-01 16:50:00 [608] [7] DEBUG:   schedule_delivery_time: NULL
2011-03-01 16:50:00 [608] [7] DEBUG:   validity_period: NULL
2011-03-01 16:50:00 [608] [7] DEBUG:   registered_delivery: 1 = 0x0001
2011-03-01 16:50:00 [608] [7] DEBUG:   replace_if_present_flag: 0 = 
0x

2011-03-01 16:50:00 [608] [7] DEBUG:   data_coding: 0 = 0x
2011-03-01 16:50:00 [608] [7] DEBUG:   sm_default_msg_id: 0 = 0x
2011-03-01 16:50:00 [608] [7] DEBUG:   sm_length: 10 = 0x000a
2011-03-01 16:50:00 [608] [7] DEBUG:   short_message: test 16:48
2011-03-01 16:50:00 [608] [7] DEBUG: SMPP PDU dump ends.
2011-03-01 16:50:00 [608] [7] DEBUG: SMPP[PROVIDER]: throughput (1.00,50.00)
2011-03-01 16:50:00 [608] [7] DEBUG: SMPP[PROVIDER]: throughput (1.00,50.00)
2011-03-01 16:50:00 [608] [7] DEBUG: SMPP[PROVIDER]: Got PDU:
2011-03-01 16:50:00 [608] [7] DEBUG: SMPP PDU 0x797cf0 dump:
2011-03-01 16:50:00 [608] [7] DEBUG:   type_name: submit_sm_resp
2011-03-01 16:50:00 [608] [7] DEBUG:   command_id: 2147483652 = 0x8004
2011-03-01 16:50:00 [608] [7] DEBUG:   command_status: 0 = 0x
2011-03-01 16:50:00 [608] [7] DEBUG:   sequence_number: 12 = 0x000c
2011-03-01 16:50:00 [608] [7] DEBUG:   message_id: 110301S00d1a44c
2011-03-01 16:50:00 [608] [7] DEBUG: SMPP PDU dump ends.


2011-03-01 16:50:04 [608] [7] DEBUG: SMPP[PROVIDER]: Got PDU:
2011-03-01 16:50:04 [608] [7] DEBUG: SMPP PDU 0x797500 dump:
2011-03-01 16:50:04 [608] [7] DEBUG:   type_name: deliver_sm
2011-03-01 16:50:04 [608] [7] DEBUG:   command_id: 5 = 0x0005
2011-03-01 16:50:04 [608] [7] DEBUG:   command_status: 0 = 0x
2011-03-01 16:50:04 [608] [7] DEBUG:   sequence_number: 21274986 = 
0x0144a16a

2011-03-01 16:50:04

RE: OpenSMPP+Kannel: DLR: (dst src) are expected INVETED in the deliver_sm (but remains as in submit_sm)

[Rene Kluwen]

Looks like the downstream SMSC (GMS in your case) turns things around.

Could you post some bearerbox logs of the offending message with log-level =
0?

 

== Rene

 

From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf
Of Dídac Royo
Sent: Tuesday, 01 March, 2011 18:47
To: users@kannel.org
Subject: OpenSMPP+Kannel: DLR: (dst  src) are expected INVETED in the
deliver_sm (but remains as in submit_sm)

 

Hi Users,

I need your help. 

We have a problem in our Kannel + openSMPPbox. The values of parameters: dst
 src are expected INVETED in the deliver_sm, I'm I correct? 



In the logs source_addr  destination_addr have the same in both submit_sm
and deliver_sm operations (when we expect them inverted in the deliver_sm)

 

This is our log for the submit_sm:

 

2011-03-01 16:50:00 [634] [6] DEBUG: SMPP[ISMSAD]: Got PDU:
2011-03-01 16:50:00 [634] [6] DEBUG: SMPP PDU 0x73b700 dump:
2011-03-01 16:50:00 [634] [6] DEBUG:   type_name: submit_sm
2011-03-01 16:50:00 [634] [6] DEBUG:   command_id: 4 = 0x0004
2011-03-01 16:50:00 [634] [6] DEBUG:   command_status: 0 = 0x
2011-03-01 16:50:00 [634] [6] DEBUG:   sequence_number: 1404 = 0x057c
2011-03-01 16:50:00 [634] [6] DEBUG:   service_type: NULL
2011-03-01 16:50:00 [634] [6] DEBUG:   source_addr_ton: 5 = 0x0005
2011-03-01 16:50:00 [634] [6] DEBUG:   source_addr_npi: 0 = 0x
2011-03-01 16:50:00 [634] [6] DEBUG:   source_addr: Info
2011-03-01 16:50:00 [634] [6] DEBUG:   dest_addr_ton: 1 = 0x0001
2011-03-01 16:50:00 [634] [6] DEBUG:   dest_addr_npi: 1 = 0x0001
2011-03-01 16:50:00 [634] [6] DEBUG:   destination_addr: 34695839615
2011-03-01 16:50:00 [634] [6] DEBUG:   esm_class: 3 = 0x0003
2011-03-01 16:50:00 [634] [6] DEBUG:   protocol_id: 0 = 0x
2011-03-01 16:50:00 [634] [6] DEBUG:   priority_flag: 0 = 0x
2011-03-01 16:50:00 [634] [6] DEBUG:   schedule_delivery_time: NULL
2011-03-01 16:50:00 [634] [6] DEBUG:   validity_period: NULL
2011-03-01 16:50:00 [634] [6] DEBUG:   registered_delivery: 1 = 0x0001
2011-03-01 16:50:00 [634] [6] DEBUG:   replace_if_present_flag: 0 =
0x
2011-03-01 16:50:00 [634] [6] DEBUG:   data_coding: 0 = 0x
2011-03-01 16:50:00 [634] [6] DEBUG:   sm_default_msg_id: 0 = 0x
2011-03-01 16:50:00 [634] [6] DEBUG:   sm_length: 10 = 0x000a
2011-03-01 16:50:00 [634] [6] DEBUG:   short_message: test 16:48
2011-03-01 16:50:00 [634] [6] DEBUG: SMPP PDU dump ends.



and this is our log for the deiver_sm:

 

2011-03-01 16:50:04 [634] [5] DEBUG: SMPP[ISMSAD]: Sending PDU:
2011-03-01 16:50:04 [634] [5] DEBUG: SMPP PDU 0x73fd30 dump:
2011-03-01 16:50:04 [634] [5] DEBUG:   type_name: deliver_sm
2011-03-01 16:50:04 [634] [5] DEBUG:   command_id: 5 = 0x0005
2011-03-01 16:50:04 [634] [5] DEBUG:   command_status: 0 = 0x
2011-03-01 16:50:04 [634] [5] DEBUG:   sequence_number: 1 = 0x0001
2011-03-01 16:50:04 [634] [5] DEBUG:   service_type: NULL
2011-03-01 16:50:04 [634] [5] DEBUG:   source_addr_ton: 2 = 0x0002
2011-03-01 16:50:04 [634] [5] DEBUG:   source_addr_npi: 1 = 0x0001
2011-03-01 16:50:04 [634] [5] DEBUG:   source_addr: Info
2011-03-01 16:50:04 [634] [5] DEBUG:   dest_addr_ton: 1 = 0x0001
2011-03-01 16:50:04 [634] [5] DEBUG:   dest_addr_npi: 1 = 0x0001
2011-03-01 16:50:04 [634] [5] DEBUG:   destination_addr: 34695839615
2011-03-01 16:50:04 [634] [5] DEBUG:   esm_class: 4 = 0x0004
2011-03-01 16:50:04 [634] [5] DEBUG:   protocol_id: 0 = 0x
2011-03-01 16:50:04 [634] [5] DEBUG:   priority_flag: 0 = 0x
2011-03-01 16:50:04 [634] [5] DEBUG:   schedule_delivery_time: NULL
2011-03-01 16:50:04 [634] [5] DEBUG:   validity_period: NULL
2011-03-01 16:50:04 [634] [5] DEBUG:   registered_delivery: 0 = 0x
2011-03-01 16:50:04 [634] [5] DEBUG:   replace_if_present_flag: 0 =
0x
2011-03-01 16:50:04 [634] [5] DEBUG:   data_coding: 0 = 0x
2011-03-01 16:50:04 [634] [5] DEBUG:   sm_default_msg_id: 0 = 0x
2011-03-01 16:50:04 [634] [5] DEBUG:   sm_length: 0 = 0x
2011-03-01 16:50:04 [634] [5] DEBUG:   short_message:
2011-03-01 16:50:04 [634] [5] DEBUG:Octet string at 0x73a350:
2011-03-01 16:50:04 [634] [5] DEBUG:  len:  112
2011-03-01 16:50:04 [634] [5] DEBUG:  size: 1024
2011-03-01 16:50:04 [634] [5] DEBUG:  immutable: 0
2011-03-01 16:50:04 [634] [5] DEBUG:  data: 69 64 3a 33 30 37 32 30 66
30 36 20 73 75 62 3a   id:30720f06 sub:
2011-03-01 16:50:04 [634] [5] DEBUG:  data: 30 30 31 20 64 6c 76 72 64
3a 30 30 31 20 73 75   001 dlvrd:001 su
2011-03-01 16:50:04 [634] [5] DEBUG:  data: 62 6d 69 74 20 64 61 74 65
3a 31 31 30 33 30 31   bmit date:110301
2011-03-01 16:50:04 [634] [5] DEBUG:  data: 31 36 35 30 20 64 6f 6e 65
20 64 61 74 65 3a 31   1650 done date:1
2011-03-01 16:50:04 [634] [5] DEBUG:  data: 31 30 33 30 31 31 36 35 30
20 73 74 61 74 3a 44   103011650 stat:D
2011-03-01 16:50:04 [634] [5] DEBUG:  data: 45 4c 49 56 52 44 20 65 72
72 3a 30 30 30 

Re: opensmpp, sqldlr, bearorbox multiple dlrs

[Nikos Balkanas]

I am no expert with sqlbox, so I can't tell you what it does or not. You can 
try connecting smppbox directly to bb to see if it helps. smppbox used to 
have that bug early on, but it fixed it and since then it will rejoin 
concatenated messages. This should be independent of size, unless there is 
another bug there.


BR,
Nikos
- Original Message - 
From: James E

To: Nikos Balkanas ; users@kannel.org
Sent: Wednesday, December 08, 2010 9:17 AM
Subject: Re: opensmpp, sqldlr, bearorbox multiple dlrs


Hi Nikos,

I am using a C# SMPP 3.4 client library, which i am using in my application 
to connect to OpenSMPPBox.


I will see if the client library is splitting it up.

Can OpenSMPPBox handle single long (400 character) messages as standard? I 
was under the impression that it does the following:


SMPP Client splits the message up  - SMPPBox - SQLBox - BB

Note: In SQLBox there is only a single row in the SENT_SMS table, but with 3 
message ids in the DLR_URL  column.


Regards,
James


2010/12/8 Nikos Balkanas nbalka...@gmail.com

Hi,

In such a case, you should not send in a concatenated message to bb, since 
it perceives it as 3 separate SMS. Instead you should rejoin it and let bb 
worry about splitting it. Opensmppbox will rejoing long SMS before sending 
them to bb. How doe you send them concatenated?



BR,
Nikos
- Original Message - From: James E

To: Nikos Balkanas ; users@kannel.org
Sent: Wednesday, December 08, 2010 4:59 AM
Subject: Re: opensmpp, sqldlr, bearorbox multiple dlrs



Hi Nikos,

We are getting the 3 delivery_sm DLRs back to the OpenSMPPBox, and in SQLBox 
there is 3 message ids in the DLR URL column.


Regards,
James


2010/12/8 Nikos Balkanas nbalka...@gmail.com

Hi,

I imagine that by deliver_sm you mean you are getting 3 dlrs back from SMSc. 
If that is the case, it is not normal, since bb will disable dlrs to all 
parts except the first.


BR,
Nikos
- Original Message - From: James E
To: users@kannel.org
Sent: Tuesday, December 07, 2010 3:59 PM
Subject: opensmpp, sqldlr, bearorbox multiple dlrs



Hi,

My setup is:

OpenSMPPBox - SQLBox - BearorBox

I send an concatenated sms (3 msgs long) and get 3 Delivery_SM messages back 
(Each with segment numbers)


Is it normal to receive 3 Delivery_SM, can it not just send 1 Delivery_SM 
once all segments have been received?


Regards,
James 

Re: opensmpp, sqldlr, bearorbox multiple dlrs

[Nikos Balkanas]

Your problem is probably due to your client C# SMPP library and your 
application. I suspect it doesn't set the concatenation correctly in the UDH 
headers and are not recognized as parts of the same SMS from smppbox. You 
can verify by checking smppbox logs and sqlbox logs (and DB). If in sqlbox 
SMS arrives as a single SMS, then it is correct and there is a problem with 
bb. Else your problem is upstream.


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

To: James E jam...@gmail.com; us...@vm1.kannel.org
Sent: Wednesday, December 08, 2010 10:12 AM
Subject: Re: opensmpp, sqldlr, bearorbox multiple dlrs


I am no expert with sqlbox, so I can't tell you what it does or not. You 
can try connecting smppbox directly to bb to see if it helps. smppbox used 
to have that bug early on, but it fixed it and since then it will rejoin 
concatenated messages. This should be independent of size, unless there is 
another bug there.


BR,
Nikos
- Original Message - 
From: James E

To: Nikos Balkanas ; users@kannel.org
Sent: Wednesday, December 08, 2010 9:17 AM
Subject: Re: opensmpp, sqldlr, bearorbox multiple dlrs


Hi Nikos,

I am using a C# SMPP 3.4 client library, which i am using in my 
application to connect to OpenSMPPBox.


I will see if the client library is splitting it up.

Can OpenSMPPBox handle single long (400 character) messages as standard? I 
was under the impression that it does the following:


SMPP Client splits the message up  - SMPPBox - SQLBox - BB

Note: In SQLBox there is only a single row in the SENT_SMS table, but with 
3 message ids in the DLR_URL  column.


Regards,
James


2010/12/8 Nikos Balkanas nbalka...@gmail.com

Hi,

In such a case, you should not send in a concatenated message to bb, since 
it perceives it as 3 separate SMS. Instead you should rejoin it and let bb 
worry about splitting it. Opensmppbox will rejoing long SMS before sending 
them to bb. How doe you send them concatenated?



BR,
Nikos
- Original Message - From: James E

To: Nikos Balkanas ; users@kannel.org
Sent: Wednesday, December 08, 2010 4:59 AM
Subject: Re: opensmpp, sqldlr, bearorbox multiple dlrs



Hi Nikos,

We are getting the 3 delivery_sm DLRs back to the OpenSMPPBox, and in 
SQLBox there is 3 message ids in the DLR URL column.


Regards,
James


2010/12/8 Nikos Balkanas nbalka...@gmail.com

Hi,

I imagine that by deliver_sm you mean you are getting 3 dlrs back from 
SMSc. If that is the case, it is not normal, since bb will disable dlrs to 
all parts except the first.


BR,
Nikos
- Original Message - From: James E
To: users@kannel.org
Sent: Tuesday, December 07, 2010 3:59 PM
Subject: opensmpp, sqldlr, bearorbox multiple dlrs



Hi,

My setup is:

OpenSMPPBox - SQLBox - BearorBox

I send an concatenated sms (3 msgs long) and get 3 Delivery_SM messages 
back (Each with segment numbers)


Is it normal to receive 3 Delivery_SM, can it not just send 1 Delivery_SM 
once all segments have been received?


Regards,
James

Re: opensmpp, sqldlr, bearorbox multiple dlrs

[James E]

Thanks Nikos for making it clearer.. I will dig a little deeper and get to
the bottom of it.

Regards,
J

2010/12/8 Nikos Balkanas nbalka...@gmail.com

 Your problem is probably due to your client C# SMPP library and your
 application. I suspect it doesn't set the concatenation correctly in the UDH
 headers and are not recognized as parts of the same SMS from smppbox. You
 can verify by checking smppbox logs and sqlbox logs (and DB). If in sqlbox
 SMS arrives as a single SMS, then it is correct and there is a problem with
 bb. Else your problem is upstream.

 BR,
 Nikos
 - Original Message - From: Nikos Balkanas nbalka...@gmail.com
 To: James E jam...@gmail.com; us...@vm1.kannel.org
 Sent: Wednesday, December 08, 2010 10:12 AM

 Subject: Re: opensmpp, sqldlr, bearorbox multiple dlrs


  I am no expert with sqlbox, so I can't tell you what it does or not. You
 can try connecting smppbox directly to bb to see if it helps. smppbox used
 to have that bug early on, but it fixed it and since then it will rejoin
 concatenated messages. This should be independent of size, unless there is
 another bug there.

 BR,
 Nikos
 - Original Message - From: James E
 To: Nikos Balkanas ; users@kannel.org
 Sent: Wednesday, December 08, 2010 9:17 AM
 Subject: Re: opensmpp, sqldlr, bearorbox multiple dlrs


 Hi Nikos,

 I am using a C# SMPP 3.4 client library, which i am using in my
 application to connect to OpenSMPPBox.

 I will see if the client library is splitting it up.

 Can OpenSMPPBox handle single long (400 character) messages as standard? I
 was under the impression that it does the following:

 SMPP Client splits the message up  - SMPPBox - SQLBox - BB

 Note: In SQLBox there is only a single row in the SENT_SMS table, but with
 3 message ids in the DLR_URL  column.

 Regards,
 James


 2010/12/8 Nikos Balkanas nbalka...@gmail.com

 Hi,

 In such a case, you should not send in a concatenated message to bb, since
 it perceives it as 3 separate SMS. Instead you should rejoin it and let bb
 worry about splitting it. Opensmppbox will rejoing long SMS before sending
 them to bb. How doe you send them concatenated?


 BR,
 Nikos
 - Original Message - From: James E

 To: Nikos Balkanas ; users@kannel.org
 Sent: Wednesday, December 08, 2010 4:59 AM
 Subject: Re: opensmpp, sqldlr, bearorbox multiple dlrs



 Hi Nikos,

 We are getting the 3 delivery_sm DLRs back to the OpenSMPPBox, and in
 SQLBox there is 3 message ids in the DLR URL column.

 Regards,
 James


 2010/12/8 Nikos Balkanas nbalka...@gmail.com

 Hi,

 I imagine that by deliver_sm you mean you are getting 3 dlrs back from
 SMSc. If that is the case, it is not normal, since bb will disable dlrs to
 all parts except the first.

 BR,
 Nikos
 - Original Message - From: James E
 To: users@kannel.org
 Sent: Tuesday, December 07, 2010 3:59 PM
 Subject: opensmpp, sqldlr, bearorbox multiple dlrs



 Hi,

 My setup is:

 OpenSMPPBox - SQLBox - BearorBox

 I send an concatenated sms (3 msgs long) and get 3 Delivery_SM messages
 back (Each with segment numbers)

 Is it normal to receive 3 Delivery_SM, can it not just send 1 Delivery_SM
 once all segments have been received?

 Regards,
 James

Re: opensmpp, sqldlr, bearorbox multiple dlrs

[Nikos Balkanas]

You don't need to go very deep. Just implement the following scheme:

smsbox-bb1 -opensmppbox-sqlbox-bb2-smsc

Try the same SMS from smsbox. Put bb1 and smppbox logs in debug mode. You 
should get 1 dlr/SMS. Then try from your application. Compare bb1  smppbox 
PDUs to see what's wrong.


BR,
Nikos
- Original Message - 
From: James E

To: Nikos Balkanas ; users@kannel.org
Sent: Wednesday, December 08, 2010 1:11 PM
Subject: Re: opensmpp, sqldlr, bearorbox multiple dlrs


Thanks Nikos for making it clearer.. I will dig a little deeper and get to 
the bottom of it.


Regards,
J


2010/12/8 Nikos Balkanas nbalka...@gmail.com

Your problem is probably due to your client C# SMPP library and your 
application. I suspect it doesn't set the concatenation correctly in the UDH 
headers and are not recognized as parts of the same SMS from smppbox. You 
can verify by checking smppbox logs and sqlbox logs (and DB). If in sqlbox 
SMS arrives as a single SMS, then it is correct and there is a problem with 
bb. Else your problem is upstream.


BR,
Nikos
- Original Message - From: Nikos Balkanas nbalka...@gmail.com
To: James E jam...@gmail.com; us...@vm1.kannel.org
Sent: Wednesday, December 08, 2010 10:12 AM

Subject: Re: opensmpp, sqldlr, bearorbox multiple dlrs



I am no expert with sqlbox, so I can't tell you what it does or not. You can 
try connecting smppbox directly to bb to see if it helps. smppbox used to 
have that bug early on, but it fixed it and since then it will rejoin 
concatenated messages. This should be independent of size, unless there is 
another bug there.


BR,
Nikos
- Original Message - From: James E
To: Nikos Balkanas ; users@kannel.org
Sent: Wednesday, December 08, 2010 9:17 AM
Subject: Re: opensmpp, sqldlr, bearorbox multiple dlrs


Hi Nikos,

I am using a C# SMPP 3.4 client library, which i am using in my application 
to connect to OpenSMPPBox.


I will see if the client library is splitting it up.

Can OpenSMPPBox handle single long (400 character) messages as standard? I 
was under the impression that it does the following:


SMPP Client splits the message up  - SMPPBox - SQLBox - BB

Note: In SQLBox there is only a single row in the SENT_SMS table, but with 3 
message ids in the DLR_URL  column.


Regards,
James


2010/12/8 Nikos Balkanas nbalka...@gmail.com

Hi,

In such a case, you should not send in a concatenated message to bb, since 
it perceives it as 3 separate SMS. Instead you should rejoin it and let bb 
worry about splitting it. Opensmppbox will rejoing long SMS before sending 
them to bb. How doe you send them concatenated?



BR,
Nikos
- Original Message - From: James E

To: Nikos Balkanas ; users@kannel.org
Sent: Wednesday, December 08, 2010 4:59 AM
Subject: Re: opensmpp, sqldlr, bearorbox multiple dlrs



Hi Nikos,

We are getting the 3 delivery_sm DLRs back to the OpenSMPPBox, and in SQLBox 
there is 3 message ids in the DLR URL column.


Regards,
James


2010/12/8 Nikos Balkanas nbalka...@gmail.com

Hi,

I imagine that by deliver_sm you mean you are getting 3 dlrs back from SMSc. 
If that is the case, it is not normal, since bb will disable dlrs to all 
parts except the first.


BR,
Nikos
- Original Message - From: James E
To: users@kannel.org
Sent: Tuesday, December 07, 2010 3:59 PM
Subject: opensmpp, sqldlr, bearorbox multiple dlrs



Hi,

My setup is:

OpenSMPPBox - SQLBox - BearorBox

I send an concatenated sms (3 msgs long) and get 3 Delivery_SM messages back 
(Each with segment numbers)


Is it normal to receive 3 Delivery_SM, can it not just send 1 Delivery_SM 
once all segments have been received?


Regards,
James 

Re: opensmpp, sqldlr, bearorbox multiple dlrs

[Nikos Balkanas]

Hi,

I imagine that by deliver_sm you mean you are getting 3 dlrs back from SMSc. 
If that is the case, it is not normal, since bb will disable dlrs to all 
parts except the first.


BR,
Nikos
- Original Message - 
From: James E

To: users@kannel.org
Sent: Tuesday, December 07, 2010 3:59 PM
Subject: opensmpp, sqldlr, bearorbox multiple dlrs


Hi,

My setup is:

OpenSMPPBox - SQLBox - BearorBox

I send an concatenated sms (3 msgs long) and get 3 Delivery_SM messages back 
(Each with segment numbers)


Is it normal to receive 3 Delivery_SM, can it not just send 1 Delivery_SM 
once all segments have been received?


Regards,
James 

Re: opensmpp, sqldlr, bearorbox multiple dlrs

[James E]

Hi Nikos,

We are getting the 3 delivery_sm DLRs back to the OpenSMPPBox, and in SQLBox
there is 3 message ids in the DLR URL column.

Regards,
James

2010/12/8 Nikos Balkanas nbalka...@gmail.com

 Hi,

 I imagine that by deliver_sm you mean you are getting 3 dlrs back from
 SMSc. If that is the case, it is not normal, since bb will disable dlrs to
 all parts except the first.

 BR,
 Nikos
 - Original Message - From: James E
 To: users@kannel.org
 Sent: Tuesday, December 07, 2010 3:59 PM
 Subject: opensmpp, sqldlr, bearorbox multiple dlrs



 Hi,

 My setup is:

 OpenSMPPBox - SQLBox - BearorBox

 I send an concatenated sms (3 msgs long) and get 3 Delivery_SM messages
 back (Each with segment numbers)

 Is it normal to receive 3 Delivery_SM, can it not just send 1 Delivery_SM
 once all segments have been received?

 Regards,
 James

Re: opensmpp, sqldlr, bearorbox multiple dlrs

[Nikos Balkanas]

Hi,

In such a case, you should not send in a concatenated message to bb, since 
it perceives it as 3 separate SMS. Instead you should rejoin it and let bb 
worry about splitting it. Opensmppbox will rejoing long SMS before sending 
them to bb. How doe you send them concatenated?


BR,
Nikos
- Original Message - 
From: James E

To: Nikos Balkanas ; users@kannel.org
Sent: Wednesday, December 08, 2010 4:59 AM
Subject: Re: opensmpp, sqldlr, bearorbox multiple dlrs


Hi Nikos,

We are getting the 3 delivery_sm DLRs back to the OpenSMPPBox, and in SQLBox 
there is 3 message ids in the DLR URL column.


Regards,
James


2010/12/8 Nikos Balkanas nbalka...@gmail.com

Hi,

I imagine that by deliver_sm you mean you are getting 3 dlrs back from SMSc. 
If that is the case, it is not normal, since bb will disable dlrs to all 
parts except the first.


BR,
Nikos
- Original Message - From: James E
To: users@kannel.org
Sent: Tuesday, December 07, 2010 3:59 PM
Subject: opensmpp, sqldlr, bearorbox multiple dlrs



Hi,

My setup is:

OpenSMPPBox - SQLBox - BearorBox

I send an concatenated sms (3 msgs long) and get 3 Delivery_SM messages back 
(Each with segment numbers)


Is it normal to receive 3 Delivery_SM, can it not just send 1 Delivery_SM 
once all segments have been received?


Regards,
James 

Re: opensmpp, sqldlr, bearorbox multiple dlrs

[James E]

Hi Nikos,

I am using a C# SMPP 3.4 client library, which i am using in my application
to connect to OpenSMPPBox.

I will see if the client library is splitting it up.

Can OpenSMPPBox handle single long (400 character) messages as standard? I
was under the impression that it does the following:

SMPP Client splits the message up  - SMPPBox - SQLBox - BB

Note: In SQLBox there is only a single row in the SENT_SMS table, but with 3
message ids in the DLR_URL  column.

Regards,
James

2010/12/8 Nikos Balkanas nbalka...@gmail.com

 Hi,

 In such a case, you should not send in a concatenated message to bb, since
 it perceives it as 3 separate SMS. Instead you should rejoin it and let bb
 worry about splitting it. Opensmppbox will rejoing long SMS before sending
 them to bb. How doe you send them concatenated?


 BR,
 Nikos
 - Original Message - From: James E
 To: Nikos Balkanas ; users@kannel.org
 Sent: Wednesday, December 08, 2010 4:59 AM
 Subject: Re: opensmpp, sqldlr, bearorbox multiple dlrs



 Hi Nikos,

 We are getting the 3 delivery_sm DLRs back to the OpenSMPPBox, and in
 SQLBox there is 3 message ids in the DLR URL column.

 Regards,
 James


 2010/12/8 Nikos Balkanas nbalka...@gmail.com

 Hi,

 I imagine that by deliver_sm you mean you are getting 3 dlrs back from
 SMSc. If that is the case, it is not normal, since bb will disable dlrs to
 all parts except the first.

 BR,
 Nikos
 - Original Message - From: James E
 To: users@kannel.org
 Sent: Tuesday, December 07, 2010 3:59 PM
 Subject: opensmpp, sqldlr, bearorbox multiple dlrs



 Hi,

 My setup is:

 OpenSMPPBox - SQLBox - BearorBox

 I send an concatenated sms (3 msgs long) and get 3 Delivery_SM messages
 back (Each with segment numbers)

 Is it normal to receive 3 Delivery_SM, can it not just send 1 Delivery_SM
 once all segments have been received?

 Regards,
 James

Re: OpenSMPP

[James E]

Sorry, I meant Open SMPPBox

On Mon, Nov 29, 2010 at 9:53 PM, James E jam...@gmail.com wrote:
 Hi,

 Is it possible to route Opensmpp to a url?

 Something like Opensmpp - bearerbox - geturl

 Regards,
 J

Re: OpenSMPP

[Nikos Balkanas]

Hi,

Yes, but it is a bearerbox question. You can route MT traffic to the HTTP 
smsc.


BR,
Nikos
- Original Message - 
From: James E jam...@gmail.com

To: users@kannel.org
Sent: Monday, November 29, 2010 4:58 PM
Subject: Re: OpenSMPP



Sorry, I meant Open SMPPBox

On Mon, Nov 29, 2010 at 9:53 PM, James E jam...@gmail.com wrote:

Hi,

Is it possible to route Opensmpp to a url?

Something like Opensmpp - bearerbox - geturl

Regards,
J