There's also the issue of DLR handling - isn't the good thing about using
different username and password is that at least it is a failsafe way of
getting DLRs back to the sending box, otherwise they'll end up getting
rejected by Kannel ?
Me too, two connections to the same SMPP, both over the
Hi,
I thought I'd configured my test kannel config such that in the event that a
connection to an smpp server went dead (smsc-id=smpp2 below) then sms sends
would get re-posted via the second smsc
(smsc-id=TEST411 below, which is actually just a call to sendsms over to
another bearerbox
We changed the source code to NOT delete the row, just update it. Hopefully
there isn't any problem with this approach, but just seemed easier at the
time.
Maybe there should be (yet another?!?) config option defining persistence of
the DLR row.
Just a quick note: Don't expect Kannel to
Hello,
I'm really struggling to get to grips with kannel support for multiple
smsc-id.
All I'm trying to do is
a) support connections to 2 different smpp ports
b) in event that both are down, use an http smsc to simply re-post the SMS
to another kannel
instance on another server (test411), with
Hi,
Can anyone point me in the direction of example kannel configs ? I'm sure
what I want to do is
fairly standard, but am having trouble getting my head around it.
All I want to do is support access to 3 or 4 different smpp gateways that
our provider has given
us, but with the additional
