2006-04-04 05:21:54

SmsRc and MSSQL

Microsoft SQL Server supports a very powerful SQL dialect. A lot of our customers prefer to use SmsRc just as a gateway between the phone and the server, implementing all SMS-handling logic in the server's stored procedures.

For this type of project, the file with just one ExecuteSQL action must be created. The SQL statement must call the stored procedure that is ready to handle incoming messages. Using appropriate ODBC escape sequence, the statement will look like this one:

{ CALL sp_incoming_sms ( [%Timestamp%], [%Sender%] , [%Message%] ) }

Returning the Answer

There are two ways to send the answer from the stored procedure.

The procedure may return one row of data, so the values in its columns will be assigned to SmsRc variables. “Expected result format” field in the action must be set to “one selected records”, and the «Store result to variable(s)" field must contain variable names, corresponding to columns, separated by spaces. Then you may add a “Send SMS” action, using the variables returned from the procedure in the message body.
The procedure may insert rows into the table named OutgoingSMs, thay may be created with the following statement:
CREATE TABLE OutgoingSMs ( [MsgID] int IDENTITY (1, 1) NOT NULL , [MsgText] nvarchar (254) NOT NULL , [MsgStatus] int NOT NULL , [MsgTarget] varchar (12) NOT NULL ) ON [PRIMARY] GO
As the rows get inserted into this table with MsgStatus=0, SmsRc will try to send out appropriate messages and update MsgStatus to 1 on success, 2 on error.

2006-04-04 05:08:01

edited by AntonKovalenko

2006-04-04 05:02:57

edited by AntonKovalenko

2006-04-04 05:01:21

edited by AntonKovalenko

2006-04-04 05:00:18

edited by AntonKovalenko

Sw4me - SMSReceptionCenter/MSSQL

2006-04-04 05:21:54

SmsRc and MSSQL

Returning the Answer

2006-04-04 05:08:01

2006-04-04 05:02:57

2006-04-04 05:01:21

2006-04-04 05:00:18