> 2.14 | AT^SCFG Extended Configuration Settings

> AT^SCFG can be used to query and configure various settings of the TC65.
> The AT^SCFG read command returns a list of all supported parameters and their current values.
> The AT^SCFG write command queries a configuration parameter (if no value is entered) or sets its value(s).
> Input of parameter names is always coded in GSM character set, parameter values are expected to be given as specified via AT+CSCS.
> The following error messages may be returned by the AT^SCFG write commands:

> • | "+CME ERROR: operation temporary not allowed" Change of parameter value(s) temporarily not allowed.

> • | "+CME ERROR: invalid index" Invalid parameter name or value(s).

> • | "+CME ERROR: invalid characters in text string" Character set conversion of parameter value(s) failed.

> • | "+CME ERROR: incorrect password" A given password was not correct.

> • | "+CME ERROR: memory failure" Could not allocate necessary memory or storing a parameter failed.

> • | "+CME ERROR: operation not allowed" Change of parameter value(s) not allowed

> • | "+CME ERROR: unknown" Other error

> Syntax

> Test Command AT^SCFG=?
> Response(s)
> ^SCFG: "AutoExec" , (list of supported <AutoExecCmd>), (list of supported <AutoExecType>), (list of supported <AutoExecIndex>), (list of supported <AutoExecMode>), (max. string length of <AutoExecATC>), (time range of <AutoExecPeriod>)
> ^SCFG: "Call/ECC", (list of supported <ecc>s)
> ^SCFG: "GPRS/ATS0/withAttach", (list of supported <gs0aa>s)
> ^SCFG: "GPRS/AutoAttach", (list of supported <gaa>s)
> ^SCFG: "GPRS/PersistentContexts", (list of supported <gpc>s)
> ^SCFG: "GPRS/RingOnIncomingData", (list of supported <groid>s)
> ^SCFG: "MEopMode/Airplane", (list of supported <map>s)
> ^SCFG: "MEopMode/Airplane/OnStart", (list of supported <mapos>s)
> ^SCFG: "MEShutdown/OnIgnition", (list of supported <msi>s)
> ^SCFG: "PowerSaver/Mode9/Timeout", (list of supported <psm9to>s)
> ^SCFG: "Radio/Band", (list of supported <rbp>s), (list of supported <rba>s)
> ^SCFG: "Radio/CNS", (list of supported <cns>s)
> ^SCFG: "Radio/FirstScan", (list of supported <firstscan>s)
> ^SCFG: "Radio/OutputPowerReduction", (list of supported <ropr>s)
> ^SCFG: "Serial/USB/DDD" , (list of supported <deviceDescr>s) , (list of supported <descrIndex>s) , (max. string length of <langId>) , (max. string length of <vendorId>) , (max. string length of <productId>) , (max. string length of <manufacturer>) , (max. string length of <product>) , (max. string length of <serialNo>)
> ^SCFG: "Tcp/BufSize", (list of supported <tcpBufSize>)
> ^SCFG: "Tcp/IRT", (list of supported <tcpIrt>)
> ^SCFG: "Tcp/MR", (list of supported <tcpMr>)
> ^SCFG: "Tcp/OT", (list of supported <tcpOt>)
> ^SCFG: "Tcp/SAck", (list of supported <tcpSack>)
> ^SCFG: "Tcp/TTcp", (list of supported <tcpTtcp>)
> ^SCFG: "Tcp/WithURCs", (list of supported <tcpWithUrc>)
> ^SCFG: "Trace/Syslog/OTAP", (list of supported <otapTracer>)
> ^SCFG: "URC/CallStatus/CIEV", (list of supported <succ>s)
> ^SCFG: "URC/CallStatus/SLCC", (list of supported <sucs>s)
> ^SCFG: "URC/Datamode/Ringline", (list of supported <udri>s)
> ^SCFG: "URC/Ringline", (list of supported <uri>s)
> ^SCFG: "URC/Ringline/ActiveTime", (list of supported <urat>s)
> ^SCFG: "Userware/Autostart", (list of supported <ua>s)
> ^SCFG: "Userware/Autostart/AppName", (max. string lengths of <uaa>)
> ^SCFG: "Userware/Autostart/Delay", (list of supported <uad>s)
> ^SCFG: "Userware/Passwd", (max. string length of <upwd>)
> ^SCFG: "Userware/DebugInterface", (<udbgif1>), (<udbgif2>), (<udbgif3>)
> ^SCFG: "Userware/Mode", (list of supported <umode>), (length of <uurl>), (range of supported <uport>values)
> ^SCFG: "Userware/Stdout", (list of supported <if>), (list of supported <intvalue>), (<filename>), (list of supported <logmode>)
> ^SCFG: "Userware/Watchdog", (list of supported <wd>)
> OK

> Read Command AT^SCFG?
> Response(s)
> ^SCFG: "AutoExec" , <AutoExecCmd>, <AutoExecType>, <AutoExecIndex>, <AutoExecMode>, <AutoExecATC>[, <AutoExecPeriod>, <AutoExecPeriodTimeLeft>]
> ^SCFG: "CALL/ECC", <ecc>
> ^SCFG: "GPRS/ATS0/withAttach", <gs0aa>
> ^SCFG: "GPRS/AutoAttach", <gaa>
> ^SCFG: "GPRS/PersistentContexts", <gpc>
> ^SCFG: "GPRS/RingOnIncomingData", <groid>
> ^SCFG: "MEopMode/Airplane", <map>
> ^SCFG: "MEopMode/Airplane/OnStart", <mapos>
> ^SCFG: "MEShutdown/OnIgnition", <msi>
> ^SCFG: "PowerSaver/Mode9/Timeout", <psm9to>
> ^SCFG: "Radio/Band", <rbc>, <rba>
> ^SCFG: "Radio/CNS", <cns>
> ^SCFG: "Radio/FirstScan", <firstscan>
> ^SCFG: "Radio/OutputPowerReduction", <ropr>
> ^SCFG: "Serial/USB/DDD" , <deviceDescr>, <descrIndex>, <langId>, <vendorId>, <productId>, <manufacturer>, <product>, <serialNo>
> ^SCFG: "Tcp/BufSize", <tcpBufSize>
> ^SCFG: "Tcp/IRT", <tcpIrt>
> ^SCFG: "Tcp/MR", <tcpMr>
> ^SCFG: "Tcp/OT", <tcpOt>
> ^SCFG: "Tcp/SAck", <tcpSack>
> ^SCFG: "Tcp/TTcp", <tcpTtcp>
> ^SCFG: "Tcp/WithURCs", <tcpWithUrc>
> ^SCFG: "Trace/Syslog/OTAP", <otapTracer>
> ^SCFG: "URC/CallStatus/CIEV", <succ>
> ^SCFG: "URC/CallStatus/SLCC", <sucs>
> ^SCFG: "URC/Datamode/Ringline", <udri>
> ^SCFG: "URC/Ringline", <uri>
> ^SCFG: "URC/Ringline/ActiveTime", <urat>
> ^SCFG: "Userware/Autostart", <ua>
> ^SCFG: "Userware/Autostart/AppName", <uaa>
> ^SCFG: "Userware/Autostart/Delay", <uad>
> ^SCFG: "Userware/Passwd"
> ^SCFG: "Userware/DebugInterface", <udbgif1>, <udbgif2>, <udbgif3>
> ^SCFG: "Userware/Mode"
> ^SCFG: "Userware/Stdout", <if>[, <intvalue>[, <filename>[, <logmode>]]]
> ^SCFG: "Userware/Watchdog", <wd>
> OK

> Write Command Automatic AT command execution AT^SCFG="AutoExec" , <AutoExecCmd>, <AutoExecType>, <AutoExecIndex>[, <AutoExecMode>, <AutoExecATC>[, <AutoExecPeriod>]]
> Response(s)
> ^SCFG: "AutoExec" , <AutoExecCmd>, <AutoExecType>, <AutoExecIndex>, <AutoExecMode>, <AutoExecATC>[, <AutoExecPeriod>, <AutoExecPeriodTimeLeft>]
> OK
> ERROR
> +CME ERROR

> Write Command Query/Configure Emergency numbers for SIM without ECC field AT^SCFG="Call/ECC"[, <ecc>]
> Response(s)
> ^SCFG: "Call/ECC", <ecc>
> OK
> ERROR
> +CME ERROR

> Write Command GPRS ATS0 with automatic attach AT^SCFG="GPRS/ATS0/withAttach"[, <gs0aa>]
> Response(s)
> ^SCFG: "GPRS/ATS0/withAttach", <gs0aa>
> OK
> ERROR
> +CME ERROR

> Write Command Automatic GPRS attach AT^SCFG="GPRS/AutoAttach"[, <gaa>]
> Response(s)
> ^SCFG: "GPRS/AutoAttach", <gaa>
> OK
> ERROR
> +CME ERROR

> Write Command Persistent GPRS contexts AT^SCFG="GPRS/PersistentContexts"[, <gpc>]
> Response(s)
> ^SCFG: "GPRS/PersistentContexts", <gpc>
> OK
> ERROR
> +CME ERROR

> Write Command Ring on incoming GPRS IP data packets AT^SCFG="GPRS/RingOnIncomingData"[, <groid>]
> Response(s)
> ^SCFG: "GPRS/RingOnIncomingData", <groid>
> OK
> ERROR
> +CME ERROR

> Write Command Enable/disable Airplane mode during operation AT^SCFG="MEopMode/Airplane"[, <map>]
> Response(s)
> ^SCFG: "MEopMode/Airplane", <map>
> OK
> ERROR
> +CME ERROR

> Write Command Airplane mode upon ME restart AT^SCFG="MEopMode/Airplane/OnStart"[, <mapos>]
> Response(s)
> ^SCFG: "MEopMode/Airplane/OnStart", <mapos>
> OK
> ERROR
> +CME ERROR

> Write Command Enable/disable shutdown by ignition line AT^SCFG="MEShutdown/OnIgnition"[, <msi>]
> Response(s)
> ^SCFG: "MEShutdown/OnIgnition", <msi>
> OK
> ERROR
> +CME ERROR

> Write Command Query/Set timeout value for power saving mode 9 AT^SCFG="PowerSaver/Mode9/Timeout"[, <psm9to>]
> Response(s)
> ^SCFG: "PowerSaver/Mode9/Timeout", <psm9to>
> OK
> ERROR
> +CME ERROR

> Write Command Radio band selection AT^SCFG="Radio/Band"[, <rbp>][, <rba>]
> Response(s)
> ^SCFG: "Radio/Band", <rbp>, <rba>
> OK
> ERROR
> +CME ERROR

> Write Command Query/Enable/Disable Continuous Network Search AT^SCFG="Radio/CNS"[, <cns>]
> Response(s)
> ^SCFG: "Radio/CNS", <cns>
> OK
> ERROR
> +CME ERROR

> Write Command Query/Enable/Disable First Network Scan over all Radio Bands AT^SCFG="Radio/FirstScan"[, <firstscan>]
> Response(s)
> ^SCFG: "Radio/FirstScan", <firstscan>
> OK
> ERROR
> +CME ERROR

> Write Command Radio output power reduction AT^SCFG="Radio/OutputPowerReduction"[, <ropr>]
> Response(s)
> ^SCFG: "Radio/OutputPowerReduction", <ropr>
> OK
> ERROR
> +CME ERROR

> Write Command Configuration of TCP parameter 'BufSize': AT^SCFG="Tcp/BufSize"[, <tcpBufSize>]
> Response(s)
> ^SCFG: "Tcp/BufSize", <tcpBufSize>
> OK
> ERROR
> +CME ERROR

> Write Command Configuration of TCP parameter 'InitialRetransmissionTimeout': AT^SCFG="Tcp/IRT"[, <tcpIrt>]
> Response(s)
> ^SCFG: "Tcp/IRT", <tcpIrt>
> OK
> ERROR
> +CME ERROR

> Write Command Configuration of TCP parameter 'MaxRetransmissions': AT^SCFG="Tcp/MR"[, <tcpMr>]
> Response(s)
> ^SCFG: "Tcp/MR", <tcpMr>
> OK
> ERROR
> +CME ERROR

> Write Command Configuration of TCP parameter 'OverallTimeout': AT^SCFG="Tcp/OT"[, <tcpOt>]
> Response(s)
> ^SCFG: "Tcp/OT", <tcpOt>
> OK
> ERROR
> +CME ERROR

> Write Command Configuration of TCP parameter 'Selective Acknowledge': AT^SCFG="Tcp/SAck"[, <tcpSack>]
> Response(s)
> ^SCFG: "Tcp/SAck", <tcpSack>
> OK
> ERROR
> +CME ERROR

> Write Command Configuration of Internet Service URCs: AT^SCFG="Tcp/WithURCs"[, <tcpWithUrc>]
> Response(s)
> ^SCFG: "Tcp/WithURCs", <tcpWithUrc>
> OK
> ERROR
> +CME ERROR

> Write Command Tracing: AT^SCFG="Trace/Syslog/OTAP"[, <otapTracer>]
> Response(s)
> ^SCFG: "Trace/Syslog/OTAP", <otapTracer>
> SYSLOG ENABLED
> ERROR
> +CME ERROR

> Write Command USB Device Descriptor: AT^SCFG="Serial/USB/DDD" [, <deviceDescr>, [<descrIndex>], [<langId>], <vendorId>, <productId>, [<manufacturer>], [<product>], [<serialNo>]]
> Response(s)
> ^SCFG: "Serial/USB/DDD" , <deviceDescr>, <descrIndex>, <langId>, <vendorId>, <productId>, <manufacturer>, <product>, <serialNo>
> OK
> ERROR
> +CME ERROR

> Write Command Configuration of URC "+CIEV: call" Call Status Indication AT^SCFG="URC/CallStatus/CIEV"[, <succ>]
> Response(s)
> ^SCFG: "URC/CallStatus/CIEV", <succ>
> OK
> ERROR
> +CME ERROR

> Write Command Configuration of URC "^SLCC" Call Status Indication AT^SCFG="URC/CallStatus/SLCC"[, <sucs>]
> Response(s)
> ^SCFG: "URC/CallStatus/SLCC", <sucs>
> OK
> ERROR
> +CME ERROR

> Write Command URC indication in datamode via Ring line: AT^SCFG="URC/Datamode/Ringline"[, <udri>]
> Response(s)
> ^SCFG: "URC/Datamode/Ringline", <udri>
> OK
> ERROR
> +CME ERROR

> Write Command URC indication via Ring line: AT^SCFG="URC/Ringline"[, <uri>]
> Response(s)
> ^SCFG: "URC/Ringline", <uri>
> OK
> ERROR
> +CME ERROR

> Write Command Duration of active RING line for URC indications: AT^SCFG="URC/Ringline/ActiveTime"[, <urat>]
> Response(s)
> ^SCFG: "URC/Ringline/ActiveTime", <urat>
> OK
> ERROR
> +CME ERROR

> Write Command Userware autostart status: AT^SCFG="Userware/Autostart"[, <upwd>, <ua>]
> Response(s)
> ^SCFG: "Userware/Autostart"[, <ua>]
> OK
> ERROR
> +CME ERROR

> Write Command Userware autostart application: AT^SCFG="Userware/Autostart/AppName"[, <upwd>, <uaa>]
> Response(s)
> ^SCFG: "Userware/Autostart/AppName"[, <uaa>]
> OK
> ERROR
> +CME ERROR

> Write Command Userware autostart delay: AT^SCFG="Userware/Autostart/Delay"[, <upwd>, <uad>]
> Response(s)
> ^SCFG: "Userware/Autostart/Delay"[, <uad>]
> OK
> ERROR
> +CME ERROR

> Write Command Userware configuration password: AT^SCFG="Userware/Passwd"[, <upwd>old, <upwd>new, <upwd>new]
> Response(s)
> ^SCFG: "Userware/Passwd"
> OK
> ERROR
> +CME ERROR

> Write Command Userware debug interface: AT^SCFG="Userware/DebugInterface"[, <udbgif1>, <udbgif2>[, <udbgif3>]]
> Response(s)
> ^SCFG: "Userware/DebugInterface", <udbgif1>, <udbgif2>, <udbgif3>
> OK
> ERROR
> +CME ERROR

> Write Command Userware mode: AT^SCFG="Userware/Mode"[, <umode>, <uurl>, <uport>]
> Response(s)
> ^SCFG: "Userware/Mode", <umode>, <uurl>, <uport>
> OK
> ERROR
> +CME ERROR

> Write Command Standard output of userware: AT^SCFG="Userware/Stdout"[, <if>[, <intvalue>][, <filename>][, <logmode>]]
> Response(s)
> ^SCFG: "Stdout" , <if>[, <intvalue>[, <filename>[, <logmode>]]]
> OK
> ERROR
> +CME ERROR

> Write Command Watchdog configuration and control: AT^SCFG="Userware/Watchdog"[, <wd>]
> Response(s)
> ^SCFG: "Watchdog", <wd>
> OK
> ERROR
> +CME ERROR

> PIN |  | ASC0 | ASC1 | USB | MUX1 | MUX2 | MUX3 |  |  | Charge | Q | Last
> - |  | + | + | + | + | + | + |  |  | ± | ± | -

> Unsolicited Result Codes
> URC 1
> ^SCFG: "AutoExec", <AutoExecState>, <AutoExecType>, <AutoExecIndex>, <AutoExecMode>, <AutoExecATC>
> If the event specified with <AutoExecType> occurs and the related AT command line is executed this URC is issued.
> URC 2
> ^SYSSTART AIRPLANE MODE
> This URC is issued each time the Airplane mode is activated, no matter whether Airplane mode is set with parameter <map>="on" or <mapos>="on". The URC notifies the user that only the AT commands supported in Airplane mode are accessible. After leaving the Airplane mode the URC "^SYSSTART" indicates that the ME has returned to Normal mode and the full set of AT commands is accessible again.
> Parameter Description

> <AutoExecCmd>(str)(+CSCS)

> AutoExec Command
> This parameter serves to switch the Autoexec function on or off.
> If it is switched off (<AutoExecCmd>=0), parameters following <AutoExecIndex> are ignored and all settings at the given index are restored to their default values.
> Value will be saved while switching off the TC65 via AT commands (e.g. AT+CFUN or AT^SMSO) and restored on next power up.
> “0“
> Disable automatic execution of the AT command(s) specified with <AutoExecATC> at a given <AutoExecIndex>.
> “1“
> Enable automatic execution of the AT command(s) specified with <AutoExecATC> at a given <AutoExecIndex>. Not allowed for <AutoExecType>=0 (DTR line activation) while multiplex mode is active, refer to AT+CMUX.

> <AutoExecType>(str)(+CSCS)

> AutoExec Event Type
> This parameter selects the kind of event used to automatically launch the AT command(s) specified with <AutoExecATC>.
> Value will be saved while switching off the TC65 via AT commands (e.g. AT+CFUN or AT^SMSO) and restored on next power up.
> “0“
> Autoexec activity is driven by ASC0 DTR line activation (OFF-ON transition).
> “1“
> Autoexec activity is timer driven. To specify the time span use <AutoExecPeriod>.

> <AutoExecIndex>(str)(+CSCS)

> AutoExec Command Index
> This parameter specifiesthe command storage index. The following table shows the index ranges supported for each variant of <AutoExecType>.
> Value will be saved while switching off the TC65 via AT commands (e.g. AT+CFUN or AT^SMSO) and restored on next power up.

> <AutoExecType> value | <AutoExecType> event | Valid Indices
> 0 | Autoexec activity is driven by ASC0 DTR line activation | 0
> 1 | Autoexec activity is timer driven. | 0-2

> <AutoExecMode>(str)(+CSCS)

> AutoExec Command Mode
> 0...255
> This parameter specifies details regarding the behavior of the TC65 when the AT command starts to be executed.
> Value is interpreted as a bit field, unused bits are reserved for future use (RFU) and shall be set to 0.
> When a call is released by an Autoexec activity, no release indication may be issued on the first logical channel.
> Value will be saved while switching off the TC65 via AT commands (e.g. AT+CFUN or AT^SMSO) and restored on next power up.

> Bit | Mask hex | Mask dec | Control
> D 0 D1 | 0x00 0x01 0x02 0x03 | 0 1 2 3 | 00: Ignore ongoing calls 01: Wait until all calls have ended 10: Dismiss any ongoing call 11: RFU
> D 2 | 0x04 | 4 | 0: One shot action 1: Periodic action (for "AutoExec/Period" only)
> D 3 | 0x08 | 8 | RFU
> D 4 | 0x10 | 16 | RFU
> D 5 | 0x20 | 32 | RFU
> D 6 | 0x40 | 64 | RFU
> D 7 | 0x80 | 128 | RFU

> <AutoExecATC>(str)(+CSCS)

> AutoExec AT command String
> This parameter specifies the AT command(s) to be launched automatically. Each AT command is executed in the same way as if it were entered online, this means that command concatenation is possible if supported by the given commands. If serial multiplex mode is activated (AT+CMUX) the first logical channel is used, i.e. CSD calls (data or fax) could be set up. If the TC65 is busy on the serial channel command execution will be delayed until ongoing action is finished.
> The first two characters of the automatically launched AT command shall be "at".
> Please refer to examples below.
> Value will be saved while switching off the TC65 via AT commands (e.g. AT+CFUN or AT^SMSO) and restored on next power up.

> <AutoExecPeriod>(str)(+CSCS)

> AutoExec Command Period
> Parameter specifies the period after which <AutoExecATC> will be executed. Format is "hhh:mm:ss", where characters indicate hours, minutes and seconds. This parameter applies to <AutoExecType>=1 only.
> Value will be saved while switching off the TC65 via AT commands (e.g. AT+CFUN or AT^SMSO) and restored on next power up.
> When using this feature with running java applications, please consider the minimum time for the execution of AT+CFUN or AT^SMSO is 15 seconds.
> 000:00:05...240:00:00

> <AutoExecPeriodTimeLeft>(str)(+CSCS)

> AutoExec Command Period Left
> This parameter shows the amount of time left until <AutoExecATC> will be executed. Format is "hhh:mm:ss", where characters indicate hours, minutes and seconds. This parameter applies to <AutoExecType>=1 only.
> Due to the internal activity and network signaling an execution delay of several seconds may occur for the overall procedure.
> 000:00:00...240:00:00

> <AutoExecState>(str)(+CSCS)

> AutoExec Command Status
> This parameter is part of the Autoexec URC which is presented when a scheduled Autoexec activity is being performed.
> “1“
> The value 1 indicates that the Autoexec activity specified with <AutoExecATC> is currently executed.

> <ecc>(str)(+CSCS)

> Emergency call numbers on non-ECC SIM
> This parameter specifies emergency call numbers on SIM cards without ECC field. The parameter has no influence on the commonly used emergency numbers 112 and 911 which are always supported.
> Please refer also to Section 7.3, ATD where you can find a list of emergency call numbers supported if no SIM is inserted.
> The value range of <ecc> is "0"..."255". To select or deselect an emergency number calculate the sum of the values of all desired numbers and use the resulting value. For example, for "08" (2) and "118" (8) please enter the value (10).
> Parameter is global for the ME, non-volatile and will not be reset by AT&F.
> “ 0“
> No additional emergency numbers
> “ 1“
> 000
> “ 2“
> 08
> “ 4“
> 110
> “ 8“
> 118
> “16“
> 119
> “32“
> 999
> “64“
> Reserved
> “128“
> Reserved
> “255“(D)
> All additional emergency call numbers are supported.

> <gs0aa>(str)(+CSCS)

> GPRS ATS0 with Attach
> This parameter can be used to control the behaviour of ATS0.
> Parameter is global for all interfaces, volatile and will not be reset by AT&F.
> “on“(P)
> When the ATS0=<n> (<n>>0) command is received, the MT will attempt to perform a GPRS attach.
> “off“
> When the ATS0=<n> (<n>>0) command is received, the MT will not attempt to perform a GPRS attach.

> <gaa>(str)(+CSCS)

> GPRS with AutoAttach
> This parameter can be used to control whether the ME will perform a GPRS attach immediately after power-up and registering to the network or not. If the setting is changed to "enabled" and the ME is not attached yet, it will not initiate an attach immediately but after the next power-up and registration to the network.
> Parameter is global for all interfaces, non volatile and will not be reset by AT&F.
> “disabled“(D)
> GPRS auto attach is disabled
> “enabled“
> GPRS auto attach is enabled

> <gpc>(str)(+CSCS)

> GPRS with persistent contexts
> This parameter can be used to control whether the ME will store the GPRS context information defined by the AT+CGDCONT volatile or non volatile.
> Parameter is global for all interfaces, non volatile and will not be reset by AT&F.
> “0“(D)
> GPRS context definitions are volatile.
> “1“
> GPRS context definitions are non-volatile and will not be reset by AT&F.

> <groid>(str)(+CSCS)

> Ring on incoming GPRS IP data packets
> This parameter can be used to control the behaviour of the RING line for incoming IP packets in GPRS online mode.
> Parameter is local for the interface, volatile and will not be reset by AT&F.
> “on“
> If the ME is in power saving mode 7 or 9 (see AT+CFUN) and hardware flow control is in use (AT\Q3) and the RTS line is inactive and there are incoming IP packets for a GPRS context which is online, then the RING line will be activated once, for a time which is configured by the parameter "URC/Ringline/ActiveTime" (<urat>). The RING line to be used can be configured with the parameter "URC/Ringline" (<uri>).
> “off“(P)
> RING line is not activated for incoming IP packets.

> <map>(str)(+CSCS)

> MEopMode/Airplane: Enable/disable Airplane mode during operation
> The two parameters <map> and <mapos> can be used to enable/disable the Airplane mode. Airplane mode shuts down the radio part of the ME (PA and receiver), causes the ME to log off from the GSM/GPRS network and disables all AT commands whose execution requires a radio connection. A list of AT commands supported during Airplane mode can be found in Section 23.4, Availability of AT Commands Depending on Operating Mode of ME. The benefit of Airplane mode is that, at locations where no RF emission is allowed (typically airplanes, hospitals etc.), the subscriber can continue using network-independent features rather than powering off the entire device (e.g. a PDA or smartphone).
> If the subscriber tries to use an AT command not available in Airplane mode the response "+CME ERROR: Unsupported AT command" is returned.
> Parameter <map> allows entering or leaving the Airplane mode any time during operation, eliminating the need to enter the SIM PIN again. It can be used no matter whether the parameter <mapos> is "on" or "off".
> Parameter <map> is global for all interfaces, volatile and will not be reset by AT&F.
> “on“
> Activates Airplane mode and shuts down the radio part of the ME. The URC "^SYSSTART AIRPLANE MODE" appears.
> “off“(P)
> Deactivates Airplane mode, wakes up the radio part of the ME and restores access to network-dependent AT commands. The URC "^SYSSTART" appears.

> <mapos>(str)(+CSCS)

> MEopMode/Airplane: Airplane mode upon ME restart
> There are two ways to enter Airplane mode upon restart: One is using AT^SCFG with <mapos> as described below.
> Another approach is configuring the ME to restart into Airplane mode at a scheduled time. In this case, use the AT+CALA command, set an alarm time and then switch the ME off. When the alarm time is reached the ME wakes up to Airplane mode, no matter whether <mapos> was set "on" or "off".
> Parameter <mapos> is global for all interfaces, non volatile and will not be reset by AT&F.
> “on“
> Causes the ME to enter the Airplane mode each time the ME is restarted or reset.
> After restart or reset, the URC "^SYSSTART AIRPLANE MODE" appears and parameter <map> is "on". The SIM PIN can be entered using the AT+CPIN command. This enables the ME to read data from the SIM and give access to SIM PIN dependent AT commands which are available in Airplane mode, such as phonebook commands or several SMS commands. To notify the user when SIM data are accessible it is recommended to activate the "^SSIM READY" URC and store its presentation mode to the user profile with AT&W.
> To return from Airplane mode to Normal mode set the parameter <map> to "off" as described above. If PIN authentication was already done, the ME will try now to register to the GSM network.
> “off“(P)
> Airplane mode will not be activated after ME restart or reset.

> <msi>(str)(+CSCS)

> MEShutdown/OnIgnition: Enable/disable shutdown by IGT line
> The parameter specifies two different switching modes of the ignition line IGT: The line may either be used only to switch on the ME, or to switch it on and off.
> Please note that the factory default is different depending on the product type.
> Designed as a ready-to-use solution the TC65 Terminal is delivered with <msi>="on". Changing the delivery default of the TC65 Terminal disables the switch-off function of its ON/OFF push button and its ONOFF line on the GPIO connector, and therefore, is not allowed.
> TC65 Modules are factory set to <msi>="off". It is only in the case of modules that the application manufacturer may decide to change the default setting. We recommend that great care be taken before changing the switch mode of IGT. It is of vital importance that the following conditions are met to ensure that IGT works properly as ON/OFF switch:
> Switch-on condition: If the ME is off the IGT line must be asserted for at least 400 ms and then released.
> Switch-off condition: If the ME is on the IGT line must be asserted for at least 1 s and then released. The switch-off routine is identical with the shutdown procedure initiated by the AT^SMSO command, i.e. the ME performs an orderly shutdown and issues the "^SHUTDOWN" URC.
> Before switching off the ME wait at least 2 seconds after startup.
> Furthermore, particular attention shall be given to the USB interface and the DTR signal: The USB interface and the DTR line shall either be decoupled from IGT to avoid unintentional shutdown of the ME, or require special precautions if you wish to restart the ME by plugging the USB cable or to toggle IGT from DTR. For further details please refer to [2] and [3].
> Parameter <msi> is global for all interfaces, non-volatile and will not be reset by AT&F.
> “on“
> Ignition line (IGT) can be used to switch on and off the ME.
> “off“
> Ignition line (IGT) can be used to switch on the ME.

> <psm9to>(str)(+CSCS)

> Power saving mode 9 timeout
> This parameter can be used to query or configure the wake up time for power saving mode 9 (see AT+CFUN with parameter <fun>=9).
> Parameter is global for the ME, volatile and will not be reset by AT&F.
> 5...20(P)...36000
> The granularity of the timeout value is 100ms (i.e. a value of 10 equal 1 second). The minimum timeout value that can be applied is 5, but accuracy is only guaranteed for timeout values greater than 20.

> <rba>(str)(+CSCS)

> Allowed radio band(s)
> The feature "Radio/Band" with its parameters <rba>, <rbp> and <rbc> can be used to set and query preferences for selecting frequency bands.
> The TC65 normally uses an automode algorithm designed to recognize automatically the radio bands of the current country, typically a combination of two bands. Commonly used dual-band combinations are, for example, 900/1800 MHz in European countries or 850/1900 MHz in North America. The standard radio band combination of a country depends on the ARFCNs (Absolute Frequency Channel Number) and the MCCs (Mobile Country Code) visible at the air interface. This enables the ME to easily find the standard band or band combination of a country every time after power-up and, thus, usually eliminates the need for the subscriber to make any changes. So, if automode is used and the allowed bands are not restricted with <rba> the response parameter <rbc> shows the standard band(s) of the current area.
> As an alternative, if any bands other than those automatically selected by the ME are needed, the automode can be influenced using the AT^SCFG command. This may be necessary, for example, when running tests of GSM applications, when access to specific radio bands shall be restricted or when the final product is not intended for operation in certain countries.
> Before changing the parameters <rba> or <rbp> ensure that no network activity occurs. The write command cannot be executed when making a call, or sending / receiving short messages.
> Execution of the write command causes the ME to deregister from and re-register to the network, no matter whether the selected <rbp> or <rba> setting really changes. Therefore, it is useful to have the URC "+CREG" enabled. Please note that <firstscan>=1 ("Radio/FirstScan" feature enabled) may override the settings selected <rba>. The status of the SIM PIN authentication remains unchanged, eliminating the need to enter the SIM PIN again after the change.
> The parameter <rba> is intended to restrict the allowed bands to less than four bands. By default, all four bands are allowed. Each band not contained in <rba> is generally disabled.
> All bands of <rbp> must be contained in the range set with <rba>. The response parameter <rbc> will never show a value outside the <rba> range. <rba> has precedence over <rbp> and <rbc>.
> The <rba> value to select resp. deselect radio bands can be either a single band value or a multiple band value as listed below. The multiple band values are calculated by adding up the appropriate single band values.
> Parameter <rba> is global for the ME, non-volatile and will not be reset by AT&F.
> “1“
> GSM 900 MHz
> “2“
> GSM 1800 MHz
> “4“
> GSM 1900 MHz
> “8“
> GSM 850 MHz
> “3“
> GSM 900 MHz + GSM 1800 MHz
> “5“
> GSM 900 MHz + GSM 1900 MHz
> “10“
> GSM 850 MHz + GSM 1800 MHz
> “12“
> GSM 850 MHz + GSM 1900 MHz

> <rbp>(str)(+CSCS)

> Preferred radio band(s)
> The write command will trigger the band selection, starting with the user preference specified by <rbp>. This means bands contained in <rbp> will be searched first, regardless of the standard band combination of the current country. The final result of the band selection can be read from <rbc>.
> If <rbp> was a band or band combination which differs from the standard band(s) and the requested band(s) are not visible at the air interface the ME reverts to the standard band(s) of this country. Please note that the band selection procedure is independent of the registration procedure, i.e. the ME selects a band no matter whether or not there is a PLMN (Public Land Mobile Network) the ME can register to. So, if the <rbp> was a band or band combination supported by the country, but currently no PLMN can be found, the ME will select the "preferred" band (indicated by <rbc>) without registering to the network. To avoid registration problems, for example when the settings are configured for testing the GSM application it is recommended that the tester first activates the desired band(s) on the test equipment and then executes the AT^SCFG write command. Besides remember that the network registration also depends on the settings made with AT+COPS.
> The <rbp> is volatile and cannot be read back with the AT^SCFG read command. This is because the value is used only for triggering one single search operation.
> The parameter <rbp> may be one of the single bands or one of the four dualband combinations listed below. All preferred bands must be contained in the range of allowed bands set with <rba>, invalid combinations are not accepted. To give priority to a certain single band or band combination and suppress all others simply select the same value both for <rbp> and <rba>.
> “1“
> GSM 900 MHz
> “2“
> GSM 1800 MHz
> “4“
> GSM 1900 MHz
> “8“
> GSM 850 MHz
> “3“
> GSM 900 MHz + GSM 1800 MHz
> “5“
> GSM 900 MHz + GSM 1900 MHz
> “10“
> GSM 850 MHz + GSM 1800 MHz
> “12“
> GSM 850 MHz + GSM 1900 MHz

> <rbc>(str)(+CSCS)

> Currently selected radio band(s)
> <rbc> is the single band or dual band combination currently used by the ME, found either by the automode algorithm or after the network search was triggered with <rbp>. The <rbc> value is saved on power down. When restarted next time the ME tries to select the same band(s) if these are visible. If the band(s) stored with <rbc> are not visible the ME uses the standard band(s) of the current country and consequently updates the <rbc> value.
> <rbc> is only a response parameter returned either after sending the read command AT^SCFG? or writing AT^SCFG="Radio/Band".
> In addition to <rbc> and to allow the subscriber to be notified whenever the selected band changes it is recommended to activate the "+CIEV: band" (see Section 3.3, AT^SIND).
> “1“
> GSM 900 MHz
> “2“
> GSM 1800 MHz
> “4“
> GSM 1900 MHz
> “8“
> GSM 850 MHz
> “3“
> GSM 900 MHz + GSM 1800 MHz
> “5“
> GSM 900 MHz + GSM 1900 MHz
> “10“
> GSM 850 MHz + GSM 1800 MHz
> “12“
> GSM 850 MHz + GSM 1900 MHz

> <cns>(str)(+CSCS)

> Continuous Network Search Mode
> This parameter can be used to influence the time the ME takes to register to the network.
> Parameter is global for the ME, volatile and will not be reset by AT&F.
> “0“(P)
> Normal
> When trying to register to a network the ME sleeps longer than in "Fast mode" before restarting a network scan.
> “1“
> Fast
> "Fast mode" reduces the time the ME sleeps before restarting a network scan when trying to register.
> Advantage: If the ME is out of network service it may take less time to find a network.
> Disadvantage: Higher current consumption while the ME is out of network service.
> Note: To monitor the search process it may be useful to have the "+CREG" URC enabled. Each time the network search starts, the URC "+CREG" equals "2" (searching). When the network search stops, the URC is issued again, indicating either "0" (not registered), or "1" (registered) or "5" (registered, roaming). As long as no network can be found, the URC will be toggling between "2" and "0".

> <firstscan>(str)(+CSCS)

> First Scan over all Radio Bands
> "Radio/FirstScan" is a specific band selection feature, designed only to initiate a one-time network search across all band combinations when the ME is forced to select a network the first time after reboot.
> The feature may be activated if the ME is expected to operate in a country using a band configuration other than the typical European or North American combinations. In most cases, the settings selected with "Radio/Band" parameter <rba> and <rbp> will do.
> Parameter is global for the ME, non-volatile and will not be reset by AT&F. Any change to this parameter takes effect after reboot.
> “0“(D)
> Disabled
> Band search follows the rules specified for the "Radio/Band" parameter <rba>. So the ME will try to register to a network within a band or band combination currently visible at the air interface. If no network can be found the ME will continue to search, but only within the same band combination.
> “1“
> Enabled
> Band search will start within the current band combination. If this band combination provides only Limited Service or no service at all, the ME starts to scan all other bands, i.e. it will try to find a band outside the currently visible standard band combination. This mechanism will override the band settings selected with <rba>.
> Bands outside the current band combination will be scanned only one time. If there is still no appropriate network, the ME will resume the network search in the first band combination.
> Conditions for using this mode:
> AT+COPS must be set to "Automatic mode" (AT+COPS=0).
> Whilst the "Radio/FirstScan" feature is active other band or network selection commands cannot be used, such as AT+COPS, AT^SNWS or the "Radio/Band" parameters <rba> and <rbp> of AT^SCFG.
> Note: To keep track of all changes you can activate the "band" indicator provided by AT^SIND which pops up when another band was selected. To track the network registration status you can activate the "+CREG" URC. The result of the band selection can be checked with <rbc>.

> <ropr>(str)(+CSCS)

> Radio Output Power Reduction
> According to 3GPP Rel99, output power reduction for multiple TX slots is a mandatory feature. The amount of power reduction is configurable up to 3.0dB for 2TX, 4.8dB for 3Tx to 6dB for 4TX. To optimize heat dissipation, power consumption and SAR values it is recommended to use full power reduction (value "3").
> Parameter is global for all interfaces, volatile and will not be reset by AT&F.
> “1“
> Medium Reduction at GMSK (0dB reduction for 1TX and 2TX, 1.8dB for 3TX and 3dB for 4TX)
> “2“
> Maximal Reduction at GMSK (0dB reduction for 1TX, 3dB for 2TX, 4.8dB for 3TX and 6dB for 4TX)
> “3“(P)
> Maximal Reduction at GMSK (0dB reduction for 1TX, 3dB for 2TX, 4.8dB for 3TX and 6dB for 4TX)

> <tcpBufSize>(str)(+CSCS)

> BufferSize
> This value defines the default size of the TCP receive queue in bytes. Higher values allow higher throughput but less number of parallel connections. The total throughput is limited by the GPRS/EDGE network resources and cannot exceed the theoretical maximum gross throughput of 230Kbit.
> Parameter is global for the ME and non-volatile. Use of default value is recommended. If changed the new value takes effect the next time you start an Internet service with AT^SISO.
> 3000...5200(&F)(D)...20000
> Size of TCP receive buffer in bytes.
> Possible number of parallel socket connections depending on buffer size:
> - 5200 bytes (default): max. 8 connections
> - 10000 bytes (medium): max. 4 connections
> - 20000 bytes (high): max. 2 connections

> <tcpIrt>(str)(+CSCS)

> Initial Retransmission Timeout (IRT)
> 1...3(&F)(D)...60
> This parameter determines the time (in seconds) the TCP/IP stack will wait before starting the first retransmission of packets during the initial connection establishment phase.
> The TCP protocol ensures the retransmission of packets several times at increasing intervals until some upper limit is reached.
> This mechanism prevents packet loss and serious congestion problems.
> Parameter is global for the ME and non-volatile. Use of default value is recommended. If changed the new value takes effect the next time you start an Internet service with AT^SISO.

> <tcpMr>(str)(+CSCS)

> Maximum Number of Retransmissions (MR)
> 1...10(&F)(D)...30
> This parameter determines the maximum number of times to retransmit TCP packets while the service is in connected state. If the service is still connecting (connection setup) another algorithm applies.
> The value set with <tcpMr> will be assumed as default for the <srvParmTag> "tcpMR" when a new service profile is created with AT^SISS. In each service profile, you can set another "tcpMR" value which has precedence over the global value set with AT^SCFG. Existing service profiles are not affected when you change the global value via AT^SCFG.
> Parameter is global for the ME and non-volatile. Use of default value is recommended.

> <tcpOt>(str)(+CSCS)

> Overall TCP Timer for outstanding connections (tcpOT)
> 1...6000(&F)(D)
> This parameter specifies the number of seconds to wait before closing a connection if TCP/IP packets are not acknowledged.
> Setting the maximum value is practically equivalent to deactivating the tcpOT mechanism because the maximum time would never be reached by the TCP/IP stack.
> The value set with <tcpOt> will be assumed as default for the <srvParmTag> "tcpOT" when a new service profile is created with AT^SISS. However, in each service profile, you can set another "tcpOT" value which has precedence over the global value set with AT^SCFG. Existing service profiles are not affected when you change the global value via AT^SCFG.
> Parameter is non-volatile. Use of default value is recommended.

> <tcpSack>(str)(+CSCS)

> Selective Acknowledge (SAck)
> This parameter concerns a set of TCP extensions to improve performance and to provide reliable operation. It defines new TCP options for scaled windows and timestamps, which are designed to provide compatible interworking with TCPs that do not implement the extensions.
> The set of TCP extensions to improve performance is described in RFC 1323. The value set with <tcpSack> enables or disables the set of TCP extensions.
> Parameter is global for the ME. Use of powerup value is recommended.
> “0“
> Disable set of TCP extensions.
> “1“(P)
> Enable set of TCP extensions.

> <tcpTtcp>(str)(+CSCS)

> Transaction/TCP (T/TCP)
> This parameter concerns T/TCP, an extension of TCP to provide a transaction-oriented service.
> T/TCP is described in RFC 1644. The value set with <tcpTtcp> enables or disables T/TCP.
> Parameter is global for the ME. Use of powerup value is recommended.
> “0“(P)
> Disable T/TCP extension.
> “1“
> Enable T/TCP extension.

> <tcpWithUrc>(str)(+CSCS)

> URC mode or polling mode for Internet service commands
> This parameter enables or disables the presentation of the following URCs related to Internet service commands: "^SISR" URC, "^SISW" URC and "^SIS" URC for parameter <urcCause>=0 (Internet service events).
> "^SIS" URCs with <urcCause>=1 or 2 used to indicate incoming Socket connections are always enabled.
> Parameter is global for the ME and non-volatile.
> “on“(&F)(D)
> Enable URCs related to Internet service commands.
> Throughout the Chapter "Internet Service AT Commands" the mode is also referred to as URC mode.
> “off“
> Disable URCs related to Internet service commands.
> This requires the host application to employ polling techniques when using the Internet service AT commands: The host application is responsible to retrieve all status information needed to control an Internet session. The method is referred to as polling mode.

> <otapTracer>(str)(+CSCS)

> OTAP tracer
> This parameter enables a trace output of the Java Over The Air procedure. The tracer is useful for obtaining additional information when setting up an OTAP scenario. The output is provided on the interface on which the command was entered. While the tracer is enabled the interface is used for trace output only, meaning that no AT commands can be entered. The tracer will be switched off only by a reset of the module, e.g. after a completed OTAP procedure.
> “1“
> Enable OTAP tracer.

> <deviceDescr>(str)(+CSCS)

> Device Descriptor
> This parameter determines whether to use the Siemens standard USB Device Descriptor configuration (default) or a Device Descriptor configuration customized by the application manufacturer.
> Parameter is global, stored non-volatile in ME and not reset by AT&F. Setting will be active after TC65 restart.
> “0“(D)
> Siemens standard USB Device Descriptor.
> If <deviceDescr>=0 is set all other parameters related to "Serial/USB/DDD" cannot be changed. For use in a Windows environment, the "usbmodem.inf" file delivered with TC65 shall be present.
> Note that whenever the TC65 firmware is updated over the USB interface the Siemens standard configuration must be present. Therefore, before starting a TC65 firmware download be sure that <deviceDescr>=0 is activated and, under Windows, the Siemens "usbmodem.inf" file can be found. Remember to restart the ME after reverting to <deviceDescr>=0 and before starting the firmware download.
> “1“
> Customer specific USB Device Descriptor.
> If <deviceDescr>=1 is set all other parameters related to "Serial/USB/DDD" can be changed.
> Customizing the USB Device Descriptor configuration requires a unique Vendor ID obtained from the USB Implementers Forum. For information please refer to http://www.usb.org.
> For use under Windows a customized INF file for the USB modem must be present. An easy way to create this file is copying the Siemens "usbmodem.inf" file and overwriting the equivalent values changed with AT^SCFG, usually at least the Vendor ID, Product ID and, optionally, the manufacturer string. This is because the strings given for the customized "Serial/USB/DDD" parameters must be identical with those contained in the INF file.

> <descrIndex>(str)(+CSCS)

> Descriptor Index
> As the TC65 shall be capable of holding 0 - 3 customized Device Desciptor configurations, the <descrIndex> allows to create and select different parameter sets consisting of the parameters listed below.
> Please note that TC65 Release 03.000 supports only one parameter set associated to value 0.
> Parameter is global, stored non-volatile in ME and not reset by AT&F. Setting will be active after TC65 restart.
> “0“(D)
> Index for the first descriptor definition.
> “1“
> Future use.
> “2“
> Future use.
> “3“
> Future use.

> <langId>(str)(+CSCS)

> Language ID
> Please refer to USB.ORG [30] to find the language IDs currently defined for USB devices. If parameter <langId> is not specified, the default value of the Siemens standard USB Device Descriptor configuration applies (US English).
> Parameter is global, stored non-volatile in ME and not reset by AT&F. Setting will be active after TC65 restart.
> Parameter length: maximum 4 characters.

> <vendorId>(str)(+CSCS)

> Vendor ID
> This parameter represents the Vendor ID obtained from the USB Implementers Forum. The Vendor ID will, together with the Product ID, be transmitted to the host during initialization. The given Vendor ID must be included in the INF file needed for Windows.
> Parameter is global, stored non-volatile in ME and not reset by AT&F. Setting will be active after TC65 restart.
> Parameter length: maximum 4 characters.

> <productId>(str)(+CSCS)

> Product ID
> Product ID (PID) defined by the application manufacturer to identify the USB device.
> The Product ID will, together with the Vendor ID, be transmitted to the host during initialization. The given Product ID must be included in the INF file needed for Windows.
> Parameter is global, stored non-volatile in ME and not reset by AT&F. Setting will be active after TC65 restart.
> Parameter length: maximum 4 characters.

> <manufacturer>(str)(+CSCS)

> Manufacturer name
> Optional manufacturer string defined by the application manufacturer. If specified with <manufacturer> the same string shall be included in the INF file needed for Windows.
> Parameter is global, stored non-volatile in ME and not reset by AT&F. Setting will be active after TC65 restart.
> Parameter length: maximum 63 characters.

> <product>(str)(+CSCS)

> Product string
> Optional product name defined by the application manufacturer. If specified with <product> it is recommended to include the same string into the INF file.
> Parameter is global, stored non-volatile in ME and not reset by AT&F. Setting will be active after TC65 restart.
> Parameter length: maximum 63 characters.

> <serialNo>(str)(+CSCS)

> Device's serial number
> Optional serial number. Empty string if not used, like in the case of the Siemens standard USB Device Descriptor configuration.
> A serial number has several advantages. For example, it enables the host to assign the same virtual COM port to same USB device even though the device is connected to another USB port. This eliminates the need for the host to load the driver again.
> Parameter is global, stored non-volatile in ME and not reset by AT&F. Setting will be active after TC65 restart. If parameter <serialNo> is not specified, the default value of Siemens standard USB Device Descriptor applies.
> Parameter length: maximum 63 characters.

> <succ>(str)(+CSCS)

> CIEV Call Status Indication
> This parameter can be used to control the behaviour of URC "+CIEV: call". See also AT+CIND, AT+CMER and Section 7.1, Call Status Information.
> Parameter is global for all interfaces and will not be reset by AT&F.
> “restricted“(P)
> URC "+CIEV: call" will be issued only when a Call Status transition ends in state "active" or "unknown" (see Section 7.1, Call Status Information) for a call in the list of active calls.
> “verbose“
> URC "+CIEV: call" will be issued when any state transition (including transitions beginning or ending in state "unknown") occurs in the list of active calls, or when a traffic channel is established.

> <sucs>(str)(+CSCS)

> SLCC Call Status Indication
> This parameter can be used to control the behaviour of URC "^SLCC". See also AT^SLCC and Section 7.1, Call Status Information.
> Parameter is global for all interfaces and will not be reset by AT&F.
> “restricted“
> URC "^SLCC" will be issued only when a Call Status transition ends in state "active" or "unknown" (see Section 7.1, Call Status Information) for a call in the list of active calls
> “verbose“(P)
> URC "^SLCC" will be issued when any state transition (including transitions beginning or ending in state "unknown") occurs in the list of active calls, or when a traffic channel is established.

> <uri>(str)(+CSCS)

> URC RING line
> This parameter can be used to control the behaviour of the RING line to indicate URCs (both for idle interfaces and, if configured by the parameter "URC/Datamode/Ringline", if link is reserved) and, if configured, the indicator for incoming IP packets (see parameter "GPRS/RingOnIncomingData" (<groid>).
> Parameter is local for the interface, volatile and will not be reset by AT&F.
> “off“
> URC is not indicated by RING.
> “local“(P)
> URC will be indicated by an activated RING line of the interface on which the URC appears
> “asc0“
> URC is indicated by an activated RING0 line.

> <udri>(str)(+CSCS)

> URC Datamode RING line
> This parameter specifies whether RING or BREAK is used for the signaling of URCs when the TA-TE link is reserved (e.g. during circuit-switched data calls, fax connections, in GPRS data mode or during the execution of an AT command).
> Parameter is global for all interfaces, volatile and will not be reset by AT&F.
> “off“(P)
> URC will be indicated by BREAK
> “on“
> URC is indicated by an active RING line for a time which is configured by the parameter "URC/Ringline/ActiveTime" (<urat>). The RING line which will be used, can be configured by the parameter "URC/Ringline" (<uri>).

> <urat>(str)(+CSCS)

> URC RING line Active Time
> This parameter can be used to control how long the RING line is activated to indicate URCs (both for idle interfaces and, if configured by the parameter "URC/Datamode/Ringline" (<udri>), if link is reserved) and, if configured by the parameter "GPRS/RingOnIncomingData", to indicate incoming GPRS IP data packets (<groid>).
> Parameter is global for all interfaces, volatile and will not be reset by AT&F.
> “0“
> RING line will be activated for a time between 4.6 and 9.2 ms.
> “1“
> RING line will be activated for about 100ms.
> “2“(P)
> RING line will be activated for about 1s.

> <ua>(str)(+CSCS)

> Userware Autostart
> Specifies if the userware is started automatically on power-up.
> If autostart is enabled, it is no longer possible to use the multiplexer (see AT+CMUX).
> If the Java application starts, all current calls will be terminated.
> The Userware/Autostart mechanism takes effect also in Airplane modeand CHARGE-ONLY-MODE.
> Parameter is global, stored non-volatile in ME and not reset by AT&F.
> “0“(D)
> Userware autostart disabled
> “1“
> Userware autostart enabled

> <uaa>(str)(+CSCS)

> Userware Autostart AppName
> Specifies the absolute path of the userware (the jar/jad file containing the desired application) to be started automatically on power-up. The local flash file system is identified by: "A:", directory separator is "/" (002Fh). The underline character "_" (005Fh) will not be supported.
> Parameter is global, stored non-volatile in ME and not reset by AT&F.
> Parameter length: maximum 100 characters.

> <uad>(str)(+CSCS)

> Userware Autostart Delay
> 0(D)...10000
> Specifies the delay time (in 100ms) when the userware is started automatically after power-up.
> Parameter is global, stored non-volatile in ME and not reset by AT&F.

> <upwd>(str)(+CSCS)

> Userware Password
> Password used to change values of userware parameters.
> Parameter is global, stored non-volatile in ME and not reset by AT&F.
> The maximum length of a given password is 8 characters. It is allowed to have an empty password (this is the value on delivery of the module).
> CAUTION: Be careful not to lose the password. There is no way to reset or recover a forgotten password or to obtain a new password from the manufacturer.

> <udbgif1>(str)(+CSCS)

> Userware Debug Interface Local IP address
> Local IP address of the module used by the userware debugger.
> Parameter is global, volatile and not reset by AT&F.

> <udbgif2>(str)(+CSCS)

> Userware Debug Interface Remote IP address
> IP address of the host running the userware debugger.
> Parameter is global, volatile and not reset by AT&F.

> <udbgif3>(str)(+CSCS)

> Default interface flag for IP connections
> Flag to select if the userware debug interface is the default interface for IP connections. Parameter is global, volatile and not reset by AT&F.
> [“0“]
> Debug interface is not the default.
> “1“
> Debug interface is default for IP connections.

> <umode>(str)(+CSCS)

> Userware Mode
> Parameter is global, volatile and not reset by AT&F.
> [“normal“]
> Userware is started by AT command or autostart option.
> “debug“
> Userware is started by debugger on host side.
> “test“
> Userware is loaded from test server.

> <uurl>(str)(+CSCS)

> Userware Mode: Location
> Use of parameter depends on selected userware mode.
> Parameter is global, volatile and not reset by AT&F.
> If <umode>= "normal": Parameter is ignored.
> If <umode>= "debug": File name of application stored on module. Maximum length: 126 characters.
> If <umode>= "test": URL of the test server. Maximum length: 126 characters.

> <uport>(str)(+CSCS)

> Userware Mode: Port
> Use of parameter depends on selected userware mode.
> Parameter is global, volatile and not reset by AT&F.
> 0...65535
> If <umode>= "normal": Parameter is ignored.
> If <umode>= "debug": Port number used by debugger.
> If <umode>= "test": Port number of the test server.

> <if>(str)(+CSCS)

> Interface for Java System.out
> This parameter specifies the interface to be used for the Java standard output System.out. The selected interface must be supported by the hardware.
> “ASC0“
> System.out is routed to the first serial interface.
> The interface is shared between Java CommConnection and System.out. The baud rate set for CommConnection applies also to System.out.
> The value is global, stored non-volatile in ME and is not reset by AT&F.
> “ASC1“(D)
> System.out is routed to the second serial interface.
> The interface is shared between Java CommConnection and System.out. The baud rate set for CommConnection applies also to System.out.
> The value is global, stored non-volatile in ME and is not reset by AT&F.
> “USB“
> System.out is routed to the Universal Serial Bus interface.
> “NULL“
> Discard data.
> The value is global, stored non-volatile in ME and is not reset by AT&F.
> “UDP“
> System.out is routed to a UDP socket. The parameter requires that the port number be given with <intvalue>.
> "UDP" is intended only for use with the Java IDE and will be set automatically each time you start the debugging emulator of the TC65 (on-device debugging). Closing the debugger causes the ME to reboot and automatically resets the <if> value last selected. This eliminates any need for manually setting "UDP" with AT^SCFG, and, besides, allows you to select another System.out target to be used when not debugging. Due to this, the value "UDP" is volatile unlike all other <if> values, and switching to "UDP" is not supported while Java is running.
> “FILE“
> System.out is written into a file. Requires additional parameters <intvalue>, <filename> and <logmode>. Because excessive writing to the ME's flash file system decreases the life time of the flash memory, we recommend using the "FILE" interface only during development phases.
> The value is global, stored non-volatile in ME and is not reset by AT&F.

> <intvalue>(str)(+CSCS)

> This parameter is required only if parameter <if> for the Java System.out is set to "UDP" or "FILE". Parameter is global, stored non-volatile in ME and not reset by AT&F.
> 1...65535
> If <if>= "UDP": UDP port number. It is recommended to use a number greater than 1023.
> If <if>= "FILE": Size of the log file in bytes, values less then 1024 are not supported.

> <filename>(str)(+CSCS)

> This parameter is required only if parameter <if> for the Java System.out is set to "FILE". It specifies the absolute path and the file name of the log. The local Flash File system is identified by: "A:", directory separator is "/" (002Fh).
> The underline character "_" (005Fh) is not supported.
> The log is split into two concatenated files, each using half of the entire log size set with parameter <intvalue>. Each file name consists of the name specified with parameter <filename> and the numeric extension "0" or "1" automatically appended, for example "a:/java/log.txt.0" for the first part of the log and "a:/java/log.txt.1" for the second part. When the first log file reaches half of the log size, the System.out is written to the second file. When the second file is used up, the ME starts to overwrite the first one.
> Parameter is global, stored non-volatile in ME and not reset by AT&F.
> Parameter length: maximum 125 characters.

> <logmode>(str)(+CSCS)

> This parameter is required only if parameter <if> for the Java System.out is set to "FILE". The parameter selects the mode of writing System.out data to file.
> Parameter is global, stored non-volatile in ME and not reset by AT&F.
> “buffered“(D)
> Uses a buffer and a timer and acts like a write cache.
> “secure“
> Writes all output data byte by byte to the file.

> <wd>(str)(+CSCS)

> Watchdog configuration and control
> This parameter is used to configure the watchdog behaviour.
> The use of the watchdog setting does not take care about network registration, file system operation and other ongoing actions (hard reset).
> Parameter is global for all interfaces, non volatile and will not be reset by AT&F.
> “0“(D)
> Watchdog "do nothing". The watchdog has no affect.
> “1“
> Watchdog "re-start". The watchdog reboot the system.
> “2“
> Watchdog "shutdown". The watchdog switch off the system.
> Notes

> • | Any changes to parameters of the Autoexec function will be saved and restored on next power-up only when the ME is switched off via AT commands (e.g. AT+CFUN or AT^SMSO).

> • | Please keep in mind, that each time the ME is restarted the timers of all autoexec actions configured with <AutoExecType>=1 and <AutoExecPeriod> will be reinitialized and restarted. As a result, an autoexec action configured at a time later then a scheduled automatic restart would never be executed.

> • | Be careful using <AutoExecType>=1 with small period values and shutdown or reset AT commands, since only little time remains to change these settings again after TC65 restart.

> • | If <AutoExecATC> uses AT commands containing secret data, this information may be retrieved with AT^SCFG?. For instance, this applies if using AT+CPIN.

> • | Parameters "GPRS/ATS0/withAttach" (<gs0aa>) and "GPRS/RingOnIncomingData" (<groid>) are available only for modules supporting GPRS.

> Examples

> EXAMPLE 1 | Usage of "AutoExec": Enable sending of a short message (SMS) on next DTR activation (OFF-ON transition). Sent SMS is assumed to be stored at first location of storage selected with AT+CPMS and AT^SSMSS, i.e. SMS may be sent either from SIM or ME storage. Also refer to AT+CMSS and AT+CMGW. Since SMS transmission and ongoing calls are possible at the same time there is no need to wait until all calls have ended (<AutoExecMode>=0).

> AT+CMGF=1 | Enable SMS text mode.
> OK
> AT+CNMI=1,1 | Enable "+CMTI:" URC to be indicated when a short message is received.
> OK
> AT+CMGD=1 | Delete first SMS location.
> OK
> AT+CMGW="01522400045",145 | Start writing a short message.
> >Test-SMS to be sent from storage! | Enter the text of the message. Finish with CTRL-Z.
> +CMGW: 1 | Confirms that message is stored to first location.
> OK
> AT^SCFG="AutoExec",1,0,0,0,"AT+CMSS=1" | Enable execution on next DTR activation.
> ^SCFG: "AutoExec","1","0","0","0","at+cmss=1"
> ^SCFG: "AutoExec","0","1","0","0","","000:00:00","000:00:00"
> ^SCFG: "AutoExec","0","1","1","0","","000:00:00","000:00:00"
> ^SCFG: "AutoExec","0","1","2","0","","000:00:00","000:00:00"
> OK

> If a DTR activation has occured the ME issues the URC "^SCFG: " followed by the response of the executed command; the message reference in this case:

> ^SCFG:"AutoExec",0,0,1,0,"AT+CMSS=1"
> OK | Confirms that AT+CMSS=1 has been issued.
> +CMSS: 16

> EXAMPLE 2 | Usage of "AutoExec": Configure TC65 to perform a reset every 10 hours. The execution of the reset command shall be deferred until after any calls have ended. For details regarding software controlled power down refer to AT+CFUN and AT^SMSO.

> AT^SCFG="AutoExec",1,1,2,5,"AT+CFUN=0,1","010:00:00"
> ...
> OK

> After ten hours:

> ^SCFG:"AutoExec",1,1,2,5,"AT+CFUN=0,1"
> OK | Confirms that AT+CFUN=0,1 has been issued.
> SYSSTART | TC65 has restarted. Remember that the "^SYSSTART" URC will not appear if autobauding is enabled.

> EXAMPLE 3 | Usage of "AutoExec": Switch off the ME after three minutes without restarting it. For details regarding software controlled power down refer to AT+CFUN and AT^SMSO. Please keep in mind that if the GSM alphabet is enabled special characters within the executed AT command shall be issued as escape sequences. A list of typical escape sequences can be found in Section 1.5.1, GSM alphabet tables and UCS2 character values. For example, the caret character "^" included in all Siemens defined AT commands shall be given as "\1B\14".

> AT^SCFG="AutoExec",1,1,0,0,"AT\1B\14SMSO","000:03:00"
> ^SCFG: "AutoExec","0","0","0","0",""
> ^SCFG: "AutoExec","1","1","0","0","ATSMSO","000:03:00","000:02:59" | Please note that the indication of the escape sequence in the write command response depends on the used program.
> ^SCFG: "AutoExec","0","1","1","0","","000:00:00","000:00:00"
> ^SCFG: "AutoExec","0","1","2","0","","000:00:00","000:00:00"
> OK

> After three minutes:

> ^SCFG:"AutoExec",0,1,1,0,"AT^SMSO"
> ^SMSO: MS OFF
> OK
> ^SHUTDOWN | Indicates that AT^SMSO was successfully executed. The ME enters the POWER DOWN mode.

> EXAMPLE 4 | Usage of "AutoExec": Deactivate a timer-driven Autoexec function configured at <AutoExecIndex> 2 (such as the periodic automatic reset or the automatic switch-off functions configured in the preceding examples):

> AT^SCFG="AutoExec",0,1,2
> ...
> OK

> EXAMPLE 5 | Usage of "URC/Ringline" and "URC/Datamode/Ringline":

> AT+CSCS="GSM" | Switch to GSM character set.
> OK
> AT^SCFG? | Query all parameters.
> ...
> ^SCFG:"URC/Datamode/Ringline","off" | While the TA-TE link is reserved URCs will be indicated by BREAK.
> ^SCFG:"URC/Ringline","local" | URCs on this interface will be indicated by Ring line associated to the interface (e.g. RING0 for ASC0).
> ...
> OK
> AT^SCFG="URC/Datamode/Ringline","on"
> ^SCFG:"URC/Datamode/Ringline","on" | While the TA-TE link is reserved URCs will be indicated by an activated "local" Ring line.
> OK
> AT^SCFG="URC/Ringline","asc0"
> ^SCFG:"URC/Ringline","asc0" | URCs on this interface will be indicated by an activated RING0 no matter whether or not the TA-TE link is reserved.
> OK
> AT^SCFG="URC/Datamode/Ringline","off"
> ^SCFG:"URC/Datamode/Ringline","off" | URCs on this interface will be indicated by an activated RING0 if the TA-TE link is not reserved and by BREAK if the TA-TE link is reserved.
> OK
> AT^SCFG="URC/Ringline" | Disable any Ring line indication for URCs on this interface.
> ^SCFG:"URC/Ringline","off"
> OK