Hi,
We were running into similar issues at one time. we have multiple bearerboxes
and multiple backend processing server that handle the MO's from kannel via
haproxy.
The way we handle multi part messages is to move the problem to our processing
engine(s)
First disable message re-assembly in
Hi,
@Joe: Technically, SMS splitting over SS7 like you are describing is not
possible. If it is indeed the case, your Telco operator has configured his
SMSC cluster in a very dumb and stupid way. Apart from A2P/P2A messages,
this should also cause a havoc on P2P messaging as well. I wonder if they
Hello Joe and Kannel community:
I am facing the same issue as you described.
Wondering if you have found a solution to your problem as I don't see
a follow-up from you on this.
Similarly to you and for obvious redundancy reasons, I have two
separate bearerbox and the upstream has multiple SMSC and
Hi,
As of My Knowledge, Kannel updates the dlr as soon as it received the 1st
dlr itself. You will see an warning that dlr not found when the 2nd dlr
report comes in. Mysql-Databse for dlr.
*Rajeev Krishna*
Operations Manager
Krishnas Software Technologies
www.krishnasoft.in
mobile :+91 888 58
I am not an kannel expert but have you tried below.
1. Add both connectivity under single kannel instance.
2. Give same smsc-id to both connectivity under kannel (smsc-id = )
Check if this resolves your issue.
On Wed, Jan 14, 2015 at 6:10 PM, Joe Power wrote:
> Hi folks,
> I have i
Hi folks,
I have inherited a working Kannel platform with binds into multiple
operators. I don't have much experience in configuring Kannel, but have
seen what works on the existing platform. I have discovered an issue we
have with multi-part messages from one of the operators we are connec
