Sorry. I have a single SMS message (ok, multiple, but lets just deal with one for now) that has a UDH and a binary body. Using 1.3.1.
I'm using an HTTP relay connection to an SMSC. The URL I use is this:
http://222.22.222.222/smschttp.php?from=%p&to=%P&text=%a&smsc=%i&coding=%c&udh=%u&textbin=%b&worthless=nothing
The worthless=nothing is there because the url called attaches ?username=xxx&password=yyy at the end.
When I get the UDH and the TEXT of the message passed to me, it is already in ASCII, which I then need to convert back into 0x00 characters so I can pass it to the SMSC.
The problem is that either I'm converting wrong or something else from the ASCII version kannel passes to the URL, or I'm using the send-url wrong.
Either way, a UDH in of 0B05041581... comes out 0B05040F51... and a whole bunch of other weird stuff.
Has anyone taken a binary message from kannel HTTP and gotten things to work?
Peter, I still don't "get it". Sorry. You are using the smsc_http module for this? Or you get an MO-SMS via an SMSC link and try to "forward" this via sms-service group to an "external HTTP server" that can be concidered as SMSC too?
Please drop some light on the connections and msg flow, to have this more understandable.
Stipe
mailto:stolj_{at}_wapme.de ------------------------------------------------------------------- Wapme Systems AG
Vogelsanger Weg 80 40470 D�sseldorf, NRW, Germany
phone: +49.211.74845.0 fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de 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-----
