@@@BINARY@@ Parameter Problem | Search |
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through February 02, 2006 ⬆ |
◄ ► |
Author | Message | |||
online New member Username: Online_star Post Number: 1 Registered: 12-2005 |
Hello, i have a small problem when using the @@BINARY@@ parameter to know the SMS type text/binary. That replacable parameter returns "0" always (in text or binary). So what is the solution?? Thanks | |||
online New member Username: Online_star Post Number: 2 Registered: 12-2005 |
Any Help??? | |||
online New member Username: Online_star Post Number: 3 Registered: 12-2005 |
Any body knows the solution??? | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5415 Registered: 10-2002 |
Hi, I tried a simple test here to try to recreate your problem, and I don't see any problem (I got "1" when the message was binary, and "0" when it was text). So, in order to understand the problem. I think I'd need to see an SMSDEBUG.LOG showing the message being received ... and that would then show the 2-way command being executed. -bn | |||
online New member Username: Online_star Post Number: 4 Registered: 12-2005 |
Thanks for the reply , but i think there is something i missed to explain to you: The binary message i mean is the Arabic text. So i want to know if the incoming message text is arabic or english by that @@BINARY@@ parameter, and still giving me "0" with the both. Any ideas? | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5465 Registered: 10-2002 |
If the text is Arabic (or Chinese or ...), it's still text. It does get transmitted over SMS in Unicode format, instead of standard GSM text. But basically, the underlying format is text, even if it is Unicode, so we deliver it as text to a 2-way command. The only thing I can think of would be to evaluate the characters in your application logic to decide whether or not the text is Arabic. Or alternatively, I think that if you use the file based interface (SMS-IN directory), we leave the message in raw Unicode format ... and it only gets translated to text when it gets processed by the 2-way command facility. So you might want to look at that. Another question that comes up a lot with people who are trying to process Arabic text ... is that they want the text to be passed to the 2-way command in the native Arabic character set (whereas NowSMS uses UTF-8). More on that here: http://support.nowsms.com/discus/messages/1/4906.html |