Docs: Routing to an ESME when ESME is down / cluster routing issues

[vetss]

https://telestax.zendesk.com/agent/tickets/33019 :

1. The current algo for routing is the following. We have two steps:

1 step - selecting ESME cluster for delivering. Each cluster can contain one or more ESME. The idea of cluster usage is to have load sharing between nodes (ESMEs) inside a cluster and/or if some cluster node are unbound then SMSC GW will send messages to another cluster.
SMSC GW selects the first cluster that ESME fits to the conditions:

• bindType==transiever or receiver (for SERVER type) or transmitter (for CLIENT type)
• the ESME is not the ESME from which the message has come to SMSC GW
• networkID of a message == networkID of an ESME
• dest address, ton and npi of a message fit to routing address, ton and npi of ESME
  The fact if this ESME is bound or not is not taken into account at this step

2 step - selecting of ESME in the cluster

• selecting of ESME in the cluster that is bound (and not stopped) now. If all ESMEs are not bound in the culster then the message will be dropped

2. We need to describe in the manual that "all routing addresses templates, npi and ton in all ESMEs in the same cluster must be equal for messages will be routed properly". May be we also need to add some functionality that will prevent of ESME creating if this condiotion is not fit.
   See also: Restriction in ESME creation / updating time: routing-address, ton and npi must be the same in the cluster #48

[vetss]

Fixed by:

ce8b83d