Cisco TelePresence Server 7010 Specification sheet

Cisco TelePresence
TelePresence Server 8710
and 7010 2.2
Product user guide
D14842
June 2011

Cisco TelePresence Server Product User Guide Page 2 of 151
Contents
Introduction 5
System status 6
System status 7
Displaying cluster status for a master blade 10
Displaying cluster status for a slave blade 13
Displaying hardware health status 14
Network settings 15
Configuring network settings 16
DNS settings 20
Configuring IP routes settings 22
Configuring IP services 25
Configuring QoS settings 27
Configuring SSL certificates 29
Network connectivity testing 32
Configuration 33
System settings 34
Displaying and resetting system time 45
Upgrading and backing up the TelePresence Server 46
Shutting down and restarting the TelePresence Server 49
Changing the password 50
Back up and restore the configuration via FTP 51
Conferences 52
Displaying the conference list 53
Displaying conference status 55
Adding and updating conferences 61
Call endpoints to join a conference 66
Send a message to participants 67
Endpoints and endpoint groups 68
Endpoints 69

Cisco TelePresence Server Product User Guide Page 3 of 151
The list of endpoints 70
Display endpoint and group status 71
Add an endpoint 74
Add a legacy Cisco CTSendpoint 75
Add an endpoint group 76
Edit an endpoint's configuration 77
Configure advanced settings of endpoints and groups 82
View endpoint or endpoint group statistics 85
TelePresence Servers 87
Displaying the TelePresence Server list 88
Adding or updating controlled TelePresence Servers 89
Understanding the Conference controller 93
Understanding clustering 95
Comparing clustering with Conference controlling 97
Understanding screen licenses 99
Rooms 100
Displaying the rooms list 101
Displaying room status 102
Adding and configuring rooms 107
Starting a conference from a room 110
Room user instructions 113
Users 116
Displaying the user list 117
Adding and updating users 118
Logs 119
Working with the event logs 120
Event capture filter 121
Event display filter 122
Logging H.323 or SIPmessages 123
Logging using syslog 124

Cisco TelePresence Server Product User Guide Page 4 of 151
Working with Call Detail Records 126
Feedback receivers 128
Reference 129
Content channel support 130
Understanding how participants display in layout views 132
Ports allocation 139
Endpoint types 140
Endpoint interoperability 142
Checking for updates and getting help 143
Contact details and license information 144

Introduction
Cisco TelePresence Server Product User Guide Page 5 of 151
Introduction
Welcome to the Cisco TelePresence Server product user guide.
This document accompanies version 2.2 of the TelePresence Server software. This software is used on
the following Cisco TelePresence hardware:
nCisco TelePresence Server 7010
nCisco TelePresence Server MSE8710 blade
The contents of this document are organized in a similar way to the product's user interface, and
replicate the contents of its online help system.
There is a chapter for each of the main interface pages and each chapter's title page contains a list of
topics in the chapter.

Cisco TelePresence Server Product User Guide Page 6 of 151
System status
System status 7
Displaying cluster status for a master blade 10
Displaying cluster status for a slave blade 13
Displaying hardware health status 14

System status
Cisco TelePresence Server Product User Guide Page 7 of 151
System status
The Status page displays an overview of the TelePresence Server's status. To access this information,
go to Status.
Refer to the table below for details of the information displayed.
Field Field Description Usage tips
Model The specific TelePresence Server model.
Serial number The unique serial number of the
TelePresence Server.
You will need to provide this information
when speaking to customer support.
Software
version
The installed software version.
Build The build version of installed software.
Uptime The time since the last restart of the
TelePresence Server.
Host name The host name assigned to the
TelePresence Server.
IP address The IP address assigned to the
TelePresence Server.
IPv6 address The IPv6 address of this TelePresence
Server.
System log The system log displays the most recent
shutdown and upgrade events, with the
most recent shown first.
The log will display "unknown" if there has
been an unexpected reboot or power failure.
If this occurs frequently, report the issues to
customer support.
H.323
gatekeeper
status
How many TelePresence Servers are
registered to an H.323 gatekeeper, and
whether the registrations have been made
to the primary or an alternate gatekeeper.
This field is only displayed on the
Conference controller TelePresence Server
and on the master blade in a TelePresence
Server cluster.
SIP registrar
status
How many TelePresence Servers are
registered to a SIP registrar.
This field is only displayed on the
Conference controller TelePresence Server
and on the master blade in a TelePresence
Server cluster.
Conference
control
Whether this TelePresence Server is the
Conference controller.
Can be:
nConference controller - this system will
manage all conferences
nConferences will be managed by an
external controller
For more information, see Understanding the
conference controller.
System status

System status
Cisco TelePresence Server Product User Guide Page 8 of 151
Field Field Description Usage tips
Enhanced
font
Indicates whether the TelePresence Server
is using a TrueType font file to render text.
In use or Not in use, depending on whether
you have uploaded the font file. If it is Not in
use, the TelePresence Server falls back on
the default text rendering method.
Field Field description Usage tips
TelePresence
Server
activation
Whether or not the unit is enabled. The TelePresence Server will not operate
without activation. This feature and key are
installed before shipping.
Encryption Whether or not encryption is enabled. The encryption feature key allows encrypted
conferences and HTTPS web management
on this blade. Feature keys are installed in
the Configuration > Upgrade page. See
Upgrading and backing up the TelePresence
Server.
Third party
interop
This feature allows the TelePresence
Server to interoperate with third party multi-
screen endpoints.
It also activates the grouped endpoints and
rooms features.
Calls to general third party endpoints will
work without this key. It is required to support
multi-screen third party endpoints, such as
the Polycom RPX, endpoint groups, and the
rooms feature.
This field is only displayed if you have the
appropriate key installed. Feature keys are
installed in the Configuration > Upgrade
page. See Upgrading and backing up the
TelePresence Server.
Screen
licenses
The number of screen licenses in use
across all active conferences. The total
number of screen licenses may be less than
the total number that the TelePresence
Server can support.
You need to install a screen license key to
enable screen licenses. For more
information about licenses, see
Understanding screen licenses.
Screen licenses are shared between the
Conference controller TelePresence Server
and the TelePresence Servers it controls.
For a Conference controller TelePresence
Server, the value shown is the total number
of screen licenses for all controlled
TelePresence Servers.
Activated features
Field Field description Usage tips
Active
TelePresence
Servers
If this TelePresence Server is the
Conference controller then this field shows
the number of TelePresence Servers
(including this system) that are being
controlled by this TelePresence Server.
A TelePresence Server that is not the
Conference controller will show 0 here.
For more information, see Understanding the
Conference controller.
Conference status

System status
Cisco TelePresence Server Product User Guide Page 9 of 151
Field Field description Usage tips
Active
conferences
The number of active conferences that this
TelePresence Server is controlling.
If this is the Conference controller, then this
is the number of active conferences across
all managed TelePresence Servers. A
TelePresence Server that is not the
Conference controller will show 0 here.
For more information, see Understanding the
Conference controller.
Active
endpoints
The number of endpoints (of all types) that
are in active conferences controlled by this
TelePresence Server.
If this is the Conference controller, then this
is the number of endpoints in active
conferences across all managed
TelePresence Servers. A TelePresence
Server that is not the Conference controller
will show 0 here.
For more information, see Understanding the
Conference controller.
Video ports The number of video ports in use. The
second number is the maximum on this
TelePresence Server.
If this is the Conference controller, the
numbers are those across all managed
TelePresence Servers controlled by this
TelePresence Server. A TelePresence
Server that is not the Conference controller
will show 0 here.
For more information, see Understanding the
Conference controller and Content channel
video support.
Audio ports The number of audio-only ports in use. The
second number is the maximum on this
TelePresence Server.
Content ports The number of content channel ports in use.
The second number is the maximum on this
TelePresence Server.
Field Field description Usage tips
The system log displays the most recent
shutdown and upgrade events, with the
most recent shown first.
The log will display "unknown" if there has
been an unexpected reboot or power failure.
If this occurs frequently, report the issues to
customer support.
System log
Field Field description Usage tips
Diagnostic
information
Diagnostic files are provided in .zip archive
format that contain a text document. To
download a diagnostic file, click Download
file.
Diagnostic information is provided to aid in
troubleshooting problems that may occur
with the TelePresence Server.
In the event of an issue with the
TelePresence Server, the support team may
ask you for these diagnostic files.
Network
capture file
To download a network capture, click
Download file.
The network capture file is only available on
the master blade in a TelePresence Server
cluster.
System logs To download the logs, click Download file. An archive containing several useful log files.
Diagnostic information

System status
Cisco TelePresence Server Product User Guide Page 10 of 151
Displaying cluster status for a master blade
To display cluster status, go to Status > Cluster.
Cluster status is only available for blades that are configured on the Cisco TelePresence Supervisor
MSE8050 to be part of a cluster. For more information about clustering, refer to Understanding
clustering.
The table below describes the Status > Cluster page that displays for the master blade in a cluster. For
details about slave blades, see Displaying cluster status for a slave blade.
Note: The Conference controlling arrangement is not the same as the clustering arrangement of multiple
TelePresence Servers. For more information, see Comparing clustering with Conference controlling.
Field Field description Usage tips
Slot The number of the slot in the Cisco TelePresence
MSE8000 chassis that corresponds to this row in the
table.
To configure a blade as a master or a
slave in a cluster, log in to the
Supervisor.
IP The IP address of the blade in this slot, or Master
blade (if this is the master).
Cluster status

System status
Cisco TelePresence Server Product User Guide Page 11 of 151
Field Field description Usage tips
Status The status of the master blade can only be OK which
means that this blade is operating correctly in the
cluster.
Possible statuses for a slave blade are:
nOK: The master and slave are communicating
correctly.
nOK (last seen <number> seconds ago): The
master has lost contact with the slave. The slave
will restart itself and in this way it will rejoin the
cluster. Wait a few minutes and then refresh the
Status > Cluster page.
nStill starting up: The slave blade is in the process
of starting up. Wait a few minutes and then refresh
the Status > Cluster page.
nLost contact <number> secs ago: The master has
lost contact with the slave. The slave will restart
itself and in this way it will rejoin the cluster. Wait a
few minutes and then refresh the Status > Cluster
page.
nCluster support not enabled: There is no Cluster
support feature key on this blade.
nFailed, version mismatch: All blades in the cluster
must be running the same version of software.
This status message indicates that this blade is
running different software to the master blade. This
blade is not part of the cluster. Update all blades in
the cluster to the same version of software.
nBlade not configured as slave: The Supervisor has
told the master that the blade is a slave, but the
blade is not a slave. Possibly the slave blade was
replaced.
nBlade incorrect type: Possibly the slave blade was
replaced with a different blade type after the
cluster was configured.
If the status of the slave is OK, it is
currently functioning in the cluster. For
any of the other statuses, the slave
blade is not currently functioning as
part of the cluster.
If a slave blade has a problem that
causes it to no longer be part of the
cluster, the cluster can continue to
operate without that slave. For
example, in a cluster of three blades if
one slave fails, the master and the
other slave can continue to operate
and accept calls. There will just be
fewer video ports available. Similarly,
in a cluster of two blades, if the slave
fails, the master continues to operate.
If a slave blade fails, participants in
conferences will not be disconnected:
if there are sufficient resources on
another blade in the cluster, they will
continue to receive audio and video.
In the worst case, the video will
disappear, but the audio will continue
because all audio is processed by the
master blade.
If the master loses contact with a
slave, the slave will automatically
restart itself. In this way, it can rejoin
the cluster.
Media
processing
load
An overview of the current media loading of each
blade in the cluster. The load may increase during
periods of peak conference use.
Conferences are distributed between
the blades in the cluster. The loads on
the blades depend on the number of
conferences running on each blade
and the sizes of those conferences.
On a slave blade, the audio load will
always be zero: the master is
responsible for all the audio.

System status
Cisco TelePresence Server Product User Guide Page 12 of 151
Field Field description Usage tips
Screen
licenses
The number of screen licenses on each blade in this
cluster.
All screen licenses on slave blades
are controlled by the master blade.
Depending on how you use the
blades in the MSE chassis, you might
want to allocate all screen licenses to
the slot that houses the master blade
or you might distribute them between
the slots in the cluster. It does not
matter to the cluster how you have
allocated the screen licenses; in any
case, the master controls all screen
licenses and even if a blade has failed
in the cluster, the master will continue
to have access to any screen licenses
allocated to the failed blade's slot.

System status
Cisco TelePresence Server Product User Guide Page 13 of 151
Displaying cluster status for a slave blade
To display cluster status, go to Status > Cluster. When you look at the Status > Cluster page on a
slave blade, it shows the status of the master blade.
The table below describes the Status > Cluster page that displays for slave blades in a cluster. For
information about the master blade, see Displaying cluster status for a master blade.
Slave blades have restricted user interfaces; not all settings are available. You must configure the
cluster from the master blade.
Note: The Conference controlling arrangement is not the same as the clustering arrangement of multiple
TelePresence Servers. For more information, see Comparing clustering with Conference controlling.
Field Field description Usage tips
Status Possible statuses for the master blade are:
nStill starting up: the master blade is in the
process of starting up. Wait a few minutes
and then refresh the Status > Cluster
page.
nOK: The master and slave are
communicating correctly.
nLost contact: The slave blade has lost
contact with the master blade. This status
will only be momentarily visible because
the slave blade will quickly restart itself in
this case.
If a slave blade loses contact with the master
blade, it will restart itself. This is the only way
that the slave blade can correctly rejoin the
cluster.
A common reason for a slave blade to lose
contact with the master is because the
master blade has restarted.
Last seen This field is only visible if the master has not
been seen for 11 seconds. The slave blade
will automatically restart itself very soon
after it loses contact with the master.
IP address The IP address of the master blade.
Cluster status

System status
Cisco TelePresence Server Product User Guide Page 14 of 151
Displaying hardware health status
The Health status page (Status>Health status) displays information about the hardware components
of the TelePresence Server.
Note: The Worst status seen conditions are those since the last time the TelePresence Server was
restarted.
To reset these values, click Clear. Refer to the table below for assistance in interpreting the information
displayed.
Field Field description Usage tips
Voltages
RTC battery
Displays two possible states:
nOK
nOut of spec
States indicate both Current status and
Worst status seen conditions.
The states indicate the following:
nOK – component is functioning properly
nOut of spec – Check with your support
provider; component might require service
If the Worst status seen column displays Out
of spec, but Current status is OK, monitor the
status regularly to verify that it was only a
temporary condition.
Temperature Displays three possible states:
nOK
nOut of spec
nCritical
States indicate both Current status and
Worst status seen conditions.
The states indicate the following:
nOK – temperature of the TelePresence
Server is within the appropriate range
nOut of spec – Check the ambient
temperature (should be less than 34
degrees Celsius) and verify that the air
vents are not blocked
nCritical – temperature of TelePresence
Server is too high. An error also appears in
the event log indicating that the system will
shutdown in 60 seconds if the condition
persists
If the Worst status seen column displays
Out of spec, but Current status is OK
monitor the status regularly to verify that it
was only a temporary condition.
Device health details

Cisco TelePresence Server Product User Guide Page 15 of 151
Network settings
Configuring network settings 16
DNS settings 20
Configuring IP routes settings 22
Configuring IP services 25
Configuring QoS settings 27
Configuring SSL certificates 29
Network connectivity testing 32

Network settings
Cisco TelePresence Server Product User Guide Page 16 of 151
Configuring network settings
To configure the network settings on the TelePresence Server and check the network status, go to
Network>Port A settings.
The TelePresence Server has two Ethernet interfaces, Port A and Port B. However, Port B is for future
expansion and cannot be enabled in the current release of the TelePresence Server. Therefore, although
there is a Network>Port B settings page, you cannot change any settings for Port B.
On this page:
nIP configuration settings
nIP status
nEthernet configuration
nEthernet status
IP configuration settings
These settings determine the IP configuration for the appropriate Ethernet port of the TelePresence
Server. When you have finished, click Update IP configuration and then reboot the TelePresence
Server.
Field Field description Usage tips
IP
configuration
Specifies whether the port should be
configured manually or automatically. If set
to Automatic via DHCP the TelePresence
Server obtains its own IP address for this
port automatically via DHCP (Dynamic Host
Configuration Protocol). If set to Manual the
TelePresence Server will use the values
that you specify in the Manual configuration
fields below.
Click Renew DHCP to request a new IP
address if you have selected automatic
configuration.
Port A should never be disabled because it
is the primary interface of the TelePresence
Server.
IP address The dot-separated IPv4 address for this
port, for example 192.168.4.45.
You only need to specify this option if you
have chosen Manual IP configuration, as
described above.
For Port A, if the IP configuration setting is set
to Automatic by DHCP this setting will be
ignored.
Subnet mask The subnet mask required for the IP
address you wish to use, for example
255.255.255.0
Default
gateway
The IP address of the default gateway on
this subnet, for example 192.168.4.1
IPv4 configuration

Network settings
Cisco TelePresence Server Product User Guide Page 17 of 151
Field Field description Usage tips
IP
configuration
Select Disabled,Automatic via
SLAAC/DHCPv6 or Manual.
If you select Manual, you must also supply
the IPv6 address, prefix length and default
gateway.
If you select Automatic via SLAAC/DHCPv6,
the TelePresence Server automatically gets
an IPv6 address. It uses SLAAC, Stateful
DHCPv6 or Stateless DHCPv6 as indicated
by the ICMPv6 Router Advertisement (RA)
messages (see Automatic IPv6 address
preferences below).
Disable IPv6 on the port if the network does
not support IPv6.
IP address If you chose Manual configuration, supply
the IPv6 address in CIDR format. Enclose
the address in square brackets, for example
[fe80::202:b3ff:fe1e:8329], in the
user interface.
You only need to enter an address if you
chose Manual IP configuration. If you chose
Automatic via SLAAC/DHCPv6, a manually
entered setting is ignored.
Prefix length If you chose Manual configuration, supply
the prefix length.
The prefix length is the (decimal) number of
bits that are fixed for this address.
Default
gateway
(Optional) Supply the IPv6 address of the
default gateway on this subnet.
The address may be global or link-local
IPv6 configuration
IP status
The IP status section shows the current IP settings for this Ethernet port of the TelePresence Server, as
follows, whether they were automatically or manually configured.
IPv4 settings:
nDHCP
nIP address
nSubnet mask
nDefault gateway
IPv6 settings:
nDHCPv6
nIPv6 address
nIPv6 default gateway
nIPv6 link-local address
Ethernet configuration
Configure the Ethernet settings for this port of the TelePresence Server, and then click Update Ethernet
configuration.

Network settings
Cisco TelePresence Server Product User Guide Page 18 of 151
Field Field description Usage tips
Ethernet
settings
Select Automatic or Manual.
If you select Manual, you must also supply
the speed and duplex settings. Select
Automatic if you want this Ethernet port to
automatically negotiate its Ethernet settings
with the connected device.
It is important that the devices at either end of
the Ethernet connection have the same
settings. That is, configure both devices to
use automatic negotiation, or configure them
both with the same fixed speed and duplex
settings.
Speed Set the connection's speed to 10 Mbit/s or
100 Mbit/s. Select automatic negotiation if
you require a connection speed of 1000
Mbit/s.
The connection speed setting must be the
same for the ports at both ends of this
connection.
Duplex Set the connection's duplex mode to Full
duplex or Half duplex.
The connection duplex setting must be the
same for the ports at both ends of this
connection.
Full duplex mode allows simultaneous
bidirectional transmission, while half duplex
mode only allows bidirectional transmission
that is not simultaneous.
Ethernet configuration

Network settings
Cisco TelePresence Server Product User Guide Page 19 of 151
Ethernet status
Field Field description Usage tips
Link status Indicates whether or not this Ethernet link is
connected.
Speed The speed (10/100/1000 Mbit/s) of this
Ethernet link.
This value is negotiated with the device to
which this port is connected or based on
your manual configuration.
Duplex The duplex mode (Full duplex or Half
duplex) of the network connection to this
port.
This value is negotiated with the device to
which this port is connected or based on
your Manual configuration selected above.
MAC address The fixed hardware MAC (Media Access
Control) address of this port.
You can not change this value, it is for
information only.
Packets sent The total number of packets sent from this
port (all TCP and UDP traffic).
This information can help you confirm that
the TelePresence Server is transmitting
packets into the network.
Packets
received
The total number of packets received by this
port (all TCP and UDP traffic).
This information can help you confirm that
the TelePresence Server is receiving
packets from the network.
Statistics: More statistics for this port.
nMulticast packets sent
nMulticast packets received
nTotal bytes sent
nTotal bytes received
nReceive queue drops
nCollisions
nTransmit errors
nReceive errors
This information can assist you with
diagnosing network issues, such as link
speed and duplex negotiation issues.
Ethernet status

Network settings
Cisco TelePresence Server Product User Guide Page 20 of 151
DNS settings
Click Network > DNS to check and change the DNS settings of the TelePresence Server.
Click Update DNS configuration to apply the new settings.
Field Field description Usage tips
DNS
configuration
Select how you want the TelePresence
Server to get its name server address.
For example, if you select Via Port A
DHCPv6, the device will automatically get a
name server address using DHCP over the
IPv6 network connected to Ethernet port A.
If you select Manual, you must provide a
name server address. You may also want to
provide a secondary name server or
domain name (DNS suffix).
Note:Although Port Bappears in this
dropdown, you should not select it because
it is disabled in this version of the software.
The TelePresence Server does not allow you
to automatically configure the name server
address if you have set a static IPaddress on
the selected interface.
For example, if you select Via Port
ADHCPv4 here but have also selected
Manual in the IPv4 configuration section of
the Port Asettings page, the TelePresence
Server will warn you that no DNS servers will
be configured.
Host name Specifies a name for the TelePresence
Server.
Depending on your network configuration,
you may be able to use this host name to
communicate with the TelePresence Server,
without needing to know its IP address.
Name server The IP address of the name server. Required if you select the Manual name
server preference.
Secondary
name server
Identifies an optional second name server. (Optional) The TelePresence Server queries
the secondary DNS server if the primary is
unavailable. If the first server is available but
does not know an address, the TelePresence
Server does not query the secondary DNS
server.
Domain name
(DNS suffix)
Specifies an optional suffix to add when
performing DNS lookups.
Add a suffix if you want to use unqualified
host names to refer to devices (instead of
using IP addresses).
For example, if the domain name (suffix) is
set to cisco.com, then a request to the name
server to look up the IP address of host
endpoint will actually look up
endpoint.cisco.com.
DNS settings
View DNS status
Use the DNS status fields to verify the current DNS settings for the TelePresence Server, including:
nHost name
nName server