0.0.5
•	This stores each message (either received from the SMSAlarmRecipient
or as result of invoking the "sendSms" Action) in a hidden component of
the service and once successfully sent is removed from the cache.
•	If an error occurs it will attempt to resend the message recursively
until error free.
•	While this is happening, any subsequent messages that are received
are cached and queued.
•	Once a message is sent, the next message in the queue is sent in the
same way.
•	When the station is stopped, the cached messages are saved to the
bog file. On reboot, the cached messages are loaded back into the queue and
the process repeats.
•	If the queue reaches max capacity (adjustable) the oldest messages
are removed. This means the sending continues with only a small loss in
messages. The queue has a hard limit of 1000 messages so as not to overload
the size of the station

0.0.7
fixes stability, where if the router was offline, the block trying to find 
the router was slowing down/stopping some other processes

0.0.8
the block now doesn't queue SMS messages when disabled or when in a 
critical fault condition (typically a license error)