ELS Messages for Serial Interface Dialer (DIAL)
- Level:
- CE-ERROR
- Short Syntax:
- DIAL.001 Received I_ERR 0x status
length message_length
dev device name
- Long Syntax:
- DIAL.001 Frame received with I_ERR set (status = 0x status
) or bad length ( message_length
), on device device name
- Description:
- DIAL received a buffer from the driver. Either the error flag set
in the buffer or the data in the buffer were shorter than the
minimum allowed length.
- Action:
- Report this event to customer service.
- Level:
- UE-ERROR
- Short Syntax:
- DIAL.002 Bad indication " type
" state state
dev device name
- Long Syntax:
- DIAL.002 Received an unrecognized modem indication ( type
) in state state
, on device device name
- Description:
- dsi_rx() received a frame from the V.25 bis modem other than a normal
V.25 bis indication in a state other than "connected".
- Action:
- Report this event to customer service.
- Level:
- U-INFO
- Short Syntax:
- DIAL.003 Call to " address
" failed seconds
. milliseconds
seconds dev device name
- Long Syntax:
- DIAL.003 Call to " address
" failed after seconds
. milliseconds
seconds on device device name
- Description:
- A connection attempt failed. Refer to DIAL.016 for possible reasons
for V.25 bis modems.
- Level:
- UI-ERROR
- Short Syntax:
- DIAL.004 Error deleting record_type
" name
" dev device name
- Long Syntax:
- DIAL.004 Error occurred while deleting record_type
" name
" on device device name
- Description:
- An error occurred during an attempt to delete a configuration record
after converting the record to the format used in the latest release
of the router software or after renaming it.
- Action:
- Report this event to customer service.
- Level:
- UE-ERROR
- Short Syntax:
- DIAL.005 Unexpected state state1
instead of state2
dev device name
- Long Syntax:
- DIAL.005 Dialer state state1
is different from that expected state2
for internal event on device device name
- Description:
- An event occurred in a state which is inconsistent with the
design of the Dialer Finite State Machine.
- Action:
- Report this event to customer service.
- Level:
- C-INFO
- Short Syntax:
- DIAL.006 Old state state1
event " event
" new state state2
dev device name
- Long Syntax:
- DIAL.006 FSM transition occurred: old state state1
, event event
, new state state2
on device device name
- Description:
- The Dialer received an event which triggered a state change
in its Finite State Machine. If this occurred as a result of a
modem signal change, the preceding log message (if enabled) should
indicate the new signals.
- Level:
- C-INFO
- Short Syntax:
- DIAL.007 Modem signal change modem1
to modem2
dev device name
- Long Syntax:
- DIAL.007 A modem signal change was detected ( modem1
to modem2
) device device name
- Description:
- A change in the modem signals from the modem was detected; this may or
may not cause a state transition (follows).
- Level:
- UE-ERROR
- Short Syntax:
- DIAL.008 Modem not responding dev device name
- Long Syntax:
- DIAL.008 Modem not responding to the Dialer on device device name
- Description:
- The Dialer attempts to raise a V.25 bis modem on self-test.
If it doesn't respond (by raising CTS), the Dialer assumes it
is non-functional or non-compliant.
- Cause:
- Modem not connected, powered-off, inoperable, or non-V.25 bis
compliant.
- Action:
- Attach the cable to the modem, turn the modem on, fix the modem,
or get a compliant modem.
- Level:
- P-TRACE
- Short Syntax:
- DIAL.009 Received length message_length
dev device name
- Long Syntax:
- DIAL.009 Received a frame of length ( message_length
) from device device name
- Description:
- The Dialer received a data frame, which it is forwarding to
its client encapsulator.
- Level:
- P-TRACE
- Short Syntax:
- DIAL.010 Transmitted length message_length
dev device name
- Long Syntax:
- DIAL.010 Transmitted a frame of length ( message_length
) over device device name
- Description:
- The Dialer has transmitted a data frame on behalf of its
client encapsulator.
- Level:
- UI-ERROR
- Short Syntax:
- DIAL.011 Error converting record_type
" name
" dev device name
- Long Syntax:
- DIAL.011 Error prevented conversion of record_type
" name
" on device device name
- Description:
- An error occurred during conversion of a configuration record
to the format used in the latest release of the router software.
Depending on the type of error, the name may be left blank.
- Action:
- Report this event to customer service.
- Level:
- UI-ERROR
- Short Syntax:
- DIAL.012 Error deleting record_type
dev device name
- Long Syntax:
- DIAL.012 Error occurred while deleting record_type
on device device name
- Description:
- An error occurred during an attempt to delete a configuration record
after converting the record to the format used in the latest release
of the router software.
- Action:
- Report this event to customer service.
- Level:
- UI-ERROR
- Short Syntax:
- DIAL.013 Error converting record_type
dev device name
- Long Syntax:
- DIAL.013 Error prevented conversion of record_type
on device device name
- Description:
- An error occurred during conversion of a configuration record
to the format used in the latest release of the router software.
Depending on the type of error, the name may be left blank.
- Action:
- Report this event to customer service.
- Level:
- UI-ERROR
- Short Syntax:
- DIAL.014 Error renaming record_type
" old_name
" to " new_name
" dev device name
- Long Syntax:
- DIAL.014 Error prevented renaming of record_type
" old_name
" to " new_name
" on device device name
- Description:
- An error occurred during an attempt to rename a configuration record.
A configuration with the new name probably already exists.
- Level:
- U-TRACE
- Short Syntax:
- DIAL.015 Discarded received length message_length
state state
dev device name
- Long Syntax:
- DIAL.015 Dropping a received data frame of length ( message_length
) in state state
from device device name
- Description:
- The Dialer received a data frame while in a state where it
did not expect one, so it dropped it.
- Level:
- U-TRACE
- Short Syntax:
- DIAL.016 Indication " indication_type
" reason " reason
" state state
dev device name
- Long Syntax:
- DIAL.016 Modem indication ( indication_type
), reason " reason
" in state state
on device device name
- Description:
- The V.25 bis modem has sent the specified indication. This may
indicate that a connection attempt, initiated by the Dialer has failed
(INV or CFI) for the reason specified (see the calling unit user's
manual for a description of the reason code, if any accompanies this
message). Alternatively, this may just be a redundant incoming call
indicatation (INC), which had already been signalled by the CI Circuit
125.
- Cause:
- Call Aborted: router timed out, or modem user interface command.
- Action:
- Extend the call establishment period or don't interrupt the call.
- Cause:
- Local Modem Busy: the user interfered through the calling unit user
interface.
- Action:
- Do not interfere.
- Cause:
- Engaged Tone: the remote end is busy.
- Action:
- Try again later (the router should automatically).
- Cause:
- No Dial Tone: the telephone network isn't responding.
- Action:
- Fix the link, contact service provider.
- Cause:
- Number not stored.
- Action:
- Call customer service: we don't use the corresponding command.
- Cause:
- No Answer Tone Detected: remote unit did not respond with answer tone.
- Action:
- Check called number, verify that remote unit is on-line.
- Cause:
- Ring Tone (but no answer).
- Action:
- Check called number, verify that remote unit is on-line.
- Level:
- C-INFO
- Short Syntax:
- DIAL.017 Indication " message
" state state
dev device name
- Long Syntax:
- DIAL.017 Modem sent " message
" in state state
, on device device name
- Description:
- The V.25 bis calling unit has either accepted the router's request
(INC), or is connecting the call (CNX). This is a normal event
even though perhaps not always reported by a given modem/CU.
- Level:
- UE-ERROR
- Short Syntax:
- DIAL.018 Delayed call delay_time
minutes dev device name
- Long Syntax:
- DIAL.018 Modem indicates call delayed for delay_time
minutes on device device name
- Description:
- The V.25 bis modem has indicated that it will not attempt
additional outgoing calls for at least the indicated period. This
is an optional feature of some modems in some administrations, which
inhibits very frequent calls over a short period. Examine the
previous log entries to determine why so many calls are being made.
- Cause:
- Connections to a particular destination(s) are continually being
cleared.
- Action:
- Check the GateWay messages, to determine if the calls are being IDLE-d
out (increase the idle period), or if the verification procedure is
failing (check the calling number at both ends).
- Cause:
- Non-responding remote modem.
- Action:
- Check the called number and verify that the remote modem is on-line.
- Cause:
- Busy remote.
- Action:
- Increase the Call Retries timeout for that destination.
- Level:
- CI-ERROR
- Short Syntax:
- DIAL.019 No buffer for connection request dev device name
- Long Syntax:
- DIAL.019 Buffer unavailable for connection request on device device name
- Description:
- The Dialer needs a buffer to send the "connection request" to the
modem, and cannot obtain one. The call fails. The router should
re-initiate the call at a later time.
- Level:
- UE-ERROR
- Short Syntax:
- DIAL.020 Bad transmit status 0x status
for CRN dev device name
- Long Syntax:
- DIAL.020 Bad transmit status (0x status
) for CRN device device name
- Description:
- The driver reports a bad transmit status when trying to send the
V.25 bis Call Request (CRN).
- Level:
- C-INFO
- Short Syntax:
- DIAL.021 Set modem control modem_signals
dev device name
- Long Syntax:
- DIAL.021 Set modem control modem_signals
on device device name
- Description:
- The router is changing its output dataset signals in response to the
preceding event. (DTR = V.24 Circuit 108/2 and RTS = V.24 Circuit 105)
- Level:
- CI-ERROR
- Short Syntax:
- DIAL.022 No buffer for " action
" dev device name
- Long Syntax:
- DIAL.022 No buffer available for " action
" device device name
- Description:
- A packet buffer was not available when the hardware-specific
interface code required one to perform the specified action.
- Level:
- U-INFO
- Short Syntax:
- DIAL.023 Selftest OK dev device name
- Long Syntax:
- DIAL.023 Selftest completed successfully on device device name
- Description:
- Self-test of the connection between the router and the modem
completed successfully.
- Level:
- C-INFO
- Short Syntax:
- DIAL.024 Transmit CRN for call to " destination
" dev device name
- Long Syntax:
- DIAL.024 Sending Dial (CRN) command for call to " destination
" on device device name
- Description:
- The modem is in a now in a state where it can actually receive
V.25 bis commands, so we are sending it the telephone number to dial.
- Level:
- C-INFO
- Short Syntax:
- DIAL.025 Connection request to " destination
" dev device name
- Long Syntax:
- DIAL.025 Client connection request to destination
on device device name
- Description:
- The client (e.g., Dial Circuit or WAN Restoral) has made a connection
request to the specified address.
- Level:
- C-INFO
- Short Syntax:
- DIAL.026 Connection request to " destination
" blocked dev device name
- Long Syntax:
- DIAL.026 Client connection request on busy device to destination
on device device name
- Description:
- The client (e.g., Dial Circuit or WAN Restoral) is trying to initiate
a connection, but the base network is busy.
- Level:
- C-INFO
- Short Syntax:
- DIAL.027 Call to " destination
" completed time
seconds dev device name
- Long Syntax:
- DIAL.027 Client connection established to destination
in time
seconds on device device name
- Description:
- The connection requested by a local client (e.g., Dial Circuit or WAN
Restoral) to the specified address has been established in the
specified time. The operator may care to use this value to adjust
the configured connect timeout.
- Level:
- ALWAYS
- Short Syntax:
- DIAL.028 Bad direct transmit protocol protocol
dev device name
- Long Syntax:
- DIAL.028 Some forwarder ( protocol
) has attempted to transmit directly over the Dialer device device name
- Description:
- Transmission over the Dialer network is supposed to be done only via
an associated dial circuit, which will do an appropriate encapsulation.
This is caused by a mistake in the configuration of the forwarders.
No forwarder should be configured to use the Dialer network. To bound
the number of these messages, they will be logged for only a
fraction of the actual events.
- Cause:
- A forwarder (IP, IPX, etc) address was assigned to the Dialer
interface.
- Action:
- Delete the address, and (probably) re-assign it to a dial circuit
(which is itself mapped to the Dialer network).
- Cause:
- The bridge or other forwarder has been configured to use the Dialer
interface.
- Action:
- Remove the Dialer interface as a port used by the bridge or forwarder.
- Level:
- P-TRACE
- Short Syntax:
- DIAL.029 DSIO completed dev device name
- Long Syntax:
- DIAL.029 DSIO completion device device name
- Description:
- The Dialer issued a DSIO request which has completed.
- Level:
- UE-ERROR
- Short Syntax:
- DIAL.030 Bad transmit status 0x status
for chat script dev device name
- Long Syntax:
- DIAL.030 Bad transmit status (0x status
) for chat script device device name
- Description:
- The driver reports a bad status when trying to transmit the data
requested by a transmit command of a chat script.
- Level:
- P-TRACE
- Short Syntax:
- DIAL.031 End chat script dev device name
- Long Syntax:
- DIAL.031 End of chat script device device name
- Description:
- The last command of the chat script has been executed.
- Level:
- P-TRACE
- Short Syntax:
- DIAL.032 Chat script transmitted " chat_script_text
" dev device name
- Long Syntax:
- DIAL.032 Transmitted line " chat_script_text
" for chat script device device name
- Description:
- The Dialer has transmitted the data requested by a transmit
command of a chat script.
- Level:
- P-TRACE
- Short Syntax:
- DIAL.033 Chat script received " chat_script_text
" dev device name
- Long Syntax:
- DIAL.033 Received line " chat_script_text
" for chat script device device name
- Description:
- The Dialer has received data to be processed by the chat script.
- Level:
- CI-ERROR
- Short Syntax:
- DIAL.034 No buffer for modem command " modem_command
" dev device name
- Long Syntax:
- DIAL.034 No buffer available for modem command " modem_command
" device device name
- Description:
- A packet buffer was not available when the Dialer attempted
to issue the specified command string to the modem.
- Level:
- P-TRACE
- Short Syntax:
- DIAL.035 Modem result code " result_code
" state state
dev device name
- Long Syntax:
- DIAL.035 Modem result code " result_code
" in state state
on device device name
- Description:
- The modem has returned the specified result code. This may
indicate that a connection attempt, initiated by the Dialer
has failed (ERROR, BUSY, NO CARRIER, NO ANSWER, NO DIALTONE) for
the reason specified (see the modem's user manual for a description
of the result code). Alternatively, this may just be an incoming
call indication (RING), which may also be signalled by the CI
Circuit 125. Or it may be an indication that a command to the
modem has succeeded (OK).
- Cause:
- OK: a modem command was successfully issued.
- Action:
- None.
- Cause:
- ERROR: a modem command failed, possibly because the command is
unknown to the modem.
- Action:
- Check the modem's user manual for the proper command to use.
- Cause:
- CONNECT: a connection has been successfully established. Carrier
detect is up.
- Action:
- None.
- Cause:
- NO CARRIER: carrier detect has failed or has been dropped because
of disconnection.
- Action:
- Retry the connection if necessary.
- Cause:
- BUSY: the remote end is busy.
- Action:
- Try again later (the router should automatically retry).
- Cause:
- NO DIALTONE: the telephone network isn't responding.
- Action:
- Fix the link, contact service provider.
- Cause:
- NO ANSWER: the remote unit did not respond with answer tone.
- Action:
- Check the called number; verify that remote unit is on-line.
- Cause:
- RING: incoming ring has been detected.
- Action:
- None. The call will be answered by the Dialer.
- Level:
- UE-ERROR
- Short Syntax:
- DIAL.036 Bad transmit status 0x status
for modem command dev device name
- Long Syntax:
- DIAL.036 Bad transmit status (0x status
) for modem command device device name
- Description:
- The driver reports a bad status when trying to transmit a command
to the modem.
- Level:
- P-TRACE
- Short Syntax:
- DIAL.037 Modem command " modem_command
" dev device name
- Long Syntax:
- DIAL.037 Modem command " modem_command
" issued device device name
- Description:
- The Dialer has issued the specified command string to the
modem.
- Level:
- U-INFO
- Short Syntax:
- DIAL.038 Failed to accept call seconds
. milliseconds
seconds dev device name
- Long Syntax:
- DIAL.038 Failed to accept call after seconds
. milliseconds
seconds on device device name
- Description:
- A attempt to accept an inbound call failed after the indicated
number of seconds had elapsed.
- Level:
- CE-ERROR
- Short Syntax:
- DIAL.039 Chat script not found dev device name
- Long Syntax:
- DIAL.039 Chat script not found device device name
- Description:
- The Dialer could not find a configuration record for the
chat script name specified in the dial circuit configuration.
The chat script does not exist.
- Level:
- P-TRACE
- Short Syntax:
- DIAL.040 Chat script waiting seconds
seconds dev device name
- Long Syntax:
- DIAL.040 Chat script waiting for seconds
seconds device device name
- Description:
- As directed by a chat script WAIT command, the Dialer is
waiting for the indicated number of seconds before processing the
next TRANSMIT command in the chat script.