Before I start ranting, this is a question - and
not a statement, so please don't flame me if I'm wrong! :-)
If you have multiple SMPP connections to a
provider, shouldn't the DLRs come back on the connection that the message was
sent out on? We're having an issue with one of our providers
:54 PM
Subject: Another broken SMSC DLR implementation?
Before I start ranting, this is a question - and not a statement, so please
don't flame me if I'm wrong! :-)
If you have multiple SMPP connections to a provider, shouldn't the DLRs come
back on the connection that the message was sent out
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
Hi ,
Ian, it's 100% wrong to send DLR's for _every_ RX session with equals
credentials (means DLR's comming twice/thrice)... I can have more as one RX
sessions but I expect to get DLR only once.
On Wednesday 12 November 2003 14:07, Ian Cass wrote:
Alex Kinch wrote:
If you have multiple SMPP
: Re: Another broken SMSC DLR
implementation?
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
ok, you mean it would break in terms of routing if you use the
smsc=foobar variable in the sendsms interface, right?
To solve this, do the following: name the links with the same smcs-id,
to ensure you get the DLRs processed. But, and that's the trick,
include unified smsc-ids to allowed-smsc-id
system for alpha sender and one on each system for numeric sender.
Alex
- Original Message -
From:
David Tully
To: [EMAIL PROTECTED] ; Alex Kinch
Sent: Wednesday, November 12, 2003 1:05
PM
Subject: Re: Another broken SMSC DLR
implementation?
Sounds like
Subject: Re: Another broken SMSC DLR
implementation?
Thanks Dave
How would giving the binds the same SMSC-ID
affect a request to suspend a particular connection, or if one of the
connections goes down? We're binding four connections on one instance of
bearerboxto two smpp systems
this is normal behaviour on multiple EMI/UCP connections to the same SMSC.
I presume what you are facing is the idea that a DLR comes back on the same link you used to submit. this is not the case as the DLR comes back on ANY link you use the same short-id to bind with. So the uniqueness is not
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
10 matches
Mail list logo
