I'm curious why do you even need this patch? You could use the same smsc-id on both and assign different smsc-admin-id values to manage each bind separately (e.g. start/stop). If by any reason you'd want to send over a specific bind, you could use different allowed-smsc-id's as well.
Regards, Alejandro On Tue, Jun 25, 2019 at 12:20 PM Lamasuta, Franck, Vodafone Automotive < franck.lamas...@vodafone.com> wrote: > Hi list, > > > > We have implemented many patches along the way and I can finally take some > time to submit them. > They are running on our staging and production platforms since years for > the oldest ones. > > I will submit them one by one in the next days/weeks. > > Let’s start with the first one… J > > > > This patch allows Kannel to retrieve a pending DLRs in its database when 2 > (or more) SMSC binds are established (with different IPs and/or ports). > > It is required when a MT-SMS is submitted to SMSC A and its DLR is sent > back by SMSC B. > > Done for CIMD2 and SMPP. > > > > Example of configuration where the patch is required: > > > > # > > # Primary server > > # > > group = smsc > > smsc = cimd2 > > smsc-id = SMSC-A > > host = 123.1.2.3 > > port = 6001 > > smsc-username = user > > smsc-password = xxxxxxxx > > allowed-smsc-id = id1 > > preferred-smsc-id = id1 > > > > # > > # Secondary server > > # > > group = smsc > > smsc = cimd2 > > smsc-id = SMSC-B > > host = 123.1.2.3 > > port = 6002 > > smsc-username = user > > smsc-password = xxxxxxxx > > allowed-smsc-id = id1 > > > > > > Regards, > > Franck >
