28.04.2015 Views

TC63i AT Command Set

TC63i AT Command Set

TC63i AT Command Set

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>TC63i</strong> <strong>AT</strong> <strong>Command</strong> <strong>Set</strong><br />

<br />

3.4 <strong>AT</strong>+CEER<br />

ID<br />

Description<br />

129 supplementary services invoke problem (GSM 04.80 3.6.7)<br />

130 supplementary services result problem (GSM 04.80 3.6.7)<br />

131 supplementary services error problem (GSM 04.80 3.6.7)<br />

241 Proprietary cause for GPRS API<br />

243 Proprietary cause for PPP/IP-stack<br />

3.4.2 Proprietary L2 cause<br />

Number Description<br />

242 L2 decoding error<br />

243 L2 decoding error<br />

244 L2 decoding error<br />

245 L2 decoding error<br />

246 L2 decoding error<br />

247 L2 decoding error<br />

248 L2 decoding error<br />

249 no network response received, e.g. due to low signal quality<br />

250 L2 decoding error<br />

251 L2 decoding error<br />

252 L2 decoding error<br />

253 L2 decoding error<br />

3.4.3 GSM release cause for L3 Radio Resource (RR)<br />

Number Description<br />

0 normal event<br />

1 abnormal release, unspecified<br />

2 abnormal release, channel unacceptable<br />

3 abnormal release, timer expired<br />

4 abnormal release, no activity on the radio path<br />

5 pre-emptive release<br />

8 handover impossible, timing advance out of range<br />

9 channel mode unacceptable<br />

10 frequency not implemented<br />

65 call already cleared<br />

95 semantically incorrect message<br />

96 invalid mandatory information<br />

97 message type non-existent or not implemented<br />

98 message type not compatible with protocol state<br />

100 conditional information element error<br />

<strong>TC63i</strong>_<strong>AT</strong>C_V01.100 Page 94 of 547 11/10/08<br />

Confidential / Released

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!