So it looks deliver_sm_resps are being sent back without any delay.
The assumption is that the SMSC sees "window full" when they don't get
a certain number of ACKs within a period.
Have you tried sms-incoming-queue-limit = -1?
Also you mentioned that dlr requests are posted to your server. Do you
Hi Vinicio
As stated, I handle that in my own app. I get queue info from kannel
admin interface parsing the status.xml page.
We defined the queue limit as the number of messages to be transmit in
a 5min interval. In our case about 40sms (using modems).
Regards
Alvaro
|--
We did the same but using Oracle PL/SQL and it sends the order to restart
Kannel, What can you say about the queue limit that I asked?, how it is
configured and how it works?.
Thanks.
-Original Message-
From: Alvaro Cornejo [mailto:cornejo.alv...@gmail.com]
Sent: Wednesday, November 27,
Hi
Sorry, forgot to cc users list.
What we did was a small php script that parses kannel status.xml page
and gets each smsc queue and based on the values retrieved, my app
insert messages to smsbox. We keep a queue of about 5 min of
transmission per modem. ie about 40 messages.
Hope helps
Alvar
Hi everyone, I have an strange behavior in kannel, on several occasions
store size contains sms but they are not sent, checking connections (5 of
them) don't have any queued messages, only when Kannel is restarted the sms
are queued and sent.
I'm using serial modems Multitech, Kannel 1.4.1, OS
Here is one other thought
we do have the following setting on the core group.
sms-incoming-queue-limit = 0
The docs for this say "Value 0 means giving strict priority to outgoing
messages" What exactly does this mean? Could this affect incoming DLRs (or
MOs for that matter) if we are doing
Yesthat is exactly what I meant. Thanks Jason. I only set
receive-port=0 on one of the transmitter binds as a test anyway. The others
do not have that, but do have transceiver-mode = 0.
In the PDU debug log, I am seeing a few occasional "got DLR but could not
find message or was not interested
I think he meant that he set receive-port = 0 on transmitters only and
he only expects DLRs to come through on receiver binds. For some
reason, he's getting DLRs on transmitter binds as well.
Are you able to post your PDU logs? Just the sections with DLRs.
On 27 November 2013 22:32, spameden wro
Most likely that's because you set receiver-port = 0.
Check your smsc log as well and post here any errors you find.
2013/11/27 Jeff Thorn
> The SMSC Operator said they were getting "Window on receiver link full"
> errors from us when trying to send DLRs. Is that possible?
>
> We are not usin
The SMSC Operator said they were getting "Window on receiver link full"
errors from us when trying to send DLRs. Is that possible?
We are not using sqlbox and we do have the dlr table indexed. I will
confirm the version of kannel.
On Wed, Nov 27, 2013 at 1:52 PM, spameden wrote:
>
>
>
> 2013/1
2013/11/27 Jeff Thorn
> I see. So does that mean the the DLRs I am seeing on the transmit binds
> are only status 8s? Would the volume of 8 messages impact the sending of
> other status from the SMSC? I am trying to understand the cause of the
> error from the operator "Window on receiver link fu
I see. So does that mean the the DLRs I am seeing on the transmit binds are
only status 8s? Would the volume of 8 messages impact the sending of other
status from the SMSC? I am trying to understand the cause of the error from
the operator "Window on receiver link full".
I appreciate your help wit
2013/11/27 Jeff Thorn
> The documentation says to set receive-port = 0 to disable I/O on this
> bind. I tested this on the one sample config I posted and it had no effect.
> Our other binds look like this and they too are receiving DLRs. What should
> be changed to make this a "pure transmitter b
2013/11/27 Jeff Thorn
> Thanks for the response. In my scenario, we want to be able to send as
> fast as possible. We are regularly submitting MTs at a rate of 200 /
> second. We get DLRs at a rate of 1.5 - 2 times this (300 - 400 / second).
> This makes sense to me since we get multiple DLRs for
The documentation says to set receive-port = 0 to disable I/O on this bind.
I tested this on the one sample config I posted and it had no effect. Our
other binds look like this and they too are receiving DLRs. What should be
changed to make this a "pure transmitter bind"? Will DLRs be received on
First of all, to bind in pure transmitter mode do not set receive-port.
After this you should have 6 pure transmit binds and 4 pure receiver binds.
On Nov 27, 2013 8:15 PM, "Jeff Thorn" wrote:
> Thanks for the response. In my scenario, we want to be able to send as
> fast as possible. We are regu
Thanks for the response. In my scenario, we want to be able to send as fast
as possible. We are regularly submitting MTs at a rate of 200 / second. We
get DLRs at a rate of 1.5 - 2 times this (300 - 400 / second). This makes
sense to me since we get multiple DLRs for every MT (status 8,4,1). We do
You can control DLR via dlr_mask parameter, if its unset you won't receive
any DLRs.
About speed - it's strange for me that speed of DLRs is much higher than MT
submit speed.
Don't think there is any algorhythm implemented to control inbound
information coming, you might turn into transmitter mod
It looks like setting receive-port=0 has no effect on DLRs. Is there any
way to control which binds receive DLRs or to somehow control how fast they
are received?
On Wed, Nov 27, 2013 at 10:15 AM, Jeff Thorn wrote:
> If we are getting DRs faster than we can process them, I assume if we
> reduce
If we are getting DRs faster than we can process them, I assume if we
reduce the number of receive binds the rate that we get DRs would go down.
Is this generally true?
We have a total of 10 binds setup - the desired design is to have 6
transmit binds for sending MTs and 4 receive binds for accept
Hi,
I am having severe error of bearerbox showing "segmentation fault" in
SVN-r5063 whenever bulk SMS are sent. If someone needs a diagnose/symptoms,
please let me know which files/trace to send to you.
Regards,
Hamza
Probably it does. But only for the first part.
From: users [mailto:users-boun...@kannel.org] On Behalf Of ?-?
Sent: woensdag 27 november 2013 8:05
To: users@kannel.org
Subject: dlr-url don't insert SMS in database if message parts > 1
Hello. Sending sms works fine, dlr-url works fine, BUT i
22 matches
Mail list logo
