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
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 j...@thorntechnologies.comwrote:
If we are getting DRs faster than we can process
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
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
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 j...@thorntechnologies.com wrote:
Thanks for the response. In my scenario, we want to be able to send as
fast
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
2013/11/27 Jeff Thorn j...@thorntechnologies.com
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
2013/11/27 Jeff Thorn j...@thorntechnologies.com
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
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 with
2013/11/27 Jeff Thorn j...@thorntechnologies.com
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
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 spame...@gmail.com
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 j...@thorntechnologies.com
The SMSC Operator said they were getting Window on receiver link full
errors from us when trying to send DLRs. Is that
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
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
Hello Group,
We are receiving DLRs from the SMSC faster than we can process them. Our
setup is supposed to have 6 transmit binds and 4 receive binds. However, I
just looked at status page showing all our binds and it looks like all 10
of our binds are receiving DLRs and they are coming in at a
15 matches
Mail list logo
