Re: Client routing

"Nikos Balkanas" <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Message-ID <042CA9909B8447809EC9B86E47803854@drwho>
It is all in the http_smsc.c. Since HTTP is stateless and drops connection 
at the end of each transaction (more or less), kannel system-type starts a 
server HTTP port to listen in to incoming MO's. On the other hand, "generic" 
handles only MT's, therefore needs only client connections. No DLRs in this 
case?

BR,
Nikos
----- Original Message ----- 
From: "Alexander Malysh" <[email protected]>
To: "Rene Kluwen" <[email protected]>
Cc: "'Nikos Balkanas'" <[email protected]>; "'Kannel Devel'" 
<[email protected]>
Sent: Wednesday, June 23, 2010 7:31 PM
Subject: Re: Client routing


yes

Am 21.06.2010 um 18:39 schrieb Rene Kluwen:

> So if you use "send-url = http://localhost:20022" (as in the example 
> given),
>
> does this enable something like:
>
> [smpp/smsbox] <--> [bearerbox localhost] <--> [bearerbox localhost] <-->
> [smpp/smsbox] ???
>
> I think that was the original question was about.
>
> == Rene
>
>
> -----Original Message-----
> From: Alexander Malysh [mailto:[email protected]] On Behalf Of
> Alexander Malysh
> Sent: maandag 21 juni 2010 18:29
> To: Rene Kluwen
> Cc: 'Nikos Balkanas'; 'Kannel Devel'
> Subject: Re: Client routing
>
> Hi Rene,
>
> look for system-type kannel and not generic...
>
> Thanks,
> Alexander Malysh
>
> Am 20.06.2010 um 23:23 schrieb Rene Kluwen:
>
>> From the manual:
>>
>> 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
>> messages.
>>
>> Or is this maybe an old comment and this has been changed meanwhile?
>>
>> == Rene
>>
>> -----Original Message-----
>> From: Alexander Malysh [mailto:[email protected]] On Behalf Of
>> Alexander Malysh
>> Sent: zondag 20 juni 2010 22:06
>> To: Rene Kluwen
>> Cc: 'Nikos Balkanas'; 'Kannel Devel'
>> Subject: Re: Client routing
>>
>> hi Rene,
>>
>> look at smsc_http. you can forward to/from smsbox/bearerbox.
>>
>> Thanks,
>> Alexander Malysh
>>
>> 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?
>>> Comments?
>>>
>>> == Rene
>>>
>>>
>>> -----Original Message-----
>>> From: Nikos Balkanas [mailto:[email protected]]
>>> 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.
>>>
>>> BR,
>>> Nikos
>>> ----- Original Message ----- 
>>> From: "Rene Kluwen" <[email protected]>
>>> To: "'Kannel Devel'" <[email protected]>
>>> Sent: Saturday, June 19, 2010 5:37 PM
>>> Subject: Client routing
>>>
>>>
>>>> Making an smsc driver that relays messages from one client (smsbox,
>>>> sqlbox,
>>>> smppbox) to another should be trivial.
>>>>
>>>> Is there any interest, either from users and/or developers in this?
>>>>
>>>> == Rene
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>
>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.