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!
greets
|
> |
Hi, We are looking into making our current Kannel setup more redundant that what we currently uses and I was wondering what were other people solutions to this problem. The plan here is to suffer minimal downtime, should a server become unavailable for some reason. My toughts was to have 2 servers running smsboxes and wapboxes process to receive the sms and wappush and have only 1 bearerbox online at a time which could be failed over by using heartbeat (or similar technology).
Here are the 2 current questions I haven’t found the answer around:
1) Most of the time we can only have 1 active connection to our partners’ smsc. What would be the best way to handle that? ( I thought about having heartbeat start the bearerbox when he detects a failure or is there a way to start a bearerbox in “inactive” mode where no connections are established and accepted from the smsbox) But how do we make the smsbox connect to the active bearerbox? Which bring question #2 2) Is it possible to have the smsbox tries to connect to different address? (If the current bearerbox go down, and he needs to reconnect to another ip, or should we have a Virtual IP handle by heartbeat that fails with the services?)
Our DLR will be stored in mysql, if you think about anything else I’m more than listening J
Regards, ------- Mathieu Bruneau
|
