Multipart texts reported delivered but are not received in their entirety by recipient.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create separate Jabber and Google accounts and configure as recommended.
2. Sign into Pidgin and initiate gtalksms connection on phone.
3. Confirm 2-way communication between phone and laptop: all commands 
functional.
4. Send multipart (ie long) SMS via "SMS:*contact*:" command from Pidgin.  
5. Confirm message sent in entirety on phone.
6. Confirm message (not) received in entirety with contact.

What is the expected output? What do you see instead?
Expected output: SMS reported sent and delivered in Pidgin.  Recipient receives 
message in its entirety.
What I see instead: SMS reported sent and delivered.  Recipient receives only 
the first part of the multipart text.

What version of the product are you using? On what operating system?
gtalksms v1.7.1 on Oxygen 2.0RC6 'Gingerbread' for HTC Desire (GSM).  Pidgin 
v2.7.9 on laptop PC (Windows 7 Professional 64-bit)

Please provide any additional information below.
Problems occurred whilst connected to Vodafone UK EDGE network with good 
connection strength.  Laptop PC was connected to the HTC Desire's WiFi Hotspot 
with WPA2-PSK encryption.  No opportunity to test on HSPA/3G network, or test 
using separate phone & computer internet connections due to constraints at 
current geographical location.

Thanks.

Original issue reported on code.google.com by milchpu...@gmail.com on 13 Jan 2011 at 2:29

[GoogleCodeExporter]

Can you please reproduce the problem and generate an application log? 
Instructions are at http://code.google.com/p/gtalksms/wiki/GenerateAppLog

Original comment by fschm...@gmail.com on 13 Jan 2011 at 8:12

[GoogleCodeExporter]

Do you use special characters ?
How many characters did you send ?
What was the target cellphone model ?

Original comment by Florent....@gmail.com on 16 Jan 2011 at 12:32

• Changed state: NotReproduced

[GoogleCodeExporter]

Sorry guys for taking so long to answer.  I've been extremely busy with work.  
I was testing with the phone and laptop on a separate WiFi connection the other 
day and the result was just fine, even with long messages.  I don't use special 
characters and the target phone were a Samsung Diva and a Samsung Monte.  The 
first text that didn't send through was 1119 characters.  The second was 1735 
characters.  I used an online Javascript-based counter to count the characters. 
 I wonder if my issue has anything to do with the fact that I'm WiFi tethering 
my laptop over a shoddy connection (3-10kBps up/downstream EDGE).  There are no 
errors in the application log.  Sorry if I'm wasting your time and thanks for 
your help thus far :)

Original comment by milchpu...@gmail.com on 16 Jan 2011 at 12:56

[GoogleCodeExporter]

I've just test to send messages to myself, 1000 and 1500 characters and that 
works fine. Maybe that's your mobile provider limitation ?

Original comment by Florent....@gmail.com on 16 Jan 2011 at 1:18

[GoogleCodeExporter]

Yeah I did think that, however I sent the 1735 character again straight from 
the phone and it actually went through just fine.  The longest message I've 
sent through my phone was well over 2000 characters.  I'll continue testing and 
get back to you.  Will remember to upload some logs next time I send a long 
text!

Original comment by milchpu...@gmail.com on 16 Jan 2011 at 8:08

[GoogleCodeExporter]

Oki, thanks for your feedback

Original comment by Florent....@gmail.com on 16 Jan 2011 at 8:14

[GoogleCodeExporter]

Original comment by Florent....@gmail.com on 28 Feb 2011 at 8:52

• Changed state: Invalid