15. SIM APPLICATION TOOLKIT
Values follow GSM 11.14 standard.
<answer> | Description |
|
|
0 | OK. |
| Performed as required. It corresponds to ‘00’ command |
| performed succesfully, described in the GSM standard |
1 | Failed. |
| User terminated session. It corresponds to ‘10’ Proactive |
| session terminated by the user, described in the GSM |
| standard |
|
|
2 | Failed. |
| User requests backwards move. It corresponds to ‘11’ |
| backward move in the proactive SIM session requested by |
| the user |
3 | Failed. |
| No response from user. It corresponds to ‘12’ no response |
| from user |
|
|
4 | Failed. |
| Screen is busy: the text could not be displayed |
6 | Failed. |
| User rejected call |
|
|
7 | Failed. |
| User cleared down call before connection or network |
| release. It corresponds to ‘23’ |
|
|
Unsolicited Result Codes:
*E2STKC: <ton>,<dial_string>,<SetUpRequirement>,<coding>, <text_length>,<alpha_id>
Values follow GSM 11.14 standard.
<ton> | Description |
|
|
Integer type | Field of 1 byte indicating the Type of Number, coded as |
| for EFAND. See GSM |
| values |
|
|
<dial_string> | Description |
|
|
String type | Phone number of format <ton> |
|
|
|
|
<coding> | Description |
|
|
0 | Text is coded in unpacked format, using the SMS default 7- |
| bit coded alphabet, as defined in GSM 03.38 with bit 8 set |
| to 0. It corresponds to data coding scheme of 8 bit |
1 | Text is coded in packed format, using the SMS default |
| coded alphabet, packed in |
| GSM 03.38. It corresponds to data coding scheme of 7 bit |
| GSM default alphabet |
|
|
229
LZT 123 7361 R1A
