Other receiving blank or un-openable text messages

[GoogleCodeExporter]

What steps will reproduce the problem?
1. open a connection to the Jabber contact in Pidgin.
2. type sms:CONTACT:a message
3. wait for message to be sent

What is the expected output? What do you see instead?
I would expect that the person I sent the text to would receive the text I sent 
(i.e. "a message").  Instead, the person is receiving a blank text, or a notice 
on their phone that the message can't be opened.

What version of the product are you using? On what operating system?
1.7.2 of GTalkSMS on a Motorola Droid.  Sending IM using Pidgin 2.7.3 on Ubuntu 
Linux (10.10 Maverick Meerkat).  Sending from my @gmail.com GTalk account to a 
jabber account used exclusively by GTalkSMS.

Please provide any additional information below.
Unfortunately the behavior is intermittent and I'm unable to precisely 
replicate the problem.

Original issue reported on code.google.com by christop...@gmail.com on 18 Jan 2011 at 10:05

[GoogleCodeExporter]

I've some question in mind to find your problem:

What is the targeted phone and its OS ?
Did your message contain special characters ?
What the length of the message ? (if > 160 do you set "convert to mms" option 
in android preferences?)
What is the encoding used by your linux pidgin version ?

Original comment by Florent....@gmail.com on 18 Jan 2011 at 10:15

[GoogleCodeExporter]

The targeted phone that gets the "cannot open" I don't know.  The phone that 
gets the blanks is a Samsung Caliber on US Cellular.

The message I sent most recently was to the unknown.  Unusual characters 
included #, &, and :.  I also sent a number which when I view it on my Android 
is hyperlinked (but I didn't hyperlink anything in Pidgin).

I can't find the setting you speak of.  I should probably mention that I am 
using Cyanogenmod.  I can say undoubtedly that the message was < 140 characters 
(in fact it was 132 characters).  From everything I read about Pidgin, it 
defaults to UTF-8.  

Original comment by christop...@gmail.com on 18 Jan 2011 at 10:56

[GoogleCodeExporter]

Can you try to send again the same message to the same phone without using 
GtalkSMS to know if the problem come from the app or the tel?

Original comment by Florent....@gmail.com on 18 Jan 2011 at 11:05

[GoogleCodeExporter]

Fortunately, I did do that right after it happened.  When I opened my phone and 
manually texted the identical message, it went through.

Original comment by christop...@gmail.com on 18 Jan 2011 at 11:19

[GoogleCodeExporter]

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

• Changed state: Invalid