| EMS Animation and 150 '@' symbols |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 15, 2006 ⬆ |
◄ ► |
| Author | Message | |||
| Nelson New member Username: Nelson Post Number: 8 Registered: 01-2006 |
Hi, We're experiencing some problems when sending EMS messages: 'Send EMS Message' 'EMS Text' Select a "Smiley" (e.g. <animation val=glad/>) When the message is received, there is a string of 150 '@' symbols after the emoticon. This was tested on a few different handsets, with the same results. I did a search on the forum, but couldn't find (anything that I understood to be) the same problem. I've also unzipped the latest patch, but I'm unsure as to whether I need to activly install anything, or if unzipping is enough? Thanks in advance! | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6366 Registered: 10-2002 |
Hi Nelson, I just tried sending such a message to 4 different handsets, and didn't experience any problems like you describe. I sent to a SonyEricsson W800 and Motorola RAZR V3i, both of which displayed the message correctly, with just the "glad" animation and no text. I also sent to a Nokia 6600 and a Blackberry 8700 ... both of which do not support EMS ... and they correctly displayed only a blank message. So I'm suspecting that either there is something different about your SMSC connection, or the phones that you are sending the message to. I'd test to suspect the SMSC connection. I used a GSM modem for this particular test. The only thing I notice that is unusual is that the message that is sent out contains only UDH (user data header). Which makes me think ... I know that we just recently resolved an encoding problem that could occur when sending some SMS messages that only contain UDH over a GSM modem. I'll bet that is the problem that you are experiencing. If I roll back the version of NowSMS that I am running, the GSM modem that I am using in my laptop will refuse to send out this particular message unless I add some text to it. If I update, the GSM modem sends the message out just fine ... and it is received just fine. We did recently find a problem with our GSM modem encoding when sending a message out that contains only UDH ... so whereas my modem rejects this message ... your modem is sending it out ... but the receiving handset is confused by the encoding. (@ is encoded as a null in the GSM character set, so the receiving handset is not properly detecting the end of the message.) The current official update doesn't include this fix yet. But I did just post an interim update this week at http://www.nowsms.com/download/20060815.zip which does include this fix. To install the update, unzip and use the files in the ZIP to overwrite existing files in your NowSMS installation directory. If you are not using a GSM modem to send out the message, then it is probable that the SMSC to which you are connecting is having a similar encoding problem in converting a message that contains only UDH into the proper GSM over-the-air format. If this is the case, I'd like to take a closer look at your debug logs to verify that the problem is not ours. -bn | |||
