Kannel not connect modem with Debian starter

Hello I settings Kannel on Debian with my Wavecom modem, and it works well if I execute it from terminal ( i.e. bearerbox -v 0 /etc/kannel/kannel.conf etc. ) , But if Kannel start with the default process ( Like /etc/init.d/kannel start ) the modem stay _connecting all time_!! Why? How is it

Too many dlr at once

Hi, I've got a kannel install with emi smsc connection. When we send lots of sms to the smsc at once the delivery notifications only come at the end when kannel's queue is empty. Smsc only accepts 10-15 SM/sec but can send back horrible amount at once. This is a problem for us because kannel gets

Re: Too many dlr at once

Hi, Check if you havd /etc/hosts, and if you do you should have specified your gateway. Also check if named is running (Linux) BR, Nikos - Original Message - From: "Gabor Maros" To: Sent: Thursday, April 01, 2010 12:58 PM Subject: Too many dlr at once Hi, I've got a kannel ins

Re: Too many dlr at once

Thanks Nikos, it may help but there is another problem i haven't mentioned before. We have a webapplication that receives dlrs from kannel. If kannel gets 10k dlr in one sec then kannel tries to send all of them in the same sec to the app. This behaviour kills the app (and the database behind it)

Re: Too many dlr at once

Hi, Most people here use lighttpd for dlr web receiver. It is very fast and should have no problem with this kind of traffic. BR, Nikos - Original Message - From: "Gabor Maros" To: Sent: Thursday, April 01, 2010 6:33 PM Subject: Re: Too many dlr at once Thanks Nikos, it may hel

Re: Too many dlr at once

Why are you getting 1 dlrs/sec when you onl;y have peak 25 SMS/sec? Something seems wrong here. BR, Nikos - Original Message - From: "Nikos Balkanas" To: "Gabor Maros" ; Sent: Thursday, April 01, 2010 8:00 PM Subject: Re: Too many dlr at once Hi, Most people here use lighttpd

Re: Too many dlr at once

In general DLR is not so important info to be injected right away into the database. if you have high load of MO/DLR, consider db pooling and even better, drop the http requests. The Apache or Lighty or even ISS can handle the traffic you have mentioned with no issues. What I do for high load of

Re: Too many dlr at once

Just to clarify: Lighty is lighttpd, and Seikath's ISS is actually IIS ;-) @Seikath: You have not tried the best of all: flexing a log-stream! Fastest and lighter than all the rest. You can even do all the db pooling you want by batching inserts together in real time (of course it is up to you

Re: Too many dlr at once

Hi Nikos, I tried to explain it before (maybe my English knowledge...). We have an smsc which can only accept 10-15 SMs per sec but we have batch SMs which are sent in the morning. So We send 40k SMs in the morning to kannel. Kannel keeps them in its queue until it can send them to smsc. While ka

Re: Too many dlr at once

Hi Seikath, Dlrs are very important for us they are in an Oracle database, and the web application is running in a WebLogic cluster (it makes DB connectio pooling). I can not use other infrastructure. I think opening 40k network connection at once is not the best and effective thing (allowing so

Re: Too many dlr at once

Big, big, big mistake. You are using a java application server, to do the work a c web server. That is your problem. I am surprised that your system is not frozen from the many connections. You could at least invest in a JBoss that is open source. Still my question stands: DLRs are not synchro

Re: Too many dlr at once

Hmm, I wouldn't throw an opinion about the technologies involved without really knowing what's really going on infrastructure-wise. IMHO there's nothing wrong with your setup from a high level perspective. Of course I can't tell a thing about how it is configured, dimensioned and/or being used, bu

Re: Too many dlr at once

Ok, now I want to know what is flexing a log-stream ?:) cheers On 04/01/2010 08:30 PM, Nikos Balkanas wrote: > Just to clarify: > > Lighty is lighttpd, and Seikath's ISS is actually IIS ;-) > > @Seikath: You have not tried the best of all: flexing a log-stream! > Fastest and lighter than all t

Re: Too many dlr at once

Flex (aka lex) is the front end parser to bison (yacc). It uses C, and it is even used by kannel. It is faster in pattern maching than C since it uses optimized tables for matching instead of if statements. Patterns are very similar to regexp. If you open the log as a stream, instead of parsin

Re: Too many dlr at once

Agreed, java can be faster than scripts like php, if designed carefully. PHP, just like java, is interpreted, needs ~7 passes before it is rendered by a webserver, and doesn't even have the benefit of intermediate byteCode that Java has. Java of course has the very annoying garbadge collection,