Hi David,
I would like to reproduce your test case scenario.
12xSMPPSim instances
4x(receiver/transmitter)bind x SMPPSim - (all this 4 with the same smsc-id)
So in total 48 smpp accounts with 12 distinct smsc-id.
dlr-storage = internal
Do I get it right?
What is the DLR mask you are using?
Can
Hi everyone!
We have just updated kannel to the las svn in trunk version (since in
our current version throughput was not working properly), and although
now Throughput is working as it should, we're back with the DLR problem
on multiple SMSCs.
We've made it so that the SMSC Simulators wait
Hi spameden,
We thought so, but we've delayed the DLR 1 second and the error still
shows up. We are not using sqlbox. DLRs are handled in memory.
group = core
admin-port = 13000
admin-password = XXX
smsbox-port = 13001
log-file = /var/log/kannel/kannel.log
log-level = 4
access-log =
Hi again!!
We've also come to realize that the trunk version is Development, so
we're not using it... In which case, we have the throttling problem.
We've seen there are patches that fix this problems, but don't know
wether we should simply apply them in the 1.4.3 stable version directly,
or
Hi spameden.
And thanks again for the quick response!!!
We did make sure our messages have at most 160 characters.
And we're not using DB, so not much to see there.
Do you know of any patch we could apply to the original 1.4.3 in order
to make throttle control work?
Thanks again!
David
Out of curiosity,
1)What is the simulator? (some when in high load, duplicate the id even in
the same session)
2)Can you increase the DLR delay = 3 secs on simulator and retry
3)Probably you already know this, however restarting the simulator the
foreign ID are restarted from beginning
4)Can you
Thanks for all the comments!
Rinor, the simulator we are using is a java implementation using SMPP
protocol called SMPPSim (or SMPP Simulator). We increased the DLR
delay from 0.05 to 1 second and got the same result. We do restart all
simulators (12 with 4 binds each) before every test.
