[RFC] SMSC redundancy (Was: RE: [REPOST] [PATCH] emi2 driver login behaviour)

Quoting Anders Lindh <[email protected]>:

> 
> I agree. I have a setup with close to 20 different connections, using 5
> different types of SMSCs (emi, cgw, cimd2, smpp, at2). Because Kannel
> isn't always able to pick up connections, or just to start up with a
> failing connection, I'm forced to run many instances of Kannel. CIMD in
> particular is problematic, as the CIMD SMSC usually doesn't allow two
> simultanious connections, and causes Kannel not to start if a connection
> has been badly broken (i.e. the SMCS thinks the connection is up, even
> though it isn't). This is true also for smpp. The bearerbox shouldn't
> panic if a connection isn't established during startup, it should try
> again until it succeeds. Otherwise Kannel is extremly stable, and this
> is just about the only problem I've ever had with it. It's also quite
> annoying at times.  


Has anyone picking this job? (sorry, couldn't read much of the mailing list 
lately)

I was asked to do smsc connection redudancy to emi2 and I might pick this job.

They don't want to put an Alteon (or some other load-balance switch) so they
want that if one smsc connection fails, I'll switch to other smsc ip.

I can't have two smsc connections because there could be only one active 
connection, so I might code it to switch to an alternate ip/port on connection
fail (or switch to itself if only one ip/port), thus resolving the problem of
restarting some broken connection



-- 
Davi