TANDBERG 6000MXP - Manual (Page 166)

166
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
D 13887.08
MAY 2008
Understanding the Table Layout
20
TANDBERG 3000 MXP & 6000 MXP
REFERENCE USER GUIDE FOR SYSTEM INTEGRATORS
Status Information
D 13887.X3
AUGUST 2006
Conference (type = Idle / PointToPoint / PointToMultiSite / MultiSite ):
If type = Idle the following will be included:
Example:
*s Conference (type=Idle): /
*s/end
If type = PointToPoint the following will be included:
Calls:
CallRef [1..11]: 1..11
DuoVideo (status = None / Ready / On ):
If status = None / Ready the following will be included:
If status = On the following will be included:
CallRef [1..11]: 0..11
LoudestParticipant:
CallRef: 0..11
Example:
*s Conference (type=PointToPoint):
Calls:
CallRef 1: 1
DuoVideo (status=Ready): /
LoudestParticipant:
CallRef: 1
*s/end
If type = PointToMultiSite the following will be included:
Calls:
CallRef [1..11]: 1..11
DuoVideo (status = None / Ready / On ):
If status = None / Ready the following will be included:
Conference
Status Information
The status element listed
on this page
Indenting is used to keep track of the
levels. In the tables one light grey square
is used per level.
This condition
causes
this to appear
The / means logical OR.
The status element
listing starts here
Example showing
status of a real
case.
Which status elements
to show in a given
situation is context
dependent. The
context is reflected in
the attribute values.
Certain conditions will
cause some status
elements to be shown,
while other conditions
will produce other
status elements.
The conditions are
always shown on grey
background and start
with an
If statement.
TIP! For easy line-by-line parser, use the complete path formatter,
described in XACLI – Status-type commands – complete path formatting