Send long text SMS to midlet result in decode error

Send long text SMS to midlet result in decode error SearchSearch
Author Message
Yang guanjin
New member
Username: Taihood

Post Number: 1
Registered: 01-2007
Posted on Thursday, January 04, 2007 - 06:48 am:   

Hi All,
I am a new mobile application developer.
I have managed to send text SMS to a midlet with Now SMS gateway by supply the UDH with port number, eg: udh=06050420082008 for port no. 8200.

This is working:
http://10.10.10.53:8800/?PhoneNumber=91370775&udh=06050420082008&Text=Hello+how+ r+u%3F

However, when the message is exceeding 152 characters(8 bytes used for UDH), the midlet listening to port 8200 is able to receive but cannot correctly decode the message. Following will display garbage in the midlet:
http://10.10.10.53:8800/?PhoneNumber=91370775&udh=06050420082008&Text=kdfiojfslf oufosuogudoguifduiogosjgljgosufgiodosgljdgjoiuodflgjldfgdlfiiiiiiiiiikkkiiiiiiii iiiiiklfjhgsljgdlfgiiiiiiijjjjjjkfffffdgjdjdjdjdjdjdjdjdjkgllllllllllll

But if I removed the UDH option above, it will go the phone's normal SMS box with correct content. I guess maybe there is uncompatible encoding scheme between Now SMS Gateway and Java WMA regarding of long message segmentation and reassembly.
Or did I miss some options? I tried to set the DCS=F5 and DCS=04, but these will result in receiving binary message in the midlet, that is not what I want. I want text message larger than 152 characters, anyone can help me?


I check the SMS out log:
2007-01-04 12:23:23,SAR-91370775-36-2-1.req,10.10.10.53,91370775,OK -- iTegno WM1080A #2,Binary=1;UDH=0B0060201050420082008;Data=6BB239FD569BE76CF3BB6E7ECFEBEF739DFC3 ED7D366723DFD3EBFE7EA335B7D7ECFEBE673FA4D7ECFCF6C35F9AC7EA7EB6FB2997D56B3C9E6339 96D4EA7D3E9743A9D4EA7D7EB753A9D4EA7D3E9743A9D4EA7D76CB31A7D9EB3D56732DB7C4EA7D3E 9743AAD56ABD56AF5DA6C369BCDE4B39AAC26ABC96AB29AAC26ABC96AB2

2007-01-04 12:23:26,SAR-91370775-36-2-2.req,10.10.10.53,91370775,OK -- iTegno WM1080A #2,Binary=1;UDH=0B0003360202050420082008;Data=7A7D66B3D96C369BCD66B3D96C

2007-01-04 12:24:37,SAR-91370775-37-2-1.req,10.10.10.53,91370775,OK -- iTegno WM1080A #2,Binary=1;UDH=050003370201;Data=D66473FAAD36CFD9E677DDFC9ED7DFE73AF97DAEA7CDE4 7AFA7D7ECFD567B6FAFC9ED7CDE7F49BFC9E9FD96AF259FD4ED7DF6433FBAC6693CD6732DB9C4EA7 D3E9743A9D4EAFD7EB743A9D4EA7D3E9743A9D4EAFD96635FA3C67ABCF64B6F99C4EA7D3E9745AAD 56ABD5EAB5D96C369BC96735594D5693D56435594D5693D564F5FACC66B3D9

2007-01-04 12:24:40,SAR-91370775-37-2-2.req,10.10.10.53,91370775,OK -- iTegno WM1080A #2,Binary=1;UDH=050003370202;Data=D86C369BCD66B301

The later two SMS is without specify UDH and correctly deliver to SMS box.
Yang guanjin
New member
Username: Taihood

Post Number: 2
Registered: 01-2007
Posted on Thursday, January 04, 2007 - 07:12 am:   

I think it is the port number specified in UDH affects the decoding, because it works exact the same way like sending long message from midlet to Now SMS Gateway.
In the midlet, when I use
MessageConnection con = (MessageConnection) Connector.open("sms://:8200");
to send message longer than 152 letters, it will be a decode error. However, when use

MessageConnection con = (MessageConnection) Connector.open("sms://phoneNumber");
everything works fine. Strange, is it?
Malcolm - Now Support
Moderator
Username: Malcolm

Post Number: 79
Registered: 12-2006
Posted on Monday, January 08, 2007 - 09:26 pm:   

Hi,

I can confirm that there is an encoding problem when submitting a long text message that includes UDH in this manner.

I have escalated this issue with our product development engineers. Unfortunately, I do not have any suggestions for a work-around at this time.

--
Malcolm
Now Wireless Support
Yang guanjin
New member
Username: Taihood

Post Number: 3
Registered: 01-2007
Posted on Wednesday, January 10, 2007 - 02:25 am:   

Thank you for your reply. Hopefully can get any fixed or patched soon.
Malcolm - Now Support
Moderator
Username: Malcolm

Post Number: 83
Registered: 12-2006
Posted on Wednesday, January 10, 2007 - 07:11 pm:   

We are currently working on an update to address some issues with Windows Vista, and hope to include a fix for this issue in the patch. We are targeting this to be in the next 2 weeks.
Malcolm - Now Support
Moderator
Username: Malcolm

Post Number: 92
Registered: 12-2006
Posted on Thursday, January 11, 2007 - 09:34 pm:   

Good news!

There is a "preliminary" fix available that addresses this problem.

It is included with an update release that addresses some Windows Vista compatibility issues, so the download is somewhat large. The download link is http://www.nowsms.com/download/nowsmsvista.zip

(The download is not specific to Windows Vista, it continues to support XP/2003/2000.)

--
Malcolm
Now Wireless Support
Yang guanjin
New member
Username: Taihood

Post Number: 4
Registered: 01-2007
Posted on Thursday, January 25, 2007 - 03:09 am:   

Nice work, Thank you.