Cisco TelePresence 7010, TelePresence MSE 8710 Help Manual

Cisco TelePresence

Server 7010 and MSE8710

in Locally Managed Mode

Printed Help

4.0

D15073

April 2014

Cisco TelePresence Server 7010 and MSE8710 in Locally Managed Mode Printed Help (4.0) Page 1 of 132

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 37 Configuring SIP settings 38 Configuring default conference settings 41 Configuring default endpoint settings 42 Operation mode 48 Displaying and resetting system time 49 Backing up and upgrading the TelePresence Server 50 Shutting down and restarting the TelePresence Server 54 Changing the administrator password 55 Backing up and restoring the configuration via FTP 56

Conferences 57

Adding and updating conferences 58 Displaying the conference list 64 Displaying conference status 66 Calling participants to join a conference 73 Sending a message to participants 74 Adding a pre-configured participant 75

Endpoints and endpoint groups 76

Displaying the list of endpoints 77 Displaying endpoint and group status 78 Adding an endpoint 81 Adding an endpoint group 82 Adding a Legacy TIP endpoint 83

Cisco TelePresence Server 7010 and MSE8710 in Locally Managed Mode Printed Help (4.0) Page 2 of 132

Editing an endpoint's configuration 84 Configuring endpoints and groups advanced settings 91 Viewing endpoint or endpoint group statistics 95

Users 98

Displaying the user list 99 Adding and updating users 100

Logs 102

Working with the event logs 103 Event capture filter 104 Event display filter 105 Logging protocols messages 106 Logging using syslog 107 Working with Call Detail Records 109 APIclients 111 Feedback receivers 112

Reference 113

Content channel support 114 Understanding how participants display in layout views 116 Endpoint types 121 Endpoint interoperability 123 Understanding clustering 124 Understanding your TelePresence Server's conferencing capacity 126

License keys and screen licenses 126

Operation modes 127

Call limits 128 Technical support 131

Cisco TelePresence Server 7010 and MSE8710 in Locally Managed Mode Printed Help (4.0) Page 3 of 132

Introduction

Logging into the web interface

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 locally managed mode. This software is used on the following Cisco TelePresence hardware:

n Cisco TelePresence Server 7010

n Cisco 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:

n Administrator: users with this privilege level may access all functionality

n APIaccess: users with this privilege level can only access the API, not the web interface

n None: 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 Locally Managed Mode Printed Help (4.0) Page 4 of 132

Introduction

Failing to log into the web interface

n Invalid username/password: you have typed the incorrect username and/or password.

n No free sessions: the maximum number of sessions allowed simultaneously on the TelePresence Server

has been reached.

n Your IP address does not match that of the browser cookie you supplied: try deleting your cookies

and log in again

n You 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

n Page 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 Locally Managed Mode Printed Help (4.0) Page 5 of 132

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 Locally Managed Mode Printed Help (4.0) Page 6 of 132

System status

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

Table 1: System status

Field Field Description Usage tips

Model The specific TelePresence Server model.

Serial number The unique serial number of the

TelePresence Server.

Software version

Build The build version of installed software.

Uptime The time since the last restart of the

Host name The host name assigned to the TelePresence

IP address The IP address assigned to the TelePresence

IPv6 address The IPv6 address of this TelePresence

H.323 gatekeeper status

SIP registrar status

The installed software version.

TelePresence Server.

Server.

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.

Whether the TelePresence Server is registered to a SIP registrar.

You will need to provide this information when speaking to customer support.

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.

Operation Mode

Cisco TelePresence Server 7010 and MSE8710 in Locally Managed Mode Printed Help (4.0) Page 7 of 132

Indicates whether the TelePresence Server is operating in locally managed or remotely managed mode.

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.

System status

Table 2: Feature keys

Field Field description Usage tips

TelePresence Server 8710 activation or

Whether or not the unit is enabled. The TelePresence Server will not operate

without activation. This feature key is installed before shipping.

TelePresence Server 7010 activation

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

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.126].

be lower than the maximum that the system can support.

Table 3: Conference status

Field Field description Usage tips

Active conferences

Active participants

Previous participants

Video ports The number of video ports in use on this

Audio ports The number of audio-only ports in use on this

Content ports The number of content channel ports in use on

Cisco TelePresence Server 7010 and MSE8710 in Locally Managed Mode Printed Help (4.0) Page 8 of 132

The number of active conferences on this TelePresence Server.

The number of participants (of all types) that are currently in conferences on this TelePresence Server.

The number of participants who were previously participating in a conference (since the last time the TelePresence Server restarted).

TelePresence Server.

this TelePresence Server.

A conference is active if it has participants.

The numbers are those supported by the number of screen licenses available on the TelePresence Server and dependent upon whether the TelePresence Server is configured to run in HD or Full HD mode.

See Content channel video support and

Understanding your TelePresence Server's conferencing capacity [p.126].

System status

Table 4: System log

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 5: Diagnostic information

Field Field description Usage tips

Diagnostic information

Network capture file

System logs To download the logs, click Download file. An archive containing several useful log files.

Diagnostic files are provided in .zip archive format that contain a text document. To download a diagnostic file, click Download file.

To download a network capture, 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.

There is also a link to Delete network capture which you should only click when your TelePresence Server is operating normally again.

Cisco TelePresence Server 7010 and MSE8710 in Locally Managed Mode Printed Help (4.0) Page 9 of 132

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.

Table 6: Device health details

Field Field description Usage tips

Fans

Voltages

RTC battery

Displays two possible states:

n OK

n Out of spec

States indicate both Current status and Worst status seen conditions.

Temperature Displays three possible states:

n OK

n Out of spec

n Critical

States indicate both Current status and Worst status seen conditions.

The states indicate the following:

n OK – component is functioning properly

n Out 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.

The states indicate the following:

n OK – temperature of the TelePresence

Server is within the appropriate range

n Out of spec – Check the ambient

temperature (should be less than 34 degrees Celsius) and verify that the air vents are not blocked

n Critical – 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

Cisco TelePresence Server 7010 and MSE8710 in Locally Managed Mode Printed Help (4.0) Page 10 of 132

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.

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

Table 7: Cluster status

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.

IP The IP addresses of the slave blades, or Master blade

in the case of the master.

To configure a blade as a master or a slave in a cluster, log in to the Supervisor.

You can click the IPaddress to go to the slave's cluster page.

Cisco TelePresence Server 7010 and MSE8710 in Locally Managed Mode Printed Help (4.0) Page 11 of 132

System status

Table 7: Cluster status (continued)

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:

n OK: The master and slave are communicating

correctly.

n OK (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.

n Still starting up: The slave is in the process of starting

up. Wait a few minutes and then refresh the Status >

Cluster page.

n Lost 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.

n Cluster support not enabled: There is no Cluster

support feature key on this TelePresence Server.

n Failed, 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.

n Blade 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.

n Blade 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

Media processing load

Cisco TelePresence Server 7010 and MSE8710 in Locally Managed Mode Printed Help (4.0) Page 12 of 132

The software version on each TelePresence Server in the cluster.

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.

System status

Table 7: Cluster status (continued)

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.

Cisco TelePresence Server 7010 and MSE8710 in Locally Managed Mode Printed Help (4.0) Page 13 of 132

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.

Table 8: Cluster status

Field Field description Usage tips

Status Possible statuses for the master unit are:

n Still starting up: the master is in the process

of starting up. Wait a few minutes and then refresh the Status > Cluster page.

n OK: The master and slave are

communicating correctly.

n Lost 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.

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.

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.

Cisco TelePresence Server 7010 and MSE8710 in Locally Managed Mode Printed Help (4.0) Page 14 of 132

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 Locally Managed Mode Printed Help (4.0) Page 15 of 132

Network settings

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:

n IP configuration settings

n IP status

n Ethernet configuration

n Ethernet 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.

Table 9: IPv4 configuration

Field Field description Usage tips

IP configuration

IP address The dot-separated IPv4 address for this port,

Subnet mask The subnet mask required for the IP address

Default gateway

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.

for example 192.168.4.45.

you wish to use, for example 255.255.255.0

The IP address of the default gateway on this subnet, for example 192.168.4.1

You can disable IPv4 on the TelePresence Server port but only if logged in using IPv6.

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.

Cisco TelePresence Server 7010 and MSE8710 in Locally Managed Mode Printed Help (4.0) Page 16 of 132

Network settings

Table 10: IPv6 configuration

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

IPv6 address If you chose Manual configuration, supply the

IPv6 address in CIDR format, for example fe80::202:b3ff:fe1e:8329.

Prefix length If you chose Manual configuration, supply the

prefix length.

Default gateway

(Optional) Supply the IPv6 address of the default gateway on this subnet.

IP status

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.

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.

The prefix length is the (decimal) number of bits that are fixed for this address.

The address may be global or link-local

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:

n DHCP

n IP address

n Subnet mask

n Default gateway

IPv6 settings:

n DHCPv6

n IPv6 address

n IPv6 default gateway

n IPv6 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 Locally Managed Mode Printed Help (4.0) Page 17 of 132

Network settings

Table 11: Ethernet configuration

Field Field description Usage tips

Ethernet settings

Speed (For Manual configuration only) Set the

Duplex (For Manual configuration only) Set the

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.

connection's speed to 10 Mbit/s or 100 Mbit/s.

connection's duplex mode to Full duplex or Half duplex.

Ethernet status

Table 12: Ethernet status

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.

The connection speed setting must be the same for the ports at both ends of this connection.

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.

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.

Duplex The duplex mode (Full duplex or Half duplex)

of the network connection to this port.

MAC address The fixed hardware MAC (Media Access

Control) address of this port.

Packets sent The total number of packets sent from this

port (all TCP and UDP traffic).

Packets received

The total number of packets received by this port (all TCP and UDP traffic).

This value is negotiated with the device to which this port is connected or based on your manual configuration.

This value is negotiated with the device to which this port is connected or based on your Manual configuration selected above.

This value can not be changed, it is for information only.

This information can help you confirm that the TelePresence Server is transmitting packets into the network.

This information can help you confirm that the TelePresence Server is receiving packets from the network.

Cisco TelePresence Server 7010 and MSE8710 in Locally Managed Mode Printed Help (4.0) Page 18 of 132

Network settings

Table 12: Ethernet status (continued)

Field Field description Usage tips

Statistics: More statistics for this port.

n Multicast packets sent

n Multicast packets received

n Total bytes sent

n Total bytes received

n Receive queue drops

n Collisions

n Transmit errors

n Receive errors

This information can assist you with diagnosing network issues, such as link speed and duplex negotiation issues.

Cisco TelePresence Server 7010 and MSE8710 in Locally Managed Mode Printed Help (4.0) Page 19 of 132

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.

Table 13: DNS settings

Field Field description Usage tips

DNS configuration

Host name Specifies a name for the TelePresence Server. Depending on your network configuration, you

Name server The IP address of the name server. Required when DNSconfiguration is Manual.

Secondary name server

Domain name (DNS suffix)

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

Identifies an optional second name server. If an optional second name server is

Specifies an optional suffix to add when performing DNS lookups.

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.

may be able to use this host name to communicate with the TelePresence Server, without needing to know its IP address.

configured, the TelePresence Server may send DNS queries to either name server.

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.

View DNS status

Use the DNS status fields to verify the current DNS settings for the TelePresence Server, including:

n Host name

n Name server

n Secondary name server

n Domain name (DNS suffix)

Cisco TelePresence Server 7010 and MSE8710 in Locally Managed Mode Printed Help (4.0) Page 20 of 132

Network settings

Configuring IP routes settings

You may need to set up one or more routes to control how IP traffic flows in and out of the TelePresence Server.

It is important that you create these routes correctly, or you may be unable to make calls or access the web interface.

To configure the route settings, go to Network > Routes.

On this page:

n IP routes configuration

n Current routes tables

IP routes configuration

In this section you can control how IP packets should be directed out of the TelePresence Server. You should only change this configuration if you have a good understanding of the topology of the network(s) to which the TelePresence Server is connected.

Add a new IP route

To add a new route:

1. Enter the IP address of the target network, and the mask length that defines the range of addresses.

2. Select whether the traffic to those addresses will be routed via Port A's default gateway or a Gateway that you specify.

3. Click Add IP route. The new route is added to the list. If the route already exists, or aliases (overlaps) an existing route, the interface prompts you to correct the route.

Use the following table for reference:

Table 14: IP route configuration

Field Field description Usage tips

IP address / mask length

Use these fields to define the range of IP addresses to which this route applies.

IPv4 addressing: Enter the IP address of the target network in dotted quad format, setting any unfixed bits of the address to 0. Use the mask length field to specify how many bits are fixed (and thus how many are unfixed, giving the range of addresses).

IPv6 addressing: Enter the IP address of the target network in CIDR format, setting any unfixed bits of the address to 0. Use the mask length field to specify how many bits are fixed (and thus how many are unfixed, giving the range of addresses).

IPv4 example: To route all IPv4 addresses in the range 192.168.4.128 to 192.168.4.255, specify the IP address as 192.168.4.128 and the mask length as 25. The first 25 bits are fixed, which means that the last seven bits determine the range of addresses.

IPv6 example: To route all IPv6 addresses in the range 2001:db8::0000 to 2001:db8::ffff, enter the IP address 2001:db8:: and the mask length as 112. The first 112 bits are fixed, which means that the last 16 bits determine the range of addresses.

Cisco TelePresence Server 7010 and MSE8710 in Locally Managed Mode Printed Help (4.0) Page 21 of 132

Network settings

Table 14: IP route configuration (continued)

Field Field description Usage tips

Route Use this field to control how packets destined

for addresses matching the specified pattern are routed.

You may select Port A, or Gateway. If you select Gateway, enter the IP address of the gateway to which you want packets to be directed.

If you select Port A, matching packets will be routed to Port A's default gateway (see

Configuring network settings).

To view or delete an existing IP route

The page displays the following details for each route:

n The IP address pattern and mask

n Where matching packets will be routed, with the possibilities being:

l Port A—meaning the default gateway configured for Port A l <IP address>—a specific address has been chosen

n Whether the route has been configured automatically as a consequence of other settings, or manually

added by you.

The default routes are configured automatically by your choice of Default gateway preferences for IPv4 and IPv6 (see Configuring network settings) and cannot be deleted. Any packets destined for addresses that are not matched by your manually configured routes will be routed via the default gateway.

You can delete manually configured routes. Select the check boxes next to the routes then click Delete

selected.

Current routes tables

Each table shows all configured routes (both manual and automatic) for IPv4 and IPv6 for the TelePresence Server's Ethernet port. If you want to change the IP configuration for the Ethernet port, go to Network >

Network settings.

Cisco TelePresence Server 7010 and MSE8710 in Locally Managed Mode Printed Help (4.0) Page 22 of 132

Network settings

Configuring IP services

Go to Network>Services to control access to the web services on the TelePresence Server.

The TelePresence Server offers web services, such as HTTP for the web interface and SIP for making and receiving calls. You can control whether services may be accessed on the unit's Ethernet interfaces, and also the TCP/UDP ports through which those services are available.

Enabling TCP/UDPservices

There are options to control IPv4 and/or IPv6 services, depending on which IP versions are enabled on the

Network>Network settings page.

1. Check the boxes next to the service names you want to enable, or clear the boxes to disable services.

2. Edit the port numbers for the services if necessary. (Commonly used port values are entered by default).

3. Click Apply changes.

Defining the ephemeral port range

1. Enter the Minimum port number in your preferred ephemeral port range. The default is 49152. The minimum port cannot be set to be below 10000.

2. Enter the Maximum port number in your preferred ephemeral port range. The default is 65535 which is the maximum possible setting, giving a default range of about 15000 ports. The TelePresence Server will not allow you to reduce the range below 5000 ports because this would potentially hamper conferencing functionality.

3. Click Apply changes.

4. If you want to reset the values to their default settings, click Reset to default and then click Apply

changes.

Resetting to the default configuration

1. Click Reset to default. The TelePresence Server replaces any changed settings with the page defaults. These do not take effect immediately.

2. Click Apply changes. The default settings take effect.

Table 15: Network >Services field descriptions

Field Field description Usage tips

HTTP Enable/disable web access on the

appropriate port.

Cisco TelePresence Server 7010 and MSE8710 in Locally Managed Mode Printed Help (4.0) Page 23 of 132

Web access is required to view and change the TelePresence Server web pages and read online help files.

Network settings

Table 15: Network >Services field descriptions (continued)

Field Field description Usage tips

HTTPS Enable/disable secure (HTTPS) web access

on the specified interface or change the port that is used for this service.

Incoming H.323

Enable/disable the ability to receive incoming calls to the TelePresence Server using H.323 or change the port that is used for this service.

SIP (TCP) Allow/reject incoming calls to the

TelePresence Server using SIP over TCP or change the port that is used for this service.

Encrypted SIP (TLS)

Allow/reject incoming encrypted SIP calls to the TelePresence Server using SIP over TLS or change the port that is used for this service.

By default, the TelePresence Server has its own SSL certificate and private key. However, you can upload a new private key and certificates if required. For more information about SSL certificates, refer to Configuring

SSL certificates.

This field is only visible if the TelePresence Server has the Encryption feature key installed. For more information about installing feature keys, refer to Upgrading and backing

up the TelePresence Server.

Disabling this option will not prevent outgoing calls to H.323 devices being made by the TelePresence Server.

Disabling this option will not prevent outgoing calls to SIP devices being made by the TelePresence Server.

This field is only visible if the TelePresence Server has the Encryption feature key installed. For more information about installing feature keys, refer to Upgrading and backing

up the TelePresence Server.

FTP Enable/disable FTP access on the specified

interface or change the port that is used for this service.

FTP can be used to upload and download TelePresence Server configuration.

You should consider disabling FTP access on any port that is outside your organization's firewall.

If you require advanced security for the TelePresence Server, disable FTP access.

SIP (UDP) Allow/reject incoming and outgoing calls to

the TelePresence Server using SIP over UDP

Disabling this option will prevent calls using SIP over UDP.

or change the port that is used for this service.

Minimum The lower limit of the ephemeral port range. Defaults to 49152, though you can set it as low

as 10000 or as high as 60535.

Maximum The upper limit of the ephemeral port range. Defaults to 65535, though you can set it as low

as 15000. The minimum range is limited to 5000 ports.

Cisco TelePresence Server 7010 and MSE8710 in Locally Managed Mode Printed Help (4.0) Page 24 of 132

Network settings

Configuring QoS settings

To configure Quality of Service (QoS) on the TelePresence Server for audio and video, go to Network >

QoS.

QoS is a term that refers to a network's ability to customize the treatment of specific classes of data. For example, QoS can be used to prioritize audio transmissions and video transmissions over HTTP traffic. These settings affect all outgoing audio and video packets. All other packets are sent with a QoS of 0.

The TelePresence Server allows you to set a 6-bit value for Type of Service (IPv4) or Traffic Class (IPv6), which can be interpreted by networks as either Type of Service (ToS) or Differentiated Services (DiffServ). Note that in terms of functionality, IPv6 QoS is identical to IPv4 QoS.

CAUTION: Do not alter the QoS settings unless you need to do so.

To configure the QoS settings you need to enter a 6-bit binary value.

Further information about QoS, including values for ToS and DiffServ, can be found in the following RFCs, available on the Internet Engineering Task Force web site www.ietf.org:

n RFC 791

n RFC 2474

n RFC 2597

n RFC 3246

On this page:

n About QoS configuration settings

n ToS configuration

n DiffServ configuration

n Default settings

About QoS configuration settings

The tables below describe the settings on the Network > QoS page.

Click Update QoS settings after making any changes.

Table 16: IPv4 configuration

Field Field description Usage tips

Audio Six bit binary field for prioritizing audio data

packets on the network.

Video Six bit binary field for prioritizing video data

packets on the network.

Do not alter this setting unless you need to.

Cisco TelePresence Server 7010 and MSE8710 in Locally Managed Mode Printed Help (4.0) Page 25 of 132

Network settings

Table 17: IPv6 configuration

Field Field description Usage tips

Audio Six bit binary field for prioritizing audio data

Do not alter this setting unless you need to.

packets on the network.

Video Six bit binary field for prioritizing video data

Do not alter this setting unless you need to.

packets on the network.

ToS configuration

ToS configuration represents a tradeoff between the abstract parameters of precedence, delay, throughput, and reliability.

ToS uses six out of a possible eight bits. The TelePresence Server allows you to set bits 0 to 5, and will place zeros for bits 6 and 7.

n Bits 0-2 set IP precedence (the priority of the packet).

n Bit 3 sets delay: 0 = normal delay, 1 = low delay.

n Bit 4 sets throughput: 0 = normal throughput, 1 = high throughput.

n Bit 5 sets reliability: 0 = normal reliability, 1 = high reliability.

n Bits 6-7 are reserved for future use and cannot be set using the TelePresence Server interface.

You need to create a balance by assigning priority to audio and video packets whilst not causing undue delay to other packets on the network. For example, do not set every value to 1.

DiffServ configuration

DiffServ uses six out of a possible eight bits to set a codepoint. (There are 64 possible codepoints.) The TelePresence Server allows you to set bits 0 to 5, and will place zeros for bits 6 and 7. The codepoint is interpreted by DiffServ nodes to determine how the packet is treated.

Default settings

The default settings for QoS are:

n Audio 101110:

l For ToS, this means IP precedence is set to 5 giving relatively high priority. Delay is set to low,

throughput is set to high, and reliability is set to normal.

l For Diff Serv, this means expedited forwarding.

n Video 100010:

l For ToS, this means IP precedence is set to 4 giving quite high priority (but not quite as high as the audio

precedence). Delay is set to normal, throughput is set to high, and reliability is set to normal.

l For DiffServ, this means assured forwarding (codepoint 41).

To return the settings to the default settings, click Reset to default.

Cisco TelePresence Server 7010 and MSE8710 in Locally Managed Mode Printed Help (4.0) Page 26 of 132

Network settings

Configuring SSL certificates

If the Cisco TelePresence Server has the Secure management (HTTPS) or Encryption feature key installed, and you enable HTTPS on the Network > Services page, you will be able to access the web interface of the TelePresence Server using HTTPS.

Note: A certificate and key are also required if you select to use the Encrypted SIP (TLS) service in Network

> Services.

The Cisco TelePresence Server has a local certificate and private key pre-installed and it uses this to authenticate itself to the browser when you access the unit using HTTPS. However, Cisco recommends that you upload your own certificate and private key to ensure security because all Cisco TelePresence Server's have identical default certificates and keys.

The TelePresence Server uses DTLS to negotiate encryption parameters with TIP endpoints—this requires a certificate to be used. The TelePresence Server’s implementation of DTLS handles customer-supplied certificates in the following way:

n Opportunistic DTLS always uses the default certificate for DTLS negotiation, even if a customer-supplied

certificate is uploaded.

n Negotiated DTLS uses the customer-supplied certificate if one is uploaded (this is the preferred procedure).

Negotiated DTLS will be used if the endpoint supports RFC 5763; otherwise, in a TIP call, opportunistic DTLS will be attempted.

To upload your own certificate and key, go to Network > SSL certificates.

Note:The SSLCertificates page is only available if your TelePresence Server has the Encryption feature key.

Complete the fields using the table below for help and click Upload certificate and key. Note that you must upload a certificate and key simultaneously. You must restart the Cisco TelePresence Server after uploading a new certificate and key.

Note: A certificate and private key must be in PEM format.

You can remove your own certificate and key, if necessary, by clicking Delete custom certificate and key. You must restart the TelePresence Server after deleting a certificate.

The following table details the fields on the Network > SSL certificates page:

Cisco TelePresence Server 7010 and MSE8710 in Locally Managed Mode Printed Help (4.0) Page 27 of 132

Network settings

Table 18: Local certificate

Field Field description Usage tips

Subject The details of the business to which the

certificate has been issued:

n C: the country where the business is

registered.

n ST: the state or province where the

business is located.

n L: the locality or city where the business is

located.

n O: the legal name of the business.

n OU: the organizational unit or department.

n CN: the common name for the certificate, or

the domain name.

Issuer The details of the issuer of the certificate. Where the certificate has been self-issued,

these details are the same as for the Subject.

Issued The date on which the local certificate was

issued.

Expires The date on which the local certificate will

expire.

Private key Whether the private key matches the

certificate.

Your web browser uses the SSL certificate's public key to encrypt the data that it sends back to the Cisco TelePresence Server. The private key is used by the Cisco TelePresence Server to decrypt that data. If the Private key field shows 'Key matches certificate' then the data is securely encrypted in both directions.

Table 19: Local certificate configuration

Field Field description Usage tips

Certificate If your organization has bought a certificate,

or you have your own way of generating certificates, you can upload it. Click Choose

File to find and select the certificate file.

Private key Click Choose File to find and select the

private key file that accompanies your certificate.

Private key encryption password

If your private key is stored in an encrypted format, you must enter the password here so that you can upload the key to the Cisco TelePresence Server.

A certificate and private key must be in PEM format.

Cisco TelePresence Server 7010 and MSE8710 in Locally Managed Mode Printed Help (4.0) Page 28 of 132

Network settings

Table 20: Trust store

Field Field description Usage tips

Subject The details of the trust store certificate;

usually a certificate issued by the authority that is used to verify the local certificate.

Issuer The details of the issuer of the trust store

certificate.

These are the details of the trusted certification authority.

Issued The date on which the trust store certificate

was issued.

Expires The date on which the trust store certificate

will expire.

Table 21: Trust store configuration

Field Field description Usage tips

Trust store The trust store is required for two reasons:

n to verify the identity of the remote end of a

SIP TLS connection (incoming call or outgoing call or registration)

n to verify the identity of the remote end of an

outgoing HTTPS connection (e.g. feedback receivers or API applications calling participant.requestDiagnostics)

Certificate verification settings

Determines the circumstances in which the remote certificate must be verified with the trust store.

Browse to and select the trust store certificate file, then click Upload trust store.

The store may contain multiple certificates.

When verification is required (see following setting) the certificate of the remote party is verified against the trust store: the remote certificate must either be in the trust store or in the trust chain of one of its certificates.

Click Delete trust store if you need to remove it or replace it with an updated file.

Select one of the drop-down options below and click Apply changes.

n No verification: The remote certificate is

never verified against the trust store (remote end always trusted).

n Outgoing connections only: The

TelePresence Server attempts to verify the remote certificate for all outgoing SIPTLSand HTTPSconnections.

n Outgoing connections and incoming calls:

The TelePresence Server attempts to verify the remote certificate for all incoming and outgoing SIPTLSconnections, and for outgoing HTTPSconnections.

Cisco TelePresence Server 7010 and MSE8710 in Locally Managed Mode Printed Help (4.0) Page 29 of 132

Network settings

Testing network connectivity

You can use the Network connectivity page to troubleshoot network issues between the TelePresence Server and a remote video conferencing device (host).

On this page you can ping another device from the TelePresence Server's web interface and trace the route to that device. The results show whether or not you have network connectivity between the TelePresence Server and the remote host.

To test connectivity with a remote device, go to Network > Connectivity. In the text box, enter the IP address or hostname of the device to which you want to test connectivity and click Test connectivity.

The results show the outbound interface for the query and the IP address of the remote host.

The ping results show the roundtrip time in milliseconds and the TTL (Time To Live) value on the echo reply.

For each intermediate host (typically routers) between the TelePresence Server and the remote host, the host's IP address and response time are shown.

Not all devices will respond to the messages from the TelePresence Server. Routing entries for nonresponding devices are shown as <unknown>. Some devices are known to send invalid ICMP response packets (for example, with invalid ICMP checksums). Invalid ICMPresponses are also not recognized by the TelePresence Server so these responses are also shown as <unknown>.

Note: The ping message is sent from the TelePresence Server to the IP address of the remote host. Therefore, if the TelePresence Server has an IP route to the given host, the ping will be successful. This feature allows the TelePresence Server’s IP routing configuration to be tested, and it has no security implications.

Note: If you are unable to ping the remote host, then check your network configuration—especially any firewalls using NAT.

Cisco TelePresence Server 7010 and MSE8710 in Locally Managed Mode Printed Help (4.0) Page 30 of 132

+ 102 hidden pages

Cisco TelePresence 7010, TelePresence MSE 8710 Help Manual

Specifications and Main Features

Frequently Asked Questions

User Manual