BGS2T AT Command Set
7.22 AT^SLCC
BGS2T_ATC_V01.301 Page 165 of 554 1/31/12
c
Alphanumeric representation of <number> corresponding to the entry found in phonebook (see for example
AT+CPBW, parameter <text>).
Due to time constraints on the necessary evaluation of the phonebook, this parameter may show a default value
during early call phases (e.g. for <stat>= "dialing", "incoming" or "alerting"), even if a phonebook entry is pres-
ent for the number concerned.
Notes
• Teleservices other than voice, data, fax are not fully supported by BGS2T. They are used only in connection
with the handling for AT+CSNS, and may therefore occur in parameter <mode> for mobile terminated calls.
• If a URC "^SLCC" in verbose mode (see AT^SCFG) has been buffered while the interface was in dedicated
mode (depending on the settings of AT+CMER parameter <bfr>), each buffered event indicator will be output
as a separate URC after the interface returns to idle mode.
However, the output will deliver the list of current calls in the "current" state (at the time when the output is
generated), possibly leading to multiple displays of identical list configurations.
• Some parameters of the AT+CHLD command, as well as some situations where the call status in the network
changes very quickly (e.g. the transition between <stat>= "unknown", "dialing" and "alerting" for a call to a
reachable subscriber within the registered network) may lead to quasi-simultaneous changes to the states of
one or several calls in the list, possibly leading to multiple displays of identical list configurations.
• If multiple displays of identical list configurations occur, this happens because of intermediate states of the
list, that have already been overridden by new transitions and states. Thus, it is guaranteed that the configu-
ration displayed in such cases is the current configuration at the time of the last display.
• It is adviseable to receive URC "^SLCC" on an interface that is not used for call initiation, if verbose output is
configured. If only voice calls are expected, a setting of AT^SM20= 0 may be used alternatively in order to
keep the call from blocking the interface.
Examples
EXAMPLE 1
<alpha>
(str)(+CSCS)
^SYSSTART
at+cpin=9999
OK
+CREG: 2
+CREG: 1,"0145","0016"
We are now registered.
at^sm20=0
Command ATD for an outgoing voice call will termi-
nate immediately with response "OK".
OK
atd"1234567";
We start a voice call.
OK
"OK" response is issued immediately because of set-
ting AT^SM20="0".
^SLCC: 1,0,2,0,0,0,"1234567",129,"Called
Party"
MO voice call starts, paging B-party.
^SLCC:
End of current list
^SLCC: 1,0,2,0,0,1,"1234567",129,"Called
Party"
Traffic channel established,
network may now transmit network announcements,
ME may now transmit DTMF tones.
^SLCC:
End of current list
^SLCC: 1,0,3,0,0,1,"1234567",129,"Called
Party"
Call is now ringing at B-Party.
^SLCC:
End of current list
^SLCC: 1,0,0,0,0,1,"1234567",129,"Called
Party"
B-Party has accepted the call, connection estab-
lished.
To Next Page
Loading...
Need help?
General
