To use it, you need to add a few extra entries for the parameters you want to be redefined. The format is: generic-param-<original-name> = <new-name>

For example, to redefine from, to, smsc and text:

generic-param-from = “phoneNumber”
generic-param-to = “shortCode”
generic-param-text = “message”
generic-param-smsc = “carrier”

That’s it, you’ll be able to use an url like this then:

http://myhost:myport/sms?phoneNumber=234567890&shortCode=1234&message=Hello+World&carrier=mycarrier

Download the patch from here.

As usual, try it and let me know.

-Alex

A problem you may have faced with dlrs on Kannel: If you’re using dlrs and have more than one bind to a given carrier, you need to name them all the same. Otherwise, if the dlr come back over a different bind than the one you’ve used to send the MT message in the first place, Kannel won’t be able to match them, since they won’t share the same “smsc” field.

This is usually OK. However, you lose the ability to control the binds independently: you cannot shutdown a single bind, for example. The problem worsens yet more if your binds are to different data centers (some carriers have redundant SMSC’s on geographycally distant places).

That’s why I’ve created this patch that adds a new configuration option to SMSC groups:

smsc-dlr-alias

Using this parameter, you can define an alias to use when storing dlrs, so they will match despite being sent/received over different binds.

For example:

…

#carrier link 1

group                      = smsc

smsc                       = smpp

smsc-id                  = “link1″

smsc-dlr-alias     = “myalias”

allowed-smsc-id = “link1;mylink”

host                        = “1.1.1.1″

…

#carrier link 2

group                      = smsc

smsc                       = smpp

smsc-id                  = “link2″

smsc-dlr-alias     = “myalias”

allowed-smsc-id = “link2;mylink”

host                        = “1.1.1.1″

…

Using this configuration, you just have to use the “&smsc=mylink” parameter on your send-sms url. The dlr will be stored using the alias “myalias” no matter which of these 2 routes the message takes. When getting the response back, again, it will be matched against “myalias”.

Download the patch here.

Please try it and let me know what you think.

Regards,

Alex