Re: How can I see the TCP packages of an incoming SMS

[DHC Admin]

You can sniff USB with wireshark. But you will need an specify scenario:

https://wiki.wireshark.org/CaptureSetup/USB

On Wed, Sep 21, 2016 at 10:37 AM, Alvaro Cornejo <cornejo.alv...@gmail.com>
wrote:

> Hi
>
> That is not possible if you use the GSM as a modem since it talks a serial
> protocol (rs232/usb), not ethernet. You might need a serial/usb sniffer.
>
> wireshark/tcpdump does "sniff" TCP packets.
>
> Regards
>
> Alvaro
>
> |---
> --|
> Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier
> celular y Nextel
> en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS
> y GPRS online
>   Visitenos en www.perusms.com
>
> On Tue, Sep 20, 2016 at 6:56 PM, DHC Admin <dhcad...@gmail.com> wrote:
>
>> If you know a tcpdump would do, why don't you use it? On a linux machine
>> you would do: tcpdump -w FILENAME.pcap -s 0 host XXX.XXX.XXX.XXX (for
>> example) then use wireshark software to read the resulting file from the
>> capture.
>>
>> Once on wireshark you can search for SMPP params, like phone number.
>>
>> hope this helps.
>>
>> On Tue, Sep 20, 2016 at 5:38 PM, Manuel García Cabrera <
>> mcabr...@contentamobile.com> wrote:
>>
>>> I have a SIM inside a GSM modem (Portech mv-374), and I need to see how
>>> an incoming SMS packet is formed. A tcpdump would do, but I don't know how
>>> to obtain that. Can someone point me in the right direction?
>>>
>>>
>>>
>>
>

Re: what to do with store.bak file after Kannel crash?

[DHC Admin]

I had a similar problem. I checked that there were no queued messages,
stopped kannel, removed all the store files, started it again and had no
problems since, nor any kind of error, files were just recreated on start
(but small size)



On Thu, Sep 8, 2016 at 5:24 PM, Jeff Thorn 
wrote:

> Hello Group,
>
> I just experienced a very rare crash of Kannel. We are using the following
> settings for store type:
>
> store-type = file
> store-location = /var/log/kannel/msg-store.db
>
> After restarting everything, I noticed a very large (3 GB)
> msg-store.db.bak file.
>
> Kannel took several minutes to start back up after this crash during this
> time the CPU was nearly maxed out. I assume during this time, Kannel was
> processing saved messages from the store file. Is this correct?
>
> What exactly is in the contents of the msg-store.db.bak file? Did these
> messages get handled by kannel or did the database simply get saved for
> backup purposes. Do I need to do anything specifically to handle all these
> messages in the .bak file? Or is it safe to delete now that kannel is back
> up?
>
> Thanks,
> Jeff
>
>

Re: Load balancing MT with preferred SMSC

[DHC Admin]

Of course you have removed the # form those lines, right? Other than that,
I cannot tell why it's not working for you.

On Sat, Sep 17, 2016 at 8:48 AM, Davor Spasoski 
wrote:

> Hi,
>
>
>
> I’m trying to  use opensmppbox and kannel to act as SMPP proxy. The SMSC
> operator doesn’t allow direct connections and it has two SMSCs, one of
> which is preferred and the other handles traffic if only the preferred
> fails. *But, both are always active*, i.e. bearerbox is normally bound to
> both.
>
> I have a dozen of ESMEs that should connect to opensmppbox with a single
> bind and then bearerbox should make two connections to smsc1 and smsc2 for
> each and every esme. To simplify, the flow with one  ESME would look like
> this:
>
>
>
> ___   _
>
> ESME1 --> | Opensmppbox   | --> | Bearerbox |---> |SMSC1|
>
> |   ||   |  -
>
> |___||   |---> |SMSC2|
>
> |___|  -
>
>
>
> For each new ESME there would be a new set of binds from bearerbox to
> SMSCs and the system-id of the esme should distinguish the rotue in
> bearerbox.
>
> Hence, use-systemid-as-smsboxid is set to true in opensmppbox.conf
>
>
>
> At the moment, I have two fake SMSCs with same SMSC-id and they share the
> load as expected. However, no matter what I try with directives like
> preferred-smsc-id and allowed-smsc-id, I can’t make a confgiration to make
> bearerbox route *all MT SMS to SMSC1 only and route to SMSC2 if only
> SMSC1* is down.
>
>
>
> This is part of my bearerbox configuration:
>
>
>
> group = smsc
>
> smsc = fake
>
> port = 12000
>
> smsc-id = vasgw
>
> #allowed-smsc-id = "vasgw"
>
> #preferred-smsc-id = "vasgw"
>
>
>
> group = smsc
>
> smsc = fake
>
> port = 12001
>
> smsc-id = vasgw
>
> #allowed-smsc-id = "vasgw"
>
>
>
> Also, bearebox should accept MO SMS from any of the SMSC1 and SMSC2
>
>
>
> Any ideas how to achieve this?
>
>
>
> BR,
>
> *Davor*
>
>
>
> --
>
> Disclaimer: one.Vip DOO Skopje
> This e-mail (including any attachments) is confidential and may be
> protected by legal privilege. If you are not the intended recipient, you
> should not copy it, re-transmit it, use it or disclose its contents, but
> should return it to the sender immediately and delete your copy from your
> system. Any unauthorized use or dissemination of this message in whole or
> in part is strictly prohibited. Please note that e-mails are susceptible to
> change. one.Vip DOO Skopje shall not be liable for the improper or
> incomplete transmission of the information contained in this communication
> nor for any delay in its receipt or damage to your system.
> Please, do not print this e-mail unless it is necessary! Think about
> saving the environment!
>
> Напомена: оне.Вип ДОО Скопје
> Оваа електронска порака (вклучувајќи ги и прилозите) е доверлива и може да
> биде заштитена со правни привилегии. Доколку не сте лицето на кое таа му е
> наменета пораката, не треба да ја копирате, дистрибуирате или да ја
> откривате нејзината содржина, туку веднаш да ја препратите до испраќачот и
> да ја избришете оригиналната порака и сите нејзини копии од Вашиот
> компјутерски систем. Секое неовластено користење на оваа порака во целост
> или делови од истата е строго забрането. Ве молиме да забележите дека
> електронските пораки се подложни на промени. оне.Вип ДОО Скопје не презема
> одговорност за несоодветно или нецелосно пренесување на информациите
> содржани во оваа комуникација, ниту пак за било какво задоцнување на
> приемот или оштетувања на вашиот систем.
> Ве молиме не ја печатете оваа порака освен ако не е неопходно! Зачувајте
> ја природата!
>

Re: Sending Prioritary SMSs

[DHC Admin]

queue does work as expected, FIFO

you may create a second connection to the same SMSC for priority messages
only, without load balancing between connections.

On Tue, Mar 10, 2015 at 2:34 PM, ha...@aeon.pk  wrote:

> I haven't used fakesmsc. However, try throttling the speed of the
> connection to 1 or 2 SMS/sec.
>
> On Tue, Mar 10, 2015 at 9:55 PM, Manuel García Cabrera <
> mcabr...@contentamobile.com> wrote:
>
>> I'm trying to test it with fakesmsc. Do you know how to simulate a delay
>> in the sending of the message? I'm having a hard time testing it this way
>> because the queue empties way too fast.
>>
>>
>> On 10/03/15 10:35, ha...@aeon.pk wrote:
>>
>> Perhaps I cannot point out the logic of why exactly this happens, since I
>> discovered it only by doing.
>>
>> Also, another way is that if your main bulk is going via SQLBOX, then if
>> you push a message via SMSBOX, it will get higher prio and gets on top of
>> the queue.
>>
>> Plz try it to confirm, since I did it quite long time ago.
>>
>> On Tue, Mar 10, 2015 at 6:28 PM, Manuel García Cabrera <
>> mcabr...@contentamobile.com> wrote:
>>
>>> Really? But wouldn't that mean that it's not actually a queue?
>>>
>>>
>>> On 10/03/15 10:19, ha...@aeon.pk wrote:
>>>
>>> If you insert a new message in the existing queue, it automatically gets
>>> delivered before the queued ones.
>>>
>>> On Tue, Mar 10, 2015 at 6:07 PM, Manuel García Cabrera <
>>> mcabr...@contentamobile.com> wrote:
>>>
 Hi, I'm trying to send prioritary messages when there already are many
 messages queued for sending. Suppose I have on SMSC with a 10.000 message
 queue, and I want the next message I queue to be sent before those 10.000
 messages. Is that possible?


>>>
>>>
>>
>>
>

Re: How can I see the TCP packages of an incoming SMS

[DHC Admin]

If you know a tcpdump would do, why don't you use it? On a linux machine
you would do: tcpdump -w FILENAME.pcap -s 0 host XXX.XXX.XXX.XXX (for
example) then use wireshark software to read the resulting file from the
capture.

Once on wireshark you can search for SMPP params, like phone number.

hope this helps.

On Tue, Sep 20, 2016 at 5:38 PM, Manuel García Cabrera <
mcabr...@contentamobile.com> wrote:

> I have a SIM inside a GSM modem (Portech mv-374), and I need to see how an
> incoming SMS packet is formed. A tcpdump would do, but I don't know how to
> obtain that. Can someone point me in the right direction?
>
>
>

Re: STKML over SMPP

[DHC Admin]

Hi Christopher
I am trying to generate this code that you talk about here. I'm following
this
http://www.simalliance.org/files/S@T/S@T_Specifications_2009/S@T%2001.00%20v4.0.0%20(Release%202009).pdf

But I cannot fully understand it.
Is there any way to create a XML that can be converted using kannel? Should
I be using PPG for this? I am trying to reverse engineering it, but is not
that easy.

Thanks!

dhcmega

On Fri, Nov 21, 2014 at 7:07 AM, Christopher Burke 
christopher.bu...@simulity.com wrote:

 Hi,

 If you have S@TML you’ll need a gateway to transform the S@TML into
 compliant ByteCode (check the SIMAlliance S@T specifications, v4.0) that
 can be interpreted by the applet. The SMPP is just for message submission.
 In any case, the UDH will be 02 70 00 for a single message or 07 00 05 XX
 YY ZZ 70 00 where XX is the same ID for all concatenated messages in the
 group, YY is the number of messages in total and ZZ is maintaining order.

 Cheers,


 *Christopher Burke*http://simulity.com
 Office: +44 (0) 1248 679 281
 Fax: +44 (0) 1248 660 323
 Skype:krslynx



 *UK*Unit 8, Ash Court,
 Parc Menai, Bangor,
 Gwynedd, LL57 4DF,
 Wales, UK


 *Malaysia*Level 30,
 The Gardens North Tower,
 Mid Valley City,
 Lingkaran Syed Putra,
 59200, Kuala Lumpur,
 Malaysia

 NOTICE: This message contains privileged  confidential information
 intended only for the use of the addressee named above. If you are not the
 intended recipient of this message, you are hereby notified that you must
 not disseminate, copy or take any action in reliance on it. If you have
 received this message in error, please notify Simulity Labs immediately.
 Any views expressed in this message are those of the individual sender
 except where the sender specifically states them to be the view of Simulity
 Labs

 On 20 November 2014 at 22:07:16, Osman (olgsevi...@gmail.com) wrote:

 Hello everyone,

 How shoud I form the UDH for sending a message to the SIM Toolkit?

 To send S@tml over smpp.

Re: UTF-8 TO UTF-16BE Error

[DHC Admin]

Hi
Have you managed to solve this?
Thanks


On Wed, Feb 6, 2013 at 5:55 AM, Ombongi Moraa Fe moraa.lovetak...@gmail.com
 wrote:

 Hi guys,

 a while ago i received my solution to receiving special characters when
 sent in messages and subsequently, sending out special characters in
 responses;

 However, i'd like a solution for another group of special characters. Some
 subscribers are sendind portugeese characters. (i think) like áú;

 Since my response script is set to coding=2 and charset =utf-8, I
 therefore result in this error in my sqlbox as seen in my log files;

 2013-02-06 10:25:03 [1148] [3] ERROR: Failed to convert string from
 UTF-8 to UTF-16BE, errno was 84

 The only way to resolve this pending message is to change in my script
 from UTF-8 to UTF-16BE so atleast the response is sent even though its
 received on phone as unreadable, then revert back to UTF-8 so that i
 don't affect the other subscribers of that service. This is especially
 currently when im running a high production with numerous messages received
 in a second yet my sqlbox is literally jammed with errors: The end result
 is I have a lot of Pending messages and a hanging server.

 How can I deal with these wierd characters in my messages in a safer way
 to ensure sqlbox is not jammed with errors?

 Thanks in advance.


 Saludos

 Ombongi Moraa fe

Re: [ANNOUNCE] Kannel 1.4.4 stable release available

[DHC Admin]

i have fixed the same problem by installing all the needed packages,
deleting the gateway-1.4.4 and starting the whole thing from scratch, re
running ./configure is not enough, so it looks.
At first I was lacking byacc and bison
Regards


On Fri, Aug 8, 2014 at 7:44 AM, Hanh Le Bich hanhmi...@gmail.com wrote:

 Many thanks Stipe.
 I've created new issue in the bug report. It's weird that have never got
 this with SVN versions.
 Anyway, i've been successful to compile on another machine with bison
 version 2.5 (the fail one has bison version 3.0.2), remain resource are
 same, because they are 2 VM on a same physical server, also OS.

 Regards,
 Hanh.


 On Fri, Aug 8, 2014 at 4:30 PM, Hanh Le Bich hanhmi...@gmail.com wrote:

 Hello,

 I have got error when do make, please help.

 app@application:/usr/src/gateway-1.4.4$ sudo make -j 24
 ...
 gcc -std=gnu99 -D_REENTRANT=1 -I. -Igw -g -O2 -D_XOPEN_SOURCE=600
 -D_BSD_SOURCE -D_LARGE_FILES= -I/usr/include/libxml2
 -I/usr/local/lib/include -I/usr/include/mysql -o gw/bearerbox.o -c
 gw/bearerbox.c
 gcc -std=gnu99 -D_REENTRANT=1 -I. -Igw -g -O2 -D_XOPEN_SOURCE=600
 -D_BSD_SOURCE -D_LARGE_FILES= -I/usr/include/libxml2
 -I/usr/local/lib/include -I/usr/include/mysql -o gw/smsbox.o -c gw/smsbox.c
 y.tab.c:348:5: error: conflicting types for ‘ws_yy_parse’
 In file included from wmlscript/wsgram.y:15:0:
 ./wmlscript/wsint.h:296:5: note: previous declaration of
 ‘ws_yy_parse’ was here
  int ws_yy_parse(void *context);
  ^
 wmlscript/wsgram.c:63:25: error: conflicting types for ‘ws_yy_parse’
  #define yyparse ws_yy_parse
  ^
 y.tab.c:1508:1: note: in expansion of macro ‘yyparse’
 In file included from wmlscript/wsgram.y:15:0:
 ./wmlscript/wsint.h:296:5: note: previous declaration of
 ‘ws_yy_parse’ was here
  int ws_yy_parse(void *context);
  ^
 wmlscript/wsgram.y: In function ‘ws_yy_parse’:
 wmlscript/wsgram.y:122:23: error: ‘pctx’ undeclared (first use in
 this function)
{ ws_error_syntax(pctx, @1.first_line); }
^
 wmlscript/wsgram.y:122:23: note: each undeclared identifier is reported
 only once for each function it appears in
 In file included from wmlscript/wslexer.c:72:0:
 y.tab.h:262:5: error: conflicting types for ‘ws_yy_parse’
 In file included from wmlscript/wslexer.c:70:0:
 wmlscript/wsint.h:296:5: note: previous declaration of ‘ws_yy_parse’
 was here
  int ws_yy_parse(void *context);
  ^
 In file included from wmlscript/wsstree.c:72:0:
 y.tab.h:262:5: error: conflicting types for ‘ws_yy_parse’
 In file included from wmlscript/wsstree.c:71:0:
 wmlscript/wsint.h:296:5: note: previous declaration of ‘ws_yy_parse’
 was here
  int ws_yy_parse(void *context);
  ^
 Makefile:231: recipe for target 'wmlscript/wsgram.o' failed
 make: *** [wmlscript/wsgram.o] Error 1
 make: *** Waiting for unfinished jobs
 Makefile:231: recipe for target 'wmlscript/wslexer.o' failed
 make: *** [wmlscript/wslexer.o] Error 1
 Makefile:231: recipe for target 'wmlscript/wsstree.o' failed
 make: *** [wmlscript/wsstree.o] Error 1
 app@application:/usr/src/gateway-1.4.4$


 Message: 1
 Date: Mon, 04 Aug 2014 15:53:42 +0200
 From: Stipe Tolj st...@kannel.org
 To: annou...@kannel.org, de...@kannel.org de...@kannel.org,
 kannel users users@kannel.org
 Subject: [ANNOUNCE] Kannel 1.4.4 stable release available
 Message-ID: 53df9066.6020...@kannel.org
 Content-Type: text/plain; charset=iso-8859-15; Format=flowed

 The Kannel Group is pleased to announce the availability of Kannel 1.4.4
 stable release via our web site at URL

 http://www.kannel.org/download.shtml

 Please find attached the NEWS file section for the 1.4.4 stable release.

 Best Regards,
 Stipe Tolj

 --
 ---
 K?lner Landstrasse 419
 40589 D?sseldorf, NRW, Germany

 tolj.org system architecture  Kannel Software Foundation (KSF)
 http://www.tolj.org/  http://www.kannel.org/

 mailto:st_{at}_tolj.org   mailto:stolj_{at}_kannel.org
 ---


 Regards,
 Hanh.

reconnect-delay bug

[DHC Admin]

Hi
I am using svn5031

group = smsc
smsc = smpp
smsc-id = my-smsc
host = 123.123.123.123
receive-port = 0
port = 5000
transceiver-mode = false
smsc-username = xxx
smsc-password = yy
system-type = smpp
enquire-link-interval = 20
reconnect-delay = 90
source-addr-ton = 4
source-addr-npi = 9
dest-addr-ton = 4
dest-addr-npi = 9
throughput = 8
esm-class = 0

and I am getting this

2014-08-24 11:04:37 [26211] [7] WARNING: SMPP: PDU NULL terminated string
(system_id) has no NULL.

2014-08-24 11:04:38 [26211] [7] ERROR: SMPP[my-smsc]: I/O error or other
error. Re-connecting.

2014-08-24 11:04:38 [26211] [7] ERROR: SMPP[my-smsc]: Couldn't connect to
SMS center (retrying in 90 seconds).

2014-08-24 11:04:38 [26211] [7] WARNING: SMPP: PDU NULL terminated string
(system_id) has no NULL.

2014-08-24 11:04:39 [26211] [7] ERROR: SMPP[my-smsc]: I/O error or other
error. Re-connecting.

2014-08-24 11:04:39 [26211] [7] ERROR: SMPP[my-smsc]: Couldn't connect to
SMS center (retrying in 90 seconds).

2014-08-24 11:04:39 [26211] [7] WARNING: SMPP: PDU NULL terminated string
(system_id) has no NULL.

2014-08-24 11:04:40 [26211] [7] ERROR: SMPP[my-smsc]: I/O error or other
error. Re-connecting.

2014-08-24 11:04:40 [26211] [7] ERROR: SMPP[my-smsc]: Couldn't connect to
SMS center (retrying in 90 seconds).

2014-08-24 11:04:40 [26211] [7] WARNING: SMPP: PDU NULL terminated string
(system_id) has no NULL.

2014-08-24 11:04:41 [26211] [7] ERROR: SMPP[my-smsc]: I/O error or other
error. Re-connecting.

2014-08-24 11:04:41 [26211] [7] ERROR: SMPP[my-smsc]: Couldn't connect to
SMS center (retrying in 90 seconds).


How can it try to reconnect every second while claiming to be waiting 90
seconds?


Thanks

Re: Tunning up kannel

[DHC Admin]

Hi Ahmed
Have you tweaked the smsbox-max-pending and/or max-pending-requests?
Check for them on the user guide


On Wed, Jun 4, 2014 at 11:33 AM, Ahmed BOUDHRAA 
ahmed.boudh...@inbmi.edunet.tn wrote:

 Hi
 we are using kannel about 2 years in our institution and its woriking like
 a charm. we have high load traffic with 3 operators with 3 kannel gatways,
 our configuration is like this:

 - kannel 1 : Operator 1 : VM 2 x CPU 3 Ghz  8 Go Ram
 - kannel 2 : Operator 2 : VM 2 x CPU 3 Ghz  8 Go Ram
 - kannel 3 : Operator 3 : VM 2 x CPU 3 Ghz  8 Go Ram
 - Web Portal: for all kannel : VM 8 x CPU 3 Ghz 32 Go RAM
 - Postgres Database behind the web server : VM 8 x CPU 3 Ghz 32 Go RAM

 All those server are running under ESXi hypervisor in SAN environnement.
 Any way we are tunning all the plateform with several tools ( ApacheBench
 for web load and fakesms for kannel)
 we want to profit of all the hardware ressources with optimizing all
 componenents to reach the limits of the hardware, but still are still far
 behind the real capability of the hardware.
 The fact is we have reached 800 sms /s with the operators and its fine,
 but we want more not that we need it right now but just to master how every
 things work...
 The WEB/DB side tunning is well done due to fact that we have mastered
 it in our webs servers but the kannel side is litle different. with fakesms
 we are sending about 1000 sms / s from each kannel so we want to manage
 3000 sms / s in our portal  but all the kannel dosent send them with the
 speed we want even if they are not even litle solicited, we noticed that
 the bottle neck is between the smsbox and the bearerbox we dont know
 exactly but all 1000 sms arrive instantelly to the bearerbox in each kannel
 and a queue is formed between the bearerbox and smsbox, the smsbox send to
 the web server ( the portal ) about 1200 request / s wich is far from his
 limit ( we have tunning it to manage 3500 request / s ) I ve talked a lot
 but the main question is how we remove that so called queue
 smsbox/bearebox? to make the kannels send more than 1200 request/s so we
 can reach the limits in all the equippements all the system is running far
 behind his capabilitys.
 thinx for the help

Re: Tunning up kannel

[DHC Admin]

Because you were talking about very high number, I have assumed it was a MO
rate, and not MT rate. What is your MT throughput?


On Mon, Jun 9, 2014 at 10:40 AM, spameden spame...@gmail.com wrote:




 2014-06-09 17:08 GMT+04:00 Ahmed BOUDHRAA ahmed.boudh...@inbmi.edunet.tn
 :

 HI
 thx for the relpay i was wondering if someone will help :)
 the fact is that we tunned the max-pending-requests and we ve concluded
 that about 800 is the best value and if we go up the results go worst, but
 the smsbox-max-pending we havent added such parametre; can you please
 explain it, is it, the smsbox-max-pending, is the queue between the smsbox
 and our portal?


 I can't imagine why do you need such high rate of sending MT messages for
 university unless you're spamming your students every second ..

 The speed also very much depends on your SMSC upstream providers, network
 link between you and them, TCP RTT (re-transmissions), etc.

 The general settings for throughput between you and smsc are:

 1) throughput -- limits MT/sec
 2) max-pending-submits -- unofficial parameter, controls how many
 outstanding operations between you and SMSC (e.g. unacknowledged
 submit_sm packets)

 Try tuning these two parameters to get maximum of your upstream SMSC. Do
 it carefully to not get THROTTLED errors or MAX_QUEUE errors. Consulting
 your provider is highly recommended.





 if i make it more simple:

 what is the difference between the tow variable that you gived to us : 
 smsbox-max-pending
 and max-pending-requests ? and where are they placed, i mean if there is
 tow pending queue, i think one is in front of the bearerbox ( can i assume
 it is the max-pending-requests ?) and one between the bearerbox and the
 smsbox ? ( should it be the smsbox-max-pending ???) if my assumption are
 right i could be the bottleneck coz we havent touch such parametre, and if
 so the default value is about how much?


 check user-guide, it's available on the WEB:
 http://kannel.org/download/kannel-userguide-snapshot/userguide.html

 bottleneck is most likely your code in DLR-url parsing script not the
 kannel itself.

 try testing with different conditions:

 1) without DLR reports at all
 2) with DLR but without your url hit
 3) with DLR and your URL

 Also, you might want to consider switching over to sqlbox, so you won't
 need to drag web-server each time report comes.



 thinx again for the help



 - Mail Original -
 De: DHC Admin dhcad...@gmail.com
 À: Ahmed BOUDHRAA ahmed.boudh...@inbmi.edunet.tn
 Cc: users@kannel.org
 Envoyé: Lundi 9 Juin 2014 13:50:46
 Objet: Re: Tunning up kannel


 Hi Ahmed
 Have you tweaked the smsbox-max-pending and/or max-pending-requests?
 Check for them on the user guide


 On Wed, Jun 4, 2014 at 11:33 AM, Ahmed BOUDHRAA 
 ahmed.boudh...@inbmi.edunet.tn wrote:

 Hi
 we are using kannel about 2 years in our institution and its woriking
 like a charm. we have high load traffic with 3 operators with 3 kannel
 gatways, our configuration is like this:

 - kannel 1 : Operator 1 : VM 2 x CPU 3 Ghz  8 Go Ram
 - kannel 2 : Operator 2 : VM 2 x CPU 3 Ghz  8 Go Ram
 - kannel 3 : Operator 3 : VM 2 x CPU 3 Ghz  8 Go Ram
 - Web Portal: for all kannel : VM 8 x CPU 3 Ghz 32 Go RAM
 - Postgres Database behind the web server : VM 8 x CPU 3 Ghz 32 Go RAM

 All those server are running under ESXi hypervisor in SAN environnement.
 Any way we are tunning all the plateform with several tools ( ApacheBench
 for web load and fakesms for kannel)
 we want to profit of all the hardware ressources with optimizing all
 componenents to reach the limits of the hardware, but still are still far
 behind the real capability of the hardware.
 The fact is we have reached 800 sms /s with the operators and its fine,
 but we want more not that we need it right now but just to master how every
 things work...
 The WEB/DB side tunning is well done due to fact that we have
 mastered it in our webs servers but the kannel side is litle different.
 with fakesms we are sending about 1000 sms / s from each kannel so we want
 to manage 3000 sms / s in our portal  but all the kannel dosent send them
 with the speed we want even if they are not even litle solicited, we
 noticed that the bottle neck is between the smsbox and the bearerbox we
 dont know exactly but all 1000 sms arrive instantelly to the bearerbox in
 each kannel and a queue is formed between the bearerbox and smsbox, the
 smsbox send to the web server ( the portal ) about 1200 request / s wich is
 far from his limit ( we have tunning it to manage 3500 request / s ) I ve
 talked a lot but the main question is how we remove that so called queue
 smsbox/bearebox? to make the kannels send more than 1200 request/s so we
 can reach the limits in all the equippements all the system is running far
 behind his capabilitys.
 thinx for the help

Re: Tunning up kannel

[DHC Admin]

Hi Ahmed
Maybe the Bearebox has emptied the its queue and the queue moves to the
smsbox? Are you sure you have enough resources to receive that much number
of SMS at the same time? The Apache web server news to spawn (create) a big
number of clients to handle the traffic, it might run out of resources for
a few seconds and the smsbox could be resending the MOs later on, based on
this configuration:

http-request-retryinteger If set, specifies how many retries should be
performed for failing HTTP requests of sms-services. Defaults to 0, which
means no retries should be performed and hence no HTTP request queuing is
done. http-queue-delayinteger If set, specifies how many seconds should
pass within the HTTP queuing thread for retrying a failed HTTP request.
Defaults to 10 sec. and is only obeyed if http-request-retry is set to a
non-zero value.

Have you tried to disable the HTTP retry and see if you loose any MO? Maybe
they are getting retried.

Please tell me where is that you see the MO Queue that you mention, are you
just checking the status by console or using a HTML page?




On Mon, Jun 9, 2014 at 11:51 AM, Ahmed BOUDHRAA 
ahmed.boudh...@inbmi.edunet.tn wrote:

 Thinx spameden

 Our plateform is made for publishing mainlly baccalaureate results, and
 tow other grades this is the main use right now, all those are about 240
 000 canditates the fact is they may look like not much, but its a very
 important event that every parents/student attends the problematic its not
 about the nember but about the ammount of incoming/outgoing sms in a short
 time, last year we have reached the 800 sms /s in the operator side so you
 can imagine how it could be stressfull for us / the operators / the
 parents-students we cant allow any unavalability or too much wait, you can
 add to that that our plateform will do other things in the future :)

 for the throughput between as and the operators we fixied it in
 accordance with them every operator have specific capabilities but as i
 said our plateform can manage them at ease, what we want is to prepare our
 self, and to understand all the possible problem/solutions that we may have
 in using kannel.

 For the web server side, i cant assure that he is far from his real
 capabilities we are using RHEL web servers from long now. for the current
 configuration our web server can serve about 4000 requests / s i ll try
 below to describe a simple test we made usining fakesms:

 We are launching this test from our 3 kannel server simultanisouly :

 ./fakesmsc -i 0.001 -m 1 100 200 text test 00*  == this
 mean about 1000 sms /s from each kannel technically we could say that our
 portal should manage 3000 sms / s

 when we llaunch the test we can see on the kannel status in the box
 connections rubrique the Queued (MO) started  1 x 3 and it take about
 5 minutes to empty the three queue now what we want to understand is how
 the viewed queue is empty, the web server is far from his treatement
 capabilities and still messages are comming about 1-2 sms /s after about
 15000 have reached the database. I dont know if i m clear normally when the
 queue is empty we have to have 3 sms on the database side, wich mean
 there is another queue somewhere else


 this is our smskannel.conf : we are not using dlr nor internal storage:



 group = core
 admin-port = 13000
 smsbox-port = 2776
 admin-password = 123456
 box-deny-ip = *.*.*.*
 box-allow-ip = 127.0.0.1
 log-file = /var/log/kannel/kannel.log
 log-level = 0
 access-log = /var/log/kannel/access_kannel.log
 access-log-clean = true
 access-log-format= SMS %t %l %i %p %P %b %F %I %k
 store-file =/var/log/kannel/sms.store
 dlr-storage = internal
 store-dump-freq = 5
 sms-resend-freq = 60
 sms-resend-retry = -1


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


 group = smsc
 smsc = fake
 smsc-id = fake
 port = 1




 group = smsc
 smsc = smpp
 smsc-id = TT
 host = x.x.x.x
 port = 
 log-file = /var/log/kannel/tt1.log
 log-level = 0
 transceiver-mode = 1
 receive-port = 
 smsc-username = user
 smsc-password = pass
 system-type = 'VMA'
 interface-version = 34
 preferred-smsc-id = TT


 group = smsc
 smsc = smpp
 smsc-id = TT

 host = x.x.x.x
 port = 
 log-file = /var/log/kannel/tt2.log
 log-level = 0
 transceiver-mode = 1
 receive-port = 
 smsc-username = user
 smsc-password = pass
 system-type = 'VMA'
 #service-type = 'test'
 interface-version = 34
 preferred-smsc-id = TT

 group = smsc
 smsc = smpp
 smsc-id = TT
 host = x.x.x.x
 port = 
 log-file = /var/log/kannel/tt3.log
 log-level = 0
 transceiver-mode = 1
 receive-port = 
 smsc-username = user
 smsc-password = pass
 system-type = 'VMA'
 interface-version = 34
 preferred-smsc-id = TT

 group = smsc

Re: FAKESMSC testing highload - 20% of MT rejected

[DHC Admin]

SUCCESS

cat *.log | grep  '36689792'

2014-05-30 21:33:21 Receive SMS [SMSC:fakesmsc] [SVC:] [ACT:] [BINF:]
[FID:] [META:] [from:36689792] [to:113] [flags:-1:0:-1:-1:-1]
[msg:4:alta] [udh:0:]

2014-05-30 21:33:21 Sent SMS [SMSC:fakesmsc] [SVC:tester] [ACT:] [BINF:]
[FID:] [META:] [from:113] [to:36689792] [flags:-1:0:-1:-1:-1]
[msg:10:id: 326670] [udh:0:]

2014-05-30 21:33:21 send-SMS request added - sender:tester:113 127.0.0.1
target:36689792 request: 'id: 326670'

2014-05-30 21:33:21 SMS HTTP-request sender:36689792 request: 'OK
[0,003] Status: 0' url: 'http://localhost/indexJson.php' reply: 200 '
successful '

2014-05-30 21:33:21 [15305] [5] INFO: Starting to service alta from
36689792 to 113

2014-05-30 21:33:21 [15305] [3] INFO: sendsms sender:tester:113
(127.0.0.1) to:36689792 msg:id: 326670


FAIL

cat *.log | grep '05695347'

2014-05-30 21:33:31 Receive SMS [SMSC:fakesmsc] [SVC:] [ACT:] [BINF:]
[FID:] [META:] [from:05695347] [to:113] [flags:-1:0:-1:-1:-1]
[msg:4:alta] [udh:0:]

2014-05-30 21:33:40 SMS HTTP-request sender:05695347 request: 'OK
[0,203] Status: 999' url: 'http://localhost/indexJson.php' reply: 200 '
successful '

2014-05-30 21:33:32 [15305] [5] INFO: Starting to service alta from
05695347 to 113


On Fri, May 30, 2014 at 9:31 PM, DHC Admin dhcad...@gmail.com wrote:

 Hi
 Ok, so I  have the 5089 csv kannel with fakesmsc
 I am stressing the server and 20% of the messages are not accepted by the
 smsbox, but silently, it is like closing the port, is it possible?
 I have increased the ulimit and tested a lot and I am out of resources:


 START SCRIPT

 #!/bin/sh
 # Start/stop the Kannel boxes: One bearer box and one WAP box.

 # This is the default init.d script for Kannel.  Its configuration is
 # appropriate for a small site running Kannel on one machine.

 # Make sure that the Kannel binaries can be found in $BOXPATH or somewhere
 # else along $PATH.  run_kannel_box has to be in $BOXPATH.

 BOXPATH=/usr/local
 PIDFILES=/var/run
 CONFDIR=/etc/kannel
 CONF=$CONFDIR/kannel-fake.conf
 CONFSP=$CONFDIR/opensmppbox-fake.conf

 USER=kannel
 VERSION=

 RB=$BOXPATH/kannel/sbin/run_kannel_box$VERSION
 BB=$BOXPATH/kannel/sbin/bearerbox$VERSION
 WB=$BOXPATH/kannel/sbin/wapbox$VERSION
 SB=$BOXPATH/kannel/sbin/smsbox$VERSION
 SP=$BOXPATH/kannel/sbin/opensmppbox$VERSION
 SSD=start-stop-daemon$VERSION

 PATH=$BOXPATH:$PATH

 # On Debian, the most likely reason for the bearerbox not being available
 # is that the package is in the removed or unconfigured state, and the
 # init.d script is still around because it's a conffile.  This is normal,
 # so don't generate any output.
 test -x $BB || exit 0

 case $1 in
   start)
 echo -n Starting SMPP gateway:
 echo -n  bearerbox
 ulimit -n 10
 $SSD --start --quiet --pidfile $PIDFILES/kannel_bearerbox-fake.pid
 --exec $RB -- --pidfile $PIDFILES/kannel_bearerbox-fake.pid $BB -v
 $DEBUGLVL -- $CONF
 #echo -n  wapbox
 #$SSD --start --quiet --pidfile $PIDFILES/kannel_wapbox-fake.pid
 --exec $RB -- --pidfile $PIDFILES/kannel_wapbox-fake.pid $WB -- $CONF
 echo -n  smsbox
 $SSD --start --quiet --pidfile $PIDFILES/kannel_smsbox-fake.pid --exec
 $RB -- --pidfile $PIDFILES/kannel_smsbox-fake.pid $SB -v $DEBUGLVL -- $CONF
 #echo -n  opensmppbox
 #$SSD --start --quiet --pidfile $PIDFILES/kannel_opensmppbox-fake.pid
 --exec $RB -- --pidfile $PIDFILES/kannel_opensmppbox-fake.pid $SP -v
 $DEBUGLVL -- $CONFSP
 echo .
 ;;

   stop)
 echo -n Stopping SMPP gateway:
 #echo -n  wapbox
 #$SSD --stop --quiet --pidfile $PIDFILES/kannel_wapbox-fake.pid --exec
 $RB
 #echo -n  opensmppbox
 #$SSD --stop --quiet --pidfile $PIDFILES/kannel_opensmppbox-fake.pid
 --exec $RB
 echo -n  smsbox
 $SSD --stop --quiet --pidfile $PIDFILES/kannel_smsbox-fake.pid --exec
 $RB
 echo -n  bearerbox
 $SSD --stop --quiet --pidfile $PIDFILES/kannel_bearerbox-fake.pid
 --exec $RB
 echo .
 ;;

   status)
 CORE_CONF=$(grep -r 'group[[:space:]]*=[[:space:]]*core' $CONFDIR |
 cut -d: -f1)
 ADMIN_PORT=$(grep '^admin-port' $CORE_CONF | sed s/.*=[[:space:]]*//)
 ADMIN_PASS=$(grep '^admin-password' $CORE_CONF | sed
 s/.*=[[:space:]]*//)
 STATUS_URL=http://127.0.0.1:
 ${ADMIN_PORT}/status.txt?password=${ADMIN_PASS}
 lynx -source $STATUS_URL
 ;;

   reload)
 # We don't have support for this yet.
 exit 1
 ;;

   restart|force-reload)
 $0 stop
 sleep 1
 $0 start
 ;;

   *)
 echo Usage: $0 {start|stop|status|reload|restart|force-reload}
 exit 1

 esac

 exit 0



 FAKESMSC configuration

 
 ## CORE CONFIGURATION ##
 

 group = core
 admin-port = 23700
 admin-password = corepass
 admin-deny-ip = *.*.*.*
 admin-allow-ip = 127.0.0.1
 smsbox-port = 23701
 box-allow

Re: FAKESMSC testing highload - 20% of MT rejected

[DHC Admin]

It seems that the problem is not Kannel or Apache related, it is a binding
problem inside the server, with this error:

Cannot assign requested address


On Sat, May 31, 2014 at 5:26 PM, DHC Admin dhcad...@gmail.com wrote:

 SUCCESS

 cat *.log | grep  '36689792'

 2014-05-30 21:33:21 Receive SMS [SMSC:fakesmsc] [SVC:] [ACT:] [BINF:]
 [FID:] [META:] [from:36689792] [to:113] [flags:-1:0:-1:-1:-1]
 [msg:4:alta] [udh:0:]

 2014-05-30 21:33:21 Sent SMS [SMSC:fakesmsc] [SVC:tester] [ACT:] [BINF:]
 [FID:] [META:] [from:113] [to:36689792] [flags:-1:0:-1:-1:-1]
 [msg:10:id: 326670] [udh:0:]

 2014-05-30 21:33:21 send-SMS request added - sender:tester:113 127.0.0.1
 target:36689792 request: 'id: 326670'

 2014-05-30 21:33:21 SMS HTTP-request sender:36689792 request: 'OK
 [0,003] Status: 0' url: 'http://localhost/indexJson.php' reply: 200 '
 successful '

 2014-05-30 21:33:21 [15305] [5] INFO: Starting to service alta from
 36689792 to 113

 2014-05-30 21:33:21 [15305] [3] INFO: sendsms sender:tester:113
 (127.0.0.1) to:36689792 msg:id: 326670


 FAIL

 cat *.log | grep '05695347'

 2014-05-30 21:33:31 Receive SMS [SMSC:fakesmsc] [SVC:] [ACT:] [BINF:]
 [FID:] [META:] [from:05695347] [to:113] [flags:-1:0:-1:-1:-1]
 [msg:4:alta] [udh:0:]

 2014-05-30 21:33:40 SMS HTTP-request sender:05695347 request: 'OK
 [0,203] Status: 999' url: 'http://localhost/indexJson.php' reply: 200 '
 successful '

 2014-05-30 21:33:32 [15305] [5] INFO: Starting to service alta from
 05695347 to 113


 On Fri, May 30, 2014 at 9:31 PM, DHC Admin dhcad...@gmail.com wrote:

 Hi
 Ok, so I  have the 5089 csv kannel with fakesmsc
 I am stressing the server and 20% of the messages are not accepted by the
 smsbox, but silently, it is like closing the port, is it possible?
 I have increased the ulimit and tested a lot and I am out of resources:


 START SCRIPT

 #!/bin/sh
 # Start/stop the Kannel boxes: One bearer box and one WAP box.

 # This is the default init.d script for Kannel.  Its configuration is
 # appropriate for a small site running Kannel on one machine.

 # Make sure that the Kannel binaries can be found in $BOXPATH or somewhere
 # else along $PATH.  run_kannel_box has to be in $BOXPATH.

 BOXPATH=/usr/local
 PIDFILES=/var/run
 CONFDIR=/etc/kannel
 CONF=$CONFDIR/kannel-fake.conf
 CONFSP=$CONFDIR/opensmppbox-fake.conf

 USER=kannel
 VERSION=

 RB=$BOXPATH/kannel/sbin/run_kannel_box$VERSION
 BB=$BOXPATH/kannel/sbin/bearerbox$VERSION
 WB=$BOXPATH/kannel/sbin/wapbox$VERSION
 SB=$BOXPATH/kannel/sbin/smsbox$VERSION
 SP=$BOXPATH/kannel/sbin/opensmppbox$VERSION
 SSD=start-stop-daemon$VERSION

 PATH=$BOXPATH:$PATH

 # On Debian, the most likely reason for the bearerbox not being available
 # is that the package is in the removed or unconfigured state, and the
 # init.d script is still around because it's a conffile.  This is normal,
 # so don't generate any output.
 test -x $BB || exit 0

 case $1 in
   start)
 echo -n Starting SMPP gateway:
 echo -n  bearerbox
 ulimit -n 10
 $SSD --start --quiet --pidfile $PIDFILES/kannel_bearerbox-fake.pid
 --exec $RB -- --pidfile $PIDFILES/kannel_bearerbox-fake.pid $BB -v
 $DEBUGLVL -- $CONF
 #echo -n  wapbox
 #$SSD --start --quiet --pidfile $PIDFILES/kannel_wapbox-fake.pid
 --exec $RB -- --pidfile $PIDFILES/kannel_wapbox-fake.pid $WB -- $CONF
 echo -n  smsbox
 $SSD --start --quiet --pidfile $PIDFILES/kannel_smsbox-fake.pid
 --exec $RB -- --pidfile $PIDFILES/kannel_smsbox-fake.pid $SB -v $DEBUGLVL
 -- $CONF
 #echo -n  opensmppbox
 #$SSD --start --quiet --pidfile $PIDFILES/kannel_opensmppbox-fake.pid
 --exec $RB -- --pidfile $PIDFILES/kannel_opensmppbox-fake.pid $SP -v
 $DEBUGLVL -- $CONFSP
 echo .
 ;;

   stop)
 echo -n Stopping SMPP gateway:
 #echo -n  wapbox
 #$SSD --stop --quiet --pidfile $PIDFILES/kannel_wapbox-fake.pid
 --exec $RB
 #echo -n  opensmppbox
 #$SSD --stop --quiet --pidfile $PIDFILES/kannel_opensmppbox-fake.pid
 --exec $RB
 echo -n  smsbox
 $SSD --stop --quiet --pidfile $PIDFILES/kannel_smsbox-fake.pid --exec
 $RB
 echo -n  bearerbox
 $SSD --stop --quiet --pidfile $PIDFILES/kannel_bearerbox-fake.pid
 --exec $RB
 echo .
 ;;

   status)
 CORE_CONF=$(grep -r 'group[[:space:]]*=[[:space:]]*core' $CONFDIR |
 cut -d: -f1)
 ADMIN_PORT=$(grep '^admin-port' $CORE_CONF | sed
 s/.*=[[:space:]]*//)
 ADMIN_PASS=$(grep '^admin-password' $CORE_CONF | sed
 s/.*=[[:space:]]*//)
 STATUS_URL=http://127.0.0.1:
 ${ADMIN_PORT}/status.txt?password=${ADMIN_PASS}
 lynx -source $STATUS_URL
 ;;

   reload)
 # We don't have support for this yet.
 exit 1
 ;;

   restart|force-reload)
 $0 stop
 sleep 1
 $0 start
 ;;

   *)
 echo Usage: $0 {start|stop|status|reload|restart|force-reload}
 exit 1

 esac

 exit 0



 FAKESMSC configuration

 
 ## CORE

FAKESMSC testing highload - 20% of MT rejected

[DHC Admin]

Hi
Ok, so I  have the 5089 csv kannel with fakesmsc
I am stressing the server and 20% of the messages are not accepted by the
smsbox, but silently, it is like closing the port, is it possible?
I have increased the ulimit and tested a lot and I am out of resources:


START SCRIPT

#!/bin/sh
# Start/stop the Kannel boxes: One bearer box and one WAP box.

# This is the default init.d script for Kannel.  Its configuration is
# appropriate for a small site running Kannel on one machine.

# Make sure that the Kannel binaries can be found in $BOXPATH or somewhere
# else along $PATH.  run_kannel_box has to be in $BOXPATH.

BOXPATH=/usr/local
PIDFILES=/var/run
CONFDIR=/etc/kannel
CONF=$CONFDIR/kannel-fake.conf
CONFSP=$CONFDIR/opensmppbox-fake.conf

USER=kannel
VERSION=

RB=$BOXPATH/kannel/sbin/run_kannel_box$VERSION
BB=$BOXPATH/kannel/sbin/bearerbox$VERSION
WB=$BOXPATH/kannel/sbin/wapbox$VERSION
SB=$BOXPATH/kannel/sbin/smsbox$VERSION
SP=$BOXPATH/kannel/sbin/opensmppbox$VERSION
SSD=start-stop-daemon$VERSION

PATH=$BOXPATH:$PATH

# On Debian, the most likely reason for the bearerbox not being available
# is that the package is in the removed or unconfigured state, and the
# init.d script is still around because it's a conffile.  This is normal,
# so don't generate any output.
test -x $BB || exit 0

case $1 in
  start)
echo -n Starting SMPP gateway:
echo -n  bearerbox
ulimit -n 10
$SSD --start --quiet --pidfile $PIDFILES/kannel_bearerbox-fake.pid
--exec $RB -- --pidfile $PIDFILES/kannel_bearerbox-fake.pid $BB -v
$DEBUGLVL -- $CONF
#echo -n  wapbox
#$SSD --start --quiet --pidfile $PIDFILES/kannel_wapbox-fake.pid --exec
$RB -- --pidfile $PIDFILES/kannel_wapbox-fake.pid $WB -- $CONF
echo -n  smsbox
$SSD --start --quiet --pidfile $PIDFILES/kannel_smsbox-fake.pid --exec
$RB -- --pidfile $PIDFILES/kannel_smsbox-fake.pid $SB -v $DEBUGLVL -- $CONF
#echo -n  opensmppbox
#$SSD --start --quiet --pidfile $PIDFILES/kannel_opensmppbox-fake.pid
--exec $RB -- --pidfile $PIDFILES/kannel_opensmppbox-fake.pid $SP -v
$DEBUGLVL -- $CONFSP
echo .
;;

  stop)
echo -n Stopping SMPP gateway:
#echo -n  wapbox
#$SSD --stop --quiet --pidfile $PIDFILES/kannel_wapbox-fake.pid --exec
$RB
#echo -n  opensmppbox
#$SSD --stop --quiet --pidfile $PIDFILES/kannel_opensmppbox-fake.pid
--exec $RB
echo -n  smsbox
$SSD --stop --quiet --pidfile $PIDFILES/kannel_smsbox-fake.pid --exec
$RB
echo -n  bearerbox
$SSD --stop --quiet --pidfile $PIDFILES/kannel_bearerbox-fake.pid
--exec $RB
echo .
;;

  status)
CORE_CONF=$(grep -r 'group[[:space:]]*=[[:space:]]*core' $CONFDIR | cut
-d: -f1)
ADMIN_PORT=$(grep '^admin-port' $CORE_CONF | sed s/.*=[[:space:]]*//)
ADMIN_PASS=$(grep '^admin-password' $CORE_CONF | sed
s/.*=[[:space:]]*//)
STATUS_URL=http://127.0.0.1:
${ADMIN_PORT}/status.txt?password=${ADMIN_PASS}
lynx -source $STATUS_URL
;;

  reload)
# We don't have support for this yet.
exit 1
;;

  restart|force-reload)
$0 stop
sleep 1
$0 start
;;

  *)
echo Usage: $0 {start|stop|status|reload|restart|force-reload}
exit 1

esac

exit 0



FAKESMSC configuration


## CORE CONFIGURATION ##


group = core
admin-port = 23700
admin-password = corepass
admin-deny-ip = *.*.*.*
admin-allow-ip = 127.0.0.1
smsbox-port = 23701
box-allow-ip = *.*.*.*
log-file = /var/log/kannel/fake/bearerbox.log
log-level = 4
access-log = /var/log/kannel/fake/bearerbox_access.log
store-location = /var/lib/kannel/store_file-ar-personal.log
smsbox-max-pending = 10
sms-resend-retry = 1
sms-resend-freq = 60


## SMSBOX ##


group = smsbox
bearerbox-host = 127.0.0.1
sendsms-port = 23713
log-file = /var/log/kannel/fake/smsbox.log
log-level = 4
access-log = /var/log/kannel/fake/smsbox_access.log
# cantidad de veces que trata de entregar el MO
#http-request-retry = 5
http-request-retry = 3
# segundos de wait antes de entregar el MO al apache en caso de retry
http-queue-delay = 60
# numero de MOs en paralelo
max-pending-requests = 500
#mo-recode = 1


## SENDSMS-USER 


group = sendsms-user
username = tester
password = foobar
user-deny-ip = *.*.*.*
user-allow-ip = 127.0.0.1;192.168.2.11;192.168.2.12;192.168.2.13
max-messages = 2
concatenation = true



## SMSCs

max-pending-requests vs max-concurrent-requests

[DHC Admin]

Hi all

If max-pending-requests is this:
Maximum number of pending MO or DLR messages that are handled in parallel.
(Default: 512)

When added it was defined as:
Added config directive 'max-pending-requests' for smsbox group to control
the outbound requests stream generated from smsbox towards HTTP application
servers.


Shouldn't it be max-concurrent-requests, max-pending-requests sounds as
queued.

I think I have always missed this directive.

Regards

Re: PDU decoding

[DHC Admin]

Hi
Is it possible that a WAP SI notification pops up with an OK-Cancel button
and that the OK triggers an MO message?
Thanks


On Tue, Nov 6, 2007 at 3:38 PM, Ady Wicaksono ady.wicaks...@gmail.comwrote:

 See this one:

 Example Service Indication XML is like this:

 ?xml version=1.0?
 !DOCTYPE si PUBLIC -//WAPFORUM//DTD SI 1.0//EN
  http://www.wapforum.org/DTD/si.dtd;
 si
 indication href=http://www.xyz.com/email/123/abc.wml;
 created=1999-06-25T15:23:15Z
 si-expires=2099-06-30T00:00:00Z
 You have 4 new emails
 /indication
 /si

 Decode that one to WBXML rule, so we have

 02 05 6A 00 45 C6 0D 03 'x' 'y' 'z' 00 85 03 'e' 'm'
 'a' 'i' 'l' '/' '1' '2' '3' '/' 'a' 'b' 'c' '.' 'w' 'm' 'l' 00
 0A C3 07 19 99 06 25 15 23 15 10 C3 04 20 99 06
 30 01 03 'Y' 'o' 'u' ' ' 'h' 'a' 'v' 'e' ' ' '4' ' ' 'n' 'e'
 'w' ' ' 'e' '-' 'm' 'a' 'i' 'l' 's' 00 01 01

 or


 02056A0045C60D0378797A008503656D61696C2F3132332F6162632E776D6C000AC307199906251
 5231510C304209906030103596F7520686176652034206E657720652D6D61696C73000101

 detail

 02  WBXML versi 1.2
 05 SI 1.0 Public Identifier,
 6A charset UTF-8
 00 Length of table string=0x00
 45 Tag si without attribute followed by content
 C6 Tag indication with attribute followed by content
 0D code for attribute href=http://www.;
 03 String followed
 'x','y','z', 00 String xyz ended by NULL (0x00)
 85 string .com/
 03 String followed
 'e', 'm', 'a', 'i', 'l', '/', '1', '2','3', '/', 'a', 'b', 'c', '.',
 'w', 'm','l', 00: String email/123/abc.wml ende dby  NULL (0x00)
 0A attribute created=
 C3 Penanda bahwa ada tipe data OPAQUE yang
 07 Panjang = 7 bytes
 19,99,06,25,15,23,15 Data opaque yang dimaksud. Data ini mengacu
 ke informasi tanggal 1999-06-25 15:23:15
 10 Kode untuk atribut si-expires=
 C3 data OPAQUE following
 04 Length = 4 bytes
 20,99,06,30 Opaq Data refer to this date:  2099-06-30 00:00:00
 01 END (end of attribute)
 03 String followed
 'Y','o','u',' ','h','a','v','e',' ','4', ' ','e','-
 ','m','a','i','l','s',00 String You have 4 emails ended by NULL (0x00)
 01 END (of indication) -tag /indication
 01 END (of si) - tag /si

 Then we need to append WSP Header

 01060403AE81EA

 Detail:
 01 Push ID
 06 WSP PDU Type = Push
 04 Length PDU Push WSP followed = 4 octet
 03 Length of content type + header = 3 octet
 AE content type: application/vnd.wap.sic (originally value is 0x2E)
 Must be coded with OR rule with 0x80
 0x2E = 00101110
 0x80 = 1000
 --- OR
 0xAE = 10101110

 we got 0xAE

 81 Header WSP 0x81 = 0x01 | 0x80, which is Accept-Charset
 EA Value of header Accept-Charset which is   UTF 8 (hexa 0x6A). 0xEA =
 0x6A|0x80


 We also need to define header WDP

 Header WDP on  SMS: 05040B8423F0

 05 IEI (Application Port Schema Addressing, 16 bit)
 04 Length  IEI = 4 byte, yakni 4 byte yang mengikuti byte ini
 0B84 Port WDP dest SMS = 0x0B84 (hexa) = 2948 (desimal) = WAP Push
 connectionless
 session service (client side)
 23F0 Port WDP sender SMS = 0x23F0 (hexa) = Connectionless WAP Browser Proxy
 Server

 Totally

 05040B8423F0 (WDP Layer)
 01060403AE81EA (WSP Layer)
 02056A0045C60D0378797A008503656D61696C2F3132332F6162632E776D6C000AC307199906251

 5231510C304209906030103596F7520686176652034206E657720652D6D61696C73000101

 we got this TP-UD sms


 05040B8423F001060403AE81EA02056A0045C60D0378797A008503656D61696C2F3132332F61626
 32E776D6C000AC3071999062515231510C304209906030103596F7520686176652034206E657720

 652D6D61696C73000101

 still under 140 octet right? so we can send it using 1 SMS only

 construct SMS like this


 55010C9126582602680800F5A75A0605040B8423F001060403AE81EA02056A0045C60D0378797A0
 08503656D61696C2F3132332F6162632E776D6C000AC3071999062515231510C304209906030103

 596F7520686176652034206E657720652D6D61696C73000101

 your WAP Push SMS is ready

 Good luck



 On 11/7/07, Diego Castillo  diego.casti...@inexbee.com wrote:

 Hello,

 I'm using Kannel to send some wap push messages and I'd like to decode
 the
 PDUs for troubleshooting. This is what I see in the Kannel logs:

 2007-11-06 12:29:30 Sent SMS [SMSC:smsc-0] [SVC:ppg] [ACT:] [BINF:]
 [from:...] [to:...] [flags:-1:1:-1:-1:0]
 [msg:72:0106246170706C69636174696F6E2F766E642E7761702E656D6E2B7762786D6C00AF


 898DA1C393030D6A008507036F6D615F656D6E407961686F6F2E65730005C305200711061201
 ] [udh:7:...]

 So far I have been able to separate the headers (010624 plus the next 36
 bytes) from the payload (which looks fine). However, I'm unable to decode
 the last bytes from my headers, more precisely: 0xAF 0x89 0x8D 0xA1 0xC3
 0x93.

 Has anyone experience on decoding such tokenised headers?

 Thanks in advance,


 Diego





 --
 Regards,

 Ady Wicaksono
 Email:
 ady.wicaksono at gmail.com
 http://adywicaksono.wordpress.com/

UNSUBSCRIBE

[admin]

UNSUBSCRIBE

Re: Where I can download the previous version of opensmppbox

[admin]

08.08.2012 18:31, Rene Kluwen пишет:


The error is self-explanatory:

Mallformed addr `TestSMSSender', alphanum length greater 11 chars.

Alpha sender addresses have a maximum length of 11 characters.

== Rene

*From:*admin [mailto:ad...@platbox.ru] **



Good time of day.

After last change, my opensmppbox is working. But after sendeing 2 or 3 
sms one after one, it crushes. :(
After that the kannel script runs opensmppbox again, usually after one 
minute.
At this time I have working PHP script, sending sms, it works correct 
with the other kannel server.

Here are the debug logs.


2012-08-11 15:41:46 [30830] [0] INFO: Added logfile 
`/var/log/kannel/opensmppbox.log' with level `1'.
2012-08-11 15:41:46 [30830] [0] WARNING: DLR: using default 'internal' 
for storage type.

2012-08-11 15:41:46 [30830] [0] INFO: DLR using storage type: internal
2012-08-11 15:41:46 [30830] [0] INFO: MYSQL: Connected to server at 
192.168.102.2.
2012-08-11 15:41:46 [30830] [0] INFO: MYSQL: server version 
5.1.63-0+squeeze1-log, client version 5.1.61.
2012-08-11 15:41:46 [30830] [0] INFO: MYSQL: Connected to server at 
192.168.102.2.
2012-08-11 15:41:46 [30830] [0] INFO: MYSQL: server version 
5.1.63-0+squeeze1-log, client version 5.1.61.
2012-08-11 15:41:46 [30830] [0] INFO: MYSQL: Connected to server at 
192.168.102.2.
2012-08-11 15:41:46 [30830] [0] INFO: MYSQL: server version 
5.1.63-0+squeeze1-log, client version 5.1.61.
2012-08-11 15:41:46 [30830] [0] INFO: MYSQL: Connected to server at 
192.168.102.2.
2012-08-11 15:41:46 [30830] [0] INFO: MYSQL: server version 
5.1.63-0+squeeze1-log, client version 5.1.61.
2012-08-11 15:41:46 [30830] [0] INFO: MYSQL: Connected to server at 
192.168.102.2.
2012-08-11 15:41:46 [30830] [0] INFO: MYSQL: server version 
5.1.63-0+squeeze1-log, client version 5.1.61.
2012-08-11 15:41:46 [30830] [0] INFO: opensmppbox DLR storage using 
type: mysql
2012-08-11 15:41:46 [30830] [0] INFO: Waiting for SMPP connections on 
port 13006.

2012-08-11 15:41:48 [30830] [1] INFO: Client connected from 1.1.1.1
2012-08-11 15:41:48 [30830] [1] INFO: Connected to bearerbox at 1.1.1.1 
port 13001.
2012-08-11 15:41:48 [30830] [1] ERROR: opensmppbox: bearerbox_to_smpp: 
thread starts  # the errors
2012-08-11 15:41:48 [30830] [2] ERROR: opensmppbox: smpp_to_bearerbox: 
thread starts  # the errors
2012-08-11 15:41:50 [30830] [2] ERROR: opensmppbox: smpp_to_bearerbox: 
thread terminates # the errors
2012-08-11 15:41:50 [30830] [1] ERROR: opensmppbox: bearerbox_to_smpp: 
thread terminates # the errors

2012-08-11 15:41:51 [30830] [0] INFO: No more waiting for SMPP connections.
2012-08-11 15:42:46 [30844] [0] INFO: Added logfile 
`/var/log/kannel/opensmppbox.log' with level `1'.   # restart by kannel 
service. After that I can send 2-3 sms, and it crashes again.


There are my config files

kannel.conf

group = core
admin-port = 13000
admin-password =
admin-deny-ip = *.*.*.*
admin-allow-ip = 127.0.0.1
smsbox-port = 13001
log-file = /var/log/kannel/bearerbox.log
log-level = 0
access-log = /var/log/kannel/kannel-access.log
#box-deny-ip = *.*.*.*
box-allow-ip = 0.0.0.0
dlr-storage = mysql
smsbox-max-pending = 100
sms-resend-retry = 20
sms-resend-freq = 180
#unified-prefix = ,+
ssl-server-cert-file=/home/aamst/commcert/cert.crt
ssl-server-key-file=/home/aamst/commcert/cert.key

group = mysql-connection
id = dlr
host = 192.168.102.2
username = sms
password =
database = smsbox
port = 3306
max-connections = 5

group = dlr-db
id = dlr
table = dlr
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 = boxcid

group = smsbox
bearerbox-host = 1.1.1.1
bearerbox-port = 13005
sendsms-port = 13131
sendsms-port-ssl = false
mo-recode = 1
sendsms-chars = 0123456789
reply-couldnotfetch = Service unavailable
log-file = /var/log/kannel/smsbox.log
log-level = 0

group = sendsms-user
username = example
password =
default-sender = platbox
user-deny-ip = 11.11.11.11
user-allow-ip = *.*.*.*
max-messages = 3
omit-empty = true
split-chars = |
concatenation = true

group = sendsms-user
username = user09
password =
default-sender = 09
user-deny-ip = 11.11.11.11
user-allow-ip = *.*.*.*
max-messages = 5
omit-empty = true
split-chars = |
concatenation = true
default-smsc = process

group = smsc
smsc = smpp
smsc-id = process
allowed-smsc-id = process
host = smpp3.test.ru
port = 
transceiver-mode = 1
smsc-username = test1
smsc-password =
system-type = NULL
source-addr-ton = 0x00
source-addr-npi = 0x00
dest-addr-ton = 0x00
dest-addr-npi = 0x00
reconnect-delay = 20
enquire-link-interval = 30
log-file = /var/log/kannel/smsc-operator-process.log
log-level = 0

group = sms-service
keyword = default
catch-all = true
accepted-smsc = process
text = Hello
max-messages = 5
concatenation = true
omit-empty = true
accept-x-kannel-headers = true



sqlbox.conf
group

Re: Where I can download the previous version of opensmppbox

[admin]

: 2147483652 = 0x8004
2012-08-11 16:51:19 [31043] [1] DEBUG:   command_status: 0 = 0x
2012-08-11 16:51:19 [31043] [1] DEBUG:   sequence_number: 2 = 0x0002
2012-08-11 16:51:19 [31043] [1] DEBUG:   message_id: f35e60b4
2012-08-11 16:51:19 [31043] [1] DEBUG: SMPP PDU dump ends.
2012-08-11 16:51:20 [31043] [2] DEBUG: SMPP[smpp3]: Got PDU:
2012-08-11 16:51:20 [31043] [2] DEBUG: SMPP PDU 0xa113670 dump:
2012-08-11 16:51:20 [31043] [2] DEBUG:   type_name: unbind
2012-08-11 16:51:20 [31043] [2] DEBUG:   command_id: 6 = 0x0006
2012-08-11 16:51:20 [31043] [2] DEBUG:   command_status: 0 = 0x
2012-08-11 16:51:20 [31043] [2] DEBUG:   sequence_number: 3 = 0x0003
2012-08-11 16:51:20 [31043] [2] DEBUG: SMPP PDU dump ends.
2012-08-11 16:51:20 [31043] [2] DEBUG: SMPP[smpp3]: Sending PDU:
2012-08-11 16:51:20 [31043] [2] DEBUG: SMPP PDU 0xa115328 dump:
2012-08-11 16:51:20 [31043] [2] DEBUG:   type_name: unbind_resp
2012-08-11 16:51:20 [31043] [2] DEBUG:   command_id: 2147483654 = 0x8006
2012-08-11 16:51:20 [31043] [2] DEBUG:   command_status: 0 = 0x
2012-08-11 16:51:20 [31043] [2] DEBUG:   sequence_number: 3 = 0x0003
2012-08-11 16:51:20 [31043] [2] DEBUG: SMPP PDU dump ends.
2012-08-11 16:51:20 [31043] [2] ERROR: opensmppbox: smpp_to_bearerbox: 
thread terminates  #same error
2012-08-11 16:51:20 [31043] [2] DEBUG: Thread 2 
(opensmppbox.c:smpp_to_bearerbox) terminates.
2012-08-11 16:51:20 [31043] [1] ERROR: opensmppbox: bearerbox_to_smpp: 
thread terminates  #same error
2012-08-11 16:51:20 [31043] [1] DEBUG: Thread 1 (opensmppbox.c:function) 
terminates.

2012-08-11 16:51:21 [31043] [0] INFO: No more waiting for SMPP connections.
2012-08-11 16:51:21 [31043] [0] DEBUG: Immutable octet strings: 125.
2012-08-11 16:51:56 [31060] [0] INFO: Added logfile 
`/var/log/kannel/opensmppbox.log' with level `0'.  #restart






11.08.2012 16:28, spameden пишет:

To identify a problem you need to use log-level = 0.

2012/8/11 admin ad...@platbox.ru mailto:ad...@platbox.ru

08.08.2012 18:31, Rene Kluwen пишет:


The error is self-explanatory:

Mallformed addr `TestSMSSender', alphanum length greater 11 chars.

Alpha sender addresses have a maximum length of 11 characters.

== Rene

*From:*admin [mailto:ad...@platbox.ru]



Good time of day.

After last change, my opensmppbox is working. But after sendeing 2
or 3 sms one after one, it crushes. :(
After that the kannel script runs opensmppbox again, usually after
one minute.
At this time I have working PHP script, sending sms, it works
correct with the other kannel server.
Here are the debug logs.


2012-08-11 15:41:46 [30830] [0] INFO: Added logfile
`/var/log/kannel/opensmppbox.log' with level `1'.
2012-08-11 15:41:46 [30830] [0] WARNING: DLR: using default
'internal' for storage type.
2012-08-11 15:41:46 [30830] [0] INFO: DLR using storage type: internal
2012-08-11 15:41:46 [30830] [0] INFO: MYSQL: Connected to server
at 192.168.102.2.
2012-08-11 15:41:46 [30830] [0] INFO: MYSQL: server version
5.1.63-0+squeeze1-log, client version 5.1.61.
2012-08-11 15:41:46 [30830] [0] INFO: MYSQL: Connected to server
at 192.168.102.2.
2012-08-11 15:41:46 [30830] [0] INFO: MYSQL: server version
5.1.63-0+squeeze1-log, client version 5.1.61.
2012-08-11 15:41:46 [30830] [0] INFO: MYSQL: Connected to server
at 192.168.102.2.
2012-08-11 15:41:46 [30830] [0] INFO: MYSQL: server version
5.1.63-0+squeeze1-log, client version 5.1.61.
2012-08-11 15:41:46 [30830] [0] INFO: MYSQL: Connected to server
at 192.168.102.2.
2012-08-11 15:41:46 [30830] [0] INFO: MYSQL: server version
5.1.63-0+squeeze1-log, client version 5.1.61.
2012-08-11 15:41:46 [30830] [0] INFO: MYSQL: Connected to server
at 192.168.102.2.
2012-08-11 15:41:46 [30830] [0] INFO: MYSQL: server version
5.1.63-0+squeeze1-log, client version 5.1.61.
2012-08-11 15:41:46 [30830] [0] INFO: opensmppbox DLR storage
using type: mysql
2012-08-11 15:41:46 [30830] [0] INFO: Waiting for SMPP connections
on port 13006.
2012-08-11 15:41:48 [30830] [1] INFO: Client connected from 1.1.1.1
2012-08-11 15:41:48 [30830] [1] INFO: Connected to bearerbox at
1.1.1.1 port 13001.
2012-08-11 15:41:48 [30830] [1] ERROR: opensmppbox:
bearerbox_to_smpp: thread starts  # the errors
2012-08-11 15:41:48 [30830] [2] ERROR: opensmppbox:
smpp_to_bearerbox: thread starts  # the errors
2012-08-11 15:41:50 [30830] [2] ERROR: opensmppbox:
smpp_to_bearerbox: thread terminates # the errors
2012-08-11 15:41:50 [30830] [1] ERROR: opensmppbox:
bearerbox_to_smpp: thread terminates # the errors
2012-08-11 15:41:51 [30830] [0] INFO: No more waiting for SMPP
connections.
2012-08-11 15:42:46 [30844] [0] INFO: Added logfile
`/var/log

Re: Where I can download the previous version of opensmppbox

[admin]

07.08.2012 17:35, spameden ?:
instead of rollbacking to previous revision, you can do what Rene said 
you need to alter opensmppbox.conf configuration and it would work.


2012/8/7 admin ad...@platbox.ru mailto:ad...@platbox.ru

Good time of day!

I have installed the last version of opensmppbox and have the bug
which is talked about here

https://redmine.kannel.org/issues/649

Where I can download the .63 version? There is no this bug in this
version as they wrote here.




Thank you for help.
Yes, i did it.
Now my opensmppbox can start.
But unfortunatelly I can't send sms by smpp, because get the errors:

 ERROR: opensmppbox: bearerbox_to_smpp: thread starts
 ERROR: opensmppbox: smpp_to_bearerbox: thread starts

Here are my config files:

kannel.conf

group = core
admin-port = 13000
admin-password =
admin-deny-ip = *.*.*.*
admin-allow-ip = 127.0.0.1
smsbox-port = 13001
log-file = /var/log/kannel/bearerbox.log
log-level = 0
access-log = /var/log/kannel/kannel-access.log
#box-deny-ip = *.*.*.*
box-allow-ip = 0.0.0.0
dlr-storage = mysql
smsbox-max-pending = 100
sms-resend-retry = 20
sms-resend-freq = 180
#unified-prefix = ,+
ssl-server-cert-file=/home/amst/commcert/cert.crt
ssl-server-key-file=/home/amst/commcert/cert.key

group = mysql-connection
id = dlr
host = 192.168.102.2
username = smsuser
password =
database = smsbox
port = 3306
max-connections = 5

group = dlr-db
id = dlr
table = dlr
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 = boxcid

group = smsbox
bearerbox-host = 1.1.1.1
bearerbox-port = 13005
sendsms-port = 13131
sendsms-port-ssl = false
mo-recode = 1
sendsms-chars = 0123456789
reply-couldnotfetch = Service unavailable
log-file = /var/log/kannel/smsbox.log
log-level = 0
group = sendsms-user
username = user_test
password =
default-sender = test
user-deny-ip = 1.1.1.2
user-allow-ip = *.*.*.*
max-messages = 5
omit-empty = true
split-chars = |
concatenation = true
default-smsc = process

group = smsc
smsc = smpp
smsc-id = process
allowed-smsc-id = process
host = 2.2.2.2
port = 888
transceiver-mode = 1
smsc-username = test
smsc-password =
system-type = NULL
source-addr-ton = 0x00
source-addr-npi = 0x00
dest-addr-ton = 0x00
dest-addr-npi = 0x00
reconnect-delay = 20
enquire-link-interval = 30
log-file = /var/log/kannel/smsc-operator-process.log
log-level = 0

group = sms-service
keyword = default
catch-all = true
accepted-smsc = process
text = Hello
max-messages = 5
concatenation = true
omit-empty = true
accept-x-kannel-headers = true


Here is smppbox.conf

group = core
#dlr-storage = mysql

# this group defines your opensmppbox
group = opensmppbox
box-dlr-storage = mysql
# our boxc type
opensmppbox-id = opensmppbox
# the port to listen on for smpp connections
opensmppbox-port = 13006
# we connect to the following host as a box
bearerbox-host = localhost
bearerbox-port = 13005
#bearerbox-dcs = utf-8
log-level = 1
log-file = /var/log/kannel/opensmppbox.log
our-system-id = platbox
route-to-smsc = process   # ?  ??? smsc-id  ,  ? 
 ??? kannel.conf

smpp-logins = /etc/opensmppbox/clients

# the following is just standard dlr configuration

group = mysql-connection
id = dlr
host = 192.168.2.2
username = smsuser
password =
database = smsbox
port = 3306
# you can increase this upon a higher load
max-connections = 5

group = dlr-db
id = dlr
table = dlr
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 = boxcid


Here is sqlbox.conf

group = sqlbox
id = sqlbox-db
smsbox-id = sqlbox
#global-sender = 
bearerbox-host = localhost
bearerbox-port = 13001
smsbox-port = 13005
smsbox-port-ssl = false
sql-log-table = sent_sms
sql-insert-table = send_sms
check-balance = 1
log-file = /var/log/kannel/kannel-sqlbox.log
log-level = 0
#access-log = /var/log/kannel/sqlaccess.log
#ssl-client-certkey-file = 
#ssl-server-cert-file = 
#ssl-server-key-file = 
#ssl-trusted-ca-file = 

# Database connection examples. Please uncomment as needed

# Example MYSQL Connection
group = mysql-connection
id = sqlbox-db
host = 192.168.2.2
username = smsuser
password =
database = smsbox
port = 3306
max-connections = 5


Here is the /etc/opensmppbox/clietnts
test Qwe123 localhost *.*.*.*
test2 Qwe1234 smpp2 *.*.*.*


Here is the peace of php check sms script
?php
define('SMPP_HOST_P', '1.1.1.1');
define('SMPP_LOGIN_P', 'test');
define('SMPP_PASSWORD_P', 'Qwe123');

define('SMPP_PORT', 13006);
define('SMPP_FROM', 'TestAddress');

class SMPP {

// ? ? SMPP
public $system_type = null;
public $interface_version = 0x34;



And here is the debug log by opensmppbox:

2012-08-08 15:23:17 [6805] [0] INFO: Starting to log to file 
/var/log/kannel/opensmppbox.l og level 1

Re: Where I can download the previous version of opensmppbox

[admin]

Changed system-type  from NULL to localhost in kannel.conf
The same error...

08.08.2012 16:15, Rene Kluwen пишет:


Specify localhost as system-type in your client.

== Rene

*From:*users-boun...@vm1.kannel.org 
[mailto:users-boun...@vm1.kannel.org] *On Behalf Of *admin

*Sent:* Wednesday, 08 August, 2012 13:34
*To:* spameden; us...@vm1.kannel.org
*Subject:* Re: Where I can download the previous version of opensmppbox

07.08.2012 17:35, spameden пишет:

instead of rollbacking to previous revision, you can do what Rene
said you need to alter opensmppbox.conf configuration and it would
work.

2012/8/7 admin ad...@platbox.ru mailto:ad...@platbox.ru

Good time of day!

I have installed the last version of opensmppbox and have the bug
which is talked about here

https://redmine.kannel.org/issues/649

Where I can download the .63 version? There is no this bug in this
version as they wrote here.


Thank you for help.
Yes, i did it.
Now my opensmppbox can start.
But unfortunatelly I can't send sms by smpp, because get the errors:

 ERROR: opensmppbox: bearerbox_to_smpp: thread starts
 ERROR: opensmppbox: smpp_to_bearerbox: thread starts

Here are my config files:

kannel.conf

group = core
admin-port = 13000
admin-password =
admin-deny-ip = *.*.*.*
admin-allow-ip = 127.0.0.1
smsbox-port = 13001
log-file = /var/log/kannel/bearerbox.log
log-level = 0
access-log = /var/log/kannel/kannel-access.log
#box-deny-ip = *.*.*.*
box-allow-ip = 0.0.0.0
dlr-storage = mysql
smsbox-max-pending = 100
sms-resend-retry = 20
sms-resend-freq = 180
#unified-prefix = ,+
ssl-server-cert-file=/home/amst/commcert/cert.crt
ssl-server-key-file=/home/amst/commcert/cert.key

group = mysql-connection
id = dlr
host = 192.168.102.2
username = smsuser
password =
database = smsbox
port = 3306
max-connections = 5

group = dlr-db
id = dlr
table = dlr
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 = boxcid

group = smsbox
bearerbox-host = 1.1.1.1
bearerbox-port = 13005
sendsms-port = 13131
sendsms-port-ssl = false
mo-recode = 1
sendsms-chars = 0123456789
reply-couldnotfetch = Service unavailable
log-file = /var/log/kannel/smsbox.log
log-level = 0
group = sendsms-user
username = user_test
password =
default-sender = test
user-deny-ip = 1.1.1.2
user-allow-ip = *.*.*.*
max-messages = 5
omit-empty = true
split-chars = |
concatenation = true
default-smsc = process

group = smsc
smsc = smpp
smsc-id = process
allowed-smsc-id = process
host = 2.2.2.2
port = 888
transceiver-mode = 1
smsc-username = test
smsc-password =
system-type = NULL
source-addr-ton = 0x00
source-addr-npi = 0x00
dest-addr-ton = 0x00
dest-addr-npi = 0x00
reconnect-delay = 20
enquire-link-interval = 30
log-file = /var/log/kannel/smsc-operator-process.log
log-level = 0

group = sms-service
keyword = default
catch-all = true
accepted-smsc = process
text = Hello
max-messages = 5
concatenation = true
omit-empty = true
accept-x-kannel-headers = true


Here is smppbox.conf

group = core
#dlr-storage = mysql

# this group defines your opensmppbox
group = opensmppbox
box-dlr-storage = mysql
# our boxc type
opensmppbox-id = opensmppbox
# the port to listen on for smpp connections
opensmppbox-port = 13006
# we connect to the following host as a box
bearerbox-host = localhost
bearerbox-port = 13005
#bearerbox-dcs = utf-8
log-level = 1
log-file = /var/log/kannel/opensmppbox.log
our-system-id = platbox
route-to-smsc = process   # здесь надо указать smsc-id  , прописанного 
в основном конфине kannel.conf

smpp-logins = /etc/opensmppbox/clients

# the following is just standard dlr configuration

group = mysql-connection
id = dlr
host = 192.168.2.2
username = smsuser
password =
database = smsbox
port = 3306
# you can increase this upon a higher load
max-connections = 5

group = dlr-db
id = dlr
table = dlr
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 = boxcid


Here is sqlbox.conf

group = sqlbox
id = sqlbox-db
smsbox-id = sqlbox
#global-sender = 
bearerbox-host = localhost
bearerbox-port = 13001
smsbox-port = 13005
smsbox-port-ssl = false
sql-log-table = sent_sms
sql-insert-table = send_sms
check-balance = 1
log-file = /var/log/kannel/kannel-sqlbox.log
log-level = 0
#access-log = /var/log/kannel/sqlaccess.log
#ssl-client-certkey-file = 
#ssl-server-cert-file = 
#ssl-server-key-file = 
#ssl-trusted-ca-file = 

# Database connection examples. Please uncomment as needed

# Example MYSQL Connection
group = mysql-connection
id = sqlbox-db
host = 192.168.2.2
username = smsuser
password =
database = smsbox
port = 3306
max-connections = 5


Here is the /etc/opensmppbox/clietnts
test Qwe123 localhost *.*.*.*
test2 Qwe1234 smpp2 *.*.*.*


Here is the peace of php check sms script
?php
define

Where I can download the previous version of opensmppbox

[admin]

Good time of day!

I have installed the last version of opensmppbox and have the bug which 
is talked about here


https://redmine.kannel.org/issues/649

Where I can download the .63 version? There is no this bug in this 
version as they wrote here.

can't install opensmppbox

[admin]

Good time of day.
I have the server with Debian 6 Squeeze, x64.
I downloaded the opensmppbox with the command
svn co https://svn.kannel.org/opensmppbox/trunk
and try to install it.
Configure was completed, but when i tried Make got this error:

make[2]: *** [opensmppbox] Ошибка 1
make[2]: Leaving directory `/home/amst/opensmpp/open2/trunk/gw'
make[1]: *** [all-recursive] Ошибка 1
make[1]: Leaving directory `/home/amst/opensmpp/open2/trunk'
make: *** [all] Ошибка 2

I have g++ and  libxml2-dev on my server.
Can you help me please?

Re: can't install opensmppbox

[admin]

06.08.2012 16:15, spameden пишет:
I don't need Makefile script, I need output generated by make command, 
not only the last lines.


2012/8/6 admin ad...@platbox.ru mailto:ad...@platbox.ru

06.08.2012 15:29, spameden пишет:

From the lines you posted I can't judge what's wrong. Paste line
before.

And yes you need to install kannel's development headers (i.e.
install kannel before compiling opensmppbox).

Read user-guide.

2012/8/6 admin ad...@platbox.ru mailto:ad...@platbox.ru

06.08.2012 15:08, spameden пишет:

Hello, you need to provide earlier lines of compilation.

2012/8/6 admin ad...@platbox.ru mailto:ad...@platbox.ru

Good time of day.
I have the server with Debian 6 Squeeze, x64.
I downloaded the opensmppbox with the command
svn co https://svn.kannel.org/opensmppbox/trunk
and try to install it.
Configure was completed, but when i tried Make got
this error:

make[2]: *** [opensmppbox] Ошибка 1
make[2]: Leaving directory
`/home/amst/opensmpp/open2/trunk/gw'
make[1]: *** [all-recursive] Ошибка 1
make[1]: Leaving directory `/home/amst/opensmpp/open2/trunk'
make: *** [all] Ошибка 2

I have g++ and  libxml2-dev on my server.
Can you help me please?



do you mean the lines
srcdir= .
topsrcdir = ..

Should i paste there the path, where opensmpp is ?




Of cource I have installed kannel, it works fine. And i read the
user-guide.

Here is my Makefile

srcdir = .
top_srcdir = ..

pkgdatadir = $(datadir)/
pkglibdir = $(libdir)/
pkgincludedir = $(includedir)/
top_builddir = ..
am__cd = CDPATH=$${ZSH_VERSION+.}$(PATH_SEPARATOR)  cd
INSTALL = /usr/bin/install -c
install_sh_DATA = $(install_sh) -c -m 644
install_sh_PROGRAM = $(install_sh) -c
install_{sh_SCRIPT = $(install_sh) -c
INSTALL_HEADER = $(INSTALL_DATA)
transform = $(program_transform_name)
NORMAL_INSTALL = :
PRE_INSTALL = :
POST_INSTALL = :
NORMAL_UNINSTALL = :
PRE_UNINSTALL = :
POST_UNINSTALL = :
build_triplet = x86_64-unknown-linux-gnu
host_triplet = x86_64-unknown-linux-gnu
sbin_PROGRAMS = opensmppbox$(EXEEXT)
subdir = gw
DIST_COMMON = $(srcdir)/Makefile.am $(srcdir)/Makefile.in
ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
am__aclocal_m4_deps = $(top_srcdir)/acinclude.m4 \
$(top_srcdir)/configure.in http://configure.in
am__configure_deps = $(am__aclocal_m4_deps)
$(CONFIGURE_DEPENDENCIES) \
$(ACLOCAL_M4)
mkinstalldirs = $(install_sh) -d
CONFIG_HEADER = $(top_builddir)/sb-config.h
CONFIG_CLEAN_FILES =
am__installdirs = $(DESTDIR)$(sbindir)
sbinPROGRAMS_INSTALL = $(INSTALL_PROGRAM)
PROGRAMS = $(sbin_PROGRAMS)
am_opensmppbox_OBJECTS = box-dlr.$(OBJEXT) opensmppbox.$(OBJEXT)
opensmppbox_OBJECTS = $(am_opensmppbox_OBJECTS)
opensmppbox_LDADD = $(LDADD)
DEFAULT_INCLUDES = -I. -I$(srcdir) -I$(top_builddir)
depcomp = $(SHELL) $(top_srcdir)/autotools/depcomp
am__depfiles_maybe = depfiles

{cutted}


It is standart Makefile script, i have not changed it.




ok, thank you for your help.

Here is the full make's output

make

/bin/bash ../libtool --tag=CC --mode=link gcc  -g -O2 
-D_XOPEN_SOURCE=600 -D_BSD_SOUR CE -I/usr/local/ssl/include 
-I/usr/local/include/kannel -g -O2 -D_XOPEN_SOURCE=600 -D _BSD_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_LARGE_FILES= -I/usr/include/libxml2 
-I/usr/incl ude -I/usr/include/mysql -I/usr/include/mysql  -rdynamic -o 
opensmppbox  box-dlr.o op ensmppbox.o  -lmysqlclient_r  
-L/usr/local/ssl/lib -lcrypto -L/usr/local/lib/kannel - lgw -lwap 
-lgwlib -lmysqlclient_r -lssl -lrt -lresolv -lnsl -lm -lpthread -lxml2 
-L/ usr/lib -lcrypto -lssl -rdynamic -L/usr/lib/mysql -lmysqlclient_r 
-rdynamic -L/usr/l ib/mysql -lmysqlclient_r
gcc -g -O2 -D_XOPEN_SOURCE=600 -D_BSD_SOURCE -I/usr/local/ssl/include 
-I/usr/local/in clude/kannel -g -O2 -D_XOPEN_SOURCE=600 -D_BSD_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_LARGE _FILES= -I/usr/include/libxml2 
-I/usr/include -I/usr/include/mysql -I/usr/include/mys ql -rdynamic -o 
opensmppbox box-dlr.o opensmppbox.o -rdynamic -rdynamic -L/usr/local 
/ssl/lib -L/usr/local/lib/kannel -lgw -lwap -lgwlib -lrt -lresolv 
/usr/lib/libxml2.so -L/usr/lib -lcrypto -lssl -L/usr/lib/mysql 
/usr/lib/libmysqlclient_r.so -lcrypt -lns l -lm -lpthread -lz

/usr/local/ssl/lib/libssl.a(t1_lib.o): In function `tls_decrypt_ticket':
t1_lib.c:(.text+0x8dc): undefined reference to `EVP_aes_128_cbc'
/usr/local/ssl/lib/libssl.a(t1_lib.o): In function `tls1_process_sigalgs':
t1_lib.c:(.text+0x2be9): undefined reference to `EVP_ecdsa'
t1_lib.c:(.text+0x2bfb): undefined reference to `EVP_dss1'
/usr/local/ssl/lib/libssl.a(t1_enc.o): In function 
`tls1_change_cipher_state':

t1_enc.c:(.text

Re: can't install opensmppbox

[admin]

06.08.2012 16:40, spameden пишет:

do you have a custom openssl compiled in /usr/local/lib?

try specifying ./configure --with-ssl=/usr/lib/ssl

2012/8/6 admin ad...@platbox.ru mailto:ad...@platbox.ru

06.08.2012 16:15, spameden пишет:

I don't need Makefile script, I need output generated by make
command, not only the last lines.

2012/8/6 admin ad...@platbox.ru mailto:ad...@platbox.ru

06.08.2012 15:29, spameden пишет:

From the lines you posted I can't judge what's wrong. Paste
line before.

And yes you need to install kannel's development headers
(i.e. install kannel before compiling opensmppbox).

Read user-guide.

2012/8/6 admin ad...@platbox.ru mailto:ad...@platbox.ru

06.08.2012 15:08, spameden пишет:

Hello, you need to provide earlier lines of compilation.

2012/8/6 admin ad...@platbox.ru mailto:ad...@platbox.ru

Good time of day.
I have the server with Debian 6 Squeeze, x64.
I downloaded the opensmppbox with the command
svn co https://svn.kannel.org/opensmppbox/trunk
and try to install it.
Configure was completed, but when i tried Make
got this error:

make[2]: *** [opensmppbox] Ошибка 1
make[2]: Leaving directory
`/home/amst/opensmpp/open2/trunk/gw'
make[1]: *** [all-recursive] Ошибка 1
make[1]: Leaving directory
`/home/amst/opensmpp/open2/trunk'
make: *** [all] Ошибка 2

I have g++ and  libxml2-dev on my server.
Can you help me please?



do you mean the lines
srcdir= .
topsrcdir = ..

Should i paste there the path, where opensmpp is ?




Of cource I have installed kannel, it works fine. And i read
the user-guide.

Here is my Makefile

srcdir = .
top_srcdir = ..

pkgdatadir = $(datadir)/
pkglibdir = $(libdir)/
pkgincludedir = $(includedir)/
top_builddir = ..
am__cd = CDPATH=$${ZSH_VERSION+.}$(PATH_SEPARATOR)  cd
INSTALL = /usr/bin/install -c
install_sh_DATA = $(install_sh) -c -m 644
install_sh_PROGRAM = $(install_sh) -c
install_{sh_SCRIPT = $(install_sh) -c
INSTALL_HEADER = $(INSTALL_DATA)
transform = $(program_transform_name)
NORMAL_INSTALL = :
PRE_INSTALL = :
POST_INSTALL = :
NORMAL_UNINSTALL = :
PRE_UNINSTALL = :
POST_UNINSTALL = :
build_triplet = x86_64-unknown-linux-gnu
host_triplet = x86_64-unknown-linux-gnu
sbin_PROGRAMS = opensmppbox$(EXEEXT)
subdir = gw
DIST_COMMON = $(srcdir)/Makefile.am $(srcdir)/Makefile.in
ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
am__aclocal_m4_deps = $(top_srcdir)/acinclude.m4 \
$(top_srcdir)/configure.in http://configure.in
am__configure_deps = $(am__aclocal_m4_deps)
$(CONFIGURE_DEPENDENCIES) \
$(ACLOCAL_M4)
mkinstalldirs = $(install_sh) -d
CONFIG_HEADER = $(top_builddir)/sb-config.h
CONFIG_CLEAN_FILES =
am__installdirs = $(DESTDIR)$(sbindir)
sbinPROGRAMS_INSTALL = $(INSTALL_PROGRAM)
PROGRAMS = $(sbin_PROGRAMS)
am_opensmppbox_OBJECTS = box-dlr.$(OBJEXT) opensmppbox.$(OBJEXT)
opensmppbox_OBJECTS = $(am_opensmppbox_OBJECTS)
opensmppbox_LDADD = $(LDADD)
DEFAULT_INCLUDES = -I. -I$(srcdir) -I$(top_builddir)
depcomp = $(SHELL) $(top_srcdir)/autotools/depcomp
am__depfiles_maybe = depfiles

{cutted}


It is standart Makefile script, i have not changed it.




ok, thank you for your help.

Here is the full make's output

make

/bin/bash ../libtool --tag=CC --mode=link gcc  -g -O2
-D_XOPEN_SOURCE=600 -D_BSD_SOUR CE -I/usr/local/ssl/include
-I/usr/local/include/kannel -g -O2 -D_XOPEN_SOURCE=600 -D
_BSD_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES=
-I/usr/include/libxml2 -I/usr/incl ude -I/usr/include/mysql
-I/usr/include/mysql  -rdynamic -o opensmppbox  box-dlr.o op
ensmppbox.o  -lmysqlclient_r  -L/usr/local/ssl/lib -lcrypto
-L/usr/local/lib/kannel - lgw -lwap -lgwlib -lmysqlclient_r -lssl
-lrt -lresolv -lnsl -lm  -lpthread -lxml2 -L/ usr/lib -lcrypto
-lssl -rdynamic -L/usr/lib/mysql -lmysqlclient_r  -rdynamic
-L/usr/l ib/mysql -lmysqlclient_r
gcc -g -O2 -D_XOPEN_SOURCE=600 -D_BSD_SOURCE
-I/usr/local/ssl/include -I/usr/local/in clude/kannel -g -O2
-D_XOPEN_SOURCE=600 -D_BSD_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGE
_FILES= -I/usr/include/libxml2 -I/usr/include -I/usr/include/mysql
-I/usr/include/mys ql -rdynamic -o opensmppbox box-dlr.o
opensmppbox.o -rdynamic -rdynamic -L/usr/local /ssl/lib

Problems using smsbox and bearerbox

[SSL Admin]

Hi, im having some problem configuring kannel with GSM modem, i have it 
installed on a debian etch server, version 1.4.1. 
The problems are:

- smsbox doesnt start automatically with bearerbox / wapbox
- When i start smsbox and try to send a SMS, i get a message that say that the 
SMS is qeued and will be sent later.

im using this config:

group = core
admin-port = 13000
smsbox-port = 13001
admin-password = 123
log-file = /var/log/kannel/kannel.log
log-level = 0
box-deny-ip = *.*.*.*
box-allow-ip = 127.0.0.1

group = smsc
smsc = at
modemtype = auto
device=/dev/ttyACM0
my-number = 584121231231
connect-allow-ip = 127.0.0.1
log-file = /var/log/kannel/modem.log
log-level = 0

group = smsbox
bearerbox-host = 127.0.0.1
sendsms-port = 13013
log-file = /var/log/kannel/smsbox.log
log-level = 0

group = sendsms-user
username = kanneluser
password = 123
concatenation= true
max-messages = 10

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

include = /etc/kannel/modems.conf

Re: Problems using smsbox and bearerbox

[SSL Admin]

Also, we have Kannel (v1.4.1) running on a Solaris 9 (on another server) and it 
start smsbox, bearerbox and wapbox together.

- Original Message - 
  From: Michael Sole 
  To: users@kannel.org 
  Sent: Friday, February 22, 2008 2:37 PM
  Subject: RE: Problems using smsbox and bearerbox


  I would also like to know why smsbox does not start automatically. Would seem 
like the desired default behavior.

   

  From: SSL Admin [mailto:[EMAIL PROTECTED] 
  Sent: Friday, February 22, 2008 11:58 AM
  To: users@kannel.org
  Subject: UNS: Problems using smsbox and bearerbox

   

  Hi, im having some problem configuring kannel with GSM modem, i have it 
installed on a debian etch server, version 1.4.1. 

  The problems are:

   

  - smsbox doesnt start automatically with bearerbox / wapbox

  - When i start smsbox and try to send a SMS, i get a message that say that 
the SMS is qeued and will be sent later.

   

  im using this config:

   

  group = core
  admin-port = 13000
  smsbox-port = 13001
  admin-password = 123
  log-file = /var/log/kannel/kannel.log
  log-level = 0
  box-deny-ip = *.*.*.*
  box-allow-ip = 127.0.0.1

   

  group = smsc
  smsc = at
  modemtype = auto
  device=/dev/ttyACM0
  my-number = 584121231231

  connect-allow-ip = 127.0.0.1
  log-file = /var/log/kannel/modem.log
  log-level = 0

   

  group = smsbox
  bearerbox-host = 127.0.0.1
  sendsms-port = 13013
  log-file = /var/log/kannel/smsbox.log
  log-level = 0

   

  group = sendsms-user
  username = kanneluser
  password = 123
  concatenation= true
  max-messages = 10

   

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

   

  include = /etc/kannel/modems.conf