Dear Andy,
Kannel is pretty flexible in its configuration. Bearerbox will do routing as
well as load balancing using rand(). The queue is single and sms' are queued
based on availability of servers. If carrier D is unavailable the sms will
be picked up sometime later by another smsc based on the rand(). Which means
that there might be a small delay to pushes for carrier D as are rerouted
and picked up by other SMScs.
Additionaly each push SMS-user can specify forced-smsc and default-smsc. Any
smsc definition can specify denied-smsc-id, allowed-smsc-id and
preferred-smsc-id.
With these 2 options you can have either sms to D accumulating until D is up
and ready, picked up by other smsc after they fail (delay) on D or you can
route all sms to the available smscs directly (no delay).
BR,
Nikos
----- Original Message -----
From: "Richard Andrews" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, November 25, 2008 9:28 PM
Subject: Message queueing on sms push gateway
Hello,
I'm looking at Kannel to possibly use as a fix to an issue we're having with
our present sms push of content to the wireless carriers in Canada. My
question is, If I have multiple outgoing sms centers defined do they each
have their own queue for messages received by our content generator? The
reason for this is to determine how Kannel provides protection or guarantee
that messages for carriers A,B,C are not affected by carrier D being
unavailable and does the backlog of messages for carrier D have an adverse
effect on carriers A,B or C?
Richard Andrews
Systems Administrator - IT Operations
Pelmorex Media Inc.
