Multi-session support for ESME

[vetss]

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: #4

This issue is a copy from SMSC GW's issue: RestComm/smscgateway#143
because SMPP staff has moved from SMSC GW project. Please see the original discussing in SMSC GW's issue RestComm/smscgateway#143

[vetss]

Do note that multiple SMPP connections to same ESME will cause conflicts in SmppTransactionHandles creation logic reported here.

RestComm/smscgateway#142

[vetss]

Hello @faizann

I understand that we need to make a major change in existing ESME logic to keep SMPP part workable.
Thank you for helping of a problem investigating.

[yulianoifa-mobius]

@vetss
Similar logic is already implemented on LB. It allows to create multiple connections and has all the required classes.
This logic may be reused

[vetss]

Hello @yulianoifa-mobius

adding of "Multi-session support for ESME" changes much the logic of smpp RA / smpp extentions, so demands of significant updates. Analizyng of current code (and design) is needed firtsly. Any help is desirable !