Re: mBlox SMPP optional parameters

Nisan Bloch - Clickatell wrote:
> 
> Hi Ian
> 
> part of the problem here is that  each vendor will then have their own
> proprietary settings,
> now most of us who use kannel for high volume messaging and have many links
> running and external applications that handle the routing - this would then
> mean that the routing apps would need to have specific knowledge of the
> optional/proprietary settings for each gateway. Part of the idea of Kannel
> is to abstract the links so external apps do not need to know anything
> about the various protocols and connections.  Then the next issue is how to
> pass these through from smsbox.
> 
> so -1 for this going to CVS,

I couldn't have frazed it clearer ;). Thanks Nisan.

Same for me: -1 in adding spefiic vendor things to SMPP.

Ian: you can think of how we could leaverage the SMPP module to
"handle" vendor specific things. Like a dependency SMPP client
implementation modole. But this is way out of scope currently for the
group I guess.

Stipe

mailto:[email protected]
-------------------------------------------------------------------
Wapme Systems AG

Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany

phone: +49.211.74845.0
fax: +49.211.74845.299

mailto:[email protected]
http://www.wapme-systems.de/
-------------------------------------------------------------------

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.2.2 (Cygwin)

mIsEP6mcYwEEAMDnUiUwrbb+xwTFWN6TxF2+XZu7/alwJMeCwMBRvXtPZqfjpPhS
OkBpU0F4TrVuugz1HINTSaJTYq10AzDQXp5NkyWgckqW79nPAWuOX0dicbJk+cN2
nM2TI4KaxUDe6u8hghNEnH/i2lXsUu9apnP/iixzV81VC2je3uc9hZpnAAYptEVT
dGlwZSBUb2xqIChUZWNobm9sb2d5IENlbnRlciAmIFJlc2VhcmNoIExhYikgPHRv
bGpAd2FwbWUtc3lzdGVtcy5kZT6ItAQTAQIAHgUCP6mcYwIbAwYLCQgHAwIDFQID
AxYCAQIeAQIXgAAKCRABV0w1BqPYRuSqA/wPzsQxao2YePENCtgRTrO86U6zg3sl
OcS6CJFI4FZP5h/xD3GRsNH1+MPSvZlomDdpFnr547DGz/Kq9MXuQwVvlVig5yWZ
K5dtKp1r5YLhxJQBhfirZbRFFnYmf19f18J8OoS28tuFVftDl1AIwJS3HLyBTv6H
g2HyLAEKQIp30Q==
=aYCI
-----END PGP PUBLIC KEY BLOCK-----