PrePaidGSM.net Forum (Archived)


Reply
 
Thread Tools Search this Thread Display Modes
Old
  (#1)
inquisitor (Offline)
Senior Member
Prepaid Professionist
 
inquisitor's Avatar
 
Posts: 1,399
Join Date: 15 Nov 2006

Country:
Default 20-09-2008, 16:07

Quote:
Originally Posted by DRNewcomb View Post
I'm not sure about FishText but as I recall smsBug only takes about 100 bytes to send a SMS. If you only send a few per day it looks like 02 would never charge you for the data.
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.

Take this example: the request has 50 bytes, the response 286 bytes and that's without those 160 bytes, which need to be transferred and without the at-least 12-digit number of the recipient. Furhter the request should contain some authentification information. So no way to stay below 512 bytes!


terminals: Samsung: Galaxy S5 DuoS (G900FD); BLU: Win HD LTE; Nokia: 1200; Asus: Fonepad 7 ME372CG; Huawei data: E3372, Vodafone R201, K3765, E1762;
postpaid: O2 on Business XL; prepaid: DE: Aldi Talk, Lidl; UK: 3; BG: MTel, vivacom; RU: MTS; RS: MTS; UAE: du Tourist SIM; INT'L: toggle mobile
VoIP: sipgate.de (German DID); sipgate.co.uk (British DID); ukddi.com (British DID); sipcall.ch (Swiss DID); megafon.bg (Bulgarian DID); InterVoip.com

Last edited by inquisitor; 20-09-2008 at 16:38..
   
Reply With Quote
Old
  (#2)
DRNewcomb (Offline)
Senior Member
Prepaid Professionist
 
Posts: 1,465
Join Date: 27 Feb 2004
Location: Mississippi, USA

Country:
Default 20-09-2008, 20:07

Quote:
Originally Posted by inquisitor View Post
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
   
Reply With Quote
Reply

Tags
travelsim, travelsimshop


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is On




Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2025, vBulletin Solutions Inc.
vBulletin Skin developed by: vBStyles.com
© 2002-2020 PrePaidGSM.net