setdevice

Send a new setting to a device.

Command's fields description:

• txtUser1 field is the “username” of MyWakes account.

• txtUser2 field is the “password” of MyWakes account.

• txtCommand field contains the command: “setdevice”.

• txtFormat optional field specifies txtParameters and response formats. more info.

• txtParameter field contains a structure like this:

<?xml version="1.0" encoding="utf-8" ?> 
<setdevice>
	<consumer>44</consumer>
	<imei>123456789012345</imei>
	<sender>+393351234567</sender>
	<phone>+393357654321</phone>
	<psw>0000</psw>
	<cmd>apn</cmd>
	<parameters>
		<par>apn.carrier.com</par>
	</parameters>
	<time>20101025183000</time> 
</setdevice>

{
  "setdevice": {
    "consumer": "44",
    "imei": "123456789012345",
    "sender": "+393351234567",
    "phone": "+393357654321",
    "psw": "0000",
    "cmd": "apn",
    "parameters": { "par": "apn.carrier.com" },
    "time": "20101025183000"
  }
}

Where

• <consumer> mandatory. It is the consumer's ID.

• <imei> mandatory. It is the consumer's IMEI code.

• <sender> optional. Can contain the sender telephone number. If used, the confirmation message from the device will be sent to this number.

• <phone> mandatory. Telephone number of the SIM into the device.

• <psw> mandatory. Device's password.

• <cmd> mandatory.The command to execute. Depending of the command and the device it will need more or less parameters. Here is the list of existing commands per device and their parameters.

• <parameters> a collection containing the command's related parameters.

  • <par> command's parameter. This tag is repeated for each parameter required for the specific command..

• <time> mandatory, date and time in UTC. The accepted format is “yyyyMMddhhmmss”.

• txtProvider field must contain the application calling ID and generated characters.

• txtSignature field must contain the signature based on the string made of “Command Name” + “consumer” + “time” + “generated character to 32”.

Looking at the previous example, the string on which calculate the check will be:
“setdeviceI123420101025183000xxxx”

Therefore the txtProvider field will be:
“76a865d4-fab8-51cd-ba78-2da325f6955axxxx”

Returns a structure like the following:

<?xml version="1.0" encoding="utf-8" ?> 
<furesult> 
	<message><![CDATA[ OK ]]></message>
	<smsres>OK</smsres>
	<sms>25</sms>
</furesult>

{
  "furesult": {
    "message": " OK ",
    "smsres": "OK",
    "sms": "25"
  }
}