Quote:
Originally Posted by inquisitor
100 bytes? That's impossible. I doubt there's any compression algorythm that can shrink 160 bytes of text + overhead (e.g. recipient's number) to 100 bytes. Further you forget all the header information of the HTTP-request on TCP/IP-level. I fear you can't send any SMS over TCP/IP with less than 512 bytes.
|
OK. I was wrong. Here is the info from the smsBug FAQ:
Q: So how much GPRS traffic does smsBug typically use?
A: Below is a table of typical smsBug transactions and the traffic generated by them.
Registering (Part I) | 422 bytes in | 240 bytes out
Verifying password (Part II) | 420 bytes in | 188 bytes out
Sending a 160 character SMS | 422 bytes in | 500 bytes out
Synchronizing 5 Contacts | 709 bytes in | 194 bytes out
Requesting remaining credits | 422 bytes in | 155 bytes out
Setting Delivery Report status | 421 bytes in | 188 bytes iut
Purchasing credits | 422 bytes in | 260 bytes out