status conference

Last Updated : Sep 28, 2022 |

Use status conference to help identify problems with a multimedia conference, and to help solve more complex problems.

Syntax

status conference [ all | conference-ID] [ schedule ] [ endpoint-all | endpoint-ID] 
all

Display all stored conference data.

conference-ID

Display data for the specified conference (current or last).

schedule

Schedule a time to run the command.

endpoint-all

Display conference data for all endpoints in the specified conference. This is the default.

endpoint-ID

Display conference data for the specified endpoint.

Description

The first screen is displayed when status conference is entered and at least 1 valid conference is found. Use status conference to solve the following multimedia problems:

  • A user unable to join or remain joined to a conference.

  • A conference having poor video quality due to it being downgraded because of the automatic algorithms — audio AUTO mode and the Px64 video picture specifications.

  • A user unable to receive full service, such as being an audio-only endpoint (no video).

  • An audio add-on user unable to join or remain joined to a conference.

  • A conferee invisible to other users due to interworking problems.

  • A user unable to participate in the Multipoint Communications Service conference.

  • A continuous conference, without switching endpoints in or out of quadrants.

Depending on the status conference command entered, it is possible to have many records display. Active conferences display first (in order of conference-ID), followed by completed conferences (most recently completed first). There is no data or information about conferences yet to begin.

The data for each conference displays in 2 parts: the first screen describes the status of the conference and indicates the modes and levels of the conference. It also shows certain endpoint information such as which endpoints are in use and which endpoint caused the conference operating mode to change. This screen is similar to the administration screens. The remainder of the screens display endpoint level data (up to 8 endpoints per screen), displaying the ports and drop reasons.

status conference output field descriptions — page 1

Field

Description

Status

The current status of the conference:

  • active

  • in-use

  • complete

Conference Name

Always set as MMCH DYNAMIC

Conference Mode

Always set as voice-activated

Password

not applicable

Password Scope

not applicable

Cascade Mode

Conference cascade mode — blank

Audio Mode

The current operating audio mode — G.711-A, G.711-mu, G.728, G.722

Class

The type of conference — dedicated

Data Mode

Data mode capability for this conference — none, any-mlp, ww-pcs

MLP Rate

MLP Data Rate for this conference — blank

No. of Channels

The number of channels (transfer rate) required for each Px64 endpoint —- 2.

Chair

Identifies the current chair token holder. This field is always blank.

Conf Bandwidth

The current operating channel conference bandwidth. This can be different from the administered bandwidth because of Rate Adaptation.

Rate Adaptation

Does this conference support Rate Adaptation? — n/y.

Format (in/out)

  • For single-screen conference, the video format of the conference, CIF, QCIF, QCIF/CIF, H.CTS, H.CTX+, and SG4.

  • For conferences other than H.261, the input and output formats are always symmetric and the mode is the same for input and output. These display as H.CTX, H.CTX+, SG4.

  • For H.261 mode non-continuous presence conferences, the format is always symmetric and displays as CIF and QCIF. The same is true for the non-presentation, continuous presence conference in single-screen.

  • For presentation mode H.261 single screen continuous presence capable conferences, the input and output formats may be symmetric QCIF/CIF (displayed as CIF) or asymmetric QCIF/CIF, depending on if the format is administered as upgradeable.

  • For quad-screen conferences, the format is QCIF/CIF to reflect the input of QCIF from every participant and output of CIF to every participant.

  • For presentation mode quad-screen conference, the format is also QCIF/CIF to reflect the input/output of every participant except the presenter. In quad-screen mode, the input from the presenter is always CIF.

FPS

The CIF frame rate (frames per second) — ‘-‘, 30, 15, 10, 7.5. FPS indicates the rate that an endpoint is capable of receiving frames. Note that there is no indication of the maximum transmit frame rate nor the current frame rate that the MCU can detect. The frame rate changes as a function of the amount of motion in the input image.

QFPS

The ACIF frame rate (frames per second) — ‘- ‘, 30, 15, 10, 7.5. QFPS indicates the rate that an endpoint is capable of generating/receiving frames. For quad-screen VAS conferences, QFPS reflects the highest common QCIF frame rate of every endpoint and the rate of the video mixer board, which may be lower than the rest of the participants. Note that QCIF calculation takes into account the highest common CIF frame rate declared by every conference participant, since QCIF rate cannot be greater than that of the highest common CIF rate.

For quad-screen presentation conferences, QFPS reflects the highest common QCIF frame rate of every participant and the rate of the video mixer board. Note that the QFPS cannot be greater than the CIF frame rate announced by the presenter.

QFPS field is blank for proprietary modes.

Lo/Hi Interworking

Conference supports Low Speed/High Speed Interworking. Always n.

Type

The type of conferee, either Audio/Video (P64), Audio Add-on (AUD), Cascade Link (CAS), BONDing Call (BOND), BONDing Cascade Link (BCAS), UCC Controller (UCC), or Dedicated Access (DA). BONDing calls use up to 12 channels to form a single multimedia pipe.

Ext

Endpoint extension chosen at administration. This field is blank.

Meet-me Number

Meet-Me Number administered for the Meet-Me Extension. This field is blank.

Dial Type

Indicates whether dial-in or dial-out is used to join the endpoint to the conference:

  • in — dial-in

  • out— dial-out

In Use

Is the endpoint currently participating in the conference or in process of connecting to the conference?

  • y — The endpoint is in use and is fully connected on all media in an active conference.

  • c — The endpoint is in use and is fully connected, however the endpoint has changed the conference audio or video capability or has changed the rate of the conference because of rate adaptation. This condition requires analysis of this endpoint’s capabilities and mode fields to identify which capability was reduced.

  • e — The endpoint is in use but the endpoint had capability problems. The endpoint does not have one of the required capabilities (Vid, Bhl, MLP) to be a full participant. For MLP capabilities, see the T120 field. This condition requires analysis of this endpoint’s capabilities and mode field to identify the missing capability.

  • f — The endpoint is in use but is disconnected from all media. This indicates that the endpoint has declared every required capability (channel/video/audio/data) but is not fully connected to all conference media at this time. This endpoint may be in the process of connecting, has failed to connect, or is not a valid video source. This condition requires analysis of this endpoint’s capabilities and mode fields to identify the problem.

  • n — The endpoint was connected in a conference but has/was disconnected or attempted to connect to a conference but was unsuccessful.

  • blank — until the first call is made from/to the endpoint.

Chl

Data on the quantify and quality of channels (transfer rate)?

  • y — The endpoint has the required number of channels.

  • e — The endpoint has not declared support for the correct number of channels and cannot participate fully in the conference.

  • n — The endpoint has declared the correct number of channels, but every channel has not yet joined the conference, due to either a network or endpoint problem.

  • blank — Audio add-on endpoints always set to blank.

Aud

Does the endpoint have the required audio capability?

  • y — The endpoint has the required audio capability. Audio add-on endpoint always have the Aud field set to y once the endpoint has joined the conference.

  • c — This endpoint is PCM only and it changed the video quality of the conference by changing the operating audio from G.728 to G.711. If the administered audio mode is auto and the administered bandwidth is 112 kbps (56 k/channel) or 128 kbps (64 k/channel), the system starts out with the highest common audio of G.728. When the administered bandwidth is greater than 128 kbps, the system starts out with the highest common bandwidth of 7 kHz.

  • e — A PCM-only endpoint that did not have the capability of supporting the administered audio mode of G.728 (such as a data conference), or G. 278/G.711 endpoint that did not have the capability of supporting the administered audio mode of 7 kHz. Such endpoints operate with PCM audio and interwork with the current operating audio mode.

  • blank — until the first call is made from/to the endpoint.

Vid

Does the endpoint have the required video capability and is receiving video?

  • y — The endpoint has the required video capability and should be receiving video if the Chl, Aud, and Dat fields are y.

  • c — It downgraded the conference’s video quality - either from CIF to ACIF or by decreasing the frame rate. The conference video mode is set by default to CIF and if a QCIF-only endpoint joins the conference, then the entire conference is made to operate in QCIF, with the video clarity downgraded. Also, the conference frame rate is initially set to the highest frame rate that can then be reduced by any endpoint. If the conference video mode is not administered with upgrade capability, then if the video parameters for a conference have been downgraded, they are not upgraded until every endpoint disconnects from the conference.

  • e — The endpoint has not declared any video capability in its cap-set.

  • n — Audio only, not receiving video, possibly due to an audio or data problem.

  • blank — Audio add-on endpoints always blank.

Mlp

The state of the Control Link to the ESM (T.120 stack terminator), the endpoint MLP data capability, and the state of the data connection in the T.120 stack. This field value is always blank, indicating that the Data Mode for the conference is none, and therefore, the data does not apply, or the endpoint has never joined the conference.

Gx

Does the endpoint have the Still Frame Graphics capability?

  • y — This endpoint has this capability.

  • e — This endpoint did not declare this capability. The conference retains the still frame graphics capability when a non-compliant endpoint joins the conference.

  • blank — This endpoint has never joined the conference.

Rate Adpt

Rate adaptation/interworking indicator. Values of 5 and 6 apply only to low-speed/high-speed interworking. Every other value applies only to rate adaptation.

  • 5 — A 56-kbps (low-speed) endpoint has joined a high-speed (128-kbps or above) conference. This endpoint is connected with audio-only capability, but is neither a valid video source nor destination.

  • 6 — A 64-kbps (low-speed) endpoint has joined a high-speed (128-kbps or above) conference. This endpoint is connected with audio-only capability, but is neither a valid video source nor destination.

  • y — This endpoint has joined a conference at the administered rate of 64 kbps, but (because rate adaptation to 56 kbps was triggered by another endpoint) this endpoint has successfully rate-adapted to 56 kbps.

  • c — The administered bandwidth of a conference is 64 kbps and this endpoint has joined the conference at 56 kbps. The first 56-kbps endpoint that joins a 64-kbps rate-adaptable conference triggers rate adaptation (see Join Time below).

  • n — A 64-kbps conference was triggered to rate adapt to 56 kbps by some other endpoint. This endpoint joined the conference at the bandwidth of 64 kbps, but encountered problems in rate adapting down to 56 kbps. This endpoint may have the audio and may be receiving video, but is not a valid video source.

  • blank — Rate adaptation was never triggered by any endpoints. So, if an endpoint is in use and connected, then it joined the conference at the administered bandwidth.

Bond Mode

Bonding Mode — blank. This field is blank for calls that are not related to bonding.

Ts

Indication of the talking state of the endpoint.

  • t — At the time the command was invoked, voice energy (talking) was detected from the endpoint.

  • m — At the time the command was invoked, the endpoint indicated to the MCU that it was muted. It is possible that an endpoint may mute, but not send any indication to the MCU. In this situation the MCU does not display a mute indication.

  • M — At the time the command was invoked, the endpoint’s audio was muted via UDD/CRCS Agent interface. M displays when both the endpoint and the UCC/CRCS Agent have muted the endpoint audio.

  • S — At the time the command was invoked, the endpoint’s audio was muted because of solo-audio state set by UCC/CRCS Agent. While in solo-audio state, new endpoints joining the conference are automatically muted.

  • blank — At the time the command was invoked, voice energy (talking) was not being detected from the endpoint.

Vs

  • a — This value applies only to quad-screen conferences. *a indicates that an endpoint is part of the current mixed image and is fixed in one of the quadrants via administration. *a indicates that the endpoint is fixed in a quadrant but is not currently connected (Fill image displays).

  • b — For full-screen conference it indicates that at the time the command was invoked, this endpoint’s video was being broadcast to other sites. This conference was in VAS, broadcast, or presentation mode. For quad-screen VAS conference it is prefixed with an asterisk (*) and indicates that this endpoint’s video is part of the mixed image because of VAS. For quad-screen presentation conferences, b(without an asterisk) identifies the presenter as the broadcaster.

  • B — At the time the command was invoked the endpoint’s video was being broadcast to other sites because of the UCC roll call feature. UCC roll call feature can only be performed in full-screen mode.

  • c — At the time the command was invoked this endpoint’s video was being broadcast to other sites. The conference was in chair mode and the broadcaster was designated by the chair. Chair features can only be performed in full-screen mode.

  • i — At the time the command was invoked the endpoint was not a valid video source. For continuous presence conference, if this endpoint is fixed in a particular quadrant, a pound (#) is affixed before i.

  • r — For full-screen conferences, at the time the command was invoked the endpoint’s video was the return video to the broadcaster. For continuous presence conference in presentation mode, *r represents a VAS quadrant that is part of the mixed image.

  • R — At the time the command was invoked, the endpoint’s video was the return video to the broadcaster because of the UCC browse feature. UCC Browse feature can only be performed in full-screen mode.

  • s — At the time the command was invoked this endpoint’s video was suppressed at the request of the endpoint. For continuous presence conference with fixed quadrant participants, if this endpoint is fixed in a particular quadrant a pound (#) is affixed before s.

  • S — At the time the command was invoked this endpoint’s video was suppressed via UCC/CRCS Agent interface. For continuous presence conference with fixed quadrant participants, if this endpoint is fixed in a particular quadrant, a pound (#) is affixed before S. S is displayed when the endpoint and the UCC/CRCS Agent have suppressed the endpoint video.

  • u — For full-screen conferences, at the time the command was invoked this endpoint’s video was being broadcast to other sites. The conference was in VAS mode and the broadcaster was designated by the UCC/CRSCS Agent interface. For quad-screen conferences, it indicates that UCC/CRCS Agent designated this endpoint as fixed in a quadrant. An asterisk (*) is affixed before u if the endpoint is currently part of the quad image, and a pound (#) is affixed if the endpoint is not currently joined.

  • U — Applies only to quad-screen conference and indicates that UCC/ CRCS Agent designated a quadrant as VAS. An asterisk (*) is affixed before U to indicate that this endpoint is part of the current quad image.

  • v — At the time the command was invoked this endpoint’s video was being broadcast to other sites. The conference was in VAS mode but the endpoint has asked to be a broadcaster via See-Me request and was granted a MCV (Multipoint Command Visualize) token. The See-Me feature is only performed in full-screen mode.

  • blank — At the time of the request the endpoint’s video was not broadcast, return, video, or part of the mixed-image, but it is a valid video source.

status conference output field descriptions — page 2

Field

Description

Sum Grp

The VD audio Level 1 (L1) and Level 2 (L2) summer group parts for each assigned group (1–4). Summer parts are assigned only for conferences with over 6 participants. When a conference operates at an audio mode of 7 kHz (administered audio mode is 7 kHz, or auto with the bandwidth greater than 128 kbps), the system allocates “primary” and “secondary” L1 and L2 summer parts. These primary and secondary parts are allocated as adjacent port slots on the same board. Status conference only displays the primary summer ports. The secondary summer ports are always one slot higher than the displayed primary summer port.

Join Time

Time (in 24-hour notation) when the channel joined the conference.

Drop Time

The endpoint is idle if the first channel has a drop time.

Drop Reason

The reason for the channel’s disconnect:

  • 2-pri — This drop reason occurs when an administration error causes a mismatch in primary-secondary designation for a cascade link. This mismatch shows that both MCUs are administered as primaries (see Cascading for a description of primary-secondary compatibility).

  • 2-sec — This drop reason occurs when an administration error causes a mismatch in primary-secondary designation for a cascade link. This mismatch shows that both MCUs are administered as secondaries (see Cascading for a description of primary-secondary compatibility).

  • Agent — The reservation agent has caused the call to disconnect (for example, the agent has changed a connected dial-out destination number).

  • Bandwidth — mismatch between a call and the conference it attempted to join. For example, a 56-kbps call attempted to join a 64-kbps conference that does not permit rate adaptation.

  • BondHshake — Bonding handshake drop reason can be caused due to the following reasons: information channel parameter not supported or invalid, parameter negotiation terminated out of sequence, timer expired because of the secondary channels did not establish, or BONDing framing was not detected for one of the other channels.

  • Busy — This dial-out drop reason occurs when the MCU detects that the conferee’s terminal equipment is busy. This drop reason is detected by an ISDN cause value (for example, h0). See Dial-out for a description of CPTR usage.

  • 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.

  • No-ring — This dial-out drop reason occurs when the call has been up for 30 seconds and no ringing is detected.

  • 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.

  • Password — Either the user entered the wrong password or the audio add-on user did not enter it within the specified time period. Note that the audio add-on user gets one attempt to enter a correct password and inter-digit timing for each digit (that is, about 10 seconds between digits).

  • 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.

  • Resource — MCU could not provide resources (VC or MMI) when the call arrived or lost the resources during the call. This could be due to them being Out of Service, busied out by craft, or being used by system maintenance. This drop reason could also occur if the DS1/ MMI cable is disconnected. If there was a resource problem when the call arrived, it would get reorder (fast busy) and not get disconnected by the MCU.

  • 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.

  • System — An MCU restart (level 2) disconnected every call.

  • UIN-Inv — The user entered an invalid User Identification Number.

  • Unknown — The system could not determine the cause of the disconnect.

  • Wrong-num — This dial-out drop reason occurs when the MCU detects the wrong destination number was dialed. This drop reason is detected by MCU CPTR resources SDN cause value. See Dial-out for details.

  • UCC — controller intentionally disconnected the endpoint.

AC Num

Administered Connection Number - from 1 to 128. AC number can be used to further diagnose a problem by combining status conference information with status administered connection and data stored in the error and alarm logs.

Ports Trunk

The data endpoint that the channel is using.

Ports Video

The MMI port for the channel.

Ports Aud

If the endpoint type is not UCC, the VC audio encoder port (which is always paired to a decoder port) for the channel (only the first channel). Because only one audio encoder port is allocated per endpoint, it is together with the ESM data port in the endpoint’s channel 1 port slot position of the Port Aud/ESM column.

For UCC endpoint type, the channel 1 port slot position displays the allocated Call Classifier resource.

Ports ESM

The Expansion Service Module MMI data port. This field is always blank.

Sum Grp

Endpoint’s assigned summer group number. The summer group port assignments are on screen 1.

Software

For Avaya use only.

status conference x endpoint y field descriptions — page 1

Field

Description

Endpoint

Endpoint-ID is a slot number associated with the endpoint entered on the conference forms.

Product

Product identification number obtained from the endpoint.

Manufacturer/Country

Manufacturer identification number and manufacturer’s country code obtained from the endpoint.

Terminal Name

blank

Sum Grp

Summer group number to which this endpoint belongs and the VC Audio Level (L1) and Level 2 (L2) summer ports for this group. These fields have an entry only for conferences with over 6 participants.

Dial Out #1

Dial Out #2

Blank

Blank

In Use

Is the endpoint currently participating in the conference or in process of connecting to the conference?

  • y — The endpoint is in use and is fully connected on all media in an active conference.

  • c — The endpoint is in use and is fully connected, however the endpoint has changed the conference audio or video capability or has changed the rate of the conference because of rate adaptation. This condition requires analysis of this endpoint’s capabilities and mode fields to identify which capability was reduced.

  • e — The endpoint is in use but the endpoint had capability problems. The endpoint does not have one of the required capabilities (Vid, Bhl, MLP) to be a full participant. For MLP capabilities, see the T120 field. This condition requires analysis of this endpoint’s capabilities and mode field to identify the missing capability.

  • f — The endpoint is in use but is disconnected from all media. This indicates that the endpoint has declared every required capability (channel/video/audio/data) but is not fully connected to all conference media at this time. This endpoint may be in the process of connecting, has failed to connect, or is not a valid video source. This condition requires analysis of this endpoint’s capabilities and mode fields to identify the problem.

  • n — The endpoint was connected in a conference but has/was disconnected or attempted to connect to a conference but was unsuccessful.

  • blank — until the first call is made from/to the endpoint.

Enh BAS

Enhanced Basic Service Flag

  • y — The endpoint supports the enhanced BAS commands/caps

  • n — The endpoint only supports the basic BAS commands/caps

Chl

Data on the quantify and quality of channels (transfer rate)?

  • y — The endpoint has the required number of channels.

  • e — The endpoint has not declared support for the correct number of channels and cannot participate fully in the conference.

  • n — The endpoint has declared the correct number of channels, but every channel has not yet joined the conference, due to either a network or endpoint problem.

  • blank — Audio add-on endpoints always have a blank Chl field.

Aud

Does the endpoint have the required audio capability?

  • y — The endpoint has the required audio capability. Audio add-on endpoint always have the Aud field set to y once the endpoint has joined the conference.

  • c — This endpoint is PCM only, and it changed the video quality of the conference by changing the operating audio from G.728 to G.711. If the administered audio mode is auto and the administered bandwidth is 112 kbps (56 k/channel) or 128 kbps (64 k/channel), the system starts out with the highest common audio of G.728. When the administered bandwidth is greater than 128 kbps, the system starts out with the highest common bandwidth of 7 kHz.

  • e — A PCM-only endpoint that did not have the capability of supporting the administered audio mode of G.728 (such as a data conference). G.278/G.711 endpoint that did not have the capability of supporting the administered audio mode of 7 kHz. Such endpoints operate with PCM audio and interwork with the current operating audio mode.

  • blank — The field is blank until the first call is made from/to the endpoint.

Vid

Does the endpoint have the required video capability and is receiving video?

  • y — The endpoint has the required video capability and should be receiving video if the Chl, Aud, and Dat fields are y.

  • c — It downgraded the conference’s video quality - either from CIF to ACIF or by decreasing the frame rate. The conference video mode is set by default to CIF and if a QCIF-only endpoint joins the conference, then the entire conference is made to operate in QCIF, with the video clarity downgraded. Also, the conference frame rate is initially set to the highest frame rate that can then be reduced by any endpoint. If the conference video mode is not administered with upgrade capability, then if the video parameters for a conference have been downgraded, they are not upgraded until every endpoint disconnects from the conference.

  • e — The endpoint has not declared any video capability in its cap-set.

  • n — Audio only, not receiving video, possibly due to an audio or data problem.

  • blank — Audio add-on endpoint always have the Vid field set to blank.

Mlp

The state of the Control Link to the ESM (T.120 stack terminator), the endpoint MLP data capability, and the state of the data connection in the T.120 stack. This field value is always blank, indicating that the Data Mode for the conference is none, and therefore, the data does not apply, or the endpoint has never joined the conference.

Gx

Does the endpoint have the Still Frame Graphics capability?

  • y — This endpoint has this capability.

  • e — This endpoint did not declare this capability. The conference retains the still frame graphics capability when a non-compliant endpoint joins the conference.

  • blank — This endpoint has never joined the conference.

Rate Adpt

Rate adaptation/Interworking indicator. Values of 5 and 6 apply only to low-speed/high-speed interworking. Every other value applies only to rate adaptation.

  • 5 — A 56-kbps (low-speed) endpoint has joined a high-speed (128-kbps or above) conference. This endpoint is connected with audio-only capability, but is neither a valid video source nor destination.

  • 6 — A 64-kbps (low-speed) endpoint has joined a high-speed (128-kbps or above) conference. This endpoint is connected with audio-only capability, but is neither a valid video source nor destination.

  • y — This endpoint has joined the conference at the administered rate of 64 kbps, but (because rate adaptation to 56 kbps was triggered by another endpoint) this endpoint has successfully rate adapted to 56 kbps.

  • c — The administered bandwidth of the conference is 64 kbps and this endpoint has joined the conference at 56 kbps. The first 56-kbps endpoint that joins 64-kbps rate-adaptable conference triggers rate adaptation (see Join Time below).

  • n — A 64-kbps conference was triggered to rate adapt to 56 kbps by some other endpoint. This endpoint joined the conference at the bandwidth of 64 kbps, but encountered problems in rate adapting down to 56 kbps. This endpoint may have the audio and may be receiving video, but is not a valid video source.

  • blank — Rate adaptation was never triggered by any endpoints. So, if this endpoint is in use and connected, then it joined the conference at the administered bandwidth.

Bond Mode

Bonding Mode — blank.

This field is blank for calls that are not related to bonding.

Ts

Indication of the talking state of the endpoint.

  • t — At the time the command was invoked, voice energy (talking) was detected from the endpoint.

  • m — At the time the command was invoked, the endpoint indicated to the MCU that it was muted. It is possible that an endpoint may mute, but not send any indication to the MCU. In this situation the MCU does not display a mute indication.

  • M — At the time the command was invoked, the endpoint’s audio was muted via UDD/CRCS Agent interface. M displays when both the endpoint and the UCC/CRCS Agent have muted the endpoint audio.

  • S — At the time the command was invoked, the endpoint’s audio was muted because of solo-audio state set by UCC/CRCS Agent. While in solo-audio state, new endpoints joining the conference are automatically muted.

  • blank — At the time the command was invoked, voice energy (talking) was not being detected from the endpoint.

Vs

Indication of the MCU video state for this endpoint.

For quad-screen conferences, an asterisk (*) is affixed before the value of Vs to indicate that an endpoint is currently part of the mixed image. A pound (#) may be affixed before the value of Vs to indicate that an endpoint was fixed to be in the mixed image (via administration or UCC/CRCS Agent), but instead, a Fill video is shown in its place. This occurs when the video of an endpoint that is fixed in a quadrant cannot be used as a video source because the endpoint is currently not joined to the conference, has suppressed its video, or has invalid video to be the video source. Notice that at most four endpoints have an * or # affixed before the Vs field value.

For quad-screen conference in VAS mode, the mixed image is broadcast to every endpoint. For quad-screen conference in presentation mode, the mixed image is return video to the presenter.

  • a — This value applies only to quad-screen conferences. *a indicates that an endpoint is part of the current mixed image and is fixed in one of the quadrants via administration. *a indicates that the endpoint is fixed in a quadrant but is not currently connected (Fill image displays).

  • b — For full-screen conference it indicates that at the time the command was invoked, this endpoint’s video was being broadcast to other sites. This conference was in VAS, broadcast, or presentation mode. For quad-screen VAS conference it is prefixed with an asterisk (*) and indicates that this endpoint’s video is part of the mixed image because of VAS. For quad-screen presentation conferences, b(without an asterisk) identifies the presenter as the broadcaster.

  • B — At the time the command was invoked the endpoint’s video was being broadcast to other sites because of the UCC roll call feature. UCC roll call feature can only be performed in full-screen mode.

  • c — At the time the command was invoked this endpoint’s video was being broadcast to other sites. The conference was in chair mode and the broadcaster was designated by the chair. Chair features can only be performed in full-screen mode.

  • B — At the time the command was invoked the endpoint’s video was being broadcast to other sites because of the UCC roll call feature. UCC roll call feature can only be performed in full-screen mode.

  • i — At the time the command was invoked the endpoint was not a valid video source. For continuous presence conference, if this endpoint is fixed in a particular quadrant, a pound (#) is affixed before i.

  • r — For full-screen conferences, at the time the command was invoked the endpoint’s video was the return video to the broadcaster. For continuous presence conference in presentation mode, *r represents a VAS quadrant that is part of the mixed image.

  • R — At the time the command was invoked, the endpoint’s video was the return video to the broadcaster because of the UCC browse feature. UCC Browse feature can only be performed in full-screen mode.

  • s — At the time the command was invoked this endpoint’s video was suppressed at the request of the endpoint. For continuous presence conference with fixed quadrant participants, if this endpoint is fixed in a particular quadrant a pound (#) is affixed before s.

  • S — At the time the command was invoked this endpoint’s video was suppressed via UCC/CRCS Agent interface. For continuous presence conference with fixed quadrant participants, if this endpoint is fixed in a particular quadrant, a pound (#) is affixed before S. S is displayed when the endpoint and the UCC/CRCS Agent have suppressed the endpoint video.

  • u — For full-screen conferences, at the time the command was invoked this endpoint’s video was being broadcast to other sites. The conference was in VAS mode and the broadcaster was designated by the UCC/CRSCS Agent interface. For quad-screen conferences, it indicates that UCC/CRCS Agent designated this endpoint as fixed in a quadrant. An asterisk (*) is affixed before u if the endpoint is currently part of the quad image, and a pound (#) is affixed if the endpoint is not currently joined.

  • U — Applies only to quad-screen conference and indicates that UCC/ CRCS Agent designated a quadrant as VAS. An asterisk (*) is affixed before U to indicate that this endpoint is part of the current quad image.

  • v — At the time the command was invoked this endpoint’s video was being broadcast to other sites. The conference was in VAS mode but the endpoint has asked to be a broadcaster via See-Me request and was granted a MCV (Multipoint Command Visualize) token. The See-Me feature is only performed in full-screen mode.

  • blank — At the time of the request the endpoint’s video was not broadcast, return, video, or part of the mixed-image, but it is a valid video source.

status conference x endpoint y field descriptions — page 2

Field

Description

Join Time

Time (in 24-hour notation) when the channel joined the conference.

Drop Time

The endpoint is idle if the first channel has a drop time.

Drop Reason

The reason for the channel’s disconnect:

  • 2-pri — This drop reason occurs when an administration error causes a mismatch in primary-secondary designation for a cascade link. This mismatch shows that both MCUs are administered as primaries (see Cascading for a description of primary-secondary compatibility).

  • 2-sec — This drop reason occurs when an administration error causes a mismatch in primary-secondary designation for a cascade link. This mismatch shows that both MCUs are administered as secondaries (see Cascading for a description of primary-secondary compatibility).

  • Agent — The reservation agent has caused the call to disconnect (for example, the agent has changed a connected dial-out destination number).

  • Bandwidth — mismatch between a call and the conference it attempted to join. For example, a 56-kbps call attempted to join a 64-kbps conference that does not permit rate adaptation.

  • BondHshake — Bonding handshake drop reason can be caused due to the following reasons: information channel parameter not supported or invalid, parameter negotiation terminated out of sequence, timer expired because of the secondary channels did not establish, or BONDing framing was not detected for one of the other channels.

  • Busy — This dial-out drop reason occurs when the MCU detects that the conferee’s terminal equipment is busy. This drop reason is detected by an ISDN cause value (for example, h0). See Dial-out for a description of CPTR usage.

  • 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.

  • No-ring — This dial-out drop reason occurs when the call has been up for 30 seconds and no ringing is detected.

  • 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.

  • Password — Either the user entered the wrong password or the audio add-on user did not enter it within the specified time period. Note that the audio add-on user gets one attempt to enter a correct password and inter-digit timing for each digit (that is, about 10 seconds between digits).

  • 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.

  • Resource — MCU could not provide resources (VC or MMI) when the call arrived or lost the resources during the call. This could be due to them being Out of Service, busied out by craft, or being used by system maintenance. This drop reason could also occur if the DS1/ MMI cable is disconnected. If there was a resource problem when the call arrived, it would get reorder (fast busy) and not get disconnected by the MCU.

  • 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.

  • System — An MCU restart (level 2) disconnected every call.

  • UIN-Inv — The user entered an invalid User Identification Number.

  • Unknown — The system could not determine the cause of the disconnect.

  • Wrong-num — This dial-out drop reason occurs when the MCU detects the wrong destination number was dialed. This drop reason is detected by MCU CPTR resources SDN cause value. See Dial-out for details.

  • UCC — controller intentionally disconnected the endpoint.

Drop Code

A detail code complementing the Drop Reason (see above). Additional bonding related information may be obtained from supplementary Bonding Drop Codes described above.

AC Num

Administered Connection Number - from 1 to 128. AC number can be used to further diagnose a problem by combining status conference information with status administered connection and data stored in the error and alarm logs.

Ports Trunk

The data endpoint that the channel is using.

Ports Video

The MMI port for the channel.

Ports Aud

If the endpoint type is not UCC, the VC audio encoder port (which is always paired to a decoder port) for the channel (only the first channel). Because only one audio encoder port is allocated per endpoint, it is together with the ESM data port in the endpoint’s channel 1 port slot position of the Port Aud/ESM column.

For UCC endpoint type, the channel 1 port slot position displays the allocated Call Classifier resource.

Ports ESM

The Expansion Service Module MMI data port. This field is always blank.

Ports Bonding

The MMI port used for Bonding for the channel.

Fr Err

Frame error counter. A circular hex counter (0-FF) to indicate the occurrence of framing errors.

status conference x endpoint y field descriptions — page 3, Conference Info

Field

Description

Conference Info

Applies mostly to full-screen conferences.

Broadcaster

Indicates the endpoint number that is the current broadcaster. Applies to full-screen and quad-screen presentation mode conferences.

  • Broadcast — a broadcast mode broadcaster.

  • Chair — the broadcaster was designated by the chair.

  • See-Me — the broadcaster is a result of MCV request from an endpoint.

  • Presenter — a presentation mode broadcaster.

  • Rollcall — the broadcaster was designated by the UCC via the Rollcall feature.

  • UCC — the broadcaster was designated by the UCC.

  • VAS — Voice Activated Switching broadcaster.

Next Broadcaster

Indicates the endpoint number that is selected to be the next broadcaster.

Return Vid

Indicates the endpoint number that is the current return video. The return video can be qualified with the following keywords:

  • blank — the return video is the previous broadcaster forced to be return video because of VAS, action by Chair, action by UCC, or endpoint MCV request. The broadcaster qualifier identifies which action forced this endpoint to become return video.

  • Autoscan — auto scan return video. This is true only when conference mode is broadcast with auto scan.

  • Browse — the return video was designated by the UCC via the Browse feature.

  • VAS — a Voice Activated Switching return video.

Next Return Vid

Indicates the endpoint number that is selected to be the next return video. MCU

status conference x endpoint y field descriptions — page 3, Mode Commands/Communication Modes

This is a collection of both incoming and outgoing bandwidth allocations for the multiplex. The Incoming data is the rate at which the MCU thinks the endpoint is communicating based on the Bit-rate Allocation Signal (BAS) codes received from the endpoint/codec and the capabilities the MCU has declared. The Outgoing data is the rate from the MCU toward the endpoint.

Field

Description

Conf

The desired conference operating mode. This may be different from the endpoint in (EPT-IN) or endpoint out (EPT-OUT) modes.

Cmd

labels for the various types of mode commands

Stat

Compatibility of conference mode and the incoming mode.

  • y — indicates mode compatibility

  • n — indicates that the modes are not compatible

EPT-IN

Communication modes coming in from an endpoint.

EPT-OUT

Communication modes sent out to an endpoint based on the number of channels connected and the capabilities of the endpoint.

XRate

One of the supported transfer rates. XRATE may be 64 when the endpoint is just dialing in, or in the event of problems. It implies that only one B-channel is being used.

Audio

Audio rate (kbps bandwidth) of the conference and the endpoint must be the same but not necessarily their mode. When the audio rate of the conference and the endpoint are different the endpoint’s audio will interwork but the endpoint’s video will be invalid. MCU may or may not send video to such an endpoint.

Other possible AUDIO mode values include neutral (neutralized I-channel) and Au-off, Frm (no audio signal) which never match conference mode and are not supported by MCU.

56/64

The 56/64 field is derestrict when operating at per-channel rates of either 64, 128, 192, 256, 320, 384, 512, 768, 1472, 1536, or 1920 kbps. It is restrict when operating at rates of either 56, 112, 168, 224, 280, 336, 448, or 672 kbps.

Note that if the conference is configured for N x 56-kbps operation, the endpoint may signal either via capabilities or modes that is operating at the proper rate. In such a case, even when we receive derestrict command which does not match the conference communication mode of restrict, if the capability indicates restrict (MISC capability has restrict displayed on Page 4) the STAT 56/64 is y to indicate 56/64 compatibility between the conference and the endpoint.

Video

The Video mode: H.261 (recommended), H.CTX (proprietary), H.CTX+ (proprietary), or SG4 (proprietary) indicate that video is on in the direction indicated; video-off when the video is off.

Mlp

Multi Layer Protocol data mode. When Data Mode is administered as any-mlp or ww-pcs, the MLP mode should be var-MLP. Other values will affect video status.

The MLP mode should be MLP-off when Data Mode is administered as none. Again, other values in this mode will affect video status.

H_Mlp

The High Speed MLP mode. The HMLP mode should be H-MLP-off. Other values in this mode will affect video status.

LSD

Low Speed Data mode.

The LSD mode should be LSD-off. Other values in this mode will affect video status.

HSD

High Speed Data mode.

The HSD mode should be HSD-off. Other values in this mode will affect video status.

CRYPT

Encryption mode.

The CRYPT mode should be encrypt-off. Other values in this mode will affect video status.

S/M

Single-/multi-channel interoperability mode.

6B-H0-comp indicates that the sender is interoperating multiple channels and a single channel (for example, 6B and H0).

Not-comp-6B-H0 indicates that the sender is not interoperating between 6B and H0. Normally this value is Not-comp-6B-H0. Other values in this mode will affect video status.

status conference endpoint field descriptions — page 3, Endpoint Misc Info

EPT MISC contains miscellaneous states and counters for an endpoint. The flags can be y or n. The counters start with initial value of 0x00, they increment to 0xff, and then wrap around to 0x01. AIM and VIS are BAS commands which can be sent as input (I) to MCU from an endpoint or as output (O) from MCU to an endpoint.

Field

Description

AIM

Audio Indicate Muted.

y on input (I) indicates that this endpoint has muted its audio. MCU will not VAS to an endpoint displaying mute indicate.

n on input indicates that this endpoint has not muted (only if endpoint audio mode is turned on).

y on output (O) indicates that every other endpoint in the conference has muted its audio (have sent AIM to MCU). MAC in turn tells this endpoint (by sending it AIM) that there is no audio output from MCU.

n on output indicates that there is an audio path open across the bridge.

VIS

Video Indicate Suppressed.

y on input (I) indicates that this endpoint has suppressed its video (indicated video is muted).

y on output (O) indicates that the MCU is not sending video to this endpoint because there is no video broadcaster (broadcaster has not joined or broadcaster’s video is not valid).

MIS

Multipoint Indicate Secondary-status.

This command is only sent as output (O) to an endpoint. n indicates that the endpoint is viewed as capable of being a valid source (although not necessarily at this moment).

y is correct for video. y indicates that MIS was sent to an endpoint and that this endpoint is viewed as a secondary endpoint. The endpoint is included in the audio portion of the conference but not the video portion. Video will not be sent.

MCV

Multipoint Command Visualize.

This command is only sent as input (I) from an endpoint. y indicates that an endpoint has requested to become a broadcaster. This is used during Still Frame Graphics and to force presentation mode.

TALK

Multipoint Command Visualize. This command is only sent as input (I) from an endpoint. y indicates that an endpoint has requested to become a broadcaster. This is used during Still Frame Graphics and to force “presentation” mode.

VRCV

y indicates if the endpoint is receiving video (MMCH is sending video to the endpoint). The VRCV counter indicates the number of times video was sent/not sent to this endpoint.

BCTK

Applies to single screen and quad-screen presentation mode conferences. y indicates that the endpoint is the video broadcast source. The BCTK counter indicates the number of times this endpoint was the video broadcast source.

RTTK

Applies to single screen conferences. y indicates that the endpoint is the return video source. The RTTK counter indicates the number of times this endpoint was the return video source.

BCLS

Applies to single screen and quad-screen presentation mode conferences. y indicates that the endpoint is watching the video of the broadcast source.

RTLS

Applies to single screen conferences. y indicates that the endpoint is watching the video of the return source.

HYPR

y indicates hyperactivity from an endpoint (MCU isolated endpoint from the MCU conference due to thrashing behavior) and affects endpoint’s status as a video source (for 5 seconds of hyperactivity timer). The HYPR counter indicates the number of times this endpoint was hyperactive.

DMUTE

y indicates that the decoder was muted by the VC board or the software in the MCU. VC board mutes the decoder when it loses MMI or endpoint framing is lost, when it receives an invalid audio code word, and when endpoint is hyperactive. The only time that the MCU software mutes the decoder of an endpoint is to mute every endpoint, other than the broadcaster, when a mode of a conference is broadcastw/scan (broadcast with auto scan). The DMUTE counter indicates the number of times this endpoint’s decoder was muted by the VC board.

VFMT

The video format applicable only to quad-screen conferences. Always n, indicating QCIF format.

H.261

y indicates video framing loss. The H.261 counter indicates the number of times the framing was lost.

status conference endpoint field descriptions — page 3, Frame Alignment Word Info

Frame Alignment Word (FAW) includes channel information for the communication paths labeled CHL 1 and 2. For 2B calls, both CHL 1 and 2 are used. For 1-channel calls (at rates of 112, 128, 168, 196, 224, 256, 280, 320, 336, 384, 768, 1472, 1536, and 1920 kbps), only CHL 1 is used. A-OUT, A-IN, M-FRM, MFA, and MFNare flags with values of y or n.

Field

Description

A-OUT

MCU has endpoint framing.

A-IN

Endpoint has MCU framing.

M-FRM

Multichannel frame alignment is present (alignment of both channels in 2B).

MFA

Multiframe alignment word is present (required in 2B call).

MFN

Multiframe numbering is present (required in 2B call).

FAS

Frame Alignment Signal (FAS) channel number (1 or 2). This number should match the column header.

MCUFAL

MCU Frame Alignment Loss (MCUFAL). A counter of the number of times the MCU indicates to the endpoint that it has lost endpoint FAW or multichannel synchronization (M-FRM). The MCU a-bit toggles when the MCU gains or loses endpoint multichannel synchronization. This counter starts with an initial value of 0x00, increments to 0xff, then wraps around to 0x01. The MCUFAL count is also shown in the Fr Err field.

FEFAL

Far End Frame Alignment Loss (FEFAL). A counter of the number of changes the MCU detects in the endpoint’s a-bit (A-OUT). The endpoint a-bit toggles when an endpoint gains or loses MCU framing. This counter starts with an initial value of 0x00, increments to 0xff, then wraps around to 0x01.

status conference endpoint field descriptions — page 4

Fields on this page only when an endpoint declares the specific capability. For example, if an endpoint does not declare the VID H.CTX capability, the H.CTX field does not display.

Field

Description

VID

Provides information about the type of video and frame rate the endpoint supports.

vfmt — does not display if the endpoint has no video capability. Every value is blank if there is an active call or if this is an audio-only endpoint. Otherwise, values for this field include:

  • FCIF — full CIF.

  • QCIF — quarter CIF. Support of CIF implies support of QCIF. In general, for larger screens, CIF displays sharper resolution video, which ZCIF is blocked, but may run at higher frame rates and less clear. The differences are less observable on very small displays.

  • cfps and qfps — maximum frame rate (frames/second) at which the endpoint can receive video for CIF and QCIF operating modes. CIF frame-rate values are 30 fps, 15 fps, 10 fps, and 7.4 fps. If the endpoint does not support CIF (that is, the vfmt field is QCIF), the cfps value should be blank.

  • da_sfg — indicates support for H.261 Still Frame Graphics transfers.

  • H.CTX, H.CTX+and SG4 — proprietary video format capabilities.

  • SG4_sfg — indicates support for SG4 Still Frame Graphics.

MISC

The restrict field is one way for an endpoint to indicate that it is operating at 56 kbps per channel. Another way is the 56/64 command mode with restrict. An endpoint on a 56-kbps conference must send one or both of the 2 indications that they are operating at 56 kbps before they become a video source in a 56-kbps conference. If they signal either way that they are operating at 56 kbps in a 64- or 384-kbps conference, they are an audio-only source, but the MCU continues to send Selected Communication Mode (SCM) toward them when possible.

A MISC capability of derestrict and a 56/64 command of derestrict together indicate that an endpoint is operating at 64 kbps. If either is restrict, the conference operates at 56 kbps. Other field values include:

  • dcomp — indicates support for WorldWorx PCS data compliance.

  • mbe — indicates support for Multi Byte Extension. MBE capability is used for the exchange of passwords, terminal names, and other special capabilities, such as, support of WorldWorx PCS specific features.

  • cic— Chair Indicate Capability. Indicates chair control capability.

XR

Transfer rate capabilities are statement about the speeds at which the endpoint can operate over the current connection and operate a Px64 Multiplex.

For a 384-kbps (H0) call, the endpoint sends its capabilities to indicate 384-kbps support, which displays as 384. On a 336-kbps call, the endpoint must signal 384-kbps support. If an endpoint does not indicate support for 384 kbps on a 384-/ 336-kbps conference, the MCU provides Audio Only Communications Mode (ACOM). For a 2B conference, the MCU sets the rate to 2x64, expecting the endpoints to do likewise (64x2 is displayed; if this is not displayed, there is no 64x2 capability). Endpoints may occasionally take 2x64 (or the current channel rate: 384, 768, 1472, 1536) out of their capability. This is Mode 0 forcing and is part of normal procedures. The MCU will provide AOCM if the endpoint does not signal support matching the configuration of the conference.

AUD

The audio fields are statements of the audio protocols that the endpoint supports. 711m and 711aare PCM (G.711) and support Mu and A-law, respectively, and at least one is required of endpoints. The g728 field indicates whether G.728 is supported (LB_CELP). This value depends upon the type of the endpoint and how that endpoint is currently configured. The g722_48 field indicates endpoint support for G.722 (7 kHz) at both 48 and 56 kbps. Therefore, g722_48 indicates that the endpoint supports G.722 audio at both rates. The g722_64 field indicates endpoint support for G.722 at 64 kbps in an unframed (not supported by the MCU) mode.

LSD

The LSD fields indicate the capabilities for Low Speed Data conferencing.

HSD

The HSD fields indicate the capabilities for High speed Data conferencing.

MLP

The MLP fields indicate the capabilities for Multi Layer Protocol Data capabilities.

HMLP

The HMLP fields indicate the conference’s capability for High Speed MLP data conferencing.

status conference endpoint field descriptions — page 5, Endpoint Call Status Information

This screen summarizes such call-related status as per-channel join counts, join/drop time, drop reason, drop code, and auxiliary bonding drop code. It also contains a drop code and software fields from the previous call. The data on the page is always retained. The Endpoint Call Status Information section groups together call-related fields. The Join Count field is described below, and other fields are described in the following field description tables.

Field

Description

Join Count

Shows the number of times this endpoint joined this conference during this conference session. This counter starts with 0, can increment to 64, and wraps around back to 1.

status conference endpoint field descriptions — page 6, Administered Connections

This screen summarizes information about the administered connections associated with this endpoint. This data can be viewed while the conference is active.

Field

Description

Dial-Out Number

The actual numbers that are dialed out by the administered connections for each channel in the call. Note that the dial Out #1 and #2 on page 1 of the forms display the DCP endpoint number. This is particularly useful with bonding dial-out calls.

Connection State

Indicates the current call state of the AC. The following are connection states associated with dial-out ACs:

  • enabled — transient in nature and indicates that an AC is about to enter the attempting to connect state.

  • disabled — this may mean one of three things:
    • The AC has reached an administered retry threshold, and all retries are stopped. Verify this by checking the error log and checking whether an error type of 9 is logged against the AC.

    • The AC was in a connected state and the far end disconnected.

    • The initial channel call has not yet connected. No dial out call attempt is made for the additional channel(s) until the initial channel has reached a connected state.

  • not scheduled — transient in nature and indicates that an AC is about to enter the attempting to connect state.

  • waiting to retry — the AC is inactive (sleeping) and waiting for the retry timer to expire. Once the timer expires, the AC sends a dial out call and enters the attempting to connect state. ACs in this state indicate that the dial out call has failed at least once.

  • attempting to connect — the AC is active on a call, but the call has not yet connected.

  • connected — the call associated with the AC has been answered and join cut-through to the conference.

Retry Count

Number of retries have been attempted for this AC during this join attempt. This field does not clear when the AC connects. This field clears when a new join attempt is made via a Redial feature. Note that this is different from the Join Count which counts the number of times the channel joined the conference during this conference session.

Failure Cause

ISDN or CPTR cause value (values lower than 0x7f) recorded when the last dial out call was dropped. Values above 0x7f are generated internally. The following table lists all possible failure cause values displayed by this field and its associated description. This value is logged in the error log and is displayed with display errors. Err Type is displayed as a decimal.

Status AC — Failure Cause Values

Failure Causes

Description

0x00 (0t0)

Not applicable

0x01 (0t1)

Incorrect destination address

0x02 (0t2)

Reason unknown

0x06 (0t6)

Reason unknown

0x10 (0t16)

Normal call clearing

0x11 (0t17)

Endpoint not available

0x12 (0t18)

ISDN timer expired

0x15 (0t21)

Reason unknown

0x12 (0t22)

Destination address changed

0x1C (0t28)

Bad destination or access denied

0x1D (0t29)

Access denied

0x1F (0t31)

Reason unknown

0x22 (0t34)

Trunks unavailable

0x26 (0t38)

Temporary or facility failure

0x29 (0t41)

Temporary or facility failure

0x2A (0t42)

Resources unavailable

0x2C (0t44)

Resources unavailable

0x32 (0t50)

Access denied

0x34 (0t52)

Access denied

0x36 (0t54)

Access denied

0x3A (0t58)

Resources unavailable

0x41 (0t65)

Required capability not implemented

0x42 (0t66)

Required capability not implemented

0x45 (0t69)

Required capability not implemented

0x51 (0t81)

ISDN protocol error

0x52 (0t82)

Required capability not implemented

0x58 (0t88)

Incorrect destination number

0x60 (0t96)

ISDN protocol error

0x61 (0t97)

ISDN protocol error

0x62 (0t98)

ISDN protocol error

0x64 (0t100)

ISDN protocol error

0x66 (0t102)

ISDN timer expired

0x7f (0t127)

Reason unknown

0xC2 (0t194)

Ring no answer

0xC8 (0t200)

Hi and dry – no feedback detected

0xC9 (0t201)

Cascade link administered wrong

0xCA (0t202)

CPTR not available to detect failure