Cisco TelePresence Server 7010 Reference guide

Cisco TelePresence
Server 7010 and MSE 8710
in Remotely Managed
Mode
Printable Help
4.0
D15072
April 2014
Cisco TelePresence Server 7010 and MSE 8710 in Remotely Managed Mode Printable Help (4.0) Page 1 of 92

Contents
Introduction 4
Logging into the web interface 4
Failing to log into the web interface 4
System status 6
Displaying system status 7
Displaying hardware health status 10
Displaying cluster status on a master TelePresence Server 11
Displaying cluster status on a slave TelePresence Server 14
Network settings 15
Configuring network settings 16
Configuring DNS settings 20
Configuring IP routes settings 21
Configuring IP services 23
Enabling TCP/UDPservices 23
Defining the ephemeral port range 23
Resetting to the default configuration 23
Configuring QoS settings 25
Configuring SSL certificates 27
Testing network connectivity 30
Viewing network statistics (netstat) 31
Configuration 32
Configuring system settings 33
Configuring H.323 settings 34
Configuring SIP settings 35
Operation mode 37
Displaying and resetting system time 38
Backing up and upgrading the TelePresence Server 39
Shutting down and restarting the TelePresence Server 43
Changing the administrator password 44
Backing up and restoring the configuration via FTP 45
Conferences 46
Displaying the conference list 47
Displaying conference status 48
Displaying endpoint and group status 53
Viewing endpoint or endpoint group statistics 56
Users 59
Displaying the user list 60
Adding and updating users 61
Logs 63
Working with the event logs 64
Event capture filter 65
Event display filter 66
Logging protocols messages 67
Logging using syslog 68
Cisco TelePresence Server 7010 and MSE 8710 in Remotely Managed Mode Printable Help (4.0) Page 2 of 92

Working with Call Detail Records 70
APIclients 72
Feedback receivers 73
Reference 74
Content channel support 75
Understanding how participants display in layout views 76
Endpoint types 81
Endpoint interoperability 83
Understanding clustering 84
Understanding your TelePresence Server's conferencing capacity 86
License keys and screen licenses 86
Operation modes 87
Call limits 88
Technical support 91
Cisco TelePresence Server 7010 and MSE 8710 in Remotely Managed Mode Printable Help (4.0) Page 3 of 92

Introduction
This document contains the text of the online help for the Cisco TelePresence Server version 4.0 web user
interface. It is provided so that the help text can be viewed or printed as a single document.
This document accompanies version 4.0 of the TelePresence Server software when operating in remotely
managed mode. 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.
Further information
See the online help for details of software licenses relating to this product.
Logging into the web interface
Why do I need to log in to the web interface?
The TelePresence Server restricts user access by holding a set of pre-configured accounts and denying
access to anyone who does not have an account. Each account has a username and password that enables
the account owner to gain access to their associated privileges.
There are three privilege levels for user accounts:
nAdministrator: users with this privilege level may access all functionality
nAPIaccess: users with this privilege level can only access the API, not the web interface
nNone: users with this privilege level may not access the TelePresence Server. This level is used to disable
accounts.
Tasks
Logging in to the web interface:
1. Enter the host name or IP address of the TelePresence Server into the address bar of a web browser.
The log in page displays.
2. Enter your assigned Username and Password.
3. Click OK.
Failing to log into the web interface
Why am Iseeing the Access denied page?
You have not been able to log in for one of the following reasons:
Cisco TelePresence Server 7010 and MSE 8710 in Remotely Managed Mode Printable Help (4.0) Page 4 of 92
Introduction
Logging into the web interface

nInvalid username/password: you have typed the incorrect username and/or password.
nNo free sessions: the maximum number of sessions allowed simultaneously on the TelePresence Server
has been reached.
nYour IP address does not match that of the browser cookie you supplied: try deleting your cookies
and log in again
nYou do not have access rights to view this page: you do not have the access rights necessary to view
the page that you attempted to see
nPage expired: the Change password page can expire if the TelePresence Server detects that the user
who requested to change password, may not actually be the user submitting the change password request.
(This may happen if you use a new browser tab to submit the request.)
Cisco TelePresence Server 7010 and MSE 8710 in Remotely Managed Mode Printable Help (4.0) Page 5 of 92
Introduction
Failing to log into the web interface

System status
Displaying system status 7
Displaying hardware health status 10
Displaying cluster status on a master TelePresence Server 11
Displaying cluster status on a slave TelePresence Server 14
Cisco TelePresence Server 7010 and MSE 8710 in Remotely Managed Mode Printable Help (4.0) Page 6 of 92

Displaying system status
The Status page displays an overview of the TelePresence Server's status. To access this information, go to
Status.
Note:Your TelePresence Server must be controlled by an external application. The external application, for
example Cisco TelePresence Conductor, uses the TelePresence Server's APIto create and manage
conferences and participants. Refer to the Cisco TelePresence Server API documentation for more
information.
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.
H.323
gatekeeper
status
Whether the TelePresence Server is
registered to an H.323 gatekeeper, and
whether the registration has been made to
the primary or an alternate gatekeeper.
This field is only displayed on the master blade
in a TelePresence Server cluster.
SIP registrar
status
Whether the TelePresence Server is
registered to a SIP registrar.
This field is only displayed on the master blade
in a TelePresence Server cluster.
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.
Operation
Mode
Indicates whether the TelePresence Server is
operating in locally managed or remotely
managed mode.
Table 1: System status
Cisco TelePresence Server 7010 and MSE 8710 in Remotely Managed Mode Printable Help (4.0) Page 7 of 92
System status

Field Field description Usage tips
TelePresence
Server 8710
activation or
TelePresence
Server 7010
activation
Whether or not the unit is enabled. The TelePresence Server will not operate
without activation. This feature key is installed
before shipping.
Encryption Whether or not encryption is enabled. The encryption feature key allows encrypted
conferences and HTTPS web management on
this TelePresence Server. Feature keys are
installed in the Configuration > Upgrade
page. See Upgrading and backing up the
TelePresence Server.
Cluster
support
This feature allows MSE8710 blades
configured on the same Cisco TelePresence
MSE8000 chassis to be linked together to
behave as a single unit.
This key does not apply to the 7010 platform,
as these appliances cannot be clustered.
Up to four blades can form a cluster. See
Understanding clustering.
If you want to cluster blades, each blade must
have the Cluster support feature key installed.
Feature keys are installed on the
Configuration > Upgrade page. See
Upgrading and backing up the TelePresence
Server
Screen
licenses
The number of screen licenses allocated to
the TelePresence Server. In the case of a
cluster, this is the number of screen licenses
allocated to the whole cluster.
The number of allocated screen licenses can
be lower than the maximum that the system
can support.
You need to install a screen license key to
enable screen licenses. For more information
about licenses, see Understanding your
TelePresence Server's conferencing capacity
[p.86].
Table 2: Feature keys
Field Field description Usage tips
Active
conferences
The number of active conferences on this
TelePresence Server.
A conference is active if it has participants.
Active
participants
The number of participants (of all types) that
are currently in conferences on this
TelePresence Server.
Previous
participants
The number of participants who were
previously participating in a conference (since
the last time the TelePresence Server
restarted).
Table 3: Conference status
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 or
after an upgrade. If this occurs frequently,
report the issues to customer support.
Table 4: System log
Cisco TelePresence Server 7010 and MSE 8710 in Remotely Managed Mode Printable Help (4.0) Page 8 of 92
System status

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 your
TelePresence Server, provide this file to the
Cisco Technical Assistance Center (TAC) who
may wish to perform further diagnostic tests.
Network
capture file
To download a network capture, click
Download file.
There is also a link to Delete network capture
which you should only click when your
TelePresence Server is operating normally
again.
System logs To download the logs, click Download file. An archive containing several useful log files.
Table 5: Diagnostic information
Cisco TelePresence Server 7010 and MSE 8710 in Remotely Managed Mode Printable Help (4.0) Page 9 of 92
System status

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
Fans
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.
Note: Fans field does not display on 8710 as it
does not have fans.
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.
Table 6: Device health details
Cisco TelePresence Server 7010 and MSE 8710 in Remotely Managed Mode Printable Help (4.0) Page 10 of 92
System status

Displaying cluster status on a master
TelePresence Server
To display cluster status, go to Status > Cluster.
Note: This cluster related page is only available if your TelePresence Server is in a 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 TelePresence Server in a
cluster. For details about slave blades, see Displaying cluster status on a slave TelePresence Server [p.14].
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 addresses of the slave blades, or Master blade
in the case of the master.
You can click the IPaddress to go to the
slave's cluster page.
Table 7: Cluster status
Cisco TelePresence Server 7010 and MSE 8710 in Remotely Managed Mode Printable Help (4.0) Page 11 of 92
System status

Field Field description Usage tips
Status The status of the master can only be OK which means
that the master is operating correctly in the cluster.
The following options are possible for slave status:
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 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 TelePresence Server.
nFailed, version mismatch: All TelePresence Servers
in the cluster must be running the same version of
software. This status message indicates that this
slave is running different software to the master, and
hence the TelePresence Server is not part of the
cluster. Update all units in the cluster to the same
version of the 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 is
not currently functioning as part of the
cluster.
If a slave has a problem that causes it to
no longer be part of the cluster, the
cluster can continue to operate without
the slave.
If a slave fails, participants in
conferences will not be disconnected: if
there are sufficient resources in the
cluster, they will continue to receive
audio and video. In the worst case,
participants may lose video. The audio
will continue because all audio is
processed by the master.
If the master loses contact with a slave,
the slave will automatically restart itself.
In this way, it can rejoin the cluster.
Software
version
The software version on each TelePresence Server in
the cluster.
Media
processing
load
An overview of the current media loading of each
TelePresence Server in the cluster. The load may
increase during periods of peak conference use.
Conferences are distributed between
the TelePresence Servers in the cluster.
The load on each depends on the
number and size of the conferences
running on them.
On a slave blade, the audio load will
always be zero: the master is
responsible for all the audio.
Table 7: Cluster status (continued)
Cisco TelePresence Server 7010 and MSE 8710 in Remotely Managed Mode Printable Help (4.0) Page 12 of 92
System status

Field Field description Usage tips
Screen
licenses
The number of screen licenses on each TelePresence
Server in this cluster.
All screen licenses on slaves are
controlled by the master. 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
allocate the screen licenses—the
master controls all screen licenses and
even if a slave fails, the master will
continue to have access to any screen
licenses allocated to the failed slave.
Table 7: Cluster status (continued)
Cisco TelePresence Server 7010 and MSE 8710 in Remotely Managed Mode Printable Help (4.0) Page 13 of 92
System status

Displaying cluster status on a slave
TelePresence Server
To display cluster status, go to Status > Cluster. When you look at the Status > Cluster page on a slave
TelePresence Server, it shows the status of the master.
Note: This cluster related page is only available if your TelePresence Server is in a cluster.
The table below describes the Status > Cluster page that displays for slave TelePresence Servers in a
cluster. For information about the master TelePresence Server, see Displaying cluster status on a master
TelePresence Server [p.11].
Slave units have restricted user interfaces; not all settings are available. You must configure the cluster from
the Cisco TelePresence Supervisor MSE 8050.
Field Field description Usage tips
Status Possible statuses for the master unit are:
nStill starting up: the master 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 has lost contact with
the master. This status will only be
momentarily visible because the slave will
quickly restart itself in this case.
If a slave TelePresence Server loses contact
with the master, it will restart itself. This is the
only way that the slave can correctly rejoin the
cluster.
A common reason for a slave to lose contact
with the master is because the master has
restarted.
Last seen This field is only visible if the master has not
been seen for up to 11 seconds. The slave
will automatically restart itself very soon after
it loses contact with the master.
IP address The IP address of the master TelePresence
Server.
Table 8: Cluster status
Cisco TelePresence Server 7010 and MSE 8710 in Remotely Managed Mode Printable Help (4.0) Page 14 of 92
System status

Network settings
Configuring network settings 16
Configuring DNS settings 20
Configuring IP routes settings 21
Configuring IP services 23
Configuring QoS settings 25
Configuring SSL certificates 27
Testing network connectivity 30
Viewing network statistics (netstat) 31
Cisco TelePresence Server 7010 and MSE 8710 in Remotely Managed Mode Printable Help (4.0) Page 15 of 92

Configuring network settings
To configure the network settings on the TelePresence Server and check the network status, go to
Network>Network settings.
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.
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.
You can disable IPv4 on the TelePresence
Server port but only if logged in using IPv6.
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
Table 9: IPv4 configuration
Cisco TelePresence Server 7010 and MSE 8710 in Remotely Managed Mode Printable Help (4.0) Page 16 of 92
Network settings

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.
You can disable IPv6 on the TelePresence
Server port but only if logged in using IPv4.
IPv6 address If you chose Manual configuration, supply the
IPv6 address in CIDR format, for example
fe80::202:b3ff:fe1e:8329.
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
Table 10: 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.
Cisco TelePresence Server 7010 and MSE 8710 in Remotely Managed Mode Printable Help (4.0) Page 17 of 92
Network settings

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.
Select Automatic negotiation if you require a
connection speed of 1000 Mbit/s.
Speed (For Manual configuration only) Set the
connection's speed to 10 Mbit/s or 100 Mbit/s.
The connection speed setting must be the
same for the ports at both ends of this
connection.
Duplex (For Manual configuration only) 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.
Table 11: Ethernet configuration
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.
This value can not be changed, 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.
Table 12: Ethernet status
Cisco TelePresence Server 7010 and MSE 8710 in Remotely Managed Mode Printable Help (4.0) Page 18 of 92
Network settings

Field Field description Usage tips
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.
Table 12: Ethernet status (continued)
Cisco TelePresence Server 7010 and MSE 8710 in Remotely Managed Mode Printable Help (4.0) Page 19 of 92
Network settings

Configuring DNS settings
Go to 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).
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 when DNSconfiguration is Manual.
Secondary
name server
Identifies an optional second name server. If an optional second name server is
configured, the TelePresence Server may
send DNS queries to either name 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.
Table 13: 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
nSecondary name server
nDomain name (DNS suffix)
Cisco TelePresence Server 7010 and MSE 8710 in Remotely Managed Mode Printable Help (4.0) Page 20 of 92
Network settings