Fri Jun 4 15:09:40 CEST 2010
Beware that this generic HTTP system-type is for MT only. We don't provide a
way for the MO side too. For MO traffic we simply expect the remote HTTP
caller to use Kannel's sendsms HTTP API on the given port to inject MO
Or is this maybe an old comment and this has been changed meanwhile?
From: Alexander Malysh [mailto:malysh00 at googlemail.com] On Behalf Of
Sent: zondag 20 juni 2010 22:06
To: Rene Kluwen
Cc: 'Nikos Balkanas'; 'Kannel Devel'
Subject: Re: Client routing
look at smsc_http. you can forward to/from smsbox/bearerbox.
Am 19.06.2010 um 17:09 schrieb Rene Kluwen:
> But reroute-smsc-id routes in between smsc's.
> Now I want to route in between bearerbox clients.
> Even though, looking at the sources of smsc_loopback.c, with some minor
> changes, it can be done?
> == Rene
> -----Original Message-----
> From: Nikos Balkanas [mailto:nbalkanas at gmail.com]
> Sent: zaterdag 19 juni 2010 17:00
> To: Rene Kluwen; 'Kannel Devel'
> Subject: Re: Client routing
> Not necessary. Already exists. Check bb's reroute-smsc-id.
> ----- Original Message -----
> From: "Rene Kluwen" <rene.kluwen at chimit.nl>
> To: "'Kannel Devel'" <devel at kannel.org>
> Sent: Saturday, June 19, 2010 5:37 PM
> Subject: Client routing
>> Making an smsc driver that relays messages from one client (smsbox,
>> smppbox) to another should be trivial.
>> Is there any interest, either from users and/or developers in this?
>> == Rene
More information about the devel