This guide introduces you to the Application Programmer
Interface (API) for the Collaboration Endpoint software, and
serves as a reference guide for the command line commands
for the following product:
• Cisco TelePresence MX700 and MX800
The guide describes the API for on-premise registered video
systems (CUCM, VCS) as well as video systems registered
to Cisco’s cloud service (Cisco Spark). For Cisco Spark
registered systems only a subset of the API is available, and
the user role (integrator and roomcontrol) of the local user
determines which commands are available.
API Reference Guide
Downloading the user documentation
You can download the user documentation from the Cisco
web site, go to: http://www.cisco.com/go/mx-docs
For Spark registred systems, go to:
https://support.ciscospark.com
Guidelines for how to find the documentation on the Cisco
web site are included in theUser documentation on the
Cisco web site appendix.
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
This section provides an overview of the new and
changed system settings, and the new features and
improvements in the Cisco Collaboration Endpoint
software version 9.2 (CE9.2) compared to CE9.1.
For more details, we recommend reading the Software
release notes:
The macro framework allows users and integrators to write
JavaScript macros in order to automate scenarios and
customize endpoint behavior so that it suites an individual
customer’s requirements.
The combination of macros and powerful features such as
listening for events/status changes, automating execution of
commands and configurations, and providing local control
functionality for the In-Room control feature, provides many
possibilities for custom setups.
Minor behavioral changes, such as having the video system
in Do Not Disturb for an infinite amount of time, can be
easily realized by macros. Some other examples are: Reset
configurations automatically, make a call at a certain time
of the day, and issue alert or help messages depending on
status changes.
The macro editor, which also provides several example
macros, is available from the video system’s web interface.
Branding and halfwake customization
You can upload your own text and images to customize the
appearance of the screen and user interface in both the
halfwake state and the awake state.
In the Halfwake state you can:
• Add a background brand image to the screen and user
interface.
• Add a small logo in the bottom right corner of the screen
and user interface.
In the Awake state you can:
• Add a small logo in the bottom right corner of the screen
and user interface.
• Add a label or message in the bottom left corner of the
screen (not the user interface).
Source composition
You can compose up to four input sources (depending on
how many input sources are available on the codec) into one
image. This is the image that will be sent in the main video
stream to the far end in a call. Source composition can only
be enabled via the API, so we recommend creating a user
interface extension combined with a macro to control the
compositions on demand.
This feature replaces some of the functionality that was
provided by the TC Console application for TC software.
HTTP Proxy support
You can set up the video system to go through a HTTP Proxy
when registering it to Cisco’s cloud service, Cisco Spark.
User interface features
• The Settings panel is restructured.
• The Settings panel in the user interface (To u ch 10) can
be protected by the video system’s admin password. If
the password is blank, anyone can access the Settings
and factory reset the system.
• If you select the Russian language on the user interface,
you can choose between a Russian keyboard and a
keyboard with a Latin character set.
• Arabic and Hebrew languages are added to the user
interface. Also localized keyboards are included.
• Basic IEEE 802.1x settings are added to the Settings
panel in the user interface.
Support for the Snap to Whiteboard feature
The Snap to Whiteboard feature is now available for all
products that have a camera with speaker track functionality:
SX80 with Cisco TelePresence Speaker Track 60 camera or
Cisco Spark Quad camera, MX700/MX800 with dual camera,
RoomKit, RoomKit Plus, Room 55 and Room70.
When the video system detects a person that is speaking
close to the whiteboard, the camera view will switch to the
whiteboard area. The wizard in the Settings panel on the
Touch 10 user interface helps you to set up the feature and
define where the whiteboard area is.
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
The Briefing Room feature, which was introduced already
in TC software, has been reworked. The in-room control
framework is used for creating the associated user interface
elements.
As before, Briefing Room is suppor ted only for dual camera
systems. Also, you need a Precision 60 camera, and a total of
three screens.
Mute and unmute remote participants in a CMS hosted
conference (Active Control)
When a video system is enabled for Active Control in a CMS
(2.1 or later) conference you can mute and unmute remote
participants from the participant list on the user interface (the
feature must also be enabled on the CMS).
A video system that is running software version CE9.2 will
not be unmuted directly. When you try to unmute such a
video system remotely, a message will show up on its screen
requesting the user to unmute the audio locally.
API commands for Custom input prompt
API commands are introduced to allow for an input prompt
in the user interface:
TextInput *
with your custom text, a text input field for the user, and a
submit button, shows up on the user interface. For example,
you can prompt a user to leave feedback after an ended call.
You can specify what type of input you want from the user:
single line text, numeric, password, or PIN code.
The prompt can only be enabled via the API, so it is recommended to combine it with macros and either a custom user
interface panel or an auto-triggered event.
Certificate upload via API
ASCII PEM formatted certificates can be installed directly
using multiline API commands (
. When issuing the display command a prompt
Ceritifcates CA Add
Services Add
system from its web interface, as before.
xCommand UserInterface Message
xCommand Security
, or
xCommand Security Ceritifcates
). You can also upload certificates to a video
API commands for user management
You can create and manage user accounts directly using API
commands (
you can also do this from the video system’s user interface.
Preview mode for In-Room Controls
The In-Room Control editor has a new preview mode. A
virtual Touch 10 user interface shows how the design looks
on the user interface. The user interface is interactive so
that you can test the functionality. It produces real events
on the video system, which can trigger any functionality
you have created with a third-party control system or with a
macro. A console in the right pane displays both the widget
values when interacted with, and control system feedback
messages.
Intelligent Proximity changes
A Proximity indicator is displayed on the screen (middle right)
to inform that one or more clients are paired to the system
with Cisco Proximity. The old indicator (top left), which
was always shown when Proximity was enabled, has been
removed.
You can no longer disable the Proximity services from the
user interface.
The ultrasound settings have moved from Peripherals Pairing
Ultrasound to Audio Ultrasound.
Automatic factory reset when changing the call service
(device activation)
The video system will automatically factory reset and restart
when using the user interface to change the device activation method, for example from VCS to Cisco UCM. This will
prevent conflicting configurations when provisioning the video
system to a new service.
Changing the provisioning from the API will not automatically
factory reset the video system.
xCommand UserManagement User *
). As before,
Support for separate RTP port ranges for audio and other
media
You can configure the video system so that audio uses a
different RTP port range than other media. The two ranges
cannot overlap. As default, all media use the same RTP port
range.
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
This section provides an overview of the new and changed
system settings, and the new features and improvements
in the Cisco Collaboration Endpoint software version 9.1
(CE9.1) compared to CE9.0.
For more details, we recommend reading the Software
release notes:
Dual Screen experience and Active Control for CMS based
meetings
Dual screen video systems can utilize both screens for video
in a CMS based meeting. The video system receives two
transcoded video streams and one content stream from the
CMS, and utilizes both screens to render the streams.
With Active Control enabled, you get a participant list that
shows all meeting participants and their current activity
status, such as mute, sharing and active speaker indication.
You can change the layout seamlessly from the touch
interface by using the layout selection panels.
New wake-up experience
The new wake-up experience introduces a Halfwake state,
which leads to a calmer wake-up of the system, and gives
users better guidance on how to get started.
When wake-up on motion detection is enabled the system
will automatically wake to the Halfwake state when people
enter the room. It will also wake to this state when a user
pairs a Cisco Proximity client to the system.
Additions for Room Analytics
Detect people presence in the room: The video system has
the capability to find whether there are people present in the
room. The feature is based on ultrasound, and it does not
keep record of who was in the room, only whether or not the
room is in use.
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
This section provides an overview of the new and changed
system settings, and the new features and improvements
in the Cisco Collaboration Endpoint software version 9.0
(CE9.0) compared to CE8.3.
For more details, we recommend reading the Software
release notes:
The user interfaces on the Touch 10, on screen, and on the
integrated touch screen have been updated. The main menu
items on the home screen have been replaced with more
prominent activities.
Some of the setting have been removed from the Touch 10
advanced settings menu to align with the on-screen display
menu.
Wakeup on motion detection
Wakeup on motion detection senses when a person
walks into the conference room and the system wakes up
automatically. You need to enable the following setting for this
feature to work:
xConfiguration Standby WakeupOnMotionDetection
You can’t manually place the system in standby when this
feature is enabled.
Updated In-Room Control Editor
The In-Room Control editor is updated with a new look,
improved logic and usability for producing a control interface
more efficiently. In addition, a new directional pad widget and
an In-Room Control simulator is added.
Added language support
We have added support for Potuguese (Portugal) to the
on-screen display and Touch controller menus.
Other changes
• Support for HTTPS client certificates has been added.
• Unplugging the presentation cable instantly stops the
presentation sharing.
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
This chapter contains a top-level view of the mechanisms
supported by the codec API.
Here you can read about how to access the API, how to use
the command line and what the different parts of the API
can be used for. This chapter also describes how to use the
feedback functions that are available for the codec.
The API consists of four major groups:
• Commands
• Configurations
• Status
• Events
These four groups are hierarchically organized, which
makes it easier to find related functionality. You can find the
complete lists of all commands, configurations and statuses
in the following chapters.
Connecting to the API
There are several ways to access the codec API. Regardless
of which method you choose, the structure of the API stays
the same. Choose the connection method that suits your
application best. Before you start, please read this section
about the different methods, as some of those may require
additional configuration changes before being enabled.
The following configurations, apart from password, can be set
from the System configuration menu on the web interface or
from the command line interface. All of the examples are for
the command line interface.
Password
The video system is delivered with a default user account
with full credentials. The user name is admin, and initially, no
password is set for the default user.
It is mandatory to set a password for the admin user in
order to restrict access to system configuration. You should
in addition set a password for any other user with similar
credentials.
You can set the password on the codec’s web interface.
Open a web browser and enter the IP address of the video
system in the address bar and log in. Click your user name in
the upper right corner and choose Change password in the
drop down menu.
API Reference Guide
SSH
SSH is a secure TCP/IP connection and it is enabled by
default on the codec. It can be disabled. You need a SSH
client, such as PuTTY, to access the API over SSH.
xConfiguration NetworkServices SSH Mode:
<O f f,O n>
Telnet
Telnet can be viewed as the equivalent of the serial protocol
in the TCP/IP world. Telnet is disabled by default. Before
connecting to the codec with Telnet you have to enable it.
To enable Telnet service, configure the following setting on
the codec. Changing this setting does not require a reboot of
the device, but it may take some time to take effect.
xConfiguration NetworkServices Telnet Mode:
<O f f,O n>
HTTP/HTTPS
As HTTP/HTTPS are connectionless protocols, there
is no persistent connection. There are several ways of
communicating with the API over HTTP.
In order to enable or disable the HT TP and HTTPS services,
configure the following setting on the codec.
xConfiguration NetworkServices HTTP Mode:
<Off, HTTP+HTTPS, HTTPS>
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
Connecting
You can inspect the API by entering the IP address or host
name of the codec in your favorite web browser. In the
web interface, you can find the API documents under the
menu section Integration > Developer API. The HTTP POST
and GET methods are used to execute commands and get
feedback from the codec. This is described in ”Using HTTP”
The video system has a standard COM-port for serial
communication. It can be used without an IP address, DNS or
a network. Serial connection is allowed by default.
xConfiguration SerialPort Mode: <Off/On>
Connect a standard 9-pin serial cable <115200, N, 8, 1> to
the COM port on the codec.
Baud-rate and other serial port parameters
The serial port uses 8 data bits, no parity and 1 stop bit. The
default baud rate is set to 11520 0 bps.
The codec can give very much feedback. We therefore
recommend keeping the connection at this speed to avoid
sluggishness.
You can change the baud rate if required.
xConfiguration SerialPort BaudRate:
<9600/19200/38400/57600/115200>
Login and password
You can choose whether login is required or not for serial
connections. For security reasons the password prompting is
turned on by default, but it can be turned off if preferred.
A user account may hold one or a combination of user roles.
A user account with full access rights, like the default admin
user, should possess the ADMIN, USER and AUDIT roles.
These are the user roles:
ADMIN: A user with this role can create new users, change
most settings, make calls, and search the contact lists. The
user cannot upload audit certificates and change the security
audit settings.
USER: A user with this role can make calls and search the
contact lists. The user can modify a few settings, for example
adjust the ringtone volume and set the time and date format.
AUDIT: A user with this role can change the security audit
settings and upload audit certificates.
ROOMCONTROL: A user with this role can create in-room
controls. The user has access to the In-room control editor
and corresponding developement tools.
INTEGR ATOR: A user with this role has access to settings,
commands and status that are required to set up advanced
AV scenarios, and to integrate our video systems with 3rd
party equipment. Such a user can also create in-room
controls.
Cisco Spark registered systems
If a video system is registered to Cisco’s cloud service
(Cisco Spark), only local users with the INTEGR ATOR and
ROOMCONTROL user roles are available.
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
To get a list of all supported top level commands you can
type ? or help after connecting to the TelePresence System
using RS-232, Telnet or SSH (Example 1).
Bye
Typing the bye command closes the command line interface.
API commands
xConfiguration
Configurations are system settings, such as system name
and network settings. These are persistent across boots.
Refer to ”Configurations” on page 27.
xCommand
Commands instruct the codec to execute actions, such as to
dial a number or to search the phone book.
Refer to ”Commands” on page 27.
xStatus
A status contains the current state of the codec, such as
connected calls, the status of the gatekeeper registration,
connected inputs and output sources.
Refer to ”Status” on page 27.
xFeedback
The Feedback commands are used to specify what parts of
the configuration and status hierarchies to monitor. Feedback
is only issued on the RS-232, Telnet or SSH session for
which it is specified. If you are connecting to the codec with
multiple sessions, you have to define feedback individually
for each session. Refer to ”Feedback mechanism” on page
The xPreferences command is used to set preferences for
the RS-232, Telnet and SSH sessions.
Refer to ”API output” on page 24.
Echo <on/off>
If echo is set to On the key inputs are displayed when
entering text in a command line interface.
If echo is set to Off user input is not displayed when entering
text in a command line interface.
xEvent
The xEvent command returns information on which events are
available for feedback. Refer to ”Events” on page 30.
xGetxml
The xGetxml request returns an XML document based on the
location parameter attached to the request. The elements
(or a complete document) matching the expression will be
returned. Refer to ”Feedback mechanism” on page 31.
xcom mand xconfiguration xevent xfeedback
Other commands
Systemtools
The systemtools commands are a set of command line tools
for administrative control and diagnostics. The commands
can be used for advanced troubleshooting together with
Cisco technical support. Systemtools are not a part of the
programming API. Refer to ”The SystemTools commands”
on page 237.
Log
The log command is used to enable advanced logs. It is only
used for debugging the system.
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
If your client supports it, there are some timesaving shortcuts
you can use:
• Tab-completion to complete the commands and
arguments.
• Arrow up and arrow down keys to navigate your
command history.
• <CTRL-a>: Jump to the beginning of the line.
• <CTRL-e>: Jump to the end of the line.
• <CTRL-r>: Incremental command history search.
• <CTRL-w>: Erase the current line.
Searching
You can use // to search for elements anywhere in the status
or configuration hierarchy (Example 1).
You can also combine multiple //’s (Example 2).
NOTE: The search shortcuts work well for inspecting the
API, but should not be used in applications. We recommend
that you always use the complete paths to avoid command
ambiguity when upgrading to newer firmware releases.
Example 1:
List all configurations that include words that starts with OUT
and HDMI:
x c o n f i g u r a t i o n // o u t // h d m i
*c xConfiguration Audio Output HDMI 1 Level: 0
*c xConfiguration Audio Output HDMI 1 Mode: On
*c xConfiguration Audio Output HDMI 2 Level: 0
*c xConfiguration Audio Output HDMI 2 Mode: Off
** end
Example 2:
Get the resolution width of all connected sources for both
inputs and outputs:
x S t a t u s // v i d // r e s // w i d
*s Video Input Source 1 Resolution Width: 1920
*s Video Input Source 2 Resolution Width: 0
*s Video Input Source 3 Resolution Width: 0
*s Video Input Source 4 Resolution Width: 0
*s Video Output Connector 1 Resolution Width: 1920
*s Video Output Connector 2 Resolution Width: 1280
*s Video Output Connector 3 Resolution Width: 1280
** end
Value types and formats
The system supports the following value types:
• Integer values: <x..y>
Defines the valid range for an integer input. x = min value,
y = max value.
• Literal values: <X/Y/../Z>
Defines the possible values for a given configuration.
• String values: <S: x, y>
Defines that the valid input for this configuration is a
string with minimum length of x and maximum length of
y characters. Strings can have rules that further specify
their format and length.
Input values that contain spaces need to be quoted
Any values for configurations and commands containing
spaces must be enclosed in quotes. Quotes are not
necessary for values without spaces.
Example:
Correct:
contains spaces”
Correct:
Incorrect:
contains spaces
Case sensitivity
All commands are case-insensitive. All of the following
commands will work.
XCOMMAND DIAL NUMBER: foo@bar.org
xcom mand dial nu mber: foo@bar.org
xCom mand Dial Number: foo@bar.org
xCommand dial number: “my number
xCommand dial number: 12345
xCommand dial number: my number
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
Commands instruct the codec to execute actions, such as
to dial a number or to search the phone book. All commands
start with the prefix xCommand followed by a command path.
Writing xCommand ? on the command line will list all the top
level commands.
To view the complete list of commands and their parameters,
write xCommand ?? on the command line.
Command arguments are key-value pairs.
When issuing a xCommand, the command consists of one
argument and one required parameter. In this document the
command usage is described for all xCommands, with both
required and optional parameters. The optional parameters
are in brackets.
Example: xCommand Dial Number: 123
• xCommand is the command prefix. The command to be
executed is Dial.
• The example contains one argument, Number: 123.
Number is the key and 123 is its value. The key/value pair
is separated with ‘:’.
Configurations
Configurations are system settings that are persistent across
boots. Like commands, also configurations are structured in
a hierarchy.
Writing xConfiguration ? on the command line lists all the top
level configurations.
Writing xConfiguration ?? lists all configurations and their
value spaces.
Writing xConfiguration lists all configurations and their
current values. To list out only some of the configurations,
write xConfiguration followed by one or more parts of the
configuration paths.
A status contains the current state of the codec, such as
connected calls, the status of the gatekeeper registration,
connected inputs and output sources.
Writing xStatus ? on the command line lists all top level
statuses.
Writing xStatus lists all statuses and their current values.
To list out only some of the statuses, write xstatus followed by
the relevant part of the status path (address expression):
xStatus <address expression>
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
Multiline commands are commands that support larger
amounts of data as input than the single line commands.
Typical use for these commands is to allow for provi-
sioning of in-room control definitions, branding images
(base64 encoded), macros, welcome banners, and security
certificates.
To issue a multiline command, you start issuing it like
any other XAPI command. However, once you enter the
command, you have set the API into an input mode where
anything you issue on the API after this is treated as input
to that command, including line breaks. You now enter the
payload for this command in accordance to the input format
expected by this command
When done, finish with a line break(“\n”) and a separate line
containing just a period ending with a line break (“.\n”). The
command will now be executed, and you will get a command
result with an OK or ERROR depending on the command
being executed successfully or not.
The commands that require multiline input format are marked
as such in the command descriptions in this guide.
The multiline commands are marked as multiline in
xCommand overview section in this guide.
API Reference Guide
Example: Set up welcome banner text
xCommand SystemUnit SignInBanner Set
Hell o!
This is the second line of text.
This is the third.
Thank yo u!
.
OK
*r SignInBannerSetResult (status=OK):
** end
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
The API works asynchronously. This means that there is no
guarantee that command responses arrive in the same order
as the commands were issued. The codec may also respond
with feedback between your request and the response, in
form of status changes or events, due to changes on the
system.
For some applications it might be crucial to match requests
with responses. The API therefore supports a responsetagging mechanism.
This mechanism works with all command types: xcommand,
xconfiguration, and xstatus. A typical use of this would be
to create a command queue in your application and assign
unique IDs to every command sent to the codec. A listener
then listens to all feedback from the codec and matches
the ID on the response with the corresponding ID in the
command queue. This enables matching the original request
with the specific response.
Example:
xcommand Video Layout Add | resultId=”mytag _ 1”
OK
*r VideoLayoutAddResult (status=OK):
LayoutId: 1
** resultId: “mytag _ 1”
** end
In XML mode the resultId is added as an attribute to the top-level XmlDoc tag:
xget x ml /Configuration/Video/Layout/Scali ng | resultId=”mytag _ 2”
<X mlDoc resultId=”my tag _ 2”>
<Configuration item=”1”>
< Vid e o ite m = ”1”>
<L a y o ut ite m = ” 1”>
<Scaling item=”1” valueSpaceRef=”...”>Off</Scaling>
</Layout>
</Vid eo>
</Configuration>
</XmlD oc>
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
Event returns information about the events that are available
for feedback. This overview presents examples of some the
events that are available on the API.
To get an overview of the supported events type ?, ?? or help
after xEvent:
• xEvent ? Lists the top level events
• xEvent ?? List all of the available events
• xEvent help Lists the top level events
The result for events depends on the state of the codec.
Example 1: Outgoing Call Indication
Outgoing Call Indication is an event reported when an
outgoing call is about to be dialled. Returns the CallId the
call has been assigned.
*e OutgoingCallIndication CallId: x
** end
Example 2: Call Disconnect
Call Disconnect is an event reported when a call is
disconnected. Returns the CallId of the disconnected call
and reason for the call’s disconnection.
To build solutions that can reliably keep the state between
your application and the codec synchronized, you can set up
a notification system to report the changes in the state of the
codec.
The API supports notifications on the following:
• Configuration changes
• Status changes
• Event notifications
These notifications will not be sent unless you have explicitly
told the codec to do so. You can subscribe to the feedback
by registering feedback expressions. How you register
feedback expressions varies according to the connection
method used.
When using HTTP, the method of handling feedback differs
slightly from what is presented in this section. See the
”Feedback from codec over HTTP” on page 35 for more
information.
WARNING: A codec may give very much feedback,
especially when calls are connected and disconnected.
Therefore, you should only subscribe to the feedback
that you need.
Never register for all status feedback by issuing
xFeedback register /Status. This may give the control
application too much data to handle, which may lead to
sluggish or unpredictable behavior.
Feedback expressions
The expression used when registering for feedback is a
variant of the XPath language. The XPath language describes
a way to select nodes from an XML/JSON document. The CE
software contains three main feedback documents.
DocumentAPI commandPath
StatusxStatus/Status
ConfigurationxConfiguration/Configuration
EventxEvent/Event
The syntax for feedback registering is:
xFeedback register <path>
Never register for all status feedback by issuing xFeedback
register /Status.
It is safe to register for all configuration changes using
xFeedback register /Configuration,
changes will most likely not occur that often.
By going through some examples, we can see how this
information can be used to build feedback expressions. A
good way to verify the expressions is to point your browser
to http://<ip-address>/getxml?location=path or to execute
To register, list and deregister feedback expressions you
use the command xFeedback and its corresponding sub
commands.
The registered expressions are only valid for the currently
active connection. If you open two Telnet sessions and
register to get feedback in one session, you do not receive
feedback in the other session. This also means that if you
disconnect from a session, you have to re-register all
expressions after reconnecting.
You can register up to 38 expressions.
Feedback output
The feedback output is exactly the same as you get when
querying the system using the xConfiguration and xStatus
commands. E.g., if you issue the command
Ac tive
on the command line the result is:
*s Standby Active: On
** end
If you have registered for feedback on status changes the
feedback you get when the system goes to standby-mode
will be exactly the same:
*s Standby Active: On
** end
This means that when you are programming against the
device you only need to handle one format.
xStatus Standby
Example: Managing feedback subscriptions
A: Register feedback expressions.
Write in:
Result:
Write in:
Result:
Write in:
xFeedback register /Status/Audio
** end
OK
xFeed back register /Event/CallDisconnect
** end
OK
xFeedback register /Configuration/Video/
MainVideoSource
Result:
B: List out currently registered expressions.
Write in:
Result:
C: Deregister feedback expressions.
Write in:
Result:
Write in:
Result:
D: List the new feedback expressions.
Write in:
Result:
** end
OK
xFeedback list
/Configuration/Video/MainVideoSource
/Event/CallDisconnect
/St a tus/A u d io
** end
OK
xFeed back deregister /Event/CallDisconnect
** end
OK
xFeedback deregister /Status/Audio
** end
OK
xFeedback list
/Configuration/Video/MainVideoSource
** end
OK
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
The codec supports sending commands and configurations
over HTTP and HTTPS. It is also possible to retrieve
configurations and statuses this way. This interface exposes
the same API as the command line, but in XML format.
HTTP XMLAPI Authentication
Access to the XMLAPI requires the user to authenticate using
HTTP Basic Access Authentication as a user with ‘ADMIN’
role. Unauthenticated requests prompt a 401 HTTP response
containing a Basic Access Authentication challenge. How to
use HTTP Basic Access Authentication varies according to
the HTTP library or tool that you are using.
If your application will be issuing multiple commands
through the API, we highly recommend that you use Session
Authentication (see below). The standard basic authentication
does a full re-authentication per request, which may affect
the performance of your application.
HTTP XMLAPI Session Authentication
Authenticating with your username and password
combination for each API request might introduce too
much latency for some use-cases. To mitigate this, the API
supports a session-based authentication mechanism.
To open a session, issue a POST to http://<ip-address>/
xmlapi/session/begin with Basic Access Authentication. The
response sets a SessionId-cookie that can be used with
subsequent requests.
Note that when using API Session Authentication, it is
important to explicitly close the session when you are done.
Failing to do so may cause the device to run out of sessions,
as there are a limited number of concurrent sessions
available, and they do not time out automatically.
URL cheat sheet
The following table contains the main URLs used when accessing the API over HTTP.
MethodURLDescription
GEThttp://<ip-address>/status.xmlComplete status document
Example 4: Get all video configurations of the codec.
http://<ip-address>/getx ml?location=/Configuration/
Vide o
Sending commands and configurations
Using HTTP POST
When sending configurations and commands to the codec, it
is important that the HTTP header Content-Type is set totext/
xml, i.e. Content-Type: text/xml. The body of the POST should
contain the XML content.
Example 1: Changing the system name.
Request
POST /putxml HTTP/1.1
Content-Type: text/xml
<Configu ration>
<SystemUnit>
<Name>newName</Name>
</Syst e m U n it>
</Configuration>
Example 2: Setting the camera position.
Request
POST /putxml HTTP/1.1
Content-Type: text/xml
<Command>
<Camera>
<PositionSet command=”True”>
<C a m e r a Id >1</Ca m eraI d >
<Pan>200</Pan>
<Tilt>200</Tilt>
</Position Set>
</Camera>
</Command>
Response
HTTP/1.1 200 OK
Content-Type: text/xml
Content-Length: 91
<?xml version=”1.0”?>
<Command>
<Ca m e ra Po sitionSetResu lt ite m=”1” st atus =”OK”/>
</Command>
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
You can get the device to post http feedback messages
(also known as webhooks) on changes to the API state, e.g.
statuses, events and configuration updates. The HTTP Post
feedback messages will be sent to the specified ServerURL.
You can choose between events being posted in either XML
or JSON format. You can subscribe to changes on multiple
parts of the API by register up to 15 different feedback
expressions.
Registering for feedback
The command for registering is
Register
described in this section.
HttpFeedback Register syntax:
. The syntax for this command and its arguments are
xCom mand HttpFeedback Register
FeedbackSlot: <1..4>
ServerUrl(r): <S: 1, 2048>
Format: <XML/JSON>
Expression: <S: 1, 255>
Expression: <S: 1, 255>
Expression: <S: 1, 255>
Expression: <S: 1, 255>
Expression: <S: 1, 255>
Expression: <S: 1, 255>
Expression: <S: 1, 255>
Expression: <S: 1, 255>
Expression: <S: 1, 255>
Expression: <S: 1, 255>
Expression: <S: 1, 255>
Expression: <S: 1, 255>
Expression: <S: 1, 255>
Expression: <S: 1, 255>
Expression: <S: 1, 255>
xComma nd HttpFeedback
HttpFeedback Register arguments:
FeedbackSlot: The codec can register up to 4 slots of servers
requesting HTTP feedback. Set the registering to one of them.
NOTE: Avoid using FeedbackSlot 3 in an environment where
Cisco TelePresence Management Suite (TMS) is used as TMS
uses this feedback slot to register its expressions.
ServerUrl: The URL to the HTTP server where you want the
codec to post the HTTP feedback messages to.
Format: Set the format for the feedback from the HTTP server
to XML or JSON.
Expression 1-15: The XPath expression specifies which parts
of the Status, Configuration or Event documents are monitored.
You can have from 1 to 15 XPath expressions
Register the expressions you want to receive feedback on.
See the “Feedback mechanism” on page 31 section for
more information about the expression formats.
Example: Registering feedback on configuration changes,
disconnect events and call status changes.
POST /putxml HTTP/1.1
Content-Type: text/xml
<Command>
<HttpFeedback>
<Register com mand=”True”>
<FeedbackSlot>1</FeedbackSlot>
<S er v e r U r l > http://127.0.0.1/ myhttpp ostscripturl</ServerUrl>
When the codec notifies the registered HTTP server about
changes, the body contains the same XML as when polling.
There is however one small difference. The root-node
contains an Identification node with children that specify the
codec from which the notification originated. This means that
you can handle multiple codecs with a single HTTP server URI.
Here are some best practices when programming the Cisco
MX series API.
DO use complete commands
You should always use complete commands when
programming, i.e. always use xConfiguration Video instead of
xconf vid. The shortcuts can be used for searches in the API
on the command line, but not for programming. The reason
for this is that you might end up with ambiguous code when
additional commands are added to the API.
DO NOT subscribe to unnecessary feedback
Subscribing to too much feedback may congest the control
application. Although the amount of feedback may seem fine
in the current version, the amount of feedback may grow in
future releases.
API Reference Guide
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
Define the default volume for the speakers. The volume is set 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. You may also use API commands (xCommand Audio Volume) to change the
volume while the video system is running, and to reset to default value.
Requires user role: ADMIN, INTEGRATOR, USER
Default value: 50
USAGE:
xConfiguration Aud io D e faultVo lum e: D efau ltVolu me
where
Defau ltVolu m e
Select a value between 1 and 100. This corresponds to the dB range from -34.5 dB to
15 dB, in steps of 0.5 dB. If set to 0 the audio is switched off.
xConfiguration Audio Microphones Mute Enabled
Define the microphone mute behaviour on the video system.
Requires user role: ADMIN, INTEGRATOR
Default value: True
USAGE:
xConfiguration Aud io Microphones Mute Ena bled: Enabled
where
Enabled
True: 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.
Set the microphone reinforcement mode individually on each microphone. The signals from all
microphones with Mode = On will be mixed and fed to the selected MicrophoneReinforcement
outputs. Also consult the Audio MicrophoneReinforcement Output Line Mode setting.
Requires user role: ADMIN, INTEGRATOR
Default value: Off
USAGE:
xConfiguration Aud io MicrophoneReinforcement Input Microphone n Mod e: Mode
where
Mode
: Off/On
On: The microphone signal will be fed to the selected MicrophoneReinforcement
outputs, as well as to the far end.
Off: The microphone signal will be sent only to the far end. It will not be fed to the
selected MicrophoneReinforcement outputs.
xConfiguration Audio MicrophoneReinforcement Output Line [1..4] Mode
Set the microphone reinforcement mode individually on each line output. If Mode = On, the line
output will add the microphone reinforcement mix to its ordinary output signal. Also consult the
Audio MicrophoneReinforcement Input Microphone Mode setting.
Requires user role: ADMIN, INTEGRATOR
Default value: Off
USAGE:
xConfiguration Aud io MicrophoneReinforcement Output Line n M ode: Mode
where
Mode
: Off/On
On: This output will deliver far end audio, local presentation audio and the microphone
reinforcement mix.
Off: This output will deliver far end audio and local presentation audio.
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
The gain (in dB) that will be applied to the mixed microphone signal that is fed to the selected
MicrophoneReinforcement outputs.
Requires user role: ADMIN, INTEGRATOR
Default value: -54
USAGE:
xConfiguration Aud io MicrophoneReinforcement Ga in: Gain
where
Gain
: Integer (-54..15)
Use this gain to adjust the level of microphone signal that should be fed to the local
output. The value -54 means "Off", and no signal will be fed from the microphone to
the output.
xConfiguration Audio SoundsAndAlerts RingTone
Define which ringtone to use for incoming calls.
Requires user role: ADMIN, INTEGRATOR, USER
Default value: Sunrise
USAGE:
xConfiguration Aud io SoundsAndAlerts RingTo n e: RingTone
This setting applies to HDMI [2..3] for single camera systems, and to HDMI [3] for dual camera
systems.
Determine whether to play audio only when you present the HDMI input source, or to always
play audio when an audio source is connected to the HDMI input.
Requires user role: ADMIN, INTEGRATOR
Default value: On
USAGE:
xConfiguration Aud io Input HDMI n VideoAssociation MuteOnInactiveVideo:
MuteOnInactiveVideo
where
n
: Unique ID that identifies the HDMI input. Range: 2..3 for single camera systems; 3..3 for
dual camera systems
MuteOnInactiveVideo
Off: Audio is always played, locally and to far end; you do not have to present the HDMI
input source.
On: Audio is played, locally and to far end, only when you present the HDMI input
source.
: Off/On
xConfiguration Audio Input Line [1..4] Equalizer ID
Select the equalizer ID of the audio source that is connected to the line input.
Requires user role: ADMIN, INTEGRATOR
Default value: 1
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
USAGE:
xConfiguration Aud io Input Line n Eq ualizer ID: ID
where
n
: Unique ID that identifies the audio line input. Range: 1..4
xConfiguration Audio Input Line [1..4] Equalizer Mode
Define the equalizer mode for the audio source that is connected to the line input.
Requires user role: ADMIN, INTEGRATOR
Default value: Off
USAGE:
xConfiguration Aud io Input Line n Eq ualizer M o d e: Mode
where
n
: Unique ID that identifies the audio line input. Range: 1..4
Mode
: Off/On
Off: No equalizer.
On: Enable the equalizer for the audio source that is connected to the line input.
xConfiguration Audio Input Line [1..4] VideoAssociation MuteOnInactiveVideo
The audio source can be associated with a video source on the video input connector, and
you can determine whether to play or mute audio depending on whether the video source is
presented or not.
Requires user role: ADMIN, INTEGRATOR
Default value: Line [1, 2]: On Line[3, 4]: Off
USAGE:
xConfiguration Aud io Input Line n VideoAssociation MuteOnInactiveVideo:
MuteOnInactiveVideo
where
n
: Unique ID that identifies the audio line input. Range: 1..4
MuteOnInactiveVideo
Off: The audio source is not associated with a video source. The audio will be played
locally and to far end regardless of whether the video source is presented.
On: The audio source is associated with a video source. The audio will be played
(locally and to far end) when the associated video source is presented. The audio will
be muted when the video source is not presented.
: Off/On
xConfiguration Audio Input Line [1..4] VideoAssociation VideoInputSource
The audio source can be associated with a video source on the video input connector.
Requires user role: ADMIN, INTEGRATOR
Default value: Line [1, 2]: 4 Line[3, 4]: 1
USAGE:
xConfiguration Aud io Input Line n VideoAssociation VideoInputSource:
VideoInp ut So urc e
where
n
: Unique ID that identifies the audio line input. Range: 1..4
VideoInp ut So urc e
Select the video input connector to associate the audio source with.
: 1/2/3/4/5
xConfiguration Audio Input Line [1..4] Channel
Define whether the audio source on the line input is a mono signal or part of a multichannel
signal.
Requires user role: ADMIN, INTEGRATOR
Default value: Left
USAGE:
xConfiguration Aud io Input Line n C h a nnel: Channel
where
n
: Unique ID that identifies the audio line input. Range: 1..4
Channel
: Left/Mono/Right
Left: The Audio Line input signal is the left channel of a stereo signal.
Mono: The Audio Line input signal is a mono signal.
Right: The Audio Line input signal is the right channel of a stereo signal.
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
Define the level of the audio source on the line input connector.
See the Audio Level table in the Physical Interface Guide for Cisco TelePresence SX80 for a
complete over view of the values represented in dB.
Requires user role: ADMIN, INTEGRATOR
Default value: 10
USAGE:
xConfiguration Aud io Input Line n L e v el: Level
where
n
: Unique ID that identifies the audio line input. Range: 1..4
Level
: Integer (0..24)
Select a value between 0 and 24, in steps of 1 dB.
xConfiguration Audio Input Line [1..4] Mode
Define the mode for the audio input line.
Requires user role: ADMIN, INTEGRATOR
Default value: On
USAGE:
xConfiguration Aud io Input Line n M o d e: Mode
where
n
: Unique ID that identifies the audio line input. Range: 1..4
The echo canceller continuously adjusts itself to the audio characteristics of the room, and
compensates for any changes it detects in the audio environment. If the changes in the audio
conditions are significant, the echo canceller may take a second or two to re-adjust.
Requires user role: ADMIN, INTEGRATOR
Default value: On
USAGE:
xConfiguration Aud io Input Microphone n EchoControl Mode: Mode
where
n
: Unique ID that identifies the microphone input. Range: 1..8
Mode
: Off/On
Off: Turn off the echo control. Recommended if external echo cancellation or playback
equipment is used.
On: Turn on the echo control. Recommended, in general, to prevent the far end from
hearing their own audio. Once selected, echo cancellation is active at all times.
The system has built-in noise reduction, which reduces stationary background noise, for
example noise from air-conditioning systems, cooling fans etc. In addition, a high pass filter
(Humfilter) reduces very low frequency noise. Noise reduction requires that Audio Input
Microphone [n] EchoControl Mode is enabled.
Requires user role: ADMIN, INTEGRATOR
Default value: On
USAGE:
xConfiguration Aud io Input Microphone n EchoControl NoiseReduction:
NoiseReduction
where
n
: Unique ID that identifies the microphone input. Range: 1..8
NoiseReduction
Off: Turn off the noise reduction.
On: Turn on the noise reduction. Recommended in the presence of low frequency noise.
: Off/On
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
The microphone can be associated with a video source on the video input connector, and
you can determine whether to play or mute audio depending on whether the video source is
presented or not. By default, audio is not muted.
Requires user role: ADMIN, INTEGRATOR
Default value: On
USAGE:
xConfiguration Aud io Input Microphone n VideoAssociation MuteOnInactiveVideo:
MuteOnInactiveVideo
where
n
: Unique ID that identifies the microphone input. Range: 1..8
MuteOnInactiveVideo
Off: No video source is associated.
On: A video source is associated, and the audio will be muted if the associated video
source is not displayed.
: Off/On
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
Define whether the Audio Line output is a mono signal or part of a multichannel signal.
Requires user role: ADMIN, INTEGRATOR
Default value: Left
USAGE:
xConfiguration Aud io Output Line n C h an n e l: Channel
where
n
: Unique ID that identifies the audio line output. Range: 1..6
Channel
: Left/Mono/Right
Left: The Audio Line output signal is the left channel of a stereo signal.
Mono: The Audio Line output signal is a mono signal.
Right: The Audio Line output signal is the right channel of a stereo signal.
xConfiguration Audio Output Line [1..6] Delay DelayMs
To obtain lip-synchronization, you can configure each audio line output with an extra delay that
compensates for delay in other connected devices, for example TVs and external loudspeakers. The delay that you set here is either fixed or relative to the delay on the HDMI output, as
defined in the Audio Output Line [n] Delay Mode setting.
Requires user role: ADMIN, INTEGRATOR
Default value: 0
USAGE:
xConfiguration Aud io Output Line n Delay DelayMs: DelayMs
where
n
: Unique ID that identifies the audio line output. Range: 1..6
DelayMs
: Integer (0..290)
The delay in milliseconds.
xConfiguration Audio Output Line [1..6] Delay Mode
You may add extra delay to an audio line output with the Audio Output Line [n] Delay DelayMs
setting. The extra delay added is either a fixed number of milliseconds, or a number of milliseconds relative to the detected delay on the HDMI output (typically introduced by the connected
TV).
Requires user role: ADMIN, INTEGRATOR
Default value: Fixed
USAGE:
xConfiguration Aud io Output Line n Delay Mode: Mode
where
n
: Unique ID that identifies the audio line output. Range: 1..6
Mode
: Fixed/RelativeToHDMI
Fixed: Any extra delay (DelayMs) added to the output, will be a fixed number of
millisecond.
RelativeToHDMI: Any extra delay (DelayMs) added to the output, will be relative to the
detected delay on the HDMI output. The actual delay is HDMI-delay + DelayMs. The
Audio Output Connectors Line [n] DelayMs status reports the actual delay.
xConfiguration Audio Output Line [1..6] Equalizer ID
Select the equalizer ID for the audio source that is connected to the output line.
Requires user role: ADMIN, INTEGRATOR
Default value: 1
USAGE:
xConfiguration Aud io Output Line n Equalizer ID: ID
where
n
: Unique ID that identifies the audio line output. Range: 1..6
ID
: Integer (1..8)
Set the equalizer ID.
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
xConfiguration Cameras Camera [1..7] AssignedSerialNumber
The camera ID is the number n in Camera [n]. By default, the camera ID is assigned automati-
cally to a camera. If EDID information is not passed on from the camera to the codec, the
camera ID is not persistent after a reboot. This means that a camera may get a new camera ID
when the codec (video system) is restarted.
You should use the Cameras Camera AssignedSerialNumber setting to cater for configurations
where the codec does not receive EDID information from multiple cameras. This setting allows
you to manually assign a camera ID to a camera by associating the camera ID with the camera's
serial number. The setting is persistent until the codec is factory reset.
Typical situations where the codec does not receive EDID information are: when you connect
a Cisco TelePresence Precision 60 camera using 3G-SDI; when you connect a Cisco
TelePresence Precision 40 (Cisco TelePresence PrecisionHD 1080p4xS2) camera; when you
use an HDMI repeater that does not pass on EDID information.
The default value is an empty string.
Requires user role: ADMIN, INTEGRATOR
Default value: ""
USAGE:
xConfiguration Cameras Camera n AssignedSerialNumber: "AssignedSerialNum ber"
where
n
: Unique ID that identifies the camera. Range: 1..7
AssignedSerialNum ber
The camera's serial number.
: String (0, 20)
xConfiguration Cameras Camera [1..7] Backlight DefaultMode
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, INTEGRATOR
Default value: Off
USAGE:
xConfiguration Cameras Camera n Backlight Default M o d e: DefaultMode
where
n
: Unique ID that identifies the camera. Range: 1..7
DefaultMode
: Off/On
Off: Turn off the camera backlight compensation.
On: Turn on the camera backlight compensation.
xConfiguration Cameras Camera [1..7] Brightness Mode
Define the camera brightness mode.
Requires user role: ADMIN, INTEGRATOR
Default value: Auto
USAGE:
xConfiguration Cameras Camera n Brightness M o de: Mode
where
n
: Unique ID that identifies the camera. Range: 1..7
Mode
: 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 [n] Brightness DefaultLevel setting.
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
xConfiguration Cameras Camera [1..7] Brightness DefaultLevel
Define the brightness level. Requires the Cameras Camera [n] Brightness Mode to be set to
Manual.
Requires user role: ADMIN, INTEGRATOR
Default value: 20
USAGE:
xConfiguration Cameras Camera n Brightness D ef ault L e v e l: D efault Lev el
where
n
: Unique ID that identifies the camera. Range: 1..7
Defau ltLe vel
The brightness level.
: Integer (1..31)
xConfiguration Cameras Camera [n..7] Flip
This setting applies to Camera [2..7] for single camera systems, and to HDMI [3..7] for dual
camera systems.
With Flip mode (vertical flip) you can flip the image upside down. Flipping applies both to the
self-view and the video that is transmitted to the far end.
Requires user role: ADMIN, INTEGRATOR
Default value: Auto
USAGE:
xConfiguration Cameras Camera n Fli p: Flip
where
n
: Unique ID that identifies the camera. Range: 2..7 for single camera systems; 3..7 for dual
camera systems
Flip
: Auto/Off/On
Auto: If the camera detects that it is mounted upside down, the image is automatically
flipped. If the camera cannot auto-detect whether it is mounted upside down or not, the
image is not changed.
Off: Display the image on screen the normal way.
On: Display the image flipped upside down. This setting is used when a camera is
mounted upside down, but cannot automatically detect which way it is mounted.
xConfiguration Cameras Camera [n..7] Focus Mode
Define the camera focus mode.
Requires user role: ADMIN, INTEGRATOR
Default value: Auto
USAGE:
xConfiguration Cameras Camera n Focus Mode: Mode
where
n
: Unique ID that identifies the camera. Range: 2..7 for single camera systems; 3..7 for dual
camera systems
Mode
: Auto/AutoLimited/Manual
Auto: The camera will do continuous auto focusing. It will, more specifically, run auto
focus once a call is connected, after moving the camera (pan, tilt, zoom), and generally
when the camera identifies a change in the scene.
AutoLimited: In most cases this mode will operate the same way as Auto. In some cases
AutoLimited will reduce the focus hunting that may occur. Problematic scenes have
large areas with no or low contrast, for instance a painted wall with no details, or maybe
a partly empty whiteboard. There’s a slightly higher chance of background focus with
this mode, compared to Auto.
Manual: Turn the autofocus off and adjust the camera focus manually.
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
This setting enables gamma corrections, and applies only to cameras which support gamma
mode. Gamma describes the nonlinear relationship between image pixels and monitor
brightness.
Requires user role: ADMIN, INTEGRATOR
Default value: Auto
USAGE:
xConfiguration Cameras Camera n Gam ma Mode: Mode
where
n
: Unique ID that identifies the camera. Range: 1..7
Mode
: 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 [n] Gamma Level.
xConfiguration Cameras Camera [1..7] 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 Cameras Camera [n] Gamma Mode to be set to
Manual.
Requires user role: ADMIN, INTEGRATOR
Default value: 0
USAGE:
xConfiguration Cameras Camera n Gam ma Level: Level
where
n
: Unique ID that identifies the camera. Range: 1..7
Level
: Integer (0..7)
Define the gamma level.
xConfiguration Cameras Camera [n..7] Mirror
This setting applies to Camera [2..7] for single camera systems, and to HDMI [3..7] for dual
camera systems.
With Mirror mode (horizontal flip) you can mirror the image on screen. Mirroring applies both to
the self-view and the video that is transmitted to the far end.
Requires user role: ADMIN, INTEGRATOR
Default value: Auto
USAGE:
xConfiguration Cameras Camera n Mirr or: Mirror
where
n
: Unique ID that identifies the camera. Range: 2..7 for single camera systems; 3..7 for dual
camera systems
Mirror
: Auto/Off/On
Auto: If the camera detects that it is mounted upside down, the image is automatically
mirrored. If the camera cannot auto-detect whether it is mounted upside down or not,
the image is not changed.
Off: Display the image as other people see you.
On: Display the image as you see yourself in a mirror.
xConfiguration Cameras Camera [1..7] Whitebalance Mode
Define the camera white balance mode.
Requires user role: ADMIN, INTEGRATOR
Default value: Auto
USAGE:
xConfiguration Cameras Camera n White b ala nce M o d e: Mode
where
n
: Unique ID that identifies the camera. Range: 1..7
Mode
: 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 [n] Whitebalance Level setting.
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
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.
: Auto/Off/On
xConfiguration Cameras SpeakerTrack Mode
This setting applies only to systems with dual cameras.
The dual camera assembly consists of two cameras and uses an audio tracking technique that
finds and captures a close-up of the active speaker. When a change of speaker is detected, the
system can switch automatically between the two cameras to always show the best camera
view. Refer to the Cameras SpeakerTrack TrackingMode setting for different switching modes.
Requires user role: ADMIN, INTEGRATOR
Default value: Auto
USAGE:
xConfiguration Cameras SpeakerTrack M o d e: Mode
where
Mode
: Auto/Off
Auto: Speaker tracking is switched on. The system will detect people in the room and
automatically select the best camera framing. Users can switch speaker track on or off
instantly in the camera control panel on the Touch controller.
Off: Speaker tracking is switched off, and the two cameras operate as individual
cameras.
xConfiguration Cameras SpeakerTrack Closeup
This setting applies only when the Cameras SpeakerTrack Mode is set to Auto.
When a person in the room speaks the system will find the person and select the best camera
framing. This is called a closeup and may not include all the persons in the room. If you
want all the persons in the room to be in the picture at all times you can turn off the closeup
functionality.
Requires user role: ADMIN, INTEGRATOR, USER
Default value: Auto
USAGE:
xConfiguration Cameras SpeakerTrack Closeup: Closeu p
where
Closeu p
: Auto/Off
Auto: The system will zoom in on the person speaking.
Off: The system will keep all the persons in the room in the camera framing at all times.
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
This setting applies only to systems with a dual camera (speaker tracking), and when Cameras
SpeakerTrack Mode is set to Auto.
The speaker tracking algorithm can react to changes in two modes, one faster than the other.
The mode determines when the camera view will change to a new speaker.
Requires user role: ADMIN, INTEGRATOR
Default value: Auto
This setting applies only to systems with dual cameras.
The Snap to Whiteboard feature extends the speaker tracking functionality, thus you need a
camera that suppor ts speaker tracking. When a presenter is standing next to the whiteboard,
the camera will capture both the presenter and the whiteboard if the Snap to Whiteboard
feature is enabled. If the feature is disabled, only the presenter will be captured. The Snap to
Whiteboard feature is set up from the Touch controller or web interface.
Requires user role: ADMIN, INTEGRATOR, USER
Default value: Off
USAGE:
xConfiguration Cameras SpeakerTrack W hite b o ard M o d e: Mode
Define 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
Default value: Off
USAGE:
xConfiguration Conference AutoAnswer M o d e: Mode
where
Mode
: 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.
xConfiguration Conference AutoAnswer Mute
Define if the microphone shall be muted when an incoming call is automatically answered.
Requires that AutoAnswer Mode is switched on.
Requires user role: ADMIN
Default value: Off
USAGE:
xConfiguration Conference AutoAnswer M u te: Mute
where
Mute
: Off/On
Off: The incoming call will not be muted.
On: The incoming call will be muted when automatically answered.
xConfiguration Conference 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
Default value: 0
USAGE:
xConfiguration Conference AutoAnswer Delay: Delay
where
Delay
: Integer (0..50)
The auto answer delay (seconds).
xConfiguration Conference DefaultCall Protocol
Define the Default Call Protocol to be used when placing calls from the system.
Requires user role: ADMIN
Default value: Auto
USAGE:
xConfiguration Conference DefaultCall Pr o toc ol: Protocol
where
Protocol
: Auto/H320/H323/Sip/Spark
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, the auto-selection chooses H323.
H320: All calls are set up as H.320 calls (only applicable if connected to Cisco
TelePresence ISDN Link).
H323: All calls are set up as H.323 calls.
Sip: All calls are set up as SIP calls.
Spark: Reserved for Spark registered systems. Do not use.
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
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. The default value is 60 minutes.
Requires user role: ADMIN, INTEGRATOR
Default value: 60
USAGE:
xConfiguration Conference DoNotDisturb DefaultTimeout: De faultTi m e o u t
where
Defau ltTime o ut
The number of minutes (maximum 1440 minutes = 24 hours) before the Do Not Disturb
session times out automatically.
: Integer (1..1440)
xConfiguration Conference 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 Encr yption Option Key is not installed on the video system, the encryption mode is
always Off.
Requires user role: ADMIN
Default value: BestEffort
USAGE:
xConfiguration Conference Encry ption Mode: Mode
where
Mode
: 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.
xConfiguration Conference 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
Default value: On
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
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
Define 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.
Define 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.
This configuration applies when using a video system's built-in MultiSite feature (optional) to
host a multipoint video conference.
Define 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.
This configuration applies when using a video system's built-in MultiSite feature (optional) to
host a multipoint video conference.
Define 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.
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
The four GPIO pins are configured individually. The state can be retrieved by xStatus GPIO Pin
[1..4] State. The default pin state is High (+12 V). When activated as an output, a pin is set to 0
V (Low); when deactivated, it is set to +12 V (High). To activate a pin as an input, the voltage on
the pin must be pulled down to 0 V; to deactivate it, raise the voltage to +12 V.
Requires user role: ADMIN, INTEGRATOR
Default value: InputNoAction
Define the authenticatin mode for the H.323 profile.
Requires user role: ADMIN
Default value: Off
USAGE:
xConfiguration H323 Authentication Mod e: Mode
where
Mode
: Off/On
Off: The system will not try to authenticate itself to a H.323 Gatekeeper, but will still try
a normal registration.
On: If an H.323 Gatekeeper indicates that it requires authentication, the system will try
to authenticate itself to the gatekeeper. Requires the H323 Authentication LoginName
and H323 Authentication Password settings to be defined on both the codec and the
Gatekeeper.
xConfiguration H323 Authentication LoginName
The system sends the H323 Authentication Login Name and the H323 Authentication Password
to an 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 try to register.
Requires the H.323 Authentication Mode to be enabled.
Requires user role: ADMIN
Default value: ""
USAGE:
xConfiguration H323 Authentication LoginNa m e: "LoginName"
where
LoginNa me
: String (0, 50)
The authentication login name.
xConfiguration H323 Authentication Password
The system sends the H323 Authentication Login Name and the H323 Authentication Password
to an 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 try to register.
Requires the H.323 Authentication Mode to be enabled.
Defines whether to use a Gatekeeper or Direct calling when establishing H.323 calls.
Direct H.323 calls can be made also when H323 CallSetup Mode is set to Gatekeeper.
Requires user role: ADMIN
Default value: Gatekeeper
USAGE:
xConfiguration H323 CallSetup Mode: Mode
where
Mode
: Direct/Gatekeeper
Direct: You can only make an H.323 call by dialing an IP address directly.
Gatekeeper: The system uses a Gatekeeper to make an H.323 call. When choosing this
option, the H323 Gatekeeper Address must also be configured.
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
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
Default value: Min1024bit
USAGE:
xConfiguration H323 Encry ption K eySize: KeySize
where
KeySize
: Min1024bit/Max1024bit/Min2048bit
Min1024bit: The minimum size is 1024 bit.
Max1024bit: The maximum size is 1024 bit.
Min2048bit: The minimum size is 2048 bit.
xConfiguration H323 Gatekeeper Address
Define the IP address of the Gatekeeper. Requires H323 CallSetup Mode to be set to
Gatekeeper.
Requires user role: ADMIN
Default value: ""
USAGE:
xConfiguration H323 Gatekeeper A d d ress: "Address"
where
Address
: String (0, 255)
A valid IPv4 address, IPv6 address or DNS name.
xConfiguration H323 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
Default value: ""
USAGE:
xConfiguration H323 H323Alias E164: "E164"
where
E16 4
: String (0, 30)
The H.323 Alias E.164 address. Valid characters are 0-9, * and #.
xConfiguration H323 H323Alias ID
Define 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.
Requires user role: ADMIN
Default value: ""
USAGE:
xConfiguration H323 H323Alias ID: "ID"
where
ID
: String (0, 49)
The H.323 Alias ID. Example: "firstname.lastname@company.com", "My H.323 Alias ID"
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
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
Default value: Off
USAGE:
xConfiguration H323 NAT Mo d e: Mode
where
Mode
: 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 startupmenu 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.
xConfiguration H323 NAT Address
Define 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
Default value: ""
USAGE:
xConfiguration H323 NAT Ad d ress: "Address"
where
Address
: String (0, 64)
A valid IPv4 address or IPv6 address.
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
Macros allow you to write snippets of JavaScript code that can automate parts of your video
endpoint, thus creating custom behavior. Use of macros is disabled by default, but the first
time you open the Macro Editor you will be asked whether to enable use of macros on the
codec. Use this setting when you want to manually enable, or to permanently disable the use
of macros on the codec. You can disable the use of macros within the Macro Editor. But this
will not permanently disable macros from running, because ever y time the codec is reset the
macros will be re-enabled automatically.
Requires user role: ADMIN
Default value: Off
USAGE:
xConfiguration Macros Mode: Mode
where
Mode
: Off/On
Off: Permanently disable the use of macros on this video system.
On: Enable the use of macros on this video system.
xConfiguration Macros AutoStart
All the macros run in a single process on the video endpoint, called the macro runtime. It should
be running by default, but you can choose to stop and start it manually. If you restart the video
system, the runtime will automatically start again if auto start is enabled.
Requires user role: ADMIN
Default value: Off
USAGE:
xConfiguration Macros AutoStart: AutoStart
where
AutoStar t
: Off/On
Off: The macro runtime will not start automatically after a restart of the video system.
On: The macro runtime will start automatically after a restart of the video system.
Network configuration
xConfiguration Network [1] DNS Domain Name
The 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, USER
Default value: ""
USAGE:
xConfiguration Network n DNS Domain N a me: "Name"
where
n
: Index that identifies the network. Range: 1..1
Name
: String (0, 64)
The DNS domain name.
xConfiguration Network [1] DNS Server [1..3] Address
Define the network addresses for DNS servers. Up to three addresses may be specified. If the
network addresses are unknown, contact your administrator or Internet Service Provider.
Requires user role: ADMIN, USER
Default value: ""
USAGE:
xConfiguration Network n DNS Server m A d dr ess: "Address"
where
n
: Index that identifies the network. Range: 1..1
m
: Index that identifies the DNS server. Maximum three DNS servers are allowed. Range: 1..3
Address
: String (0, 64)
A valid IPv4 address or IPv6 address.
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
The system can be connected to an IEEE 802.1X LAN network, with a port-based network
access control that is used to provide authenticated network access for Ethernet networks.
Requires user role: ADMIN, USER
Default value: Off
USAGE:
xConfiguration Network n IEEE8021X Mo d e: Mode
where
n
: Index that identifies the network. Range: 1..1
Mode
: Off/On
Off: The 802.1X authentication is disabled (default).
On: The 802.1X authentication is enabled.
xConfiguration Network [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] IEEE8021X Eap Tls is enabled (On).
Requires user role: ADMIN, USER
Default value: Off
USAGE:
xConfiguration Network n IEEE8021X TlsVerify: TlsVerify
where
n
: Index that identifies the network. Range: 1..1
TlsVerify
: 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
CA-list for all TLS connections. Only servers with a valid certificate will be allowed.
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
EAP-TTLS. If set, the anonymous ID will be used for the initial (unencrypted) EAP Identity
Request.
Requires user role: ADMIN, USER
Default value: ""
USAGE:
xConfiguration Network n IEEE8021X Anony mousIde ntity: "AnonymousIdentity"
where
n
: Index that identifies the network. Range: 1..1
AnonymousIdentity
The 802.1X Anonymous ID string.
: String (0, 64)
xConfiguration Network [1] IEEE8021X Eap Md5
Define 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, USER
Default value: On
USAGE:
xConfiguration Network n IEEE8021X Eap Md5: Md5
where
n
: Index that identifies the network. Range: 1..1
Md5
: Off/On
Off: The EAP-MD5 protocol is disabled.
On: The EAP-MD5 protocol is enabled (default).
xConfiguration Network [1] IEEE8021X Eap Ttls
Define 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, USER
Default value: On
USAGE:
xConfiguration Network n IEEE8021X Eap Ttls: Ttls
where
n
: Index that identifies the network. Range: 1..1
Ttls
: Off/On
Off: The EAP-TTLS protocol is disabled.
On: The EAP-TTLS protocol is enabled (default).
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
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, USER
Default value: On
USAGE:
xConfiguration Network n IEEE8021X Eap Tls: Tls
where
n
: Index that identifies the network. Range: 1..1
Tls
: Off/On
Off: The EAP-TLS protocol is disabled.
On: The EAP-TLS protocol is enabled (default).
xConfiguration Network [1] IEEE8021X Eap Peap
Define 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, USER
Default value: On
USAGE:
xConfiguration Network n IEEE8021X Eap Peap: Peap
where
n
: Index that identifies the network. Range: 1..1
Peap
: Off/On
Off: The EAP-PEAP protocol is disabled.
On: The EAP-PEAP protocol is enabled (default).
xConfiguration Network [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, USER
Default value: Dual
USAGE:
xConfiguration Network n IPStack: IP Stac k
where
n
: Index that identifies the network. Range: 1..1
IPSt ac k
: 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.
xConfiguration Network [1] IPv4 Assignment
Define how the system will obtain its IPv4 address, subnet mask and gateway address. This
setting applies only to systems on IPv4 networks.
Requires user role: ADMIN, USER
Default value: DHCP
USAGE:
xConfiguration Network n IP v4 Assig n m e nt: A ssign m ent
where
n
: Index that identifies the network. Range: 1..1
Assignm e nt
: 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.
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
Define the static IPv4 network address for the system. Applicable only when Network IPv4
Assignment is set to Static.
Requires user role: ADMIN, USER
Default value: ""
USAGE:
xConfiguration Network n IP v4 Add r e s s: "Add ress"
where
n
: Index that identifies the network. Range: 1..1
Address
: String (0, 64)
A valid IPv4 address.
xConfiguration Network [1] IPv4 Gateway
Define the IPv4 network gateway address. Applicable only when the Network IPv4 Assignment
is set to Static.
Requires user role: ADMIN, USER
Default value: ""
USAGE:
xConfiguration Network n IP v4 Gateway: "Gateway "
where
n
: Index that identifies the network. Range: 1..1
Gate way
: String (0, 64)
A valid IPv4 address.
xConfiguration Network [1] IPv4 SubnetMask
Define the IPv4 network subnet mask. Applicable only when the Network IPv4 Assignment is
set to Static.
Requires user role: ADMIN, USER
Default value: ""
USAGE:
xConfiguration Network n IP v4 Su bnetMask: "SubnetM ask"
where
n
: Index that identifies the network. Range: 1..1
Sub netMask
: String (0, 64)
A valid IPv4 address.
xConfiguration Network [1] IPv6 Assignment
Define how the system will obtain its IPv6 address and the default gateway address. This
setting applies only to systems on IPv6 networks.
Requires user role: ADMIN, USER
Default value: Autoconf
USAGE:
xConfiguration Network n IP v6 Assign m e nt: Assignme nt
where
n
: Index that identifies the network. Range: 1..1
Assignm e nt
: 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.
DHCPv6: All IPv6 addresses, including options, will be obtained from a DHCPv6 server.
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.
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
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, USER
Default value: Diffserv
USAGE:
xConfiguration Network n QoS Mode: Mode
where
n
: Index that identifies the network. Range: 1..1
Mode
: 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 Diffser v
Signalling, Network QoS Diffserv ICMPv6 and Network QoS Diffserv NTP settings are
used to prioritize packets.
xConfiguration Network [1] QoS Diffserv Audio
This setting will only take effect if Network QoS Mode is set to Diffserv.
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 prior-
ity. 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, USER
Default value: 0
USAGE:
xConfiguration Network n QoS Diffserv Au dio: Aud io
where
n
: Index that identifies the network. Range: 1..1
Audio
: Integer (0..63)
Set the priority of the audio packets in the IP network - the higher the number, the
higher the priority. The default value is 0 (best effort).
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
This setting will only take effect if Network QoS Mode is set to Diffserv.
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, USER
Default value: 0
USAGE:
xConfiguration Network n QoS Diffserv Video: Video
where
n
: Index that identifies the network. Range: 1..1
Video
: Integer (0..63)
Set the priority of the video packets in the IP network - the higher the number, the
higher the priority. The default value is 0 (best effort).
xConfiguration Network [1] QoS Diffserv Data
This setting will only take effect if Network QoS Mode is set to Diffserv.
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 prior-
ity. 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, USER
Default value: 0
USAGE:
xConfiguration Network n QoS Diffserv Data: D ata
where
n
: Index that identifies the network. Range: 1..1
Data
: Integer (0..63)
Set the priority of the data packets in the IP network - the higher the number, the higher
the priority. The default value is 0 (best effort).
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
This setting will only take effect if Network QoS Mode is set to Diffserv.
Define which priority Signalling packets that are deemed critical (time-sensitive) for the realtime 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, USER
Default value: 0
USAGE:
xConfiguration Network n QoS Diffserv Sig n all ing: Sig na lling
where
n
: Index that identifies the network. Range: 1..1
Signalling
: Integer (0..63)
Set the priority of the signalling packets in the IP network - the higher the number, the
higher the priority. The default value is 0 (best effort).
xConfiguration Network [1] QoS Diffserv ICMPv6
This setting will only take effect if Network QoS Mode is set to Diffserv.
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, USER
Default value: 0
USAGE:
xConfiguration Network n QoS Diffserv IC M Pv6: IC M P v6
where
n
: Index that identifies the network. Range: 1..1
ICMP v6
: Integer (0..63)
Set the priority of the ICMPv6 packets in the IP network - the higher the number, the
higher the priority. The default value is 0 (best effort).
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
This setting will only take effect if Network QoS Mode is set to Diffserv.
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 prior-
ity. 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, USER
Default value: 0
USAGE:
xConfiguration Network n QoS Diffserv NTP: NTP
where
n
: Index that identifies the network. Range: 1..1
NTP
: Integer (0..63)
Set the priority of the NTP packets in the IP network - the higher the number, the higher
the priority. The default value is 0 (best effort).
xConfiguration Network [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.
xConfiguration Network [1] Speed
Define the Ethernet link speed. We recommend not to change from the default value, which
negotiates with the network to set the speed automatically. If you do not use autonegotiation, make sure that the speed you choose is supported by the closest switch in your network
infrastructure.
Requires user role: ADMIN, USER
Default value: Auto
USAGE:
xConfiguration Network n Spee d: Speed
where
n
: Index that identifies the network. Range: 1..1
Speed
: Aut o/10h alf/10f ull/100h alf/100f ull/1000 full
Auto: Autonegotiate link speed.
10half: Force link to 10 Mbps half-duplex.
10full: Force link to 10 Mbps full-duplex.
100half: Force link to 100 Mbps half-duplex.
100full: Force link to 100 Mbps full-duplex.
1000full: Force link to 1 Gbps full-duplex.
Requires user role: ADMIN, USER
Default value: ""
USAGE:
xConfiguration Network n RemoteAccess Allo w: "Allow"
where
n
: Index that identifies the network. Range: 1..1
Allow
: String (0, 255)
A valid IPv4 address or IPv6 address.
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
Define 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, USER
Default value: Auto
USAGE:
xConfiguration Network n VLAN Voic e Mode: Mode
where
n
: Index that identifies the network. Range: 1..1
Mode
: 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.
xConfiguration Network [1] VLAN Voice VlanId
Define the VLAN voice ID. This setting will only take effect if Network VLAN Voice Mode is set
to Manual.
Requires user role: ADMIN, USER
Default value: 1
USAGE:
xConfiguration Network n VLAN Voic e VlanId: VlanId
where
n
: Index that identifies the network. Range: 1..1
VlanId
: Integer (1..4094)
Set the VLAN voice ID.
NetworkServices configuration
xConfiguration 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
Default value: On
USAGE:
xConfiguration NetworkServices CDP M o de: Mode
where
Mode
: Off/On
Off: The CDP daemon is disabled.
On: The CDP daemon is enabled.
xConfiguration NetworkServices H323 Mode
Define whether the system should be able to place and receive H.323 calls or not.
Requires user role: ADMIN
Default value: Off
USAGE:
xConfiguration NetworkServices H323 Mo d e: Mode
where
Mode
: 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).
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
This is the user name part of the credentials for authentication towards the HTTP proxy.
Requires that the NetworkServices HTTP Proxy Mode is set to Manual.
Requires user role: ADMIN, USER
Default value: ""
USAGE:
xConfiguration NetworkServices HTTP Proxy LoginNa m e: "LoginName"
This is the password part of the credentials for authentication towards the HTTP proxy.
Requires that the NetworkServices HTTP Proxy Mode is set to Manual.
The HTTP Strict Transport Security header lets a web site inform the browser that it should
never load the site using HTTP and should automatically convert all attempts to access the site
using HTTP to HTTPS requests instead.
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.
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.
: Off/On
xConfiguration 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
Default value: Auto
USAGE:
xConfiguration NetworkServices NTP M ode: Mode
where
Mode
: 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 Server [n] Address setting will be used.
Manual: The system will use the NTP server that is specified in the NetworkServices
NTP Server [n] Address setting for time reference.
Off: The system will not use an NTP server. The NetworkServices NTP Ser ver [n]
Address setting will be ignored.
xConfiguration NetworkServices NTP Server [1..3] Address
The address of the NTP server that will be used when NetworkServices NTP Mode is set to
Manual, and when NetworkSer vices NTP Mode is set to Auto and no address is supplied by a
DHCP server.
Requires user role: ADMIN
Default value: 0.tandberg.pool.ntp.org
USAGE:
xConfiguration NetworkServices NTP Server n A d d ress: "Address"
where
n
: Unique ID that identifies the NTP server. Range: 1..3
Address
: String (0, 255)
A valid IPv4 address, IPv6 address or DNS name.
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
Define 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
Default value: ""
USAGE:
xConfiguration NetworkServices SNMP Host n A d d ress: "Address"
where
n
: Identifies the SNMP host. Maximum three SNMP hosts are allowed. Range: 1..3
Address
: String (0, 255)
A valid IPv4 address, IPv6 address or DNS name.
xConfiguration NetworkServices SNMP CommunityName
Define 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
Default value: ""
USAGE:
xConfiguration NetworkServices SNMP Com m unityNa m e: "CommunityName"
where
CommunityName
The SNMP community name.
: String (0, 50)
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
SSH (or Secure Shell) protocol can provide secure encrypted communication between the
codec and your local computer.
Requires user role: ADMIN
Default value: On
USAGE:
xConfiguration NetworkServices SSH M o d e: Mode
where
Mode
: Off/On
Off: The SSH protocol is disabled.
On: The SSH protocol is enabled.
xConfiguration NetworkServices Telnet Mode
Telnet is a network protocol used on the Internet or Local Area Network (LAN) connections.
Requires user role: ADMIN
Default value: Off
USAGE:
xConfiguration NetworkServices Telnet M o d e: Mode
where
Mode
: Off/On
Off: The Telnet protocol is disabled. This is the factory setting.
On: The Telnet protocol is enabled.
xConfiguration NetworkServices UPnP Mode
Fully disable UPnP (Universal Plug and Play), or enable UPnP for a short time period after the
video system has been switched on or restarted.
The default operation is that UPnP is enabled when you switch on or restart the video
system. Then UPnP is automatically disabled after the timeout period that is defined in the
NetworkServices UPnP Timeout setting. Use the video system’s web interface to set the
timeout.
When UPnP is enabled, the video system advertises its presence on the network. The advertisement permits a Touch controller to discover video systems automatically, and you do not
need to manually enter the video system's IP address in order to pair the Touch controller.
Requires user role: ADMIN
Default value: On
USAGE:
xConfiguration NetworkServices UPnP M o d e: Mode
where
Mode
: <Off/On>
Off: UPnP is disabled. The video system does not advertise its presence, and you have
to enter the video system's IP address manually in order to pair a Touch controller to the
video system.
On: UPnP is enabled. The video system advertises its presence until the timeout period
expires.
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
Choose which information the user should see when logging on to the codec through Telnet/
SSH.
Requires user role: ADMIN
Default value: On
USAGE:
xConfiguration NetworkServices Welc o m eText: WelcomeText
where
WelcomeText
Off: The welcome text is: Login successful
On: The welcome text is: Welcome to <system name>; Software version; Software
release date; Login successful.
: Off/On
Peripherals configuration
xConfiguration Peripherals Profile Cameras
Define the number of cameras 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
cameras does not match this setting, the diagnostics service will report it as an inconsistency.
Requires user role: ADMIN, INTEGRATOR
Default value: Minimum1
USAGE:
xConfiguration Peripherals Profile Ca m era s: Cameras
where
Cameras
: N o t S et/Min i m u m1/0/1/ 2/3/4 /5/ 6/7
NotSet: No camera check is performed.
Minimum1: At least one camera should be connected to the video system.
0-7: Select the number of cameras that are expected to be connected to the video
system.
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
Minimum1: At least one Cisco Touch controller should be connected to the video
system.
0-5: Select the number of Touch controllers that are expected to be connected to the
video system. Note that only one Cisco Touch controller is officially supported.
: N o t S et/Min i m u m1/0/1/ 2/3/4 /5
Phonebook configuration
xConfiguration Phonebook Server [1] ID
Define a name for the external phone book.
Requires user role: ADMIN
Default value: ""
USAGE:
xConfiguration Phonebook Server n ID: "ID"
where
n
: Unique ID that identifies the phonebook server. Range: 1..1
ID
: String (0, 64)
The name for the external phone book.
xConfiguration Phonebook Server [1] Type
Select the phonebook server type.
Requires user role: ADMIN
Default value: Off
USAGE:
xConfiguration Phonebook Server n Ty p e: Type
where
n
: Unique ID that identifies the phonebook server. Range: 1..1
Type
: Off/CUCM/Spark/TMS/VCS
Off: Do not use a phonebook.
CUCM: The phonebook is located on the Cisco Unified Communications Manager.
Spark: The phonebook is located on Spark.
TMS: The phonebook is located on the Cisco TelePresence Management Suite server.
VCS: The phonebook is located on the Cisco TelePresence Video Communication
Server.
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
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 simultane-
ously. 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, USER
Default value: Auto
USAGE:
xConfiguration Provisioning M o d e: Mode
where
Mode
: Off/Auto/CUCM/Edge/Spark/TMS/VCS
Off: The video system is not configured by a provisioning system.
Auto: The provisioning server is automatically selected as set up in the DHCP server.
CUCM: Push configurations to the video system from CUCM (Cisco Unified
Communications Manager).
Edge: Push configurations to the video system from CUCM (Cisco Unified
Communications Manager). The system connects to CUCM via the Collaboration Edge
infrastructure. In order to register over Edge the encryption option key must be installed
on the video system.
Spark: Push configurations to the video system from Spark.
TMS: Push configurations to the video system from TMS (Cisco TelePresence
Management System).
VCS: Push configurations to the video system from VCS (Cisco TelePresence Video
Communication Server).
xConfiguration Provisioning LoginName
This is the username 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.
Requires user role: ADMIN, USER
Default value: ""
USAGE:
xConfiguration Provisioning LoginNa m e: "LoginName"
where
LoginNa me
: String (0, 80)
A valid username.
xConfiguration 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.
Requires user role: ADMIN, USER
Default value: ""
USAGE:
xConfiguration Provisioning Password: "Password"
where
Password
: String (0, 64)
A valid password.
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
Only applicable when the endpoint is provisioned by Cisco Unified Communication Manager
(CUCM) and an alternate CUCM is available for redundancy. Define 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.
Define whether to use the HTTP (unsecure communication) or HTTPS (secure communication)
protocol when sending requests to the external manager / provisioning system.
The selected protocol must be enabled in the NetworkServices HTTP Mode setting.
Requires user role: ADMIN, USER
Default value: HTTP
USAGE:
xConfiguration Provisioning ExternalManager Prot o c o l: Protocol
where
Protocol
: HTTPS/HTTP
HTTPS: Send requests via HT TPS.
HTTP: Send requests via HTTP.
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
Define the SIP domain for the VCS provisioning server.
Requires user role: ADMIN, USER
Default value: ""
USAGE:
xConfiguration Provisioning ExternalManager Do m a i n: "Domain"
where
Domain
: String (0, 64)
A valid domain name.
Proximity configuration
xConfiguration Proximity Mode
Determine whether the video system will emit ultrasound pairing messages or not.
When the video system emits ultrasound, Proximity clients can detect that they are close to the
video system. In order to use a client, at least one of the Proximity services must be enabled
(refer to the Proximity Services settings). In general, Cisco recommends enabling all the
Proximity services.
Requires user role: ADMIN, USER
Default value: On
USAGE:
xConfiguration Proximity Mode: Mode
where
Mode
: Off/On
Off: The video system does not emit ultrasound, and Proximity services cannot be used.
On: The video system emits ultrasound, and Proximity clients can detect that they are
close to the video system. Enabled Proximity services can be used.
xConfiguration Proximity Services CallControl
Enable or disable basic call control features on Proximity clients. When this setting is enabled,
you are able to control a call using a Proximity client (for example dial, mute, adjust volume and
hang up). This service is supported by mobile devices (iOS and Android). Proximity Mode must
be On for this setting to take any effect.
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
Requires user role: ADMIN, USER
Default value: Disabled
USAGE:
xConfiguration Proximity Services CallControl: Ca llCo nt rol
where
Ca llCo nt rol
: Enabled/Disabled
Enabled: Call control from a Proximity client is enabled.
Disabled: Call control from a Proximity client is disabled.
The video system has the capability to find whether or not people are present in the room, and
report the result in the RoomAnalytics PeoplePresence status. This feature is based on ultrasound. It takes a minimum of 2 minutes to detect whether people are present or not in the room,
and it may take up to 2 minutes for the status to change after the room becomes vacant.
Requires user role: ADMIN, INTEGRATOR, USER
Default value: Off
USAGE:
xConfiguration Roo m A n aly t ics PeoplePresenceDetector: PeoplePresenceDetector
where
PeoplePresenceDetector
Off: The video system's status does not show whether or not there are people present
in the room.
On: The video system's status shows whether or not there are people present in the
room.
: Off/On
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
ICE (Interactive Connectivity Establishment, RFC 5245) is a NAT traversal solution that the video
systems can use to discover the optimized media path. Thus the shortest route for audio and
video is always secured between the video systems.
Requires user role: ADMIN
Default value: Auto
USAGE:
xConfiguration SIP Ic e Mode: Mode
where
Mode
: Auto/Off/On
Auto: ICE is enabled if a TURN server is provided, otherwise ICE is disabled.
Off: ICE is disabled.
On: ICE is enabled.
xConfiguration SIP Ice DefaultCandidate
The ICE protocol needs some time to reach a conclusion about which media route to use (up to
the first 5 seconds of a call). During this period media for the video system will be sent to the
Default Candidate as defined in this setting.
Requires user role: ADMIN
Default value: Host
USAGE:
xConfiguration SIP Ic e DefaultCandidate: DefaultCandidate
where
DefaultCandidate
Host: Send media to the video system's private IP address.
Rflx: Send media to the video system's public IP address, as seen by the TURN server.
Relay: Send media to the IP address and port allocated on the TURN server.
: Host/Rflx/Relay
xConfiguration 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).
Requires user role: ADMIN
Default value: On
USAGE:
xConfiguration SIP ListenPort: ListenPort
where
ListenPort
: 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.
xConfiguration SIP Proxy [1..4] Address
The Proxy Address is the manually configured address for the outbound proxy. It is possible to
use a fully qualified domain name, or an IP address. The default port is 5060 for TCP and UDP
but another one can be provided.
Requires user role: ADMIN
Default value: ""
USAGE:
xConfiguration SIP Proxy n Ad d ress: "Address"
where
n
: Index that identifies the proxy (maximum 4 proxys can be defined). Range: 1..4
Address
: String (0, 255)
A valid IPv4 address, IPv6 address or DNS name.
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
Define the address of the TURN (Traversal Using Relay NAT) server. 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
Default value: ""
USAGE:
xConfiguration SIP Turn Server: "Server"
where
Server
: String (0, 255)
The preferred format is DNS SRV record (e.g. _turn._udp.<domain>), or it can be a valid
IPv4 or IPv6 address.
xConfiguration SIP Turn UserName
Define the user name needed for accessing the TURN server.
Requires user role: ADMIN
Default value: ""
USAGE:
xConfiguration SIP Turn UserName: "UserName"
where
UserName
: String (0, 128)
A valid user name.
xConfiguration SIP 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
Default value: ""
USAGE:
xConfiguration SIP U RI: "URI"
where
URI
: String (0, 255)
An address (URI) that is compliant with the SIP URI syntax.
xConfiguration SIP Turn Password
Define the password needed for accessing the TURN server.
Requires user role: ADMIN
Default value: ""
USAGE:
xConfiguration SIP Turn Password: "Password"
where
Password
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
On: When people walk into the room the system will automatically wake up from
standby.
: Off/On
xConfiguration Standby PowerSave
You can reduce the video system's power consumption during out-of-office hours with this
setting. The Power Save mode is an extension to the regular standby mode.
When the video system enters power save mode, power is cut to some of the video system's
modules, for example the integrated cameras. The codec and Touch controller behaves like in
regular standby. The video system wakes up from power save mode when you tap the touch
panel.
Waking up the video system from power save mode takes longer than waking it up from regular
standby, because the cameras must boot. You can make calls right away, but there is no outgoing video until the cameras has completed their boot process.
Requires user role: ADMIN
Default value: Never
USAGE:
xConfiguration Standby PowerSave: PowerSave
where
PowerSave
: Never/OutsideOfficeHours
Never: The video system will never go into power save mode; only to regular standby.
OutsideOfficeHours: The video system will go into power save mode during out-of-
office hours. You must provide the office hours with the following settings: Time
WorkWeek FirstDayOfWeek, Time WorkWeek LastDayOfWeek, Time WorkDay Start,
and Time WorkDay End.
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
The Time WorkWeek FirstDayOfWeek, Time WorkWeek LastDayOfWeek, Time WorkDay Start,
and Time WorkDay End settings are available so that you can specify when the regular working
hours are, and thereby also find the out-of-office hours.
Knowing the out-of-office hours is required if you want to use the power save mode, which is
set up using the Standby PowerSave setting.
Requires user role: ADMIN, USER
Default value: "07:00"
USAGE:
xConfiguration Tim e WorkDay Start: "Start"
where
Start
: String (5, 5)
The working day start time, using the 24-hour clock. Example: "07:00"
xConfiguration Time WorkDay End
The Time WorkWeek FirstDayOfWeek, Time WorkWeek LastDayOfWeek, Time WorkDay Start,
and Time WorkDay End settings are available so that you can specify when the regular working
hours are, and thereby also find the out-of-office hours.
Knowing the out-of-office hours is required if you want to use the power save mode, which is
set up using the Standby PowerSave setting.
Requires user role: ADMIN, USER
Default value: "18:00"
USAGE:
xConfiguration Tim e WorkDay End: "End"
where
End
: String (5, 5)
The working day end time, using the 24-hour clock. Example: "16:00"
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
Auto: Show the address which another system should dial to reach this video system.
The address depends on the default call protocol and system registration.
None: Do not show any contact information.
IPv4: Show the system's IPv4 address.
IPv6: Show the system's IPv6 address.
H323Id: Show the system's H.323 ID (refer to the H323 H323Alias ID setting).
H320Number: Show the system's H.320 number as contact information (only applicable
if connected to Cisco TelePresence ISDN Link).
E164Alias: Show the system's H.323 E164 Alias as contact information (refer to the
H323 H323Alias E164 setting).
SipUri: Show the system's SIP URI (refer to the SIP URI setting).
SystemName: Show the system's name (refer to the SystemUnit Name setting).
DisplayName: Show the system's display name (refer to the SIP DisplayName setting).
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
A custom message can be displayed in the middle of the main screen when the system is in
the half wake state. This will replace the default message "Tap the touch panel to get started"
together with an illustration of a Touch panel. You can also choose not to have a message.
Define on which monitor the on-screen information and indicators (OSD) should be displayed.
Requires user role: ADMIN, INTEGRATOR
Default value: 1
USAGE:
xConfiguration UserInterface OSD Output: Output
where
Output
: Auto/1/2/3
Auto: The system sends the on-screen information and indicators to the system's
integrated display. If the system has two integrated displays, the left display is used.
Range 1-3: The system sends the on-screen information and indicators to the specified output. Choose n to send the on-screen information and indicators to the system's
Output Connector n.
The Settings panel in the user interface (Touch 10 or on-screen) can be protected by the
video system’s admin password. If this password is blank, anyone can access the settings in
the Settings menu, and for example factory reset the system. If authentication is enabled, all
settings that require authentication have a padlock icon. You will be prompted to enter the
administrator’s user name and passphrase when you select the setting. Some settings do not
require authentication, they do not have a padlock icon.
Requires user role: ADMIN
Default value: Unlocked
USAGE:
xConfiguration UserInterface OSD SettingsMenu M o d e: Mode
where
Mode
: Locked/Unlocked
Locked: Authentication with administrator's username and passphrase is required.
Unlocked: No authentication is required.
UserManagement configuration
xConfiguration UserManagement LDAP Mode
The video system supports the use of an LDAP (Lightweight Directory Access Protocol) server
as a central place to store and validate user names and passwords. Use this setting to configure whether or not to use LDAP authentication. Our implementation is tested for the Microsoft
Active Directory (AD) service.
Requires user role: ADMIN
Default value: Off
USAGE:
xConfiguration UserManagement LDAP M o d e: Mode
where
Mode
: Off/On
Off: LDAP authentication is not allowed.
On: For client cer tificate verification to work when LDAP authentication is enabled, the
codec requires a CA (Certificate Authority) certificate, and the user must have a Client
Certificate that matches their user distinguishing name (DN) in the active directory (AD).
xConfiguration UserManagement LDAP Server Address
Set the IP address or hostname of the LDAP server.
Requires user role: ADMIN
Default value: ""
USAGE:
xConfiguration UserManagement LDAP Server Add r e s s: "Add ress"
where
Address
: String (0, 255)
A valid IPv4 address, IPv6 address or hostname.
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
Set the port to connect to the LDAP server on. If set to 0, use the default for the selected
protocol (see the UserManagement LDAP Encryption setting).
Requires user role: ADMIN
Default value: 0
USAGE:
xConfiguration UserManagement LDAP Server Port: Port
where
Port
: Integer (0..65535)
The LDAP server por t number.
xConfiguration UserManagement LDAP Encryption
Define how to secure the communication between the video system and the LDAP server. You
can override the port number by using the UserManagement LDAP Server Port setting.
Requires user role: ADMIN
Default value: LDAPS
USAGE:
xConfiguration UserManagement LDAP Encr y pt ion: Encr y ption
where
Enc ryption
: LDAPS/None/STARTTLS
LDAPS: Connect to the LDAP server on port 636 over TLS (Transport Layer Security).
None: Connect to LDAP server on port 389 with no encryption.
STARTTLS: Connect to LDAP ser ver on port 389, then send STARTTLS to enable TLS
encryption.
When the video system connects to an LDAP server, the server will identify itself to the video
system by presenting its certificate. Use this setting to determine whether or not the video
system will verify the server certificate.
Off: The video system will not verify the LDAP server’s certificate.
On: The video system must verify that the LDAP server’s certificate is signed by a
trusted Certificate Authority (CA). The CA must be on the list of trusted CAs that are
uploaded to the system in advance. Use the video system’s web interface to manage
the list of trusted CAs (see more details in the administrator guide).
: Off/On
D15335.08 Cisco TelePresence MX700 and MX800 API Reference Guide CE9.2, NOVEMBER 2017.
The LDAP filter is used to determine which users should be granted administrator privileges. If
set, this setting takes precedence over the UserManagement LDAP Admin Group setting.
Requires user role: ADMIN
Default value: ""
USAGE:
xConfiguration UserManagement LDAP Admin Filt er: "Filte r "
where
Filte r
: String (0, 1024)
Refer to the LDAP specification for the syntax of this string. Example: "(CN=adminuser)"
xConfiguration UserManagement LDAP Admin Group
Members of this AD (Active Directory) group will be given administrator access. This
setting is a shorthand for saying (memberOf:1.2.840.113556.1.4.1941:=<group name>). If
UserManagement LDAP Admin Filter is set, this setting is ignored.