Page 1
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
Software version TC7.3
JU LY 2015
MX200 MX300
Administrator guide
for Cisco TelePresence MX200 and MX300 (1st generation)
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
1
Page 2
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
Contents
Thank you for choosing Cisco!
Your Cisco product has been designed to give you many
years of safe, reliable operation.
This part of the product documentation is aimed at
administrators working with the setup of the MX200 and
MX3 0 0 (1
Our main objective with this Administrator guide is to address
your goals and needs. Please let us know how well we
succeeded!
May we recommend that you visit the Cisco web site
regularly for updated versions of this guide.
The user documentation can be found on
► http://www.cisco.com/go/telepresence/docs
st
generation).
How to use this guide
The top menu bar and the entries in the Table of contents are
all hyperlinks. You can click on them to go to the topic.
Table of contents
Introduction ............................................................................. 4
User documentation ................................................................. 5
Software ................................................................................... 5
What’s new in this version ........................................................ 6
Cisco TelePresence MX200 and MX300 at a glance ............... 7
Web interface ......................................................................... 9
Accessing the web interface ...................................................10
Changing the system password ..............................................11
The interactive menu ...............................................................12
System information ..................................................................13
About snapshots and remote monitoring
(TC7.3.3 and later)
About snapshots and remote monitoring
(TC7.3.0 to TC7.3.2)
Placing a call ............................................................................16
Sharing content ........................................................................17
Controlling and monitoring a call .............................................18
Controlling your camera ...........................................................19
Local layout control ................................................................. 20
Controlling the far end camera ................................................21
Accessing call information ...................................................... 22
System configuration .............................................................. 23
Changing system settings ...................................................... 24
System status ......................................................................... 25
Managing the favorites list ...................................................... 26
Favorite list folders .................................................................. 27
Choosing a wallpaper ............................................................. 28
Choosing a ringtone ................................................................ 29
Peripherals overview .............................................................. 30
User administration ..................................................................31
Adding a sign in banner .......................................................... 35
Managing the video system’s certificates .............................. 36
Managing the list of trusted certificate authorities ................. 37
Managing pre-installed certificates for Edge provisioning ..... 39
Setting strong security mode ................................................. 40
Changing the persistency mode ..............................................41
Deleting trust lists (CUCM only) .............................................. 42
...................................................................14
.................................................................15
Troubleshooting ...................................................................... 43
Downloading log files .............................................................. 44
Starting extended logging ...................................................... 45
Capturing user interface screenshots .................................... 46
Upgrading the system software...............................................47
Adding option keys ................................................................. 48
Backup and restore ................................................................. 49
Reverting to the previously used software version ................ 50
Factory reset ............................................................................51
Remote support user .............................................................. 52
Restarting the system ............................................................. 53
System settings .................................................................... 54
Overview of the system settings ............................................ 55
Audio settings ......................................................................... 58
Cameras settings .................................................................... 60
Conference settings ............................................................... 62
FacilityService settings ........................................................... 67
H323 settings .......................................................................... 68
Logging settings ......................................................................71
Network settings ..................................................................... 72
NetworkServices settings ....................................................... 79
Peripherals settings ................................................................ 84
Phonebook settings ................................................................ 85
Provisioning settings ............................................................... 86
RTP settings ............................................................................ 88
Security settings ..................................................................... 89
SerialPort settings....................................................................91
SIP settings ............................................................................. 92
Standby settings ..................................................................... 96
SystemUnit settings ................................................................ 97
Time settings .......................................................................... 98
UserInterface settings............................................................101
Video settings ....................................................................... 102
Experimental settings ............................................................ 112
Setting passwords ............................................................... 113
Setting the system password ................................................ 114
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
2
Page 3
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
Contents
Appendices ..........................................................................115
Cisco VCS provisioning .........................................................116
Optimal definition profiles ......................................................117
Packet loss resilience - ClearPath .........................................11 8
Factory resetting the video system ....................................... 119
Factory resetting the Touch 8 control panel ..........................120
Technical specification ...........................................................121
Supported RFCs ....................................................................123
User documentation on the Cisco web site ...........................124
Cisco contacts .....................................................................125
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
3
Page 4
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
Introduction
Chapter 1
Introduction
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
4
Page 5
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
Introduction
This document provides you with the information required to
administrate your product at an advanced level.
How to install the product and the initial configurations
required are described in the Installation guide and Getting
started guide, respectively.
Products covered in this guide
• Cisco TelePresence MX300
• Cisco TelePresence MX200
Note that MX300 G2 (second generation MX300) is covered
in a separate guide.
User documentation
The user documentation for the Cisco TelePresence systems
running the TC software includes several guides suitable for
various user groups.
• Installation guides:
How to install the products
• Getting started guide:
Initial configurations required to get the system up and
running
• Administering TC Endpoints on CUCM:
Tasks to perform to start using the product with the Cisco
Unified Communications Manager (CUCM)
• Administrator guide (this guide):
Information required to administer your product
• Quick reference guides:
How to use the product
• User guides:
How to use the product
• Knowledge base articles
• Video conferencing room primer:
General guidelines for room design and best practice
• Video conference room acoustics guidelines:
Things to do to improve the perceived audio quality
• Software release notes
• Regulatory compliance and safety information guide
• Legal & license information
Software
You can download the software for your product from the
Cisco web site. Go to:
► http://www.cisco.com/cisco/software/navigator.html
We recommend reading the Software Release Notes (TC7),
go to:
► http://www.cisco.com/c/en/us/support/collaborationendpoints/telepresence-mx-series/tsd-productssupport-series-home.html
Downloading the user documentation
We recommend you visit the Cisco web site regularly for
updated versions of the user documentation.
Go to: ► http://www.cisco.com/go/telepresence/docs
Guidelines how to find the documentation
on the Cisco web site are included in the
► User documentation on the Cisco web site appendix.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
5
Page 6
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
Introduction
What’s new in this version
This section provides an overview of the new and changed
system settings and new features in the TC7.3 software
version.
Software release notes
For a complete overview of new features and changes, we
recommend reading the Software Release Notes (TC7). Go
to:
► http://www.cisco.com/c/en/us/support/collaboration-
endpoints/telepresence-mx-series/tsd-products-supportseries-home.html
Software download
For software download go to:
► http://www.cisco.com/cisco/software/navigator.html
New features and improvements
Local preview of presentation in a call
This allows the user to preview the presentation locally before
sharing it with far end. The feature has previously been
available for EX systems, and is now available across the
portfolio.
TC7.3.0-TC7.3.2: Users are notified when snapshots are
taken
Both the on screen display and web interface have warnings
when the snapshots feature is enabled. A notification pops up
on the on screen display, when a snapshot is taken. On the
web interface the administrator is warned that this notice will
show up when the feature is enabled.
The system also logs when snapshots are taken, and which IP
address the request was initiated from.
It is possible to allow and disallow snapshots remotely, but
not to observe the room without the users being notified.
TC7.3.3 and later: Remote Monitoring option key
Due to security reasons, taking snapshots of local and far end
video streams from the call control page on the system’s web
interface now requires an option key to be installed on the
endpoint.
The remote monitoring option key can only be added to
systems that are upgraded to TC7.3.3 and above. Remote
monitoring is enabled once the option key is added, and the
system rebooted. Once this feature is enabled, the only way
to disable it is to remove the option key.
This feature does not display warning messages or indicators
on the local system that someone is monitoring the room.
Please provide adequate notice to users of the system that
the system administrator may monitor and control the camera
and screen.
System configuration changes
New configurations
Cameras Preset TriggerAutofocus
H323 Profile Encryption KeySize
NetworkServices CDP Mode
Configurations that are removed
H323 Profile [1] Encryption MinKeySize
Video AllowWebSnapshots (TC7.3.3)
Configurations that are modified
FacilityService Service [5] Name
OLD: <S: 0, 255>
NEW: <S: 0, 1024>
FacilityService Service [5] Number
OLD: <S: 0, 255>
NEW: <S: 0, 1024>
Video AllowWebSnapshots (TC7.3.0-TC7.3.2)
OLD: <Off/On>, default Off
NEW: <Off/On/LocalDeviceOnly>, default
LocalDeviceOnly
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
6
Page 7
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
Introduction
The Cisco TelePresence® MX Series makes telepresence
more accessible to teams everywhere with ready-to-use
simplicity and high quality. This highly integrated telepresence
system is easy to install, so you can quickly transform any
meeting space into a video-enabled team room. Whether
(page 1 of 2)Cisco TelePresence MX200 and MX300 at a glance
you are just getting started with video communications
or implementing a large-scale deployment, the Cisco
TelePresence MX Series delivers high quality performance in
a simple and intuitive way.
Features and benefits
• The systems are easy to install – one piece plus floor
stand, table stand (MX200 only), or wall mount brackets
(VESA mount).
• The systems are self-configuring with Cisco Unified
Communications Manager (UCM), Cisco TelePresence
Video Communication Server (VCS), or Cisco WebEx
TelePresence provisioning. All you need is to authenticate
your endpoint to the network.
• PrecisionHD camera with pan, tilt, and 4x optical zoom
helps ensure optimal framing and video clarity.
• Dedicated camera presets provide flexibility and easy
viewing for any meeting scenario.
• The 8-inch Touch interface offers simple control.
• Simple one-button-to-push calling integrates with
common calendar programs.
• Video resolutions of 1080p30 and 720p60 bring
telepresence experience to any meeting room or office.
• The high-quality 42-inch (MX200) and 55-inch (MX300)
displays with 1920 x 1080 resolution enable clear images.
• You can easily connect and share your PC content at
WXGA and 720p30 resolution and frame rate.
• The systems support H.323 and Session Initiation
Protocol (SIP) with bandwidth up to 6 Mbps point-topoint.
• Two front speakers provide superior audio quality.
• The systems are standards-based.
• Capabilities for large conferences and transparent
escalation from point-to-point to multipoint calls using the
Cisco TelePresence Multiway™ technology.
MX300 MX200
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
7
Page 8
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
Introduction
Cisco TelePresence MX200 and MX300 at a glance (page 2 of 2)
Rear view
Internal microphone
Loudspeakers
MX200: 1 external microphone (+ 1 optional)
MX300: 2 external microphones
Precision HD camera
MX200: 42” LCD monitor
MX300: 55” LCD monitor
Codec embedded in
video unit
MX200MX300
MX300 mounting options
(floor stand, wall mount)
MX200 mounting options
(floor stand, table stand, wall mount)
Touch controller
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
8
Page 9
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
Chapter 2
Web interface
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
9
Page 10
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
Accessing the web interface
The web interface provides full configuration access to your
video conference system.
You can connect from a computer and administer the system
remotely.
In this chapter you will find information how to use the web
interface for system configuration and maintenance.
We recommend that you use the latest release of one of the
major web browsers.
1. Connect to the video system
Open a web browser and enter the IP address of
the video system in the address bar.
How to find the IP address
Touch controller: Tap the contact
information in the upper left corner
of the Touch controller and open the
Settings menu. Then tap System
Information.
2. Sign in
Enter the user name and password for your
video system and click Sign In.
The system is delivered with a default
user named admin with no password.
Leave the Password field blank when
signing in for the first time.
It is mandatory to set a password for
the admin user, see the next page.
Signing out
Hover the mouse
over the user
name and choose
Sign out from the
drop-down list.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
10
Page 11
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
Changing the system password
It is mandatory to set a password for a user with
ADMIN rights in order to restrict access to system
configuration. This includes the default admin us e r.
A warning, saying that the system password is not set, is
shown on screen until you set a password.
You can read more about passwords in the
► Setting passwords ch apte r.
1. Open the Change Password dialog
Hover the mouse over your the name, and
choose Change password in the drop-down list.
2. Set the new password
Enter your current and new passwords as
requested, and click Change password for the
change to take effect.
If the password currently is not set, leave
the Current password field blank.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
11
Page 12
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
The interactive menu
The web interface provides access to tasks and
configurations. They are available from the main menu, which
appears near the top of the page when you have signed in.
When you hover the mouse over an item in the main menu,
you can navigate to its related sub-pages.
Main menu
Hover the mouse over a main menu item in
order to see the titles of the related sub-pages.
Click a sub-page’s title to open it. Click the
main menu item itself if there are no subpages. Only pages that the user has access
rights for are shown
*
.
Click Home to return to the System Information
page.
*
You can read more about user administration, user roles and access
Sub-pages
Call Control Maintenance
Configuration
System Configuration
System Status
Local Contacts Management
Personalization
Peripherals
User Administration
Sign In Ba nner
Startup Scripts
API
Security
Diagnostics
Troubleshooting
Call History
Log Files
User Interface Screenshots
Software Upgrade
Option Keys
Backup an d Restore
System Recovery
Restart
rights in the ► User administration section.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
12
Page 13
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
System information
The video system’s Home page shows an overview of the
basic set-up and status of the system
This includes information like system name and product type,
which software version the system runs, its IPaddress, etc.
Also the registration status for the video networks (SI P and
H.323) is included, as well as the number/URI to use when
making a call to the system.
*
.
Navigate to: Home
*
The system information shown in the illustration serve as an
example. Your system may be different.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
13
Page 14
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
About snapshots and remote monitoring (TC7.3.3 and later)
Snapshots of local input sources
If the Remote Monitoring option key is installed on the video
system, snapshots of the video system’s input sources are
displayed on the Call Control page.
Snapshots are displayed both when the video system is idle,
and when in a call.
This feature may be used when administering the video
system from a remote location, for example to check the
camera view and control the camera.
Far end snapshots
If the Remote Monitoring option key is installed on the video
system, far end snapshots may also be captured. Whether or
not the Remote Monitoring option key is installed on the far
end video system, does not make any difference.
Far end snapshots are prohibited during encrypted calls.
Navigate to: Call Control
View snapshots from the input sources
Install the Remote Monitoring option key in order
to view snapshots from the selected main source
or presentation source in this area.
PLEASE BE AWARE THAT IF YOU ENABLE THE REMOTE
MONITORING OPTION YOU MUST MAKE SURE THAT YOU COMPLY
WITH LOCAL LAWS AND REGULATIONS WITH REGARD TO PRIVACY
AND PROVIDE ADEQUATE NOTICE TO USERS OF THE SYSTEM THAT
THE SYSTEM ADMINISTRATOR MAY MONITOR AND CONTROL THE
CAMER A AND SCREEN. IT IS YOUR RESPONSIBILIT Y TO COMPLY
WITH PRIVACY REGUL ATIONS WHEN USING THE SYSTEM AND
CISCO DISCLAIMS ALL LIABILITY FOR ANY UNLAWFUL USE OF
THIS FEATURE.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
14
Page 15
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
About snapshots and remote monitoring (TC7.3.0 to TC7.3.2)
Snapshots of local input sources
If the snapshot feature is enabled on the video system,
snapshots of the video system’s input sources are displayed
on the Call Control page.
Snapshots are displayed both when the video system is idle,
and when in a call.
This feature may be used when administering the video
system from a remote location, for example to check the
camera view and control the camera.
The users of the video system are notified when the
snapshot feature is in use. A notification saying that
the administrator is visually monitoring the room is
displayed on the main display of the video system.
Far end snapshots
If the snapshot feature is enabled on the video system, far
end snapshots may also be captured. Whether or not the
snapshot feature is enabled on the far end video system,
does not make any difference.
Far end snapshots are prohibited during encrypted calls.
Navigate to: Call Control
Enable the snapshot feature
By default, the snapshot feature is disabled.
Enable the feature using the web interface.
• Go to the Configuration tab and select System
Configuration
• Navigate to Video > AllowWebSnapshots and
choose On.
• Click Save for the change to take effect.
View snapshots from the input sources
Click in this area to view snapshots from the
selected main source or presentation source.
Snapshots of the main or presentation source
are displayed for approximately 10 seconds.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
15
Page 16
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
Placing a call
You can use the Call Control page to place a call.
It is the video system (display, microphones and
loudspeakers) that is used for the call; it is not the PC
running the web interface.
Calling
You can call someone either by choosing a contact name in
the Local, Directory or Recents lists, or by typing a complete
URI or number in the Search or Dial field. Then click Call in
the associated contact card.
Searching the contact lists
Enter one or more characters in the Search or Dial field.
Matching entries from the Local, Directory and Recents lists
will be listed as you type.
Select the correct entry in the list and click Call.
Calling more than one
A point-to-point video call (a call involving two parties only)
can be expanded to include one more participant on audioonly.
Follow the same procedure to call the next conference
participant as you did when calling the first par ticipant.
Calling more than one using a conference bridge (CUCM ad
hoc conferencing or MultiWay) is not supported from the web
interface, even if it is supported by the video system itself.
Whether or not snapshots of input sources are shown as illustrated,
depends on the sof tware version, configuration, and options installed
on the video system. Refer to the About snapshots and remote
monitoring sections (► TC7.3.3 or newer or ► TC7.3.0 to TC7.3.2).
Navigate to: Call Control
Calling someone
Click a contact name, either in the
Local, Directory or Recents lists.
Then click Call in the contact card.
Alternatively, enter the complete URI
or number in the Search and Dial
field. Then click the Call button that
appears next to the URI or number.
Holding and resuming
Use the
to the participant’s name
to put him on hold.
To resume the call,
use the button
that is present when a
participant is on hold.
button next
Ending a call
If you want to terminate a
call or conference, click End
all. Confirm your choice in
the dialog that appears.
To disconnect just one
participant in a conference,
click the
participant.
button for that
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
16
Page 17
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
Sharing content
You can connect a presentation source to one of the external
inputs of your video system. Most often a PC is used as
presentation source, but other options may be available
depending on your system setup.
While in a call you can share content with the other
participant in the call (far end).
If you are not in a call, the content is shared locally on your
display.
Navigate to: Call Control
Sharing content
1. Choose a Presentation source from the
drop-down list.
2. Click Start Presentation.
Stop content sharing:
Whether or not snapshots of input sources are shown as illustrated,
depends on the sof tware version, configuration, and options installed
on the video system. Refer to the About snapshots and remote
monitoring sections (► TC7.3.3 or newer or ► TC7.3.0 to TC7.3.2).
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
17
Click the Stop Presentation button that is present
while sharing.
Page 18
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
Controlling and monitoring a call
You can control and monitor several call features using the
Call Control page.
Navigate to: Call Control
Microphone
mute
Click the button
to mute the
microphone.
Then the text
changes to
Microphone: Off.
Click again to
unmute.
Volume down
Volume up
Show/hide
call details
Click the
information button
to show details
about the call.
Click the button
again to hide the
information.
Call details
Whether or not snapshots of input sources are shown as illustrated,
depends on the sof tware version, configuration, and options installed
on the video system. Refer to the About snapshots and remote
monitoring sections (► TC7.3.3 or newer or ► TC7.3.0 to TC7.3.2).
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
18
scroll your browser to
If necessary,
see all call details.
Page 19
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
Controlling your camera
For software version TC7.3.3 and later:
You can control the camera of the video system (pan, tilt,
zoom) from the Call Control page. Only available camera
controls will appear.
For software version TC7.3.0 to TC7.3.2:
You can control the camera of the video system (pan, tilt,
zoom) from the Call Control page provided that the Video
AllowWebSnapshots setting is switched On. Only available
camera controls will appear.
If snapshots from the camera are shown on the web
interface, a notification will be sent to the users of
the video system (shown on the main display) that an
administrator is monitoring their video.
Whether or not snapshots of input sources are shown as illustrated,
depends on the sof tware version, configuration, and options installed
on the video system. Refer to the About snapshots and remote
monitoring sections (► TC7.3.3 or newer or ► TC7.3.0 to TC7.3.2).
Navigate to: Call Control
Control the camera
1. Click the camera icon to open
the camera control window.
2. Use the left and right arrows
to pan the camera; the up
and down arrows to tilt it; and
+ and - to zoom in and out.
For software versions
TC7.3.0 to TC7.3.2, the
cursor must be in the image
to show the controls.
Choose which camera to control
Click the arrow to open the
drop-down list. Then choose the
camera you want to control.
Camera presets
If one or more presets are defined,
click Presets... to open a list of
available presets.
Click a preset’s name to move the
camera(s) to the preset position.
Click OK to close the window.
You cannot use the web interface to
define a preset; you should use the
video system’s Touch user interface.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
19
Page 20
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
Local layout control
You can choose a local layout using the Call Control page.
The term layout is used to describe the various ways the
videos from the conference participants and a presentation
can appear on the screen. Different types of meetings may
require different layouts.
Navigate to: Call Control
Change the layout
Click Change layout, and choose
your preferred layout in the window
that opens.
The set of layouts to choose
from depends on the system
configurations.
You may change the layout while
in a call.
Whether or not snapshots of input sources are shown as illustrated,
depends on the sof tware version, configuration, and options installed
on the video system. Refer to the About snapshots and remote
monitoring sections (► TC7.3.3 or newer or ► TC7.3.0 to TC7.3.2).
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
20
Page 21
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
Controlling the far end camera
While in a call, you can control the remote participant’s
camera (far end) provided that:
• The Remote Monitoring option is installed on your video
system (software version TC7.3.3 and later).
• The Video AllowWebSnapshots setting is switched On
(software versions TC7.3.0 to TC7.3.2).
• Far end camera control (FECC) is enabled on the far end
system. Only the available controls will appear.
Navigate to: Call Control
Control the remote participant’s camera
1. Click the camera icon to open the
remote camera control window.
2. Use the left and right arrows to pan the
camera; the up and down arrows to tilt
it; and + and - to zoom in and out.
For software versions TC7.3.0 to
Whether or not snapshots of input sources are shown as illustrated,
depends on the sof tware version, configuration, and options installed
on the video system. Refer to the About snapshots and remote
monitoring sections (► TC7.3.3 or newer or ► TC7.3.0 to TC7.3.2).
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
TC7.3.2, the cursor must be in the
image to show the controls.
21
Page 22
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
Accessing call information
A call state indicator is available in the top bar in the web
interface. It shows whether the system is in a call or not, and
how many calls it is engaged in. You may also be notified
about incoming calls.
Call state indicator
The call state indicator is
available on all pages except
the Call Control page.
The badge indicates the number
of active calls. If the system is
idle, there is no badge.
Click the indicator to get more
details about connected calls.
Call control
Use these buttons to:
• Show call details
• Put the call on hold
• Disconnect the call
Incoming call notification
As default, a notification is given when the
system receives a call.
Check this box, if you do not want to receive
such notifications.
Opening the Call Control page
Click Open Call Control to go straight to the Call Control page.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
22
Page 23
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
System configuration
The system settings are grouped in several categories. When
you choose a category in the left pane all related settings
appear to the right
Each system setting is further described in the
► System settings c hapte r.
*
.
Navigate to: Configuration > System Configuration
All settings (including the value space) containing these letters will be highlighted.
Searching for settings
Enter as many letters as needed in the search field.
Selecting a category
The system settings are structured in categories.
Choose a category in order to display the related settings.
*
The configuration shown in the illustration serve as an example.
Your system may be configured dif ferently.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
23
Expanding and collapsing lists
Use these buttons to expand and
collapse all or individual lists.
Page 24
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
Changing system settings
All system settings can be changed from the System
Configuration page
either in a drop-down list or by text following the input field.
Different settings may require different user credentials. In
order to be sure that an administrator is able to change all
system settings, an administrator user must possess all user
roles.
You can read more about user administration and user roles
in the ► User administration chap ter.
*
. The value space for a setting is specified
Navigate to: Configuration > System Configuration
Drop-down list
Click the arrow to open the drop-down
list, and choose the preferred value.
Click Save for the change to take effect.
Text input field
*
The configuration shown in the illustration serve as an example.
Your system may be configured dif ferently.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
24
Enter new text in the input field.
Click Save for the change to take effect.
Page 25
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
System status
The system status is grouped in several categories. When
you choose a category in the left column, the related status
appears in the window to the right
*
.
Navigate to: Configuration > System Status
Selecting a category
The system status is structured in
categories. Choose a category in order
to display the related status information.
Searching for status entries
Enter as many letters as needed in the search field.
All entries (including the value space) containing these letters will be highlighted.
Expanding and collapsing lists
Use these buttons to expand and
collapse all or individual lists.
*
The status shown in the illustration serve as an example. The status
of your system may be different.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
25
Page 26
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
Managing the favorites list
The entries in the favorites list can be accessed from the
Touch controller and the Web interface.
Navigate to: Configuration > Local Contacts Management
Adding a contact
Click Add contact and fill in the form that
pops up. Then click Save to store the contact
in the Favorites list.
Editing contact details
Click a contacts name
followed by Edit contact.
Change the details in the form
as appropriate and click Save.
Import/Export contacts from file
Click Export to save the Local contacts in a file;
and click Import to bring in contacts from a file.
Note that all current contacts will be discarded
when importing new contacts from a file.
Storing a contact in a folder
Choose the appropriate folder
from the drop down list.
No folder means that the contact
will be stored at the top level.
Deleting a contact
Click a contacts name
followed by Edit contact. Then
click Delete to remove the
*
Note that only the first contact method appears in the Favorites list
on the Touch controller.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
entry from the Favorites list.
26
Adding a contact method*
You can store more than one
contact method for each contact,
e.g. video, telephone and mobile.
Page 27
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
Favorite list folders
The entries in the Favorites list can be organized in folders.
Navigate to: Configuration > Local Contacts Management
Adding a folder
Click Add folder and fill in the
form that pops up. Then click
Save to create the folder.
Opening a folder
Click the folder
name to open the
folder and show its
list of contacts.
Changing or Deleting a folder
Click Edit folder and update the
information in the form that pops up.
Then click Save to store the changes
Click Delete to remove the folder
and all its contacts and sub-folders.
Confirm your choice in the dialog that
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
27
pops up.
Page 28
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
Choosing a wallpaper
Your video system has a set of predefined wallpapers. The
wallpapers may be used as background on the display.
If you want the company logo or another custom picture as
background on the video display, you may upload and use a
custom wallpaper.
Navigate to: Configuration > Personalization
Activate/deactivate a wallpaper
Available wallpapers are represented by a miniature. If
you have uploaded a custom wallpaper, it will appear
in the list.
Click the miniature to switch to the corresponding
wallpaper. Choose None if you do not want a
wallpaper.
The chosen option is highlighted.
Upload a custom wallpaper
Click Brows e... and locate your custom wallpaper
image file.
Click Upload to save the file on the video system.
Supported file formats: BMP, GIF, JPEG, PNG
Maximum file size: 4 MByte
The custom wallpaper will be automatically
activated once uploaded.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
28
Delete the custom wallpaper
Click the delete symbol to remove the custom
wallpaper from the video system. Note that this
will remove the image file completely; you have to
upload it anew if you want to use it again.
You cannot delete a predefined wallpaper.
Page 29
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
Choosing a ringtone
You can choose from a set of predefined ringtones. The
chosen ringtone can be played back from this page.
The ringtone will be played back on the video system
itself, and not through the web interface.
Navigate to: Configuration > Personalization
Changing ringtone
Choose a ringtone from the drop-down list,
and click Save to make it the active ringtone.
Playing back the ringtone
Click the play button ( ► ) to play back the ringtone.
Use the stop button ( ) to end the playback.
Set the ringtone volume
Use the slide bar to adjust the ringtone volume.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
29
Page 30
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
Peripherals overview
This page shows an overview of devices that are connected
to the video system, like video inputs and outputs, cameras,
microphones, ISDN Links and Touch controllers
*
.
Navigate to: Configuration > Peripherals
Managing ISDN Link
If an ISDN Link is paired to the video system
it can be managed from this page.
How to configure and use the ISDN Link are
described in the ISDN Link documentation on
► http://www.cisco.com/go/isdnlink-docs
*
The peripherals shown in the illustration serve as examples. Your
system may have different peripherals and video input/output
configurations.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
30
Page 31
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
User administration
You can manage your video conference system’s user
accounts from this page.
(page 1 of 4)
The default user account
The system comes with a default administrator user account
with full access rights. The user name is admin and no
password is set.
It is mandatory to set a password for the admin us e r.
Read more about passwords in the ► Setting passwords
ch a pter.
About user roles
A user account must hold one or a combination of several
user roles.
The following three user roles, with non-overlapping rights,
exist:
• ADMIN: A user holding this role can create new users and
change most settings. The user neither can upload audit
certificates nor change the security audit settings.
• USER: A user holding this role can make calls and search
the phone book. The user can modify a few settings, e.g.
adjusting the ringtone volume and setting the time and
date format.
• AUDIT: A user holding this role can change the security
audit configurations and upload audit certificates.
Navigate to: Configuration > User Administration
Default user account
The system comes with
admin as the default user
account. This user has
full access rights.
An administrator user account with full access rights,
like the default admin user, must possess all the three
roles.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
31
Page 32
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
User administration
(page 2 of 4)
Creating a new user account
Follow these steps in order to create a new user account:
1. Click Add new user....
*
2. Fill in the Username and Password
appropriate user roles check boxes.
As a default the user has to change the password when
signing in for the first time.
Do not fill in the Client Certificate DN (Distinguished
Name) field unless you want to use certificate login on
HTTPS.
3. Set the Status to Active to activate the user.
4. Click Create User to save the changes.
Use the Back button to leave without making any
changes.
, and check the
Navigate to: Configuration > User Administration
*
The password is used with the web interface and command line
interface.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
32
Page 33
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
User administration
(page 3 of 4)
Changing user privileges
Follow these steps in order to change the user privileges:
1. Click the name of an existing user to open the Editing
user window.
2. Check the appropriate user roles check boxes, decide if
the user has to change the password on the next sign in,
and fill in the Client Certificate DN field if using certificate
login on HTTPS.
3. Click Update User to save the changes.
Use the Back button to leave without making any
changes.
Changing the password
Follow these steps in order to change the password*:
1. Click the name of an existing user to open the Editing
user window.
2. Enter the new password in the appropriate input fields.
3. Click Change Password to save the change.
Use the Back button to leave without making any
changes.
Navigate to: Configuration > User Administration
*
The password is used with the web interface and command line
interface.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
33
Page 34
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
User administration
(page 4 of 4)
Deactivating a user account
Follow these steps in order to deactivate a user account:
1. Click the name of an existing user to open the Editing
user window.
2. Set the Status to Inactive.
3. Click Update User to save the changes.
Use the Back button to leave without making any
changes.
Deleting a user account
Follow these steps in order to delete a user account:
1. Click the name of an existing user to open the Editing
user window.
2. Click Delete <user name>... and confirm when prompted.
Navigate to: Configuration > User Administration
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
34
Page 35
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
Adding a sign in banner
If a system administrator wants to provide initial information
to all users, he can create a sign in banner. The message will
be shown when the user signs in to the web interface and the
command line interface.
Navigate to: Configuration > Sign In Banner
Adding a sign in banner
Enter the message that you
want to present to the user
when signing in, and click
Save to activate the banner.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
35
Page 36
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
Managing the video system’s certificates
Certificate validation may be required when using TLS
(Transport Layer Security).
A server or client may require that your video system
presents a valid certificate to them before communication can
be set up.
The video system’s certificates are text files that verify the
authenticity of the system. These certificates may be issued
by a certificate authority (CA).
The certificates are listed as shown in the illustration to the
*
. They can be used for the following services: HTTPS
right
server, SIP, IEEE 802.1X and audit logging.
You can store several certificates on the system, but only one
certificate can be used for each service at a time.
If authentication fails, the connection will not be established.
Contact your system administrator to obtain the
following file(s):
• Certificate (file format: .PEM)
• Private key, either as a separate file or
included in the same file as the certificate
(file format: .PEM format)
• Password (required only if the private key is
encrypted)
The certificate and the private key will be stored in
the same file on the video system.
Navigate to: Configuration > Security: Certificates tab
Adding a certificate
1. Click Browse... and find the Certificate and
Private key file(s) on your computer.
2. Fill in the Password if required.
3. Click Add certificate... to store the certificate
on your system.
Enabling and disabling certificates
Use the buttons to switch a certificate on or off for
the different services.
You can also view a certificate, and delete a
certificate using the corresponding buttons.
*
The cer tificates and certificate issuers shown in the illustration
serve as examples. Your system may have other certificate(s).
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
36
Page 37
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
Managing the list of trusted certificate authorities
Certificate validation may be required when using TLS
(Transport Layer Security).
Your video system may be set up to require that a server
or client presents its certificate to the video system before
communication can be set up.
The certificates are text files that verify the authenticity of the
server or client. The certificates must be signed by a trusted
certificate authority (CA).
To be able to verify the signature of the certificates, a list of
trusted CAs must reside on the video system. The certificates
of the CAs are listed as shown in the illustration to the right
The list must include all CAs needed in order to verify
certificates for audit logging, HTTPS, SIP and IEEE 802.1X
connections.
If the server cannot be authenticated, the connection will not
be established.
(page 1 of 2)
*
.
Navigate to: Configuration > Security: CAs tab
Uploading a list of certificate authorities
The entries in a new file with CA cer tificates
will be appended to the existing list, so that
the previously stored certificates will not be
deleted.
i. Click Brows e... and find the file containing a
list of CA certificates (file format: .PEM) on
ii. Click the Add certificate authority... to store
the new CA certificate(s) on your system.
Viewing and deleting certificates
You can view a certificate, and
delete a certificate using the
corresponding buttons.
your computer.
Contact your system administrator to obtain
the CA certificate list (file format: .PEM).
*
The cer tificate and certificate issuers shown in the illustration serve
as examples. Your system will have other certificate(s).
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
37
Page 38
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
Managing the list of trusted
certificate authorities
As from software version TC7.2, the signature of an
audit server is verified using the same CA list as other
servers/clients.
Setting up secure audit logging
Audit logging records all sign in activity and configuration
changes on your video system.
Audit logging is disabled by default, but you can enable it
using the Security > Audit > Logging > Mode setting.
In ExternalSecure audit logging mode the video system
sends encrypted audit logs to an external audit server
(syslog server), which identity must be verified by a signed
certificate.
If the audit server cannot be authenticated, the logs will not
be sent.
Always upload the list of trusted certificate authorities
before enabling secure audit logging.
(page 2 of 2)
Navigate to: Configuration > Security: CAs tab / Configuration > System Configuration
iii
ii
i
Enable secure audit logging
i. Go to the System Configuration
page and choose the Security
category.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
38
ii. Enter the Address of the audit
server. If you choose Manual
PortAssignment, you must also
enter a Port number for the
audit server. Click Save for the
changes to take effect.
iii. Choose ExternalSecure from the
Logging Mode drop-down list.
Click Save for the change to take
effect.
Page 39
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
Managing pre-installed certificates for Edge provisioning
The list of pre-installed certificates that is shown on this
page in the web interface
used when the video system is provisioned by Cisco Unified
Communications Manager (CUCM) via Expressway (Edge).
Only Edge infrastructure certificates will be checked against
this list.
If the Edge infrastructure certificate validation fails, the video
system will not receive the provisioning and not be registered.
Factory resetting the video system will not delete the list of
pre-installed certificates.
*
, contains certificates that will be
Navigate to: Configuration > Security: Preinstalled CAs tab
Viewing or disabling certificates
You can view a certificate, and
disable a certificate using the
corresponding buttons.
You can disable all the preinstalled certificates, and use
a manually uploaded list of
certificates for verification instead.
See the Configuration > Security:
CAs page how to upload trusted
certificates to the video system
manually.
*
The cer tificate and certificate issuers shown in the illustration serve
as examples. Your system will have other certificate(s).
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
39
Page 40
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
Setting strong security mode
Strong security mode should be used only when compliance
with DoD JITC regulations is required.
Read the provided information carefully before setting
strong security mode.
Strong security mode sets very strict password requirements,
and requires all users to change their password on the next
sign in.
Navigate to: Configuration > Security: Strong Security Mode tab
Setting strong security mode
Read carefully about the consequences of
strong security mode before you continue.
1. If you want to use strong security mode,
click Enable strong security mode....
Confirm your choice in the dialog box
that appears.
The system will restart automatically.
2. Change the password when you are
prompted. The new password must meet
the strict criteria as described.
How to change the system password is
described in the ► Setting passwords
section.
Return to normal mode
When in strong security mode, the system
can be restored to normal mode by clicking
Disable strong security mode.... Confirm your
choice in the dialog box that appears
The system will restart automatically.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
40
Page 41
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
Changing the persistency mode
By default, all persistency settings are set to Persistent. This
means that configurations, call history, internal logs, local
phonebook / favorites list and IP connectivity information
are stored as normal. A system restart does not delete
information.
As a general rule, we recommend NOT to change the
default settings for persistency. But in the case were a
new user is not supposed to see or trace back to any kind
of logged information from the previous session, Non-
persistent mode must be used.
In order to clear/delete information that was stored
before changing to Non-persistent mode, you should
consider to factory reset the video system.
There is more information about performing a factory
reset in the ► Factory resetting appendix.
When in Non-persistent mode, the following information will
be lost/cleared each time the system restarts:
• System Configuration changes that have been made
since the last system restart.
• Information about calls that are placed or received since
the last system restart (call history).
• Internal log files that has been made since the last system
restart.
• Changes that are made to the local contacts / favorites
list since the last system restart.
• All IP related information (DHCP) from the last session.
Checking the persistency status
The radio buttons that are active when you open the Security
page and go to the Non-persistent Mode tab, shows the
current persistency status of the video system.
You can also see the status by checking Security >
Persistency on the Configuration > System Status page.
Navigate to: Configuration > Security: Non-persistent Mode tab
Changing the persistency settings
1. Set the persistency settings for the five
categories as desired.
2. Click Save and reboot....
The system will restart. After the
restart, behavior according to the new
persistency settings will start.
Note that logs, configurations etc. that
was stored before you switch to Nonpersistent mode, will not be cleared or
deleted.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
41
Page 42
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
Deleting trust lists (CUCM only)
The information on this page is only relevant for
video systems that are registered to a Cisco Unified
Communications Manager (CUCM).
The web interface can be used to delete existing trust lists
(CTL and ITL) that are stored on the video system. Normally,
you will not delete the old CTL and ITL files, but there are a
few cases when you will need to delete them.
The trust lists’ fingerprints and an overview of the certificates
in the lists are displayed on the web page. This information
can be useful for troubleshooting.
For more information about CUCM and trust lists, read the
Administering TC Endpoints on CUCM guide available on the
Cisco web site.
Navigate to: Configuration > Security: CUCM tab
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
42
Page 43
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
Troubleshooting
The troubleshooting page lists the status for some common
sources of errors. The list may be different for different
products and installations
Note that critical issues and errors are clearly marked in red
color; warnings are yellow.
*
.
Navigate to: Diagnostics > Troubleshooting
Run diagnostics
Click Re-run diagnostics to make sure
the information in the list is up-to-date.
Leave standby mode
This button is only visible when the
system is in standby mode. If in
standby mode, click Deactivate standby
to wake up the system.
*
The messages shown in the illustration serve as examples. Your
system may show other information.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
43
Page 44
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
Downloading log files
The log files* are Cisco specific debug files which may be
requested by the Cisco support organization if you need
technical support.
The current log files are time stamped event log files.
All current log files are archived in a time stamped historical
log file each time the system restarts. If the maximum
number of historical log files is reached, the oldest one will be
overwritten.
Navigate to: Diagnostics > Log Files
Downloading all log files
Click Download logs archive and follow
the instructions.
An anonymized call history is included in
the log files by default.
Use the drop down list if you want to
exclude the call history from the log files,
or if want to include the full call history
(non-anonymous caller/callee).
Open/save one log file
Click the file name to open the log file in
the web browser; right click to save the
file on the computer.
*
The log files shown in the illustration serve as examples. Your
system may have other f iles.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
44
Refresh the list of log files
Page 45
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
Starting extended logging
Extended logging mode may be switched on to help diagnose
network issues and problems during call setup. While in this
mode more information is stored in the log files.
Note that extended logging uses more of your video system’s
resources, and may cause your video system to underperform. You should only use extended logging mode when
troubleshooting an issue.
Navigate to: Diagnostics > Log Files
Start extended logging
Click Start extended logging.
Extended logging lasts for 10 minutes. You can stop
the extended logging before it times out by clicking
the Stop extended logging button that appears when
extended logging is on.
As default, the network traffic is not captured. Use the
drop down menu if you want to include a full or partial
capture of the network traffic.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
45
Page 46
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
Capturing user interface screenshots
You can capture screenshots both of a Touch controller that is
connected to the video system, and of the on-screen display
(menus, indicators and messages on the main display).
Navigate to: Diagnostics > User Interface Screenshots
Capture a screenshot
Click Take screenshot of Touch Panel to
capture a screenshot of the Touch controller,
or click Take screenshot of OSD to capture a
screenshot of the on-screen display.
The screenshot will display in the area below
the buttons. Note that it can take up to
30 seconds before the screenshot is ready.
All captured snapshots are included in the list
above the buttons. Click the screenshot ID to
display the image.
Deleting screenshots
If you want to delete all screenshots,
click Remove all.
To delete just one screenshot, click
button for that screenshot.
the
×
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
46
Page 47
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
Upgrading the system software
This video conference system is using TC software. The
version described in this document is TC7.3.
Contact your system administrator if you have
questions about the software version.
Software release notes
For a complete overview of the news and changes, we
recommend reading the Software Release Notes (TC7).
Go to: ► http://www.cisco.com/c/en/us/support/
collaboration-endpoints/telepresence-mx-series/tsdproducts-support-series-home.html
New software
For software download, go to the
Cisco Download Software web page:
► http://www.cisco.com/cisco/software/navigator.html.
Then navigate to your product.
The format of the file name is “s52000tc7_3_0.pkg” (each
software version has a unique file name).
Release key
You need a valid release key to be able to use the video
system. As from version TC6.1, any TC release key will do.
For older releases the release key is specific for each main
release (e.g. TC4, TC5, TC6).
Normally, you do not need to install the release key yourself.
The release key is preserved when you upgrade from an
earlier software version, and the release key is pre-installed
on new systems. As from TC7.0, it is no longer possible to
enter a release key from the web interface.
Navigate to: Maintenance > Software Upgrade
Install new software
Download the appropriate software package from the
Cisco Software Download web page (see link to the
left) and store it on your local computer. This is a .pkg
file.
i. Click Brows e... and find the downloaded .pkg file
that contains the new software.
ii. Click Install software to start the installation
process.
The complete installation may take up to 30minutes.
You can follow the progress on the web page. The
system restarts automatically after the installation.
You must sign in anew in order to continue
working with the web interface after the restart.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
47
Page 48
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
Adding option keys
Your video system may or may not have one or more
software options installed. In order to activate the optional
functionality the corresponding option key must be present
on the video system.
Option keys are not deleted when performing a software
upgrade or factory reset, so they need to be added only
once.
Each video system has unique option keys, for
example: 1R000-1-AA7A4A09
Contact your Cisco representative to obtain information about
available option keys, and how to get the required key(s).
Navigate to: Maintenance > Option Keys
Add an option key
i. Enter an Option Key in the
appropriate text input field.
ii. Click Add option key.
If you want to add more than one option
key, repeat these steps for all keys.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
48
Page 49
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
Backup and restore
All the system settings, which are available on the System
configuration page, can be listed on-screen or stored as a
text file.
The text file can be loaded back onto the system, thereby
restoring the configuration.
Navigate to: Maintenance > Backup and Restore
Backing up or showing the current configuration
Click Preview backup to display the current
settings on-screen.
Click Take backup to store the configuration
as a text file.
Restoring an earlier configuration
Click Brows e... and find the file with the
configuration you want to restore.
Click Restore to reconfigure the system as
defined in the file.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
49
Page 50
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
Reverting to the previously used software version
If there is a severe problem with the video system, switching
to the previously used software version may help solving the
problem.
If the system has not been factory reset since the last
software upgrade, the previously used software image still
resides on the system; you do not have to download the
software again.
Reverting to the previously used software version should only
be done by a system administrator or in contact with Cisco
technical support.
We strongly recommend that you backup your system’s log
files and configuration before you swap to the other software
image.
Navigate to: Maintenance > System Recovery: Backup tab and Software Recovery Swap tab
1. Backing up log files and
system configuration
We recommend that you backup your
system’s log files and configuration before
you swap to the other software image.
Click Download Logs and Download
Configuration Backup and follow the
instructions to save the files on your
computer.
2. Reverting to the previously used
software version
1. Revert to the previously used software
version by clicking Switch to software
TCx.y.z..., where x.y.z indicates the
software version.
2. Click Yes to confirm your choice, or
Cancel if you have changed your mind.
Wait while the system resets. The
system will restart automatically when
finished.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
50
Page 51
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
Factory reset
If there is a severe problem with the video system, the last
resort may be to reset it to its default factory settings. Always
consider reverting to the previously used software image
before performing a factory reset. In many situations this will
recover the system*.
A factory reset should only be performed by a system
administrator or in contact with Cisco technical support.
When factory resetting the video system the following
happens:
• The call logs will be deleted.
• Passwords will be reset to default.
• All system parameters will be reset to default values.
• All files that have been uploaded to the system will be
deleted. This includes, but is not limited to, custom
wallpapers, certificates and favorites list.
• The previous (inactive) software image will be deleted.
• Option keys and release keys will not be affected.
The system restarts automatically after the reset. It is using
the same software image as before.
We strongly recommend that you backup your system’s log
files and configuration before you perform a factory reset.
It is not possible to undo a factory reset.
Navigate to: Maintenance > System Recovery: Backup tab and Factory Reset tab
There is more information about performing a factory reset in
the ► Factory resetting appendix.
*
Read about software swapping in the ► Rever ting to the previously
used software version section.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
1. Backing up log files and
system configuration
We strongly recommend that you backup
your system’s log files and configuration
before you perform a factory reset;
otherwise these data will be lost.
Click Download Logs and Download
Configuration Backup and follow the
instructions to save the files on your
computer.
51
2. Performing a factory reset
Read the provided information carefully
before you click Perform a factory reset....
Click Yes to confirm your choice, or Cancel if
you have changed your mind.
Wait while the system resets. The system
will restart automatically when finished.
Page 52
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
Remote support user
In cases where you need to diagnose problems on the video
system you can create a remote support user.
The remote support user will be granted read access to the
system and will have access to a limited set of commands
that can aid troubleshooting.
You will need assistance from Cisco Technical Assistance
Center (TAC) to acquire the password for the remote
support user.
The remote support user should only be enabled
for troubleshooting reasons when instructed by
Ci sco TA C.
Navigate to: Maintenance > System Recovery: Remote Support User tab
Create remote support user
1. Open a case with Cisco TAC.
2. Click Create user.
3. Copy the text in the To ken field and
send to Cisco TAC.
4. Cisco TAC will generate a password.
The remote support user is valid for seven
days, or until it is deleted.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
52
Delete remote support user
Click Delete user.
Page 53
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interfaceWeb interface
Restarting the system
The system can be shut down or restarted remotely using the
web interface.
Navigate to: Maintenance > Restart
Restarting the system
Click Restart TelePresence device... to
restart the system.
It will take a few minutes before
the system is ready for use.
Shutting down the system
Click Shutdown TelePresence device...
to shut down the system.
The system cannot be turned on
again remotely; you must press
its power button physically to
turn it on.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
53
Page 54
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
Chapter 3
System settings
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
54
Page 55
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
Overview of the system settings
In the following pages you will find a complete list of the
system settings which are configured from the System
Configuration page on the web interface. The examples show
either the default value or an example of a value.
Open a web browser and enter the IP address of the video
system; then sign in.
To find the IP address (IPv4 orIPv6), open the
Settings
System Information.
* The Settings menu can be accessed from the drop down window
that appears when you tap the contact information in the upper, left
corner of the Touch controller.
*
menu on the Touch controller and tap
Audio settings ....................................................................... 58
Audio DefaultVolume............................................................... 58
Audio InternalSpeaker Mode................................................... 58
Audio Microphones Mute Enabled .......................................... 58
Audio SoundsAndAlerts KeyTones Mode ............................... 58
Audio SoundsAndAlerts RingTone .......................................... 58
Audio SoundsAndAlerts RingVolume...................................... 58
Audio Volume .......................................................................... 59
Cameras settings .................................................................. 60
Cameras Camera [1] Backlight ................................................ 60
Cameras Camera [1] Brightness Level .................................... 60
Cameras Camera [1] Brightness Mode ................................... 60
Cameras Camera [1] Flip ......................................................... 60
Cameras Camera [1] Focus Mode............................................61
Cameras Camera [1] Gamma Level .........................................61
Cameras Camera [1] Gamma Mode .........................................61
Cameras Camera [1] Mirror ......................................................61
Cameras Camera [1] Whitebalance Level ................................61
Cameras Camera [1] Whitebalance Mode ...............................61
Cameras PowerLine Frequency .............................................. 60
Cameras Preset TriggerAutofocus .......................................... 60
Conference settings ............................................................. 62
Conference [1..1] ActiveControl Mode .................................... 62
Conference [1..1] AutoAnswer Delay ....................................... 62
Conference [1..1] AutoAnswer Mode ...................................... 62
Conference [1..1] AutoAnswer Mute ........................................ 62
Conference [1..1] CallProtocolIPStack ..................................... 62
Conference [1..1] DefaultCall Protocol ..................................... 64
Conference [1..1] DefaultCall Rate ........................................... 64
Conference [1..1] DoNotDisturb DefaultTimeout ..................... 63
Conference [1..1] DoNotDisturb Mode .................................... 63
Conference [1..1] Encryption Mode ......................................... 64
Conference [1..1] FarEndControl Mode ................................... 63
Conference [1..1] FarEndControl SignalCapability ................... 63
Conference [1..1] IncomingMultisiteCall Mode ........................ 66
Conference [1..1] MaxReceiveCallRate ................................... 64
Conference [1..1] MaxTotalReceiveCallRate ............................ 65
Conference [1..1] MaxTotalTransmitCallRate ........................... 65
Conference [1..1] MaxTransmitCallRate ................................... 64
Conference [1..1] MicUnmuteOnDisconnect Mode ................. 63
Conference [1..1] Multipoint Mode .......................................... 66
Conference [1..1] Presentation OnPlacedOnHold ................... 66
Conference [1..1] Presentation RelayQuality ........................... 65
Conference [1..1] TelephonyPrefix........................................... 62
Conference [1..1] VideoBandwidth MainChannel Weight ........ 65
Conference [1..1] VideoBandwidth Mode ................................ 65
Conference [1..1] VideoBandwidth PresentationChannel
Weight
..................................................................................... 65
FacilityService settings ......................................................... 67
FacilityService Service [1..5] CallType .................................... 67
FacilityService Service [1..5] Name ........................................ 67
FacilityService Service [1..5] Number ..................................... 67
FacilityService Service [1..5] Type .......................................... 67
H323 settings ........................................................................ 68
H323 NAT Address ................................................................. 68
H323 NAT Mode ..................................................................... 68
H323 Profile [1..1] Authentication LoginName ......................... 68
H323 Profile [1..1] Authentication Mode .................................. 68
H323 Profile [1..1] Authentication Password ........................... 69
H323 Profile [1..1] CallSetup Mode .......................................... 69
H323 Profile [1..1] Encryption KeySize ................................... 69
H323 Profile [1..1] Gatekeeper Address .................................. 69
H323 Profile [1..1] Gatekeeper Discovery ................................ 69
H323 Profile [1..1] H323Alias E164 .......................................... 69
H323 Profile [1..1] H323Alias ID ............................................... 70
H323 Profile [1..1] Port Allocation ............................................. 70
Logging settings ....................................................................71
Logging Mode ..........................................................................71
Network settings ................................................................... 72
Network [1..1] DHCP RequestTFTPServerAddress ................. 73
Network [1..1] DNS Domain Name ........................................... 73
Network [1..1] DNS Server [1..3] Address ................................ 73
Network [1..1] IEEE8021X AnonymousIdentity ......................... 76
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
55
Page 56
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
Network [1..1] IEEE8021X Eap Md5 ......................................... 76
Network [1..1] IEEE8021X Eap Peap ........................................ 77
Network [1..1] IEEE8021X Eap Tls ............................................ 77
Network [1..1] IEEE8021X Eap Ttls ........................................... 77
Network [1..1] IEEE8021X Identity ............................................ 76
Network [1..1] IEEE8021X Mode .............................................. 75
Network [1..1] IEEE8021X Password ........................................ 76
Network [1..1] IEEE8021X TlsVerify .......................................... 76
Network [1..1] IEEE8021X UseClientCertificate ....................... 76
Network [1..1] IPStack .............................................................. 72
Network [1..1] IPv4 Address .................................................... 72
Network [1..1] IPv4 Assignment ............................................... 72
Network [1..1] IPv4 Gateway .................................................... 72
Network [1..1] IPv4 SubnetMask .............................................. 72
Network [1..1] IPv6 Address .................................................... 73
Network [1..1] IPv6 Assignment ............................................... 72
Network [1..1] IPv6 DHCPOptions ........................................... 73
Network [1..1] IPv6 Gateway .................................................... 73
Network [1..1] MTU .................................................................. 77
Network [1..1] QoS Diffserv Audio ............................................ 74
Network [1..1] QoS Diffserv Data .............................................. 74
Network [1..1] QoS Diffserv ICMPv6 ....................................... 75
Network [1..1] QoS Diffserv NTP ............................................. 75
Network [1..1] QoS Diffserv Signalling ..................................... 75
Network [1..1] QoS Diffserv Video ............................................ 74
Network [1..1] QoS Mode ......................................................... 74
Network [1..1] RemoteAccess Allow ........................................ 78
Network [1..1] Speed ............................................................... 77
Network [1..1] TrafficControl Mode .......................................... 77
Network [1..1] VLAN Voice Mode ............................................ 78
Network [1..1] VLAN Voice VlanId............................................ 78
NetworkServices settings ..................................................... 79
NetworkServices CDP Mode .................................................. 79
NetworkServices CTMS Encryption ....................................... 83
NetworkServices CTMS Mode ............................................... 82
NetworkServices H323 Mode ................................................ 79
NetworkServices HT TP Mode ................................................ 79
NetworkServices HT TPS Mode .............................................. 80
NetworkServices HT TPS OCSP Mode ................................... 80
NetworkServices HT TPS OCSP URL ......................................81
NetworkServices HTTPS VerifyClientCertificate .................... 80
NetworkServices HTTPS VerifyServerCertificate .................. 80
NetworkServices Medianet Metadata .....................................81
NetworkServices MultiWay Address ...................................... 80
NetworkServices MultiWay Protocol ...................................... 80
NetworkServices NTP Address ...............................................81
NetworkServices NTP Mode ...................................................81
NetworkServices SIP Mode .................................................... 79
NetworkServices SNMP CommunityName ............................ 82
NetworkServices SNMP Host [1..3] Address ...........................81
NetworkServices SNMP Mode ................................................81
NetworkServices SNMP SystemContact ............................... 82
NetworkServices SNMP SystemLocation .............................. 82
NetworkServices SSH AllowPublicKey ................................... 82
NetworkServices SSH Mode .................................................. 82
NetworkServices Telnet Mode ............................................... 79
NetworkServices WelcomeText .............................................. 79
NetworkServices XMLAPI Mode ............................................ 79
Peripherals settings .............................................................. 84
Peripherals Profile TouchPanels ............................................. 84
Phonebook settings .............................................................. 85
Phonebook Server [1..1] ID ...................................................... 85
Phonebook Server [1..1] Type ................................................. 85
Phonebook Server [1..1] URL .................................................. 85
Provisioning settings ............................................................. 86
Provisioning Connectivity ....................................................... 86
Provisioning ExternalManager Address .................................. 87
Provisioning ExternalManager AlternateAddress.................... 87
Provisioning ExternalManager Domain ................................... 87
Provisioning ExternalManager Path ........................................ 87
Provisioning ExternalManager Protocol .................................. 87
Provisioning HttpMethod ........................................................ 86
Provisioning LoginName ......................................................... 86
Provisioning Mode .................................................................. 86
Provisioning Password ............................................................ 86
RTP settings .......................................................................... 88
RTP Ports Range Start ............................................................ 88
RTP Ports Range Stop ............................................................ 88
Security settings ................................................................... 89
Security Audit Logging Mode ................................................. 89
Security Audit OnError Action ................................................. 89
Security Audit Server Address ............................................... 89
Security Audit Server Port ...................................................... 89
Security Audit Server PortAssignment ................................... 89
Security Session InactivityTimeout ......................................... 90
Security Session ShowLastLogon .......................................... 90
SerialPort settings ................................................................ 91
SerialPort BaudRate .................................................................91
SerialPort LoginRequired .........................................................91
SerialPort Mode .......................................................................91
SIP settings ........................................................................... 92
SIP ANAT ................................................................................ 92
SIP AuthenticateTransferror .................................................... 92
SIP ListenPort ......................................................................... 92
SIP OCSP DefaultResponder .................................................. 92
SIP OCSP Mode...................................................................... 92
SIP PreferredIPMedia .............................................................. 92
SIP PreferredIPSignaling ......................................................... 92
SIP Profile [1..1] Authentication [1..1] LoginName .................... 94
SIP Profile [1..1] Authentication [1..1] Password ....................... 94
SIP Profile [1..1] DefaultTransport ............................................ 94
SIP Profile [1..1] DisplayName.................................................. 94
SIP Profile [1..1] Ice DefaultCandidate ..................................... 93
SIP Profile [1..1] Ice Mode ........................................................ 93
SIP Profile [1..1] Line ................................................................ 95
SIP Profile [1..1] Mailbox .......................................................... 95
SIP Profile [1..1] Outbound ....................................................... 95
SIP Profile [1..1] Proxy [1..4] Address ....................................... 95
SIP Profile [1..1] Proxy [1..4] Discovery .................................... 95
SIP Profile [1..1] TlsVerify ......................................................... 94
SIP Profile [1..1] Turn BandwidthProbe .................................... 93
SIP Profile [1..1] Turn DiscoverMode ....................................... 93
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
56
Page 57
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
SIP Profile [1..1] Turn DropRflx ................................................. 93
SIP Profile [1..1] Turn Password ............................................... 94
SIP Profile [1..1] Turn Server .................................................... 93
SIP Profile [1..1] Turn UserName ............................................. 93
SIP Profile [1..1] Type ............................................................... 95
SIP Profile [1..1] URI ................................................................. 94
Standby settings ................................................................... 96
Standby BootAction ................................................................ 96
Standby Control ...................................................................... 96
Standby Delay ......................................................................... 96
Standby StandbyAction .......................................................... 96
Standby WakeupAction ........................................................... 96
SystemUnit settings .............................................................. 97
SystemUnit CallLogging Mode ............................................... 97
SystemUnit ContactInfo Type ................................................. 97
SystemUnit MenuLanguage .................................................... 97
SystemUnit Name ................................................................... 97
Time settings ........................................................................ 98
Time DateFormat .................................................................... 98
Time OlsonZone ..................................................................... 99
Time TimeFormat .................................................................... 98
Time Zone ............................................................................... 98
UserInterface settings ..........................................................101
UserInterface TouchPanel DefaultPanel ................................101
UserInterface UserPreferences .............................................101
Video settings ......................................................................102
Video AllowWebSnapshots ................................................... 102
Video CamCtrlPip CallSetup Duration .................................. 102
Video CamCtrlPip CallSetup Mode ....................................... 102
Video ControlPanel Brightness ............................................. 102
Video DefaultPresentationSource ......................................... 102
Video Input DVI [1] RGBQuantizationRange........................... 10 3
Video Input DVI [1] Type ........................................................ 103
Video Input Source [1..2] CameraControl CameraId ............. 104
Video Input Source [1..2] CameraControl Mode ................... 104
Video Input Source [1..2] Name ............................................ 103
Video Input Source [1..2] OptimalDefinition Profile ............... 105
Video Input Source [1..2] OptimalDefinition Threshold60fps 105
Video Input Source [1..2] PresentationSelection ................... 104
Video Input Source [1..2] Quality ........................................... 10 5
Video Input Source [1..2] Type .............................................. 104
Video Input Source [1..2] Visibility ......................................... 104
Video Input Source [1] Connector ......................................... 103
Video Input Source [2] Connector ......................................... 103
Video Layout DisableDisconnectedLocalOutputs ................. 106
Video Layout LocalLayoutFamily .......................................... 106
Video Layout PresentationDefault View ................................ 106
Video Layout RemoteLayoutFamily ........................................107
Video Layout ScaleToFrame ..................................................107
Video Layout ScaleToFrameThreshold ...................................107
Video Layout Scaling .............................................................107
Video MainVideoSource ....................................................... 106
Video Monitors ...................................................................... 109
Video OSD AutoSelectPresentationSource ...........................110
Video OSD CallSettingsSelection .......................................... 110
Video OSD EncryptionIndicator .............................................110
Video OSD InputMethod Cyrillic ............................................ 110
Video OSD InputMethod InputLanguage ...............................11 0
Video OSD LanguageSelection ............................................ 109
Video OSD LoginRequired .....................................................11 0
Video OSD MenuStartupMode ............................................. 109
Video OSD MissedCallsNotification ....................................... 110
Video OSD Mode .................................................................. 109
Video OSD MyContactsExpanded ......................................... 110
Video OSD Output .................................................................110
Video OSD TodaysBookings .................................................. 110
Video OSD VirtualKeyboard .................................................. 10 9
Video OSD WallpaperSelection ............................................ 10 9
Video Output Internal [2] MonitorRole .................................... 111
Video Output LCD [1] Blue ..................................................... 111
Video Output LCD [1] Brightness ...........................................110
Video Output LCD [1] Green ................................................... 111
Video Output LCD [1] MonitorRole .........................................110
Video Output LCD [1] Red ...................................................... 111
Video Output LCD [1] Resolution ............................................ 110
Video PIP ActiveSpeaker DefaultValue Position ................... 108
Video PIP Presentation DefaultValue Position ...................... 108
Video Selfview ...................................................................... 108
Video SelfviewDefault FullscreenMode ................................ 108
Video SelfviewDefault Mode ................................................. 108
Video SelfviewDefault OnMonitorRole .................................. 109
Video SelfviewDefault PIPPosition ........................................ 10 9
Video WallPaper.....................................................................111
Experimental settings .......................................................... 112
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
57
Page 58
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
Audio settings
Audio InternalSpeaker Mode
Set the internal loudspeaker mode.
Requires user role: ADMIN
Value space: <Off/On>
Off: The internal speakers are disabled.
On: The internal speakers are enabled.
Example:
Audio InternalSpeaker Mode: On
Audio Microphones Mute Enabled
Determine whether audio-mute is allowed or not. The default value is True.
Requires user role: ADMIN
Value space: <True/InCallOnly>
Tru e: Muting of audio is always available.
InCallOnly: Muting of audio is only available when the device is in a call. When Idle it is not
possible to mute the microphone. This is useful when an external telephone service/audio
system is connected via the codec and is to be available when the codec is not in a call.
When set to InCallOnly this will prevent the audio-system from being muted by mistake.
Example:
Audio Microphones Mute Enabled: True
Audio SoundsAndAlerts KeyTones Mode
The system can be configured to make a keyboard click sound effect (key tone) when typing
text or numbers on the Touch controller.
Requires user role: USER
Value space: <Off/On>
Off: No key tones will be played when you type.
On: You will hear key tones when you type.
Example:
Audio SoundsAndAlerts KeyTones Mode: Off
Audio SoundsAndAlerts RingTone
This setting defines which ringtone to use for incoming calls. You need to enter the exact name
of the ringtone. You can find the available ringtones the following ways.
Web interface: On the Configuration > Personalization page.
Touch controller: On the Ringtone & Sound panel of the Settings menu. This panel is either
in the open part of the Settings menu, or included in the password protected Administrator
menu. The UserInterface UserPreference setting defines which panels will be in the password
protected area.
Requires user role: USER
Value space: <S: 1, 100>
Format: String with a maximum of 100 characters.
Example:
Audio SoundsAndAlerts RingTone: "Sunrise"
Audio SoundsAndAlerts RingVolume
Sets the ring volume for an incoming call.
Requires user role: USER
Value space: <0..100>
Range: The value goes in steps of 5 from 0 to 100 (from -34.5 dB to 15 dB). Volume 0 = Off.
Example:
Audio SoundsAndAlerts RingVolume: 50
Audio DefaultVolume
Set the default speaker volume. The volume returns to this value when you switch on or restart
the video system. Use the Touch controller to change the volume while the video system is
running.
Requires user role: USER
Value space: <0..100>
Range: The value must be between 0 and 100. The values from 1 to 100 correspond to the
range from -34.5 dB to 15 dB (0.5 dB steps). The value 0 means that the audio is switched
off.
Example:
Audio D efaultVolu m e: 50
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
58
Page 59
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
Audio Volume
Set the speaker volume. This setting is obsoleted by the Audio DefaultVolume setting.
Requires user role: USER
Value space: <0..100>
Range: The value must be between 0 and 100. The values from 1 to 100 correspond to the
range from -34.5 dB to 15 dB (0.5 dB steps). The value 0 means that the audio is switched
off.
Example:
Audio Volume: 50
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
59
Page 60
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
Cameras settings
Cameras PowerLine Frequency
The video system's camera is able to compensate for any flicker noise from the electrical power
supply (power line frequency anti-flickering). Set this camera configuration based on your
power line frequency. The default value is 50Hz, so you should change this setting if your power
line frequency is 60 Hz.
Requires user role: ADMIN
Value space: <50Hz/60Hz>
50Hz: Use this value when the power line frequency is 50 Hz.
60Hz: Use this value when the power line frequency is 60 Hz.
Example:
Cameras PowerLine Frequency: 50Hz
Cameras Preset TriggerAutofocus
The current position (pan and tilt), zoom and focus are stored with a preset. Use this setting to
determine if the camera should refocus or use the focus value that is stored with the preset.
Requires user role: ADMIN
Value space: <Auto/Off/On>
Auto: Whether the camera refocuses or not when selecting a preset, depends on the
camera type.
Off: The focus value that is stored with the preset will be used. The camera will not refocus
when selecting a preset.
On: The camera will refocus when selecting a preset. The focus value that is stored with the
preset may be overridden.
Example:
Cameras Preset TriggerAutofocus: Auto
Cameras Camera [1] Backlight
This configuration turns backlight compensation on or off. Backlight compensation is useful
when there is much light behind the persons in the room. Without compensation the persons
will easily appear very dark to the far end.
Requires user role: ADMIN
Value space: <Off/On>
Off: Turn off the camera backlight compensation.
On: Turn on the camera backlight compensation.
Example:
Cameras Camera 1 Backlight: Off
Cameras Camera [1] Brightness Mode
Set the camera brightness mode.
Requires user role: ADMIN
Value space: <Auto/Manual>
Auto: The camera brightness is automatically set by the system.
Manual: Enable manual control of the camera brightness. The brightness level is set using
the Cameras Camera Brightness Level setting.
Example:
Cameras Camera 1 Brightness Mode: Auto
Cameras Camera [1] Brightness Level
Set the brightness level. Requires the Camera Brightness Mode to be set to Manual.
Requires user role: ADMIN
Value space: <1..31>
Range: Select a value between 1 and 31.
Example:
Cameras Camera 1 Brightness Level: 20
Cameras Camera [1] Flip
Not applicable for this product.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
60
Page 61
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
Cameras Camera [1] Focus Mode
Set the camera focus mode.
Requires user role: ADMIN
Value space: <Auto/Manual>
Auto: The camera will auto focus once a call is connected, as well as after moving the
camera (pan, tilt, zoom). The system will use auto focus only for a few seconds to set the
right focus; then auto focus is turned off to prevent continuous focus adjustments of the
camera.
Manual: Turn the autofocus off and adjust the camera focus manually.
Example:
Cameras Camera 1 Focus Mode: Auto
Cameras Camera [1] Gamma Mode
This setting enables gamma corrections. Gamma describes the nonlinear relationship between
image pixels and monitor brightness.
Requires user role: ADMIN
Value space: <Auto/Manual>
Auto: Auto is the default and the recommended setting.
Manual: In manual mode the gamma value is changed with the gamma level setting, ref:
Cameras Camera [1..n] Gamma Level.
Example:
Cameras Camera 1 Gamma Mode: Auto
Cameras Camera [1] Gamma Level
By setting the Gamma Level you can select which gamma correction table to use. This setting
may be useful in difficult lighting conditions, where changes to the brightness setting does not
provide satisfactory results. Requires the Gamma Mode to be set to Manual.
Requires user role: ADMIN
Value space: <0..7>
Range: Select a value between 0 and 7.
Example:
Cameras Camera 1 Gamma Level: 0
Cameras Camera [1] Whitebalance Mode
Set the camera white balance mode.
Requires user role: ADMIN
Value space: <Auto/Manual>
Auto: The camera will continuously adjust the white balance depending on the camera view.
Manual: Enables manual control of the camera white balance. The white balance level is set
using the Cameras Camera Whitebalance Level setting.
Example:
Cameras Camera 1 Whitebalance Mode: Auto
Cameras Camera [1] Whitebalance Level
Set the white balance level. Requires the Camera Whitebalance Mode to be set to manual.
Requires user role: ADMIN
Value space: <1..16>
Range: Select a value between 1 and 16.
Example:
Cameras Camera 1 Whitebalance Level: 1
Cameras Camera [1] Mirror
Not applicable for this product.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
61
Page 62
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
Conference settings
Conference [1..1] ActiveControl Mode
Active control is a feature that allows conference participants to administer a conference on
Cisco TelePresence Server using the video system's interfaces (not available from the TRC5
remote control and on-screen display). Each user can see the participant list, change video
layout, disconnect participants, etc. from the interface. The active control feature is enabled
by default, provided that it is supported by the infrastructure (Cisco Unified Communications
Manager (CUCM) version 9.1.2 or newer, Cisco TelePresence Video Communication Server
(VCS) version X8.1 or newer). Change this setting if you want to disable the active control
features.
Requires user role: ADMIN
Value space: <Auto/Off>
Auto: Active control is enabled when supported by the infrastructure.
Off: Active control is disabled.
Example:
Conference ActiveControl Mode: Auto
Conference [1..1] CallProtocolIPStack
Select if the system should enable IPv4, IPv6, or dual IP stack on the call protocol (SIP, H323).
Requires user role: ADMIN
Value space: <Dual/IPv4/IPv6>
Dual: Enables both IPv4 and IPv6 for the call protocol.
IPv4: When set to IPv4, the call protocol will use IPv4.
IPv6: When set to IPv6, the call protocol will use IPv6.
Example:
Conference 1 CallProtocolIPStack: Dual
Conference [1..1] TelephonyPrefix
Enter the prefix to be used for telephony calls.
Requires user role: ADMIN
Value space: <S: 0, 80>
Format: String with a maximum of 80 characters.
Example:
Conference 1 TelephonyPrefix: "520"
Conference [1..1] AutoAnswer Mode
Set the auto answer mode. Use the Conference AutoAnswer Delay setting if you want the
system to wait a number of seconds before answering the call, and use the Conference
AutoAnswer Mute setting if you want your microphone to be muted when the call is answered.
Requires user role: ADMIN
Value space: <Off/On>
Off: You must answer incomming calls manually by tapping Answer on the Touch controller.
On: The system automatically answers incoming calls, except if you are already in a call. You
must always answer or decline incoming calls manually when you are already engaged in a
call.
Example:
Conference 1 AutoAnswer Mode: Off
Conference [1..1] AutoAnswer Mute
Determine if the microphone shall be muted when an incoming call is automatically answered.
Requires that AutoAnswer Mode is switched on.
Requires user role: ADMIN
Value space: <Off/On>
Off: The incoming call will not be muted.
On: The incoming call will be muted when automatically answered.
Example:
Conference 1 AutoAnswer Mute: Off
Conference [1..1] AutoAnswer Delay
Define how long (in seconds) an incoming call has to wait before it is answered automatically by
the system. Requires that AutoAnswer Mode is switched on.
Requires user role: ADMIN
Value space: <0..50>
Range: Select a value between 0 and 50 seconds.
Example:
Conference 1 AutoAnswer Delay: 0
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
62
Page 63
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
Conference [1..1] MicUnmuteOnDisconnect Mode
Determine if the microphones shall be unmuted automatically when all calls are disconnected.
In a meeting room or other shared resources this may be done to prepare the system for the
ne x t user.
Requires user role: ADMIN
Value space: <Off/On>
Off: If muted during a call, let the microphones remain muted after the call is disconnected.
On: Unmute the microphones after the call is disconnected.
Example:
Conference 1 MicUnmuteOnDisconnect Mode: On
Conference [1..1] DoNotDisturb Mode
Determine whether to allow incoming calls.
Requires user role: USER
Value space: <Off/On/Timed>
Off: The incoming calls will come through as normal.
On: All incoming calls will be rejected and they will be registered as missed calls. The calling
side will receive a busy signal. A message telling that Do Not Disturb is switched on will
display on the Touch controller or main display. NOTE: This setting is not recommended as
all calls will be rejected until the setting is manually turned off. The recommended option is
Timed.
Timed: When set to timed (default), the system will revert back and allow incoming calls after
the specified timeout, defined by the setting: Conference DoNotDisturb DefaultTimeout.
Example:
Conference 1 DoNotDisturb Mode: Timed
Conference [1..1] FarEndControl Mode
Lets you decide if the remote side (far end) should be allowed to select your video sources and
control your local camera (pan, tilt, zoom).
Requires user role: ADMIN
Value space: <Off/On>
Off: The far end is not allowed to select your video sources or to control your local camera
(pan, tilt, zoom).
On: Allows the far end to be able to select your video sources and control your local camera
(pan, tilt, zoom). You will still be able to control your camera and select your video sources
as normal.
Example:
Conference 1 FarEndControl Mode: On
Conference [1..1] FarEndControl SignalCapability
Set the far end control (H.224) signal capability mode.
Requires user role: ADMIN
Value space: <Off/On>
Off: Disable the far end control signal capability.
On: Enable the far end control signal capability.
Example:
Conference 1 FarEndControl SignalCapability: On
Conference [1..1] DoNotDisturb DefaultTimeout
This setting determines the default duration of a Do Not Disturb session, i.e. the period when
incoming calls are rejected and registered as missed calls. The session can be terminated
earlier by using the user interface (Touch controller) or the Conference DoNotDisturb Mode
setting. The default value is 60 minutes.
Requires user role: ADMIN
Value space: <0..1440>
Range: Select the number of minutes (between 0 and 1440, i.e. 24 hours) before the Do Not
Disturb session times out automatically.
Example:
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
Conference 1 DoNotDisturb DefaultTimeOut: 60
63
Page 64
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
Conference [1..1] Encryption Mode
Define the conference encryption mode. A padlock with the text "Encryption On" or
"Encryption Off" displays on screen for a few seconds when the conference starts.
NOTE: If the TC-NC software (no crypto) is installed on the video system, the encryption mode
is always Off.
Requires user role: ADMIN
Value space: <Off/On/BestEffort>
Off: The system will not use encryption.
On: The system will only allow calls that are encrypted.
BestEffort: The system will use encryption whenever possible.
> In Point to point calls: If the far end system supports encryption (AES-128), the call will be
encrypted. If not, the call will proceed without encryption.
> In MultiSite calls: In order to have encrypted MultiSite conferences, all sites must support
encryption. If not, the conference will be unencrypted.
Example:
Conference 1 Encryption Mode: BestEffort
Conference [1..1] DefaultCall Protocol
Set the Default Call Protocol to be used when placing calls from the system.
Requires user role: ADMIN
Value space: <Auto/H323/Sip/H320>
Auto: Enables auto-selection of the call protocol based on which protocols are available.
If multiple protocols are available, the order of priority is: 1) SIP; 2) H323; 3) H320. If the
system cannot register, or the call protocol is not enabled, the auto-selection chooses H323.
H323: All calls are set up as H.323 calls.
Sip: All calls are set up as SIP calls.
H320: All calls are set up as H.320 calls (only applicable if connected to a Cisco
TelePresence ISDN Link gateway).
Example:
Conference 1 DefaultCall Protocol: Auto
Conference [1..1] DefaultCall Rate
Set the Default Call Rate to be used when placing calls from the system.
Requires user role: ADMIN
Value space: <64..6000>
Range: Select a value between 64 and 6000 kbps.
Example:
Conference 1 DefaultCall Rate: 1920
Conference [1..1] MaxTransmitCallRate
Specify the maximum transmit bit rate to be used when placing or receiving calls. Note that this
is the maximum bit rate for each individual call; use the Conference MaxTotalTransmitCallRate
setting to set the aggregated maximum for all simultaneous active calls.
Requires user role: ADMIN
Value space: <64..6000>
Range: Select a value between 64 and 6000 kbps.
Example:
Conference 1 MaxTransmitCallRate: 6000
Conference [1..1] MaxReceiveCallRate
Specify the maximum receive bit rate to be used when placing or receiving calls. Note that this
is the maximum bit rate for each individual call; use the Conference MaxTotalReceiveCallRate
setting to set the aggregated maximum for all simultaneous active calls.
Requires user role: ADMIN
Value space: <64..6000>
Range: Select a value between 64 and 6000 kbps.
Example:
Conference 1 MaxReceiveCallRate: 6000
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
64
Page 65
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
Conference [1..1] MaxTotalTransmitCallRate
This configuration applies when using a video system's built-in MultiSite feature (optional) to
host a multipoint video conference.
Specify the maximum overall transmit bit rate allowed. The bit rate will be divided fairly among
all active calls at any time. This means that the individual calls will be up-speeded or downspeeded as appropriate when someone leaves or enters a multipoint conference, or when a call
is put on hold (suspended) or resumed.
The maximum transmit bit rate for each individual call is defined in the Conference
MaxTransmitCallRate setting.
Requires user role: ADMIN
Value space: <64..10000>
Range: Select a value between 64 and 10000.
Example:
Conference 1 MaxTotalTransm itCallRate: 10000
Conference [1..1] MaxTotalReceiveCallRate
This configuration applies when using a video system's built-in MultiSite feature (optional) to
host a multipoint video conference.
Specify the maximum overall receive bit rate allowed. The bit rate will be divided fairly among
all active calls at any time. This means that the individual calls will be up-speeded or downspeeded as appropriate when someone leaves or enters a multipoint conference, or when a call
is put on hold (suspended) or resumed.
The maximum receive bit rate for each individual call is defined in the Conference
MaxReceiveCallRate setting.
Requires user role: ADMIN
Value space: <64..10000>
Range: Select a value between 64 and 10000.
Example:
Conference 1 MaxTotalReceiveCallRate: 10000
Conference [1..1] VideoBandwidth Mode
Set the conference video bandwidth mode.
Requires user role: ADMIN
Value space: <Dynamic/Static>
Dynamic: The available transmit bandwidth for the video channels are distributed among the
currently active channels. If there is no presentation, the main video channels will use the
bandwidth of the presentation channel.
Static: The available transmit bandwidth is assigned to each video channel, even if it is not
active.
Example:
Conference 1 VideoBandwidth Mode: Dynamic
Conference [1..1] VideoBandwidth MainChannel Weight
The available transmit video bandwidth is distributed on the main channel and presentation
channel according to "MainChannel Weight" and "PresentationChannel Weight". If the main
channel weight is 2 and the presentation channel weight is 1, then the main channel will use
twice as much bandwidth as the presentation channel.
Requires user role: ADMIN
Value space: <1..1 0 >
Range: 1 to 10.
Example:
Conference 1 VideoBandwidth MainChannel Weight: 5
Conference [1..1] VideoBandwidth PresentationChannel Weight
The available transmit video bandwidth is distributed on the main channel and presentation
channel according to "MainChannel Weight" and "PresentationChannel Weight". If the main
channel weight is 2 and the presentation channel weight is 1, then the main channel will use
twice as much bandwidth as the presentation channel.
Requires user role: ADMIN
Value space: <1..1 0 >
Range: 1 to 10.
Example:
Conference 1 VideoBandwidth PresentationChannel Weight: 5
Conference [1..1] Presentation RelayQuality
Not applicable in this version.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
65
Page 66
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
Conference [1..1] Presentation OnPlacedOnHold
Define whether or not to continue sharing a presentation after the remote site has put you on
hold.
Requires user role: ADMIN
Value space: <Stop/NoAction>
Stop: The video system stops the presentation sharing when the remote site puts you on
hold. The presentation will not continue when the call is resumed.
NoAction: The video system will not stop the presentation sharing when put on hold. The
presentation will not be shared while you are on hold, but it will continue automatically when
the call is resumed.
Example:
Conference 1 Presentation OnPlacedOnHold: NoAction
Conference [1..1] Multipoint Mode
Define how the video system handles multiparty video conferences.
If registered to a Cisco TelePresence Video Communication Ser ver (VCS), the video system
can use the MultiWay network solution. MultiWay requires that the video network includes
a multipoint control unit (MCU). If registered to a Cisco Unified Communications Manager
(CUCM), the video system can use the CUCM conference bridge. Both MultiWay and the CUCM
conference bridge allows you to set up conferences with many par ticipants.
Requires user role: ADMIN
Value space: <Auto/Off/MultiWay/CUCMMediaResourceGroupList>
Auto: The multipoint method available will be choosen automatically; if none are available the
Multipoint Mode will automatically be set to Off.
Off: Multiparty conferences are not allowed.
MultiWay: Multiparty conferences are set up using the MultiWay service. If MultiWay is
chosen when the MultiWay service is not available, the Multipoint Mode will automatically be
set to Off. This may occur when the NetworkSer vices MultiWay Address setting is empty or
not properly set.
CUCMMediaResourceGroupList: Multiparty conferences (ad hoc conferences) will be hosted
by the CUCM configured conference bridge. This setting is provisioned by CUCM in a CUCM
environment and should never be set manually by the user.
Example:
Conference 1 Multipoint Mode: Auto
Conference [1..1] IncomingMultisiteCall Mode
Select whether or not to allow incoming calls when already in a call/conference.
Requires user role: ADMIN
Value space: <Allow/Deny>
Allow: You will be notified when someone calls you while you are already in a call. You can
accept the incoming call or not. The ongoing call may be put on hold while answering the
incoming call; or you may merge the calls (requires MultiSite or MultiWay support).
Deny: An incoming call will be rejected if you are already in a call. You will not be notified
about the incoming call. However, the call will appear as a missed call in the call history list.
Example:
Conference 1 IncomingMultisiteCall Mode: Allow
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
66
Page 67
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
FacilityService settings
FacilityService Service [1..5] Type
Up to five different facility services can be supported simultaneously. With this setting you
can select what kind of services they are. A facility service is not available unless both the
FacilityService Service Name and the FacilityService Service Number settings are properly set.
Only FacilityService Service 1 with Type Helpdesk is available on the Touch controller; the other
options are available for system integrators using the API (Application Programming Interface)
command set.
Requires user role: ADMIN
Value space: <Other/Concierge/Helpdesk/Emergency/Security/Catering/Transportation>
Other: Select this option for services not covered by the other options.
Concierge: Select this option for concierge services.
Helpdesk: Select this option for helpdesk services.
Emergency: Select this option for emergency services.
Security: Select this option for security services.
Catering: Select this option for catering services.
Transportation: Select this option for transportation services.
Example:
FacilityService Service 1 Type: Helpdesk
FacilityService Service [1..5] Name
Enter the name of the facility service. Up to five different facility services are supported.
A facility service is not available unless both the FacilityService Service Name and the
FacilityService Service Number settings are properly set. Only FacilityService Service 1 is
available on the Touch controller. The name will show on the facility ser vice call button, which
appears when you tap the question mark icon in the top bar. The other services are available for
system integrators using the API (Application Programming Interface) command set.
Requires user role: ADMIN
Value space: <S: 0, 1024>
Format: String with a maximum of 1024 characters.
Example:
FacilityService Service 1 Name: ""
FacilityService Service [1..5] Number
Enter the number (URI or phone number) of the facility service. Up to five different facility
services are supported. A facility service is not available unless both the FacilityService Service
Name and the FacilityService Ser vice Number settings are properly set. Only FacilityService
Service 1 is available on the Touch controller; the other options are available for system
integrators using the API (Application Programming Interface) command set.
Requires user role: ADMIN
Value space: <S: 0, 1024>
Format: String with a maximum of 1024 characters.
Example:
FacilityService Service 1 Number: ""
FacilityService Service [1..5] CallType
Set the call type for each facility service. Up to five different facility services are supported.
A facility service is not available unless both the FacilityService Service Name and the
FacilityService Service Number settings are properly set. Only FacilityService Service 1 is
available on the Touch controller; the other options are available for system integrators using
the API (Application Programming Interface) command set.
Requires user role: ADMIN
Value space: <Video/Audio>
Video: Select this option for video calls.
Aud io: Select this option for audio calls.
Example:
FacilityService Service 1 CallType: Video
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
67
Page 68
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
H323 settings
H323 NAT Mode
The firewall traversal technology creates a secure path through the firewall barrier, and enables
proper exchange of audio/video data when connected to an external video conferencing
system (when the IP traffic goes through a NAT router). NOTE: NAT does not work in
conjunction with gatekeepers.
Requires user role: ADMIN
Value space: <Auto/Off/On>
Auto: The system will determine if the H323 NAT Address or the real IP address should be
used in signaling. This makes it possible to place calls to endpoints on the LAN as well as
endpoints on the WAN. If the H323 NAT Address is wrong or not set, the real IP address will
be used.
Off: The system will signal the real IP address.
On: The system will signal the configured H323 NAT Address instead of its real IP address
in Q.931 and H.245. The NAT Server Address will be shown in the startup-menu as: "My IP
Address: 10.0.2.1". If the H323 NAT Address is wrong or not set, H.323 calls cannot be set
up.
Example:
H323 NAT Mode: Off
H323 NAT Address
Enter the external/global IP address to the router with NAT support. Packets sent to the
router will then be routed to the system. Note that NAT cannot be used when registered to a
gatekeeper.
In the router, the following ports must be routed to the system's IP address:
* Port 1720
* Port 5555-6555
* Port 2326-2487
Requires user role: ADMIN
Value space: <S: 0, 64>
Format: A valid IPv4 address or IPv6 address.
Example:
H323 NAT Address: ""
H323 Profile [1..1] Authentication Mode
Set the authentication mode for the H.323 profile.
Requires user role: ADMIN
Value space: <Off/On>
Off: If the H.323 Gatekeeper Authentication Mode is set to Off the system will not try to
authenticate itself to a H.323 Gatekeeper, but will still try a normal registration.
On: If the H.323 Gatekeeper Authentication Mode is set to On and a H.323 Gatekeeper
indicates that it requires authentication, the system will try to authenticate itself to the
gatekeeper. Requires the Authentication LoginName and Authentication Password to be
defined on both the codec and the Gatekeeper.
Example:
H323 Profile 1 Authentication Mode: Off
H323 Profile [1..1] Authentication LoginName
The system sends the Authentication Login Name and the Authentication Password to a H.323
Gatekeeper for authentication. The authentication is a one way authentication from the codec
to the H.323 Gatekeeper, i.e. the system is authenticated to the gatekeeper. If the H.323
Gatekeeper indicates that no authentication is required, the system will still tr y to register.
Requires the H.323 Gatekeeper Authentication Mode to be enabled.
Requires user role: ADMIN
Value space: <S: 0, 50>
Format: String with a maximum of 50 characters.
Example:
H323 Profile 1 Authentication LoginName: ""
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
68
Page 69
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
H323 Profile [1..1] Authentication Password
The system sends the Authentication Login Name and the Authentication Password to a H.323
Gatekeeper for authentication. The authentication is a one way authentication from the codec
to the H.323 Gatekeeper, i.e. the system is authenticated to the gatekeeper. If the H.323
Gatekeeper indicates that no authentication is required, the system will still tr y to register.
Requires the H.323 Gatekeeper Authentication Mode to be enabled.
Requires user role: ADMIN
Value space: <S: 0, 50>
Format: String with a maximum of 50 characters.
Example:
H323 Profile 1 Authentication Password: ""
H323 Profile [1..1] CallSetup Mode
The H.323 Call Setup Mode defines whether to use a Gatekeeper or Direct calling when
establishing H323 calls.
NOTE: Direct H.323 calls can be made even though the H.323 Call Setup Mode is set to
Gatekeeper.
Requires user role: ADMIN
Value space: <Direct/Gatekeeper>
Direct: An IP address must be used when dialing in order to make the H323 call.
Gatekeeper: The system will use a Gatekeeper to make a H.323 call. When selecting this
option the H323 Profile Gatekeeper Address and H323 Profile Gatekeeper Discover y
settings must also be configured.
Example:
H323 Profile 1 CallSetup Mode: Gatekeeper
H323 Profile [1..1] Encryption KeySize
Define the minimum or maximum key size for the Diffie-Hellman key exchange method, which is
used when establishing the Advanced Encryption Standard (AES) encryption key.
Requires user role: ADMIN
Value space: <Min1024bit/Max1024bit/Min2048bit>
Min1024bit: The minimum size is 1024 bit.
Ma x1024b it: The maximum size is 1024 bit.
Min2048bit: The minimum size is 2048 bit.
Example:
H323 Profile 1 Encryption MinKeySize: Max1024bit
H323 Profile [1..1] Gatekeeper Discovery
Determine how the system shall register to a H.323 Gatekeeper.
Requires user role: ADMIN
Value space: <Manual/Auto>
Manual: The system will use a specific Gatekeeper identified by the Gatekeeper's IP address.
Auto: The system will automatically try to register to any available Gatekeeper. If a
Gatekeeper responds to the request sent from the codec within 30 seconds this specific
Gatekeeper will be used. This requires that the Gatekeeper is in auto discovery mode as
well. If no Gatekeeper responds, the system will not use a Gatekeeper for making H.323
calls and hence an IP address must be specified manually.
Example:
H323 Profile 1 Gatekeeper Discovery: Manual
H323 Profile [1..1] Gatekeeper Address
Enter the IP address of the Gatekeeper. Requires the H.323 Call Setup Mode to be set to
Gatekeeper and the Gatekeeper Discovery to be set to Manual.
Requires user role: ADMIN
Value space: <S: 0, 255>
Format: A valid IPv4 address, IPv6 address or DNS name.
Example:
H323 Profile 1 Gatekeeper Address: "192.0.2.0"
H323 Profile [1..1] H323Alias E164
The H.323 Alias E.164 defines the address of the system, according to the numbering plan
implemented in the H.323 Gatekeeper. The E.164 alias is equivalent to a telephone number,
sometimes combined with access codes.
Requires user role: ADMIN
Value space: <S: 0, 30>
Format: Compact string with a maximum of 30 characters. Valid characters are 0-9, * and #.
Example:
H323 Profile 1 H323Alias E164: "90550092"
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
69
Page 70
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
H323 Profile [1..1] H323Alias ID
Lets you specify the H.323 Alias ID which is used to address the system on a H.323 Gatekeeper
and will be displayed in the call lists. Example: "firstname.lastname@company.com", "My H.323
Alias ID"
Requires user role: ADMIN
Value space: <S: 0, 49>
Format: String with a maximum of 49 characters.
Example:
H323 Profile 1 H323Alias ID: "firstname.lastname@company.com"
H323 Profile [1..1] PortAllocation
The H.323 Port Allocation setting affects the H.245 port numbers used for H.323 call signaling.
Requires user role: ADMIN
Value space: <Dynamic/Static>
Dynamic: The system will allocate which ports to use when opening a TCP connection.
The reason for doing this is to avoid using the same ports for subsequent calls, as some
firewalls consider this as a sign of attack. When Dynamic is selected, the H.323 ports used
are from 11000 to 20999. Once 20999 is reached they restart again at 11000. The ports are
automatically selected by the system within the given range. Firewall administrators should
not try to deduce which ports are used when, as the allocation schema within the mentioned
range may change without any further notice.
Static: When set to Static the ports are given within a static predefined range [5555-6555].
Example:
H323 Profile 1 PortAllocation: Dynamic
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
70
Page 71
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
Logging settings
Logging Mode
Not applicable in this version.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
71
Page 72
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
Network settings
Network [1..1] IPStack
Select if the system should use IPv4, IPv6, or dual IP stack, on the network interface. NOTE:
After changing this setting you may have to wait up to 30 seconds before it takes effect.
Requires user role: ADMIN
Value space: <Dual/IPv4/IPv6>
Dual: When set to Dual, the network interface can operate on both IP versions at the same
time, and can have both an IPv4 and an IPv6 address at the same time.
IPv4: When set to IPv4, the system will use IPv4 on the network interface.
IPv6: When set to IPv6, the system will use IPv6 on the network interface.
Example:
Network 1 IPStack: Dual
Network [1..1] IPv4 Assignment
Define how the system will obtain its IPv4 address, subnet mask and gateway address. This
setting only applies to systems on IPv4 networks.
Requires user role: ADMIN
Value space: <Static/DHCP>
Static: The addresses must be configured manually using the Network IPv4 Address,
Network IPv4 Gateway and Network IPv4 SubnetMask settings (static addresses).
DHCP: The system addresses are automatically assigned by the DHCP server.
Example:
Network 1 IPv4 Assignment: DHCP
Network [1..1] IPv4 Address
Enter the static IPv4 network address for the system. This setting is only applicable when
Network Assignment is set to Static.
Requires user role: ADMIN
Value space: <S: 0, 64>
Format: A valid IPv4 address.
Example:
Network 1 IPv4 Address: "192.0.2.2"
Network [1..1] IPv4 Gateway
Define the IPv4 network gateway. This setting is only applicable when the Network Assignment
is set to Static.
Requires user role: ADMIN
Value space: <S: 0, 64>
Format: A valid IPv4 address.
Example:
Network 1 IPv4 Gateway: "192.0.2.1"
Network [1..1] IPv4 SubnetMask
Define the IPv4 network subnet mask. This setting is only applicable when the Network
Assignment is set to Static.
Requires user role: ADMIN
Value space: <S: 0, 64>
Format: The valid IPv4 address format.
Example:
Network 1 IPv4 SubnetMask: "255.255.255.0"
Network [1..1] IPv6 Assignment
Define how the system will obtain its IPv6 address and the default gateway address. This
setting only applies to systems on IPv6 networks.
Requires user role: ADMIN
Value space: <Static/DHCPv6/Autoconf>
Static: The codec and gateway IP addresses must be configured manually using the Network
IPv6 Address and Network IPv6 Gateway settings. The options, for example NTP and DNS
server addresses, must either be set manually or obtained from a DHCPv6 server. The
Network IPv6 DHCPOptions setting determines which method to use.
DHCP v6: All IPv6 addresses, including options, will be obtained from a DHCPv6 ser ver. See
RFC 3315 for a detailed description. The Network IPv6 DHCPOptions setting will be ignored.
Autoconf: Enable IPv6 stateless autoconfiguration of the IPv6 network interface. See RFC
4862 for a detailed description. The options, for example NTP and DNS server addresses,
must either be set manually or obtained from a DHCPv6 server. The Network IPv6
DHCPOptions setting determines which method to use.
Example:
Network 1 IPv6 Assignment: Autoconf
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
72
Page 73
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
Network [1..1] IPv6 Address
Enter the static IPv6 network address for the system. This setting is only applicable when the
Network IPv6 Assignment is set to Static.
Requires user role: ADMIN
Value space: <S: 0, 64>
Format: A valid IPv6 address.
Example:
Network 1 IPv6 Add ress: "2001:0DB8:0000:0000:0000:0000:0000:0002"
Network [1..1] IPv6 Gateway
Define the IPv6 network gateway address. This setting is only applicable when the Network
IPv6 Assignment is set to Static.
Requires user role: ADMIN
Value space: <S: 0, 64>
Format: A valid IPv6 address.
Example:
Network 1 IPv6 Gateway: "2001:0DB8:0000:0000:0000:0000:0000:0001"
Network [1..1] IPv6 DHCPOptions
Retrieve a set of DHCP options, for example NTP and DNS server addresses, from a DHCPv6
server.
Requires user role: ADMIN
Value space: <Off/On>
Off: Disable the retrieval of DHCP options from a DHCPv6 server.
On: Enable the retrieval of a selected set of DHCP options from a DHCPv6 server.
Example:
Network 1 IPv6 DHCPOptions: On
Network [1..1] DHCP RequestTFTPServerAddress
This setting is used only for video systems that are registered to a Cisco Unified
Communications Manager (CUCM).
The setting determines whether the endpoint should ask the DHCP server for DHCP option 150,
so that it can discover the address of the TFTP server (provisioning server) automatically.
If this setting is Off or the DHCP server does not support option 150, the TFTP server address
must be set manually using the Provisioning ExternalManager Address setting.
If the Network VLAN Voice Mode setting is Auto and the Cisco Discovery Protocol (CDP)
assigns an ID to the voice VLAN, then a request for option 150 will always be sent. That is, the
Network DHCP RequestTFTFServerAddress setting will be ignored.
Requires user role: ADMIN
Value space: <Off/On>
Off: The video system will not send a request for DHCP option 150 and the address of the
TFTP server must be set manually. See the note above for any exception to this rule.
On: The video system will send a request for option 150 to the DHCP server so that it can
automatically discover the address of the TFTP server.
Example:
Network 1 DHCP RequestTFTPServerAddress: On
Network [1..1] DNS Domain Name
DNS Domain Name is the default domain name suffix which is added to unqualified names.
Example: If the DNS Domain Name is "company.com" and the name to lookup is
"MyVideoSystem", this will result in the DNS lookup "MyVideoSystem.company.com".
Requires user role: ADMIN
Value space: <S: 0, 64>
Format: String with a maximum of 64 characters.
Example:
Network 1 DNS Domain Name: ""
Network [1..1] DNS Server [1..3] Address
Define the network addresses for DNS servers. Up to 3 addresses may be specified. If the
network addresses are unknown, contact your administrator or Internet Service Provider.
Requires user role: ADMIN
Value space: <S: 0, 64>
Format: A valid IPv4 address or IPv6 address.
Example:
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
73
Network 1 DNS Server 1 Address: ""
Page 74
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
Network [1..1] QoS Mode
The QoS (Quality of Service) is a method which handles the priority of audio, video and data in
the network. The QoS settings must be supported by the infrastructure. Diffserv (Differentiated
Services) is a computer networking architecture that specifies a simple, scalable and coarsegrained mechanism for classifying, managing network traffic and providing QoS priorities on
modern IP networks.
Requires user role: ADMIN
Value space: <Off/Diffserv>
Off: No QoS method is used.
Diffserv: When you set the QoS Mode to Diffserv, the Network QoS Diffserv Audio, Network
QoS Diffserv Video, Network QoS Diffserv Data, Network QoS Diffserv Signalling, Network
QoS Diffserv ICMPv6 and Network QoS Diffserv NTP settings are used to prioritize packets.
Example:
Network 1 QoS Mode: Diffserv
Network [1..1] QoS Diffserv Audio
This setting will only take effect if Network QoS Mode is set to Diffser v.
Define which priority Audio packets should have in the IP network.
The priority for the packets ranges from 0 to 63 - the higher the number, the higher the priority.
The recommended class for Audio is CS4, which equals the decimal value 32. If in doubt,
contact your network administrator.
The priority set here might be overridden when packets are leaving the network controlled by
the local network administrator.
Requires user role: ADMIN
Value space: <0..63>
Range: Select a value between 0 to 63 - the higher the number, the higher the priority. The
default value is 0 (best effort).
Example:
Network 1 QoS Diffserv Audio: 0
Network [1..1] QoS Diffserv Video
This setting will only take effect if Network QoS Mode is set to Diffser v.
Define which priority Video packets should have in the IP network. The packets on the
presentation channel (shared content) are also in the Video packet category. The priority for the
packets ranges from 0 to 63 - the higher the number, the higher the priority. The recommended
class for Video is CS4, which equals the decimal value 32. If in doubt, contact your network
administrator.
The priority set here might be overridden when packets are leaving the network controlled by
the local network administrator.
Requires user role: ADMIN
Value space: <0..63>
Range: Select a value between 0 to 63 - the higher the number, the higher the priority. The
default value is 0 (best effort).
Example:
Network 1 QoS Diffserv Video: 0
Network [1..1] QoS Diffserv Data
This setting will only take effect if Network QoS Mode is set to Diffser v.
Define which priority Data packets should have in the IP network.
The priority for the packets ranges from 0 to 63 - the higher the number, the higher the priority.
The recommended value for Data is 0, which means best effort. If in doubt, contact your
network administrator.
The priority set here might be overridden when packets are leaving the network controlled by
the local network administrator.
Requires user role: ADMIN
Value space: <0..63>
Range: Select a value between 0 to 63 - the higher the number, the higher the priority. The
default value is 0 (best effort).
Example:
Network 1 QoS Diffserv Data: 0
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
74
Page 75
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
Network [1..1] QoS Diffserv Signalling
This setting will only take effect if Network QoS Mode is set to Diffser v.
Define which priority Signalling packets that are deemed critical (time-sensitive) for the real-
time operation should have in the IP network.
The priority for the packets ranges from 0 to 63 - the higher the number, the higher the priority.
The recommended class for Signalling is CS3, which equals the decimal value 24. If in doubt,
contact your network administrator.
The priority set here might be overridden when packets are leaving the network controlled by
the local network administrator.
Requires user role: ADMIN
Value space: <0..63>
Range: Select a value between 0 to 63 - the higher the number, the higher the priority. The
default value is 0 (best effort).
Example:
Network 1 QoS Diffserv Signalling: 0
Network [1..1] QoS Diffserv ICMPv6
This setting will only take effect if Network QoS Mode is set to Diffser v.
Define which priority ICMPv6 packets should have in the IP network.
The priority for the packets ranges from 0 to 63 - the higher the number, the higher the priority.
The recommended value for ICMPv6 is 0, which means best effort. If in doubt, contact your
network administrator.
The priority set here might be overridden when packets are leaving the network controlled by
the local network administrator.
Requires user role: ADMIN
Value space: <0..63>
Range: Select a value between 0 to 63 - the higher the number, the higher the priority. The
default value is 0 (best effort).
Example:
Network 1 QoS Diffserv ICMPv6: 0
Network [1..1] QoS Diffserv NTP
This setting will only take effect if Network QoS Mode is set to Diffser v.
Define which priority NTP packets should have in the IP network.
The priority for the packets ranges from 0 to 63 - the higher the number, the higher the priority.
The recommended value for NTP is 0, which means best effort. If in doubt, contact your
network administrator.
The priority set here might be overridden when packets are leaving the network controlled by
the local network administrator.
Requires user role: ADMIN
Value space: <0..63>
Range: Select a value between 0 to 63 - the higher the number, the higher the priority. The
default value is 0 (best effort).
Example:
Network 1 QoS Diffserv NTP: 0
Network [1..1] IEEE8021X Mode
The system can be connected to an IEEE 802.1X LAN network, with a por t-based network
access control that is used to provide authenticated network access for Ethernet networks.
Requires user role: ADMIN
Value space: <Off/On>
Off: The 802.1X authentication is disabled (default).
On: The 802.1X authentication is enabled.
Example:
Network 1 IEEE8021X Mode: Off
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
75
Page 76
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
Network [1..1] IEEE8021X TlsVerify
Verification of the server-side certificate of an IEEE802.1x connection against the certificates in
the local CA-list when TLS is used. The CA-list must be uploaded to the video system. This can
be done from the web interface.
This setting takes effect only when Network [1..1] IEEE8021X Eap Tls is enabled (On).
Requires user role: ADMIN
Value space: <Off/On>
Off: When set to Off, TLS connections are allowed without verifying the server-side X.509
certificate against the local CA-list. This should typically be selected if no CA-list has been
uploaded to the codec.
On: When set to On, the server-side X.509 certificate will be validated against the local CAlist for all TLS connections. Only servers with a valid certificate will be allowed.
Example:
Network 1 IEEE8021X TlsVerify: Off
Network [1..1] IEEE8021X UseClientCertificate
Authentication using a private key/certificate pair during an IEEE802.1x connection. The
authentication X.509 certificate must be uploaded to the video system. This can be done from
the web interface.
Requires user role: ADMIN
Value space: <Off/On>
Off: When set to Off client-side authentication is not used (only server-side).
On: When set to On the client (video system) will perform a mutual authentication TLS
handshake with the server.
Example:
Network 1 IEEE8021X UseClientCertificate: Off
Network [1..1] IEEE8021X Identity
The 802.1X Identity is the user name needed for 802.1X authentication.
Requires user role: ADMIN
Value space: <S: 0, 64>
Format: String with a maximum of 64 characters.
Example:
Network 1 IEEE8021X Identity: ""
Network [1..1] IEEE8021X Password
The 802.1X Password is the password needed for 802.1X authentication.
Requires user role: ADMIN
Value space: <S: 0, 32>
Format: String with a maximum of 32 characters.
Example:
Network 1 IEEE8021X Password: ""
Network [1..1] IEEE8021X AnonymousIdentity
The 802.1X Anonymous ID string is to be used as unencrypted identity with EAP (Extensible
Authentication Protocol) types that support different tunneled identity, like EAP-PEAP and EAPTTLS. If set, the anonymous ID will be used for the initial (unencrypted) EAP Identity Request.
Requires user role: ADMIN
Value space: <S: 0, 64>
Format: String with a maximum of 64 characters.
Example:
Network 1 IEEE8021X AnonymousIdentity: ""
Network [1..1] IEEE8021X Eap Md5
Set the Md5 (Message-Digest Algorithm 5) mode. This is a Challenge Handshake
Authentication Protocol that relies on a shared secret. Md5 is a Weak security.
Requires user role: ADMIN
Value space: <Off/On>
Off: The EAP-MD5 protocol is disabled.
On: The EAP-MD5 protocol is enabled (default).
Example:
Network 1 IEEE8021X Eap Md5: On
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
76
Page 77
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
Network [1..1] IEEE8021X Eap Ttls
Set the TTLS (Tunneled Transport Layer Security) mode. Authenticates LAN clients without the
need for client certificates. Developed by Funk Software and Certicom. Usually supported by
Agere Systems, Proxim and Avaya.
Requires user role: ADMIN
Value space: <Off/On>
Off: The EAP-TTLS protocol is disabled.
On: The EAP-TTLS protocol is enabled (default).
Example:
Network 1 IEEE8021X Eap Ttls: On
Network [1..1] IEEE8021X Eap Tls
Enable or disable the use of EAP-TLS (Transport Layer Security) for IEEE802.1x connections.
The EAP-TLS protocol, defined in RFC 5216, is considered one of the most secure EAP
standards. LAN clients are authenticated using client certificates.
Requires user role: ADMIN
Value space: <Off/On>
Off: The EAP-TLS protocol is disabled.
On: The EAP-TLS protocol is enabled (default).
Example:
Network 1 IEEE8021X Eap Tls: On
Network [1..1] IEEE8021X Eap Peap
Set the Peap (Protected Extensible Authentication Protocol) mode. Authenticates LAN clients
without the need for client certificates. Developed by Microsoft, Cisco and RSA Security.
Requires user role: ADMIN
Value space: <Off/On>
Off: The EAP-PEAP protocol is disabled.
On: The EAP-PEAP protocol is enabled (default).
Example:
Network 1 IEEE8021X Eap Peap: On
Network [1..1] MTU
Set the Ethernet MTU (Maximum Transmission Unit).
Requires user role: ADMIN
Value space: <576 . .150 0 >
Range: Select a value between 576 and 1500 bytes.
Example:
Network 1 MTU: 1500
Network [1..1] Speed
Set the Ethernet link speed.
Requires user role: ADMIN
Value space: <Auto/10h alf/10fu ll/10 0hal f/10 0full/100 0full>
Auto: Autonegotiate link speed.
10h alf : Force link to 10 Mbps half-duplex.
10f ull: Force link to 10 Mbps full-duplex.
100 half: Force link to 100 Mbps half-duplex.
100 full: Force link to 100 Mbps full-duplex.
1000full: Force link to 1 Gbps full-duplex.
Example:
Network 1 Speed: Auto
Network [1..1] TrafficControl Mode
Set the network traffic control mode to decide how to control the video packets transmission
speed.
Requires user role: ADMIN
Value space: <Off/On>
Off: Transmit video packets at link speed.
On: Transmit video packets at maximum 20 Mbps. Can be used to smooth out bursts in the
outgoing network traffic.
Example:
Network 1 TrafficControl: On
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
77
Page 78
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
Network [1..1] RemoteAccess Allow
Define which IP addresses (IPv4/IPv6) are allowed for remote access to the codec from SSH/
Telnet/HTTP/HTTPS. Multiple IP addresses are separated by a white space.
A network mask (IP range) is specified by <ip address>/N, where N is 1-32 for IPv4, and N is
1-128 for IPv6. The /N is a common indication of a network mask where the first N bits are set.
Thus 192.168.0.0/24 would match any address starting with 192.168.0, since these are the first
24 bits in the address.
Requires user role: ADMIN
Value space: <S: 0, 255>
Format: String with a maximum of 255 characters.
Example:
Network 1 Re moteAccess Allow: "10.11.2.3 192.168.0.0/24 2001:0db8:0000:0000:0
000:ff00:0042:8329 2001:db8:abcd:0012::0/64"
Network [1..1] VLAN Voice Mode
Set the VLAN voice mode. The VLAN Voice Mode will be set to Auto automatically if you have
Cisco UCM (Cisco Unified Communications Manager) as provisioning infrastructure. Note that
Auto mode will NOT work if the NetworkServices CDP Mode setting is Off.
Requires user role: ADMIN
Value space: <Auto/Manual/Off>
Auto: The Cisco Discovery Protocol (CDP), if available, assigns an id to the voice VLAN. If
CDP is not available, VLAN is not enabled.
Manual: The VLAN ID is set manually using the Network VLAN Voice VlanId setting. If CDP is
available, the manually set value will be overruled by the value assigned by CDP.
Off: VLAN is not enabled.
Example:
Network 1 VLAN Voice Mode: Auto
Network [1..1] VLAN Voice VlanId
Set the VLAN voice ID. This setting will only take effect if VLAN Voice Mode is set to Manual.
Requires user role: ADMIN
Value space: <1..409 4>
Range: Select a value between 1 and 4094.
Example:
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
Network 1 VLAN Voice VlanId: 1
78
Page 79
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
NetworkServices settings
NetworkServices CDP Mode
Enable or disable the CDP (Cisco Discovery Protocol) daemon. Enabling CDP will make the
endpoint report certain statistics and device identifiers to a CDP-enabled switch. If CDP is
disabled, the Network VLAN Voice Mode: Auto setting will not work.
Requires user role: ADMIN
Value space: <Off/On>
Off: The CDP daemon is disabled.
On: The CDP daemon is enabled.
Example:
NetworkServices CDP Mode: On
NetworkServices H323 Mode
Determine whether the system should be able to place and receive H.323 calls or not.
Requires user role: ADMIN
Value space: <Off/On>
Off: Disable the possibility to place and receive H.323 calls.
On: Enable the possibility to place and receive H.323 calls (default).
Example:
NetworkServices H323 Mode: On
NetworkServices HTTP Mode
Set the HTTP mode to enable/disable access to the system through a web browser. The web
interface is used for system management, call management such as call transfer, diagnostics
and software uploads.
Requires user role: ADMIN
Value space: <Off/On>
Off: The HTTP protocol is disabled.
On: The HTTP protocol is enabled.
Example:
NetworkServices HTTP Mode: On
NetworkServices SIP Mode
Determine whether the system should be able to place and receive SIP calls or not.
Requires user role: ADMIN
Value space: <Off/On>
Off: Disable the possibility to place and receive SIP calls.
On: Enable the possibility to place and receive SIP calls (default).
Example:
NetworkServices SIP Mode: On
NetworkServices Telnet Mode
Telnet is a network protocol used on the Internet or Local Area Network (LAN) connections.
Requires user role: ADMIN
Value space: <Off/On>
Off: The Telnet protocol is disabled. This is the factory setting.
On: The Telnet protocol is enabled.
Example:
NetworkServices Telnet Mode: Off
NetworkServices WelcomeText
Choose which information the user should see when logging on to the codec through Telnet/
SSH.
Requires user role: ADMIN
Value space: <Off/On>
Off: The welcome text is: Login successful
On: The welcome text is: Welcome to <system name>; Software version; Software release
date; Login successful.
Example:
NetworkServices WelcomeText: On
NetworkServices XMLAPI Mode
Not applicable in this version.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
79
Page 80
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
NetworkServices MultiWay Address
The MultiWay address must be equal to the Conference Factory Alias, as configured on the
Video Communication Server. The MultiWay™ conferencing enables video endpoint users to
introduce a 3rd party into an existing call.
MultiWay™ can be used in the following situations:
1) When you want to add someone else in to your existing call.
2) When you are called by a 3rd party while already in a call and you want to include that person
in the call.
Requirements: Video Communication Server (VCS) version X5 (or later) and Codian MCU
version 3.1 (or later). Video systems invited to join the MultiWay™ conference must support the
H.323 routeToMC facility message if in an H.323 call, or SIP REFER message if in a SIP call.
Requires user role: ADMIN
Value space: <S: 0, 255>
Format: String with a maximum of 255 characters (a valid dial URI).
Example:
NetworkServices MultiWay Address: "h323:multiway@company.com"
NetworkServices MultiWay Protocol
Determine the protocol to be used for MultiWay calls.
Requires user role: ADMIN
Value space: <Auto/H323/Sip>
Auto: The system will select the protocol for MultiWay calls.
H323: The H323 protocol will be used for MultiWay calls.
Sip: The SIP protocol will be used for MultiWay calls.
Example:
NetworkServices MultiWay Protocol: Auto
NetworkServices HTTPS Mode
HTTPS is a web protocol that encr ypts and decrypts user page requests as well as the pages
that are returned by the web server.
Requires user role: ADMIN
Value space: <Off/On>
Off: The HTTPS protocol is disabled.
On: The HTTPS protocol is enabled.
Example:
NetworkServices HTTPS Mode: On
NetworkServices HTTPS VerifyServerCertificate
When the video system connects to an external HTTPS server (like a phone book server or an
external manager), this server will present a certificate to the video system to identify itself.
Requires user role: ADMIN
Value space: <Off/On>
Off: Do not verify server certificates.
On: Requires the system to verify that the server certificate is signed by a trusted Certificate
Authority (CA). This requires that a list of trusted CAs are uploaded to the system in advance.
Example:
NetworkServices HTTPS VerifyServerCertificate: Off
NetworkServices HTTPS VerifyClientCertificate
When the video system connects to a HTTPS client (like a web browser), the client can be
asked to present a certificate to the video system to identify itself.
Requires user role: ADMIN
Value space: <Off/On>
Off: Do not verify client certificates.
On: Requires the client to present a certificate that is signed by a trusted Certificate
Authority (CA). This requires that a list of trusted CAs are uploaded to the system in advance.
Example:
NetworkServices HTTPS VerifyClientCertificate: Off
NetworkServices HTTPS OCSP Mode
Define the support for OCSP (Online Certificate Status Protocol) responder ser vices. The OCSP
feature allows users to enable OCSP instead of certificate revocation lists (CRLs) to check the
certificate status.
For any outgoing HTTPS connection, the OCSP responder is queried of the status. If the
corresponding certificate has been revoked, then the HTTPS connection will not be used.
Requires user role: ADMIN
Value space: <Off/On>
Off: Disable OCSP support.
On: Enable OCSP support.
Example:
NetworkServices HTTPS OCSP Mode: Off
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
80
Page 81
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
NetworkServices HTTPS OCSP URL
Specify the URL of the OCSP responder (server) that will be used to check the certificate
status.
Requires user role: ADMIN
Value space: <S: 0, 255>
Format: String with a maximum of 255 characters.
Example:
NetworkServices HTTPS OCSP URL: "http://ocspserver.company.com:81"
NetworkServices Medianet Metadata
Switch On or Off the capability to tag media flows with metadata related to the Cisco Medianet
deployment.
Requires user role: ADMIN
Value space: <Off/On>
Off: Media flows will not be tagged with such metadata.
On: Media flows will be tagged with such metadata.
Example:
NetworkServices Medianet Metadata: Off
NetworkServices NTP Mode
The Network Time Protocol (NTP) is used to synchronize the system's time and date to a
reference time server. The time server will be queried regularly for time updates.
Requires user role: ADMIN
Value space: <Auto/Manual/Off>
Auto: The system will use an NTP server for time reference. As default, the server address
will be obtained from the network’s DHCP server. If a DHCP server is not used, or if the
DHCP server does not provide an NTP server address, the NTP server address that is
specified in the NetworkServices NTP Address setting will be used.
Manual: The system will use the NTP server that is specified in the NetworkServices NTP
Address setting for time reference.
Off: The system will not use an NTP server. The Network Ser vices NTP Address setting will
be ignored.
Example:
NetworkServices NTP Mode: Auto
NetworkServices NTP Address
The address of the NTP server that will be used when NetworkServices NTP Mode is set to
Manual, and when NetworkServices NTP Mode is set to Auto and no address is supplied by a
DHCP server.
Requires user role: ADMIN
Value space: <S: 0, 64>
Format: A valid IPv4 address, IPv6 address or DNS name.
Example:
NetworkServices NTP Add ress: "0.tandberg.pool.ntp.org"
NetworkServices SNMP Mode
SNMP (Simple Network Management Protocol) is used in network management systems to
monitor network-attached devices (routers, servers, switches, projectors, etc) for conditions
that warrant administrative attention. SNMP exposes management data in the form of variables
on the managed systems, which describe the system configuration. These variables can then
be queried (set to ReadOnly) and sometimes set (set to ReadWrite) by managing applications.
Requires user role: ADMIN
Value space: <Off/ReadOnly/ReadWrite>
Off: Disable the SNMP network service.
ReadOnly: Enable the SNMP network service for queries only.
ReadWrite: Enable the SNMP network service for both queries and commands.
Example:
NetworkServices SNMP Mode: ReadOnly
NetworkServices SNMP Host [1..3] Address
Enter the address of up to three SNMP Managers.
The system's SNMP Agent (in the codec) responds to requests from SNMP Managers (a PC
program etc.), for example about system location and system contact. SNMP traps are not
supported.
Requires user role: ADMIN
Value space: <S: 0, 64>
Format: A valid IPv4 address, IPv6 address or DNS name.
Example:
NetworkServices SNMP Host 1 Address: ""
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
81
Page 82
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
NetworkServices SNMP CommunityName
Enter the name of the Network Services SNMP Community. SNMP Community names are used
to authenticate SNMP requests. SNMP requests must have a password (case sensitive) in order
to receive a response from the SNMP Agent in the codec. The default password is "public".
If you have the Cisco TelePresence Management Suite (TMS) you must make sure the same
SNMP Community is configured there too. NOTE: The SNMP Community password is case
sensitive.
Requires user role: ADMIN
Value space: <S: 0, 50>
Format: String with a maximum of 50 characters.
Example:
NetworkServices SNMP CommunityName: "public"
NetworkServices SNMP SystemContact
Enter the name of the Network Services SNMP System Contact.
Requires user role: ADMIN
Value space: <S: 0, 50>
Format: String with a maximum of 50 characters.
Example:
NetworkServices SNMP SystemContact: ""
NetworkServices SNMP SystemLocation
Enter the name of the Network Services SNMP System Location.
Requires user role: ADMIN
Value space: <S: 0, 50>
Format: String with a maximum of 50 characters.
Example:
NetworkServices SNMP SystemLocation: ""
NetworkServices SSH Mode
SSH (or Secure Shell) protocol can provide secure encrypted communication between the
codec and your local computer.
Requires user role: ADMIN
Value space: <Off/On>
Off: The SSH protocol is disabled.
On: The SSH protocol is enabled.
Example:
NetworkServices SSH Mode: On
NetworkServices SSH AllowPublicKey
Secure Shell (SSH) public key authentication can be used to access the codec.
Requires user role: ADMIN
Value space: <Off/On>
Off: The SSH public key is not allowed.
On: The SSH public key is allowed.
Example:
NetworkServices SSH AllowPublicKey: On
NetworkServices CTMS Mode
This setting determines whether or not to allow multiparty conferences controlled by a Cisco
TelePresence Multipoint Switch (CTMS).
Video systems are able to initiate or join non-encrypted multiparty conferences controlled by
CTMS version 1.8 or later. Encrypted conferences are supported as from software versions
CTMS 1.9.1. Encryption is addressed in the NetworkServices CTMS Encryption setting.
Requires user role: ADMIN
Value space: <Off/On>
Off: Multiparty conferencing via CTMS is prohibited.
On: Multiparty conferencing via CTMS is allowed.
Example:
NetworkServices CTMS Mode: On
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
82
Page 83
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
NetworkServices CTMS Encryption
This setting indicates whether or not the video system supports encryption when participating
in a multiparty meeting controlled by a Cisco TelePresence Multipoint Switch (CTMS).
CTMS allows three security settings for meetings: non-secure (not encrypted), best effort
(encrypted if all participants support encryption, otherwise not encr ypted) and secure (always
encr ypted).
Requires user role: ADMIN
Value space: <Off/BestEffort>
Off: The video system does not allow encryption and therefore cannot par ticipate in a secure
CTMS meeting (encrypted). When participating in a best effort CTMS meeting, the meeting
will be downgraded to non-secure (not encrypted).
BestEffort: The video system can negotiate encryption parameters with CTMS and
participate in a secure CTMS meeting (encrypted). Do not use this value if the CTMS version
is older than 1.9.1.
Example:
NetworkServices CTMS Encryption: Off
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
83
Page 84
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
Peripherals settings
Peripherals Profile TouchPanels
Set the number of touch panels that are expected to be connected to the video system. This
information is used by the video system’s diagnostics service. If the number of connected touch
panels does not match this setting, the diagnostics service will report it as an inconsistency.
Note that only one Cisco Touch controller is supported in this version.
Requires user role: ADMIN
Value space: <N o t S e t /Minimum1/ 0/1/2/ 3/4/5 >
NotSet: No touch panel check is performed.
Minimum1: At least one touch panel should be connected to the video system.
0-5: This number of Touch controllers should be connected to the video system.
Example:
Peripherals Profile TouchPanels: NotSet
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
84
Page 85
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
Phonebook settings
Phonebook Server [1..1] ID
Enter a name for the external phone book.
Requires user role: ADMIN
Value space: <S: 0, 64>
Format: String with a maximum of 64 characters.
Example:
Phonebook Server [1..1] Type
Select the phonebook server type.
Requires user role: ADMIN
Value space: <VCS/TMS/Callway/CUCM>
Example:
Phonebook Server 1 ID: ""
VCS: Select VCS if the phonebook is located on the Cisco TelePresence Video
Communication Server.
TMS: Select TMS if the phonebook is located on the Cisco TelePresence Management Suite
server.
Callway: Select Callway if the phonebook is to be provided by the WebEx TelePresence
subscription service (formerly called CallWay). Contact your WebEx TelePresence provider
for more information.
CUCM: Select CUCM if the phonebook is located on the Cisco Unified Communications
Manager.
Phonebook Server 1 Type: TMS
Phonebook Server [1..1] URL
Enter the address (URL) to the external phone book server.
Requires user role: ADMIN
Value space: <S: 0, 255>
Format: String with a maximum of 255 characters.
Example:
Phonebook Server 1 URL: "http://tms.company.com/tms/public/external/
phonebook/phonebookservice.asmx"
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
85
Page 86
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
Provisioning settings
Provisioning Connectivity
This setting controls how the device discovers whether it should request an internal or external
configuration from the provisioning server.
Requires user role: ADMIN
Value space: <Internal/External/Auto>
Internal: Request internal configuration.
External: Request external configuration.
Auto: Automatically discover using NAPTR queries whether internal or external configurations
should be requested. If the NAPTR responses have the "e" flag, external configurations will
be requested. Otherwise internal configurations will be requested.
Example:
Provisioning Connectivity: Auto
Provisioning Mode
It is possible to configure a video system using a provisioning system (external manager).
This allows video conferencing network administrators to manage many video systems
simultaneously. With this setting you choose which type of provisioning system to use.
Provisioning can also be switched off. Contact your provisioning system provider/representative
for more information.
Requires user role: ADMIN
Value space: <Off/TMS/VCS/CallWay/CUCM/Auto/Edge>
Off: The video system will not be configured by a provisioning system.
Auto: The provisioning server will automatically be selected by the video system.
TMS: The video system will be configured using TMS (Cisco TelePresence Management
System).
VCS: The video system will be configured using VCS (Cisco TelePresence Video
Communication Server).
Callway: The video system will be configured using the WebEx TelePresence subscription
service (formerly named Callway).
CUCM: The video system will be configured using CUCM (Cisco Unified Communications
Manager).
Edge: The system will connect to CUCM via the Collaboration Edge infrastructure.
Example:
Provisioning Mode: Auto
Provisioning LoginName
This is the user name part of the credentials used to authenticate the video system with the
provisioning server. This setting must be used when required by the provisioning server. If
Provisioning Mode is Callway (WebEx TelePresence), enter the video number.
Requires user role: ADMIN
Value space: <S: 0, 80>
Format: String with a maximum of 80 characters.
Example:
Provisioning LoginNa me: ""
Provisioning Password
This is the password part of the credentials used to authenticate the video system with the
provisioning server. This setting must be used when required by the provisioning server. If
Provisioning Mode is Callway (WebEx TelePresence), enter the activation code.
Requires user role: ADMIN
Value space: <S: 0, 64>
Format: String with a maximum of 64 characters.
Example:
Provisioning Password: ""
Provisioning HttpMethod
Select the HTTP method to be used for the provisioning.
Requires user role: ADMIN
Value space: <G E T/ P O ST>
GE T: Select GET when the provisioning server supports GET.
PO S T: Select POST when the provisioning server supports POST.
Example:
Provisioning HttpMethod: POST
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
86
Page 87
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
Provisioning ExternalManager Address
Enter the IP Address or DNS name of the external manager / provisioning system.
If an External Manager Address (and Path) is configured, the system will send a message to this
address when starting up. When receiving this message the external manager / provisioning
system can return configurations/commands to the unit as a result.
When using CUCM or TMS provisioning, the DHCP server can be set up to provide the external
manager address automatically (DHCP Option 242 for TMS, and DHCP Option 150 for CUCM).
An address set in the Provisioning ExternalManager Address setting will override the address
provided by DHCP.
Requires user role: ADMIN
Value space: <S: 0, 64>
Format: A valid IPv4 address, IPv6 address or DNS name.
Example:
Provisioning ExternalManager Address: ""
Provisioning ExternalManager AlternateAddress
Only applicable when the endpoint is provisioned by Cisco Unified Communication Manager
(CUCM) and an alternate CUCM is available for redundancy. Enter the address of the alternate
CUCM. If the main CUCM is not available, the endpoint will be provisioned by the alternate
CUCM. When the main CUCM is available again, the endpoint will be provisioned by this CUCM.
Requires user role: ADMIN
Value space: <S: 0, 64>
Format: A valid IPv4 address, IPv6 address or DNS name.
Example:
Provisioning ExternalManager AlternateAddress: ""
Provisioning ExternalManager Path
Set the Path to the external manager / provisioning system. This setting is required when
several management services reside on the same server, i.e. share the same External Manager
address.
Requires user role: ADMIN
Value space: <S: 0, 255>
Format: String with a maximum of 255 characters.
Example:
Provisioning ExternalManager Path: "tms/public/external/management/
SystemManagementService.asmx"
Provisioning ExternalManager Domain
Enter the SIP domain for the VCS provisioning ser ver.
Requires user role: ADMIN
Value space: <S: 0, 64>
Format: String with a maximum of 64 characters.
Example:
Provisioning ExternalManager Domain: "any.domain.com"
Provisioning ExternalManager Protocol
Determine whether to use secure management or not.
Requires user role: ADMIN
Value space: <HTTP/HTTPS>
HTTP: Set to HTTP to disable secure management. Requires HTTP to be enabled in the
NetworkServices HT TP Mode setting.
HTTPS: Set to HTTPS to enable secure management. Requires HTTPS to be enabled in the
NetworkServices HT TPS Mode setting.
Example:
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
Provisioning ExternalManager Protocol: HTTP
87
Page 88
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
RTP settings
RTP Ports Range Start
Specify the first port in the range of RTP ports.
As default, the system is using the UDP ports in the range 2326 to 2487 for RTP and RTCP
media data. Each media channel is using two adjacent ports for RTP and RTCP. The default
number of ports required in the UDP port range is based on the number of simultaneous calls
that the endpoint is capable of.
NOTE: Restar t the system for any change to this setting to take effect.
Requires user role: ADMIN
Value space: <1024..65438>
Range: Select a value between 1024 and 65438.
Example:
RTP Ports Range Stop
Specify the last RTP port in the range.
As default, the system is using the UDP ports in the range 2326 to 2487 for RTP and RTCP
media data. Each media channel is using two adjacent ports for RTP and RTCP. The default
number of ports required in the UDP port range is based on the number of simultaneous calls
that the endpoint is capable of.
NOTE: Restar t the system for any change to this setting to take effect.
Requires user role: ADMIN
Value space: <1120..65535>
Example:
RTP Ports Range Start: 2326
Range: Select a value between 1120 and 65535.
RTP Ports Range Stop: 2486
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
88
Page 89
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
Security settings
Security Audit Logging Mode
Determine where to record or transmit the audit logs. The audit logs are sent to a syslog server.
When using the External/ExternalSecure modes and setting the port assignment to manual in
the Security Audit Server Port Assignment setting, you must also enter the address and port
number for the audit server in the Security Audit Server Address and Security Audit Server Port
settings.
Requires user role: AUDIT
Value space: <Off/Internal/External/ExternalSecure>
Off: No audit logging is performed.
Internal: The system records the audit logs to internal logs, and rotates logs when they are
full.
External: The system sends the audit logs to an external syslog server. The syslog server
must support UDP.
ExternalSecure: The system sends encrypted audit logs to an external syslog server that is
verified by a certificate in the Audit CA list. The Audit CA list file must be uploaded to the
codec using the web interface. The common_name parameter of a certificate in the CA list
must match the IP address of the syslog server, and the secure TCP server must be set up
to listen for secure (TLS) TCP Syslog messages.
Example:
Security Audit Logging Mode: Off
Security Audit OnError Action
Determine what happens when the connection to the syslog server is lost. This setting is only
relevant when Security Audit Logging Mode is set to ExternalSecure.
Requires user role: AUDIT
Value space: <Halt/Ignore>
Halt: If a halt condition is detected the system codec is rebooted and only the auditor is
allowed to operate the unit until the halt condition has passed. When the halt condition has
passed the audit logs are re-spooled to the syslog server. Halt conditions are: A network
breach (no physical link), no syslog server running (or incorrect address or port to the syslog
server), TLS authentication failed (if in use), local backup (re-spooling) log full.
Ignore: The system will continue its normal operation, and rotate internal logs when full.
When the connection is restored it will again send its audit logs to the syslog server.
Example:
Security Audit OnError Action: Ignore
Security Audit Server Address
The audit logs are sent to a syslog server. Enter the IP address of the syslog ser ver. Only valid
IPv4 or IPv6 address formats are accepted. Host names are not supported. This setting is only
relevant when Security Audit Logging Mode is set to External or ExternalSecure.
Requires user role: AUDIT
Value space: <S: 0, 64>
Format: A valid IPv4 address or IPv6 address
Example:
Security Audit Server Address: ""
Security Audit Server Port
The audit logs are sent to a syslog server. Enter the port of the syslog server that the system
shall send its audit logs to. This setting is only relevant when Security Audit PortAssignment is
set to Manual.
Requires user role: AUDIT
Value space: <0..65535>
Range: Select a value between 0 to 65535.
Example:
Security Audit Server Port: 514
Security Audit Server PortAssignment
The audit logs are sent to a syslog server. You can define how the port number of the external
syslog server will be assigned. This setting is only relevant when Security Audit Logging
Mode is set to External or ExternalSecure. To see which port number is used you can check
the Security Audit Server Port status. Navigate to Configuration > System status on the web
interface or; if on a command line interface, run the command xStatus Security Audit Server
Port.
Requires user role: AUDIT
Value space: <Auto/Manual>
Auto: Will use UDP port number 514 when the Security Audit Logging Mode is set to
External. Will use TCP port number 6514 when the Security Audit Logging Mode is set to
ExternalSecure.
Manual: Will use the por t value defined in the Security Audit Server Port setting.
Example:
Security Audit Server PortAssignment: Auto
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
89
Page 90
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
Security Session ShowLastLogon
When logging in to the system using SSH or Telnet you will see the UserId, time and date of the
last session that did a successful login.
Requires user role: ADMIN
Value space: <Off/On>
On: Show information about the last session.
Off: Do not show information about the last session.
Example:
Security Session ShowLastLogon: Off
Security Session InactivityTimeout
Determine how long the system will accept inactivity from the user before he is automatically
logged out.
Requires user role: ADMIN
Value space: <0..10000>
Range: Select a value between 1 and 10000 seconds; or select 0 when inactivity should not
enforce automatic logout.
Example:
Security Session InactivityTimeout: 0
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
90
Page 91
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
SerialPort settings
SerialPort Mode
Enable/disable the serial port. You will need a console cable made for the purpose. A
description is found on Cisco Support Forum. Make a search for "Making a Console Cable and
Consoling In".
Requires user role: ADMIN
Value space: <Off/On>
Off: Disable the serial port.
On: Enable the serial port.
Example:
SerialPort BaudRate
Specify the baud rate (data transmission rate, bits per second) for the serial port. The default
value is 38400.
Other connection parameters for the serial port are: Data bits: 8; Parity: None; Stop bits: 1; Flow
control: None.
Requires user role: ADMIN
Value space: <9600/19200/38400/57600/115200>
Example:
SerialPort Mode: On
Range: Select a baud rate from the baud rates listed (bps).
SerialPort BaudRate: 38400
SerialPort LoginRequired
Determine if login shall be required when connecting to the serial port.
Requires user role: ADMIN
Value space: <Off/On>
Off: The user can access the codec via the serial port without any login.
On: Login is required when connecting to the codec via the serial port.
Example:
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
SerialPort LoginRequired: On
91
Page 92
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
SIP settings
SIP ANAT
ANAT (Alternative Network Address Types) enables media negotiation for multiple addresses
and address types, as specified in RFC 4091.
Requires user role: ADMIN
Value space: <Off/On>
Off: Disable ANAT.
On: Enable ANAT.
Example:
SIP ANAT: Off
SIP AuthenticateTransferror
Not applicable in this version.
SIP ListenPort
Turn on or off the listening for incoming connections on the SIP TCP/UDP ports. If turned
off, the endpoint will only be reachable through the SIP registrar (CUCM or VCS). It is
recommended to leave this setting at its default value.
Requires user role: ADMIN
Value space: <Off/On>
Off: Listening for incoming connections on the SIP TCP/UDP ports is turned off.
On: Listening for incoming connections on the SIP TCP/UDP ports is turned on.
Example:
SIP ListenPort: On
SIP PreferredIPMedia
Define the preferred IP version for sending and receiving media (audio, video, data). Only
applicable when both Network IPStack and Conference CallProtocolIPStack are set to Dual, and
the network does not have a mechanism for choosing the preferred IP version.
Requires user role: ADMIN
Value space: <IPv4/IPv6>
IPv4: The preferred IP version for media is IPv4.
IPv6: The preferred IP version for media is IPv6.
Example:
SIP PreferredIPM edia: IPv4
SIP PreferredIPSignaling
Define the preferred IP version for signaling (audio, video, data). Only applicable when both
Network IPStack and Conference CallProtocolIPStack are set to Dual, and the network does
not have a mechanism for choosing the preferred IP version. It also determines the priority of
the A/AAAA lookups in DNS, so that the preferred IP version is used for registration.
Requires user role: ADMIN
Value space: <IPv4/IPv6>
IPv4: The preferred IP version for signaling is IPv4.
IPv6: The preferred IP version for signaling is IPv6.
Example:
SIP PreferredIPSignaling: IPv4
SIP OCSP Mode
Not applicable in this version.
SIP OCSP DefaultResponder
Not applicable in this version.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
92
Page 93
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
SIP Profile [1..1] Ice Mode
ICE (Interactive Connectivity Establishment, RFC 5245) is a NAT traversal solution that the
endpoints can use to discover the optimized media path. Thus the shortest route for audio and
video is always secured between the endpoints. NOTE: ICE is not supported when registered to
CUCM (Cisco Unified Communication Manager).
Requires user role: ADMIN
Value space: <Auto/Off/On>
Auto: When set to Auto, ICE will be enabled if a turn server is provided, otherwise ICE will be
disabled.
Off: Set to Off to disable ICE.
On: Set to On to enable ICE.
Example:
SIP Profile 1 Ice Mode: Auto
SIP Profile [1..1] Ice DefaultCandidate
This is the default IP address that the endpoint will receive media on until ICE has reached a
conclusion about which media route to use (up to the first 5 seconds of a call.
Requires user role: ADMIN
Value space: <Host/Rflx/Relay>
Host: The endpoint will receive media on its own IP address.
Rflx: The endpoint will receive media on its public IP address as seen by the TURN server.
Relay: The endpoint will receive media on the IP address and por t allocated on the TURN
server, and is used as a fallback until ICE has concluded.
Example:
SIP Profile 1 Ice DefaultCandidate: Host
SIP Profile [1..1] Turn BandwidthProbe
Not applicable in this version.
SIP Profile [1..1] Turn DropRflx
DropRflx will make the endpoint force media through the Turn relay, unless the remote endpoint
is on the same network.
Requires user role: ADMIN
Value space: <Off/On>
Off: Disable DropRflx.
On: The system will force media through the Turn relay when the remote endpoint is on
another network.
Example:
SIP Profile Turn DropRflx: Off
SIP Profile [1..1] Turn Server
This is the address of the TURN (Traversal Using Relay NAT) server that the endpoints will use.
It is used as a media relay fallback and it is also used to discover the endpoint’s own public IP
address.
Requires user role: ADMIN
Value space: <S: 0, 255>
Format: The preferred format is DNS SRV record (e.g. _turn._udp.<domain>), or it can be a
valid IPv4 or IPv6 address.
Example:
SIP Profile 1 Turn Server: " _ turn. _ udp.example.com"
SIP Profile [1..1] Turn DiscoverMode
Set the discover mode to enable/disable the application to search for available Turn servers in
DNS. Before making calls, the system will test if port allocation is possible.
Requires user role: ADMIN
Value space: <Off/On>
Off: Set to Off to disable discovery mode.
On: When set to On, the system will search for available Turn servers in DNS, and before
making calls the system will test if port allocation is possible.
Example:
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
SIP Profile Turn DiscoverMode: On
SIP Profile [1..1] Turn UserName
The user name needed for accessing the TURN server.
Requires user role: ADMIN
Value space: <S: 0, 128>
Format: String with a maximum of 128 characters.
Example:
93
SIP Profile 1 Turn UserName: ""
Page 94
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
SIP Profile [1..1] Turn Password
The password needed for accessing the TURN ser ver.
Requires user role: ADMIN
Value space: <S: 0, 128>
Format: String with a maximum of 128 characters.
Example:
SIP Profile 1 Turn Password: ""
SIP Profile [1..1] URI
The SIP URI (Uniform Resource Identifier) is the address that is used to identify the video
system. The URI is registered and used by the SIP services to route inbound calls to the
system. The SIP URI syntax is defined in RFC 3261.
Requires user role: ADMIN
Value space: <S: 0, 255>
Format: String with maximum 255 characters and compliant with the SIP URI syntax.
Example:
SIP Profile 1 URI: "sip:firstname.lastname@company.com"
SIP Profile [1..1] DisplayName
When configured the incoming call will report the DisplayName instead of the SIP URI.
Requires user role: ADMIN
Value space: <S: 0, 255>
Format: String with a maximum of 255 characters.
Example:
SIP Profile 1 DisplayName: ""
SIP Profile [1..1] Authentication [1..1] LoginName
This is the user name part of the credentials used to authenticate towards the SIP proxy.
Requires user role: ADMIN
Value space: <S: 0, 128>
Format: String with a maximum of 128 characters.
Example:
SIP Profile 1 Authentication 1 LoginName: ""
SIP Profile [1..1] Authentication [1..1] Password
This is the password part of the credentials used to authenticate towards the SIP proxy.
Requires user role: ADMIN
Value space: <S: 0, 128>
Format: String with a maximum of 128 characters.
Example:
SIP Profile 1 Authentication 1 Password: ""
SIP Profile [1..1] DefaultTransport
Select the transport protocol to be used over the LAN.
Requires user role: ADMIN
Value space: <TCP/UDP/Tl s/A uto>
TCP: The system will always use TCP as the default transport method.
UDP: The system will always use UDP as the default transport method.
Tls: The system will always use TLS as the default transport method. For TLS connections
a SIP CA-list can be uploaded to the video system. If no such CA-list is available on the
system then anonymous Diffie Hellman will be used.
Auto: The system will try to connect using transport protocols in the following order: TLS,
TC P, U D P.
Example:
SIP Profile 1 DefaultTransport: Auto
SIP Profile [1..1] TlsVerify
For TLS connections a SIP CA-list can be uploaded to the video system. This can be done from
the web interface.
Requires user role: ADMIN
Value space: <Off/On>
Off: Set to Off to allow TLS connections without verifying them. The TLS connections are
allowed to be set up without verifying the x.509 certificate received from the server against
the local CA-list. This should typically be selected if no SIP CA-list has been uploaded.
On: Set to On to verify TLS connections. Only TLS connections to servers, whose x.509
certificate is validated against the CA-list, will be allowed.
Example:
SIP Profile 1 TlsVerify: Off
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
94
Page 95
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
SIP Profile [1..1] Outbound
Turn on or off the client initiated connections mechanism for firewall traversal, connection reuse
and redundancy. The current version supports RFC 5626.
Requires user role: ADMIN
Value space: <Off/On>
Off: Connect to the single proxy configured first in Proxy Address list.
On: Set up multiple outbound connections to servers in the Proxy Address list. A random
proxy is selected from the list for each SIP outbound request.
Example:
SIP Profile 1 Outbound: Off
SIP Profile [1..1] Proxy [1..4] Address
The Proxy Address is the manually configured address for the outbound proxy. The default port
is 5060 for TCP and UDP but another one can be provided.
If SIP Profile Outbound is enabled, multiple proxies can be addressed.
Requires user role: ADMIN
Value space: <S: 0, 255>
Format: If SIP Profile Outbound is enabled, use a fully qualified domain name. If SIP Profile
Outbound is disabled, you can also use a valid IPv4 address or IPv6 address.
Example:
SIP Profile 1 Proxy 1 Address: ""
SIP Profile [1..1] Proxy [1..4] Discovery
Select if the SIP Proxy address is to be obtained manually or by using Dynamic Host
Configuration Protocol (DHCP).
Requires user role: ADMIN
Value space: <Auto/Manual>
Auto: When Auto is selected, the SIP Proxy address is obtained using Dynamic Host
Configuration Protocol (DHCP).
Manual: When Manual is selected, the manually configured SIP Proxy address will be used.
Example:
SIP Profile 1 Proxy 1 Discovery: Manual
SIP Profile [1..1] Type
Enables SIP extensions and special behavior for a vendor or provider.
NOTE: The SIP types Alcatel, Avaya, Microsoft, and Nortel are no longer supported from
software version TC6.3.
Requires user role: ADMIN
Value space: <Standard/Cisco>
Standard: Use this when registering to standard SIP Proxy (tested with Cisco TelePresence
VCS and Broadsoft)
Cisco: Use this when registering to Cisco Unified Communication Manager.
Example:
SIP Profile 1 Type: Standard
SIP Profile [1..1] Mailbox
When registered to a Cisco Unified Communications Manager (CUCM) you may be offered
the option of having a private voice mailbox. Enter the number (address) of the mailbox in this
setting, or leave the string empty if you do not have a voice mailbox.
Requires user role: ADMIN
Value space: <S: 0, 255>>
Format: String with a maximum of 255 characters.
Example:
SIP Profile 1 Mailbox: "12345678"
SIP Profile [1..1] Line
When registered to a Cisco Unified Communications Manager (CUCM) the endpoint may be
part of a shared line. This means that several devices share the same directory number. The
different devices sharing the same number receive status from the other appearances on the
line as defined in RFC 4235.
Note that shared lines are set up by CUCM, not by the endpoint. Therefore do not change this
setting manually; CUCM pushes this information to the endpoint when required.
Requires user role: ADMIN
Value space: <Private/Shared>
Shared: The system is part of a shared line and is therefore sharing its directory number with
other devices.
Private: This system is not part of a shared line (default).
Example:
SIP Profile 1 Line: Private
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
95
Page 96
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
Standby settings
Standby Control
Determine whether the system should go into standby mode or not.
Requires user role: ADMIN
Value space: <Off/On>
Off: The system will not enter standby mode.
On: Enter standby mode when the Standby Delay has timed out. Requires the Standby Delay
to be set to an appropriate value.
Example:
Standby Control: On
Standby Delay
Define how long (in minutes) the system shall be in idle mode before it goes into standby mode.
Requires the Standby Control to be enabled.
Requires user role: ADMIN
Value space: <1..480>
Range: Select a value between 1 and 480 minutes.
Example:
Standby Delay: 10
Standby BootAction
Define the camera position after a restart of the codec.
Requires user role: ADMIN
Value space: <None/Preset1/Preset2/Preset3/Preset4/Preset5/Preset6/Preset7/Preset8/
Preset9/Preset10/Preset11/Preset12/Preset13/Preset14/Preset15/RestoreCameraPosition/
DefaultCameraPosition>
None: No action.
Preset1 to Preset15: After a reboot the camera position will be set to the position defined by
the selected preset.
RestoreCameraPosition: After a reboot the camera position will be set to the position it had
before the last boot.
DefaultCameraPosition: After a reboot the camera position will be set to the factory default
position.
Example:
Stand by Boot Action: DefaultCameraPosition
Standby StandbyAction
Define the camera position when going into standby mode.
Requires user role: ADMIN
Value space: <None/PrivacyPosition>
None: No action.
PrivacyPosition: Turns the camera to a sideways position for privacy.
Example:
Standby StandbyAction: PrivacyPosition
Standby WakeupAction
Define the camera position when leaving standby mode.
Requires user role: ADMIN
Value space: <None/Preset1/Preset2/Preset3/Preset4/Preset5/Preset6/Preset7/Preset8/
Preset9/Preset10/Preset11/Preset12/Preset13/Preset14/Preset15/RestoreCameraPosition/
DefaultCameraPosition>
None: No action.
Preset1 to Preset15: When leaving standby the camera position will be set to the position
defined by the selected preset.
RestoreCameraPosition: When leaving standby the camera position will be set to the position
it had before entering standby.
DefaultCameraPosition: When leaving standby the camera position will be set to the factor y
default position.
Example:
Standby WakeupAction: RestoreCameraPosition
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
96
Page 97
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
SystemUnit settings
SystemUnit Name
Define the system name. The system name will be sent as the hostname in a DHCP request and
when the codec is acting as an SNMP Agent.Define the system name. The system name will be
sent as the hostname in a DHCP request and when the codec is acting as an SNMP Agent.
Requires user role: ADMIN
Value space: <S: 0, 50>
Format: String with a maximum of 50 characters.
Example:
SystemUnit Name: "Meeting Room"
SystemUnit MenuLanguage
Select the language to be used on the Touch controller.
Requires user role: USER
Value space: <English/ChineseSimplified/ChineseTraditional/Catalan/Czech/Danish/
Dutch/Finnish/French/German/Hungarian/Italian/Japanese/Korean/Norwegian/Polish/
PortugueseBrazilian/Russian/Spanish/Swedish/Turkish/Arabic/Hebrew>
Example:
SystemUnit MenuLanguage: English
SystemUnit CallLogging Mode
Set the call logging mode for calls that are received or placed by the system. The call logs may
then be viewed via the web interface.
Requires user role: ADMIN
Value space: <Off/On>
Off: Disable logging.
On: Enable logging.
Example:
SystemUnit CallLogging Mode: On
SystemUnit ContactInfo Type
Choose which type of contact information to show in the status field in the upper left corner of
the Touch controller.
Requires user role: ADMIN
Value space: <Auto/None/IPv4/IPv6/H323Id/E164Alias/H320Number/SipUri/SystemName/
DisplayName>
Auto: Show the address which another system can dial to reach this system. The address
depends on the default call protocol and system registration.
None: Do not show any contact information in the status field.
IPv4: Show the IPv4 address as contact information.
IPv6: Show the IPv6 address as contact information.
H323Id: Show the H.323 ID as contact information (see the H323 Profile [1..1] H323Alias ID
settin g).
E164 Alias: Show the H.323 E164 Alias as contact information (see the H323 Profile [1..1]
H323Alias E164 setting).
H320Number: Show the H.320 number as contact information (only applicable if connected
to a Cisco TelePresence ISDN Link gateway).
SipUri: Show the SIP URI as contact information (see the SIP Profile [1..1] URI setting).
SystemName: Show the system name as contact information (see the SystemUnit Name
settin g).
DisplayName: Show the display name as contact information (see the SIP Profile [1..1]
DisplayName setting).
Example:
SystemUnit ContactInfo Type: Auto
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
97
Page 98
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
Time settings
Time TimeFormat
Set the time format.
Requires user role: USER
Value space: <24H/12H>
24H: Set the time format to 24 hours.
12H : Set the time format to 12 hours (AM/PM).
Example:
Time DateFormat
Set the date format.
Requires user role: USER
Value space: <DD_MM_YY/MM_DD_YY/YY_MM_DD>
Example:
Time TimeFor mat: 24H
DD _ M M _Y Y: The date January 30th 2010 will be displayed: 30.01.10
MM_DD _Y Y: The date January 30th 2010 will be displayed: 01.30.10
YY_MM_DD: The date January 30th 2010 will be displayed: 10.01.30
Tim e DateFormat: DD _ M M _ YY
Time Zone
This has been replaced with the Time OlsonZone setting as of software version TC7.2.
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
98
Page 99
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
Time OlsonZone
Set the time zone for the geographical location of the video system. The information in the
value space is from the tz database, also called the IANA Time Zone Database.
Requires user role: USER
Value space: <Africa/Abidjan, Africa/Accra, Africa/Addis_Ababa, Africa/Algiers, Africa/Asmara,
Africa/Asmera, Africa/Bamako, Africa/Bangui, Africa/Banjul, Africa/Bissau, Africa/Blantyre,
Africa/Brazzaville, Africa/Bujumbura, Africa/Cairo, Africa/Casablanca, Africa/Ceuta, Africa/
Conakry, Africa/Dakar, Africa/Dar_es_Salaam, Africa/Djibouti, Africa/Douala, Africa/El_Aaiun,
Africa/Freetown, Africa/Gaborone, Africa/Harare, Africa/Johannesburg, Africa/Juba, Africa/
Kampala, Africa/Khartoum, Africa/Kigali, Africa/Kinshasa, Africa/Lagos, Africa/Libreville, Africa/
Lome, Africa/Luanda, Africa/Lubumbashi, Africa/Lusaka, Africa/Malabo, Africa/Maputo, Africa/
Maseru, Africa/Mbabane, Africa/Mogadishu, Africa/Monrovia, Africa/Nairobi, Africa/Ndjamena,
Africa/Niamey, Africa/Nouakchott, Africa/Ouagadougou, Africa/Porto-Novo, Africa/Sao_Tome,
Africa/Timbuktu, Africa/Tripoli, Africa/Tunis, Africa/Windhoek, America/Adak, America/
Anchorage, America/Anguilla, America/Antigua, America/Araguaina, America/Argentina/
Buenos_Aires, America/Argentina/Catamarca, America/Argentina/ComodRivadavia, America/
Argentina/Cordoba, America/Argentina/Jujuy, America/Argentina/La_Rioja, America/Argentina/
Mendoza, America/Argentina/Rio_Gallegos, America/Argentina/Salta, America/Argentina/San_
Juan, America/Argentina/San_Luis, America/Argentina/Tucuman, America/Argentina/Ushuaia,
America/Aruba, America/Asuncion, America/Atikokan, America/Atka, America/Bahia, America/
Bahia_Banderas, America/Barbados, America/Belem, America/Belize, America/Blanc-Sablon,
America/Boa_Vista, America/Bogota, America/Boise, America/Buenos_Aires, America/
Cambridge_Bay, America/Campo_Grande, America/Cancun, America/Caracas, America/
Catamarca, America/Cayenne, America/Cayman, America/Chicago, America/Chihuahua,
America/Coral_Harbour, America/Cordoba, America/Costa_Rica, America/Creston, America/
Cuiaba, America/Curacao, America/Danmarkshavn, America/Dawson, America/Dawson_Creek,
America/Denver, America/Detroit, America/Dominica, America/Edmonton, America/Eirunepe,
America/El_Salvador, America/Ensenada, America/Fort_Wayne, America/Fortaleza, America/
Glace_Bay, America/Godthab, America/Goose_Bay, America/Grand_Turk, America/Grenada,
America/Guadeloupe, America/Guatemala, America/Guayaquil, America/Guyana, America/
Halifax, America/Havana, America/Hermosillo, America/Indiana/Indianapolis, America/Indiana/
Knox, America/Indiana/Marengo, America/Indiana/Petersburg, America/Indiana/Tell_City,
America/Indiana/Vevay, America/Indiana/Vincennes, America/Indiana/Winamac, America/
Indianapolis, America/Inuvik, America/Iqaluit, America/Jamaica, America/Jujuy, America/
Juneau, America/Kentucky/Louisville, America/Kentucky/Monticello, America/Knox_IN,
America/Kralendijk, America/La_Paz, America/Lima, America/Los_Angeles, America/Louisville,
America/Lower_Princes, America/Maceio, America/Managua, America/Manaus, America/
Marigot, America/Martinique, America/Matamoros, America/Mazatlan, America/Mendoza,
America/Menominee, America/Merida, America/Metlakatla, America/Mexico_City, America/
Miquelon, America/Moncton, America/Monterrey, America/Montevideo, America/Montreal,
America/Montserrat, America/Nassau, America/New_York, America/Nipigon, America/Nome,
America/Noronha, America/North_Dakota/Beulah, America/North_Dakota/Center, America/
North_Dakota/New_Salem, America/Ojinaga, America/Panama, America/Pangnirtung, America/
Paramaribo, America/Phoenix, America/Port-au-Prince, America/Port_of_Spain, America/
Porto_Acre, America/Porto_Velho, America/Puerto_Rico, America/Rainy_River, America/
Rankin_Inlet, America/Recife, America/Regina, America/Resolute, America/Rio_Branco,
America/Rosario, America/Santa_Isabel, America/Santarem, America/Santiago, America/
Santo_Domingo, America/Sao_Paulo, America/Scoresbysund, America/Shiprock, America/
Sitka, America/St_Barthelemy, America/St_Johns, America/St_Kitts, America/St_Lucia,
America/St_Thomas, America/St_Vincent, America/Swift_Current, America/Tegucigalpa,
America/Thule, America/Thunder_Bay, America/Tijuana, America/Toronto, America/Tortola,
America/Vancouver, America/Virgin, America/Whitehorse, America/Winnipeg, America/Yakutat,
America/Yellowknife, Antarctica/Casey, Antarctica/Davis, Antarctica/DumontDUrville, Antarctica/
Macquarie, Antarctica/Mawson, Antarctica/McMurdo, Antarctica/Palmer, Antarctica/Rothera,
Antarctica/South_Pole, Antarctica/Syowa, Antarctica/Vostok, Arctic/Longyearbyen, Asia/Aden,
Asia/Almaty, Asia/Amman, Asia/Anadyr, Asia/Aqtau, Asia/Aqtobe, Asia/Ashgabat, Asia/
Ashkhabad, Asia/Baghdad, Asia/Bahrain, Asia/Baku, Asia/Bangkok, Asia/Beirut, Asia/Bishkek,
Asia/Brunei, Asia/Calcutta, Asia/Choibalsan, Asia/Chongqing, Asia/Chungking, Asia/Colombo,
Asia/Dacca, Asia/Damascus, Asia/Dhaka, Asia/Dili, Asia/Dubai, Asia/Dushanbe, Asia/Gaza, Asia/
Harbin, Asia/Hebron, Asia/Ho_Chi_Minh, Asia/Hong_Kong, Asia/Hovd, Asia/Irkutsk, Asia/
Istanbul, Asia/Jakarta, Asia/Jayapura, Asia/Jerusalem, Asia/Kabul, Asia/Kamchatka, Asia/
Karachi, Asia/Kashgar, Asia/Kathmandu, Asia/Katmandu, Asia/Khandyga, Asia/Kolkata, Asia/
Krasnoyarsk, Asia/Kuala_Lumpur, Asia/Kuching, Asia/Kuwait, Asia/Macao, Asia/Macau, Asia/
Magadan, Asia/Makassar, Asia/Manila, Asia/Muscat, Asia/Nicosia, Asia/Novokuznetsk, Asia/
Novosibirsk, Asia/Omsk, Asia/Oral, Asia/Phnom_Penh, Asia/Pontianak, Asia/Pyongyang, Asia/
Qatar, Asia/Qyzylorda, Asia/Rangoon, Asia/Riyadh, Asia/Saigon, Asia/Sakhalin, Asia/Samarkand,
Asia/Seoul, Asia/Shanghai, Asia/Singapore, Asia/Taipei, Asia/Tashkent, Asia/Tbilisi, Asia/Tehran,
Asia/Tel_Aviv, Asia/Thimbu, Asia/Thimphu, Asia/Tokyo, Asia/Ujung_Pandang, Asia/Ulaanbaatar,
Asia/Ulan_Bator, Asia/Urumqi, Asia/Ust-Nera, Asia/Vientiane, Asia/Vladivostok, Asia/Yakutsk,
Asia/Yekaterinburg, Asia/Yerevan, Atlantic/Azores, Atlantic/Bermuda, Atlantic/Canary, Atlantic/
Cape_Verde, Atlantic/Faeroe, Atlantic/Faroe, Atlantic/Jan_Mayen, Atlantic/Madeira, Atlantic/
Reykjavik, Atlantic/South_Georgia, Atlantic/St_Helena, Atlantic/Stanley, Australia/ACT, Australia/
Adelaide, Australia/Brisbane, Australia/Broken_Hill, Australia/Canberra, Australia/Currie,
Australia/Darwin, Australia/Eucla, Australia/Hobart, Australia/LHI, Australia/Lindeman, Australia/
Lord_Howe, Australia/Melbourne, Australia/NSW, Australia/North, Australia/Perth, Australia/
Queensland, Australia/South, Australia/Sydney, Australia/Tasmania, Australia/Victoria, Australia/
West, Australia/Yancowinna, Brazil/Acre, Brazil/DeNoronha, Brazil/East, Brazil/West, CET,
CST6CDT, Canada/Atlantic, Canada/Central, Canada/East-Saskatchewan, Canada/Eastern,
Canada/Mountain, Canada/Newfoundland, Canada/Pacific, Canada/Saskatchewan, Canada/
Yukon, Chile/Continental, Chile/EasterIsland, Cuba, EET, EST, EST5EDT, Egypt, Eire, Etc/GMT,
Etc/GMT+0, Etc/GMT+1, Etc/GMT+10, Etc/GMT+11, Etc/GMT+12, Etc/GMT+2, Etc/GMT+3, Etc/
GMT+4, Etc/GMT+5, Etc/GMT+6, Etc/GMT+7, Etc/GMT+8, Etc/GMT+9, Etc/GMT-0, Etc/GMT-1,
Etc/GMT-10, Etc/GMT-11, Etc/GMT-12, Etc/GMT-13, Etc/GMT-14, Etc/GMT-2, Etc/GMT-3, Etc/
GMT-4, Etc/GMT-5, Etc/GMT-6, Etc/GMT-7, Etc/GMT-8, Etc/GMT-9, Etc/GMT0, Etc/Greenwich,
Etc/UCT, Etc/UTC, Etc/Universal, Etc/Zulu, Europe/Amsterdam, Europe/Andorra, Europe/Athens,
Europe/Belfast, Europe/Belgrade, Europe/Berlin, Europe/Bratislava, Europe/Brussels, Europe/
Bucharest, Europe/Budapest, Europe/Busingen, Europe/Chisinau, Europe/Copenhagen, Europe/
Dublin, Europe/Gibraltar, Europe/Guernsey, Europe/Helsinki, Europe/Isle_of_Man, Europe/
Istanbul, Europe/Jersey, Europe/Kaliningrad, Europe/Kiev, Europe/Lisbon, Europe/Ljubljana,
Europe/London, Europe/Luxembourg, Europe/Madrid, Europe/Malta, Europe/Mariehamn,
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
99
Page 100
Cisco TelePresence MX200 and MX300 Administrator Guide
Contents
Introduction
System settings
Setting passwords
Appendices
Web interface
System settings
Europe/Minsk, Europe/Monaco, Europe/Moscow, Europe/Nicosia, Europe/Oslo, Europe/Paris,
Europe/Podgorica, Europe/Prague, Europe/Riga, Europe/Rome, Europe/Samara, Europe/
San_Marino, Europe/Sarajevo, Europe/Simferopol, Europe/Skopje, Europe/Sofia, Europe/
Stockholm, Europe/Tallinn, Europe/Tirane, Europe/Tiraspol, Europe/Uzhgorod, Europe/Vaduz,
Europe/Vatican, Europe/Vienna, Europe/Vilnius, Europe/Volgograd, Europe/Warsaw, Europe/
Zagreb, Europe/Zaporozhye, Europe/Zurich, GB, GB-Eire, GMT, GMT+0, GMT-0, GMT0,
Greenwich, HST, Hongkong, Iceland, Indian/Antananarivo, Indian/Chagos, Indian/Christmas,
Indian/Cocos, Indian/Comoro, Indian/Kerguelen, Indian/Mahe, Indian/Maldives, Indian/Mauritius,
Indian/Mayotte, Indian/Reunion, Iran, Israel, Jamaica, Japan, Kwajalein, Libya, MET, MST,
MST7MDT, Mexico/BajaNorte, Mexico/BajaSur, Mexico/General, NZ, NZ-CHAT, Navajo, PRC,
PST8PDT, Pacific/Apia, Pacific/Auckland, Pacific/Chatham, Pacific/Chuuk, Pacific/Easter,
Pacific/Efate, Pacific/Enderbury, Pacific/Fakaofo, Pacific/Fiji, Pacific/Funafuti, Pacific/Galapagos,
Pacific/Gambier, Pacific/Guadalcanal, Pacific/Guam, Pacific/Honolulu, Pacific/Johnston, Pacific/
Kiritimati, Pacific/Kosrae, Pacific/Kwajalein, Pacific/Majuro, Pacific/Marquesas, Pacific/Midway,
Pacific/Nauru, Pacific/Niue, Pacific/Norfolk, Pacific/Noumea, Pacific/Pago_Pago, Pacific/Palau,
Pacific/Pitcairn, Pacific/Pohnpei, Pacific/Ponape, Pacific/Port_Moresby, Pacific/Rarotonga,
Pacific/Saipan, Pacific/Samoa, Pacific/Tahiti, Pacific/Tarawa, Pacific/Tongatapu, Pacific/Truk,
Pacific/Wake, Pacific/Wallis, Pacific/Yap, Poland, Portugal, ROC, ROK, Singapore, Turkey, UCT,
US/Alaska, US/Aleutian, US/Arizona, US/Central, US/East-Indiana, US/Eastern, US/Hawaii, US/
Indiana-Starke, US/Michigan, US/Mountain, US/Pacific, US/Pacific-New, US/Samoa, UTC,
Universal, W-SU, WET, Zulu>
Range: Select a time zone from the list.
Example:
Time OlsonZone: Etc/UTC
D14850.12 MX200 and MX300 Administrator Guide TC7.3, JULY 2015. www.cisco.com — Copyright © 2011–2015 Cisco Systems, Inc. All rights reserved.
100
Loading...