170
D14049.07
March 2010
Grey Headline
(continued)
TANDBERG
VIDEO COMMUNICATION SERVER
ADMINISTRATOR GUIDE
Introduction
Overview and
status
System
configuration
VCS
configuration
Zones and
neighbors
Clustering and
peers
Call
processing
Bandwidth
control
Firewall
traversal
Appendices
Applications
Maintenance
Incident reporting
The incident reporting feature of the VCS automatically saves information about critical system
issues such as application failures. You can:
•
view the reports
from the VCS web interface
•
download and send the reports manually
to TANDBERG (usually at the request of TANDBERG
customer support)
•
configure the VCS to
send the reports automatically
to TANDBERG.
The information contained in these reports can then be used by TANDBERG customer support
to diagnose the cause of the failures. All information gathered during this process will be held in
confidence and used by TANDBERG personnel for the sole purpose of issue diagnosis and problem
resolution.
This feature is only intended for use at the request of TANDBERG customer support in exceptional
situations, and is off by default.
Warning: privacy-protected personal data
!
IN NO EVENT SHOULD PRIVACY-PROTECTED PERSONAL DATA BE INCLUDED IN ANY
REPORTS TO TANDBERG. Privacy-Protected Personal Data means any information about
persons or entities that the Customer receives or derives in any manner from any source
that contains any personal information about prospective, former, and existing customers,
employees or any other person or entity. Privacy-Protected Personal Data includes, without
limitation, names, addresses, telephone numbers, electronic addresses, social security numbers,
credit card numbers, customer proprietary network information (as defined under 47 U.S.C. § 222
and its implementing regulations), IP addresses or other handset identifiers, account information,
credit information, demographic information, and any other information that, either alone or in
combination with other data, could provide information specific to a particular person.
PLEASE BE SURE THAT PRIVACY-PROTECTED PERSONAL DATA IS NOT SENT TO TANDBERG WHEN
THE TANDBERG VCS IS CONFIGURED TO AUTOMATICALLY SEND REPORTS.
IF DISCLOSURE OF SUCH INFORMATION CANNOT BE PREVENTED, PLEASE DO NOT USE THE
AUTOMATIC CONFIGURATION FEATURE. Instead, copy the data from the
Incident detail
page and
paste it into a text file. You can then edit out any sensitive information before forwarding the file
on to TANDBERG customer support. See the section
Sending incident reports manually
for more
information.
Overview
The information contained in the report is:
Time
the date and time at which the incident occurred.
Version
the version of software running when the incident occurred.
Build
the internal build number for the software.
Name
the name of the software.
System
the configured system name.
Serial number
the hardware serial number.
Process ID
the process ID the VCS application had when the incident occurred.
Release
a True/False flag indicating if this is release build (rather than a
development build).
User name
the name of the person that built this software. This is blank for release
builds.
Stack
the trace of the thread of execution that caused the incident.
Debug information
a full trace of the application call stack for all threads and the values of
the registers.
!
For each call stack the
Debug information
will include the contents of variables which may
contain some sensitive information, for example alias values and IP addresses. If your
deployment is such that this information could contain information specific to a particular
person, please read the
Warning: privacy-protected personal data
section (left) before you decide
whether to enable automatic incident reporting.
If you choose not to enable automatic incident reporting, you can still manually send the reports
to TANDBERG customer support. See the
Sending incident reports manually
section for more
information.
What information does the report contain?
