Re: Inbound capture of WAP Push Trigger over SMS for MMS

El mar, 28-10-2003 a las 16:27, Alex Judd escribió:

Just a stupid question, how will you download the binary data from the
MMSc center?, cause (at least in Spain) the operators has the MMS
content available via GPRS but on a private network, not available
through the Internet.... :-?

Best regards,

> Hello everyone
> 
> Has anyone managed to convince a handset to parse the inbound WAP Push
> trigger for an MMS message to be pushed to Kannel rather than read
> automatically by the handset?
> 
> According to the docs on the Now SMS gateway (the commercial competition
> :-) ), they're using a handset that isn't MMS compliant to catch the SMS
> that gets sent to phones that can't receive MMS content to use the embedded
> URL in that to go grab the content.
> 
> This strikes me as a pretty long route to what we're trying to achieve.
> 
> So, ideally, we should be able to catch the WAP Push SMS in Kannel, decrypt
> into the parameters and content URL, download the binary MMS content from
> the MMSC and then decrypt this (externally to Kannel using the Nokia
> libraries or similar).
> 
> If I can grab the initial binary SMS I can do the rest - any bright sparks
> know a way to do it?
> 
> Cheers
> 
> Alex
-- 
--------------------------------------------------------------------------
|Juan Enrique Gomez Perez
|Metropoli2000 Networks, S.L.
| Phone: +34 914250023 Fax: +34 914250136
| email: [email protected]
--------------------------------------------------------------------------
PGP Fingerprint: 6B39 3A2B A17B 1E8E CFFD  FC14 678E 0A22 BD80 C486
Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBD80C486

If this message hasn't a correct signature please notify 
it to [email protected]. To get the public key please
use the above url. Thanks for your help.
--------------------------------------------------------------------------

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQA/noyNZ44KIr2AxIYRAubeAJ46O8beakokrv7Xo8cNLFTsXLlcVACg54Z6
lbV5DLqlf4hZMf3rzRTvAYY=
=FAK1
-----END PGP SIGNATURE-----