Specifications

TC35i AT Command Set
Confidential / Released
TC35i_ATC_V01.05 Page 21 of 278 04.08.2003
executed implicitly (see AT+CUSD, pg. 151).
· Parameter ‘G’ or ‘g’ will be ignored if Closed User Group was already activated,
or accordingly, deactivated with AT+CCUG command. Call by call invocation of
CUG uses the settings provisioned by the provider or, if available, the settings
of the parameters <index> and <info> made with AT+CCUG. See also Chapter
4.8.
· See ATX command in Chapter 2.31 for setting result code and call monitoring
parameters. Refer to Chapter 8.1.4 for <text>.
Blacklist management:
· The ME provides a blacklist function according to GSM02.07 Annex A. After a
predefined number of failed call attempts to the same number, the dialed num-
ber is entered into a read-only phonebook called “blacklist” (phonebook “BL”).
Call attempts to numbers contained in the blacklist will be barred by the ME and
not signaled to the network. An attempt to start a voice call to a barred phone
number will be stopped with CME ERROR 257 “Call barred”. An attempt to start
a data or fax call to a barred phone number will be answered immediately with
the result code “NO CARRIER”.
· The barred numbers are automatically removed from the blacklist according to
the timing conditions specified in GSM02.07 Annex A.
Different call release indications
· Upon termination, an outgoing fax or data call may show a different result code
than a voice call would deliver under identical conditions. In order to track down
the actual reason for call release, ATS18 (see Chapter 2.28) or AT+CEER (see
chapter 4.10) should be used.
Different response modes
· For voice calls two different response modes can be determined: TA returns
“OK” either after dialing was completed or after the call has been established.
The setting is made with AT^SM20 (see Chapter 7.17 for more details).
Factory default is AT^SM20=1. This causes the ME to return “OK” in case of
successful connection, otherwise one of the call release indications “NO CAR-
RIER”, “NO DIAL TONE”, “NO CARRIER” will follow.
· Data calls: In data connections, call setup always terminates when the call has
been established (indicated by result code “CONNECT<text>”) or when it fails
(indicated by “NO CARRIER”).
Using ATD during an active voice call:
· When a user originates a second voice call while there is already an active
voice call, the first call will be automatically put on hold.
· The second call attempt is acknowledged with “OK” immediately after dialing
with ATD has completed, without relation to a successful call setup. In case of
failure, the additional result codes “NO CARRIER”, “NO DIAL TONE”, “NO
CARRIER” will be presented afterwards (see example below).
This behavior is similar to the mode set with AT^SM20=0, but occurs also if
AT^SM20=1 and cannot be changed. To avoid different behavior in all proce-
dures of voice call setup simply give priority to AT^SM20=0 (“OK” appears al-
ways immediately after dialing).
· The current states of all calls can be easily checked at any time by using the
AT+CLCC command. For details refer to Chapter 4.20.
Example
The following example shows the call setup procedure when a call is already ac-
tive and a second call attempt fails because the line of the called party is busy:
atd0301234567; Dialing out the first party’s number.
OK The first call is established.