Hi,
You are not using correct configuration for load-balancing. Use different
smsc-id for each smsc and simply do not specify smsc in your sendsms url.
Kannel will load-balance SMS using rand() and load on each smsc. This will
allow finer control (load) over your smscs, since when you want to use a
specific SMSc (termination issues?) you can still direct to a specific SMSc
from your sendsms URL. For that you will want to specify preferred-smsc-id
as itself in each smsc definition.
However, I suspect that this will not fix your problem. For a fix, SMPPbox
needs to reassemble SMS to 1 before sending it to bearerbox 2. Any takers on
that?
BR,
Nikos
----- Original Message -----
From: "Tomasz" <[email protected]>
To: <[email protected]>
Sent: Tuesday, June 15, 2010 11:25 AM
Subject: Issue with concatenated messages and load balancing over SMPP
I'm currently using Kannel from last SVN in such configuration:
CGI PUSH -- SMSBOX 1 -- BEARERBOX 1 ------ SMPP LINK ------ Open SMPPBOX ---
BEARERBOX 2
To BEARERBOX 2 I have connected 3 SMSC via AT2. Each SMSC have the same
smsc-id to make load balancing available.
When I push a MT Message to CGI interface of SMSBOX 1 which is longer
than 160 chars, it is concatenated and BEARERBOX 1 sends two submit_sm
PDUs to BEARERBOX 2 via SMPPBOX.
But BEARERBOX 2 sends each part of concatenated message via different
SMSC (make load balancing for each part of concatenated msg) which
makes the message unavailable to read on mobile.
I think that BEARERBOX 2 doesn't know that these two messages are parts
of one message and should be sent via the same SMSC.
I can attach some logs if they are needed.
If you could please help me to fix this issue. Thank you.
Regarards,
Tomasz
