Contents:
Welcome to
56K Information Access
Product
Features
Installation for All Operating Systems
Troubleshooting
Technical Reference >
Introduction to Syntax and
Procedures
Data Command Set
Result Codes
Glossary
Regulatory
Information
Limited
Warranty
|
Diagnostic Commands
#UD - Last Call Status
Report
#UD is an action command requesting reporting of
logged operation events. It does not take parameters and must be the last
command in the command line.
The modem logs aspects of their operation for each
call, and saves these results until cleared by one of the following
events:
- Power off
- Hard reset (e.g., negate DTR with &D3 set;
reset button)
- Soft reset = ATZ or AT&F
- ATD command issued
- ATA command issued
- Automatic answer (e.g., set register S0>0
and ring detected)
These results are NOT cleared by changing DTR,
V.24 circuit 108.2, if &D0, &D1 or &D2.
Data Call State Model
For purposes of this command, there are four data
call states, and associated status issues:
Call Setup - Calling DCE: get dial tone, generate dial
digits, detect call progress signals. - Answering
DCE: detect ringing, detect CallerID, etc.
Negotiation - V.25 calling tone/answer tone exchanges - V.8 or V.8bis call function negotiations - V-series modem carrier detection and training - Modem-to-modem protocols (e.g., V.42, V.42bis).
Data Transfer - Bit-error rates, for each direction - Rate renegotiation -
Retraining
Call Termination - protocol disconnect signals - carrier disconnect signals - loss of carrier -
excessive error rates
Command Syntax
In response to this command, the modem will report
one or more lines of information text as defined below. Information text
format conforms to V.250; each line is preceded by a <CR><LF> pair,
and terminated by <CR><LF>. (CR and LF characters may be changed by writing new
values to the contents of registers S3 and S4, respectively.)
The modem may generate a single line or multiple
lines, followed by a standard OK final result code. For example, if call
setup failed, only that result is useful. Each information text line is
formatted as follows, including one or more key=value pairs:
Syntax
#UD
Response
DIAG <token key=value [[key=value]
[key=value]]...>
Defined Values
DIAG
|
5 hexadecimal characters (44h, 49h, 41h, 47h, 20h)
|
<
|
Left angle bracket (less than sign) (3Ch) |
token
|
Unique 32-bit hexadecimal string 2A4D3263(32h,
4h1, 34h, 44h, 33h, 32h, 36h, 33h) |
space
|
space character (20h) |
Key
|
One- or two-digit hexadecimal number |
=
|
Equal sign (3Dh) |
value
|
Any string as defined below |
>
|
Right angle bracket (greater than sign)
(3Eh) |
Unless otherwise noted, all values are hexadecimal
numbers. Any numeric values from tables in ITU V.58 are converted to
hexadecimal. Multi-digit values are reported MSD first. Leading 0's may be
deleted.
Monitoring an active
connection
This command is intended for use after call
termination. However, codes are defined so that a modem can respond before
the first call is placed, and during a call for live monitoring purposes.
For example, key 60, call termination, has value 1 defined, indicating
that the call is still in progress.
There are at least two ways to do this. First, the
DTE could switch the modem to On-Line command state, issue the command,
capture the responses and then issue an ATO command. For smoother on-line
monitoring, in-band means defined in ITU V.80 are recommended if available
in the modem. If V.80 methods are used, each response line shall be a
separate extended in-band message.
Notes for Tables
- The modem may insert a delay (e.g., 10 ms)
between information text lines.
- The code tables include values for data and fax
calls. Some of the codes are applicable only to data calls (e.g., data
compression), some are applicable only to call origination (e.g., busy,
answering signal detection) and some are applicable only to the
answering modem (e.g., calling signal detection).
callCleared codes from
3.6.4/V.58-1994
callCleared: indicates that the DCE has gone on-hook and that the previously
existing network connection has been cleared. These value are hex, converted
from decimal in V.58.
Key
|
Value(s)
|
Definition
|
0 |
2 digits |
Diagnostic Command Specification revision
number, digit.digit |
1 |
Table 3-4 |
Call Setup Result code |
2 |
Table 3-5 |
Multi-media mode |
3 |
Table 3-6 |
DTE-DCE interface mode |
4 |
String |
V.8 CM octet string, same format as V.250,
in quotes |
5 |
String |
V.8 JM octet string, same format as V.250,
in quotes |
10 |
0-2F |
Received signal power level, in-dBm (0-43) |
11 |
0-1F |
Transmit signal poer level, in -dBm (e.g.,
0-17) |
12 |
0-64 |
Estimated noise level, in -dBm (e.g., 10-90) |
17 |
0-FFF |
Round Trip delay, in units of ms |
18 |
Table 3-7 |
V.34 INFO bit map |
20 |
Table 3-8 |
Transmit Carrier Negotiation Result |
21 |
Table 3-8 |
Receive Carrier Negotiation Result |
22 |
0-1F40 |
Transmit Carrier symbol rate (0-8000) in
symbol/s |
23 |
0-1F40 |
Receive Carrier symbol rate (0-8000) in
sybol/s |
24 |
0-FAO |
Transmit Carrier frequency (0-4000) in
Hz |
25 |
0-FAO |
Receive Carrier frequency (0-4000) in Hz |
26 |
0-FAOO |
Initial transmit carrier data rate (0-64000)
in bit/s |
27 |
0-FAOO |
Receive transmit carrier data rate (0-64000)
in bit/s |
30 |
0-FF |
Temporary carrier loss event count |
31 |
0-FF |
Carrier Rate re-negotiation even court |
32 |
0-FF |
Carrier Retrains requested |
33 |
0-FF |
Carrier Retrain requests granted |
34 |
0-FAOO |
Final transmit carrier data rate in bit/s |
35 |
0-FAOO |
Final receive carrier data rate in bit/s |
40 |
Table 3-9 |
Protocol Negotiation Result |
41 |
0-400 |
Error Control frame size in bytes |
42 |
0-FF |
Error control link timeouts in transmission |
43 |
0-FF |
Error control link NAKs received |
44 |
Table 3-10 |
Compression Negotiation Result |
50 |
0-2 |
Transmit flow control: 0 = off; 1 = DC1/DC3;
2 = V.24 circuit 106/133 |
51 |
0-2 |
Receive flow control: 0 = off; 1 = DC1/DC3;
2 = V.24 circuit 106/133 |
52 |
0-FFFFFFFF |
Transmit characters sent from DTE |
53 |
0-FFFFFFFF |
Received characters sent to DTE |
54 |
0-FFFF |
Transmit characters lost (data overrun
errors from DTE) |
55 |
0-FFFF |
Received characters lost (data overrun
errors to DTE) |
56 |
0-FFFFFFFF |
Transmit I-Frame count, if error control
protocol running |
57 |
0-FFFFFFFF |
Received I-Frame count, if error control
protocol running |
58 |
0-FFFF |
Transmit I-Frame error count, if error
control protocol running |
59 |
0-FFFF |
Received I-Frame error count, if error
control protocol running |
60 |
Table 3-11 |
Termination Cause |
61 |
O-FF |
Call Waiting event count |
Code |
Definition |
0 |
No previous call (modem log has
been cleared since any previous calls) |
1 |
No dial tone detected |
2 |
Reorder signal detected, network
busy |
3 |
Busy signal detected |
4 |
No recognized signal detected
(e.g., no signal, or nothing recognizable) |
5 |
Voice detected * if this is a
voice modem (e.g., V.253) operating in voice mode (e.g.,
+FCLASS=8.0) |
7 |
Data Answering signal detected
(e.g., V.25 ANS, V.8 ANSam) |
8 |
Data Calling signal detected
(e.g., V.25 CT, V.8 CI) |
9 |
Fax Answering signal detected
(e.g., T.30 CED, DIS) |
A |
Fax Calling signal detected
(e.g., T.30 CNG) |
B |
V.8bis signal
detected |
Code |
Definition |
0 |
Data Only |
1 |
Fax Only |
2 |
Voice |
9 |
Video-telephony, H.324 |
A |
Other V.80
call |
Code |
Definition |
0 |
Async data |
1 |
V.80 transparent synchronous
mode |
2 |
V.80 framed synchronous
mode |
Bits
|
Source bits
|
Definition
|
31-30
|
INFO0 bit 20; 0 |
|
20-29
|
INFOc bits 79-88 |
|
16-19
|
INFOc bits 26-29 or 35-38 or 44-47 or 53-56-
or 62-65 or 71-74 |
Pre-emphasis field, selected by the symbol
rate chosen |
12-15
|
INFOa bits 26-29 |
|
10-11
|
MP bit 50; 0 |
|
0-9
|
INFOa bits 40-49 |
|
gstnModulationSchemeActive from 3.7.2/V.58
Value
|
Description
|
0
|
V.17 (G3 Fax call) |
1
|
V.21 |
2
|
V.22 |
3
|
V.22bis |
4
|
V.23 Constant Carrier (1200/75) |
8
|
V.27ter (G3 Fax call) |
9
|
V.29 HD (G3 Fax call) |
A
|
V.32 |
B
|
V.32bis |
C
|
V.34 |
E
|
V.90 and V.92 |
81
|
K56flex |
84
|
Bell 212A |
85
|
Bell 103 |
Value
|
Description
|
0
|
Diable/none |
1
|
V.42 LAPM |
2
|
V.42 Alternative protocol (MNPT) |
80
|
MNP10 |
Value
|
Description
|
0
|
None |
1
|
V.42bis and V.44 |
80
|
MNPT |
Value
|
Description
|
Notes
|
0
|
CauseUnidentified |
Call setup issues |
1
|
No Previous call |
Not in V.58 |
2
|
Call is still in progress |
Not in V.58 |
3
|
Call Waiting signal detected |
Not in V.58, only if modem can detect it |
4
|
Delayed |
Same as value 2A, CallAttemptsLimitExceeded
|
19
|
InactivityTimerExpired |
|
1F
|
cct108isOffInhibitsDial |
DTR low |
20
|
cct108turnedOff |
DTR drop |
29
|
BlacklistedNumber |
|
2A
|
CallAttemptsLimitExceeded |
Same as "Delayed", see ETS 300 301 |
2B
|
ExtensionPhoneOff-hook |
If extension detection supported |
2C
|
CallSetupFailTimerExpired |
e.g., S7 timeout |
2D
|
IncomingCallDetected |
If incoming call while sending dial command |
2E
|
LoopCurrentInterrupted |
|
2F
|
NoDial tone |
|
31
|
ReorderTone |
Fast busy |
33
|
EngagedTone |
Busy |
34
|
LongSpaceDisconnect |
And if modem program to abort on long space |
3C
|
CarrierLost |
Signal Converter |
3D
|
TrainingFailed |
|
3E
|
NoModulationinCommon |
|
3F
|
RetrainFailed |
|
40
|
RetrainAttemptCountExceeded |
|
41
|
GstnCleardownReceived |
|
42
|
FaxDetected |
If this was not a fax call attempt |
46
|
InTestMode |
Test |
50
|
AnyKeyAbort |
Call Control |
51
|
DteHangupCommand
|
If ATH was used to terminate the previous
call |
52
|
DteResetCommand |
If ATH was used to terminate the previous
call |
5A
|
FrameReject |
Error Control |
5B
|
NoErrorControlEstablished |
Error control was required |
5C
|
ProtocolViolation |
|
5D
|
n400exceeded |
LAPM retransmission Count Timer |
5E
|
NegotiationFailed |
|
5F
|
DisconnectFrameReceived |
|
60
|
SabmeFrameReceived |
|
64
|
LossOfSynchronization |
Data Compression |
Example Modem Response and Usage
Example #UD commend response are shown in
Modem Response line
|
Description
|
DIAG <2A4D3263 0=9> |
This is version 0.9 |
DIAG <2A4D3263 1=06 2=0 3=0> |
Data Answer signal detected; Data only;
Character async |
DIAG <2A4D3263 5="C14513902A" 6="A145"> |
V.8 Call Menu indicates:
V.8 Joint Menu selects: |
DIAG <2A4D3263 10=1F 11=0C 12=52> |
Receive level = -31 dBm; transmit level
= -12 dBm; noise level = -82 dBm |
DIAG <2A4D3263 14=03 15=05 16=10> |
Far end echo delay in milliseconds; Far
end echo loss in dB; Near end echo loss = 16 dB |
DIAG <2A4D3263 20=C 22=780 24=0C80 26=79E0> |
Transmitter: V.34 training completed; V.34
carrier frequency = 1920; V.34 symbol rate = 3200; initial transmit
rate is 31200 bit/s |
DIAG <2A4D3263 21=D 25=1F40 27=DAC0> |
Receiver: V.90 training completed; V.90
symbol rate = 8000; initial receive rate is 56000 bit/s |
DIAG <2A4D3263 30=00 31=03 32=01 33=01> |
No carrier loss events, 3 carrier rate
renegotiations attempted; 1 carrier retrain requested; 1 carrier retrain
granted |
DIAG <2A4D3263 34=7080 35=CB20> |
Final transmit rate is 28800 bit/s; final
receive rate is 52000 bit/s |
DIAG <2A4D3263 40=1 41=100> |
LAPM negotiation completed; frame size
= 256 |
DIAG <2A4D3263 42=0 43=0> |
No error control timeout or link NAKs |
DIAG <2A4D3263 44=1 45=400> |
V.42bis data compression used; dictionary
size = 1024 |
DIAG <2A4D3263 50=2 51=2> |
Hardware transmit and receive flow control |
DIAG <2A4D3263 52=343CC 54=0> |
213964 DTE characters transmitted, w/o
underrun |
DIAG <2A4D3263 53=7230E6 55=47> |
7483622 DTE characters received, 71 characters
lost due to receive data overrun |
DIAG <2A4D3263 56=29D 58=0001 |
597 (decimal) frames transmitted, with
1 frame error |
DIAG <2A4D3263 58=2A4B 59=0004> |
10827 (decimal) frames received, with 4
frame errors |
DIAG <2A4D3263 60=51> |
Local PC initiated hangup |
|