AC75 AT Command Set
15.1 AT^SRSA s
AC75_ATC_V01.002 Page 421 of 569 10/30/06
Confidential / Released
SAP connection state
0 No SAP connection established.
1 SAP connection ongoing, i.e. peers exchange messages.
SAP link change cause
0 Link changed, no diagnostic given.
10 Error, server unable to connect.
11 Error, server does not support maximum message size.
12 Error, maximum message size sent by client too small.
13 Error, client's network deregistration refused due to ongoing network activity.
20 Error, card not accessible.
21 Error, card removed.
22 Error, wrong ATR. Please refer to AT^SATR.
23 Error, data not available.
24 Error, not supported.
25 Error, no reason.
30 Error, server response timeout.
Causes 10 to 30 are present for SAP client only.
Notes
• If AT^SRSA with <dataForm> set to 1 (SAP) is given on the same serial multiplex channel as specified with
parameter <muxChan> the SAP data transfer mode is entered immediately. Therefore no command response
is issued by the AC75 in this case.
• If a AC75 acting as SAP client switches to a remote SIM card, it needs to load data from the SIM card first.
The duration of the initial data load varies depending on the SIM card. Users should be aware that during this
time SIM related AT commands (e.g. Phonebook or SMS commands) cannot be used. Therefore, it is recom-
mended to activate the "^SSIM READY" which indicates when the SIM card is accessible. See AT^SSET for
detail.
• If the AC75 is acting as SAP server and has released its SIM to a client it considers it as not accessible. There-
fore AT commands which require SIM access will be rejected with "+CME ERROR: SIM not inserted".
• Parameters <muxChan>, <dataForm> and <beaconPer> are applicable for RSA activation only.
• It is possible to use RSA with Java. In this case multiplexer is not used. Please refer to Java User's Guide [3]
for details.
<connState>(num)
<linkChangeCause>(num)