The SMSC may be high availability, however the connection to it may not. High
availability may be achieved by having multiple consumers from different
load sharing SMSC. The SMSC may reject the bind if it is too busy, or a
specific ESME may only be allowed to operate eg at off-peak times.
Not comm
Ah. I've just seen the following Jira which suggests that
"lazySessionCreation" was only implemented for the producer.
https://issues.apache.org/jira/browse/CAMEL-3853
--
View this message in context:
http://camel.465427.n5.nabble.com/Route-failure-on-startup-for-SMPP-consumer-if-SMSC-down-tp5
Hi , I'm trying to set up a route to process incoming SMS. Everything works
fine if the SMSC is available and accepts the ESME connection on startup,
and it can handle connection failures, etc. However if the initial
connection attempt fails (eg if the SMSC is not accessible) then the route
fails (
