Hi,
This seems to be a different problem. Start a new thread, post fresh logs
and the output from store-status. Restarting smsc or bb won't fix this.
BR,
Nikos
----- Original Message -----
From: Brent Ingram
To: 'Nikos Balkanas'
Cc: [email protected]
Sent: Monday, July 11, 2011 12:37 PM
Subject: RE: Messages queueing
Hi Nikos
Thanks for your response.
Ok I understand now. I have changed them both to transceiver mode however I
have still had the problem a couple of times today.
I checked the store-status at the time and the messages in there had no
“SMSC ID” or “BOX ID”.
Does that help you any further?
Thanks
Brent
From: Nikos Balkanas [mailto:[email protected]]
Sent: Thursday, 7 July 2011 8:38 a.m.
To: Brent Ingram
Cc: [email protected]
Subject: Re: Messages queueing
Hi,
I think I see your problem. It is a known kannel bug. When not using
separate connections for transmit and receive, It is possible that only the
transmit connection is dropped. Since kannel still gets enquire PDUs from
the receive connection, it marks the SMSc as active, and never tries to
reconnect. But since the transmit line is down, it cannot. As a work around
you can just restart the SMSc, not the whole bb. The fix would be to use
transceiver-mode. Check with your provider if he supports it.
If that's not the case, please do:
1) Post output of status and a few lines of store-status from web admin
2) Post max detail of bb logs (with smsc traffic) of what it is trying to
do. Router should wake up every 30' and try to send queued SMS to active
SMScs. What is the log saying? (skip enquire PDUs)
3) From store-status, are queued SMS associated with any particular SMSc, or
from both?
BR,
Nikos
On Wed, Jul 6, 2011 at 10:19 PM, Brent Ingram <[email protected]> wrote:
Hi Nikos
Here is the current config:
group = core
admin-port = 13000
smsbox-port = 13001
admin-password =
dlr-storage = mysql
log-file = "/home/kannel/smskannel.log"
log-level = 0
access-log = "/home/kannel/smsaccess.log"
store-type = file
store-location = "/home/kannel/smskannel.store"
###Begin
group = smsc
smsc = smpp
host = smsc2.com.au
port = 1775
receive-port = 1775
smsc-username =
smsc-password =
system-type = "VMA"
address-range =""
smsc-id = smsc2
allowed-smsc-id = smsc2
preferred-smsc-id = smsc2
###End
####Begin
group = smsc
smsc = smpp
host = smpp.smsc1.net
port = 8100
receive-port = 8101
smsc-username =
smsc-password =
system-type = "CMT"
address-range =""
smsc-id = smsc1
####End
group = smsbox
bearerbox-host = 127.0.0.1
sendsms-port = 13013
log-file = "/home/kannel/smsbox.log"
log-level = 1
access-log = "/home/kannel/smsboxaccess.log"
http-request-retry = 5
http-queue-delay = 60
group = sendsms-user
username =
password =
#MySQL setup for DLR
group = mysql-connection
id = mydlr
host = localhost
username = kannel
password =
database = dlr
max-connections = 5
group = dlr-db
id = mydlr
table = dlr
field-smsc = smsc
field-timestamp = ts
field-destination = destination
field-source = source
field-service = service
field-url = url
field-mask = mask
field-status = status
field-boxc-id = boxc
Thanks
Brent
From: Nikos Balkanas [mailto:[email protected]]
Sent: Tuesday, 5 July 2011 6:03 p.m.
To: Brent Ingram
Cc: [email protected]
Subject: Re: Messages queueing
Hi,
Can you also post your configuration?
BR,
Nikos
On Tue, Jul 5, 2011 at 7:47 AM, Brent Ingram <[email protected]> wrote:
Hi Nikos
The issue has happened again while I had debug logging enabled.
Attached is the bearerbox showing everything around the time and also
showing me shutting down bearerbox.
Hope that might give some of you insight into what could be causing it.
Thanks in advance for your time.
Thanks
Brent
-----Original Message-----
From: Nikos Balkanas [mailto:[email protected]]
Sent: Tuesday, 28 June 2011 7:50 p.m.
To: Brent Ingram; [email protected]
Subject: Re: Messages queueing
Hi,
Please include max detail logs when posting to this list.
BR,
Nikos
----- Original Message -----
From: Brent Ingram
To: [email protected]
Sent: Tuesday, June 28, 2011 12:39 AM
Subject: Messages queueing
Hello
We have been having issues lately with messages sometimes going into the
Queue to be sent, but not actually been sent.
All SMSC connections are online, but none of them show queued messages.
What I do to get around the issue is restart bearerbox which then queues
the
messages to the SMSC and they are sent.
Here is the log:
2011-06-28 02:38:33 [13284] [9] ERROR: SMPP[dialogue]: I/O error or other
error. Re-connecting.
2011-06-28 02:38:33 [13284] [9] ERROR: SMPP[dialogue]: Couldn't connect to
SMS center (retrying in 10 seconds).
2011-06-28 09:27:15 [13284] [0] WARNING: Killing signal or HTTP admin
command received, shutting down...
2011-06-28 09:28:12 [13284] [14] INFO: Connection closed by the box
<127.0.0.1>
2011-06-28 09:28:13 [13284] [0] INFO: All flow threads have died, killing
core
2011-06-28 09:28:13 [13284] [0] INFO: Total WDP messages: received 0, sent
0
2011-06-28 09:28:13 [13284] [0] INFO: Total SMS messages: received 448,
sent
132
2011-06-28 09:28:32 [30091] [0] INFO: Added logfile
`/home/kannel/smskannel.log' with level `1'.
2011-06-28 09:28:32 [30091] [0] INFO: Started access logfile
`/home/kannel/smsaccess.log'.
2011-06-28 09:28:32 [30091] [0] INFO: HTTP: Opening server at port 13000.
2011-06-28 09:28:32 [30091] [0] INFO: BOXC: 'smsbox-max-pending' not set,
using default (100).
2011-06-28 09:28:32 [30091] [0] INFO: Set SMS resend frequency to 60
seconds.
2011-06-28 09:28:32 [30091] [0] INFO: SMS resend retry set to unlimited.
2011-06-28 09:28:32 [30091] [0] INFO: DLR rerouting for smsc id <x>
disabled.
2011-06-28 09:28:32 [30091] [0] INFO: DLR rerouting for smsc id <y>
disabled.
2011-06-28 09:28:32 [30091] [0] INFO: DLR rerouting for smsc id <z>
disabled.
2011-06-28 09:28:32 [30091] [0]
INFO: ----------------------------------------
2011-06-28 09:28:32 [30091] [0] INFO: Kannel bearerbox II version 1.4.3
starting
2011-06-28 09:28:32 [30091] [0] INFO: Loading store file
`/home/kannel/smskannel.store'
2011-06-28 09:28:32 [30091] [0] INFO: Store-file size 3759, starting to
unpack
2011-06-28 09:28:32 [30091] [0] INFO: Retrieved 9 messages,
non-acknowledged
messages: 9
2011-06-28 09:28:32 [30091] [0] INFO: MAIN: Start-up done, entering
mainloop
2011-06-28 09:28:33 [30091] [5] INFO: Client connected from <127.0.0.1>
This is running Kannel v1.4.3 built 17/10/09.
I assume you will recommend updatuing to the latest SVN. However I just
wanted to see if there were any other suggestions as to the possible
cause.
Thanks
Brent
