kannel doesn't start processing of queue if you issue stop-smsc or remove-smsc
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:
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.