So interestingly this raises some very real issues for companies such as us in the market place who connect to the MBlox gateway as one of our aggregator partners and keep getting complained at that our installations of Kannel _don't_ support the extended parameters that Ian and the team have added.
In meetings I do stress that Kannel supports the standard specs of SMPP 3.4 and therefore we shouldn't need to support the extended parameters that the MBlox gateway has been the argument back has always been that SMPP 3.4 specification _does_ allow extended parameters to be added. Therefore we have the issue here of either rebuilding Kannel against CVS every few months and adding in the MBlox changes or branching our own version and maintaining that. Obviously neither are ideal as with the first we don't get the bug fixes and updates from the group, but obviously with the second we're not diffing and patching files all the time. So.. what about the ability to have vendor specific #defines in the build? If you look at the SOAP code (which Nisan I think you wrote some of, and Mobileway wrote some of) there are two vendor specific formats in there for European carriers to support their own formats of XML. I agree they shouldn't be there as standard, but this could be a way of extending the SMPP support to proprietary formats. Stipe - any thoughts your side on how we could extract vendor specific code, but maybe still have it as a build option? Regards Alex Skywire/Enpocket
