Hi, The second solution is better : use hearbeat to take care of the service and if one box fails, the second one will start it own process.
Configuration is quite simple, and we use to do it with our own kannel box. Hope it helps -----Original Message----- From: Mathieu Bruneau [mailto:[EMAIL PROTECTED] Sent: mardi 15 janvier 2008 07:06 To: [EMAIL PROTECTED] Cc: [email protected] Subject: RE: Kannel Redundant Setup Hi, Yeah SMSC people are picky about their log :) I doubt they would like me to try to reconnect every x seconds just for fun! Since it continues to sends the sms, I guess it's connecting to the SMSC, not good for me... We could use the suspended mode; in that mode would it attempt to connect to the SMSC? I guess this brings back the problem of having "pending" messages left inside the system...  ------- Mathieu Bruneau -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 15, 2008 8:52 AM To: Mathieu Bruneau Cc: [email protected] Subject: Re: Kannel Redundant Setup well, the smsbox dies when there is no responce from the bearerbox. So in case you may register more than one IP per smsc account, you may go for identical active nodes. The first registered at the smsc will handle the traffic, the second, third etc. will try to connect, but the smsc will be drop their attempts out in case of existing restriction of one active connection per account. In each node set different smsc name and log that with the service URL, so you will know from which node the MO message has come, in a view to easy the MT routing decision. and yes, set a watchdog script to check which node has the connection, like each second. the kannel http admin interface is perfect for that. Have to say, we use here the smsc balancing feature, but the above scheme was considered as alternative. In addition, we where about to set db replication from the nodes at one or two external boxes. NICE idea is first to check the above scenario with the smsc ppl, they hate to see connection errors in the SMSC logs .. :/ alternative: identical nodes behind loadbalancer. the loadbalancer will host the IP registered with the smsc account. One active node, and several started, but in isolated mode. use the watchdog script to check their statuses, and to decide which isolated node to activate upon non responding active node. the modes are described in the manual .. :) cheers -----Original Message----- From: Mathieu Bruneau [EMAIL PROTECTED] Sent: 15 ?????? 2008 ?. To: [EMAIL PROTECTED] Subject:Kannel Redundant Setup > 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 > > No virus found in this outgoing message. > Checked by AVG Free Edition. > Version: 7.5.516 / Virus Database: 269.19.2/1223 - Release Date: > 2008-01-13 20:23 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.516 / Virus Database: 269.19.2/1224 - Release Date: 2008-01-14 17:39 _____ Antivirus avast! <http://www.avast.com> : message Sortant sain. Base de donnees virale (VPS) : 080115-0, 15/01/2008 Analyse le : 16/01/2008 00:37:04 avast! - copyright (c) 1988-2008 ALWIL Software.
