Re: [PATCH] better smsbox-route abilities

Alexander Malysh <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Message-ID <[email protected]>
Hi Stipe,

I hope you know that we never add/change config values without updating
userguide? Please update user guide...

Stipe Tolj wrote:

> Stipe Tolj wrote:
> 
>> Hi list,
>> 
>> please find attached a patch for enhancing the current smsbox routing
>> via 'smsbox-route' group in bearerbox scope.
>> 
>> Changed the config directives to 'smsc-id' and 'shortcode' for
>> smsbox-route group, since this fits the naming convention more, even
>> while these are semicolon seperated lists. (yep, need to update
>> userguide.xml too ;)
>> 
>> The need for the routing enhancement is the following situation you want
>> to handle:
>> 
>> smsc A, smsc B. Both have a shortcode X registered and deliver MOs for
>> it. You have various smsbox connections, ie. for different customers.
>> Now you want to route MO with receiver X from A to smsbox-id S1 and the
>> same receiver X from B to smsbox-id S2. Which is not possible in our
>> current way.
>> 
>> That's why I added another Dict in the gw/bb_boxc.c scope that is used
>> as lookup hash for keys of the format <shortcode>:<smsc-id>. So we get
>> the following routing logic:
>> 
>> 1) get smsbox route for smsc-id
>> 2) get smsbox route for receiver
>> 3) get smsbox route for <receiver:smsc-id>
>> 
>> Route with priority: 3, 2, 1
>> 
>> Please review and comment.
> 
> In Alex's words: no objections? commited to cvs. :)
> 
> Stipe
> 
> -------------------------------------------------------------------
> Kölner Landstrasse 419
> 40589 DÃŒsseldorf, NRW, Germany
> 
> tolj.org system architecture      Kannel Software Foundation (KSF)
> http://www.tolj.org/              http://www.kannel.org/
> 
> mailto:st_{at}_tolj.org           mailto:stolj_{at}_kannel.org
> -------------------------------------------------------------------

-- 
Thanks,
Alex
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.