Hi Renaat and thank you for your help, I am using 1.2.1 and as far as I know, there is no way for Kannel to know when something's gone bad at SMPP level, so the setup I've tried (exactly the same as you are suggesting, I guess we've read the same article) does not work if, for example, the carrier changes the password for the connection or just filters out the traffic with a firewall. Kannel just doesnīt notice the link is gone and keeps sending messages thru it for a long time, until it finally goes down.
If I restart the service, the link cannot be established and everything works as expected: it routes traffic thru the second link, I've applied a patch to the source code (mostly manually and I even had to to add some lines to gwlib/cfg.def to make it work) that drops the link when a certain number (configurable per smsc group) of enquire_link's doesn't receive the corresponding enquire_link_response's. This should do the trick on 1.2.1. I will be trying it later today and I'll let you know how it goes. Another issue I suppose I'll have to drill will be the DLR reports. Since the message was first addressed to an SMSC connection and ended up on another, I donīt know if that would impact the retrieval of the DLR from the MySQL database (since the SMSC connection id is used as part of the primary key on the DLR table, along with the timestamp). A simple modification on the MySQL queries should do the trick by now, though. Regards, ----- Original Message ----- From: "Renaat Dumon" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, August 18, 2004 11:31 AM Subject: Re: Kannel multiple SMSC connections / PLEASE HELP > Hi, > > I tried to set this up this week and after a lot of scouring the > internet, I too found an article on somelist.com :-) (probably the same > one) > > I found out that doing it like this worked for me. > > group = smsc > smsc = "smpp" > smsc-id = "nsi1" > ... > preferred-smsc-id = "nsi1" > enquire-link-interval = 60 > > ... > > group=smsc > smsc = "smpp" > smsc-id = "nsi2" > enquire-link-interval = 60 > ... > > > > I set up 2 SMSC Simulators from Logica (see > http://opensmpp.logica.com/CommonPart/Introduction/Introduction.htm) had > them listen. I could clearly see traffic going to the "nsi1" SMSC and > not to the nsi2. > When I hit the "2" key in the "nsi1" simulator (which means stop > listening for smpp), I notice traffic immediately gets routed to the > "nsi2" smsc. > Restarting the listener has traffic routed back to the "nsi1" SMSC after > the bearerbox reconnects (default is 10 seconds interval, see more > below) > > I tested this with both 1.2.1 & 1.3.2. > > With regards to your enquire interval, I just checked with 1.3.2 and the > interval is respected when the SMPP connection is bound. > > However when a link is down, the reconnect-delay interval is used, which > per default is 10 seconds. This can be adjusted by using the > reconnect-delay parameter (for smsc= "smpp" anyway) > > Try it, it should work! > > Kind regards, > > Renaat > > On Wed, 2004-08-18 at 00:34, Alejandro Guerrieri wrote: > > Hi, > > > > I've finally found a way dealing with multiple SMSC connections to the same > > operator. > > > > I've found it in an <almost> forgotten thread from somelist.com I've got > > from the Google cache (considering somelist.com is down since some time... I > > love Goggle cache!). > > > > What I did is to set two SMSC connections with different names, and I've set > > preferred-smsc-id for the first connection to itself. > > > > I also put all other connections on the denied-smsc-id list. > > > > I send the messages using sms-push interface and setting "&smsc=balance1". > > If for some reason the link for balance1 is down, it automatically routes > > using balance2. > > > > -- > > group = smsc > > smsc = smpp > > smsc-id = balance1 > > preferred-smsc-id = balance1 > > denied-smsc-id = "other1;other2;another" > > host = "my.host1.address" > > port = 1234 > > receive-port = 1234 > > smsc-username = "somename" > > smsc-password = "somepass" > > > > group = smsc > > smsc = smpp > > smsc-id = balance2 > > denied-smsc-id = "other1;other2;another" > > host = "my.host2.address" > > port = 1234 > > receive-port = 1234 > > smsc-username = "somename" > > smsc-password = "somepass" > > -- > > > > It would seem like my problems are solved? NO :( keep reading: > > > > 1. For some unknown reason, I cannot change the reconnect-delay timer. It > > keeps asking each 10 seconds despite I've set 60 seconds (as my carrier > > asked me to do) to no avail. I even tocuhed > > > > 2. The worst problem: Kannel does not detect when the link goes down at SMPP > > level. I mean: For example, if my provider changes the password for a > > transmitter, the link goes down and I start seeing the bind_receiver > > messages again, but the link still appears as "connected" using the http > > interface. Worst: Kannel still try to route messages thru that link, so all > > my fancy setups are close to useless since Kannel still tries to use the > > (now broken) link. > > > > Any hints? > > > > Thank you in advance, > > > > > > > >
