Hi, just try somethink like this: #TX SMSC-1 group = smsc smsc = smpp smsc-id = SMPP_1 port = 9999 host = 127.0.0.1 receive-port = 0 smsc-username = test smsc-password = test system-type = ABC allowed-smsc-id = SMPP_1
#RX SMSC-1 group = smsc smsc = smpp smsc-id = SMPP_C port = 0 host = 127.0.0.1 receive-port = 9999 smsc-username = test smsc-password = test system-type = ABC allowed-smsc-id = SMPP_1 the same for SMSC-2... Good luck! Alejandro Guerrieri wrote: > Hi all, > > This is my first posting to this list. I've been using the [EMAIL PROTECTED] > list a lot during the last months, but it seems that this problem is more > suitable for this list than for [EMAIL PROTECTED] > > I just moved from 1.2.1 to 1.3.2 yesterday and despite being able to > compile MySQL support (not an issue for me as for today), everything went > fine. > > I am trying to connect to a carrier that demands a somewhat strange > connection scheme: > > 1. The carrier has 2 SMSC running on 2 different IP's, let's call them > SMSC-1 and SMSC-2 on 1.1.1.1 and 2.2.2.2. > 2. I am supposed to have 2 RX connections running continuosly connected > (one for each SMSC). > 3. I am supposed to have at least 1 TX connection. I can have 2 if I want > _but_ (and here comes the funny part): > > 4. If the TX connection drops (or one of them if I have 2), I am supposed > to bring the other one online inmediatly after noticing it > (enquire_link_resp not received). If I have both TX connections running, I > should route all traffic on the "good" connection. > > I've tried many different patches on 1.2.1 and after a week of frustration > and madness with some bugs on that version, I've switched to 1.3.2. It > solved a great deal of my problems, mainly having to do with the retry > connection stuff, but there is one I cannot solve: > > * If the TX connection drops, Kannel also drops the RX connection on that > link. > > My question is: Is there any way to "independize" the TX/RX links, so > Kannel does not drop the RX when the TX fails? It would be good, since the > enquire_link/_resp stuff is already being sent and received in both > directions. > > Is there any patch or workaround to make Kannel work with this kind of > situation? > > I'm thinking if I set up different SMSC groups for TX and RX, but there is > no way I can set an TX-Only connection isn?t it? When I put port=1234 and > receive-port=0 both get asigned to 1234. I've tried setting receive-port > to an arbitrary value (9999) and the TX link goes up, but after a few > unsuccessful retries on the 9999 both TX and RX get disconnected. > > Thank you in advance, -- Thanks, Alex
