That's true.
You could use two different smsc groups and get the control of which
to use passing smsc_id parameter to your messages.
On 4/4/2012 3:58 μμ, Kyriacos/Netsmart wrote:
Hi,
I believe the "load balance" happens only in the sence that if one
bind is busy sending an SMS and a new request comes, instead of
queuing it, it goes to the second bind of the same name, rather
than doing "round-robin" load balancing which seems to be what
most people expect/assume. If your send rate is fairly low, then
most messages will leave via the 1st bind.
Regards,
Kyriacos Sakkas
On 04/04/2012 13:58, spameden wrote:
I'm using latest kannel from SVN with sqlbox in
scheme:
Box connections: smsbox:sqlbox, IP 127.0.0.1 (0 queued),
(on-line 0d 0h 13m 12s)
I'm using multiple connections to the same SMSC with the same
login (my smsc allows up to 4 concurrent connections under the
same login).
I have configured 2 connections for sending SMS and 2
connections for receiving DLRs.
I noticed from kannel's status kannel isn't load balancing
properly between them:
mysmsc[smsc] SMPP:smpp-provider.com:2775/0:login:NULL
(online 623s, rcvd: sms 0 (0.00,0.00,0.00) / dlr 2559
(4.29,4.21,4.11), sent: sms 2559 (4.29,4.21,4.11) / dlr 0
(0.00,0.00,0.00), failed 0, queued 0 msgs)
mysmsc[smsc] SMPP:smpp-provider.com:2775/0:login:NULL
(online 623s, rcvd: sms 0 (0.00,0.00,0.00) / dlr 234
(0.40,0.38,0.38), sent: sms 234 (0.40,0.38,0.38) / dlr 0
(0.00,0.00,0.00), failed 0, queued 0 msgs)
dlr's are here because I'm using dlr_mask=31 to get also
state=8.
You can clearly see that number of sent sms are not the same and
differs in about 10 times or more.
I can't use different smsc_id's because in this case messages
won't be matched against dlr table.
I can post relevant bits from configuration as well if needed..
--
Πετσούκα Τάνια
Web Developer
Tessera Multimedia Α.Ε.
Βασ. Γεωργίου 24, Θεσσαλονίκη 54640
Τηλ. +302310889155
Fax: +302310889156
|
