Hello.. for point 2)
connect to apache on the localhost where bearerbox is running! make
an php, python or perl-script.. save the sms into database and THEN
test a connection with another script (cronjob), if the test fails,
test the other connection(s).. if the test not fails, send the sms!
do u know, what i mean???
another possibility is a loadbalancer such as pound on the
localhost.. as backends of the "cluster" you set your target-
urls... pound connect to one of them (you can additionally give
different weights of spreading out to the backends!) .. with kannel
you connect only to the address of pound on localhost!
This would be a solution for SMSBOX to connect to a service, but I
think the original question was about SMSBOX connecting to BEARERBOX.
At the moment SMSBOX can only connect to one BEARERBOX and does not
have failover built in. Your solution of a VIP, using CARP could
work, but your problem will be any messages that are currently queued
on the original BEARERBOX, they will stay there until the connection
switches back over. So you will need some way to deal with that. I
think ideally you really need your upstream SMSC to accept
connections from both of your BEARERBOX processes.
Your other problem with this would be that your slave BEARERBOX will
not have an SMSBOX connected, so any inbound SMS it has not yet
processed, or DLRs say, will not get processed. I'm specifically
thinking of the situation where the master comes back online and the
slave acting as the current master becomes the slave again, mid flow.
You probably need to think of some manual process to deal with this
situation, possibly involving a local SMSBOX that can be started on
the slave to process any outstanding messages.
Regards
Ben
