1.5 AT^SSTR Remote-SAT Response – Generic Format
Test command
AT^SSTR=?
Read command
AT^SSTR?
Write command
AT^SSTR=
<cmdType>,
<status>
[,<itemId>]
[,<inputString>]
Response
^SSTR:(list of supported <state>s), (list of supported <cmdType>s)
OK
Response
^SSTR: <state>, <cmdType>
OK
Parameters |
|
<state> |
<cmdType> Ongoing Proactive Command (values see chapter 1.1.4 “Command Type Values”). However, this information is valid during states PAC and WAIT only.
The TA is expected to acknowledge the ^SSTGI response with AT^SSTR to confirm that the proactive command has been executed.
AT^SSTR will also provide any user information e.g. selected menu item.
Response
During execution of a Proactive Command after AT^SSTR a response parameter line may be issued by the ME:
^SSTR: <pac>, <TermQualifier>, <TerminationCauseText>
<TerminationQualifier> | Unsigned Integer, range 0 – 255 |
0If <TerminationQualifier> is equal to 0, the Proactive Command has been successfully finished.
>0 | If <TerminationQualifier> is not equal to 0 the Proactive Command |
| did not perform sucessfully. |
<TerminationCauseText>
•If <TermQualifier> is not equal to 0 the Proactive Command did not perform sucessfully:
If <TerminationCauseText> is not an empty string, this text has to be shown to the user for an appropriate time, e.g. 2 seconds. The text contains information regarding the termination cause, e.g. in case of a failed dialling process call barring through Call Control by SIM mechanism may be indicated.
If <TerminationCauseText> is an empty string, the TA shall give an own indication to the user.
•If <TermQualifier> is equal to 0, the Proactive Command has been successfully finished:
If <TerminationCauseText> is not an empty string, this text shall be shown to the user for an appropriate time.
OK
MC35_SAT_01_v02.00 | Page 40 of 65 | 11.01.2002 |
