Re: [PATCH] smsc-dlr-alias on SMSC connections

Hi Alex,

why do you need this?

here is needed config for you:

# first connection
group = smsc
smsc-id = mylink
allowed-smsc = mylink;mylink1

# second connection
group = smsc
smsc-id = mylink
allowed-smsc = mylink;mylink2

So you can send with &smsc=mylink and bearerbox loadbalance between  
two links,
with &smsc=mylink[1|2] you can choose between two links.
In both cases DLRs added to DB with mylink as SMSC.

Why do you need dlr alias?

Thanks,
Alex

Am 04.05.2009 um 21:34 schrieb Alejandro Guerrieri:

> We were facing a problem when dealing with multiple binds to the  
> same carriers.
>
>
> Some of the carriers we're working with have SMSC's on  
> twogeographically-distant places. They asked us to connect to both  
> of them from our also replicated kannel clients.
>
> So, we have two identical connections on each of our servers to both  
> of their smsc's. This guarantees that I could use "&smsc=mylink" on  
> my send-sms url and kannel will choose one of the available links to  
> send the messages.
>
> The problem is, in this particular scenario, the DLR for that MT  
> could come back from the _other_ link (which has a different "id"),  
> so even on the same server it wouldn't be possible to match the  
> incoming DLR with the records stored on the DB.
>
> To solve this, I've created a patch that adds a new parameter to  
> SMSC connections: smsc-dlr-alias. This parameter, if not defined,  
> gets loaded with the value on smsc-id. If defined, that value is  
> used when inserting to/reading from the dlr database, making it  
> possible to find the dlr's despite being created on another bind.
>
> Please see this post for more info and the patch:
>
> http://www.blogalex.com/archives/121
>
> Regards,
> --
> Alejandro Guerrieri
> [email protected]
>
>
>
>