As for now SMSC GW does not support several concurent connections for an ESME. If we need several connections we have to create several ESME instanses that make configuring more complicated.
To solve it we need add some other class - Session that will be hosted by Esme class and change the logic of Emse class usage.
PS: Let's think also for keeping of some Emse parameters that are unique for Esme cluster at the Cluster level to avoid possible wrong configuring of different ESMEs in the same cluster. We have a separate issue for this case:
#48
As for now SMSC GW does not support several concurent connections for an ESME. If we need several connections we have to create several ESME instanses that make configuring more complicated.
To solve it we need add some other class - Session that will be hosted by Esme class and change the logic of Emse class usage.
PS: Let's think also for keeping of some Emse parameters that are unique for Esme cluster at the Cluster level to avoid possible wrong configuring of different ESMEs in the same cluster. We have a separate issue for this case:
#48