|
When sending many SMS at once, the bearerbox
(version 1.4 compiled on RedHat 9) seems to have strange
behaviours.
It gets the first 2-3 messages, then send them
upon the EMI smsc I have.
All the remaining SMS goes into the STORE and
are sent really VERY VERY slowly.
Restarting the bearerbox causes some other 2-3
messages to be sent quick, than the thing re-happen.
I've noticed that this can be causes, in some
obscure circumstances, by the way you start the kannel.
I've tryed the start-stop daemon but are really
bad documented, the -d option, and actually using the nohup with '&' sign to
background the process.
Can anyone help in understanding how comes the
SMS goes into the store and don't get sent quickly even if the 'operator' is
connected ?
Can this be related by the 'fake' operator
?
thanks
Julien
Mi "status" is like this:
Kannel bearerbox version
`1.4.0'. Build `Nov 25 2004 18:44:17', compiler `3.2.2 20030222 (Red Hat Linux
3.2.2-5)'. System Linux, release 2.4.20-8,
version #1 Thu Mar 13 17:54:28 EST 2003, machine i686. Hostname berlinzoo, IP 127.0.0.1. Libxml version 2.5.4. Compiled with MySQL 3.23.54, using MySQL 3.23.54. Using native malloc. Status: running, uptime 0d 0h 9m
43s
WDP: received 0 (0 queued), sent 0
(0 queued)
SMS: received 4 (0 queued), sent 3
(0 queued), store size 3
SMS: inbound 0.01 msg/sec, outbound
0.01 msg/sec
DLR: 2 queued, using mysql
storage
Box
connections:
smsbox:(none), IP 10.100.10.5 (0 queued), (on-line 0d 0h 9m 24s) SMSC
connections:
operator EMI2:212.XXX.251.XXX:1000:7253 (online 349s, rcvd 4, sent 3, failed 0, queued 0 msgs) fake FAKE:10000 (connecting, rcvd 0, sent 0, failed 0, queued 0 msgs) |
