Maintenance Commands
555-233-143
7-318 Issue 1 May 2002
Drop Reason
(cont’d)
Chair disconnected the endpoint, using either Chair Command Disconnect
(CCD) or Chair Command Kill (CCK) signals.
■ Conf End The conference was ended due to reaching stop time for a
reserved conference or due to an active conference being converted to file.
■ Endpoint Clearing received from DS1 - the disconnect came from the
endpoint. The endpoint notified the MCU that it intended to disconnect.
■ Far-end Clearing received from DS1 - the disconnect came from either
the network or the endpoint.
■ Handshake Either framing was never found (the endpoint could not
complete initialization - problems finding Frame Alignment Signal (FAS),
Multi Frame Alignment (MFA) and getting a corrected coded cap-set) or
framing was lost for some time (over 40 seconds) and the endpoint was
disconnected.
■ IDtimeout The MCU has not received response to the UIN/password
Query from the H.320 user after three attempts. Each attempt has a
system administered timeout period.
■ Internal MCU has a problem allocating trunk resources necessary to
route the dial-out call for the specified dial-numbers. This problem can be
associated with routing pattern or trunk associated translation (for example,
TAC specified in the dial-out number or routing pattern points to a trunk
group without members), or it can indicate a lack of trunk resources (for
example, every trunk member is maintenance busy or every in-service
member is busy on a call).
■ Network Clearing received from DS1 - the disconnect came from the
network. The endpoint that had the disconnect notification capability
disconnected without notifying the MCU.
■ Not-MCU The dial-out destination number(s) of the “CAS” extension has
terminated to a number that is not a dial-in cascade MCU extension.
■ No-ring This dial-out drop reason occurs when the call has been up for
30 seconds and no ringing is detected.
■ Reorder This dial-out drop reason occurs when the MCU detects that
there are no available trunks in the network to place the call. This drop
reason is detected by MCU CPTR resources. See “Dial-out” for a
description of CPTR usage.
■ Pre-AnsDrop The call disconnected before answer by an endpoint. The
cause of the disconnect may be the network, an endpoint, or a terminal
adapter. This drop reason is different from ‘No-answer,’ which indicates
that a 60-second timeout occurred while alerting. In this case, the call
drops before the 60-second timer has expired. Some busy endpoints
connected through terminal adapters display this behavior.
To Next Page
Loading...
