"Arne K. Haaje" wrote: > > > Yes, I know - but that is what they are using.. To send an SMS you craft a > packet then send it over HTTPS. > > I am okay with the encryption for the transport, but why use HTTP (S). Why not > just connect to a SMSC that speak the protocol natively? There is also the > issue of 1 SMS/sec they have. Wonder what they do with votes etc. from a TV > program... > > Telia has always been a bit strange..
which means you have to pass the UCP string via HTTP GET/POST over HTTPS to them? ... what kind of perversion is this?! I guess they use HTTPS for getting the security purpose "done"?! Seems they never heard of stunnel (for SSL-enabling TCP server-client applications) or of VPNs. I wouldn't call this strange, but "perverted". So if it is that way, then: no, Kannel does not support this. ;) You'll be on your own to get either: a) implement the UCP string encapsulation into gw/smsc/smsc_http.c for a special 'telia' type. b) tell them to give you a native UCP account and use SSL tunnel or VPN for security. Stipe mailto:[EMAIL PROTECTED] ------------------------------------------------------------------- Wapme Systems AG M�nsterstr. 248 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-----
