Re: SMSBOX not starting with PANIC

[Vangelis Typaldos]

You need first to start bearerbox before starting smsbox.

Best Regards,

Αποκτήστε το Outlook για Android

From: users  on behalf of Norbert Kwizera 

Sent: Wednesday, December 15, 2021 9:07:33 PM
To: users@kannel.org 
Subject: SMSBOX not starting with PANIC

Hey All,

We run a kannel instances with multiple connections and to increase the 
throughput for each we found that we can set multiple instances for each 
connection

We have no issue when we set the instances to 5 however
we have an issue when we set that to 10, starting kannel service fails with the 
error below

2021-12-14 10:39:14 [4089406] [0] ERROR: connect to <127.0.0.1> failed
2021-12-14 10:39:14 [4089406] [0] ERROR: System error 111: Connection refused
2021-12-14 10:39:14 [4089406] [0] ERROR: error connecting to server `localhost' 
at port `13001'
2021-12-14 10:39:14 [4089406] [0] PANIC: Couldn't connect to the bearerbox.
2021-12-14 10:39:14 [4089406] [0] PANIC: 
/usr/local/sbin/smsbox(gw_backtrace+0xf0) [0x5557e89e6fc0]
2021-12-14 10:39:14 [4089406] [0] PANIC: /usr/local/sbin/smsbox(gw_panic+0x167) 
[0x5557e89e7137]
2021-12-14 10:39:14 [4089406] [0] PANIC: /usr/local/sbin/smsbox(main+0xead) 
[0x5557e89b4b8d]
2021-12-14 10:39:14 [4089406] [0] PANIC: 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0x7ffb41e3e0b3]
2021-12-14 10:39:14 [4089406] [0] PANIC: /usr/local/sbin/smsbox(_start+0x2e) 
[0x5557e89b560e]

The kannel.conf  is

#*
# Core Config
#*
group = core
admin-port = 13000
smsbox-port = 13001
admin-password = X
admin-deny-ip = "*.*.*.*"
admin-allow-ip = "127.0.0.1"
wdp-interface-name = "*"
log-file = "/var/log/kannel/kannel.log"
log-level = 1
store-type = spool
store-location = "/var/kannel/spooled"
sms-resend-retry = 10
sms-outgoing-queue-limit = 1000
box-allow-ip = "127.0.0.1"
box-deny-ip = "*.*.*.*"

#*
# SMS Box Config
#*
group = smsbox
bearerbox-host = localhost
sendsms-port = 13013
log-file = "/var/log/kannel/smsbox.log"
log-level = 1
mo-recode = true

include = "/etc/kannel.d/"

And each connection has config such as below

##
# operator X
##
group   = smsc
smsc= smpp
host = 192.168.14.14
port = 9000
smsc-username = FOO
smsc-password = BAR
transceiver-mode = true
window = 1
throughput = 40
system-type = "SMPP"
smsc-id = operator_x
allowed-smsc-id = operator_x
log-level = 0
log-file = "/var/log/kannel/operator_x.log"
address-range = ""
interface-version = "34"
instances = 10

Is there a maximum number of connections we can have at the same at the same 
time?

Thanks

Re: UDH Support on OpenSMPPBox

[Vangelis Typaldos]

In my eyes it seems like a 7-byte udh header with 2 byte reference number that 
should be a valid smpp PDU.

Note sure that opensmppbox and kannel in general supports -byte reference 
numbers udh header but are quite valid in the smpp protocol - tipically used 
for high traffic environments to avoid duplicated udh headers in SMSC side.

Kind Regards
Vangelis

Sent from my BlackBerry 10 smartphone.
From: garz m
Sent: Δευτέρα, 25 Μαρτίου 2019 - 03:46
To: Davor Spasoski
Cc: users@kannel.org
Subject: Re: UDH Support on OpenSMPPBox


Hi Davor,

Thanks for the response. No, i'm not. I'm seeing ESME's seeing PDU like i'd 
shared more often now. I think their purpose is to notify via SMPP Apple 
devices.

Regards

On Thu, Mar 21, 2019 at 3:27 PM Davor Spasoski 
mailto:davor.spaso...@onevip.mk>> wrote:
Are you trying to reverse engineer iMessage? I don't think it uses MAP for that 
purpose. iMessage is available only on Wi-Fi/Cellular data, it’s something 
proprietary to Apple and I’d even be surprised if it’s related to RCS. Can you 
shed some light if you know the insights?

Cheers

On Mar 21, 2019, at 2:27 AM, garz m 
mailto:garz...@gmail.com>> wrote:

Dear Users,

Greetings!

Just like to consult if our Opensmppbox service supports Apple type Push 
Notification such as imessage and facetime? I have seen the correct UDH on the 
PDU however I found a - maybe an error that I hope you can help check. I'm 
sharing here the PDU captured:
==
DEBUG: SMPP: Got PDU:
DEBUG: SMPP PDU 0x7f1c10001270 dump:
DEBUG:   type_name: submit_sm
DEBUG:   command_id: 4 = 0x0004
DEBUG:   command_status: 0 = 0x
DEBUG:   sequence_number: 128203 = 0x0001f4cb
DEBUG:   service_type: NULL
DEBUG:   source_addr_ton: 1 = 0x0001
DEBUG:   source_addr_npi: 1 = 0x0001
DEBUG:   source_addr: ""
DEBUG:   dest_addr_ton: 1 = 0x0001
DEBUG:   dest_addr_npi: 1 = 0x0001
DEBUG:   destination_addr: ""
DEBUG:   esm_class: 67 = 0x0043
DEBUG:   protocol_id: 0 = 0x
DEBUG:   priority_flag: 0 = 0x
DEBUG:   schedule_delivery_time: NULL
DEBUG:   validity_period: NULL
DEBUG:   registered_delivery: 1 = 0x0001
DEBUG:   replace_if_present_flag: 0 = 0x
DEBUG:   data_coding: 4 = 0x0004
DEBUG:   sm_default_msg_id: 0 = 0x
DEBUG:   sm_length: 90 = 0x005a
DEBUG:   short_message:
DEBUG:Octet string at 0x7f1c100014d0:
DEBUG:  len:  90
DEBUG:  size: 91
DEBUG:  immutable: 0
DEBUG:  data: 06 05 04 15 79 00 00 42 66 78 20 32 34 20 73 75   y..Bfx 
24 su
DEBUG:  data: 20 61 69 64 6c 75 65 2e 20 3f 20 32 50 76 3d 20aidlue. ? 
2Pv=
DEBUG:  data: 35 39 31 20 33 2d 38 20 39 2b 52 53 72 33 45 52   591 3-8 
9+RSr3ER
DEBUG:  data: 20 38 3b 30 35 20 3d 33 6e 20 45 3d 33 20 34 318;05 =3n 
E=3 41
DEBUG:  data: 30 32 20 37 30 3d 20 31 31 33 73 20 36 42 3b 20   02 70= 113s 
6B;
DEBUG:  data: 47 38 34 3b 20 30 35 43 33 2e G84; 05C3.
DEBUG:Octet string dump ends.
DEBUG: SMPP PDU dump ends.
DEBUG: SMPP: UDH length read as 7
DEBUG: Found unknown IEI 5 with length 4
DEBUG: UDH was present, but no reference to multipart SMSs
DEBUG: Msg object at 0x7f1c10001a90:
DEBUG:  type: sms
DEBUG:  sms.sender:
DEBUG:  Octet string at 0x7f1c1000:
DEBUG:len:  13
DEBUG:size: 1024
DEBUG:immutable: 0
DEBUG:data: 2b +
DEBUG:  Octet string dump ends.
DEBUG:  sms.receiver:
DEBUG:  Octet string at 0x7f1c1000:
DEBUG:len:  13
DEBUG:size: 1024
DEBUG:immutable: 0
DEBUG:data: 2b +
DEBUG:  Octet string dump ends.
DEBUG:  sms.udhdata:
DEBUG:  Octet string at 0x7f1c100022e0:
DEBUG:len:  7
DEBUG:size: 8
DEBUG:immutable: 0
DEBUG:data: 06 05 04 15 79 00 00  y..
DEBUG:  Octet string dump ends.
DEBUG:  sms.msgdata:
DEBUG:  Octet string at 0x7f1c100014d0:
DEBUG:len:  83
DEBUG:size: 91
DEBUG:immutable: 0
DEBUG:data: 42 66 78 20 32 34 20 73 75 20 61 69 64 6c 75 65   Bfx 24 su 
aidlue
DEBUG:data: 2e 20 3f 20 32 50 76 3d 20 35 39 31 20 33 2d 38   . ? 2Pv= 591 
3-8
DEBUG:data: 20 39 2b 52 53 72 33 45 52 20 38 3b 30 35 20 3d9+RSr3ER 
8;05 =
DEBUG:data: 33 6e 20 45 3d 33 20 34 31 30 32 20 37 30 3d 20   3n E=3 4102 
70=
DEBUG:data: 31 31 33 73 20 36 42 3b 20 47 38 34 3b 20 30 35   113s 6B; G84; 
05
DEBUG:data: 43 33 2e  C3.
DEBUG:  Octet string dump ends.
DEBUG:  sms.time: 1552605905
DEBUG:  sms.smsc_id:
DEBUG:  sms.smsc_number:
DEBUG:  sms.foreign_id:
DEBUG:  sms.service:
DEBUG:  Octet string at 0x7f1c100022b0:
DEBUG:len:  4
DEBUG:size: 5
DEBUG:immutable: 0
DEBUG:data:
DEBUG:  Octet string dump ends.
DEBUG:  sms.account:
DEBUG:  

Re: Use cert chain in SSL settings

[Vangelis Typaldos]

It seems you are using an SNI certificate (that is, sharing multiple SSL hosts 
on a single IP address).
You should correct the openssl s_client command to

openssl s_client -showcerts -servername www.example.com -connect 
www.example.com:443

I'm not sure that kannel support SNI certificates though

Best Regards,


From: users  on behalf of Szalai Kálmán 

Sent: Tuesday, December 4, 2018 11:22 AM
To: users@kannel.org
Subject: Use cert chain in SSL settings


Dear All,



How can I set to use SSL in sendsms and admin and providing CA cert chain?



I used settings from documentation:



To use the SSL-enabled HTTP server please use the following configuration 
directive within the core and smsbox groups

group = core

...

ssl-server-cert-file = "filename"

ssl-server-key-file = "filename"



group = smsbox

...

sendsms-port-ssl = true



I tried to add my cert chain to ssl-server-cert-file file, but it is still 
providing only one cert, not the chain. I found ssl-trusted-ca-file option but 
it is not for server certs, isn’t it?



openssl s_client command output:



CONNECTED(0003)

depth=0 CN = *. example.hu

verify error:num=20:unable to get local issuer certificate

verify return:1

depth=0 CN = *.example.hu

verify error:num=21:unable to verify the first certificate

verify return:1

---

Certificate chain

0 s:/CN=*.example.hu

   i:/C=US/O=Cert Inc/OU=www.cert.com/CN=Cert RSA CA 2018



(domain name and cert retaled names were renamed.)



So is there any way to provide full cert chain via kannel configuration?





Thank you in advance!



Best regards,

KAMI

Ez a levél vírus- és spammentes. | This e-mail is virus-free.

Re: Messages with more than 160 Characters

[Vangelis Typaldos]

If the sms is splitted in an external app, so you add the proper udh headers 
and submitted to kannel as single part sms and you request delivery report for 
each of them you will receive both dlrs.

If you send to kannel the long sms via sendsms, kannel will perform the 
required splitting properly but will request for dlr only for the first part. 
At least this occurs for kannel v.1.5.0. Not sure for the latest releases 1.4.x

Kind Regards,


Sent from my BlackBerry 10 smartphone.
From: Robin C
Sent: Τρίτη, 23 Οκτωβρίου 2018 - 13:41
To: users@kannel.org
Subject: Messages with more than 160 Characters


Hi,

I am having trouble in fetching the DLR report of messages with more than 160 
characters. More than 160 character messages having two message IDs. But the 
DLR report comes for only one message ID. How is it possible to map the DLR for 
both the messages? Or is it possible to send more than 160 character messages 
with a single message ID?


--
 Thanks & Regards,



  Robin






Disclaimer:  This message contains confidential information and is intended 
only for the individual named.  If you are not the named addressee you should 
not disseminate, distribute or copy this e-mail.  Please notify the sender 
immediately by e-mail if you have received this e-mail by mistake and delete 
this e-mail from your system.  E-mail transmission cannot be guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents of this 
message, which arise as a result of e-mail transmission.  If verification is 
required please request a hard-copy version.

7 Switch off as you go |q Recycle always | P Print only if absolutely necessary

Re: Queue in Store

[Vangelis Typaldos]

As far as you have a working kannel environment you should check for latency, 
retransmission, retries... A tcpdump would help you identify the source of 
issue.

BR
Vangelis

Sent from my BlackBerry 10 smartphone.
From: Robin C
Sent: Τετάρτη, 13 Δεκεμβρίου 2017 - 13:01
To: info.ubichip
Cc: users@kannel.org
Subject: Re: Queue in Store


Ok... Please find the details below.:
Kannel bearerbox version `1.4.4'. Build `Feb 10 2017 19:38:03', compiler `4.4.7 
20120313 (Red Hat 4.4.7-17)'. System Linux, release 2.6.32-696.1.1.el6.x86_64, 
version #1 SMP Tue Apr 11 17:13:24 UTC 2017, machine x86_64. Hostname 
CentOS-67-64-minimal, .Libxml version 2.7.6. Using OpenSSL 1.0.1e-fips 11 Feb 
2013. Compiled with MySQL 5.7.17, using MySQL 5.7.18. Using native malloc.



On Wed, Dec 13, 2017 at 4:28 PM, info.ubichip 
> wrote:

Hello,



In order to give a chance to the community to answer you, please provide at 
least a description of what you are using (kannel versio, opensmppbox, 
databse...etc).



Regards





De : users [mailto:users-boun...@kannel.org] 
De la part de Robin C
Envoyé : mercredi 13 décembre 2017 06:38
À : users@kannel.org
Objet : Queue in Store




Dear Team,



When we send large volume of sms the queue is building up in the store. And it 
process very slowly. Only getting 16 tps. Can anyone help me to solve this 
issue.?

--





Disclaimer:  This message contains confidential information and is intended 
only for the individual named.  If you are not the named addressee you should 
not disseminate, distribute or copy this e-mail.  Please notify the sender 
immediately by e-mail if you have received this e-mail by mistake and delete 
this e-mail from your system.  E-mail transmission cannot be guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents of this 
message, which arise as a result of e-mail transmission.  If verification is 
required please request a hard-copy version.

7 Switch off as you go |q Recycle always | P Print only if absolutely necessary



--




Disclaimer:  This message contains confidential information and is intended 
only for the individual named.  If you are not the named addressee you should 
not disseminate, distribute or copy this e-mail.  Please notify the sender 
immediately by e-mail if you have received this e-mail by mistake and delete 
this e-mail from your system.  E-mail transmission cannot be guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents of this 
message, which arise as a result of e-mail transmission.  If verification is 
required please request a hard-copy version.

7 Switch off as you go |q Recycle always | P Print only if absolutely necessary

Re: SMPP 3.4 Protocol: Concatenated Message Flow

[Vangelis Typaldos]

The only difference is that the payload is reduced from 140 bytes to 134 or 133 
bytes (1 or 2bytes reference number)  due to udh header.

BR
V.

From: Grant Saicom
Sent: Τρίτη, 21 Νοεμβρίου 2017 - 11:20
To: amal...@kannel.org
Cc: Kannel Users
Subject: Re: SMPP 3.4 Protocol: Concatenated Message Flow


That is what I thought. Thank you for confirmation.
On 21 Nov 2017, at 10:49, amal...@kannel.org wrote:

Hi,

there is submit_sm_resp for each submit_sm for concatenated message as well.

Thanks,
Alex


Am 21.11.2017 um 08:23 schrieb Grant Saicom 
>:

Hello Kannel Users

I have a question with regards to the signaling flow of a concatenated SMS.

Simplistically, when we send a single (successful) sms of less than 160 chars 
(gsm7) on an established bind, the ESME sends a single submit_sm to the SMSC, 
then the SMSC responds to the ESME with a submit_sm_resp for that message. 
According to a document I found at 
docs.nimta.com/SMPP_v3_4_Issue1_2.pdf,
 it says that for each submit_sm, there should be a submit_sm_resp (pages 21 - 
22).

What does the message flow look like when a message of more than 160 characters 
(concatenated message) is sent using GSM SMS User Data and UDH?

Is there a submit_sm_resp for each submit_sm or a single submit_sm_resp for the 
several submit_sm of the concatenated message?

Kind regards
Grant

Re: Unable to render line break [generic SMSC type]

[Vangelis Typaldos]

Try using \n as newline char.
Consider that you need to url-encode the text on sendsms api url

BR

Sent from my BlackBerry 10 smartphone.
From: Amir Mahmoud
Sent: Κυριακή, 30 Ιουλίου 2017 - 14:36
To: users
Subject: Re: Unable to render line break [generic SMSC type]


Hello,

Had anyone encountered this issue ? is it bug in rendering the line break while 
using generic SMSC type ?

Regards,
Amir

On 25 July 2017 at 21:32, Amir Mahmoud 
> wrote:
Hello dears,

My kannel GW is configured with generic system-type directive in the SMSC group 
to propagate the submitted SMSs to HTTP server.

It works properly but seems having problem in propagating the SMSs that contain 
line break chars.

I'm trying to send this sms
"test1
test2
test3"

The bearerbox log shows that the sms received properly,
2017-07-25 20:36:35 FAILED Send SMS [SMSC:generic1] [SVC:vfbulk] [ACT:] 
[BINF:] [FID:] [META:] [from:Test1] [to:201x] [flags:-1:2:-1:-1:-1] 
[msg:38:00740065007300740031000D000A00740065007300740032000D000A00740065007300740033]
 [udh:0:]


But the access log of my HTTP server shows that the propagated SMS from kannel 
is,
"%00t%00e%00s%00t%001%00+%00+%00t%00e%00s%00t%002%00+%00+%00t%00e%00s%00t%003"

I have no idea why kannel replaces line break chars with space chars, Do you 
have any insights about what may cause this issus ?

Regards,
Amir

Re: Opensmppbox Issue

[Vangelis Typaldos]

Rene which was the issue? I have the same issue and these garbage generate nack 
pdu to the client and disconnections.

BR


Από: René Kapayo
Αποστολή: Πέμπτη, 6 Απριλίου 2017 11:18
Προς: Stipe Tolj
Κοιν.: users@kannel.org
Θέμα: Re: Opensmppbox Issue

Hi Stipe,
Sorry for delay.
The issue was resolved.
Thanks

2017-04-05 15:48 GMT+01:00 Stipe Tolj 
>:
Am 05.04.17 03:25, schrieb Wan Md Arif Noor Bin. Wan Nizam:
Hi Rene,

I don’t quite understand what you mean by something different from smpp,
is there any way for me to trace which transaction / sequence was
causing this error, I already done a tcpdump but can’t really find
anything peculiar.

if you can share the tcpdump capture file to Rene and me, we can have a chance 
to look into it.

--
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
---




--
Rene KAPAYO
Ingenieur Informaticien
Certifié Prince 2 Fundation
Tél.(portable) : +236 75 20 25 79
Domicile (portable) : +236 77 06 40 43
B.P. 2533 Bangui
Republique Centrafricaine

RE: Kannel low throughput and high smsc queue though TPS unlimited at Telco

[Vangelis Typaldos]

Throughput is defined with *throughput* parameter in your smsc bind definition 
(is missing from your configuration).

Setup max-pending-submits in base of the smpp latency with your operator.

Regards,
Vangelis


From: Web Services
Sent: Wednesday, January 25, 2017 2:23 PM
To: Daniel
Cc: users@kannel.org
Subject: Re: Kannel low throughput and high smsc queue though TPS unlimited at 
Telco

Hi,

try with sqlbox we are using kannel with 4gb and 1 core processor it's provide 
us upto 150-200 TPS

thanks

On Wed, Jan 25, 2017 at 5:26 PM, Daniel 
> wrote:

Hi All,

I have been having serious queuing  on my SMSC binds.

The telco operator indicates that they have not limited our TPS but I can't 
seem to push more.

Kannel status page always show less than 2TPS and msgs are queued all day and 
night.

My setup is on a 48GB 16CORE machine and am using nginx php-fpm to receive dlrs.

How can I optimize my config to increase throughput..

Please find my config below:


#KannelConfiguration
group=core
admin-port  =
admin-password  =
admin-allow-ip  =*.*.*.*
smsbox-port =
log-file=/var/log/kannel.log
log-level   =5
access-log  =/var/log/access/kannel-access.log
access-log-clean=true
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]"
sms-resend-freq=3600
dlr-storage=spool
dlr-spool="/var/spool/kannel_dlr"
store-type=spool
store-location="/var/spool/kannel_spool"


## SMSC - 40 of these

group=smsc
smsc=smpp
smsc-id=TELCO
host= xx.xx.xx.xx
port=
transceiver-mode=true
smsc-username=username
smsc-password=password
source-addr-ton=0
dest-addr-ton=1
source-addr-npi=1
dest-addr-npi=1
system-type=
allowed-smsc-id=TELCO
max-pending-submits=400
wait-ack=600
wait-ack-expire=0x02
log-file="/var/log/telc_logs/smsc.log"

Will appreciate your help very much. Thanks

Regards,

RE: SMS REJECTED due to throttling

[Vangelis Typaldos]

On gw/smsc/smsc_smpp.c is defined smpp_status_to_smscconn_failure_reason that 
defines the retry policy in base of submit_sm_resp response.

As far as i can see SMPP_ESME_RTHROTTLED (throttling error) is marked as 
SMSCCONN_FAILED_TEMPORARILY so it should generate retry attempts.

Enable debug log on bearerbox and check for "SMSC returned error code" lines.

Regards,
Vangelis


static long smpp_status_to_smscconn_failure_reason(long status)
{
switch(status) {
case SMPP_ESME_RMSGQFUL:
case SMPP_ESME_RTHROTTLED:
case SMPP_ESME_RX_T_APPN:
case SMPP_ESME_RSYSERR:
return SMSCCONN_FAILED_TEMPORARILY;
break;

default:
return SMSCCONN_FAILED_REJECTED;
}
}



From: Fajar
Sent: Saturday, October 22, 2016 4:58 AM
To: Giulio Giovannini; 
users@kannel.org
Subject: Re: SMS REJECTED due to throttling

you'll need to reduce, by setting throughput. document doesn't say about 
temporary condition, it will discard it, but if you put delivery report url, it 
will call back with spesific status, in my setting, it is set as 16. my 
application will hit the message again, to queue in kannel...



From: Giulio Giovannini 
To: users@kannel.org
Sent: Friday, 21 October 2016, 23:22
Subject: SMS REJECTED due to throttling

Hi all,

I have recently moved some UCP connections from kannel 1.4 to kannel 1.5.

I am pretty sure that when kannel 1.4 received a NACK 04 (throttling) it 
considered it as temporary error and retried. Version 1.5 seems to consider it 
a permanent error and discards the SMS.

Have a look at this log sequence from bearer-access.log:

2016-10-21 09:31:25 REJECTED Send SMS [SMSC:FO_HQS] [SVC:C00127_001] 
[ACT:433f083f-209f-4f62-979f-ae82b5742c90] [BINF:] [FID:8609681] [META:] 
[from:J.UNIVERSE] [to:+33682412951] [flags:-1:0:-1:-1:11] [msg:159:xxx] [udh:0:]
2016-10-21 09:31:25 Receive DLR [SMSC:FO_HQS] [SVC:C00127_001] [ACT:] [BINF:] 
[FID:8609681] [META:?orig_msg?dlr_mask=11&] [from:J.UNIVERSE] [to:+33682412951] 
[flags:-1:-1:-1:-1:16] [msg:24:NACK/04-Throttling error] [udh:0:]

Should I set something in the conf to tell kannel that that error is temporary?

Thanks,
Giulio Giovannini

RE: Installing SQLBox

[Vangelis Typaldos]

Bootstrap should be only for debian/ubuntu OS. In Centos/RHEL use only 
./configure && make && make install

BR

From: Loyc Cossou
Sent: Friday, May 13, 2016 8:40 AM
To: users@kannel.org
Subject: Installing SQLBox

Hi.

I am trying to install SQLBox:

$ cd addons/sqlbox/
$ sudo ./bootstrap

+ set -e
+ amvers=no
+ automake-1.11 --version
+ automake-1.10 --version
+ automake-1.9 --version
+ automake-1.8 --version
+ automake-1.7 --version
+ automake-1.6 --version
+ automake-1.5 --version
+ automake --version
++ sed -e '1s/[^0-9]*//' -e q
++ automake --version
+ amvers=1.13.4
+ expr 1.13.4 '<' 1.5
+ amvers=no
+ test no = no
+ set +x
*./bootstrap: you need automake version 1.5 or later*


​It's saying I need to update automake up to ​1.15. I have currently 1.13.4
installer and it doesn't seem that 1.15 is available for my system. I am on
Amazon Linux which is kind of CentOs/RHEL.

Anyone already face this issue? Any suggestion?

Thank you.




--
loyc Cossou



Sent with MailTrack

RE: add kannel service to startup

[Vangelis Typaldos]

Include the below lines in a bash script and handle as a normal startup script 
for your linux environment.

cd /where/my/kannel.conf/lives
nohup ./bearerbox  &
nohup ./smsbox &

BR

From: John Mwale
Sent: Wednesday, May 11, 2016 4:33 PM
To: users@kannel.org
Subject: add kannel service to startup

good day ,

i am kindly asking how to add kannel services to startup. i will appreciate.

--
Tapiwa Mwale,
mobile number +260 97 9 947571

RE: Create SMS box for handling dlrs

[Vangelis Typaldos]

Dear Nanda,

Have you checked for latency/retransmissions?

Try to setup
max-pending-submits=100
in your smsc config.


BR
Vangelis

From: Nanda Kumar
Sent: Monday, April 25, 2016 7:34 PM
To: Alvaro Cornejo
Cc: users@kannel.org
Subject: Re: Create SMS box for handling dlrs

Hi Alvaro,
Thanks for the information. I'm currently interested in delivered and 
undelivered messages only. Hence my dlr-mask is 3. Please suggest what I need 
to do in order to get the expected throughput? Besides, the problem I face here 
is that the speeds reduce gradually due to which there is no predictability in 
how long it will take to send all my messages. Is there anything in the data 
structure used for the dlr registration at the bearer box that causes the 
sluggishness when more and more dlrs are getting registered ?
Thanks,Nanda

 Original message 
From: Alvaro Cornejo 
Date: 25/04/2016  19:27  (GMT+05:30)
To: Nanda Kumar P 
Cc: users@kannel.org
Subject: Re: Create SMS box for handling dlrs

Hi Nadar
Note that the dlr is a "specially crafted" sms therefore it consumes bandwidth. 
Each dlr, including intermediate ones, counts -in terms of throughput- as one 
message. This is more noticeable when using modems.
Also, as such the dlr handling consumes system resources.
Therefore you should carefully select which dlrs you are interested in.
Hope helps,
Alvaro


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

On Sun, Apr 24, 2016 at 12:20 AM, Nanda Kumar P  wrote:








Just to add.

I was wondering if it were possible to have two sms boxes, one for sending the 
sms and another that the bearer box uses to redirect only the delivery reports. 
Please let me know.

Thanks & Regards,
Nanda



From: Nanda Kumar P


Sent: 24 April 2016 10:41

To: 'users@kannel.org'

Subject: Create SMS box for handling dlrs



Hi,

I’m using one instance of bearer box and sms box each and I use kannel to send 
sms to the SMSC with delivery report parameters (dlr-mask & dlr-url) included 
in the send-sms url. I have no trouble functionality wise in sending the sms or
 getting the delivery. However, I do have a problem in the final throughput I 
see with and without delivery report. If I do not request for delivery report, 
the speeds are consistent at the rate of 300/sec which the throughput I have 
configured. However, when
 I use delivery reports, it starts with the expected throughput but gradually 
goes down to 25/sec or less.

Any idea why this could be? I use kannel 1.4.4

Thanks & Regards,
Nanda

RE: Kannel TPS reduces gradually if DLR is used

[Vangelis Typaldos]

For point 1: It sounds like you get DLR for multipart sms. Note that for 
multipart messages you receive DLR for each part.

For point 2: You are absolutely correct. Ignore my statement. My bad.

BR

From: Nanda Kumar P<mailto:nanda.ku...@pelatro.com>
Sent: Sunday, April 24, 2016 10:34 AM
To: Vangelis Typaldos<mailto:vty...@outlook.com>; 
users@kannel.org<mailto:users@kannel.org>
Subject: RE: Kannel TPS reduces gradually if DLR is used

Thank you Vangelis.

Few follow up questions though:

1.   While I understand the point about the throughput dropping to half, I 
fail to understand how it went as low as 25 per second.

2.   What is the significance of changing the dlr-mask from 3 to 7 or 15? 
Would it not lower the speeds further as it has to deal with calling the 
dlr-url for two other flags aside from delivered and undelivered?

Thanks & Regards,
Nanda

From: Vangelis Typaldos [mailto:vty...@outlook.com]
Sent: 24 April 2016 12:56
To: Nanda Kumar P; users@kannel.org
Subject: RE: Kannel TPS reduces gradually if DLR is used

The throughput assigned by your operator/smsc includes DLR activity.
So the actual bind throughput would drop to the half you if you request DLR for 
any MT. I would suggest to raise dlr-mask from 3 to 7 or 15.

Kind Regards,
Vangelis

From: Nanda Kumar P<mailto:nanda.ku...@pelatro.com>
Sent: Sunday, April 24, 2016 8:08 AM
To: users@kannel.org<mailto:users@kannel.org>
Subject: Kannel TPS reduces gradually if DLR is used


Hi,



I’m using kannel to send SMS to SMSC and in the send-sms url, I’m also using 
the dlr-mask as 3 (Delivered and undelivered) and providing a dlr-url callback 
for the same.

I have set the throughput as 300/sec.



If I do not use the delivery report, the TPS is consistent and close to 
300/sec. However, if I do use delivery report with the above said parameters, 
the TPS starts from 300 but gradually reduces to less than 25 per second. It 
would be great if someone can tell me what the reason for this could be.



Thanks & Regards,

Nanda

RE: Kannel TPS reduces gradually if DLR is used

[Vangelis Typaldos]

The throughput assigned by your operator/smsc includes DLR activity.
So the actual bind throughput would drop to the half you if you request DLR for 
any MT. I would suggest to raise dlr-mask from 3 to 7 or 15.

Kind Regards,
Vangelis

From: Nanda Kumar P
Sent: Sunday, April 24, 2016 8:08 AM
To: users@kannel.org
Subject: Kannel TPS reduces gradually if DLR is used

Hi,

I'm using kannel to send SMS to SMSC and in the send-sms url, I'm also using 
the dlr-mask as 3 (Delivered and undelivered) and providing a dlr-url callback 
for the same.
I have set the throughput as 300/sec.

If I do not use the delivery report, the TPS is consistent and close to 
300/sec. However, if I do use delivery report with the above said parameters, 
the TPS starts from 300 but gradually reduces to less than 25 per second. It 
would be great if someone can tell me what the reason for this could be.

Thanks & Regards,
Nanda

RE: Force DLR Request in OpenSMPP Kannel

[Vangelis Typaldos]

Dear Gorki,

Please refer to the kannel documentation.

Like with sendsms API, sqlbox will request for a delivery report to the smsc if 
you setup dlr-mask (with any valid value, not only 7) and define a dlr-url .

As per Rene comment I think this won’t be returned to the ESME client that is 
connected on opensmppbox , but the intermediation of sqlbox alter the original 
registered_delivery value of the submit_sm packet PDU requesting a delivery 
receipt from smsc.

The mentioned sql statement just set a default value for dlr-mask column(maps 
to registered_delivery value) in sendsms table.

BR
Vangelis

From: Gorki Alfaro<mailto:gork...@gmail.com>
Sent: Thursday, April 14, 2016 11:06 PM
To: Vangelis Typaldos<mailto:vty...@outlook.com>
Cc: Rene Kluwen<mailto:rene.klu...@chimit.nl>; 
users@kannel.org<mailto:users@kannel.org>
Subject: Re: Force DLR Request in OpenSMPP Kannel

Hello Friends

I have installed SQLBox between BearerBox and OpenSMPPBox, I will try
changing  the DRL-Mask to 7.
But how it works? How setting this value to 7 will force DRL Request to be
called?

Thanks for your answer,

Gorki

On Thu, Apr 14, 2016 at 2:47 AM, Vangelis Typaldos <vty...@outlook.com>
wrote:

>
>
> A solution could be to use a sqlbox between opensmppbox and bearerbox and
> set a default value for column dlr-mask  in your sendsms table
>
>
>
> ALTER TABLE sendsms ALTER COLUMN dlr-mask SET DEFAULT 7;
>
>
>
> BR
>
>
>
> *From: *Rene Kluwen <rene.klu...@chimit.nl>
> *Sent: *Thursday, April 14, 2016 10:11 AM
> *To: *'Gorki Alfaro' <gork...@gmail.com>; users@kannel.org
> *Subject: *RE: Force DLR Request in OpenSMPP Kannel
>
>
>
> I don’t think this is possible without changing the source code.
>
>
>
> *Van:* users [mailto:users-boun...@kannel.org] *Namens *Gorki Alfaro
> *Verzonden:* woensdag 13 april 2016 21:58
> *Aan:* users@kannel.org
> *Onderwerp:* Force DLR Request in OpenSMPP Kannel
>
>
>
> Hello friends
>
> Is there any way to enable a DLR request on OpenSMPP client even if this
> is not requested by the SMPP client (ESME)?
>
>
>
> I would like to keep record of the delivery success rate for billing and
> statistics purporses.
>
>
>
> Regards,
>
> Gorki
>

RE: Force DLR Request in OpenSMPP Kannel

[Vangelis Typaldos]

A solution could be to use a sqlbox between opensmppbox and bearerbox and set a 
default value for column dlr-mask  in your sendsms table

ALTER TABLE sendsms ALTER COLUMN dlr-mask SET DEFAULT 7;

BR

From: Rene Kluwen
Sent: Thursday, April 14, 2016 10:11 AM
To: 'Gorki Alfaro'; 
users@kannel.org
Subject: RE: Force DLR Request in OpenSMPP Kannel

I don’t think this is possible without changing the source code.



Van: users [mailto:users-boun...@kannel.org] Namens Gorki Alfaro
Verzonden: woensdag 13 april 2016 21:58
Aan: users@kannel.org
Onderwerp: Force DLR Request in OpenSMPP Kannel



Hello friends

Is there any way to enable a DLR request on OpenSMPP client even if this is not 
requested by the SMPP client (ESME)?



I would like to keep record of the delivery success rate for billing and 
statistics purporses.



Regards,

Gorki