If you send an SMS command message and ClearSCADA does not respond as expected, your SMS message may have failed. There are several possible causes for failed SMS commands, and so if you suspect your SMS message has failed, you will need to investigate the problem.
- If there are alarms relating to your SMS message shown in ViewX or WebX, the message has been rejected by ClearSCADA or the Pager Driver.
If the alarm Message contains:
- 'SMS command rejected by pager driver', see SMS Messages Rejected by the Pager Driver.
- 'Failed to process incoming SMS command', see SMS Messages Rejected by ClearSCADA.
- If there are no alarms relating to your SMS message, there are two possible reasons for your SMS command failing to achieve the desired effect:
- The SMS message that you sent contained a valid command, but the command has been performed on a different database item. This can occur if your message is incorrect for the intended database item and action, but the mistake in the message means that the command is valid for a different database item. For example, if you gave an alias the same name as an action for the 'Root' Group (System), sending that action for the 'Root' Group as an SMS command would trigger the action for the alias instead (the action associated with the alias in the configuration of the Method Call takes precedence over the action for a database item).
If you suspect that the SMS command may have been accidentally performed on an incorrect database item, display the Events List and examine the entries. If the SMS command was processed and actioned, it will be logged in the Events List for the system (and the Events List for the SMS Service).
- The SMS message was not received by the Pager Driver. This can mean that the SMS service provider has not sent the message, cannot send the message, or the message is delayed in transit.
The cause of the problem is related to your device or your service provider. Please contact your service provider for assistance.
- The SMS message that you sent contained a valid command, but the command has been performed on a different database item. This can occur if your message is incorrect for the intended database item and action, but the mistake in the message means that the command is valid for a different database item. For example, if you gave an alias the same name as an action for the 'Root' Group (System), sending that action for the 'Root' Group as an SMS command would trigger the action for the alias instead (the action associated with the alias in the configuration of the Method Call takes precedence over the action for a database item).
Further Information
Events in the ClearSCADA Guide to ViewX and WebX Clients.