> 7.3 | ATD Mobile originated call to specified number

> Syntax

> Exec Command ATD<n>[<mgsm>][;]
> Response(s)
> If no dialtone (parameter setting ATX2 or ATX4):
> NO DIALTONE
> If busy (parameter setting ATX3 or ATX4):
> BUSY
> If a connection cannot be set up:
> NO CARRIER
> OK
> If successfully connected and non-voice call (TA switches to online data mode):
> CONNECT <text>
> When TA returns to command mode after call release:
> OK
> If successfully connected and voice call:
> OK

> Reference(s) |  | PIN |  | ASC0 | ASC1 | USB | MUX1 | MUX2 | MUX3 |  |  | Charge | Q | Last
> V.250 |  | ± |  | + | ± | + | + | ± | ± |  |  | - | - | -

> Command Description
> This command can be used to set up outgoing voice, data or fax calls. It also serves to control Supplementary Services. The termination character ";" is mandatory to set up voice calls or to send *# codes for Supplementary Services. It must not be used for data and fax calls.
> Additional notes on the responses returned after dialing with ATD:

> • | For voice calls, you have the choice of two different response modes that can be selected with AT^SM20: AT^SM20=1 (factory default) causes the ME to respond once the call setup is completed either successfully ("OK") or unsuccessfully ("NO CARRIER", "NO DIAL TONE", "BUSY"). AT^SM20=0 causes the ME to return "OK" immediately after dialing was completed (i.e. before call setup terminates successfully or unsuccessfully).

> • | For data connections, call setup always terminates when the call has been established (indicated by the result code "CONNECT <text>), or when it fails (indicated by "NO CARRIER"). The settings of AT^SM20 do not apply.

> Different call release indications:

> • | Upon termination, an outgoing fax or data call may show a different result code than a voice call would show under identical conditions. In order to track down the actual reason for call termination, AT+CEER or ATS18 should be used for all applicable connections.

> Using ATD during an active call:

> • | When a user originates a second voice call while there is already an active voice call, the first call will 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).

> Parameter Description

> <n>(text)

> String of dialing digits and optional V.250 modifiers: 0-9, *, #, +, A, B, C
> The following V.250 modifiers are ignored: ,(comma), T, P, !, W ,@

> <mgsm>(str)

> String of GSM modifiers:
> I Activates CLIR (disables presentation of own phone number to called party)
> i Deactivates CLIR (enables presentation of own phone number to called party)
> G Activate Closed User Group explicit invocation for this call only.
> g Deactivate Closed User Group explicit invocation for this call only.
> Notes

> • | The command may be aborted generally when receiving a character during execution. It cannot be aborted in some connection setup states, such as handshaking.

> • | Parameter "I" and "i" only if no *#-code is within the dial string.

> • | <mgsm> is not supported for data calls.

> • | <n> is default for last number that can be dialled by ATDL.

> • | See also ATX for <text>.

> • | If ATD is used with a USSD command (e.g. ATD*100#;) an AT+CUSD=1 is executed implicitly (see AT+CUSD).

> • | Parameter 'G' or 'g' will be ignored if Closed User Group was already activated, respectively deactivated with AT+CCUG command before. 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.

> • | The ME is equipped with a "Blacklist" function according to GSM02.07 Annex A: After a predefined number of failed call attempts, the dialed number is entered into a read-only phonebook called "blacklist" (phonebook "BL"). Call attempts to numbers contained in the blacklist will be barred by ME and not signalled to the network. An attempt to start a voice call to a barred phone number will be stopped with a CME ERROR 257 "Call Barred". An attempt to start a data or fax call to a barred phone number will be answered immediately with result code "NO CARRIER". The barred numbers are automatically removed from the blacklist according to the timing conditions specified in GSM02.07 Annex A.

> • | Emergency calls: If no SIM is inserted, call numbers 000, 08, 110, 112, 118,119, 911 and 999 cause an emergency call setup. If a SIM with ECC file is inserted, 112 and 911 and all additional call numbers stored in the ECC file cause an emergency call setup. If a SIM without ECC file is inserted, call numbers 112 and 911 and in addition all call numbers specified with AT^SCFG, "Call/ECC", parameter <ecc> will cause an emergency call setup.

> • | To start ATD via TC65's DTR line AT^SCFG may be used, refer parameter <AutoExecATC>.

> • | When using the command on the second serial interface please see also Section 1.9.

> Example
> The following example shows the call setup procedure when a call is already active and a second call attempt fails because the line of the called party is busy:

> atd03012345678 | Dialing out the first party's number.
> OK | The first call is established.
> ATD03022222222 | The number of the second party is dialed.
> OK | The response "OK" is issued immediately though no call is established (same behavior as is you had chosen AT^SM20=0.)
> BUSY | Line of the second called party is busy.