@-sign in SMS messages? | Search |
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 15, 2003 ⬆ |
◄ ► |
Author | Message | |||
Aki-Ville Pöykiö |
Hi, I trying to use @-sign in incoming messages, should they come through as normal characters, or are they somehow special since they are used in "variable" names in urls such as @@something@@ and so forth. so if i have a @-sign in a incoming SMS message, should it come through with no problems, or is it just me? greets, aki | |||
Bryce Norwood - NowSMS Support (Bryce) |
Aki, The "@" symbol should come through just fine. If you're having a specific problem with a message not being encoded (or decoded) properly, please send us a debug log. To enable debug mode in the gateway, manually edit SMSGWS.INI, and under the [SMSGW] section header, add the statement Debug=Yes. Then restart the gateway. Repeat whatever action to take to create the problem message. Send the resulting SMSDEBUG.LOG to nowsms@now.co.uk. (If you're connecting over SMPP, UCP/EMI or CIMD, also include the SMPPDEBUG.LOG, UCPDEBUG.LOG or CIMDDEBUG.LOG as appropriate.) -bn | |||
Aki-Ville Pöykiö |
Ok correction. It was not the *-sign, it was a line feed in a message that made the gateway go crazy! With SonyEricsson T68 one can add a /n (or is it \n) to a message as a carriage return or line feed or what you call it. When this kind of message is sent to the gateway, the message gets stuck! Gateway processes the message again and again and again... I removed the /n from the incoming SMS file under SMS-IN directory and message finally came unstuck. Is this a bug or a feature? Thank you for the swift responses! Greets, Aki | |||
Bryce Norwood - NowSMS Support (Bryce) |
Hi Aki, Let me know exactly what you're entering in on the T68, and I'll check it out. I know we do some escaping of our own on new line characters, so maybe its ending up as double escaped causing some problems. -bn | |||
Aki-Ville Pöykiö |
well, my message just had text, then in the middle of text it had the line feed character that you get when pressing #-sign 3 times on T68i. it showed up in the file as /n. i think straight after that there was a @-sign, that's why i thought it to be the culprit at first. i was doing no escaping of my own, since it was a message coming straight from the phone. i can send you the same SMS message if you have some number to send it to, the message is still stored in my phone. greets, aki | |||
Bryce Norwood - NowSMS Support (Bryce) |
Aki, Sorry to take so long to get back to you on this. I wanted to sort out a test environment, but now that I have, I see it is easy enough to generate an SMS message with carriage return/line feed by submitting a text SMS message through the web interface of the gateway. I take it that you're running a two way command (against an HTTP URL?) ... and I can see where this would cause the HTTP request to be malformatted, as we should be escaping the CR/LF in the HTTP request. Is that what is happening to you? I'm trying to get a patch together to fix this ... -bn | |||
MarkDunham |
Hi, I'm having the same problem.. if a user send an SMS with a CR/LF in it the gateway goes nuts and get stuck in a loop sending that first line of the SMS over and over again.. whats the answer, or is there a fix.. Cheers, ta, etc.. MArk. | |||
Bryce Norwood - NowSMS Support (Bryce) |
Mark, Is the 2-way command an HTTP request, or is it a command line request? (The above was about an HTTP request, which we addressed, so I'm guessing there might be an issue with the command line request?) -bn | |||
Bryce Norwood - NowSMS Support |
Just an FYI ... should have thought of this in the response to Mark. There was a fix for this problem (carriage return/line feed in a received SMS message causing a malformed URL request if the configured "2-way" command was an HTTP request) included in the v4.20 release. | |||
Aki-Ville Pöykiö |
hi Bryce, thank you for the replys and especially for the fix. and yes, i was running 2-way command with HTTP req. but i guess it is all good now. -aki |