DLR rerouting for smsc id disabled

[Web Min]

Hello,

I am unable  to receive DLR in Kannel using SMPP Connectivity.,

The log is showing when start binding , this INFO: DLR rerouting for smsc
id  disabled.

Any help would be appreciated

below are my configuration details

# CORE
group = core
admin-port = 13000
smsbox-port = 13001
wapbox-port = 13002
wdp-interface-name = "xx.xx.xx.xx"
admin-password = kannelpass
status-password = kannelpass
store-type = spool
store-location = /var/spool/kannel/store
dlr-storage = mysql
box-deny-ip = "*.*.*.*"
box-allow-ip = "127.0.0.1"
sms-resend-freq = 30
sms-resend-retry = 2
sms-incoming-queue-limit = "-1"
sms-outgoing-queue-limit = 999
smsbox-max-pending = 999
log-level=0
log-file = /var/log/kannel/core.log
access-log = /var/log/kannel/access-core.log
##
# DLR SETUP
group = mysql-connection
id = mydlr
host = localhost
port = 3306
username = root
password = kannelpass
database = kannel_db
max-connections = 25

# DLR TABLE STRUCTURE
group = dlr-db
id = mydlr
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=boxc

##
# SMSBOX
group = smsbox
bearerbox-host = localhost
bearerbox-port = 13001
sendsms-port = 13301
sendsms-chars = "0123456789+ "
mo-recode = true
http-request-retry = 10
http-queue-delay = 60
immediate-sendsms-reply = false
log-level = 0
log-file = /var/log/kannel/smsbox.log
access-log = /var/log/kannel/access-smsbox.log

##
# SENDSMS-USER
group = sendsms-user
default-smsc = mysmsc
forced-smsc = mysmsc
username = user
password = pass
max-messages = 1000
concatenation = true
#dlr-url="http://IPadress:port
/dlr.php?smscID=%i&user=&passwd=&type=%d&reply=%A&to=%p&receiver=%P&time=%t&smsID=%T&charset=%C&kannel_id=%I&message=%b"

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

##
# SMSC
group = smsc
smsc = smpp
smsc-id = mysmsc
allowed-smsc-id = mysmsc
preferred-smsc-id = mysmsc
interface-version = 34
allowed-prefix = xxx
host = xx.xx.xx.xx
port = 8899
receive-port = 0
transceiver-mode = 0
smsc-username = user
smsc-password = pass
system-type = VMA
source-addr-ton = 5
source-addr-npi = 1
dest-addr-ton = 0
dest-addr-npi = 0
keepalive = 600
reconnect-delay = 3
enquire-link-interval = 30
esm-class = 0
#max-pending-submits = 50
#throughput = 50
#wait-ack = 240
#wait-ack-expire = 0x00
msg-id-type = 0x01
log-level = 0
log-file = /var/log/kannel/smsc-transmitter.log

group = smsc
smsc = smpp
smsc-id = mysmsc
allowed-smsc-id = mysmsc
preferred-smsc-id = mysmsc
interface-version = 34
allowed-prefix = xxx
host = xx.xx.xx.xx
port = 0
receive-port = 8899
smsc-username = user
smsc-password = pass
system-type = VMA
source-addr-ton = 5
source-addr-npi = 1
dest-addr-ton = 0
dest-addr-npi = 0
keepalive = 600
reconnect-delay = 3
enquire-link-interval = 30
esm-class = 0
msg-id-type = 0x01
log-level = 0
log-file = /var/log/kannel/smsc-receiver.log

Re: TLS 1.2 support in kannel

[Web Min]

Hello,

In order to start with Ubuntu make sure the following packages are
installed:

apt-get install libmysqlclient-dev libmysqld-dev libxml2 libxml2-dev bison
byacc libssh-dev libssl-dev

Best Regards,

On Sat, Nov 3, 2018 at 1:51 AM info.ubichip  wrote:

> hello,
>
> I tried to reinstall a full clean machine with ubuntu 18.04 and last
> openssl
> 1.1.0g (nov 2017)
> and when I tried
> ./configure --enable-start-stop-daemon --with-mysql --enable-ssl --with-ssl
> I got error :
> Configuring OpenSSL support ...
> configure: error: Unable to find OpenSSL libs and/or directories at yes
>
> Does anyone got this error ?
>
> thanks in advance
>
>
> -Message d'origine-
> De : users [mailto:users-boun...@kannel.org] De la part de info.ubichip
> Envoyé : vendredi 2 novembre 2018 16:41
> À : users@kannel.org
> Objet : RE: TLS 1.2 support in kannel
>
> Hello,
>
> some update, I forgot to mention, I'm using kannel 1.4.5, and it has been
> seen the following errors as well in smsbox log :
>
> :SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure
>
> Does anyone have seen this issue so far ?
>
> thanks in advance for your help
>
> -Message d'origine-
> De : users [mailto:users-boun...@kannel.org] De la part de info.ubichip
> Envoyé : vendredi 2 novembre 2018 09:42
> À : users@kannel.org
> Objet : TLS 1.2 support in kannel
> Importance : Haute
>
> Hello,
>
> I have similar issue with SSL and kannel, in SMSBOX it appears the
> following
> errors :
>
> 2018-10-01 21:11:12 [3345] [8] ERROR: Couldn't fetch
> 
> 2018-10-01 21:11:32 [3345] [8] ERROR: SSL write failed: OpenSSL error 1:
> error:0001:lib(0):func(0):reason(1)
> 2018-10-01 21:11:32 [3345] [8] ERROR: SSL write failed: OpenSSL error 1:
> error:0001:lib(0):func(0):reason(1)
> 2018-10-01 21:11:32 [3345] [8] ERROR: SSL read failed: OpenSSL error 1:
> error:0001:lib(0):func(0):reason(1)
>
> It is related to the fact the web site drop TLS1 and TLS1.1 and is using
> only TLS 1.2 and up. Does someone got similar issue and how to resolve or
> patch it ?
>
> Thanks in advance for your help
>
>
>
>
>
>
>

Re: TLS 1.2 support in kannel

[Web Min]

I'm sorry for that, I don't have any experience with the SSL in Kannel.

Regards

On Sat, Nov 3, 2018 at 7:14 PM info.ubichip  wrote:

> the email was gone too fast :
>
>
>
> do you have any experience with the following added feature of the 1.4.5
> specially the one in red (le last one) ?
>
>
>
> * Added OpenSSL 1.1.x support.
>
>
>
>   * Added support for chained certificate files.
>
>
>
>   * Added support to define which SSL/TLS chipher suites to use.
>
>
>
> *De :* info.ubichip [mailto:info.ubic...@free.fr]
> *Envoyé :* samedi 3 novembre 2018 17:12
> *À :* 'Web Min'
> *Cc :* 'users@kannel.org'
> *Objet :* RE: TLS 1.2 support in kannel
>
>
>
> thanks,
>
>
>
> it working with
>
> ./configure --enable-start-stop-daemon --with-mysql --enable-ssl
>
>
>
> but not with :
>
>
>
> ./configure --enable-start-stop-daemon --with-mysql --enable-ssl --with-ssl
>
> Configuring OpenSSL support ...
> configure: error: Unable to find OpenSSL libs and/or directories at yes
>
>
>
> Do you ha
>
>
>
>
>
> *De :* Web Min [mailto:meweb...@gmail.com]
> *Envoyé :* samedi 3 novembre 2018 09:05
> *À :* info.ubic...@free.fr
> *Cc :* users@kannel.org
> *Objet :* Re: TLS 1.2 support in kannel
>
>
>
> Hello,
>
>
>
> In order to start with Ubuntu make sure the following packages are
> installed:
>
>
>
> apt-get install libmysqlclient-dev libmysqld-dev libxml2 libxml2-dev bison
> byacc libssh-dev libssl-dev
>
>
>
> Best Regards,
>
>
>
> On Sat, Nov 3, 2018 at 1:51 AM info.ubichip  wrote:
>
> hello,
>
> I tried to reinstall a full clean machine with ubuntu 18.04 and last
> openssl
> 1.1.0g (nov 2017)
> and when I tried
> ./configure --enable-start-stop-daemon --with-mysql --enable-ssl --with-ssl
> I got error :
> Configuring OpenSSL support ...
> configure: error: Unable to find OpenSSL libs and/or directories at yes
>
> Does anyone got this error ?
>
> thanks in advance
>
>
> -Message d'origine-
> De : users [mailto:users-boun...@kannel.org] De la part de info.ubichip
> Envoyé : vendredi 2 novembre 2018 16:41
> À : users@kannel.org
> Objet : RE: TLS 1.2 support in kannel
>
> Hello,
>
> some update, I forgot to mention, I'm using kannel 1.4.5, and it has been
> seen the following errors as well in smsbox log :
>
> :SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure
>
> Does anyone have seen this issue so far ?
>
> thanks in advance for your help
>
> -Message d'origine-
> De : users [mailto:users-boun...@kannel.org] De la part de info.ubichip
> Envoyé : vendredi 2 novembre 2018 09:42
> À : users@kannel.org
> Objet : TLS 1.2 support in kannel
> Importance : Haute
>
> Hello,
>
> I have similar issue with SSL and kannel, in SMSBOX it appears the
> following
> errors :
>
> 2018-10-01 21:11:12 [3345] [8] ERROR: Couldn't fetch
> <https://www.joe.com/input.php?from=%2B712341234>
> 2018-10-01 21:11:32 [3345] [8] ERROR: SSL write failed: OpenSSL error 1:
> error:0001:lib(0):func(0):reason(1)
> 2018-10-01 21:11:32 [3345] [8] ERROR: SSL write failed: OpenSSL error 1:
> error:0001:lib(0):func(0):reason(1)
> 2018-10-01 21:11:32 [3345] [8] ERROR: SSL read failed: OpenSSL error 1:
> error:0001:lib(0):func(0):reason(1)
>
> It is related to the fact the web site drop TLS1 and TLS1.1 and is using
> only TLS 1.2 and up. Does someone got similar issue and how to resolve or
> patch it ?
>
> Thanks in advance for your help
>
>
>
>
>

Re: INVALID SERVICE-TYPE KANNEL

[Web Min]

try the below smsc settings copy /paste from my kannel server

adjust it as you see fit

# SMSC
group = smsc
smsc = smpp
smsc-id = myid
allowed-smsc-id = myid
preferred-smsc-id = myid
interface-version = 34
host = xx.xx.xx.xx.
port = 
receive-port = 0
transceiver-mode = 0
smsc-username = user
smsc-password = pass
system-type = VMA
source-addr-ton = 5
source-addr-npi = 1
dest-addr-ton = 0
dest-addr-npi = 0
keepalive = 600
reconnect-delay = 3
enquire-link-interval = 30
esm-class = 0
#max-pending-submits = 50
#throughput = 50
#wait-ack = 240
#wait-ack-expire = 0x00
msg-id-type = 0x01
log-level = 0
log-file = /var/log/kannel/myid.log

On Mon, Nov 12, 2018 at 7:07 AM Rajesh Sahoo  wrote:

> *smsc-id = zoned  --> Issue is Here??*
>
> 2018-11-09 14:00:20 Receive DLR *[SMSC:airtel]* [SVC:] [ACT:] [BINF:]
> [FID:] [META:?smpp_resp?] [from:] [to:260976298808]
> [flags:-1:-1:-1:-1:16] [msg:36:NACK/0x0015/Invalid Service Type]
> [udh:0:]
>
> According to those above 2 things, I can say you used *smsc=airtel* but
> you should use *smsc=zoned*
>
> On Fri, Nov 9, 2018 at 6:06 PM christopher kamutumwa <
> chriskamutu...@gmail.com> wrote:
>
>> Hello,
>> I have an issue I have configured kannel and am able to bind to SMSC
>> provider. Not when I send message to SMSc Provider am getting an
>> error message in log as below
>> 2018-11-09 14:00:20 Receive DLR [SMSC:airtel] [SVC:] [ACT:] [BINF:]
>> [FID:] [META:?smpp_resp?] [from:] [to:260976298808]
>> [flags:-1:-1:-1:-1:16] [msg:36:NACK/0x0015/Invalid Service Type]
>> [udh:0:]
>>
>>
>> My question where is that put?
>>
>> I have asked SMSC provider and the have told me service-type=smpp
>>
>> I added to config file but still get same error
>>
>> TCPDUMP from smsc provider show they are receiving NOBAL as service type
>> from our end.
>> please help below is config
>>
>> group = smsc
>> smsc = smpp
>> smsc-id = zoned
>> host = 172.xx.xx.xx
>> port = 5xx
>> interface-version = 34
>> smsc-username = xx
>> smsc-password = xx
>> system-type = smpp
>> service-type = smpp
>> source-addr-ton = 5
>> source-addr-npi = 0
>> dest-addr-ton = 1
>> dest-addr-npi = 1
>> transceiver-mode = true
>> throughput = 40
>>
>>
>> Thanks
>>
>> Chris Kamutumwa
>>
>
>
> --
>
> *Regards,*
> *Rajesh Kumar Sahoo* | Designation: Technical Manager
> *Hand Phone:* +91-8884882772
>
>      
> *3m Digital Networks Pvt. Ltd.*
> Ph: 080-3007-2323 Extn:- 104
> *A2P Messaging l Voice & Cloud Telephony l Digital l Technology *
>
> *Our Offices:* Bengaluru l Hyderabad l Delhi l Bhubaneswar
>

Re: [PATCH] allow setting service-type for SMPP SMSC

[Web Min]

what is your smsc variables? in kannel.conf

On Mon, Nov 12, 2018 at 9:13 PM christopher kamutumwa <
chriskamutu...@gmail.com> wrote:

> hello,
> where can I find this patch I have noticed when service-type= smpp is put
> in config log shows NOBAL instead of smpp. hence getting error INVALID
> SERVICE_TYPE. does anyone have a patch to make it work. or a fix to this
> problem
>
> Thanks
>
> Chris
>

Re: [PATCH] allow setting service-type for SMPP SMSC

[Web Min]

try to match the below

# SMSC
group = smsc
smsc = smpp
smsc-id = myid
allowed-smsc-id = myid
preferred-smsc-id = myid
interface-version = 34
host = xx.xx.xx.xx.
port = 
receive-port = 0
transceiver-mode = 0
smsc-username = user
smsc-password = pass
system-type = VMA
source-addr-ton = 5
source-addr-npi = 1
dest-addr-ton = 0
dest-addr-npi = 0
keepalive = 600
reconnect-delay = 3
enquire-link-interval = 30
esm-class = 0
#max-pending-submits = 50
#throughput = 50
#wait-ack = 240
#wait-ack-expire = 0x00
msg-id-type = 0x01
log-level = 0
log-file = /var/log/kannel/myid.log

On Mon, Nov 12, 2018 at 9:47 PM christopher kamutumwa <
chriskamutu...@gmail.com> wrote:

> Below are variables and operator says the are ok; just the variable for
> service-type which is not parsing the correct variable
>
> group = smsc
> smsc = smpp
> smsc-id = zoned
> host = 172.xx.xx.xxx
> port = 5001
> interface-version = 34
> smsc-username = xx
> smsc-password = xx
> system-type = "smpp"
> service-type = smpp
> #allowed-prefix = 26097
> source-addr-ton = 5
> source-addr-npi = 0
> dest-addr-ton = 1
> dest-addr-npi = 1
> transceiver-mode = true
> throughput = 40
>
> Thanks in advance
>
> Chris
>
> On Mon, Nov 12, 2018 at 8:17 PM Web Min  wrote:
>
>> what is your smsc variables? in kannel.conf
>>
>> On Mon, Nov 12, 2018 at 9:13 PM christopher kamutumwa <
>> chriskamutu...@gmail.com> wrote:
>>
>>> hello,
>>> where can I find this patch I have noticed when service-type= smpp is
>>> put in config log shows NOBAL instead of smpp. hence getting error INVALID
>>> SERVICE_TYPE. does anyone have a patch to make it work. or a fix to this
>>> problem
>>>
>>> Thanks
>>>
>>> Chris
>>>
>>

Re: Kannel multiboxing.

[Web Min]

Hi, coinhosting

Can you guide us about the installation and preparation? I tried to use
SQLBOX before but I'm facing a lot of problems.

One more question, do you recommend to install & prepare the server via the
apt-get repositories or via compilation source code?

Regards

On Tue, Nov 27, 2018 at 3:50 PM Web Services  wrote:

> Hi,
>
> 2 servers is possible if you use kannel with sqlbox. on first server
> install kannel and sqlbox and on second server keep only for reporting.
> make a cron job script on second server which access sqlbox table
> (Remotely) and insert data in local DB
>
> we are using this method from last 2 years and works fine
>
> thanks
>
> Deepak
>
> On Tue, Nov 27, 2018 at 5:37 PM Davor Spasoski 
> wrote:
>
>> 1. Yes, just dedicate unique ports to your two instances of the boxes
>> 2. This is actually a very good question to which I don't have an answer.
>> It is certainly possible to instruct both instances to use the same DB,
>> typically used as a store and/or DLR repository, but I wonder how will
>> kannel handle the concurrency? Load balancing is usually brought on kannel
>> table in the context of balancing between SMS centers, not instances of
>> kannel. It's best if you try, and you would probably need to set same
>> smsc-ids, etc. I'm interested of the results.
>> If you wish to accomplish kannel redundancy another way is to  use
>> active/standby kannel, and I don't see a reason why wouldn't this work.
>>
>> BR,
>> Davor Spasoski
>>
>> one.Vip DOOEL Skopje | Ploshtad Presveta Bogorodica 1 | 1000 Skopje |
>> Macedonia
>> -Original Message-
>> From: users  On Behalf Of Gert Tamm
>> Sent: Tuesday, November 27, 2018 12:29 PM
>> To: users@kannel.org
>> Subject: Kannel multiboxing.
>>
>> Hello,
>>
>> I have question if you could multibox kannel in one computer?
>>
>> And how to set up 2 servers with one database to load balance the sending
>> of SMS?
>>
>> --
>> Tervitades/Best Wishes,
>> Gert Tamm
>> Süsteemiadministraator/System administrator
>> E-mail: g...@messenger.ee
>> Direct Messenger OÜ
>>
>>
>>
>> 
>>
>> Disclaimer: one.Vip DOOEL 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 DOOEL 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: Kannel multiboxing.

[Web Min]

As suggested Bavor, you can open multiple sessions as a transmitter (like 3
sessions) and one receiver to get the status back from the provider

On Wed, Nov 28, 2018 at 12:02 PM Davor Spasoski 
wrote:

> Hm, that could be for a number of reasons. If kannel is firing the
> submit_sm PDUs fast enough, check if you are getting any throttling errors?
> Also check the throughput to your SMSC.
> Alternatively, you can always multi-bind to the same SMSC using same
> smsc-id in your kannel config and kannel will load balance for you on the
> same instance.
>
> --Davor
>
> -Original Message-
> From: Gert Tamm 
> Sent: Wednesday, November 28, 2018 9:55 AM
> To: Davor Spasoski ; users@kannel.org
> Subject: Re: Kannel multiboxing.
>
> The reason I wanan try Load Balancing, is that our outgoing sms speed is
> slow when we send it maxes out (8.3x,5.xx,x.xx). How could I make it better?
>
>
> 11/27/2018 14:06 Davor Spasoski kirjutas:
> > 1. Yes, just dedicate unique ports to your two instances of the boxes
> > 2. This is actually a very good question to which I don't have an
> answer. It is certainly possible to instruct both instances to use the same
> DB, typically used as a store and/or DLR repository, but I wonder how will
> kannel handle the concurrency? Load balancing is usually brought on kannel
> table in the context of balancing between SMS centers, not instances of
> kannel. It's best if you try, and you would probably need to set same
> smsc-ids, etc. I'm interested of the results.
> > If you wish to accomplish kannel redundancy another way is to  use
> active/standby kannel, and I don't see a reason why wouldn't this work.
> >
> > BR,
> > Davor Spasoski
> >
> > one.Vip DOOEL Skopje | Ploshtad Presveta Bogorodica 1 | 1000 Skopje |
> Macedonia
> > -Original Message-
> > From: users  On Behalf Of Gert Tamm
> > Sent: Tuesday, November 27, 2018 12:29 PM
> > To: users@kannel.org
> > Subject: Kannel multiboxing.
> >
> > Hello,
> >
> > I have question if you could multibox kannel in one computer?
> >
> > And how to set up 2 servers with one database to load balance the
> sending of SMS?
> >
> > --
> > Tervitades/Best Wishes,
> > Gert Tamm
> > Süsteemiadministraator/System administrator
> > E-mail: g...@messenger.ee
> > Direct Messenger OÜ
> >
> >
> >
> > 
> >
> > Disclaimer: one.Vip DOOEL 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 DOOEL 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!
> >
> > Напомена: оне.Вип ДООЕЛ Скопје
> > Оваа електронска порака (вклучувајќи ги и прилозите) е доверлива и може
> да биде заштитена со правни привилегии. Доколку не сте лицето на кое таа му
> е наменета пораката, не треба да ја копирате, дистрибуирате или да ја
> откривате нејзината содржина, туку веднаш да ја препратите до испраќачот и
> да ја избришете оригиналната порака и сите нејзини копии од Вашиот
> компјутерски систем. Секое неовластено користење на оваа порака во целост
> или делови од истата е строго забрането. Ве молиме да забележите дека
> електронските пораки се подложни на промени. оне.Вип ДООЕЛ Скопје не
> презема одговорност за несоодветно или нецелосно пренесување на
> информациите содржани во оваа комуникација, ниту пак за било какво
> задоцнување на приемот или оштетувања на вашиот систем.
> > Ве молиме не ја печатете оваа порака освен ако не е неопходно! Зачувајте
> ја природата!
>
> --
> Tervitades/Best Wishes,
> Gert Tamm
> Süsteemiadministraator/System administrator
> E-mail: g...@messenger.ee
> Direct Messenger OÜ
>
>
> 
>
> Disclaimer: one.Vip DOOEL 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 DOOEL 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
> sa

Re: Kannel compil issue (config.status: error: cannot find input file: `Makefile.in')

[Web Min]

if you have kannel source then try first ./bootstrap.sh

Regards

On Thu, Nov 29, 2018 at 9:54 AM Bertrand Dupont 
wrote:

> Hi,
>
> Trying to make a fresh compil / installation of kannel on a new Centos 7
> and I've got the following error after launching ./configure :
>
> *config.status: error: cannot find input file: `Makefile.in'*
>
> If someone have an idea of what can cause this error ! I've try to deal
> with automake and autoconf but still get stuck with this error
> Thank you in advance for your help,
> Regards,
> Bertrand
>

Re: Kannel 1.4.5 migration

[Web Min]

It seems you have a problem in so file  as mentioned below

/lib64/libc.so.6

Did you install the Kannel via source? if yes make sure to run the
bootrtap.sh first

Regards

On Thu, Nov 29, 2018 at 10:41 PM Ron Rechtman 
wrote:

>
>
> Hello,
>
>
>
> I have 1.4.3 running no problem on Cent 6.6
>
>
> I have built a new box with Cent 7 and 1.4.5 and I cannot get it to run.
>
>
>
> I have installed Kannel, and used the same CONFIG from the 1.4.3 and get
> errors.
>
>
>
>
>
> 2018-11-29 14:27:51 [29716] [0] PANIC: Cannot start with SMSC connection
> failing
>
> 2018-11-29 14:27:51 [29716] [0] PANIC:
> /etc/kannel/sbin/bearerbox(gw_backtrace+0xae) [0x49840e]
>
> 2018-11-29 14:27:51 [29716] [0] PANIC:
> /etc/kannel/sbin/bearerbox(gw_panic+0x15f) [0x49857f]
>
> 2018-11-29 14:27:51 [29716] [0] PANIC:
> /etc/kannel/sbin/bearerbox(smsc2_start+0x5ee) [0x418eae]
>
> 2018-11-29 14:27:51 [29716] [0] PANIC:
> /etc/kannel/sbin/bearerbox(main+0xed4) [0x40d8f4]
>
> 2018-11-29 14:27:51 [29716] [0] PANIC:
> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f197d2de445]
>
> 2018-11-29 14:27:51 [29716] [0] PANIC: /etc/kannel/sbin/bearerbox()
> [0x40db86]
>
> 2018-11-29 14:28:51 [29738] [0] PANIC: Cannot start with SMSC connection
> failing
>
> 2018-11-29 14:28:51 [29738] [0] PANIC:
> /etc/kannel/sbin/bearerbox(gw_backtrace+0xae) [0x49840e]
>
> 2018-11-29 14:28:51 [29738] [0] PANIC:
> /etc/kannel/sbin/bearerbox(gw_panic+0x15f) [0x49857f]
>
> 2018-11-29 14:28:51 [29738] [0] PANIC:
> /etc/kannel/sbin/bearerbox(smsc2_start+0x5ee) [0x418eae]
>
> 2018-11-29 14:28:51 [29738] [0] PANIC:
> /etc/kannel/sbin/bearerbox(main+0xed4) [0x40d8f4]
>
> 2018-11-29 14:28:51 [29738] [0] PANIC:
> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7fd5d78e9445]
>
> 2018-11-29 14:28:51 [29738] [0] PANIC: /etc/kannel/sbin/bearerbox()
> [0x40db86]
>
>
>
> Some guidance would be appreciated.
>
>
>
> Thank you,
>
>
>
> Ron
>

Re: Kannel 1.4.5 migration

[Web Min]

49840e]
>
> 2018-11-29 15:15:43 [40483] [0] PANIC:
> /etc/kannel/sbin/bearerbox(gw_panic+0x15f) [0x49857f]
>
> 2018-11-29 15:15:43 [40483] [0] PANIC:
> /etc/kannel/sbin/bearerbox(smsc2_start+0x5ee) [0x418eae]
>
> 2018-11-29 15:15:43 [40483] [0] PANIC:
> /etc/kannel/sbin/bearerbox(main+0xed4) [0x40d8f4]
>
> 2018-11-29 15:15:43 [40483] [0] PANIC:
> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f03ded88445]
>
> 2018-11-29 15:15:43 [40483] [0] PANIC: /etc/kannel/sbin/bearerbox()
> [0x40db86]
>
> 2018-11-29 15:15:53 [40498] [0] PANIC: Cannot start with SMSC connection
> failing
>
> 2018-11-29 15:15:53 [40498] [0] PANIC:
> /etc/kannel/sbin/bearerbox(gw_backtrace+0xae) [0x49840e]
>
> 2018-11-29 15:15:53 [40498] [0] PANIC:
> /etc/kannel/sbin/bearerbox(gw_panic+0x15f) [0x49857f]
>
> 2018-11-29 15:15:53 [40498] [0] PANIC:
> /etc/kannel/sbin/bearerbox(smsc2_start+0x5ee) [0x418eae]
>
> 2018-11-29 15:15:53 [40498] [0] PANIC:
> /etc/kannel/sbin/bearerbox(main+0xed4) [0x40d8f4]
>
> 2018-11-29 15:15:53 [40498] [0] PANIC:
> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7efeafc29445]
>
> 2018-11-29 15:15:53 [40498] [0] PANIC: /etc/kannel/sbin/bearerbox()
> [0x40db86]
>
>
>
> *From:* Web Min 
> *Sent:* Thursday, November 29, 2018 2:44 PM
> *To:* Ron Rechtman 
> *Cc:* users@kannel.org
> *Subject:* Re: Kannel 1.4.5 migration
>
>
>
> It seems you have a problem in so file  as mentioned below
>
>
>
> /lib64/libc.so.6
>
>
>
> Did you install the Kannel via source? if yes make sure to run the
> bootrtap.sh first
>
>
>
> Regards
>
>
>
> On Thu, Nov 29, 2018 at 10:41 PM Ron Rechtman 
> wrote:
>
>
>
> Hello,
>
>
>
> I have 1.4.3 running no problem on Cent 6.6
>
>
> I have built a new box with Cent 7 and 1.4.5 and I cannot get it to run.
>
>
>
> I have installed Kannel, and used the same CONFIG from the 1.4.3 and get
> errors.
>
>
>
>
>
> 2018-11-29 14:27:51 [29716] [0] PANIC: Cannot start with SMSC connection
> failing
>
> 2018-11-29 14:27:51 [29716] [0] PANIC:
> /etc/kannel/sbin/bearerbox(gw_backtrace+0xae) [0x49840e]
>
> 2018-11-29 14:27:51 [29716] [0] PANIC:
> /etc/kannel/sbin/bearerbox(gw_panic+0x15f) [0x49857f]
>
> 2018-11-29 14:27:51 [29716] [0] PANIC:
> /etc/kannel/sbin/bearerbox(smsc2_start+0x5ee) [0x418eae]
>
> 2018-11-29 14:27:51 [29716] [0] PANIC:
> /etc/kannel/sbin/bearerbox(main+0xed4) [0x40d8f4]
>
> 2018-11-29 14:27:51 [29716] [0] PANIC:
> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f197d2de445]
>
> 2018-11-29 14:27:51 [29716] [0] PANIC: /etc/kannel/sbin/bearerbox()
> [0x40db86]
>
> 2018-11-29 14:28:51 [29738] [0] PANIC: Cannot start with SMSC connection
> failing
>
> 2018-11-29 14:28:51 [29738] [0] PANIC:
> /etc/kannel/sbin/bearerbox(gw_backtrace+0xae) [0x49840e]
>
> 2018-11-29 14:28:51 [29738] [0] PANIC:
> /etc/kannel/sbin/bearerbox(gw_panic+0x15f) [0x49857f]
>
> 2018-11-29 14:28:51 [29738] [0] PANIC:
> /etc/kannel/sbin/bearerbox(smsc2_start+0x5ee) [0x418eae]
>
> 2018-11-29 14:28:51 [29738] [0] PANIC:
> /etc/kannel/sbin/bearerbox(main+0xed4) [0x40d8f4]
>
> 2018-11-29 14:28:51 [29738] [0] PANIC:
> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7fd5d78e9445]
>
> 2018-11-29 14:28:51 [29738] [0] PANIC: /etc/kannel/sbin/bearerbox()
> [0x40db86]
>
>
>
> Some guidance would be appreciated.
>
>
>
> Thank you,
>
>
>
> Ron
>
>

Re: Kannel 1.4.5 migration

[Web Min]

Glad to hear it! What is the full log of installation?

On Thu, Nov 29, 2018 at 11:26 PM Ron Rechtman 
wrote:

> First off thanks for the super fast replies.
>
>
>
> The bootstrap didn’t give errors now
>
> But ended up with the same error
>
>
>
>
>
>
>
>
>
> *From:* Web Min 
> *Sent:* Thursday, November 29, 2018 3:21 PM
> *To:* Ron Rechtman 
> *Cc:* users@kannel.org
> *Subject:* Re: Kannel 1.4.5 migration
>
>
>
> try the below first
>
>
>
> mv configure.in configure.ac
>
> ./bootstrap
>
>
>
> then make
>
> make install
>
>
>
> On Thu, Nov 29, 2018 at 11:17 PM Ron Rechtman 
> wrote:
>
> I followed instructions
>
> https://blog.onesconsultants.com/2018/08/how-to-install-kannel-in-centos-7.html
>
> But pulling 1.4.5
>
> Applied patch
>
> https://redmine.kannel.org/issues/699
>
>
>
> & my config file
>
>
>
> I ran the .sh file, but guessing the earlier make install broke it?
>
>
>
> [root@sms-2 gateway-1.4.5]# ./bootstrap.sh
>
> + export WANT_AUTOMAKE=1.8
>
> + WANT_AUTOMAKE=1.8
>
> ++ which glibtoolize
>
> which: no glibtoolize in
> (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin)
>
> + libtoolize --copy --automake --force
>
> + aclocal
>
> aclocal: warning: autoconf input should be named 'configure.ac', not '
> configure.in'
>
> + autoheader
>
> autoheader: warning: missing template: ENABLE_COOKIES
>
> autoheader: Use AC_DEFINE([ENABLE_COOKIES], [], [Description])
>
> autoheader: warning: missing template: GW_NAME
>
> autoheader: warning: missing template: GW_VERSION
>
> autoheader: warning: missing template: HAVE_CASS
>
> autoheader: warning: missing template: HAVE_FUNC_GETHOSTBYNAME_R_3
>
> autoheader: warning: missing template: HAVE_FUNC_GETHOSTBYNAME_R_5
>
> autoheader: warning: missing template: HAVE_FUNC_GETHOSTBYNAME_R_6
>
> autoheader: warning: missing template: HAVE_GSOAP
>
> autoheader: warning: missing template: HAVE_MYSQL
>
> autoheader: warning: missing template: HAVE_NFTW
>
> autoheader: warning: missing template: HAVE_PCRE
>
> autoheader: warning: missing template: HAVE_PGSQL
>
> autoheader: warning: missing template: HAVE_PTHREAD_RWLOCK
>
> autoheader: warning: missing template: HAVE_PTHREAD_SPINLOCK_T
>
> autoheader: warning: missing template: HAVE_REDIS
>
> autoheader: warning: missing template: HAVE_REGEX
>
> autoheader: warning: missing template: HAVE_SDB
>
> autoheader: warning: missing template: HAVE_SEMAPHORE
>
> autoheader: warning: missing template: HAVE_SQLITE
>
> autoheader: warning: missing template: HAVE_SQLITE3
>
> autoheader: warning: missing template: HAVE_UCONTEXT
>
> autoheader: warning: missing template: HAVE_WTLS_OPENSSL
>
> autoheader: warning: missing template: HAVE___FUNCTION__
>
> autoheader: warning: missing template: HAVE___FUNC__
>
> autoheader: warning: missing template: LIBPCRE_VERSION
>
> autoheader: warning: missing template: LIBSDB_VERSION
>
> autoheader: warning: missing template: LOG_TIMESTAMP_LOCALTIME
>
> autoheader: warning: missing template: MUTEX_STATS
>
> autoheader: warning: missing template: NO_GWASSERT
>
> autoheader: warning: missing template: NO_SMS
>
> autoheader: warning: missing template: NO_WAP
>
> autoheader: warning: missing template: SUFFIX
>
> autoheader: warning: missing template: USE_GWMEM_CHECK
>
> autoheader: warning: missing template: USE_GWMEM_NATIVE
>
> autoheader: warning: missing template: USE_GWMEM_SLOW
>
> autoheader: warning: missing template: USE_KEEPALIVE
>
> autoheader: warning: missing template: WS_DEBUG
>
> + automake --add-missing --copy --gnu
>
> automake: warning: autoconf input should be named 'configure.ac', not '
> configure.in'
>
> configure.in:89: warning: AM_INIT_AUTOMAKE: two- and three-arguments
> forms are deprecated.  For more info, see:
>
> configure.in:89:
> http://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_005fINIT_005fAUTOMAKE-invocation
>
> automake: warning: autoconf input should be named 'configure.ac', not '
> configure.in'
>
> + autoconf
>
>
>
> So I decided to try again
>
> Deleted everything
>
>
>
> Sudo wget http://www.kannel.org/download/1.4.5/gateway-1.4.5.tar.gz
>
> sudo tar -zxvf gateway-1.4.5.tar.gz
>
>
>
> and had the same warnings as above
>
>
>
> sudo ./configure  --prefix=/etc/kannel --enable-start-stop-daemon
>
> sudo make gives error…
>
>
>
> sudo make clean
>
> apply patch from https://redmine.

Re: Kannel 1.4.5 migration

[Web Min]

I don't have much experience with kannel under CentOS, but my experience
under Ubuntu.

try check the automake version to match it with bootstrap
automake --version | sed -e '1s/[^0-9]*//' -e q


On Thu, Nov 29, 2018 at 11:30 PM Ron Rechtman 
wrote:

>
>
>
>
> *From:* Web Min 
> *Sent:* Thursday, November 29, 2018 3:29 PM
> *To:* Ron Rechtman 
> *Cc:* users@kannel.org
> *Subject:* Re: Kannel 1.4.5 migration
>
>
>
> Glad to hear it! What is the full log of installation?
>
>
>
> On Thu, Nov 29, 2018 at 11:26 PM Ron Rechtman 
> wrote:
>
> First off thanks for the super fast replies.
>
>
>
> The bootstrap didn’t give errors now
>
> But ended up with the same error
>
>
>
>
>
>
>
>
>
> *From:* Web Min 
> *Sent:* Thursday, November 29, 2018 3:21 PM
> *To:* Ron Rechtman 
> *Cc:* users@kannel.org
> *Subject:* Re: Kannel 1.4.5 migration
>
>
>
> try the below first
>
>
>
> mv configure.in configure.ac
>
> ./bootstrap
>
>
>
> then make
>
> make install
>
>
>
> On Thu, Nov 29, 2018 at 11:17 PM Ron Rechtman 
> wrote:
>
> I followed instructions
>
> https://blog.onesconsultants.com/2018/08/how-to-install-kannel-in-centos-7.html
>
> But pulling 1.4.5
>
> Applied patch
>
> https://redmine.kannel.org/issues/699
>
>
>
> & my config file
>
>
>
> I ran the .sh file, but guessing the earlier make install broke it?
>
>
>
> [root@sms-2 gateway-1.4.5]# ./bootstrap.sh
>
> + export WANT_AUTOMAKE=1.8
>
> + WANT_AUTOMAKE=1.8
>
> ++ which glibtoolize
>
> which: no glibtoolize in
> (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin)
>
> + libtoolize --copy --automake --force
>
> + aclocal
>
> aclocal: warning: autoconf input should be named 'configure.ac', not '
> configure.in'
>
> + autoheader
>
> autoheader: warning: missing template: ENABLE_COOKIES
>
> autoheader: Use AC_DEFINE([ENABLE_COOKIES], [], [Description])
>
> autoheader: warning: missing template: GW_NAME
>
> autoheader: warning: missing template: GW_VERSION
>
> autoheader: warning: missing template: HAVE_CASS
>
> autoheader: warning: missing template: HAVE_FUNC_GETHOSTBYNAME_R_3
>
> autoheader: warning: missing template: HAVE_FUNC_GETHOSTBYNAME_R_5
>
> autoheader: warning: missing template: HAVE_FUNC_GETHOSTBYNAME_R_6
>
> autoheader: warning: missing template: HAVE_GSOAP
>
> autoheader: warning: missing template: HAVE_MYSQL
>
> autoheader: warning: missing template: HAVE_NFTW
>
> autoheader: warning: missing template: HAVE_PCRE
>
> autoheader: warning: missing template: HAVE_PGSQL
>
> autoheader: warning: missing template: HAVE_PTHREAD_RWLOCK
>
> autoheader: warning: missing template: HAVE_PTHREAD_SPINLOCK_T
>
> autoheader: warning: missing template: HAVE_REDIS
>
> autoheader: warning: missing template: HAVE_REGEX
>
> autoheader: warning: missing template: HAVE_SDB
>
> autoheader: warning: missing template: HAVE_SEMAPHORE
>
> autoheader: warning: missing template: HAVE_SQLITE
>
> autoheader: warning: missing template: HAVE_SQLITE3
>
> autoheader: warning: missing template: HAVE_UCONTEXT
>
> autoheader: warning: missing template: HAVE_WTLS_OPENSSL
>
> autoheader: warning: missing template: HAVE___FUNCTION__
>
> autoheader: warning: missing template: HAVE___FUNC__
>
> autoheader: warning: missing template: LIBPCRE_VERSION
>
> autoheader: warning: missing template: LIBSDB_VERSION
>
> autoheader: warning: missing template: LOG_TIMESTAMP_LOCALTIME
>
> autoheader: warning: missing template: MUTEX_STATS
>
> autoheader: warning: missing template: NO_GWASSERT
>
> autoheader: warning: missing template: NO_SMS
>
> autoheader: warning: missing template: NO_WAP
>
> autoheader: warning: missing template: SUFFIX
>
> autoheader: warning: missing template: USE_GWMEM_CHECK
>
> autoheader: warning: missing template: USE_GWMEM_NATIVE
>
> autoheader: warning: missing template: USE_GWMEM_SLOW
>
> autoheader: warning: missing template: USE_KEEPALIVE
>
> autoheader: warning: missing template: WS_DEBUG
>
> + automake --add-missing --copy --gnu
>
> automake: warning: autoconf input should be named 'configure.ac', not '
> configure.in'
>
> configure.in:89: warning: AM_INIT_AUTOMAKE: two- and three-arguments
> forms are deprecated.  For more info, see:
>
> configure.in:89:
> http://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_005fINIT_005fAUTOMAKE-invocation
>
> automake: warning: autoconf input should be named 'configure.ac', not '
&

Re: Kannel 1.4.5 migration

[Web Min]

Better to update the version of Automake via the bootstrap file instead

On Thu, Nov 29, 2018 at 11:51 PM Ron Rechtman 
wrote:

> I left C/linux in 2000 when I got my Comp Eng. Degree.
>
> After that it has been mostly Microsoft & moved to C#.
>
>
>
> So you’ll have to be a bit patient with me
>
>
>
> Automake = 1.13.4
>
>
>
> So I tried edited the config.ac file…
>
> Seems quite a bit of changes in the INIT need to be done.
>
>
>
> Better Ideas?
>
>
>
>
>
> *From:* Web Min 
> *Sent:* Thursday, November 29, 2018 3:36 PM
> *To:* Ron Rechtman 
> *Cc:* users@kannel.org
> *Subject:* Re: Kannel 1.4.5 migration
>
>
>
> I don't have much experience with kannel under CentOS, but my experience
> under Ubuntu.
>
>
>
> try check the automake version to match it with bootstrap
>
> automake --version | sed -e '1s/[^0-9]*//' -e q
>
>
>
>
>
> On Thu, Nov 29, 2018 at 11:30 PM Ron Rechtman 
> wrote:
>
>
>
>
>
> *From:* Web Min 
> *Sent:* Thursday, November 29, 2018 3:29 PM
> *To:* Ron Rechtman 
> *Cc:* users@kannel.org
> *Subject:* Re: Kannel 1.4.5 migration
>
>
>
> Glad to hear it! What is the full log of installation?
>
>
>
> On Thu, Nov 29, 2018 at 11:26 PM Ron Rechtman 
> wrote:
>
> First off thanks for the super fast replies.
>
>
>
> The bootstrap didn’t give errors now
>
> But ended up with the same error
>
>
>
>
>
>
>
>
>
> *From:* Web Min 
> *Sent:* Thursday, November 29, 2018 3:21 PM
> *To:* Ron Rechtman 
> *Cc:* users@kannel.org
> *Subject:* Re: Kannel 1.4.5 migration
>
>
>
> try the below first
>
>
>
> mv configure.in configure.ac
>
> ./bootstrap
>
>
>
> then make
>
> make install
>
>
>
> On Thu, Nov 29, 2018 at 11:17 PM Ron Rechtman 
> wrote:
>
> I followed instructions
>
> https://blog.onesconsultants.com/2018/08/how-to-install-kannel-in-centos-7.html
>
> But pulling 1.4.5
>
> Applied patch
>
> https://redmine.kannel.org/issues/699
>
>
>
> & my config file
>
>
>
> I ran the .sh file, but guessing the earlier make install broke it?
>
>
>
> [root@sms-2 gateway-1.4.5]# ./bootstrap.sh
>
> + export WANT_AUTOMAKE=1.8
>
> + WANT_AUTOMAKE=1.8
>
> ++ which glibtoolize
>
> which: no glibtoolize in
> (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin)
>
> + libtoolize --copy --automake --force
>
> + aclocal
>
> aclocal: warning: autoconf input should be named 'configure.ac', not '
> configure.in'
>
> + autoheader
>
> autoheader: warning: missing template: ENABLE_COOKIES
>
> autoheader: Use AC_DEFINE([ENABLE_COOKIES], [], [Description])
>
> autoheader: warning: missing template: GW_NAME
>
> autoheader: warning: missing template: GW_VERSION
>
> autoheader: warning: missing template: HAVE_CASS
>
> autoheader: warning: missing template: HAVE_FUNC_GETHOSTBYNAME_R_3
>
> autoheader: warning: missing template: HAVE_FUNC_GETHOSTBYNAME_R_5
>
> autoheader: warning: missing template: HAVE_FUNC_GETHOSTBYNAME_R_6
>
> autoheader: warning: missing template: HAVE_GSOAP
>
> autoheader: warning: missing template: HAVE_MYSQL
>
> autoheader: warning: missing template: HAVE_NFTW
>
> autoheader: warning: missing template: HAVE_PCRE
>
> autoheader: warning: missing template: HAVE_PGSQL
>
> autoheader: warning: missing template: HAVE_PTHREAD_RWLOCK
>
> autoheader: warning: missing template: HAVE_PTHREAD_SPINLOCK_T
>
> autoheader: warning: missing template: HAVE_REDIS
>
> autoheader: warning: missing template: HAVE_REGEX
>
> autoheader: warning: missing template: HAVE_SDB
>
> autoheader: warning: missing template: HAVE_SEMAPHORE
>
> autoheader: warning: missing template: HAVE_SQLITE
>
> autoheader: warning: missing template: HAVE_SQLITE3
>
> autoheader: warning: missing template: HAVE_UCONTEXT
>
> autoheader: warning: missing template: HAVE_WTLS_OPENSSL
>
> autoheader: warning: missing template: HAVE___FUNCTION__
>
> autoheader: warning: missing template: HAVE___FUNC__
>
> autoheader: warning: missing template: LIBPCRE_VERSION
>
> autoheader: warning: missing template: LIBSDB_VERSION
>
> autoheader: warning: missing template: LOG_TIMESTAMP_LOCALTIME
>
> autoheader: warning: missing template: MUTEX_STATS
>
> autoheader: warning: missing template: NO_GWASSERT
>
> autoheader: warning: missing template: NO_SMS
>
> autoheader: warning: missing template: NO_WAP
>
> autoheader: warning: missing template: SUFFIX
>
> autoheader: warning: missing templ

Re: Kannel 1.4.5 migration

[Web Min]

try to follow the below link:

http://www.sabinshrestha.com.np/linux-downloads/centos-7-kannel-1-4-5-and-mariadb-10-3-install-and-configure-2018/

Good night

On Thu, Nov 29, 2018 at 11:56 PM Ron Rechtman 
wrote:

> I don’t follow
>
> export WANT_AUTOMAKE=1.8
>
> change to
>
> export WANT_AUTOMAKE=1.13.4
>
> ?
>
>
>
> I still end up with the same errors
>
>
>
>
>
>
>
>
>
> *From:* Web Min 
> *Sent:* Thursday, November 29, 2018 3:55 PM
> *To:* Ron Rechtman 
> *Cc:* users@kannel.org
> *Subject:* Re: Kannel 1.4.5 migration
>
>
>
> Better to update the version of Automake via the bootstrap file instead
>
>
>
> On Thu, Nov 29, 2018 at 11:51 PM Ron Rechtman 
> wrote:
>
> I left C/linux in 2000 when I got my Comp Eng. Degree.
>
> After that it has been mostly Microsoft & moved to C#.
>
>
>
> So you’ll have to be a bit patient with me
>
>
>
> Automake = 1.13.4
>
>
>
> So I tried edited the config.ac file…
>
> Seems quite a bit of changes in the INIT need to be done.
>
>
>
> Better Ideas?
>
>
>
>
>
> *From:* Web Min 
> *Sent:* Thursday, November 29, 2018 3:36 PM
> *To:* Ron Rechtman 
> *Cc:* users@kannel.org
> *Subject:* Re: Kannel 1.4.5 migration
>
>
>
> I don't have much experience with kannel under CentOS, but my experience
> under Ubuntu.
>
>
>
> try check the automake version to match it with bootstrap
>
> automake --version | sed -e '1s/[^0-9]*//' -e q
>
>
>
>
>
> On Thu, Nov 29, 2018 at 11:30 PM Ron Rechtman 
> wrote:
>
>
>
>
>
> *From:* Web Min 
> *Sent:* Thursday, November 29, 2018 3:29 PM
> *To:* Ron Rechtman 
> *Cc:* users@kannel.org
> *Subject:* Re: Kannel 1.4.5 migration
>
>
>
> Glad to hear it! What is the full log of installation?
>
>
>
> On Thu, Nov 29, 2018 at 11:26 PM Ron Rechtman 
> wrote:
>
> First off thanks for the super fast replies.
>
>
>
> The bootstrap didn’t give errors now
>
> But ended up with the same error
>
>
>
>
>
>
>
>
>
> *From:* Web Min 
> *Sent:* Thursday, November 29, 2018 3:21 PM
> *To:* Ron Rechtman 
> *Cc:* users@kannel.org
> *Subject:* Re: Kannel 1.4.5 migration
>
>
>
> try the below first
>
>
>
> mv configure.in configure.ac
>
> ./bootstrap
>
>
>
> then make
>
> make install
>
>
>
> On Thu, Nov 29, 2018 at 11:17 PM Ron Rechtman 
> wrote:
>
> I followed instructions
>
> https://blog.onesconsultants.com/2018/08/how-to-install-kannel-in-centos-7.html
>
> But pulling 1.4.5
>
> Applied patch
>
> https://redmine.kannel.org/issues/699
>
>
>
> & my config file
>
>
>
> I ran the .sh file, but guessing the earlier make install broke it?
>
>
>
> [root@sms-2 gateway-1.4.5]# ./bootstrap.sh
>
> + export WANT_AUTOMAKE=1.8
>
> + WANT_AUTOMAKE=1.8
>
> ++ which glibtoolize
>
> which: no glibtoolize in
> (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin)
>
> + libtoolize --copy --automake --force
>
> + aclocal
>
> aclocal: warning: autoconf input should be named 'configure.ac', not '
> configure.in'
>
> + autoheader
>
> autoheader: warning: missing template: ENABLE_COOKIES
>
> autoheader: Use AC_DEFINE([ENABLE_COOKIES], [], [Description])
>
> autoheader: warning: missing template: GW_NAME
>
> autoheader: warning: missing template: GW_VERSION
>
> autoheader: warning: missing template: HAVE_CASS
>
> autoheader: warning: missing template: HAVE_FUNC_GETHOSTBYNAME_R_3
>
> autoheader: warning: missing template: HAVE_FUNC_GETHOSTBYNAME_R_5
>
> autoheader: warning: missing template: HAVE_FUNC_GETHOSTBYNAME_R_6
>
> autoheader: warning: missing template: HAVE_GSOAP
>
> autoheader: warning: missing template: HAVE_MYSQL
>
> autoheader: warning: missing template: HAVE_NFTW
>
> autoheader: warning: missing template: HAVE_PCRE
>
> autoheader: warning: missing template: HAVE_PGSQL
>
> autoheader: warning: missing template: HAVE_PTHREAD_RWLOCK
>
> autoheader: warning: missing template: HAVE_PTHREAD_SPINLOCK_T
>
> autoheader: warning: missing template: HAVE_REDIS
>
> autoheader: warning: missing template: HAVE_REGEX
>
> autoheader: warning: missing template: HAVE_SDB
>
> autoheader: warning: missing template: HAVE_SEMAPHORE
>
> autoheader: warning: missing template: HAVE_SQLITE
>
> autoheader: warning: missing template: HAVE_SQLITE3
>
> autoheader: warning: missing template: HAVE_UCONTEXT
>
> autoheader: warning: missing template: HAVE_WTLS_OPENSSL
>
> autohea

Re: DLRs getting deleted from Msql

[Web Min]

It delete from dlr table if you are passing dlr_url to update your original
database

in my case, I have queue table contain the status, sender_id, msg, etc...
this table is used by my portal, when I send an sms it insert into
dlr table for while and once I received the DLR status pushed from the
SMSC, I'm updating my queue table and Kannel delete the record from the dlr

On Tue, Dec 11, 2018 at 6:07 PM christopher kamutumwa <
chriskamutu...@gmail.com> wrote:

> I have kannel v1.4.4 running properly am able to sending messages and
> receive dlrs as per access log.
>
> but I cant see it getting saved to msql as table dlr in temp_dlr is empty.
> I have checked bearerbox.log and am getting below action that dlr is
> getting deleted. How do I resolve this?
>
> Bearerbox.log below
> ….
> removing DLR from database
> 2018-12-11 14:34:08 [16289] [7] DEBUG: sql: DELETE FROM `dlr` WHERE
> `smsc`=? AND `ts`=?  LIMIT 1
>
> ………
>
> Thanks in advance
> Chris
>

receiving delivery issue

[Web Min]

Hello,

I'm using the following configuration on my kannel on 3 gateways, each
gateway contains 2 sessions, one for sending and the other for receiving,
the below is for receiving delivery status.

I have no issue with all of them till 3 months before one of them not able
to pull the status, at the same time the same gateways is connected with
more than 6000 clients with no issue at all.

The provider asked me to change the register_dlr=1 , any help plz?

interface-version = 34
host = xx.xx.xx.xx
port = 0
receive-port = 8899
smsc-username = user
smsc-password = pass
system-type = VMA
source-addr-ton = 5
source-addr-npi = 1
dest-addr-ton = 0
dest-addr-npi = 0
keepalive = 600
reconnect-delay = 3
enquire-link-interval = 30
esm-class = 0
msg-id-type = 0x01

Re: receiving delivery issue

[Web Min]

Hello,

I found this parameter in kannel registered_delivery, how do I use it in
the kannel.conf?

When I place it the bearbox wont run

Regards

On Sat, Jan 19, 2019 at 7:18 PM Web Min  wrote:

> Hello,
>
> I'm using the following configuration on my kannel on 3 gateways, each
> gateway contains 2 sessions, one for sending and the other for receiving,
> the below is for receiving delivery status.
>
> I have no issue with all of them till 3 months before one of them not able
> to pull the status, at the same time the same gateways is connected with
> more than 6000 clients with no issue at all.
>
> The provider asked me to change the register_dlr=1 , any help plz?
>
> interface-version = 34
> host = xx.xx.xx.xx
> port = 0
> receive-port = 8899
> smsc-username = user
> smsc-password = pass
> system-type = VMA
> source-addr-ton = 5
> source-addr-npi = 1
> dest-addr-ton = 0
> dest-addr-npi = 0
> keepalive = 600
> reconnect-delay = 3
> enquire-link-interval = 30
> esm-class = 0
> msg-id-type = 0x01
>

Re: source of a message

[Web Min]

If I'm not mistaken, the 301000 is the sender id to appear for the
recipient not the IP address of the client.

Warm Regards,

On Sun, Feb 10, 2019 at 5:13 PM Stuart Kendrick 
wrote:

> Starting a few days ago, I see the following once in syslog:
>
>
>
> 2019-02-07T10:03:10.411207-08:00 vishnu smsbox[2075]: 2019-02-07 10:03:10
> [2075] [5] INFO: Starting to service
> <#001#006'application/vnd.wap.mms-message> from <301000> to <1234>
>
>
>
> Followed by many of these:
>
> 2019-02-07.gz:2019-02-07T10:05:10.583219-08:00 guru smsbox[2075]:
> 2019-02-07 10:05:10 [2075] [5] INFO: Starting to service <11121611611 Error
> Invalid Number. Please re-send using a valid 10 digit mobile number or
> valid short code. No service specified> from <+1121611611> to <1234>
>
>
>
> What device submitted this message?  I don’t see an IP address in these
> log lines
>
>
>
>
>
> As far as I know, the only source of SMS messages to my Kannel
> installation is a script (‘send-sms’) which executes an HTTP PUT on the
> following URL:
>
>   $url = "http://
> $gateway/cgi-bin/sendsms?username=$username&password=$password&to=$recipient_tel&text=$message";
>
>
>
> And normally, I see something like the following in syslog:
>
>
>
> 2019-02-07T08:00:32.314355-08:00 guru smsbox[2075]: 2019-02-07 08:00:32
> [2075] [3] INFO: smsbox: Got HTTP request  from
> <10.12.7.11>
>
> 2019-02-07T08:00:32.314415-08:00 guru smsbox[2075]: 2019-02-07 08:00:32
> [2075] [3] INFO: sendsms used by 
>
> 2019-02-07T08:00:32.314472-08:00 guru smsbox[2075]: 2019-02-07 08:00:32
> [2075] [3] INFO: sendsms sender: (10.12.7.11)
> to:<2069548415> msg:dn:1[console.aws.amazon.com]>
>
>
>
> In other words, the only source for SMS messages is 10.12.7.11 … what does
> the source *301000* mean … it doesn’t look like an IP address to me.
>
>
>
> --sk
>
>
>

Re: kannel with sigtran

[Web Min]

Hello,

You can always start with Kannel via

https://medium.com/@SudeepParajuli/quickstart-with-kannel-7005684bffb9

https://kannel.org/download/1.5.0/userguide-1.5.0/userguide.html

https://mahtabrasheed.wordpress.com/2013/01/10/how-to-installconfigure-kannelsms-gateway-for-sending-sms-from-your-computer/

Best Regards

On Mon, Feb 11, 2019 at 10:54 AM eyas barhouk  wrote:

> Good evening dears,
>
> i'm trying to build GSM SMSC starting from kannel, so is that's applicable
> and what other components i may need to deal with SIGTRAN signalling?
>
> Thanks in advance
> Best regards
> Eyas
>
>

Re: kannel with sigtran

[Web Min]

Dear Eyas,

The SS7 protocol is usually used between operator to operator but the SMPP
with a high number of sessions can support 10M messages sure if you split
the connections, like 10 session transmitter and 5 for push delivery status.

Regards

On Mon, Feb 11, 2019 at 12:45 PM eyas barhouk  wrote:

> Dear Davor,
>
> thanks for your kind reply.
>
> i am already thinking about the architecture that i will use to build the
> SMSC.
> it could be (kannel for smpp , Queue with database, and SIGTRAN PROTOCOL
> SUITE from shabed or Open SIGTRAN Project) but for now i don't know how to
> make it work or how the whole of system should work.
> so i'm looking for any kind of experience with this domain.
>
> B.R
> Eyas Barhok
>
>
> --
> *From:* Davor Spasoski 
> *Sent:* Monday, February 11, 2019 8:59 AM
> *To:* eyas barhouk; users@kannel.org
> *Subject:* RE: kannel with sigtran
>
>
> Hi Eyas,
>
>
>
> I’m not sure if you allready went throught the architecture of and SMSC,
> but implementing one is quite an endevor with a large scope of problems
> (not only technical) that need to be solved.
>
> Regardless of Sigtran or SS7, none of the upper layer protocols (MAP, TCAP
> and SCCP) are supported on kannel. Kannel is naturally SMS gateway helping
> to bridge tha gap betwenn the IT world and the complexities of the
> protocols listed above.
>
> Other than http, radius, smpp, and a bunch of now more or less obsolete
> protocols I’m not aware of anything closer to the tellecommunication
> protocols.
>
> Kannel is very good at what it does, but it’s not an SMSC.
>
>
>
> SMSC typically needs SS7/Sigtran capable element that receives and sends
> SMS from wireless network users a store and forward engine with elaborate
> retry schemes and a way to resolve the routing (SRI_SM towards HLR). If you
> are after an entity that would only send application originated messages
> and you are capable of resolving the technical demands, you would still
> need a telecom operator to give you a whitelisted global title, otherwise,
> most of the operators today will simply block the traffic from your SMSC.
>
>
>
> If you decide to pursue the challenge, try the open SS7 protocol stack and
> start from there, but you will need access to a telecom network.
>
>
>
> *Davor Spasoski*
>
>
>
> *From:* users  *On Behalf Of *eyas barhouk
> *Sent:* Monday, February 11, 2019 8:53 AM
> *To:* users@kannel.org
> *Subject:* kannel with sigtran
>
>
>
> Good evening dears,
>
>
>
> i'm trying to build GSM SMSC starting from kannel, so is that's applicable
> and what other components i may need to deal with SIGTRAN signalling?
>
>
>
> Thanks in advance
>
> Best regards
>
> Eyas
>
>
>
> --
>
> Disclaimer: one.Vip DOOEL 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 DOOEL 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: kannel with sigtran

[Web Min]

SIGTRAN (for Signaling Transport) is the standard telephony protocol used
to transport Signaling System 7 (SS7) signals over the Internet. SS7
signals consist of special commands for handling a telephone call.

I don't have any idea about the Sigtran Signaling setup yet because I don't
have Telephone Company or Operator yet.

I have experience with SMPP as I'm running over 4 years without any problem.

I canceled the mechanism of Bulk SMS Over HTTP since a long time ago.

Back to your Original question: Refer to my links in the first reply and
fly.

Regards

On Mon, Feb 11, 2019 at 10:21 PM eyas barhouk  wrote:

> thanks for your kind reply dear,
>
> do you have any idea about how to start with creating the SMSC
> (SMPP&sigtran signaling).
>
> B.R
> Eyas Barhok
>
> --
> *From:* Web Min 
> *Sent:* Monday, February 11, 2019 10:03 AM
> *To:* eyas barhouk
> *Cc:* Davor Spasoski; users@kannel.org
> *Subject:* Re: kannel with sigtran
>
> Dear Eyas,
>
> The SS7 protocol is usually used between operator to operator but the SMPP
> with a high number of sessions can support 10M messages sure if you split
> the connections, like 10 session transmitter and 5 for push delivery status.
>
> Regards
>
> On Mon, Feb 11, 2019 at 12:45 PM eyas barhouk  wrote:
>
> Dear Davor,
>
> thanks for your kind reply.
>
> i am already thinking about the architecture that i will use to build the
> SMSC.
> it could be (kannel for smpp , Queue with database, and SIGTRAN PROTOCOL
> SUITE from shabed or Open SIGTRAN Project) but for now i don't know how to
> make it work or how the whole of system should work.
> so i'm looking for any kind of experience with this domain.
>
> B.R
> Eyas Barhok
>
>
> --
> *From:* Davor Spasoski 
> *Sent:* Monday, February 11, 2019 8:59 AM
> *To:* eyas barhouk; users@kannel.org
> *Subject:* RE: kannel with sigtran
>
>
> Hi Eyas,
>
>
>
> I’m not sure if you allready went throught the architecture of and SMSC,
> but implementing one is quite an endevor with a large scope of problems
> (not only technical) that need to be solved.
>
> Regardless of Sigtran or SS7, none of the upper layer protocols (MAP, TCAP
> and SCCP) are supported on kannel. Kannel is naturally SMS gateway helping
> to bridge tha gap betwenn the IT world and the complexities of the
> protocols listed above.
>
> Other than http, radius, smpp, and a bunch of now more or less obsolete
> protocols I’m not aware of anything closer to the tellecommunication
> protocols.
>
> Kannel is very good at what it does, but it’s not an SMSC.
>
>
>
> SMSC typically needs SS7/Sigtran capable element that receives and sends
> SMS from wireless network users a store and forward engine with elaborate
> retry schemes and a way to resolve the routing (SRI_SM towards HLR). If you
> are after an entity that would only send application originated messages
> and you are capable of resolving the technical demands, you would still
> need a telecom operator to give you a whitelisted global title, otherwise,
> most of the operators today will simply block the traffic from your SMSC.
>
>
>
> If you decide to pursue the challenge, try the open SS7 protocol stack and
> start from there, but you will need access to a telecom network.
>
>
>
> *Davor Spasoski*
>
>
>
> *From:* users  *On Behalf Of *eyas barhouk
> *Sent:* Monday, February 11, 2019 8:53 AM
> *To:* users@kannel.org
> *Subject:* kannel with sigtran
>
>
>
> Good evening dears,
>
>
>
> i'm trying to build GSM SMSC starting from kannel, so is that's applicable
> and what other components i may need to deal with SIGTRAN signalling?
>
>
>
> Thanks in advance
>
> Best regards
>
> Eyas
>
>
>
> --
>
> Disclaimer: one.Vip DOOEL 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 DOOEL 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: Need help for opensmpp and SQLBox

[Web Min]

Which version of SQLBOX and KAnnel installed?

Did you install them via a repository or via truck then compile?

Regards

On Mon, Feb 18, 2019 at 11:21 AM Loyc Cossou  wrote:

> Hi,
>
> It's now been 2 weeks that I am struggling with this configuration.
>
> I am trying to connect OpenSMPPBox to SqlBix so all the messages are sent
> via SQLBox and the DLRs and Logs are available in the database.
>
> Kannel is working fine  as I am able to send SMS.
> SQLBox is also working fine as all the messages I insert in the SEND_SMS
> table are being sent and moved to SENT_SMS.
> And all my clients are able to connect via SMPP and send SMS.
>
> The configuration is like OpenSmppBox and SQLBox are all connected to
> bearearBox, but I need this openSMPP --> SQLBox --> Kannel.
>
> Bellow is my configuration files. Can you please advise on how to modify
> it so i have opensmppbox connected to sqlbox connected to Bearerbox?
> openSMPP --> SQLBox --> Kannel
>
>
> *# Default kannel configuration file*
> *group = core*
> *admin-port = 13000*
> *admin-password = adminuser*
> *status-password = adminpass*
> *admin-deny-ip = "*.*.*.*"*
> *admin-allow-ip = "*.*.*.*"*
> *smsbox-port = 13001*
> *box-allow-ip = "*.*.*.*"*
> *wdp-interface-name = "*"*
> *log-file = "/etc/kannel/log/bearerbox.log"*
> *log-level = 0*
> *dlr-storage = mysql*
> *smsbox-max-pending = 5000*
> *sms-resend-freq = 5*
> *sms-resend-retry = 5*
> *store-location = "/etc/kannel/log/kannel-insms-tmp"*
>
> *# SMSBOX SETUP*
> *group = smsbox*
> *smsbox-id = mysmsbox*
> *bearerbox-host = localhost*
> *sendsms-port = 13013*
> *global-sender = Connectify*
> *log-file = "/etc/kannel/log/smsbox.log"*
> *log-level = 1*
> *access-log = "/etc/kannel/log/Mo_sendSMSRequests.access"*
> *reply-couldnotfetch = "Aucune correspondance pour votre requete"*
> *reply-couldnotrepresent = "Le resultat ne peut etre transmis via SMS"*
> *reply-requestfailed = "Une erreur temporaire est survenue... Veuillez
> ressayer plus tard"*
> *reply-emptymessage = "Aucune correspondance pour votre requete"*
> *http-request-retry = 1*
> *http-queue-delay = 5*
> *max-pending-requests = 5000*
> *#sms-length = 160*
> *#mo-recode = true*
>
> *group = smsbox-route*
> *smsbox-id = mysmsbox*
> *smsc-id = favoriteSMSC*
>
> *# SMSC CONNECTIONS*
> *group = smsc*
> *smsc = smpp*
> *smsc-id = MoovBjSoneb*
> *preferred-smsc-id = MoovBjSoneb*
> *denied-smsc-id = favoriteSMSC*
> *interface-version = 34*
> *host = *
> *port = 2775*
> *smsc-username = aa*
> *smsc-password = bb*
> *system-type = smpp*
> *address-range = ""*
> *dest-addr-ton = 1*
> *dest-addr-npi = 1*
> *bind-addr-ton = 1*
> *bind-addr-npi = 1*
> *#msg-id-type = 0x00*
> *transceiver-mode = yes*
> *source-addr-autodetect = yes*
>
> *# SMSC CONNECTIONS*
> *group = smsc*
> *smsc = smpp*
> *smsc-id = favoriteSMSC*
> *preferred-smsc-id = favoriteSMSC*
> *denied-smsc-id = MoovBjSoneb*
> *interface-version = 34*
> *host = *
> *port = 2775*
> *smsc-username = cc*
> *smsc-password = dd*
> *system-type = smpp*
> *address-range = ""*
> *dest-addr-ton = 1*
> *dest-addr-npi = 1*
> *bind-addr-ton = 1*
> *bind-addr-npi = 1*
> *msg-id-type = 0x00*
> *transceiver-mode = yes*
> *source-addr-autodetect = yes*
>
> *group = sendsms-user*
> *username = my*
> *password = god*
> *max-messages = 7*
> *concatenation = true*
> *forced-smsc = favoriteSMSC*
>
> *# mysql connection*
> *group = mysql-connection*
> *id = mydlr*
> *host = something.amazonaws.com *
> *username = theuser*
> *password = thepass*
> *database = thedb*
> *max-connections = 1*
>
> *# DLR table structure*
> *group = dlr-db*
> *id = mydlr*
> *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 = boxc*
>
>
>
>
> *SQLBox Conf *
> *#SqlBox*
> *group = sqlbox*
> *id = sqlbox-db*
> *smsbox-id = public_ctf*
> *bearerbox-host = localhost*
> *bearerbox-port = 13001*
> *smsbox-port = 130013*
> *smsbox-port-ssl = false*
> *sql-log-table = sent_sms*
> *sql-insert-table = send_sms*
> *log-file = "/etc/kannel/log/sqlbox.log"*
> *log-level = 0*
>
> *# mysql connection*
> *group = mysql-connection*
> *id = sqlbox-db*
> *host = something.amazonaws.com *
> *port = 3306*
> *username = theuser*
> *password = thepass*
> *database = aSQLBoxDb*
> *max-connections = 1*
>
>
>
> * Opensmppbox.conf ==*
>
> *group = core*
> *dlr-storage = mysql*
>
> *#OpenSmppBox*
> *group = opensmppbox*
> *opensmppbox-id = smppboxA*
> *opensmppbox-port = 8990*
> *bearerbox-host = localhost*
> *bearerbox-port = 13001*
> *#bearerbox-port = 13013*
> *our-system-id = public_ctf*
> *smpp-logins = /etc/kannel/utilisateurs.txt*
> *use-systemid-as-smsboxid = true*
> *route-to-smsc = favoriteSMSC*
> *source-addr-ton = 1*
> *source-addr-npi = 1*
> *dest-addr-ton = 1*
> *dest-addr-npi = 1*
> *

Re: OPENSMPPBox issue.

[Web Min]

How you are running both bearerbox and smsbox?

make sure to pico /etc/default/kannel
and then add

START_WAPBOX=1
START_SMSBOX=1

then restart the kannel service, after that check the status via your brower


On Mon, Feb 18, 2019 at 12:49 PM Gert Tamm  wrote:

> Hello,
>
> When I start my bearerbox and smsbox with any configuration of
> OpenSMPPBox, only SMPPBox starts, bearerbox and smsbox won't start. And
> I'm not getting any errors to log files.
> What I might have done wrong?
>
> --
> Tervitades/Best Wishes,
> Gert Tamm
> Süsteemiadministraator/System administrator
> E-mail: g...@messenger.ee
> Direct Messenger OÜ
>
>
>

Re: OPENSMPPBox issue.

[Web Min]

try the following instead

bearerbox -v 0 /etc/kannel/kannel.conf

smsbox -v 0 /etc/kannel/kannel.conf

and share the output


On Tue, Feb 19, 2019 at 10:03 AM Gert Tamm  wrote:

> I start all the parts of kannel like this :
>
> sudo /usr/local/sbin/run_kannel_box --pidfile
> /var/run/kannel/kannel_bearerbox.pid --no-extra-args
> /usr/local/sbin/bearerbox -v 0 -- /etc/kannel/kannel.conf
> sudo /usr/local/sbin/run_kannel_box --pidfile
> /var/run/kannel/kannel_smsbox.pid --no-extra-args /usr/local/sbin/smsbox -v
> 0 -- /etc/kannel/kannel.conf
> sudo /usr/local/sbin/run_kannel_box --pidfile
> /var/run/kannel/kannel_smppbox.pid --no-extra-args
> /usr/local/sbin/opensmppbox -v 0 -- /etc/kannel/kannel.conf
> 2/18/2019 11:54 Web Min kirjutas:
>
> How you are running both bearerbox and smsbox?
>
> make sure to pico /etc/default/kannel
> and then add
>
> START_WAPBOX=1
> START_SMSBOX=1
>
> then restart the kannel service, after that check the status via your
> brower
>
>
> On Mon, Feb 18, 2019 at 12:49 PM Gert Tamm  wrote:
>
>> Hello,
>>
>> When I start my bearerbox and smsbox with any configuration of
>> OpenSMPPBox, only SMPPBox starts, bearerbox and smsbox won't start. And
>> I'm not getting any errors to log files.
>> What I might have done wrong?
>>
>> --
>> Tervitades/Best Wishes,
>> Gert Tamm
>> Süsteemiadministraator/System administrator
>> E-mail: g...@messenger.ee
>> Direct Messenger OÜ
>>
>>
>> --
> Tervitades/Best Wishes,
> Gert Tamm
> Süsteemiadministraator/System administrator
> E-mail: g...@messenger.ee
> Direct Messenger OÜ
>
>

Re: OPENSMPPBox issue.

[Web Min]

it seems you have a problem with your configuration as showing below

2019-02-19 08:07:13 [13238] [0] ERROR: Group 'opensmppbox' is no valid
group identifier.
2019-02-19 08:07:13 [13238] [0] ERROR: Error found on line 5 of file
`/etc/kannel/kannel.conf'.



On Tue, Feb 19, 2019 at 10:08 AM Gert Tamm  wrote:

> 2019-02-19 08:07:13 [13238] [0] INFO: Debug_lvl = 0, log_file = ,
> log_lvl = 0
> 2019-02-19 08:07:13 [13238] [0] DEBUG: Loading include file
> `/etc/kannel/opensmppbox.conf' (on line 39 of file /etc/kannel/kannel.conf).
> 2019-02-19 08:07:13 [13238] [0] ERROR: Group 'opensmppbox' is no valid
> group identifier.
> 2019-02-19 08:07:13 [13238] [0] ERROR: Error found on line 5 of file
> `/etc/kannel/kannel.conf'.
> 2019-02-19 08:07:13 [13238] [0] PANIC: Couldn't read configuration from
> `/etc/kannel/kannel.conf'.
> 2019-02-19 08:07:13 [13238] [0] PANIC: bearerbox(gw_panic+0x16b) [0x48068b]
> 2019-02-19 08:07:13 [13238] [0] PANIC: bearerbox(main+0xe3a) [0x40d69a]
> 2019-02-19 08:07:13 [13238] [0] PANIC:
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f9fe54d0830]
> 2019-02-19 08:07:13 [13238] [0] PANIC: bearerbox(_start+0x29) [0x40d759]
>
>
> 2019-02-19 08:07:15 [13239] [0] INFO: Debug_lvl = 0, log_file = ,
> log_lvl = 0
> 2019-02-19 08:07:15 [13239] [0] DEBUG: Loading include file
> `/etc/kannel/opensmppbox.conf' (on line 39 of file /etc/kannel/kannel.conf).
> 2019-02-19 08:07:15 [13239] [0] ERROR: Group 'opensmppbox' is no valid
> group identifier.
> 2019-02-19 08:07:15 [13239] [0] ERROR: Error found on line 5 of file
> `/etc/kannel/kannel.conf'.
> 2019-02-19 08:07:15 [13239] [0] PANIC: Couldn't read configuration from
> `/etc/kannel/kannel.conf'.
> 2019-02-19 08:07:15 [13239] [0] PANIC: smsbox(gw_panic+0x16b) [0x439adb]
> 2019-02-19 08:07:15 [13239] [0] PANIC: smsbox(main+0x12b9) [0x40d7d9]
> 2019-02-19 08:07:15 [13239] [0] PANIC:
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7fbc458d8830]
> 2019-02-19 08:07:15 [13239] [0] PANIC: smsbox(_start+0x29) [0x40da69]
>
> 2/19/2019 09:05 Web Min kirjutas:
>
> try the following instead
>
> bearerbox -v 0 /etc/kannel/kannel.conf
>
> smsbox -v 0 /etc/kannel/kannel.conf
>
> and share the output
>
>
> On Tue, Feb 19, 2019 at 10:03 AM Gert Tamm  wrote:
>
>> I start all the parts of kannel like this :
>>
>> sudo /usr/local/sbin/run_kannel_box --pidfile
>> /var/run/kannel/kannel_bearerbox.pid --no-extra-args
>> /usr/local/sbin/bearerbox -v 0 -- /etc/kannel/kannel.conf
>> sudo /usr/local/sbin/run_kannel_box --pidfile
>> /var/run/kannel/kannel_smsbox.pid --no-extra-args /usr/local/sbin/smsbox -v
>> 0 -- /etc/kannel/kannel.conf
>> sudo /usr/local/sbin/run_kannel_box --pidfile
>> /var/run/kannel/kannel_smppbox.pid --no-extra-args
>> /usr/local/sbin/opensmppbox -v 0 -- /etc/kannel/kannel.conf
>> 2/18/2019 11:54 Web Min kirjutas:
>>
>> How you are running both bearerbox and smsbox?
>>
>> make sure to pico /etc/default/kannel
>> and then add
>>
>> START_WAPBOX=1
>> START_SMSBOX=1
>>
>> then restart the kannel service, after that check the status via your
>> brower
>>
>>
>> On Mon, Feb 18, 2019 at 12:49 PM Gert Tamm  wrote:
>>
>>> Hello,
>>>
>>> When I start my bearerbox and smsbox with any configuration of
>>> OpenSMPPBox, only SMPPBox starts, bearerbox and smsbox won't start. And
>>> I'm not getting any errors to log files.
>>> What I might have done wrong?
>>>
>>> --
>>> Tervitades/Best Wishes,
>>> Gert Tamm
>>> Süsteemiadministraator/System administrator
>>> E-mail: g...@messenger.ee
>>> Direct Messenger OÜ
>>>
>>>
>>> --
>> Tervitades/Best Wishes,
>> Gert Tamm
>> Süsteemiadministraator/System administrator
>> E-mail: g...@messenger.ee
>> Direct Messenger OÜ
>>
>> --
> Tervitades/Best Wishes,
> Gert Tamm
> Süsteemiadministraator/System administrator
> E-mail: g...@messenger.ee
> Direct Messenger OÜ
>
>

Re: disabling incoming SMS

[Web Min]

Hello,

If you are using the SMSBOX, did you try to change the password of group =
sendsms-user

Try to add also the global-sender parameter to the group = smsbox , to
restrict certain pre-code like 001 for state etc in this way, it will
ignore the none prefix mobile number.

Try to change the smsbox-port if applicable.

Warm Regards

On Tue, Feb 19, 2019 at 7:47 PM Stuart Kendrick 
wrote:

> I’m seeing a lot of this in my logs:
>
>
>
> 2019-02-18T19:28:26.526495-08:00 vishnu smsbox[21580]: 2019-02-18 19:28:26
> [21580] [5] INFO: Starting to service
> <#001#006'application/vnd.wap.mms-message> from <301000> to <1234>
>
> 2019-02-18T19:28:44.167763-08:00 vishnu smsbox[21580]: 2019-02-18 19:28:44
> [21580] [5] INFO: Starting to service <1301000 Error Invalid Number.
> Please re-send using a valid 10 digit mobile number or valid short code. No
> service specified> from <+1121611611> to <1234>
>
> […]
>
> 2019-02-19T08:38:24.918834-08:00 vishnu smsbox[21580]: 2019-02-19 08:38:24
> [21580] [5] INFO: Starting to service <11121611611 Error Invalid Number.
> Please re-send using a valid 10 digit mobile number or valid short code. No
> service specified> from <+1121611611> to <1234>
>
> 2019-02-19T08:38:37.474384-08:00 vishnu smsbox[21580]: 2019-02-19 08:38:37
> [21580] [5] INFO: Starting to service <11121611611 Error Invalid Number.
> Please re-send using a valid 10 digit mobile number or valid short code. No
> service specified> from <+1121611611> to <1234>
>
>
>
> I speculate:  someone has found my cellular modem number and is sending me
> spam.
>
>
>
> For this application, I transmit SMS over the cellular modem; I don’t want
> to receive anything.
>
>- My carrier (AT&T) tells me that they cannot block in-bound SMS –
>they can enable bi-directional SMS or disable it:  all or nothing.
>- I disabled auto-answer on the modem … but this setting appears to
>govern POTS, not SMS
>
>
>
>- Is there a Kannel way (bearerbox or smsbox) to disable incoming
>reception of SMS?
>- Alternatively, is there a way to instruct Kannel to send requests
>for Invalid Numbers (e.g. ‘1234’) to /dev/null?
>- Other ideas for dumping these messages?  I’m mostly annoyed by the
>repetitive logging
>
>
>
> At the moment, I have a cronjob job which stops bearerox & smsbox, sleeps
> for several minutes (not clear to me why this is necessary), and then
> restarts them.  This of course creates a dead zone, in terms of service,
> which is suboptimal.
>
>
>
> --sk
>
>
>
>
>

Re: disabling incoming SMS

[Web Min]

Awesome.

On Wed, Feb 20, 2019 at 10:32 PM Stuart Kendrick 
wrote:

> I ended up adding my modem’s phone number to the white-list line.  This
> seems to be working as desired – no more spam.
>
>
>
> # Smsbox related
>
> group = smsbox
>
> bearerbox-host = localhost
>
> global-sender = xx
>
> white-list = xx
>
>
>
> where ‘xx’ is really my modem’s phone number
>
>
>
> --sk
>
>
>
> *From:* Web Min 
> *Sent:* Tuesday, February 19, 2019 8:57 AM
> *To:* Stuart Kendrick 
> *Cc:* users@kannel.org
> *Subject:* Re: disabling incoming SMS
>
>
>
> Hello,
>
>
>
> If you are using the SMSBOX, did you try to change the password of group =
> sendsms-user
>
>
>
> Try to add also the global-sender parameter to the group = smsbox , to
> restrict certain pre-code like 001 for state etc in this way, it will
> ignore the none prefix mobile number.
>
>
>
> Try to change the smsbox-port if applicable.
>
>
>
> Warm Regards
>
>
>
> On Tue, Feb 19, 2019 at 7:47 PM Stuart Kendrick <
> stua...@alleninstitute.org> wrote:
>
> I’m seeing a lot of this in my logs:
>
>
>
> 2019-02-18T19:28:26.526495-08:00 vishnu smsbox[21580]: 2019-02-18 19:28:26
> [21580] [5] INFO: Starting to service
> <#001#006'application/vnd.wap.mms-message> from <301000> to <1234>
>
> 2019-02-18T19:28:44.167763-08:00 vishnu smsbox[21580]: 2019-02-18 19:28:44
> [21580] [5] INFO: Starting to service <1301000 Error Invalid Number.
> Please re-send using a valid 10 digit mobile number or valid short code. No
> service specified> from <+1121611611> to <1234>
>
> […]
>
> 2019-02-19T08:38:24.918834-08:00 vishnu smsbox[21580]: 2019-02-19 08:38:24
> [21580] [5] INFO: Starting to service <11121611611 Error Invalid Number.
> Please re-send using a valid 10 digit mobile number or valid short code. No
> service specified> from <+1121611611> to <1234>
>
> 2019-02-19T08:38:37.474384-08:00 vishnu smsbox[21580]: 2019-02-19 08:38:37
> [21580] [5] INFO: Starting to service <11121611611 Error Invalid Number.
> Please re-send using a valid 10 digit mobile number or valid short code. No
> service specified> from <+1121611611> to <1234>
>
>
>
> I speculate:  someone has found my cellular modem number and is sending me
> spam.
>
>
>
> For this application, I transmit SMS over the cellular modem; I don’t want
> to receive anything.
>
>- My carrier (AT&T) tells me that they cannot block in-bound SMS –
>they can enable bi-directional SMS or disable it:  all or nothing.
>- I disabled auto-answer on the modem … but this setting appears to
>govern POTS, not SMS
>
>
>
>- Is there a Kannel way (bearerbox or smsbox) to disable incoming
>reception of SMS?
>- Alternatively, is there a way to instruct Kannel to send requests
>for Invalid Numbers (e.g. ‘1234’) to /dev/null?
>- Other ideas for dumping these messages?  I’m mostly annoyed by the
>repetitive logging
>
>
>
> At the moment, I have a cronjob job which stops bearerox & smsbox, sleeps
> for several minutes (not clear to me why this is necessary), and then
> restarts them.  This of course creates a dead zone, in terms of service,
> which is suboptimal.
>
>
>
> --sk
>
>
>
>
>
>

Re: Kannel Installtion error CentOS 7

[Web Min]

Hello,

I tried many times to compile the kannel and SQLBox via source under Ubuntu
but it always failed. There are many errors you have to follow each one to
solve it. finally, I decided to install the Kannel Via Repository apt-get
get install kannel kannel-extra and it's working like charm.

Regarding your CentOS, Personally; I have no Idea as I'm using It only for
website server running under WHM. Below are some commands you must follow
first might be helped, did you?

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

Best Regards


On Sat, Mar 9, 2019 at 7:31 PM MOSES KARIUKI  wrote:

> Dear Users,
>
> Any assistance on this? Please assist.
>
> Regards,
> Moses
>
> On Thu, Jan 3, 2019 at 4:16 PM MOSES KARIUKI  wrote:
>
>> Dear Users,
>>
>> I am getting the below error while trying to install Kannel after running
>> the command  make -j3 install :
>>
>> -lxml2 -lz -lm -ldl -lpcreposix -lpcre -lcrypto -lssl -Wl,-rpath
>> -Wl,/usr/local/lib
>> smscconn.o: In function `smscconn_create':
>> /opt/knl/installs/kannel.svn/trunk/gw/smscconn.c:360: *undefined
>> reference to `smsc_soap_parlayx_create'*
>> collect2: error: ld returned 1 exit status
>> make[2]: *** [bearerbox] Error 1
>> make[2]: *** Waiting for unfinished jobs
>> make[2]: Leaving directory `/opt/knl/installs/kannel.svn/trunk/gw'
>> make[1]: *** [install-recursive] Error 1
>> make[1]: Leaving directory `/opt/knl/installs/kannel.svn/trunk'
>> make: *** [install] Error 2
>>
>> These are the steps I have followed so far :
>>
>>1. Install Postgres
>>2. yum install postgresql-devel
>>3. yum update
>>4. yum groupinstall -y 'Development Tools'
>>5. yum install libxml2-devel -y
>>6. yum install openssl-devel -y
>>7. Install GSOAP support
>>
>> wget https://sourceforge.net/projects/gsoap2/files/latest/download
>> unzip download
>> cd gsoap/
>> ./configure --prefix=/usr
>> make
>> make install
>>
>> cd /opt/knl/installs/kannel/trunk/
>> ./bootstrap.sh
>> ./configure  --with-pgsql --enable-ssl --with-gsoap
>> --enable-start-stop-daemon --enable-pcre
>> make -j3 install
>>
>> Then the above error occurs:
>>
>> /opt/knl/installs/kannel.svn/trunk/gw/smscconn.c:360: *undefined
>> reference to `smsc_soap_parlayx_create'*
>>
>>
>> Please assist
>>
>>
>>
>>
>>

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: SQLBox Database structure on Kannel 1.4.5

[Web Min]

I'm trying to install the SQLbox since a long time ago, no installation
procedure yet.

Could you please share your steps for the installation and will compare the
new structure with the old one.

Regards

On Sat, Jun 1, 2019 at 9:44 PM Loyc Cossou  wrote:

> Hi Friends,
>
> It seems like the structure on the Database for SQLBox on kannel 1.4.5 has
> changed. I have noticed that the new parameter/Column "priority" has been
> added.
>
> Anyone can suggest the new database structure please? Any other change I
> should be aware of when switching from Kannel 1.4.4 to 1.4.5?
>
> Thanks
>
> --
> loyc Cossou
>
> [image: Mailtrack]
> 
>  Sender
> notified by
> Mailtrack
> 
>  01/06/19
> à 19:39:12
>

Re: DLR-MO store increases

[Web Min]

How size is the DLR Table? And did you try to empty the DLR it?

On Wed, Nov 13, 2019 at 12:15 PM vinayak mv 
wrote:

> Hi,
>
> When we are sending MT SMS about 1 lakhs or more , the kannel store is
> filled with DLR-MO messages and these messages are routing back to SQLBOX
> or OPENSMPPBOX at a slow ratio at that time tps is reduced but when i
> restart the SQLBOX or OPENSMPPBOX the size of the store gets decreases
> rapidly coz all the DLR are routed back to SQLBOX.Does anyone know this
> strange behaviour?? And how to overcome
>
> --
> Thanks & Regards,
> Vinayak
>
> ==
>
> *Confucius* once said,
> "*Life is really simple, but we insist on making it complicated.*"
>
> *Leonardo da Vinci* once said,
> "*Simplicity is the ultimate sophistication.*"
>
> *Albert Einstein* once said,
> "*Everything should be made as simple as possible, but not simpler.*"
>
>
>

Re: users Digest, Vol 159, Issue 6

[Web Min]

Can you try the below link, please?

http://localhost:13013/cgi-bin/sendsms?username=YRFN5JRa&password=jL3Uwcmt&to=00967774168311&text=%00H%00e%00l%00l%00o%00+%00w%00o%00r%00l%00d%00+%06%2A%06%2C%061%06%28%06%29%00+%06E%06F%06J&from=test&coding=2&charset=UTF-16BE&dlr-mask=31

On Wed, Nov 13, 2019 at 7:29 PM abod ahameed  wrote:

> Still the same problem
>
> ‫في الأربعاء، 13 نوفمبر 2019 في 7:22 م تمت كتابة ما يلي بواسطة <‪
> users-requ...@kannel.org‬‏>:‬
>
>> Send users mailing list submissions to
>> users@kannel.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> http://www.kannel.org/mailman/listinfo/users
>> or, via email, send a message with subject or body 'help' to
>> users-requ...@kannel.org
>>
>> You can reach the person managing the list at
>> users-ow...@kannel.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of users digest..."
>>
>>
>> Today's Topics:
>>
>>1. RE: users Digest, Vol 159, Issue 4 (Rene Kluwen)
>>
>>
>> --
>>
>> Message: 1
>> Date: Wed, 13 Nov 2019 17:21:46 +0100
>> From: "Rene Kluwen" 
>> To: "'abod ahameed'" ,   
>> Subject: RE: users Digest, Vol 159, Issue 4
>> Message-ID: <029b01d59a3e$7217cd30$56476790$@chimit.nl>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Like I said: Add ?&smsc=smpp-clicksend? (without the qutoes) to the end
>> of your url.
>>
>>
>>
>> == Rene
>>
>>
>>
>> Van: users  Namens abod ahameed
>> Verzonden: woensdag 13 november 2019 16:58
>> Aan: users@kannel.org
>> Onderwerp: Re: users Digest, Vol 159, Issue 4
>>
>>
>>
>>  <
>> http://localhost:13013/cgi-bin/sendsms?username=YRFN5JRa&password=jL3Uwcmt&to=00967774168311&text=Hello%20World&from=test&charset=ISO-8859-1&dlr-mask=17>
>>
>> http://localhost:13013/cgi-bin/sendsms?username=YRFN5JRa&password=jL3Uwcmt&to=00967774168311&text=Hello%20World&from=test&charset=ISO-8859-1&dlr-mask=17
>>
>>
>>
>> ??? ? 13 ?? 2019 ?? 6:17 ? ??? ? ?? ??? ?? > users-requ...@kannel.org> users-requ...@kannel.org?>:
>>
>> Send users mailing list submissions to
>>   users@kannel.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>>  
>> http://www.kannel.org/mailman/listinfo/users
>> or, via email, send a message with subject or body 'help' to
>>   users-requ...@kannel.org
>>
>> You can reach the person managing the list at
>>   users-ow...@kannel.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of users digest..."
>>
>>
>> Today's Topics:
>>
>>1. hi i have problem when linking kannel with clicksend
>>   (abod ahameed)
>>2. RE: hi i have problem when linking kannel with clicksend
>>   (Rene Kluwen)
>>
>>
>> --
>>
>> Message: 1
>> Date: Wed, 13 Nov 2019 18:13:22 +0300
>> From: abod ahameed <  ahameeda...@gmail.com
>> >
>> To:   users@kannel.org
>> Subject: hi i have problem when linking kannel with clicksend
>> Message-ID:
>> < > caoh7rmzsc0g2stdbbluzilbqdpu%2b6%2bdusynvrp_2ja28sw8...@mail.gmail.com>
>> caoh7rmzsc0g2stdbbluzilbqdpu+6+dusynvrp_2ja28sw8...@mail.gmail.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>> this my kannel.conf
>> group = core
>> admin-port = 13000
>> admin-password = bar
>> admin-deny-ip = "*.*.*.*"
>> admin-allow-ip = "127.0.0.1"
>> smsbox-port = 2775
>> log-file = "/var/log/kannel/bearerbox.log"
>> box-deny-ip = "*.*.*.*"
>> box-allow-ip = "127.0.0.1"
>>
>> group = smsbox
>> bearerbox-host="localhost"
>> sendsms-port = 13013
>> sendsms-chars = "+0123456789"
>> log-file = "/var/log/kannel/smsbox.log"
>> log-level = 0
>> access-log = "/var/log/kannel/access.log"
>> log-level = 0
>> mo-recode = 1
>>
>> group = smsc
>> smsc = smpp
>> smsc-id = smpp-clicksend
>> host =    smpp1.clicksend.com
>> port = 2775
>> receive-port = 2775
>> transceiver-mode = false
>> throughput = 10
>> smsc-username = *
>> smsc-password = *
>> system-type = clicksend
>> dest-addr-ton=1
>> log-file = "/var/log/kannel/smpp-clicksend.log"
>> log-level = 0
>> msg-id-type=0x01
>> alt-charset = LATIN1
>> enquire-link-interval = 30
>>
>> group = sendsms-user
>> username = *
>> password = **
>> forced-smsc =  smpp-clicksend
>> name = users
>> user-deny-ip = "*.*.*.*"
>> user-allow-ip = "127.0.0.1"
>> max-messages = 3
>>
>> and this my smsbox.conf
>>
>> group = core
>> admin-port = 13000
>> admin-password = bar
>> admin-deny-ip = "*.*.*.*"
>> admin-allow-ip = "127.0.0.1"
>> smsbox-port = 2775
>> log-file = "/var/log/kannel/bearerbox.log"
>> box-deny-ip = "*.*.*.*"
>> box-allow-ip = "127.0.0.1"
>>
>> group = smsbox
>> bearerbox-hos

Re: Issue of DLR - URL with opensmppbox kannel

[Web Min]

Provide your sqlbox.conf please

On Thu, Feb 13, 2020, 4:32 PM Umair Baig  wrote:

> Hello All,
>
> I have configured opensmppbox and I am trying to submit sms using mysql as
> dlr storage.
> When I receive sms it gets delivered but dlr does not get inserted into
> dlr table instead I get an error message in opensmppbox logs saying the
> below.
>
> 2020-02-13 19:21:14 [15724] [2] ERROR: MYSQL: mysql_stmt_execute() failed:
> `Data truncated for column 'url' at row 1'
> 2020-02-13 19:21:14 [15724] [2] ERROR: DLR: MYSQL: Error while adding dlr
> entry for DST<+9177XX>
>
> I am not sure why url data is not coming when sms is being received and
> field dlr-url in the log file is always empty.
>
> my opensmppbox conf
>
> #configuration
> group = core
> dlr-storage = mysql
>
> ###
> group = mysql-connection
> id = dlr-db
> host = 127.0.0.1
> port = 3303
> username = opensmppbox
> password = "X"
> database = new_sms
> max-connections = 20
>
> ###
> group = dlr-db
> id = dlr-db
> 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 = boxc
> ###
>
> group = opensmppbox
> bearerbox-host = 127.0.0.1
> bearerbox-port = 13001
> opensmppbox-id = smppbox1
> opensmppbox-port = 2775
> log-file = /usr/opensmppbox.log
> log-level = 0
> our-system-id =smpp
> use-systemid-as-smsboxid = true
> route-to-smsc = Test001
> # New accounts
> smpp-logins = /usr/smpplogin.txt
>
> *Thanks & Regards,*
>
>
> *UMAIR BAIG*
> *Sr.Manager*
> *Buzz: +91- 7738857063*
> *On Desk: 022-22007840*
> *SKYPE-ID -umair.baig2893*
>
>   
>
>

change windows size

[Web Min]

Hello,

I just received the following message from the gateway, any help would be
appreciated.

Please notice that today we received bad request from your side and after
investigation found that problem from your side because of sending messages
using ASYNC mode ,

please make sure that window size = 1 .

Which parameter should I Add or change to effect the size of the window?

Regards

Re: change windows size

[Web Min]

I've changed the throughput = 1 but it seems when  I changed the
max-pending-submits is worked.

When I'm checking the guide, I found max-submit-requests any idea about the
purpose of it?

REgards

On Sun, Mar 8, 2020 at 8:41 PM Alejandro Guerrieri <
alejandro.guerri...@gmail.com> wrote:

> That would be max-pending-submits
>
> Check the user guide for further details.
>
> Regards,
>
> --
> Alejandro Guerrieri
>
> On Mar 8, 2020, at 12:47 PM, Web Min  wrote:
>
> 
> Hello,
>
> I just received the following message from the gateway, any help would be
> appreciated.
>
> Please notice that today we received bad request from your side and after
> investigation found that problem from your side because of sending messages
> using ASYNC mode ,
>
> please make sure that window size = 1 .
>
> Which parameter should I Add or change to effect the size of the window?
>
> Regards
>
>

Re: OpenSMPPBox won't create DLR

[Web Min]

I was getting the same issue but now I'm getting the below error from the
access-log

2021-04-27 23:testsender08:20 2021-04-27 23:08:20 DISCARDED SMS [SMSC:]
[SVC:] [ACT:] [BINF:] [FID:18][from:testsender] [to:2378945612]
[flags:-1:2:-1:-1:31] [msg:0:] [udh:0:]
2021-04-27 23:08:20 2021-04-27 23:08:20 Receive DLR [SMSC:] [SVC:] [ACT:]
[BINF:] [FID:18][from:testsender] [to:2378945612] [flags:-1:-1:-1:-1:16]
[msg:12:NACK/no SMSC] [udh:0:]
2021-04-27 23:09:21 2021-04-27 23:08:20 DISCARDED SMS [SMSC:smsc1] [SVC:]
[ACT:] [BINF:] [FID:17][from:testsender] [to:2378945612]
[flags:-1:2:-1:-1:31] [msg:0:] [udh:0:]
2021-04-27 23:09:21 2021-04-27 23:09:21 Receive DLR [SMSC:smsc1] [SVC:]
[ACT:] [BINF:] [FID:17][from:testsender] [to:2378945612]
[flags:-1:-1:-1:-1:16] [msg:21:NACK/Retries Exceeded] [udh:0:]

Any idea about the discarded msgs?



On Thu, Apr 29, 2021 at 10:26 PM Rene Kluwen  wrote:

> Hi Martin,
>
> Looks like you got opensmppbox setup correctly for dlr.
> Adding or omitting sqlbox won't make a difference, like you already saw
> that
> correctly.
>
> Could you list if there is any rows available in the dlr table in your
> postgres database?
>
> Are the submit_sm's sent with registered_delivery set to 1?
>
> It could be a msg-id-type issue. I'm not even sure if that's implemented in
> opensmppbox.
>
> == Rene
>
>
> -Oorspronkelijk bericht-
> Van: users  Namens Martin Caetano
> Verzonden: donderdag 29 april 2021 21:01
> Aan: users@kannel.org
> Onderwerp: OpenSMPPBox won't create DLR
>
> I've spent a significant amount of time around this issue. I've read the
> complete Kannel guide, SO, Nabble and any other resource I could find yet I
> couldn't find any solution or hint on why the DLR aren't being created.
>
> I believe what I'm trying to do is very straightforward:
>
> I'm connected using SMPP to OpenSMPPBox, using PostgreSQL and routing to a
> SMPP SMSC like this:
>
> opensmppbox --> sqlbox ->  bearerbox -> smsc
>
> I can send SMS with no problem to the other end and I can see the pdu
> responses back in the logs. However, the DLRs aren't being created as they
> are when I use HTTP with smsbox and dlr-mask/dlr-url params.
>
> It doesn't matter if I remove the sqlbox and use internal storage, the DLRs
> are never being created (or at least never appear as created in the logs)
> when connecting via smpp to opensmppbox.
>
> 2021-04-29 05:28:14 [35121] [6] DEBUG: SMPP[smsc1]: throughput (0.00,0.00)
> 2021-04-29 05:28:14 [35121] [6] DEBUG: SMPP[smsc1]: Got PDU:
> 2021-04-29 05:28:14 [35121] [6] DEBUG: SMPP PDU 0x7eff380010e0 dump:
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   type_name: deliver_sm
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   command_id: 5 = 0x0005
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   command_status: 0 = 0x
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   sequence_number: 31 = 0x001f
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   service_type: NULL
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   source_addr_ton: 0 = 0x
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   source_addr_npi: 0 = 0x
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   source_addr: "xx"
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   dest_addr_ton: 5 = 0x0005
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   dest_addr_npi: 0 = 0x
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   destination_addr: "MySender"
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   esm_class: 4 = 0x0004
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   protocol_id: 8 = 0x0008
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   priority_flag: 0 = 0x
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   schedule_delivery_time: NULL
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   validity_period: NULL
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   registered_delivery: 0 =
> 0x
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   replace_if_present_flag: 0 =
> 0x
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   data_coding: 0 = 0x
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   sm_default_msg_id: 0 = 0x
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   sm_length: 105 = 0x0069
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   short_message:
> 2021-04-29 05:28:14 [35121] [6] DEBUG:Octet string at 0x7eff38001340:
> 2021-04-29 05:28:14 [35121] [6] DEBUG:  len:  105
> 2021-04-29 05:28:14 [35121] [6] DEBUG:  size: 106
> 2021-04-29 05:28:14 [35121] [6] DEBUG:  immutable: 0
> 2021-04-29 05:28:14 [35121] [6] DEBUG:  data: 69 64 3a 37 32 36 34 37
> 33
> 33 37 20 73 75 62 3a   id:72647337 sub:
> 2021-04-29 05:28:14 [35121] [6] DEBUG:  data: 30 20 64 6c 76 72 64 3a
> 32
> 38 20 73 75 62 6d 69   0 dlvrd:28 submi
> 2021-04-29 05:28:14 [35121] [6] DEBUG:  data: 74 20 64 61 74 65 3a 32
> 31
> 30 34 32 39 30 32 32   t date:210429022
> 2021-04-29 05:28:14 [35121] [6] DEBUG:  data: 38 20 64 6f 6e 65 20 64
> 61
> 74 65 3a 32 31 30 34   8 done date:2104
> 2021-04-29 05:28:14 [35121] [6] DEBUG:  data: 32 39 30 32 32 38 20 73
> 74
> 61 74 3a 45 4e 52 4

DISCARDED SMS / NACK/Retries Exceeded

[Web Min]

Hello,

I've spent a significant amount of time around this issue. I couldn't find
any solution or hint on why getting DISCARDED SMS as below:

2021-05-02 00:25:30 2021-05-02 00:25:30 DISCARDED SMS [SMSC:] [SVC:] [ACT:]
[BINF:] [FID:26][from:SellerAJ] [to:1946873251] [flags:-1:2:-1:-1:31]
[msg:0:] [udh:0:]
2021-05-02 00:25:30 2021-05-02 00:25:30 Receive DLR [SMSC:] [SVC:] [ACT:]
[BINF:] [FID:26][from:SellerAJ] [to:1946873251] [flags:-1:-1:-1:-1:16]
[msg:12:NACK/no SMSC] [udh:0:]
2021-05-02 00:26:30 2021-05-02 00:25:30 DISCARDED SMS [SMSC:MySMSC] [SVC:]
[ACT:] [BINF:] [FID:25][from:SellerAJ] [to:1946873251]
[flags:-1:2:-1:-1:31] [msg:0:] [udh:0:]
2021-05-02 00:26:30 2021-05-02 00:26:30 Receive DLR [SMSC:MySMSC] [SVC:]
[ACT:] [BINF:] [FID:25][from:SellerAJ] [to:1946873251]
[flags:-1:-1:-1:-1:16] [msg:21:NACK/Retries Exceeded] [udh:0:]

It is straightforward and it was working well with the same configuration
since the last incident in STRASBOURG

I'm connecting to SMPP using MySQL database and routing to the defined SMSC

Kannel --> sqlbox ->  bearerbox -> smsc

Here is the configuration:

kannel.conf

# core
group = core
admin-port = 13000
smsbox-port = 13001
wapbox-port = 13002
store-type = spool
store-location = /var/spool/kannel/store
dlr-storage = mysql
box-deny-ip = "*.*.*.*"
box-allow-ip = "127.0.0.1"
sms-resend-freq = 30
sms-resend-retry = 2
sms-incoming-queue-limit = "-1"
sms-outgoing-queue-limit = 999
smsbox-max-pending = 999
log-level=0
log-file = /var/log/kannel/core.log
access-log = /var/log/kannel/access-core.log
access-log-format="%t %l [SMSC:%i] [SVC:%n] [ACT:%A] [BINF:%B]
[FID:%F][from:%p] [to:%P] [flags:%m:%c:%M:%C:%d] [msg:%L:%b] [udh:%U:%u]"


# dlr setup
group = mysql-connection
id = mydlr
host = localhost
port = 3306
username = root
password = rootpassword
database = my_db
max-connections = 25

# dlr table structure
group = dlr-db
id = mydlr
table = dlr
field-smsc=dlr_smsc
field-timestamp=dlr_timestamp
field-destination=dlr_destination
field-source=dlr_source
field-service=dlr_service
field-url=dlr_url
field-mask=dlr_mask
field-status=dlr_status
field-boxc-id=dlr_boxc_id


# smsbox
group = smsbox
bearerbox-host = localhost
bearerbox-port = 13001
sendsms-port = 13301
global-sender = 001
sendsms-chars = "0123456789+ "
mo-recode = true
http-request-retry = 10
http-queue-delay = 60
immediate-sendsms-reply = true
log-level = 0
log-file = /var/log/kannel/smsbox.log
access-log = /var/log/kannel/access-smsbox.log


group = sendsms-user
default-smsc = MySMSC
forced-smsc = MySMSC
username = user
password = password
max-messages = 1000
concatenation = true

# SMS-SERVICE
group = sms-service
keyword = default
#accept-x-kannel-headers = true
#concatenation = true
#omit-empty = true
#catch-all = true
max-messages = 1000
#text = "Galaxy ROBOT by Zaib"
#get-url = "
http://localhost/playsms/index.php?app=call&cat=gateway&plugin=kannel&access=geturl&t=%t&q=%q&a=%a&Q=%Q&smsc=%i
"


# smsc
group = smsc
smsc = smpp
smsc-id = MySMSC
allowed-smsc-id = MySMSC
preferred-smsc-id = MySMSC
interface-version = 34
allowed-prefix = 1
host = xx.xx.xx.xx
port = 9876
receive-port = 0
smsc-username = smscuser
smsc-password = smscpass
system-type = sysType
source-addr-ton = 5
source-addr-npi = 1
dest-addr-ton = 0
dest-addr-npi = 0
keepalive = 600
reconnect-delay = 3
enquire-link-interval = 30
max-pending-submits = 1
log-level = 0
log-file = /var/log/kannel/smsc-transmitter.log
msg-id-type = 0x01
throughput = 50
wait-ack = 240
wait-ack-expire = 0x00

Any idea would be appearited.

Re: DISCARDED SMS / NACK/Retries Exceeded

[Web Min]

It is already in the SMSC before the host

allowed-prefix = 1

Any Idea please

On Tue, May 25, 2021 at 4:10 AM Mesbahuddin Malik 
wrote:

> Hello,
>   where is your allowed prefix in SMSC ?
>
> Regards
> Mesbah
>
> On Mon, May 24, 2021 at 7:06 PM Web Min  wrote:
>
>> Hello,
>>
>> I've spent a significant amount of time around this issue. I couldn't
>> find any solution or hint on why getting DISCARDED SMS as below:
>>
>> 2021-05-02 00:25:30 2021-05-02 00:25:30 DISCARDED SMS [SMSC:] [SVC:]
>> [ACT:] [BINF:] [FID:26][from:SellerAJ] [to:1946873251]
>> [flags:-1:2:-1:-1:31] [msg:0:] [udh:0:]
>> 2021-05-02 00:25:30 2021-05-02 00:25:30 Receive DLR [SMSC:] [SVC:] [ACT:]
>> [BINF:] [FID:26][from:SellerAJ] [to:1946873251] [flags:-1:-1:-1:-1:16]
>> [msg:12:NACK/no SMSC] [udh:0:]
>> 2021-05-02 00:26:30 2021-05-02 00:25:30 DISCARDED SMS [SMSC:MySMSC]
>> [SVC:] [ACT:] [BINF:] [FID:25][from:SellerAJ] [to:1946873251]
>> [flags:-1:2:-1:-1:31] [msg:0:] [udh:0:]
>> 2021-05-02 00:26:30 2021-05-02 00:26:30 Receive DLR [SMSC:MySMSC] [SVC:]
>> [ACT:] [BINF:] [FID:25][from:SellerAJ] [to:1946873251]
>> [flags:-1:-1:-1:-1:16] [msg:21:NACK/Retries Exceeded] [udh:0:]
>>
>> It is straightforward and it was working well with the same configuration
>> since the last incident in STRASBOURG
>>
>> I'm connecting to SMPP using MySQL database and routing to the defined
>> SMSC
>>
>> Kannel --> sqlbox ->  bearerbox -> smsc
>>
>> Here is the configuration:
>>
>> kannel.conf
>>
>> # core
>> group = core
>> admin-port = 13000
>> smsbox-port = 13001
>> wapbox-port = 13002
>> store-type = spool
>> store-location = /var/spool/kannel/store
>> dlr-storage = mysql
>> box-deny-ip = "*.*.*.*"
>> box-allow-ip = "127.0.0.1"
>> sms-resend-freq = 30
>> sms-resend-retry = 2
>> sms-incoming-queue-limit = "-1"
>> sms-outgoing-queue-limit = 999
>> smsbox-max-pending = 999
>> log-level=0
>> log-file = /var/log/kannel/core.log
>> access-log = /var/log/kannel/access-core.log
>> access-log-format="%t %l [SMSC:%i] [SVC:%n] [ACT:%A] [BINF:%B]
>> [FID:%F][from:%p] [to:%P] [flags:%m:%c:%M:%C:%d] [msg:%L:%b] [udh:%U:%u]"
>>
>>
>> 
>> # dlr setup
>> group = mysql-connection
>> id = mydlr
>> host = localhost
>> port = 3306
>> username = root
>> password = rootpassword
>> database = my_db
>> max-connections = 25
>>
>> # dlr table structure
>> group = dlr-db
>> id = mydlr
>> table = dlr
>> field-smsc=dlr_smsc
>> field-timestamp=dlr_timestamp
>> field-destination=dlr_destination
>> field-source=dlr_source
>> field-service=dlr_service
>> field-url=dlr_url
>> field-mask=dlr_mask
>> field-status=dlr_status
>> field-boxc-id=dlr_boxc_id
>>
>>
>> 
>> # smsbox
>> group = smsbox
>> bearerbox-host = localhost
>> bearerbox-port = 13001
>> sendsms-port = 13301
>> global-sender = 001
>> sendsms-chars = "0123456789+ "
>> mo-recode = true
>> http-request-retry = 10
>> http-queue-delay = 60
>> immediate-sendsms-reply = true
>> log-level = 0
>> log-file = /var/log/kannel/smsbox.log
>> access-log = /var/log/kannel/access-smsbox.log
>>
>>
>> 
>> group = sendsms-user
>> default-smsc = MySMSC
>> forced-smsc = MySMSC
>> username = user
>> password = password
>> max-messages = 1000
>> concatenation = true
>>
>> 
>> # SMS-SERVICE
>> group = sms-service
>> keyword = default
>> #accept-x-kannel-headers = true
>> #concatenation = true
>> #omit-empty = true
>> #catch-all = true
>> max-messages = 1000
>> #text = "Galaxy ROBOT by Zaib"
>> #get-url = "
>> http://localhost/playsms/index.php?app=call&cat=gateway&plugin=kannel&access=geturl&t=%t&q=%q&a=%a&Q=%Q&smsc=%i
>> "
>>
>>
>> 
>> # smsc
>> group = smsc
>> smsc = smpp
>> smsc-id = MySMSC
>> allowed-smsc-id = MySMSC
>> preferred-smsc-id = MySMSC
>> interface-version = 34
>> allowed-prefix = 1
>> host = xx.xx.xx.xx
>> port = 9876
>> receive-port = 0
>> smsc-username = smscuser
>> smsc-password = smscpass
>> system-type = sysType
>> source-addr-ton = 5
>> source-addr-npi = 1
>> dest-addr-ton = 0
>> dest-addr-npi = 0
>> keepalive = 600
>> reconnect-delay = 3
>> enquire-link-interval = 30
>> max-pending-submits = 1
>> log-level = 0
>> log-file = /var/log/kannel/smsc-transmitter.log
>> msg-id-type = 0x01
>> throughput = 50
>> wait-ack = 240
>> wait-ack-expire = 0x00
>>
>> Any idea would be appearited.
>>
>

Arabic & English SMS using SQLBOX - problem in encoding

[Web Min]

Dear Experts,

I would appreciate it if anyone can assist with the below concern.

I am trying to send Arabic & English SMS from kannel using SQLBOX, and it
does not deliver perfectly (receiving it as ?? for Arabic words); after
doing some analysis on the values sent between the Bearebox, SMS BOX, and
SMSC, I found out that the error in encoding happens when SMSC start
transmitting.

I have used charset=utf-8 and coding=2 on SQLBOX database request when
inserting SMS

Does anyone have any idea what the problem? Although I have no problem in
receiving the SMS in English with the charset UTF-8.

Regards

Re: DISCARDED SMS / NACK/Retries Exceeded

[Web Min]

Hello Stipe,

The problem is solved, it wasn't related to the SMSC configuration, I have
defied another SMSC, and when I sent it, I got an error message related to
the text field is null because I'm using SQLBOX the msgdata was empty.
After I fixed it I was able to send it without any problems unless the long
message.

I'm using the UTF-8 with the coding = 2, when I send an Arabic Message with
less than 70 chars it sent it with no issue, but when I send a message
length 240 chars the smsc log showing more_messages_to_send: 1 = 0x0001
and stuck without delivery.

Any suggestion please let me know.

Regards

On Sat, May 29, 2021 at 11:41 AM Stipe Tolj  wrote:

> Am 25.05.21, 09:54, schrieb Web Min:
> > It is already in the SMSC before the host
> >
> > allowed-prefix = 1
>
> when your users inject as destination addr 1xxx that is fine, but if
> they use a international prefixed addr +1xxx that would not be able to
> pass via the configured SMSC then.
>
> this would then yield the following code block in
> gw/bb_smsconn.c:smsc2_rout():
>
>  } else {
>  gw_rwlock_unlock(&smsc_list_lock);
>  if (bb_status == BB_SHUTDOWN) {
>  msg_destroy(msg);
>  return SMSCCONN_QUEUED;
>  }
>  warning(0, "Cannot find SMSCConn for message to <%s>, rejected.",
>  octstr_get_cstr(msg->sms.receiver));
>  bb_smscconn_send_failed(NULL, msg_duplicate(msg),
> SMSCCONN_FAILED_DISCARDED, octstr_create("no SMSC"));
>  return SMSCCONN_FAILED_DISCARDED;
>  }
>
> check if you can see this WARNING entry in the log, to double check.
>
> --
> Best Regards,
> Stipe Tolj
>
> ---
> Düsseldorf, NRW, Germany
>
> Kannel Foundation tolj.org system architecture
> http://www.kannel.org/http://www.tolj.org/
>
> st...@kannel.org  s...@tolj.org
> ---
>
>

registered_delivery could be a bug in 1.5.0

[Web Min]

Hello,

I'm using 1.5.0, I have reported a problem to my gateway to check from
their side why I'm not receiving the DLR Report, I surprised when
replied that they are receiving the registered_delivery = 0 although it is
showing from the SMSC transmitter log.

2021-05-29 15:09:49 [10316] [6] DEBUG: SMPP PDU 0x7ff53800e060 dump:
2021-05-29 15:09:49 [10316] [6] DEBUG:   type_name: submit_sm
2021-05-29 15:09:49 [10316] [6] DEBUG:   command_id: 4 = 0x0004
2021-05-29 15:09:49 [10316] [6] DEBUG:   command_status: 0 = 0x
2021-05-29 15:09:49 [10316] [6] DEBUG:   sequence_number: 58 = 0x003a
2021-05-29 15:09:49 [10316] [6] DEBUG:   service_type: NULL
2021-05-29 15:09:49 [10316] [6] DEBUG:   source_addr_ton: 5 = 0x0005
2021-05-29 15:09:49 [10316] [6] DEBUG:   source_addr_npi: 0 = 0x
2021-05-29 15:09:49 [10316] [6] DEBUG:   source_addr: "SenderID"
2021-05-29 15:09:49 [10316] [6] DEBUG:   dest_addr_ton: 0 = 0x
2021-05-29 15:09:49 [10316] [6] DEBUG:   dest_addr_npi: 0 = 0x
2021-05-29 15:09:49 [10316] [6] DEBUG:   destination_addr: "123456789"
2021-05-29 15:09:49 [10316] [6] DEBUG:   esm_class: 3 = 0x0003
2021-05-29 15:09:49 [10316] [6] DEBUG:   protocol_id: 0 = 0x
2021-05-29 15:09:49 [10316] [6] DEBUG:   priority_flag: 3 = 0x0003
2021-05-29 15:09:49 [10316] [6] DEBUG:   schedule_delivery_time: NULL
2021-05-29 15:09:49 [10316] [6] DEBUG:   validity_period: NULL
2021-05-29 15:09:49 [10316] [6] DEBUG:   *registered_delivery: 1 =
0x0001*
2021-05-29 15:09:49 [10316] [6] DEBUG:   replace_if_present_flag: 0 =
0x
2021-05-29 15:09:49 [10316] [6] DEBUG:   data_coding: 8 = 0x0008
2021-05-29 15:09:49 [10316] [6] DEBUG:   sm_default_msg_id: 0 = 0x
2021-05-29 15:09:49 [10316] [6] DEBUG:   sm_length: 38 = 0x0026
2021-05-29 15:09:49 [10316] [6] DEBUG:   short_message:
2021-05-29 15:09:49 [10316] [6] DEBUG:Octet string at 0x7ff538012350:
2021-05-29 15:09:49 [10316] [6] DEBUG:  len:  38
2021-05-29 15:09:49 [10316] [6] DEBUG:  size: 39
2021-05-29 15:09:49 [10316] [6] DEBUG:  immutable: 0
2021-05-29 15:09:49 [10316] [6] DEBUG:  data: 00 74 00 65 00 73 00 74
00 20 00 6d 00 65 00 73   .t.e.s.t. .m.e.s
2021-05-29 15:09:49 [10316] [6] DEBUG:  data: 00 73 00 61 00 67 00 65
00 0d 00 0a 06 2a 06 2c   .s.a.g.e.*.,
2021-05-29 15:09:49 [10316] [6] DEBUG:  data: 06 31 06 28 06 29
.1.(.)
2021-05-29 15:09:49 [10316] [6] DEBUG:Octet string dump ends.
2021-05-29 15:09:49 [10316] [6] DEBUG: SMPP PDU dump ends.
2021-05-29 15:09:49 [10316] [6] DEBUG: SMPP[MySMSC]: throughput (1.00,50.00)
2021-05-29 15:09:49 [10316] [6] DEBUG: SMPP[MySMSC]: throughput (1.00,50.00)
2021-05-29 15:09:49 [10316] [6] DEBUG: SMPP[MySMSC]: Got PDU:
2021-05-29 15:09:49 [10316] [6] DEBUG: SMPP PDU 0x7ff53800e060 dump:

Re: registered_delivery could be a bug in 1.5.0

[Web Min]

Hello,

Unfortunately, I have the same SMSC configuration; I'm able to transmit via
the first gateway a message concatenated 4 msgs long, and I'm able to
receive the submit_sm_resp, unlike from the second gateway, it won't
transmit a message long 4 msgs using the SQLBOX  and UTF-8 chars.

Furthermore: it successfully works for a single message, and I'm able to
receive it.

Further assistance would be appreciated.

Regards

On Fri, Jun 4, 2021 at 4:02 PM Stipe Tolj  wrote:

> Am 29.05.21, 21:44, schrieb Web Min:
> > Hello,
> >
> > I'm using 1.5.0, I have reported a problem to my gateway to check from
> > their side why I'm not receiving the DLR Report, I surprised when
> > replied that they are receiving the registered_delivery = 0 although it
> > is showing from the SMSC transmitter log.
> >
> > 2021-05-29 15:09:49 [10316] [6] DEBUG: SMPP PDU 0x7ff53800e060 dump:
> > 2021-05-29 15:09:49 [10316] [6] DEBUG:   type_name: submit_sm
> > 2021-05-29 15:09:49 [10316] [6] DEBUG:   command_id: 4 = 0x0004
> > 2021-05-29 15:09:49 [10316] [6] DEBUG:   command_status: 0 = 0x
> > 2021-05-29 15:09:49 [10316] [6] DEBUG:   sequence_number: 58 = 0x003a
> > 2021-05-29 15:09:49 [10316] [6] DEBUG:   service_type: NULL
> > 2021-05-29 15:09:49 [10316] [6] DEBUG:   source_addr_ton: 5 = 0x0005
> > 2021-05-29 15:09:49 [10316] [6] DEBUG:   source_addr_npi: 0 = 0x
> > 2021-05-29 15:09:49 [10316] [6] DEBUG:   source_addr: "SenderID"
> > 2021-05-29 15:09:49 [10316] [6] DEBUG:   dest_addr_ton: 0 = 0x
> > 2021-05-29 15:09:49 [10316] [6] DEBUG:   dest_addr_npi: 0 = 0x
> > 2021-05-29 15:09:49 [10316] [6] DEBUG:   destination_addr: "123456789"
> > 2021-05-29 15:09:49 [10316] [6] DEBUG:   esm_class: 3 = 0x0003
> > 2021-05-29 15:09:49 [10316] [6] DEBUG:   protocol_id: 0 = 0x
> > 2021-05-29 15:09:49 [10316] [6] DEBUG:   priority_flag: 3 = 0x0003
> > 2021-05-29 15:09:49 [10316] [6] DEBUG:   schedule_delivery_time: NULL
> > 2021-05-29 15:09:49 [10316] [6] DEBUG:   validity_period: NULL
> > 2021-05-29 15:09:49 [10316] [6] DEBUG: *registered_delivery: 1 =
> 0x0001*
>
> if this is the SMPP PDU dump from the bearebox, then this is what we ARE
> SENDING.
>
> If they object, they may provide a tcpdump trace of the traffic,
> including the submit_sm_resp PDU showing the message_id, then you can
> simply compare what you have on the wire.
>
> OR, you do the tcpdump scan on your own, so you know what is on the wire
> when the TCP packets are going towards the SMSC.
>
> Assuming that there is no IP router that will do SMPP
> deep-packet-inspection and modification, this is what they SHOULD
> receive too then.
>
> Stipe
>
> --
> Best Regards,
> Stipe Tolj
>
> ---
> Düsseldorf, NRW, Germany
>
> Kannel Foundation tolj.org system architecture
> http://www.kannel.org/http://www.tolj.org/
>
> st...@kannel.org  s...@tolj.org
> ---
>
>

Re: [RIP] Remembering René Kluwen

[Web Min]

Sad incident. RIP Rene

On Fri, Jun 11, 2021 at 6:13 PM Alvaro Cornejo 
wrote:

> Really sad to hear this.
>
> He might rest in peace forever!!!
>
> We will continue to have him around into his code.
>
>
> ||
>  Stay safe / Cuídate/  Reste sécurisé
> *7* Switch off as you go / Apaga lo que no usas /  Débranchez au fur et à
> mesure.
>  *q *Recycle always / Recicla siempre / Recyclez toujours
>  P Print only if absolutely necessary / Imprime solo si es necesario /
> Imprimez seulement si nécessaire
>
>
> Le ven. 11 juin 2021 à 10:07, Mpeirwe Benjamin  a
> écrit :
>
>> So SAD. RIP Rene.
>> "The Scientist explores what is,
>> the Engineer creates what has never been."
>> Theodore von Karman
>>
>>
>>
>> On Fri, Jun 11, 2021 at 6:04 PM M Sleem  wrote:
>>
>>> I am so sad to hear that. My deep condolences. Hope he is in better
>>> place.
>>>
>>> On Fri, Jun 11, 2021, 17:37 Donald Jackson 
>>> wrote:
>>>
 RIP Rene - will be truly missed and his contributions were used by many
 across this community.

 On Fri, 11 Jun 2021 at 16:27, tulip neo  wrote:

> Sorry to hear about this.for some years I was not in touch with Rene
> but in the period of 2005-2010 when ever I triggered any query got
> immediate response from stipe n rene.
> Sorry to hear about this.
> Can any one let me know what exactly happened.
> Regards
> Neo
>
> Sent from Yahoo Mail on Android
> 
>
> On Fri, 11 Jun 2021 at 19:29, Web Services
>  wrote:
> It's very sad incident
>
> RIP Rane
>
> We will always remember your great contribution
>
> On Fri, 11 Jun, 2021, 6:33 pm Stipe Tolj,  wrote:
>
> Dear all,
>
> With deep regret and sorrow we let you know that René Kluwen, one of
> Kannel core developers has passed away this week. René has been a
> wonderful character and person, a father and a long year active
> supporter of the Kannel project. His work contributed to the main
> gateway module, the sqlbox and opensmppbox sub-modules, along with
> most
> valued discussions in our mailing list groups. Some of us have been
> friends with René and we’re heavily shaken by the news.
>
> We will miss him, and we would like to express our sincerely
> condolences
> to his family.
>
> Like in the hearts and minds of his family, his persona will keep on
> living in his work he contributed with passion to our project.
> Honoring
> his contributions is our privilege and determination.
>
> Rest in peace René Kluwen (* 10-05-1970, ✝ 06-06-2021)
>
> https://kannel.org/images/rouwkaart_rene.png
>
>
> --
> Best Regards,
> Stipe Tolj
>
> ---
> Düsseldorf, NRW, Germany
>
> Kannel Foundation tolj.org system architecture
> http://www.kannel.org/http://www.tolj.org/
>
> st...@kannel.org  s...@tolj.org
> ---
>
>

 --
 Donald Jackson

>>>

Re: Decode Optional Parameters in deliver_sm TLV

[Web Min]

The best choice is to use the latest user guide
https://www.kannel.org/download/kannel-userguide-snapshot/userguide.html

Regards

On Mon, Jul 5, 2021 at 10:32 AM Srujan Kumar Kunchakara <
srujankunchak...@gmail.com> wrote:

> I want the code to decode optional parameters received in deliver_sm
> I received 0zx1452 and want to use that values received in that kannel
> code.
>
> [image: image.png]
>

Re: Kannel :: How can I filter incoming traffic

[Web Min]

Hello,

I'm using the allowed-prefix in the SMSC group to guarantee using the
allocated gateway.

Refer to the document for more information.

Good luck

On Thu, Dec 9, 2021 at 1:56 AM Loyc Cossou  wrote:

> Hi,
> I use Kannel as SMS gateway - It works fine for me. I am connnected one
> operator and I provide SMPP COnnections to my clients. All works fine.
> But now I need to filter the traffic based on the recipient number ie I
> need to be able to set a REGEX for the receipient and reject the SMS if
> it's supposed to be sent to those recipients.
> Is this possible in Kannel? Any idea of how this can be done?
>
> #Kannel
>
> Thank you.
>
> --
> loyc Cossou
>
> [image: Mailtrack]
> 
>  Sender
> notified by
> Mailtrack
> 
>  09/12/21,
> 00:54:55
>

Re: FREE BULK SMS FRONT END APPLICATION

[Web Min]

Is there any online version?

In which PHP Framework was built?

On Wed, Nov 30, 2022 at 6:49 AM Textnator Support 
wrote:

>
> https://drive.google.com/file/d/1ExpJAeWDMlK1FPpM4Jbbt9fBbK3Bmms7/view?usp=drive_web
>
> On Tue, Nov 29, 2022 at 7:23 PM MOSES KARIUKI  wrote:
>
>> Hello Textnator,
>>
>> I am interested.
>>
>> Regards,
>> Moses K
>>
>> On Mon, Nov 14, 2022 at 11:12 AM Textnator Support 
>> wrote:
>>
>>> Hi,
>>> If anybody wants free bulk sms,voice,smpp source code pls reply to my
>>> email,it's an old one,not updated but currently used by some companies.
>>>
>>> PHP5.6 you can try with newer versions
>>> Zend 1.12 With Doctrine ORM
>>> Mysql 5.7
>>> Backend is Kannel, Sqlbox and Asterisk which is not included, you can
>>> install and configure from their website.
>>>
>>> Features
>>> DYNAMIC ROLE AND RESOURCE
>>> CREDIT SYSTEM
>>> WHITE LABELLED RESELLER
>>> WITH PERCENTAGE CUTTING(FAKE REPORT)
>>> SMS
>>> VOICE
>>> SMPP
>>> TINY URL
>>> ADD SMSC
>>> MONITOR
>>> LOGS
>>> MULTIPLE VIEW TEMPLATE FOR RESELLERS
>>>
>>