Make incoming BIND request rejection log more informative #7
Description
We have now a message in log "Received BIND request but no ESME configured for SystemId=%s Host=%s Port=%d SmppBindType=%s" that is for many cases including:
- no such ESME is configured
- we have such configured ESMEs but all of them are already connected
We need to differentiate them and alco care for a case when ESME is configured but stopped (caser for this in "getEsmeByPrimaryKey()") and the message will be like "all ESMEs are already bound or not started"