| No action taken according to SMS command table after receiving SMS |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through February 20, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| kuo Unregistered guest |
I am using Sierra AirCard 750 as modem for Now SMS Gateway. I have enabled to allow processing SMS received and defined the command table to run console program echoing the SMS message in the 2-Way tab. After I sent SMS from another phone or online to this modem, the SMS is received in the SMS-IN folder successfully. But the echo program is not run. Could anybody help me with this problem? Thanks | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1357 Registered: 10-2002 |
Hi Kuo, Does the message file remain in the SMS-IN subdirectory? Does it have a .IN or .SMS extension? If it has a .IN extension, then NowSMS has not yet processed the 2-way command against the message. (Possibly there is an error occurring executing the command, and NowSMS is retrying. This situation happens more with HTTP commands than it does with executables like the ECHO example.) If it has a .SMS extension, then NowSMS has evaluated the 2-way command table, and there was no match. NowSMS looks at the "SMS Command Prefix", and tries to find a match between that text and the first word (up to the first white space) of the received SMS message. A prefix of "*" matches all messages, but any other text expects a match. So perhaps you did not specify "*" as the command prefix? Another possibility is that the received message contained binary data. Binary format messages are never processed by executable 2-way commands. (They can be processed by HTTP based 2-way commands, see: http://support.nowsms.com/discus/messages/1/456.html) Another issue is that if the message comes from an alpha sender (perhaps an SMS message sent through a service provider where the sender address is a text field instead of a phone number), then there is a bug in most versions of the Sierra Aircard 750 firmware which can cause NowSMS to interpret the message incorrectly. To get around this, under the [Modem - Sierra ...] section of the SMSGW.INI file, add AlphaSenderAddressBug=Yes. (Note that you can't reply to a message from an alpha sender ... but this particular problem can be an issue with receiving MMS messages where some service providers send out the MMS notification with an alpha sender in the SMS that carries the notification.) All this said, if you still can't determine the problem, then take the following action: Manually edit SMSGW.INI, and under the [SMSGW] section header, add Debug=Yes. Restart the SMS gateway service. Send in another message to the phone number of the modem. Post the SMSDEBUG.LOG and your SMSGW.INI file, or e-mail them to nowsms@now.co.uk. -bn | |||
| BHASKAR Unregistered guest |
can you tell me about how to generate SMS command in a handset ? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1910 Registered: 10-2002 |
Sorry, but I don't understand your question. The process of creating and sending an SMS message varies from handset to handset. If you are unsure how to create an SMS message, please refer to the documentation/manual for your handset. If you are thinking that there is something different between sending an "SMS message" and sending an "SMS command", then I think you are just getting confused by the terminology. There is no difference. What people are talking about here is sending an SMS message in to a phone number where the message is received by a gateway, and the gateway treats the received message as a command, performing different actions based upon the text of the SMS message. -bn | |||
