Project

General

Profile

Bug #664

kannel doesn't start processing of queue if you issue stop-smsc or remove-smsc

Added by mr bugreporter almost 8 years ago.

Status:
New
Priority:
High
Assignee:
-
Category:
Bearerbox MT routing
Target version:
Start date:
11/02/2012
Due date:
% Done:

0%

Estimated time:
Affected version:

Description

If you have active queue at the moment and for example SMSC1 server rebooted or network connection between you and SMSC1 broken for some reason, and you want to switch to another SMSC2 via standard commands, e.g:

http://localhost:13000/stop-smsc?smsc=smsc1&password=XXX
http://localhost:13000/start-smsc?smsc=smsc2&password=XXX

both smsc1 and smsc2 have allowed-smsc-id="smsc" (e.g. common identified)

kannel won't start processing pending queue until you manually restart it

same situation happens if you just down smsc with stop-smsc or remove-smsc and add it again.

Right now bearerbox will continue processing it's queue only if SMSC1 was in status 're-connecting' - in dead or removed - it just removes whole queue and after you add smsc it's not starting.

Also available in: Atom PDF