Another way (cludge) is to use an sql-based DLR storage mechanism and use the same SMSCID for _all_ messages. This sort of gives you global DLR message id functionality. I've had to do this because our service provider can only operate on one port, but we need to specify different TON values for short and long numbers in different SMSC boxes.
Sorry, I realise this isn't a very pure suggestion! On 12/11/03, Stipe Tolj ([EMAIL PROTECTED]) wrote: > David Tully wrote: > > > > Sounds like a provider issue.. > > > > We have a provider that does just this - delivers DLRs on one bind that > > relate to another bind. I get round this by giving the binds the same > > SMSC-ID. > > correct! > > This is currently the only practible solution. Name all SMPP smsc > links with the *same* smsc-id and you will get it done. > > This issue is on the TODO for implementing smsc-groups. > > Stipe -- Rory Campbell-Lange <[EMAIL PROTECTED]> <www.campbell-lange.net>
