Hi Mariella,
the last mail was just a typo by me, it was OK to send that directly
to me, but this is a whole new problem. In a normal case always
respond to the list, because you are shurely not the only onefacing a
problem..
If you send this SMS to an application you have allready installed,
you could "invent" something like your own "TCP over SMS" protocol.
But I strongly not recommend this! Mind that a SMS can only contain
140 Byte of data. if you want to transfer a only 32 kB large jar-file,
that would be 235 SMS(!!!) not containing headers (mind that SMS could
overhaul each other or you might have transport problems, checksums
and so on). Given you pay 6 cent per SMS that would be about 13€. It's
cheaper to put the program on a memory stick and send it with snail
mail! ;-) And, by the way, most phones only store a maximum of 100
messages.
I would always prefer to simply send a small SMS with an URL inside to
the phone and then the phone loads the content via WAP.
If you not want to send the .jar file to your application but to the
phone in general, WAPPUSH is your friend. Wappush is a special form of
SMS that, when received, automaticly starts a download from a given
WAP or Internetaddress, after the user has confirmed. Kannel is a very
effective tool for generating Wappush. Read a little bit in the
internet about Wappush and "Push Proxy Gateways" (PPG). After that
read the chapter "Setting up a ppg" in the kannel manual and there you
go...
Regards
Falko
Am 16.02.2009 um 18:28 schrieb [email protected]:
hi falko,
if i wanted to send file.jar in a sms, what should i do?
Thanks
----Messaggio originale----
Da: [email protected]
Data: 13/02/2009 18.17
A: "[email protected]"<[email protected]>
Ogg: Re: R: Re: R: Re: send sms to application on specific port on
phone
Ahh, yes sorry, You have to set the "%"-sign, but before every
octet:
&udh=%06%05%04%C3%51%C3%51
Here I set source and destination por to 50001. 50001 decimal is 0xc3
0x51 hex. The source port is only "virtual". So the idea is that you
can defined different source-ports inside your application. If the
"sourceport" is 25, handle the object like email, if it's 80 handle
it
like http... But in most cases you can simply ignore the sourceport.
Regards
Falko
