SendSMS and WaitForSMS

The SMS Send and Receive actions communicate either through a serial port, Bluetooth connection, infrared port or any TAPI compliant device. When using the COM port directly, device properties must be setup properly before you can start to send or receive messages. When using TAPI, these settings are controlled by the TAPI telephone driver, and should be configured through the TAPI settings as described below:

• Open the Windows Control Panel;

• Double-click on 'Phone and Modem Options' and select the 'Modems' tab;

• Select the preferred modem and click on 'Properties'; from here, you can change the settings.

To select a TAPI device in the toolkit's object, you must assign the Device member:

• Device - the literal TAPI device string, for instance: 'Standard 9600 Modem'.

If you prefer not to use TAPI, you must assign COM port properties through the following member variables:

• Device - the actual COM port device, formatted as COM x, where x represents the COM port number;

• DeviceHwFlowControl - hardware flow control is used to regulate commands from PC to device and visa versa; default: On;

• DeviceSwFlowControl - software flow control is used to regulate data from device to device; default: Off;

• DeviceSpeed - the speed to be used to communicate with modem or GSM phone; default: 0 (which means that factory defaults are used for modem communications);

• DeviceSettings - the number of databits, paritybits and stopbits; default: 8 databits, no parity, 1 stopbit;

• DeviceInitString - the modem initialization string is used to initialize the modem; default value: "" (which means a generic initialization string will be used).

Before you can actually send an SMS or Pager message, the Toolkit needs to know a bit more about the sender, recipient and the actual message. Therefore, you must assign the following properties:

• Sender - the phone number of the sender of the message; only digits are allowed. The sender address will be displayed on the recipient's mobile phone. If not assigned, 00000000000 will be used as sender address;

• Recipient - the phone number of the recipient of the message; if not specified, the message cannot be sent;

• MessageText - the actual message body, containing any character. Maximum message length is 160 characters when using normal (non-Unicode) text. When Unicode is used, you can only send 70 characters;

• Dial-in number of the SMS/Paging service provider (not required if you send a message through a directly connected GSM phone).

If you send through an SMSC provider, you must tell the component which provider protocol you are going to use:

• ProviderType - the type of protocol requested by the provider. You can choose: UCP or TAP.

Important: Sending an SMS through a service provider requires special knowledge of the protocol and provider requirements of your equipment. A provider requires its own speed (1200 bps is most common, but also 300 and 2400 are also often required), data format (7 databits, no parity, 1 stopbit or 8 databits, even parity and 1 stopbit) and provider type (UCP or TAP).

Supported Phone Models

The following table depicts the supported phones by AVEVA Work Tasks: