Dear List, I've made a patch that implements full support for MO parameters and return messages for the 'generic' HTTP SMSC.
It adds the following (optional) parameters to the smsc group with system-type='generic' 1. Parameters for the incoming (MO) HTTP request: mo-from mo-to mo-text mo-udh mo-account mo-binfo mo-dlr-url mo-dlr-mid mo-flash mo-mclass mo-mwi mo-coding mo-validity mo-deferred mo-dlr-mask This allows to set a specific parameter name for all those values. If missing, the default is used, so no changes are needed if you're using the defaults. 2. Parameters for the return strings: mo-ret-accepted mo-ret-denied mo-ret-unknown-dlr mo-ret-missing-args mo-ret-udh-mismatch mo-ret-udh-long mo-ret-auth-failed mo-ret-dlr-accepted mo-ret-dlr-denied This allows to set specific strings to be return instead of "Sent.", "Not Accepted", etc. If missing, the default strings are used, so no changes are needed on conf files unless you really want to modify the strings. The patch also allows to ignore the username and password for the MO request. Just don't set "smsc-username" and "smsc-password" and the request won't ask for those parameters. To download the patch, please go to: http://www.magicom-bcn.net/kannel/full-mo-http-params.patch I know there are many scenarios where this is not enough to accomodate third parties' requirementes, but I think that a lot of "custom http smsc's" could be implemented using this patch, without the need of modifying the source code and recompiling Kannel. In my particular case, all but one of the many HTTP connections we have could be implemented with this (being the one missing one using synchronous messaging, so it needs a lot of "glue" to make it work). Please let me know what you think. I'll make proper userguide patches as well if this have any chances of going into the main tree. Regards, -- Alejandro Guerrieri Magicom http://www.magicom-bcn.net/ LinkedIn: http://www.linkedin.com/in/aguerrieri
