Peter Beckman wrote:

Folks -- Having a little problem with kannel and binary messages sent via
HTTP.

Right now, I can't seem to successfully convert the text passed by kannel
via an HTTP relay connection back to the hex encoded string.

The original:

    UDH: 0B0504158100000003010301
    Txt: 
024A3A61A5B991858DB1D5880400D522CAEB2CD49082CAB12418400410B2AD49082CB312408B26D49082CAB12408B2CD49082CAB12418400410B2AD4

What I get from Kannel:

    [from] => #####
    [to] => 1##########
    [text] => J:aïïïïïïÕ\0ï\"ïï,[EMAIL PROTECTED],[EMAIL 
PROTECTED]&ÔïÊ$ïïI,ïAï\0A*ï
    [smsc] => ####http
    [coding] => 2
    [udh] => ï\0\0\0
    [textbin] => %b
    [worthless] => nothing?username=nada
    [password] => nada

I have a function that gets it close (taking each character and trying to
convert it to its binary then hex format, taking in account \0 is a null),
but not exact.

This is as close as I get:

    [udh]  => 0B05040F5100000003010301
    OrigUDH:  0B0504158100000003010301

    [text] => 
0204033D00005B550800005804000000000002005A520000181228040A0000310802000C28081A005A52000018080000310802000C29540029000200
    OrigTxt:  
024A3A61A5B991858DB1D5880400D522CAEB2CD49082CAB12418400410B2AD49082CB312408B26D49082CAB12408B2CD49082CAB12418400410B2AD4

Any suggestions? Here's my function that I use to parse:

Hi Peter,

first of all, please _do NOT_ crosspost to mailing lists. We consider this abuse. ;)

Ok, now regarding the question itself. Unfortunatly it's a bit to "unspecified" in terms of what szenario you are trying to solve. Could you please outline a bit more in details what you are trying to do?!

At least I didn't get the point... or am I missing the obvious? ;)

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-----



Reply via email to