CMIIW, it only route incoming MO from smsc-link. While MT routing so far done by explicitly define the smsc-id in the send-sms URL and or smsc_id field in the SQLBox.
sangprabv sangpr...@gmail.com On Jun 19, 2010, at 9:14 PM, Rene Kluwen wrote: > I am thinking of a possibility. Does the group = smsbox-route also route > incoming message from a box? Or just incoming messages from the smsc-link? > > == Rene > > -----Original Message----- > From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf > Of Nikos Balkanas > Sent: zaterdag 19 juni 2010 14:15 > To: sangprabv > Cc: users@kannel.org > Subject: Re: For the ones using (open) smppbox... > > Nope. The way it works is (SMPP_CLIENT = ESME): > > ESME -> SMPPBOX ->Bearerbox->SMSC > > The connection from ESME is SMPP. The connection to Bearerbox is (Msg *), > which is a kannel protocol. ESME can be any SMPP client. > > BR, > Nikos > > ----- Original Message ----- > From: "sangprabv" <sangpr...@gmail.com> > To: "Rene Kluwen" <rene.klu...@chimit.nl> > Cc: <users@kannel.org> > Sent: Saturday, June 19, 2010 2:55 PM > Subject: Re: For the ones using (open) smppbox... > > > What about a pass-thru(forward) configuration between connections? Is it > possible, let's say we want to pass traffics SMPP_CLIENT_A > <->SMPPBOX<->SMPP_CLIENT_B. > > > > sangprabv > sangpr...@gmail.com > > > On Jun 19, 2010, at 3:31 AM, Rene Kluwen wrote: > >> Today, I committted a patch to smppbox svn trunk that allows for long >> (catenated) messages to be delivered via the same smsc, in case of load >> balancing. >> >> This version obsoletes that patch that is available for download on the >> chimit server. >> >> For the latest (stand-alone) version, use svn co >> https://svn.kannel.org/smppbox/trunk >> >> == Rene Kluwen >> >> >> > > > > >
