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
It might be the same problem when DLR comes before MT is registered.
Do you use sqlbox?
2013/2/14 David Szanto :
> 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 wo
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 = /var/lo
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 i
Trunk version is pretty much stable, I've been using for a while svn
revision 5001, last uptime was 90days, had to reboot kannel due box
upgrade.
The only issues with DLR matching I've encountered (possible scenarios):
1) kannel requests only 1st part DLR of the message, so if your SMSC
sends DLR
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 Szant
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 se
Sure Willy,
I'll post them in one hour, the time to remove the sensitive information,
but I can tell you in advance there is nothing fancy on them.
One scenario is the following:
4xSMSbox -> 1xSQLbox -> 1xBEARERbox => 10xConnections to 4xMNOs.
(7xSMPPxTRANSCEIVER + 3 custom http connections to int
Hey Rinor.
Your idea about splitting MO, MT, DLR in separate tables is just great!
How do you do matching against MT's btw? Do you invoke everytime
script or just update table via unique dlr_url id in the MT table?
Would love to see your patch against SQLBox.
I'm also wondering if you solved th
Its fine, my system is working like a charm now and you are right about the
"" to " errors, I can ignore them for now...
Sorry for my late response, I had two surgeries recently.
Aldo Zavala
Network Operations
From: Juan Luis Gómez Correa [juanluis.go...@blipbl
Looking forward for it Rinor, many thanks.
Willy Mularto
sangpr...@gmail.com
On Feb 15, 2013, at 12:19 AM, Rinor Hoxha wrote:
> Sure Willy,
> I'll post them in one hour, the time to remove the sensitive information, but
> I can tell you in advance there is nothing fancy on them.
>
> One sce
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. A
12 matches
Mail list logo
