xConfiguration

Cisco TelePresence System Codec C90 API xConfiguration TC5.0

Description of the xConfiguration commands for Cisco TelePresence Codec C90 with software version TC5.0

Revision: D1464707

The xConfiguration commands defines the system settings which are persistent across boots. The examples shows either the default value or an example of a value. The commands are case-insensitive.

  • Writing xconfiguration ? on the command line will list all the top level configurations.
  • Writing xconfiguration ?? will list all configurations and their value spaces.
  • Writing xconfiguration will list all configurations and their current values.
  • To only list out parts of the configuration, write xconfiguration followed by one or more parts of the configuration paths.

Value space: The valuespace of each command is explained in the Valuespace field.

String: The string syntax is <S: 0, 255>, which means that the length of this string can be from 0 to 255 characters. String parameters must be enclosed in quotation marks when you issue a command.

Integer: The integer syntax is <0..100>, which means that this value can go from 0 to 100.

Troubleshooting: Check that the spelling and syntax is right. Check also that the value space is valid, that all the required parameters are included, and that the command is valid for your product.

User roles: The user accounts on the system can have three different user roles which possess different system rights.

  • ADMIN: A user account with ADMIN rights can create new users and change all settings, except the security audit configurations. The ADMIN user can upload all certificates, except the audit certificates.
  • USER: A user account with USER rights can make calls and search the phonebook.
  • AUDIT: A user account with AUDIT rights can change the security audit settings and upload audit certificates.

The system comes with a default user account. The user name is admin with no password set. This user has USER, ADMIN and AUDIT rights.

NOTE: It is very important that at least one user has ADMIN rights at all times.


Read more about the Application Programmer Interface (API) in the API Guide for the codec. All specifications are subject to change without prior notice. We recommend you visit our web site regularly for updated versions of the user documentation. Go to: http://www.cisco.com/go/telepresence/docs and navigate to TelePresence Solutions Platform > TelePresence Integrator Products and select the C Series.

All contents are Copyright 2010 Cisco Systems, Inc. All rights reserved.

The xConfiguration Audio commands

xConfiguration Audio Input HDMI [3, 4] Mode

Determine if the audio channels on the HDMI input shall be enabled. The HDMI input 3 and 4 have two audio channels.

Requires user role: ADMIN

Value space:

<On/Off>

On: Enable the audio channels on the HDMI input.
Off: Disable the audio channels on the HDMI input.

Example:

xConfiguration Audio Input HDMI 3 Mode: On

xConfiguration Audio Input HDMI [3, 4] Level

Define the audio level of the HDMI input connector, in steps of 1 dB.

See the Audio Level tables in the Physical Interfaces Guide for the codec for a complete overview of the menu values represented in dB.

Requires user role: ADMIN

Value space:

<-24..0>

Range: Select a value from -24 to 0 dB.

Example:

xConfiguration Audio Input HDMI 3 Level: 0

xConfiguration Audio Input HDMI [3..4] VideoAssociation MuteOnInactiveVideo

Enable association of a video source to an HDMI audio input.

Requires user role: ADMIN

Value space:

<On/Off>

On: A video source is associated, and the audio will be muted if the associated video source is not displayed.
Off: No video source is associated.

Example:

xConfiguration Audio Input HDMI 3 VideoAssociation MuteOnInactiveVideo: Off

xConfiguration Audio Input HDMI [3..4] VideoAssociation VideoInputSource

Select the associated video input source.

Requires user role: ADMIN

Value space:

<1/2/3/4/5>

Range: Select one of the video input sources.

Example:

xConfiguration Audio Input HDMI 3 VideoAssociation VideoInputSource: 1

xConfiguration Audio Input Line [1..4] Equalizer ID

Select the audio input line equalizer ID.

Requires user role: ADMIN

Value space:

<1..8>

Range: Select EqualizerID 1 to 8.

Example:

xConfiguration Audio Input Line 1 Equalizer ID: 1

xConfiguration Audio Input Line [1..4] Equalizer Mode

Set the audio input line equalizer mode.

Requires user role: ADMIN

Value space:

<On/Off>

On: Enable the equalizer for the audio input line.
Off: No equalizer.

Example:

xConfiguration Audio Input Line 1 Equalizer Mode: Off

xConfiguration Audio Input Line [1..4] VideoAssociation MuteOnInactiveVideo

Enable association of a video source to a Line audio input.

Requires user role: ADMIN

Value space:

<On/Off>

On: A video source is associated, and the audio will be muted if the associated video source is not displayed.
Off: No video source is associated.

Example:

xConfiguration Audio Input Line 1 VideoAssociation MuteOnInactiveVideo: Off

xConfiguration Audio Input Line [1..4] VideoAssociation VideoInputSource

Select the associated video input source.

Requires user role: ADMIN

Value space:

<1/2/3/4/5>

Range: Select one of the video input sources.

Example:

xConfiguration Audio Input Line 1 VideoAssociation VideoInputSource: 1

xConfiguration Audio Input Line [1..4] Channel

Define whether the Audio Line input is a mono signal or part of a multichannel signal.

Requires user role: ADMIN

Value space:

<Left/Right/Mono>

Left: The Audio Line input signal is the left channel of a stereo signal.
Right: The Audio Line input signal is the right channel of a stereo signal.
Mono: The Audio Line input signal is a mono signal.

Example:

xConfiguration Audio Input 1 Channel: Left

xConfiguration Audio Input Line [1..4] Level

Define the audio level of the Line input connector, in steps of 1 dB.

See the Audio Level tables in the Physical Interfaces Guide for the codec for a complete overview of the menu values represented in dB.

Requires user role: ADMIN

Value space:

<0..24>

Range: Select a value from 0 to 24 dB.

Example:

xConfiguration Audio Input Line 1 Level: 10

xConfiguration Audio Input Line [1..4] LoopSuppression

The loop suppression functionality detects whether a delayed signal loop is present from an audio Line output to an audio Line input on the codec. If a loop is detected the unwanted feedback is suppressed.

NOTE: Only loops between line output 3 and line input 3, and between line output 4 and line input 4 are suppressible.

Requires user role: ADMIN

Value space:

<On/Off>

On: Activate Loop Suppression.
Off: Deactivate Loop Suppression.

Example:

xConfiguration Audio Input Line 3 LoopSuppression: On

xConfiguration Audio Input Line [1..4] Mode

Set the audio input line mode.

Requires user role: ADMIN

Value space:

<On/Off>

On: Enable the Audio Line input.
Off: Disable the Audio Line input.

Example:

xConfiguration Audio Input Line 1 Mode: On

xConfiguration Audio Input Microphone [1..8] EchoControl Mode

The echo canceller continuously adjusts itself to the audio characteristics of the room and compensate for any changes it detects in the audio environment. If the changes in the audio conditions are very significant the echo canceller may take a second or two to re-adjust.

Requires user role: ADMIN

Value space:

<On/Off>

On: Echo Control is normally set to On to prevent the far end from hearing their own audio. Once selected, echo cancellation is active at all times.
Off: Echo Control should be switched Off if external echo cancellation or playback equipment is used.

Example:

xConfiguration Audio Input Microphone 1 EchoControl Mode: On

xConfiguration Audio Input Microphone [1..8] EchoControl NoiseReduction

The system has a built-in noise reduction which reduces constant background noise (e.g. noise from air-conditioning systems, cooling fans etc.). In addition, a high pass filter (Humfilter) reduces very low frequency noise. NOTE: Requires the Echo Control Mode to be enabled for the microphone.

Requires user role: ADMIN

Value space:

<On/Off>

On: The Noise Reduction should be enabled in the presence of low frequency noise.
Off: Turn off the Noise Reduction.

Example:

xConfiguration Audio Input Microphone 1 EchoControl NoiseReduction: On

xConfiguration Audio Input Microphone [1..8] EchoControl Dereverberation

The system has built-in signal processing to reduce the effect of room reverberation. NOTE: Requires the Echo Control Mode to be enabled for the microphone.

Requires user role: ADMIN

Value space:

<On/Off>

On: Turn on the dereverberation.
Off: Turn off the dereverberation.

Example:

xConfiguration Audio Input Microphone 1 EchoControl Dereverberation: On

xConfiguration Audio Input Microphone [1..8] Equalizer ID

Select the audio input microphone equalizer ID.

Requires user role: ADMIN

Value space:

<1..17>

Range: Select Equalizer ID 1 to 17.

Example:

xConfiguration Audio Input Microphone 1 Equalizer ID: 1

xConfiguration Audio Input Microphone [1..8] Equalizer Mode

Set the audio input microphone equalizer mode.

Requires user role: ADMIN

Value space:

<On/Off>

On: Enable the equalizer for the audio input microphone.
Off: No equalizer.

Example:

xConfiguration Audio Input Microphone 1 Equalizer Mode: Off

xConfiguration Audio Input Microphone [1..8] VideoAssociation MuteOnInactiveVideo

Enable association of a video source to a microphone audio input.

Requires user role: ADMIN

Value space:

<On/Off>

On: A video source is associated, and the audio will be muted if the associated video source is not displayed.
Off: No video source is associated.

Example:

xConfiguration Audio Input Microphone 1 VideoAssociation MuteOnInactiveVideo: On

xConfiguration Audio Input Microphone [1..8] VideoAssociation VideoInputSource

Select the associated video input source.

Requires user role: ADMIN

Value space:

<1/2/3/4/5>

Range: Select one of the video input sources.

Example:

xConfiguration Audio Input Microphone 1 VideoAssociation VideoInputSource: 1

xConfiguration Audio Input Microphone [1..8] Level

Define the audio level of the Microphone input connector, in steps of 1dB.

See the Audio Level tables in the Physical Interfaces Guide for the codec for a complete overview of the menu values represented in dB.

Requires user role: ADMIN

Value space:

<0..24>

Range: Select a value from 0 to 24 dB.

Example:

xConfiguration Audio Input Microphone 1 Level: 15

xConfiguration Audio Input Microphone [1..8] Mode

Set the audio input microphone mode.

Requires user role: ADMIN

Value space:

<On/Off>

On: Enable the microphone connector.
Off: Disable the microphone connector.

Example:

xConfiguration Audio Input Microphone 1 Mode: On

xConfiguration Audio Input Microphone [1..8] Type

The microphone connectors are intended for electret type microphones. The microphone connector can be set to line or microphone mode.

Requires user role: ADMIN

Value space:

<Microphone/Line>

Microphone: Select Microphone when you have 48 V Phantom voltage and the pre-amplification is On.
Line: Select Line when you have a standard balanced line input. The phantom voltage and pre-amplification is Off.

Example:

xConfiguration Audio Input Microphone 1 Type: Line

xConfiguration Audio Output HDMI [1, 3] Level

Define the output level of the HDMI output connector, in steps of 1 dB.

See the Audio Level tables in the Physical Interfaces Guide for the codec for a complete overview of the menu values represented in dB.

Requires user role: ADMIN

Value space:

<-24..0>

Range: Select a value from -24 to 0dB.

Example:

xConfiguration Audio Output HDMI 1 Level: 0

xConfiguration Audio Output HDMI [1, 3] Mode

Determine if the audio channel on the HDMI output connector shall be enabled.

Requires user role: ADMIN

Value space:

<On/Off>

On: Enable the audio channel on the HDMI output.
Off: Disable the audio channel on the HDMI output.

Example:

xConfiguration Audio Output HDMI 1 Mode: On

xConfiguration Audio Output Line [1..6] Channel

Define whether the Audio Line output is a mono signal or part of a multichannel signal.

Requires user role: ADMIN

Value space:

<Left/Right/Mono>

Left: The Audio Line output signal is the left channel of a stereo signal.
Right: The Audio Line output signal is the right channel of a stereo signal.
Mono: The Audio Line output signal is a mono signal.

Example:

xConfiguration Audio Output Line 1 Channel: left

xConfiguration Audio Output Line [1..6] Equalizer ID

Select the audio output line equalizer ID.

Requires user role: ADMIN

Value space:

<1..8>

Range: Select EqualizerID 1 to 8.

Example:

xConfiguration Audio Output Line 1 Equalizer ID: 1

xConfiguration Audio Output Line [1..6] Equalizer Mode

Set the audio output line equalizer mode.

Requires user role: ADMIN

Value space:

<On/Off>

On: Enable the equalizer for the audio output line.
Off: No equalizer.

Example:

xConfiguration Audio Output Line 1 Equalizer Mode: Off

xConfiguration Audio Output Line [1..6] Level

Define the output level of the Audio Output Line connector, in steps of 1 dB.

See the Audio Level tables in the Physical Interfaces Guide for the codec for a complete overview of the menu values represented in dB.

Requires user role: ADMIN

Value space:

<-24..0>

Range: Select a value from -24 to 0 dB.

Example:

xConfiguration Audio Output Line 1 Level: -10

xConfiguration Audio Output Line [1..6] Mode

Set the audio output line mode.

Requires user role: ADMIN

Value space:

<On/Off>

On: Enable the Audio Line output.
Off: Disable the Audio Line output.

Example:

xConfiguration Audio Output Line 1 Mode: On

xConfiguration Audio Output Line [1, 3] Type

Determine if the Audio Line output will be analog or digital type output. The digital output on the Cisco TelePresence Profile systems are identified as DNAM (Digital Natural Audio Module).

Requires user role: ADMIN

Value space:

<Auto/SPDIF>

Auto: If a Digital NAM is detected then SPDIF mode will be selected, otherwise analog mode will be selected.
SPDIF: Set to SPDIF when you want the line output to be in digital mode.

Example:

xConfiguration Audio Output Line 1 Type: Auto

xConfiguration Audio Output Line [2, 4, 5, 6] Type

Line output 2, 4, 5, 6 are dedicated analog outputs, hence type can be set to analog only.

Requires user role: ADMIN

Value space:

<Analog>

Analog: Can be set to analog only.

Example:

xConfiguration Audio Output Line 2 Type: Analog

xConfiguration Audio Microphones Mute Enabled

Determine whether audio-mute is allowed or not. The default value is True.

Requires user role: ADMIN

Value space:

<True/InCallOnly>

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.

Example:

xConfiguration Audio Microphones Mute Enabled: True

xConfiguration Audio SoundsAndAlerts KeyTones Mode

The system can produce a sound every time a key on the remote control is pressed.

Requires user role: USER

Value space:

<On/Off>

On: There will be a sound indicator when pressing keys on the remote control.
Off: The remote control Key Tones is switched off.

Example:

xConfiguration Audio SoundsAndAlerts KeyTones Mode: Off

xConfiguration Audio SoundsAndAlerts RingTone

Select the ring tone for incoming calls.

Requires user role: USER

Value space:

<Marbles/IceCrystals/Polaris/Alert/Discreet/Fantasy/Jazz/Nordic/Echo/Rhythmic>

Range: Select a tone from the list of ring tones.

Example:

xConfiguration Audio SoundsAndAlerts RingTone: Jazz

xConfiguration Audio SoundsAndAlerts RingVolume

Sets the ring tone volume for an incoming call.

Requires user role: USER

Value space:

<0..100>

Range: The value goes in steps of 5 from 0 to 100 (from -34.5 dB to 15 dB). Volume 0 = Off.

Example:

xConfiguration Audio SoundsAndAlerts RingVolume: 50

xConfiguration Audio Volume

Set the volume on the loudspeaker.

Requires user role: USER

Value space:

<0..100>

Range: The value goes in steps of 5 from 0 to 100 (from -34.5 dB to 15 dB). Value 0 = Off.

Example:

xConfiguration Audio Volume: 70

The xConfiguration Cameras commands

xConfiguration Cameras PowerLine Frequency

Applies to cameras supporting PowerLine frequency anti-flickering, i.e PrecisionHD 1080p cameras.

Requires user role: ADMIN

Value space:

<Auto/50Hz/60Hz>

Auto: Set to Auto to enable power frequency auto detection in the camera.
50Hz: Set to 50 Hz.
60Hz: Set to 60 Hz.

Example:

xConfiguration Cameras PowerLine Frequency: Auto

xConfiguration Cameras Camera [1..7] Backlight

The backlight functionality compensates for light shining directly at the camera (usually the sun entering the window) to avoid a too dark image from the room.

Requires user role: ADMIN

Value space:

<On/Off>

On: Turn on the camera backlight.
Off: Turn off the camera backlight.

Example:

xConfiguration Cameras Camera 1 Backlight: Off

xConfiguration Cameras Camera [1..7] Brightness Mode

Set the camera brightness mode.

Requires user role: ADMIN

Value space:

<Auto/Manual>

Auto: The camera brightness is automatically set by the system.
Manual: Enable manual control of the camera brightness, e.g. the level of the brightness level setting will be used for the camera.

Example:

xConfiguration Cameras Camera 1 Brightness Mode: Auto

xConfiguration Cameras Camera [1..7] Brightness Level

Set the brightness level. NOTE: Requires the Camera Brightness Mode to be set to Manual.

Requires user role: ADMIN

Value space:

<1..31>

Range: Select a value from 1 to 31.

Example:

xConfiguration Cameras Camera 1 Brightness Level: 1

xConfiguration Cameras Camera [1..7] Flip

With Flip mode (vertical flip) you can flip the image upside down.

Requires user role: ADMIN

Value space:

<Auto/On/Off>

Auto: When the camera is placed upside down the image is automatically flipped upside down. Use this setting with cameras that can be mounted upside down, and that can auto detect that the camera is mounted upside down.
On: When enabled the video on screen is flipped. This setting is used with cameras that can be mounted upside down, but cannot auto detect that the camera is mounted upside down.
Off: Display the video on screen the normal way.

Example:

xConfiguration Cameras Camera 1 Flip: Off

xConfiguration Cameras Camera [1..7] Focus Mode

Set the camera focus mode.

Requires user role: ADMIN

Value space:

<Auto/Manual>

Auto: When set to Auto the focus will be updated throughout the call. When moving the camera, the system will use auto focus for a few seconds to set the right focus of the new camera position. After a few seconds auto focus is turned off to prevent continuous focus adjustments of the camera.
Manual: Turn the autofocus off and adjust the camera focus manually.

Example:

xConfiguration Cameras Camera 1 Focus Mode: Auto

xConfiguration Cameras Camera [1..7] Gamma Mode

Applies to cameras which supports gamma mode. The Gamma Mode setting enables for gamma corrections. Gamma describes the nonlinear relationship between image pixels and monitor brightness. The Cisco TelePresence PrecisionHD 720p camera supports gamma mode. The PrecisionHD 1080p camera does not support gamma mode.

Requires user role: ADMIN

Value space:

<Auto/Manual>

Auto: Auto is the default and the recommended setting.
Manual: In severe light conditions, you may switch mode to manual and specify explicitly which gamma table to use by setting the Gamma Level.

Example:

xConfiguration Cameras Camera 1 Gamma Mode: Auto

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. NOTE: Requires the Gamma Mode to be set to Manual.

Requires user role: ADMIN

Value space:

<0..7>

Range: Select a value from 0 to 7.

Example:

xConfiguration Cameras Camera 1 Gamma Level: 0

xConfiguration Cameras Camera [1..7] IrSensor

The IR sensor LED is located in the front of the camera and flickers when the IR sensor is activated from the remote control. Both the Codec C Series and PrecisionHD camera have IR sensors, and only one of them needs to be enabled at the time.

Requires user role: ADMIN

Value space:

<On/Off>

On: Enable the IR sensor on the camera.
Off: Disable the IR sensor on the camera.

Example:

xConfiguration Cameras Camera 1 IrSensor: On

xConfiguration Cameras Camera [1..7] Mirror

With Mirror mode (horizontal flip) you can mirror the image on screen.

Requires user role: ADMIN

Value space:

<Auto/On/Off>

Auto: When the camera is placed upside down the image is automatically mirrored. Use this setting with cameras that can be mounted upside down, and that can auto detect that the camera is mounted upside down.
On: See the selfview in mirror mode, e.g. the selfview is reversed and the experience of selfview is as seeing yourself in a mirror.
Off: See the selfview in normal mode, e.g. the experience of selfview is as seeing yourself as other people see you.

Example:

xConfiguration Cameras Camera 1 Mirror: Off

xConfiguration Cameras Camera [1..7] Whitebalance Mode

Set the camera whitebalance mode.

Requires user role: ADMIN

Value space:

<Auto/Manual>

Auto: The camera will continuously adjust the whitebalance depending on the camera view.
Manual: Enables manual control of the camera whitebalance, e.g. the level of the whitebalance level setting will be used for the camera.

Example:

xConfiguration Cameras Camera 1 Whitebalance Mode: Auto

xConfiguration Cameras Camera [1..7] Whitebalance Level

Set the whitebalance level. NOTE: Requires the Camera Whitebalance Mode to be set to manual.

Requires user role: ADMIN

Value space:

<1..16>

Range: Select a value from 1 to 16.

Example:

xConfiguration Cameras Camera 1 Whitebalance Level: 1

xConfiguration Cameras Camera [1..7] DHCP

Applies to cameras which supports DHCP. The Cisco TelePresence PrecsisionHD 1080p camera supports DHCP. The camera must be connected to a LAN. When set, the command enables support for SW upgrade of daisy chained cameras. It will enable the camera's DHCP function and force start of MAC and IP address retrieval. Remember to reset the DHCP when the camera is no longer connected to a LAN.

Requires user role: ADMIN

Value space:

<On/Off>

On: Enable DHCP in the camera. The camera is automatically re-booted. After re-boot the DHCP is started and the IP address will be retrieved. Run the commnand "xStatus Camera" for result.
Off: Disable DHCP in the camera. NOTE: This setting should be applied when the camera is not connected to a LAN.

Example:

xConfiguration Cameras Camera 1 DHCP: Off

The xConfiguration Conference commands

xConfiguration Conference [1..1] AutoAnswer Mode

Set the AutoAnswer mode.

Requires user role: ADMIN

Value space:

<On/Off>

On: Enable AutoAnswer to let the system automatically answer all incoming calls.
Off: The incoming calls must be answered manually by pressing the OK key or the green Call key on the remote control.

Example:

xConfiguration Conference 1 AutoAnswer Mode: Off

xConfiguration Conference [1..1] AutoAnswer Mute

Determine if the microphone shall be muted when an incoming call is automatically answered. NOTE: Requires the AutoAnswer Mode to be enabled.

Requires user role: ADMIN

Value space:

<On/Off>

On: The incoming call will be muted when automatically answered.
Off: The incoming call will not be muted.

Example:

xConfiguration Conference 1 AutoAnswer Mute: Off

xConfiguration Conference [1..1] AutoAnswer Delay

Define how long (in seconds) an incoming call has to wait before it is answered automatically by the system. NOTE: Requires the AutoAnswer Mode to be enabled.

Requires user role: ADMIN

Value space:

<0..50>

Range: Select a value from 0 to 50 seconds.

Example:

xConfiguration Conference 1 AutoAnswer Delay: 0

xConfiguration Conference [1..1] MicUnmuteOnDisconnect Mode

Determine if the microphones shall be unmuted automatically when all calls are disconnected. In a meeting room or other shared resources this could be done to prepare the system for the next user.

Requires user role: ADMIN

Value space:

<On/Off>

On: Un-mute the microphones after the call is disconnected.
Off: If muted, let the microphones remain muted after the call is disconnected.

Example:

xConfiguration Conference 1 MicUnmuteOnDisconnect Mode: On

xConfiguration Conference [1..1] DoNotDisturb Mode

Determine if there should be an alert on incoming calls.

Requires user role: USER

Value space:

<On/Off>

On: All incoming calls will be rejected, with no alert. The calling side will receive a busy signal when trying to call the codec. A message will display on screen, telling that Do not disturb is turned on, together with an option to turn off the Do not disturb. When turning off the Do not disturb mode you will see a list of the calls that have been rejected.
Off: The incoming calls will be alerted.

Example:

xConfiguration DoNotDisturb Mode: Off

xConfiguration Conference [1..1] FarEndControl Mode

Lets you decide if the remote side (far end) should be allowed to select your video sources and control your local camera (pan, tilt, zoom).

Requires user role: ADMIN

Value space:

<On/Off>

On: Allows the far end to be able to select your video sources and control your local camera (pan, tilt, zoom). You will still be able to control your camera and select your video sources as normal.
Off: The far end is not allowed to select your video sources or to control your local camera (pan, tilt, zoom).

Example:

xConfiguration Conference 1 FarEndControl Mode: On

xConfiguration Conference [1..1] FarEndControl SignalCapability

Set the far end control (H.224) signal capability mode.

Requires user role: ADMIN

Value space:

<On/Off>

On: Enable the far end control signal capability.
Off: Disable the far end control signal capability.

Example:

xConfiguration Conference 1 FarEndControl SignalCapability: On

xConfiguration Conference [1..1] Encryption Mode

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

Requires user role: ADMIN

Value space:

<BestEffort/On/Off>

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.
On: The system will only allow calls that are encrypted.
Off: The system will not use encryption.

Example:

xConfiguration Conference 1 Encryption Mode: BestEffort

xConfiguration Conference [1..1] DefaultCall Protocol

Set the Default Call Protocol to be used when placing calls from the system.

Requires user role: ADMIN

Value space:

<H323/Sip>

H.323: Select H.323 to ensure that calls are set up as H.323 calls.
Sip: Select SIP to ensure that calls are set up as SIP calls.

Example:

xConfiguration Conference 1 DefaultCall Protocol: H323

xConfiguration Conference [1..1] DefaultCall Rate

Set the Default Call Rate to be used when placing calls from the system.

Requires user role: ADMIN

Value space:

<64..6000>

Range: Select a value between 64 and 6000 kbps

Example:

xConfiguration Conference 1 DefaultCall Rate: 768

xConfiguration Conference [1..1] MaxTransmitCallRate

Specify the maximum transmit call rate to be used when placing or receiving calls.

Requires user role: ADMIN

Value space:

<64..6000>

Range: Select a value between 64 and 6000 kbps.

Example:

xConfiguration Conference 1 MaxTransmitCallRate: 6000

xConfiguration Conference [1..1] MaxReceiveCallRate

Specify the maximum receive call rate to be used when placing or receiving calls.

Requires user role: ADMIN

Value space:

<64..6000>

Range: Select a value between 64 and 6000 kbps.

Example:

xConfiguration Conference 1 MaxReceiveCallRate: 6000

xConfiguration Conference [1..1] VideoBandwidth Mode

Set the conference video bandwidth mode.

Requires user role: ADMIN

Value space:

<Dynamic/Static>

Dynamic: The available transmit bandwidth for the video channels are distributed among the currently active channels. If there is no presentation, the main video channels will use the bandwidth of the presentation channel.
Static: The available transmit bandwidth is assigned to each video channel, even if it is not active.

Example:

xConfiguration Conference 1 VideoBandwidth Mode: Dynamic

xConfiguration Conference [1..1] VideoBandwidth MainChannel Weight

The available transmit video bandwidth is distributed on the main channel and presentation channel according to "MainChannel Weight" and "PresentationChannel Weight". If the main channel weight is 2 and the presentation channel weight is 1, then the main channel will use twice as much bandwidth as the presentation channel.

Requires user role: ADMIN

Value space:

<1..10>

Range: 1 to 10.

Example:

xConfiguration Conference 1 VideoBandwidth MainChannel Weight: 5

xConfiguration Conference [1..1] VideoBandwidth PresentationChannel Weight

The available transmit video bandwidth is distributed on the main channel and presentation channel according to "MainChannel Weight" and "PresentationChannel Weight". If the main channel weight is 2 and the presentation channel weight is 1, then the main channel will use twice as much bandwidth as the presentation channel.

Requires user role: ADMIN

Value space:

<1..10>

Range: 1 to 10.

Example:

xConfiguration Conference 1 VideoBandwidth PresentationChannel Weight: 5

xConfiguration Conference [1..1] PacketLossResilience Mode

Set the packetloss resilience mode. This configuration will only take effect for calls initiated after the configuration is set.

Requires user role: ADMIN

Value space:

<On/Off>

On: Enable the packetloss resilience.
Off: Disable the packetloss resilience.

Example:

xConfiguration Conference 1 PacketLossResilience Mode: On

xConfiguration Conference [1..1] Presentation Policy

Control how the presentation service is to be performed.

Requires user role: ADMIN

Value space:

<LocalRemote/LocalOnly>

LocalRemote: The presentation will be shown locally and sent to remote side.
LocalOnly: The presentation will only be shown locally.

Example:

xConfiguration Conference 1 Presentation Policy: LocalRemote

xConfiguration Conference [1..1] IncomingMultisiteCall Mode

Set the incoming Multisite call mode. The MultiSite feature allows participants from more than two locations to join a meeting — by video and/or telephone.

Requires user role: ADMIN

Value space:

<Allow/Deny>

Allow: Accept incoming calls to an already active call/conference. The incoming call will be added to the MCU conference.
Deny: The system will not accept incoming calls when you are in a call. The calling side will receive a busy signal.

Example:

xConfiguration Conference 1 IncomingMultisiteCall Mode: Allow

The xConfiguration GPIO commands

xConfiguration GPIO Pin [1..4] Mode

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 output, they are set to 0 V. To activate them as input, they must be pulled down to 0 V.

Requires user role: ADMIN

Value space:

<InputNoAction/OutputManualState/OutputInCall/OutputMicrophonesMuted/OutputPresentationOn/OutputAllCallsEncrypted/OutputStandbyActive/InputMuteMicrophones>

InputNoAction: The pin state can be set, but no operation is performed.
OutputManualState: The pin state can be set by "xCommand GPIO ManualState Set PinX: <High/Low>" (to +12 V or 0 V, respectively).
OutputInCall: The pin is activated when in call, deactivated when not in call.
OutputMicrophonesMuted: The pin is activated when microphones are muted, deactivated when not muted.
OutputPresentationOn: The pin is activated when presentation is active, deactivated when presentation is not active.
OutputAllCallsEncrypted: The pin is activated when all calls are encrypted, deactivated when one or more calls are not encrypted.
OutputStandbyActive: The pin is activated when the system is in standby mode, deactivated when no longer in standby.
InputMuteMicrophones: When the pin is activated (0 V), the microphones will be muted. When deactivated (+ 12 V), the microphones are unmuted.

Example:

xConfiguration GPIO Pin 1 Mode: InputNoAction

The xConfiguration H323 commands

xConfiguration H323 NAT Mode

The firewall traversal technology creates a secure path through the firewall barrier, and enables proper exchange of audio/video data when connected to an external video conferencing system (when the IP traffic goes through a NAT router). NOTE: NAT does not work in conjunction with gatekeepers.

Requires user role: ADMIN

Value space:

<Auto/On/Off>

Auto: The system will determine if the "NAT Address" or the real IP-address should be used within signalling. This is done to make it possible to place calls to endpoints on the LAN as well as endpoints on the WAN.
On: The system will signal the configured "NAT Address" in place of its own IP-address within Q.931 and H.245. The NAT Server Address will be shown in the startup-menu as: "My IP Address: 10.0.2.1".
Off: The system will signal the real IP Address.

Example:

xConfiguration H323 NAT Mode: Off

xConfiguration H323 NAT Address

Enter the external/global IP-address to the router with NAT support. Packets sent to the router will then be routed to the system.

In the router, the following ports must be routed to the system's IP-address:

* Port 1720

* Port 5555-5574

* Port 2326-2485

Requires user role: ADMIN

Value space:

<S: 0, 64>

Format: String with a maximum of 64 characters.

Example:

xConfiguration H323 NAT Address: ""

xConfiguration H323 Profile [1..1] Authentication Mode

Set the authenticatin mode for the H.323 profile.

Requires user role: ADMIN

Value space:

<On/Off>

On: If the H.323 Gatekeeper Authentication Mode is set to On and a H.323 Gatekeeper indicates that it requires authentication, the system will try to authenticate itself to the gatekeeper. NOTE: Requires the Authentication LoginName and Authentication Password to be defined on both the codec and the Gatekeeper.
Off: If the H.323 Gatekeeper Authentication Mode is set to Off the system will not try to authenticate itself to a H.323 Gatekeeper, but will still try a normal registration.

Example:

xConfiguration H323 Profile 1 Authentication Mode: Off

xConfiguration H323 Profile [1..1] Authentication LoginName

The system sends the Authentication Login Name and the Authentication Password to a H.323 Gatekeeper for authentication. The authentication is a one way authentication from the codec to the H.323 Gatekeeper, i.e. the system is authenticated to the gatekeeper. If the H.323 Gatekeeper indicates that no authentication is required, the system will still try to register. NOTE: Requires the H.323 Gatekeeper Authentication Mode to be enabled.

Requires user role: ADMIN

Value space:

<S: 0, 50>

Format: String with a maximum of 50 characters.

Example:

xConfiguration H323 Profile 1 Authentication LoginName: ""

xConfiguration H323 Profile [1..1] Authentication Password

The system sends the Authentication Login Name and the Authentication Password to a H.323 Gatekeeper for authentication. The authentication is a one way authentication from the codec to the H.323 Gatekeeper, i.e. the system is authenticated to the gatekeeper. If the H.323 Gatekeeper indicates that no authentication is required, the system will still try to register. NOTE: Requires the H.323 Gatekeeper Authentication Mode to be enabled.

Requires user role: ADMIN

Value space:

<S: 0, 50>

Format: String with a maximum of 50 characters.

Example:

xConfiguration H323 Profile 1 Authentication Password:

xConfiguration H323 Profile [1..1] CallSetup Mode

The H.323 Call Setup Mode defines whether to use a Gatekeeper or Direct calling when establishing H323 calls.

NOTE: Direct H.323 calls can be made even though the H.323 Call Setup Mode is set to Gatekeeper.

Requires user role: ADMIN

Value space:

<Direct/Gatekeeper>

Direct: An IP-address must be used when dialling in order to make the H323 call.
Gatekeeper: The system will use a Gatekeeper to make a H.323 call. When selecting this option the H323 Profile Gatekeeper Address and H323 Profile Gatekeeper Discovery settings must also be configured.

Example:

xConfiguration H323 Profile 1 CallSetup Mode: Gatekeeper

xConfiguration H323 Profile [1..1] Gatekeeper Discovery

Determine how the system shall register to a H.323 Gatekeeper.

Requires user role: ADMIN

Value space:

<Manual/Auto>

Manual: The system will use a specific Gatekeeper identified by the Gatekeeper's IP-address.
Auto: The system will automatically try to register to any available Gatekeeper. If a Gatekeeper responds to the request sent from the codec within 30 seconds this specific Gatekeeper will be used. This requires that the Gatekeeper is in auto discovery mode as well. If no Gatekeeper responds, the system will not use a Gatekeeper for making H.323 calls and hence an IP-address must be specified manually.

Example:

xConfiguration H323 Profile 1 Gatekeeper Discovery: Manual

xConfiguration H323 Profile [1..1] Gatekeeper Address

Enter the IP address of the Gatekeeper. NOTE: Requires the H.323 Call Setup Mode to be set to Gatekeeper and the Gatekeeper Discovery to be set to Manual.

Requires user role: ADMIN

Value space:

<S: 0, 255>

Format: Only the valid IP address format is accepted. An IP address that contains letters (192.a.2.0) or unvalid IP addresses (192.0.1234.0) will be rejected.

Example:

xConfiguration H323 Profile 1 Gatekeeper Address: "192.0.2.0"

xConfiguration H323 Profile [1..1] H323Alias E164

The H.323 Alias E.164 defines the address of the system, according to the numbering plan implemented in the H.323 Gatekeeper. The E.164 alias is equivalent to a telephone number, sometimes combined with access codes.

Requires user role: ADMIN

Value space:

<S: 0, 30>

Format: Compact string with a maximum of 30 characters. Valid characters are 0-9, * and #.

Example:

xConfiguration H323 Profile 1 H323Alias E164: "90550092"

xConfiguration H323 Profile [1..1] H323Alias ID

Lets you specify the H.323 Alias ID which is used to address the system on a H.323 Gatekeeper and will be displayed in the call lists. Example: "firstname.surname@company.com", "My H.323 Alias ID"

Requires user role: ADMIN

Value space:

<S: 0, 49>

Format: String with a maximum of 49 characters

Example:

xConfiguration H323 Profile 1 H323Alias ID: "firstname.surname@company.com"

xConfiguration H323 Profile [1..1] PortAllocation

The H.323 Port Allocation setting affects the H.245 port numbers used for H.323 call signalling.

Requires user role: ADMIN

Value space:

<Dynamic/Static>

Dynamic: The system will allocate which ports to use when opening a TCP connection. The reason for doing this is to avoid using the same ports for subsequent calls, as some firewalls consider this as a sign of attack. When Dynamic is selected, the H.323 ports used are from 11000 to 20999. Once 20999 is reached they restart again at 11000. For RTP and RTCP media data, the system is using UDP ports in the range 2326 to 2487. Each media channel is using two adjacent ports, ie 2330 and 2331 for RTP and RTCP respectively. The ports are automatically selected by the system within the given range. Firewall administrators should not try to deduce which ports are used when, as the allocation schema within the mentioned range may change without any further notice.
Static: When set to Static the ports are given within a static predefined range [5555-6555].

Example:

xConfiguration H323 Profile 1 PortAllocation: Dynamic

The xConfiguration Network commands

xConfiguration Network [1..1] Assignment

Define whether to use DHCP or Static IPv4 assignment.

Requires user role: ADMIN

Value space:

<Static/DHCP>

Static: Set the network assignment to Static and configure the static IPv4 settings (IP Address, SubnetMask and Gateway).
DHCP: The system addresses are automatically assigned by the DHCP server.

Example:

xConfiguration Network 1 Assignment: DHCP

xConfiguration Network [1..1] DNS Domain Name

DNS Domain Name is the default domain name suffix which is added to unqualified names.

Example: If the DNS Domain Name is "company.com" and the name to lookup is "MyVideoSystem", this will result in the DNS lookup "MyVideoSystem.company.com".

Requires user role: ADMIN

Value space:

<S: 0, 64>

Format: String with a maximum of 64 characters.

Example:

xConfiguration Network 1 DNS Domain Name: ""

xConfiguration Network [1..1] DNS Server [1..5] Address

Define the network addresses for DNS servers. Up to 5 addresses may be specified. If the network addresses are unknown, contact your administrator or Internet Service Provider.

Requires user role: ADMIN

Value space:

<S: 0, 64>

Format: String with a maximum of 64 characters.

Example:

xConfiguration Network 1 DNS Server 1 Address: ""

xConfiguration Network [1..1] IPStack

Select which internet protocols the system will support.

Requires user role: ADMIN

Value space:

<IPv4/IPv6>

IPv4: IP version 4 is supported.
IPv6: IP version 6 is supported. The IPv4 settings (IP Address, IP Subnet Mask and Gateway) will be disabled.

Example:

xConfiguration Network 1 IPStack: IPv4

xConfiguration Network [1..1] IPv4 Address

Enter the static IPv4 network address for the system. Only applicable if the Network Assignment is set to Static.

Requires user role: ADMIN

Value space:

<S: 0, 64>

Format: Only the valid IP address format is accepted. An IP address that contains letters (192.a.2.0) or unvalid IP addresses (192.0.1234.0) will be rejected.

Example:

xConfiguration Network 1 IPv4 Address: "192.0.2.0"

xConfiguration Network [1..1] IPv4 Gateway

Define the IPv4 network gateway. Only applicable if the Network Assignment is set to Static.

Requires user role: ADMIN

Value space:

<S: 0, 64>

Format: Compact string with a maximum of 64 characters.

Example:

xConfiguration Network 1 IPv4 Gateway: "192.0.2.0"

xConfiguration Network [1..1] IPv4 SubnetMask

Define the IPv4 network subnet mask. Only applicable if the Network Assignment is set to Static.

Requires user role: ADMIN

Value space:

<S: 0, 64>

Format: Compact string with a maximum of 64 characters.

Example:

xConfiguration Network 1 IPv4 SubnetMask: "255.255.255.0"

xConfiguration Network [1..1] IPv6 Address

Enter the static IPv6 network address for the system. Only applicable if the Network IPv6 Assignment is set to Static.

Requires user role: ADMIN

Value space:

<S: 0, 64>

Format: The IPv6 address of host name.

Example:

xConfiguration Network 1 IPv6 Address: "ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff"

xConfiguration Network [1..1] IPv6 Gateway

Define the IPv6 network gateway address. Only applicable if the Network IPv6 Assignment is set to Static.

Requires user role: ADMIN

Value space:

<S: 0, 64>

Format: The IPv6 address of host name.

Example:

xConfiguration Network 1 IPv6 Gateway: "ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff"

xConfiguration Network [1..1] IPv6 Assignment

Define whether to use Autoconf or Static IPv6 assignment.

Requires user role: ADMIN

Value space:

<Static/Autoconf>

Static: Set the network assignment to Static and configure the static IPv6 settings (IP Address and Gateway).
Autoconf: Enable IPv6 stateless autoconfiguration of the IPv6 network interface. See RFC4862 for a detailed description.

Example:

xConfiguration Network 1 IPv6 Assignment: Autoconf

xConfiguration Network [1..1] IPv6 DHCPOptions

Retrieves a set of DHCP options from a DHCPv6 server.

Requires user role: ADMIN

Value space:

<On/Off>

On: Enable the retrieval of a selected set of DHCP options from a DHCPv6 server.
Off: Set to Off when IPv6 Assignment is set to Static.

Example:

xConfiguration Network 1 IPv6 Gateway: On

xConfiguration Network [1..1] QoS Mode

The QoS (Quality of Service) is a method which handles the priority of audio, video and data in the network. The QoS settings must be supported by the infrastructure. Diffserv (Differentiated Services) is a computer networking architecture that specifies a simple, scalable and coarse-grained mechanism for classifying, managing network traffic and providing QoS priorities on modern IP networks.

Requires user role: ADMIN

Value space:

<Off/Diffserv>

Off: No QoS method is used.
Diffserv: When you set the QoS Mode to Diffserv you must configure the Diffserv sub menu settings (Audio, Data, Signalling and Video).

Example:

xConfiguration Network 1 QoS Mode: diffserv

xConfiguration Network [1..1] QoS Diffserv Audio

The Diffserv Audio defines which priority Audio packets should have in an IP network. Enter a priority, which ranges from 0 to 63 for the packets. The higher the number, the higher the priority. These priorities might be overridden when packets are leaving the network controlled by the local network administrator. NOTE: Requires the Network QoS Mode to be set to Diffserv.

Requires user role: ADMIN

Value space:

<0..63>

Audio: A recommended value is Diffserv Code Point (DSCP) AF41, which equals the value 34. If in doubt, contact your network administrator.
Range: Select a value from 0 to 63.

Example:

xConfiguration Network 1 QoS Diffserv Audio: 0

xConfiguration Network [1..1] QoS Diffserv Data

The Diffserv Data defines which priority Data packets should have in an IP network. Enter a priority, which ranges from 0 to 63 for the packets. The higher the number, the higher the priority. These priorities might be overridden when packets are leaving the network controlled by the local network administrator. NOTE: Requires the Network QoS Mode to be set to Diffserv.

Requires user role: ADMIN

Value space:

<0..63>

Data: A recommended value is Diffserv Code Point (DSCP) AF23, which equals the value 22. If in doubt, contact your network administrator.
Range: Select a value from 0 to 63.

Example:

xConfiguration Network 1 QoS Diffserv Data: 0

xConfiguration Network [1..1] QoS Diffserv Signalling

The Diffserv Signalling defines which priority Signalling packets should have in an IP network. Enter a priority, which ranges from 0 to 63 for the packets. The higher the number, the higher the priority. These priorities might be overridden when packets are leaving the network controlled by the local network administrator. NOTE: Requires the Network QoS Mode to be set to Diffserv.

Requires user role: ADMIN

Value space:

<0..63>

Signalling: A recommended value is Diffserv Code Point (DSCP) AF31, which equals the value 26. If in doubt, contact your network administrator.
Range: Select a value from 0 to 63.

Example:

xConfiguration Network 1 QoS Diffserv Signalling: 0

xConfiguration Network [1..1] QoS Diffserv Video

The Diffserv Video defines which priority Video packets should have in an IP network. Enter a priority, which ranges from 0 to 63 for the packets. The higher the number, the higher the priority. These priorities might be overridden when packets are leaving the network controlled by the local network administrator. NOTE: Requires the Network QoS Mode to be set to Diffserv.

Requires user role: ADMIN

Value space:

<0..63>

Video: A recommended value is Diffserv Code Point (DSCP) AF41, which equals the value 34. If in doubt, contact your network administrator.
Range: Select a value from 0 to 63.

Example:

xConfiguration Network 1 QoS Diffserv Video: 0

xConfiguration Network [1..1] IEEE8021X Mode

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

Value space:

<On/Off>

On: The 802.1X authentication is enabled.
Off: The 802.1X authentication is disabled (default).

Example:

xConfiguration Network 1 IEEE8021X Mode: Off

xConfiguration Network [1..1] IEEE8021X TlsVerify

Verification of the server-side certificate of an IEEE802.1x connection against the certificates in the local CA-list when TLS is used. The CA-list must be uploaded to the video system / codec.

This setting takes effect only when Network [1..1] IEEE8021X Eap Tls is enabled (On).

Requires user role: ADMIN

Value space:

<Off/On>

Off: When set to Off, TLS connections are allowed without verifying the server-side X.509 certificate against the local CA-list. This should typically be selected if no CA-list has been uploaded to the codec.
On: When set to On, the server-side X.509 certificate will be validated against the local CA-list for all TLS connections. Only servers with a valid certificate will be allowed.

Example:

xConfiguration xConfiguration Network 1 IEEE8021X TlsVerify: Off

xConfiguration Network [1..1] IEEE8021X UseClientCertificate

Authentication using a private key/certificate pair during an IEEE802.1x connection. The authentication X.509 certificate must be uploaded to the video system / codec.

Requires user role: ADMIN

Value space:

<Off/On>

Off: When set to Off client-side authentication is not used (only server-side).
On: When set to On the client (codec) will perform a mutual authentication TLS handshake with the server.

Example:

xConfiguration Network 1 IEEE8021X UseClientCertificate: Off

xConfiguration Network [1..1] IEEE8021X Identity

The 802.1X Identity is the user name needed for 802.1X authentication.

Requires user role: ADMIN

Value space:

<S: 0, 64>

Format: String with a maximum of 64 characters.

Example:

xConfiguration Network 1 IEEE8021X Identity: ""

xConfiguration Network [1..1] IEEE8021X Password

The 802.1X Password is the password needed for 802.1X authentication.

Requires user role: ADMIN

Value space:

<S: 0, 32>

Format: String with a maximum of 32 characters.

Example:

xConfiguration Network 1 IEEE8021X Password: "***"

xConfiguration Network [1..1] IEEE8021X AnonymousIdentity

The 802.1X Anonymous ID string is to be used as unencrypted identity with EAP (Extensible Authentication Protocol) types that support different tunneled identity, like EAP-PEAP and EAP-TTLS. If set, the anonymous ID will be used for the initial (unencrypted) EAP Identity Request.

Requires user role: ADMIN

Value space:

<S: 0, 64>

Format: String with a maximum of 64 characters.

Example:

xConfiguration Network 1 IEEE8021X AnonymousIdentity: ""

xConfiguration Network [1..1] IEEE8021X Eap Md5

Set the Md5 (Message-Digest Algorithm 5) mode. This is a Challenge Handshake Authentication Protocol that relies on a shared secret. Md5 is a Weak security.

Requires user role: ADMIN

Value space:

<On/Off>

On: The EAP-MD5 protocol is enabled (default).
Off: The EAP-MD5 protocol is disabled.

Example:

xConfiguration Network 1 IEEE8021X Eap Md5: On

xConfiguration Network [1..1] IEEE8021X Eap Ttls

Set the TTLS (Tunneled Transport Layer Security) mode. Authenticates LAN clients without the need for client certificates. Developed by Funk Software and Certicom. Usually supported by Agere Systems, Proxim and Avaya.

Requires user role: ADMIN

Value space:

<On/Off>

On: The EAP-TTLS protocol is enabled (default).
Off: The EAP-TTLS protocol is disabled.

Example:

xConfiguration Network 1 IEEE8021X Eap Ttls: On

xConfiguration Network [1..1] IEEE8021X Eap Tls

Enable or disable the use of EAP-TLS (Transport Layer Security) for IEEE802.1x connections. The EAP-TLS protocol, defined in RFC5216, is considered one of the most secure EAP standards. LAN clients are authenticated using client certificates.

Requires user role: ADMIN

Value space:

<Off/On>

Off: The EAP-TLS protocol is disabled.
On: The EAP-TLS protocol is enabled (default).

Example:

xConfiguration Network 1 IEEE8021X Eap Tls: On

xConfiguration Network [1..1] IEEE8021X Eap Peap

Set the Peap (Protected Extensible Authentication Protocol) mode. Authenticates LAN clients without the need for client certificates. Developed by Microsoft, Cisco and RSA Security.

Requires user role: ADMIN

Value space:

<On/Off>

On: The EAP-PEAP protocol is enabled (default).
Off: The EAP-PEAP protocol is disabled.

Example:

xConfiguration Network 1 IEEE8021X Eap Peap: On

xConfiguration Network [1..1] MTU

Set the Ethernet MTU (Maximum Transmission Unit).

Requires user role: ADMIN

Value space:

<576..1500>

Range: Select a value from 576 to 1500 bytes.

Example:

xConfiguration Network 1 MTU: 1500

xConfiguration Network [1..1] Speed

Set the Ethernet link speed.

Requires user role: ADMIN

Value space:

<Auto/10half/10full/100half/100full/1000full>

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.

Example:

xConfiguration Network 1 Speed: Auto

xConfiguration Network [1..1] TrafficControl Mode

Set the network traffic control mode to decide how to control the video packets transmission speed.

Requires user role: ADMIN

Value space:

<On/Off>

On: Transmit video packets at maximum 20 Mbps. Can be used to smooth out bursts in the outgoing network traffic.
Off: Transmit video packets at link speed.

Example:

xConfiguration Network 1 TrafficControl: On

xConfiguration Network [1..1] RemoteAccess Allow

Filter IP addresses for access to ssh/telnet/HTTP/HTTPS.

Requires user role: ADMIN

Value space:

<S: 0, 255>

Format: String with a maximum of 255 characters, comma separated IP adresses or IP range.

Example:

xConfiguration Network 1 RemoteAccess Allow: "192.168.1.231, 192.168.1.182"

xConfiguration Network [1..1] VLAN Voice Mode

Set the VLAN voice mode.

Requires user role: ADMIN

Value space:

<Auto/Manual/Off>

Auto: The Cisco Discovery Protocol (CDP), if available, assigns an id to the voice VLAN. If CDP is not available, VLAN is not enabled. The VLAN Voice Mode automatically will be set to Auto when the GUI is used to set the Provisioning Mode to CUCM.
Manual: The VLAN id is set manually using the Network VLAN Voice VlanId setting. If CDP is available, the manually set value will be overruled by the value assigned by CDP.
Off: VLAN is not enabled.

Example:

xConfiguration Network 1 VLAN Voice Mode: Off

xConfiguration Network [1..1] VLAN Voice VlanId

Set the VLAN voice ID. This setting will only take effect if VLAN Voice Mode is set to Manual.

Requires user role: ADMIN

Value space:

<1..4094>

Range: Select a value from 1 to 4094.

Example:

xConfiguration Network 1 VLAN Voice VlanId: 1

The xConfiguration NetworkPort commands

xConfiguration NetworkPort [2] Mode

Define if the network port 2 shall be enabled for direct pairing with the Cisco TelePresence Touch for C Series.

Requires user role: ADMIN

Value space:

<Inactive/DirectPairing>

Inactive: Set the NetworkPort 2 to Inactive when no device is connected.
DirectPairing: Set the NetworkPort 2 to DirectPairing when you have a Cisco TelePresence Touch unit connected to the port. This will enable for direct pairing between the touch unit and the codec.

Example:

xConfiguration NetworkPort 2 Mode: Inactive

The xConfiguration NetworkServices commands

xConfiguration NetworkServices Multiway Address

The Multiway address must be equal to the Conference Factory Alias, as configured on the Video Communication Server. The Multiway™ conferencing enables video endpoint users to introduce a 3rd party into an existing call.

Multiway™ can be used in the following situations:

1) When you want to add someone else in to your existing call.

2) When you are called by a 3rd party while already in a call and you want to include that person in the call.

Requirements: The Codec C20 must be running TC3.0 (or later), Codec C90/C60/C40 must be running TC4.0 (or later), EX90/EX60/MX200/MX300 must be running TC4.2 (or later), Video Communication Server (VCS) version X5 (or later) and Codian MCU version 3.1 (or later). Endpoints invited to join the Multiway™ conference must support the H.323 routeToMC facility message if in an H.323 call, or SIP REFER message if in a SIP call.

Requires user role: ADMIN

Value space:

<S: 0, 255>

Format: String with a maximum of 255 characters.

Example:

xConfiguration NetworkServices Multiway Address: "h323:multiway@company.com"

xConfiguration NetworkServices Multiway Protocol

Determine the protocol to be used for Multiway calls. NOTE: Requires a restart of the codec.

Requires user role: ADMIN

Value space:

<Auto/H323/Sip>

Auto: The system will select the protocol for Multiway calls.
H323: The H323 protocol will be used for Multiway calls.
Sip: The SIP protocol will be used for Multiway calls.

Example:

xConfiguration NetworkServices Multiway Protocol: Auto

xConfiguration NetworkServices H323 Mode

Determine whether the system should be able to place and receive H.323 calls or not. NOTE: Requires a restart of the codec.

Requires user role: ADMIN

Value space:

<On/Off>

On: Enable the possibility to place and receive H.323 calls (default).
Off: Disable the possibility to place and receive H.323 calls.

Example:

xConfiguration NetworkServices H323 Mode: On

xConfiguration NetworkServices HTTP Mode

Set the HTTP mode to enable/disable access to the system through a web browser. The web interface is used for system management, call management such as call transfer, diagnostics and software uploads.

Requires user role: ADMIN

Value space:

<On/Off>

On: The HTTP protocol is enabled.
Off: The HTTP protocol is disabled.

Example:

xConfiguration NetworkServices HTTP Mode: On

xConfiguration NetworkServices HTTPS Mode

HTTPS is a web protocol that encrypts and decrypts user page requests as well as the pages that are returned by the web server.

Requires user role: ADMIN

Value space:

<On/Off>

On: The HTTPS protocol is enabled.
Off: The HTTPS protocol is disabled.

Example:

xConfiguration NetworkServices HTTPS Mode: On

xConfiguration NetworkServices HTTPS VerifyServerCertificate

When the system connects to an external HTTPS server (like a phonebook server or an external manager), this server will present a certificate to the system to identify itself.

Requires user role: ADMIN

Value space:

<On/Off>

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.
Off: Do not verify server certificates.

Example:

xConfiguration NetworkServices HTTPS VerifyServerCertificate: Off

xConfiguration NetworkServices HTTPS VerifyClientCertificate

When the system connects to a HTTPS client (like a web browser), the client can be asked to present a certificate to the system to identify itself.

Requires user role: ADMIN

Value space:

<On/Off>

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: Do not verify client certificates.

Example:

xConfiguration NetworkServices HTTPS VerifyClientCertificate: Off

xConfiguration NetworkServices HTTPS OCSP Mode

Define the support for OCSP (Online Certificate Status Protocol) responder services. The OCSP feature allows users to enable OCSP instead of certificate revocation lists (CRLs) to check certificate status.

Requires user role: ADMIN

Value space:

<On/Off>

On: Enable OCSP support.
Off: Disable OCSP support.

Example:

xConfiguration NetworkServices HTTPS OCSP Mode: Off

xConfiguration NetworkServices HTTPS OCSP URL

Specify the URL of an OCSP server.

Requires user role: ADMIN

Value space:

<S: 0, 255>

Format: String with a maximum of 255 characters.

Example:

xConfiguration NetworkServices HTTPS OCSP URL: "http://ocspserver.company.com:81"

xConfiguration NetworkServices NTP Mode

The Network Time Protocol (NTP) is used to synchronize the time of the system to a reference time server. The time server will subsequently be queried every 24th hour for time updates. The time will be displayed on the top of the screen. The system will use the time to timestamp messages transmitted to Gatekeepers or Border Controllers requiring H.235 authentication. The system will use the time to timestamp messages transmitted to Gatekeepers or Border Controllers that requires H.235 authentication. It is also used for timestamping Placed Calls, Missed Calls and Received Calls.

Requires user role: ADMIN

Value space:

<Off/Auto/Manual>

Off: The system will not use an NTP server.
Auto: The system will use the NTP server, by which address is supplied from the DHCP server in the network. If no DHCP server is used, or the DHCP server does not provide the system with a NTP server address, the system will use the static defined NTP server address specified by the user.
Manual: The system will always use the static defined NTP server address specified by the user.

Example:

xConfiguration NetworkServices NTP Mode: Manual

xConfiguration NetworkServices NTP Address

Enter the NTP Address to define the network time protocol server address. This address will be used if NTP Mode is set to Manual, or if set to Auto and no address is supplied by a DHCP server.

Requires user role: ADMIN

Value space:

<S: 0, 64>

Format: String with a maximum of 64 characters.

Example:

xConfiguration NetworkServices NTP Address: "1.ntp.tandberg.com"

xConfiguration NetworkServices SIP Mode

Determine whether the system should be able to place and receive SIP calls or not. NOTE: Requires a restart of the codec.

Requires user role: ADMIN

Value space:

<On/Off>

On: Enable the possibility to place and receive SIP calls (default).
Off: Disable the possibility to place and receive SIP calls.

Example:

xConfiguration NetworkServices SIP Mode: On

xConfiguration NetworkServices SNMP Mode

SNMP (Simple Network Management Protocol) is used in network management systems to monitor network-attached devices (routers, servers, switches, projectors, etc) for conditions that warrant administrative attention. SNMP exposes management data in the form of variables on the managed systems, which describe the system configuration. These variables can then be queried (set to ReadOnly) and sometimes set (set to ReadWrite) by managing applications.

Requires user role: ADMIN

Value space:

<Off/ReadOnly/ReadWrite>

Off: Disable the SNMP network service.
ReadOnly: Enable the SNMP network service for queries only.
ReadWrite: Enable the SNMP network service for both queries and commands.

Example:

xConfiguration NetworkServices SNMP Mode: ReadWrite

xConfiguration NetworkServices SNMP Host [1..3] Address

Enter the address of up to three SNMP Managers.

The system's SNMP Agent (in the codec) responds to requests from SNMP Managers (a PC program etc.), e.g. about system location and system contact. SNMP traps are not supported.

Requires user role: ADMIN

Value space:

<S: 0, 64>

Format: String with a maximum of 64 characters.

Example:

xConfiguration NetworkServices SNMP Host 1 Address: ""

xConfiguration NetworkServices SNMP CommunityName

Enter the name of the Network Services SNMP Community. SNMP Community names are used to authenticate SNMP requests. SNMP requests must have a password (case sensitive) in order to receive a response from the SNMP Agent in the codec. The default password is "public". If you have the Cisco TelePresence Management Suite (TMS) you must make sure the same SNMP Community is configured there too. NOTE: The SNMP Community password is case sensitive.

Requires user role: ADMIN

Value space:

<S: 0, 50>

Format: String with a maximum of 50 characters.

Example:

xConfiguration NetworkServices SNMP CommunityName: "public"

xConfiguration NetworkServices SNMP SystemContact

Enter the name of the Network Services SNMP System Contact.

Requires user role: ADMIN

Value space:

<S: 0, 50>

Format: String with a maximum of 50 characters.

Example:

xConfiguration NetworkServices SNMP SystemContact: ""

xConfiguration NetworkServices SNMP SystemLocation

Enter the name of the Network Services SNMP System Location.

Requires user role: ADMIN

Value space:

<S: 0, 50>

Format: String with a maximum of 50 characters.

Example:

xConfiguration NetworkServices SNMP SystemLocation: ""

xConfiguration NetworkServices SSH Mode

SSH (or Secure Shell) protocol can provide secure encrypted communication between the codec and your local computer.

Requires user role: ADMIN

Value space:

<On/Off>

On: The SSH protocol is enabled.
Off: The SSH protocol is disabled.

Example:

xConfiguration NetworkServices SSH Mode: On

xConfiguration NetworkServices SSH AllowPublicKey

Secure Shell (SSH) public key authentication can be used to access the codec.

Requires user role: ADMIN

Value space:

<On/Off>

On: The SSH public key is allowed.
Off: The SSH public key is not allowed.

Example:

xConfiguration NetworkServices SSH AllowPublicKey: On

xConfiguration NetworkServices Telnet Mode

Telnet is a network protocol used on the Internet or Local Area Network (LAN) connections.

Requires user role: ADMIN

Value space:

<On/Off>

On: The Telnet protocol is enabled.
Off: The Telnet protocol is disabled. This is the factory setting.

Example:

xConfiguration NetworkServices Telnet Mode: Off

The xConfiguration Phonebook commands

xConfiguration Phonebook Server [1..1] ID

Enter a name for the external phonebook.

Requires user role: ADMIN

Value space:

<S: 0, 64>

Format: String with a maximum of 64 characters.

Example:

xConfiguration Phonebook Server 1 ID: ""

xConfiguration Phonebook Server [1..1] Type

Select the phonebook server type.

Requires user role: ADMIN

Value space:

<VCS/TMS/Callway/CUCM>

VCS: Select VCS if the phonebook is located on the Cisco TelePresence Video Communication Server.
TMS: Select TMS if the phonebook is located on the Cisco TelePresence Management Suite server.
Callway: Select Callway if the phonebook is to be provided by the Callway subscription service. Contact your Callway provider for more information.
CUCM: Select CUCM if the phonebook is located on the Cisco Unified Communications Manager.

Example:

xConfiguration Phonebook Server 1 Type: TMS

xConfiguration Phonebook Server [1..1] URL

Enter the address (URL) to the external phonebook server.

Requires user role: ADMIN

Value space:

<S: 0, 255>

Format: String with a maximum of 255 characters.

Example:

xConfiguration Phonebook Server 1 URL: "http://tms.company.com/tms/public/external/phonebook/phonebookservice.asmx"

The xConfiguration Provisioning commands

xConfiguration Provisioning Connectivity

This setting controls how the device discovers whether it should request an internal or external configuration from the provisioning server.

Requires user role: ADMIN

Value space:

<Internal/External/Auto>

Internal: Request internal configuration.
External: Request external configuration.
Auto: Automatically discover using NAPTR queries whether internal or external configurations should be requested. If the NAPTR responses have the "e" flag, external configurations will be requested. Otherwise internal configurations will be requested.

Example:

xConfiguration Provisioning Connectivity: Auto

xConfiguration Provisioning Mode

It is possible to configure the codec (video system) using a provisioning system / an external manager. This allows video conferencing network administrators to manage many video systems simultaneously.

With this setting you choose which type of provisioning system to use. Provisioning can also be switched off. Contact your provisioning system provider/representative for more information.

Requires user role: ADMIN

Value space:

<Off/TMS/VCS/CallWay/CUCM/Auto>

Off: The video system will not be configured by a provisioning system.
TMS: The video system will be configured using TMS (Cisco TelePresence Management System).
VCS: The video system will be configured using VCS (Cisco TelePresence Video Communication Server).
Callway: The video system will be configured using Callway (subscription service).
CUCM: The video system will be configured using CUCM (Cisco Unified Communications Manager).
Auto: The provisioning server will automatically be selected by the video system.

Example:

xConfiguration Provisioning Mode: TMS

xConfiguration Provisioning LoginName

This is the user name part of the credentials used to authenticate the video system with the provisioning server. This setting must be used when required by the provisioning server. If Provisioning Mode is Callway, enter the video number.

Requires user role: ADMIN

Value space:

<S: 0, 80>

Format: String with a maximum of 80 characters.

Example:

xConfiguration Provisioning LoginName: ""

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. If Provisioning Mode is Callway, enter the activation code.

Requires user role: ADMIN

Value space:

<S: 0, 64>

Format: String with a maximum of 64 characters.

Example:

xConfiguration Provisioning Password: ""

xConfiguration Provisioning HttpMethod

Select the HTTP method to be used for the provisioning.

Requires user role: ADMIN

Value space:

<GET/POST>

GET: Select GET when the provisiong server supports GET.
POST: Select POST when the provisiong server supports POST.

Example:

xConfiguration Provisioning HttpMethod: POST

xConfiguration Provisioning ExternalManager Address

Enter the IP Address or DNS name of the external manager / provisioning system.

If an External Manager Address (and Path) is configured, the system will send a message to this address when starting up. When receiving this message the external manager / provisioning system can return configurations/commands to the unit as a result.

When using CUCM or TMS provisioning, the DHCP server can be set up to provide the external manager address automatically (DHCP Option 242 for TMS, and DHCP Option 150 for CUCM). An address set in the Provisioning ExternalManager Address setting will override the setting provided by DHCP.

Requires user role: ADMIN

Value space:

<S: 0, 64>

Format: A valid IP address format or DNS name; a compact string with a maximum of 64 characters.

Example:

xConfiguration Provisioning ExternalManager Address: ""

xConfiguration Provisioning ExternalManager Protocol

Determine whether to use secure management or not.

Requires user role: ADMIN

Value space:

<HTTP/HTTPS>

HTTP: Set to HTTP to disable secure management. Requires HTTP to be enabled in the xConfiguration NetworkServices HTTP Mode setting.
HTTPS: Set to HTTPS to enable secure management. Requires HTTPS to be enabled in the xConfiguration NetworkServices HTTPS Mode setting.

Example:

xConfiguration Provisioning ExternalManager Protocol: HTTP

xConfiguration Provisioning ExternalManager Path

Set the Path to the external manager / provisioning system. This setting is required when several management services reside on the same server, i.e. share the same External Manager address.

Requires user role: ADMIN

Value space:

<S: 0, 255>

Format: String with a maximum of 255 characters.

Example:

xConfiguration Provisioning ExternalManager Path: "tms/public/external/management/SystemManagementService.asmx"

xConfiguration Provisioning ExternalManager Domain

Enter the SIP domain for the VCS provisioning server.

Requires user role: ADMIN

Value space:

<S: 0, 64>

Format: String with a maximum of 64 characters.

Example:

xConfiguration Provisioning ExternalManager Domain: "any.domain.com"

The xConfiguration RTP commands

xConfiguration RTP Ports Range Start

Specify the first port in the range of RTP ports. See also the "H323 Profile [1..1] PortAllocation" command.

Requires user role: USER

Value space:

<1024..65502>

Range: Select a value from 1024 to 65502.

Example:

xConfiguration RTP Ports Range Start: 2326

xConfiguration RTP Ports Range Stop

Specify the last RTP port in the range. See also the "H323 Profile [1..1] PortAllocation" command.

Requires user role: USER

Value space:

<1056..65535>

Range: Select a value from 1056 to 65535.

Example:

xConfiguration RTP Ports Range Stop: 2486

The xConfiguration Security commands

xConfiguration Security Audit Server Address

Enter the external/global IP-address to the audit syslog server. IPv6 is not supported.

NOTE: Requires a restart of the system for any change to take effect.

Requires user role: AUDIT

Value space:

<S: 0, 64>

Format: String with a maximum of 64 characters.

Example:

xConfiguration Security Audit Server Address: ""

xConfiguration Security Audit Server Port

Enter the port of the syslog server that the system shall send its audit logs to. The default port is 514.

NOTE: Requires a restart of the system for any change to take effect.

Requires user role: AUDIT

Value space:

<0..65535>

Range: Select a value from 0 to 65535.

Example:

xConfiguration Security Audit Server Port: 514

xConfiguration Security Audit OnError Action

Describes what actions will be taken if connection to the syslog server is lost. This setting is only relevant if Security Audit Logging Mode is set to ExternalSecure.

NOTE: Requires a restart of the system for any change to take effect.

Requires user role: AUDIT

Value space:

<Halt/Ignore>

Halt: If a halt condition is detected the unit is rebooted and only the auditor is allowed to operate the unit until the halt condition has passed. When the halt condition has passed the audit logs are re-spooled to the external server. Halt conditions are: A network breach (no physical link), no external syslog server running (or wrong server address or port), TLS authentication failed (if in use), local backup (re-spooling) log full.
Ignore: The system will continue its normal operation, and rotate internal logs when full. When connection is restored it will again send its audit logs to the syslog server.

Example:

xConfiguration Security Audit OnError Action: Ignore

xConfiguration Security Audit Logging Mode

Describes where the audit logs are recorded or transmitted.

NOTE: Requires a restart of the system for any change to take effect.

Requires user role: AUDIT

Value space:

<Off/Internal/External/ExternalSecure>

Off: No audit logging is performed.
Internal: The system records the audit logs to internal logs, and rotates logs when they are full.
External: The system sends the audit logs to an external audit syslog server. The external server must support TCP.
ExternalSecure: The system sends encrypted audit logs to an external audit server that is verified by a certificate in the Audit CA list. The Audit CA list file must be uploaded to the codec using the web interface. The common_name parameter of a certificate in the CA list must match the IP address of the syslog server.

Example:

xConfiguration Security Audit Logging Mode: Off

xConfiguration Security Session ShowLastLogon

When logging in to the system using SSH or Telnet you will see the UserId, time and date of the last session that did a successful login.

Requires user role: ADMIN

Value space:

<Off/On>

On: Set to On to enable the possibility to show information about the last session.
Off: Set to Off to disable the possibility to show information about the last session.

Example:

xConfiguration Security Session ShowLastLogon: Off

xConfiguration Security Session InactivityTimeout

Determines how long the system will accept inactivity from the user before he is automatically logged out.

Requires user role: ADMIN

Value space:

<0..10000>

Range: Select a value from 0 to 10000 seconds. 0 means that inactivity will not enforce automatically logout.

Example:

xConfiguration Security Session InactivityTimeout: 0

The xConfiguration SerialPort commands

xConfiguration SerialPort Mode

Set the COM 1 serial port to be enabled/disabled.

Requires user role: ADMIN

Value space:

<On/Off>

On: Enable the COM 1 serial port.
Off: Disable the COM 1 serial port.

Example:

xConfiguration SerialPort Mode: On

xConfiguration SerialPort BaudRate

Specify the baud rate (data transmission rate, bits per second) for the COM 1 port on the codec. The default value is 38400.

Connection parameters for the COM port: Data bits: 8; Parity: None; Stop bits: 1; Flow control: None.

Requires user role: ADMIN

Value space:

<9600/19200/38400/57600/115200>

Range: Select a baud rate from the baud rates listed (bps).

Example:

xConfiguration SerialPort BaudRate: 38400

xConfiguration SerialPort LoginRequired

Determine if login shall be required when connecting to the COM 1 port at the codec.

Requires user role: ADMIN

Value space:

<On/Off>

On: Login is required when connecting to the codec through COM 1 port.
Off: The user can access the codec through COM 1 port without any login.

Example:

xConfiguration SerialPort LoginRequired: On

The xConfiguration SIP commands

xConfiguration SIP Profile [1..1] URI

The SIP URI or number is used to address the system. This is the URI that is registered and used by the SIP services to route inbound calls to the system. A Uniform Resource Identifier (URI) is a compact string of characters used to identify or name a resource.

Requires user role: ADMIN

Value space:

<S: 0, 255>

Format: Compact string with a maximum of 255 characters.

Example:

xConfiguration SIP Profile 1 URI: "sip:firstname.lastname@company.com"

xConfiguration SIP Profile [1..1] DisplayName

When configured the incoming call will report the DisplayName instead of the SIP URI.

Requires user role: ADMIN

Value space:

<S: 0, 255>

Format: String with a maximum of 255 characters.

Example:

xConfiguration SIP Profile 1 DisplayName: ""

xConfiguration SIP Profile [1..1] Authentication [1..1] LoginName

This is the user name part of the credentials used to authenticate towards the SIP proxy.

Requires user role: ADMIN

Value space:

<S: 0, 128>

Format: String with a maximum of 128 characters.

Example:

xConfiguration SIP Profile 1 Authentication 1 LoginName: ""

xConfiguration SIP Profile [1..1] Authentication [1..1] Password

This is the password part of the credentials used to authenticate towards the SIP proxy.

Requires user role: ADMIN

Value space:

<S: 0, 128>

Format: String with a maximum of 128 characters.

Example:

xConfiguration SIP Profile 1 Authentication 1 Password:

xConfiguration SIP Profile [1..1] DefaultTransport

Select the transport protocol to be used over the LAN.

Requires user role: ADMIN

Value space:

<UDP/TCP/Tls/Auto>

UDP: The system will always use UDP as the default transport method.
TCP: The system will always use TCP as the default transport method.
Tls: The system will always use TLS as the default transport method. For TLS connections a SIP CA-list can be uploaded to the video system. If no such CA-list is available on the system then anonymous Diffie Hellman will be used.
Auto: The system will try to connect using transport protocols in the following order: TLS, TCP, UDP.

Example:

xConfiguration SIP Profile 1 DefaultTransport: Auto

xConfiguration SIP Profile [1..1] TlsVerify

For TLS connections a SIP CA-list can be uploaded to the video system.

Requires user role: ADMIN

Value space:

<On/Off>

On: Set to On to verify TLS connections. Only TLS connections to servers, whose x.509 certificate is validated against the CA-list, will be allowed.
Off: Set to Off to allow TLS connections without verifying them. The TLS connections are allowed to be set up without verifying the x.509 certificate received from the server against the local CA-list. This should typically be selected if no SIP CA-list has been uploaded.

Example:

xConfiguration SIP Profile 1 TlsVerify: Off

xConfiguration SIP Profile [1..1] Outbound

The client initiated connections mechanism for firewall traversal, connection reuse and redundancy. The current version supports http://tools.ietf.org/html/draft-ietf-sip-outbound-20.

Requires user role: ADMIN

Value space:

<On/Off>

On: Set up multiple outbound connections to servers in the Proxy Address list.
Off: Connect to the single proxy configured first in Proxy Address list.

Example:

xConfiguration SIP Profile 1 Outbound: Off

xConfiguration SIP Profile [1..1] 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. If Outbound is enabled, multiple proxies can be addressed.

Requires user role: ADMIN

Value space:

<S: 0, 255>

Format: Compact string with a maximum of 255 characters. An IP address that contains letters (192.a.2.0) or unvalid IP addresses (192.0.1234.0) will be rejected.

Example:

xConfiguration SIP Profile 1 Proxy 1 Address: ""

xConfiguration SIP Profile [1..1] Proxy [1..4] Discovery

Select if the SIP Proxy address is to be obtained manually or by using Dynamic Host Configuration Protocol (DHCP).

Requires user role: ADMIN

Value space:

<Auto/Manual>

Auto: When Auto is selected, the SIP Proxy address is obtained using Dynamic Host Configuration Protocol (DHCP).
Manual: When Manual is selected, the manually configured SIP Proxy address will be used.

Example:

xConfiguration SIP Profile 1 Proxy 1 Discovery: Manual

xConfiguration SIP Profile [1..1] Type

Enables SIP extensions and special behaviour for a vendor or provider.

Requires user role: ADMIN

Value space:

<Standard/Alcatel/Avaya/Cisco/Microsoft/Nortel>

Standard: To be used when registering to standard SIP Proxy (tested with Cisco TelePresence VCS and Broadsoft)
Alcatel: To be used when registering to Alcatel-Lucent OmniPCX Enterprise. NOTE: This mode is not fully supported.
Avaya: To be used when registering to Avaya Communication Manager. NOTE: This mode is not fully supported.
Cisco: To be used when registering to Cisco Unified Communication Manager.
Microsoft: To be used when registering to Microsoft LCS or OCS. NOTE: This mode is not fully supported.
Nortel: To be used when registering to Nortel MCS 5100 or MCS 5200 PBX. NOTE: This mode is not fully supported.

Example:

xConfiguration SIP Profile 1 Type: Standard

The xConfiguration Standby commands

xConfiguration Standby Control

Determine whether the system should go into standby mode or not.

Requires user role: ADMIN

Value space:

<On/Off>

On: Enter standby mode when the Standby Delay has timed out. NOTE: Requires the Standby Delay to be set to an appropriate value.
Off: The system will not enter standby mode.

Example:

xConfiguration Standby Control: On

xConfiguration Standby Delay

Define how long (in minutes) the system shall be in idle mode before it goes into standby mode. NOTE: Requires the Standby Control to be enabled.

Requires user role: ADMIN

Value space:

<1..480>

Range: Select a value from 1 to 480 minutes.

Example:

xConfiguration Standby Delay: 10

xConfiguration Standby BootAction

Define the camera position after a restart of the codec.

Requires user role: ADMIN

Value space:

<None/Preset1/Preset2/Preset3/Preset4/Preset5/Preset6/Preset7/Preset8/Preset9/Preset10/Preset11/Preset12/Preset13/Preset14/Preset15/RestoreCameraPosition/DefaultCameraPosition>

None: No action.
Preset1 to Preset15: After a reboot the camera position will be set to the position defined by the selected preset.
RestoreCameraPosition: After a reboot the camera position will be set to the position it had before the last boot.
DefaultCameraPosition: After a reboot the camera position will be set to the factory default position.

Example:

xConfiguration Standby BootAction: DefaultCameraPosition

xConfiguration Standby StandbyAction

Define the camera position when going into standby mode.

Requires user role: ADMIN

Value space:

<None/PrivacyPosition>

None: No action.
PrivacyPosition: Turns the camera to a sideways position for privacy.

Example:

xConfiguration Standby StandbyAction: PrivacyPosition

xConfiguration Standby WakeupAction

Define the camera position when leaving standby mode.

Requires user role: ADMIN

Value space:

<None/Preset1/Preset2/Preset3/Preset4/Preset5/Preset6/Preset7/Preset8/Preset9/Preset10/Preset11/Preset12/Preset13/Preset14/Preset15/RestoreCameraPosition/DefaultCameraPosition>

None: No action.
Preset1 to Preset15: When leaving standby the camera position will be set to the position defined by the selected preset.
RestoreCameraPosition: When leaving standby the camera position will be set to the position it had before entering standby.
DefaultCameraPosition: When leaving standby the camera position will be set to the factory default position.

Example:

xConfiguration Standby WakeupAction: RestoreCameraPosition

The xConfiguration SystemUnit commands

xConfiguration SystemUnit Name

Enter a System Name to define a name of the system unit. If the H.323 Alias ID is configured on the system then this ID will be used instead of the system name. The system name will be displayed:

1) When the codec is acting as an SNMP Agent.

2) Towards a DHCP server.

Requires user role: ADMIN

Value space:

<S: 0, 50>

Format: String with a maximum of 50 characters.

Example:

xConfiguration SystemUnit Name: "Meeting Room"

xConfiguration SystemUnit MenuLanguage

Select the language to be used in the menus on screen.

Requires user role: USER

Value space:

<English/ChineseSimplified/ChineseTraditional/Czech/Danish/Dutch/Finnish/French/German/Hungarian/Italian/Japanese/Korean/Norwegian/Polish/PortugueseBrazilian/Russian/Spanish/SpanishLatin/Swedish/Turkish>

Example:

xConfiguration SystemUnit MenuLanguage: English

xConfiguration SystemUnit ContactInfo Type

Describes which parameter to put in the status field in the upper left corner on the screen display. The information can also be read with the command xStatus SystemUnit ContactInfo.

Requires user role: ADMIN

Value space:

<Auto/None/IPv4/IPv6/H323Id/E164Alias/SipUri/SystemName>

Auto: Shows the address which another system can dial to reach this system, depending on the default call protocol and system registration.
None: Do not show any contact information.
IPv4: Shows the IPv4 address as the contact information.
IPv6: Shows the IPv6 address as the contact information.
H323Id: Shows the H323 ID as the contact information.
E164Alias: Shows the H323 E164 Alias as the contact information.
SipUri: Shows the SIP URI as the contact information.
SystemName: Shows the system name as the contact information.

Example:

xConfiguration SystemUnit ContactInfo Type: Auto

xConfiguration SystemUnit Type

Select whether the video system is for personal use or to be used in a multiuser environment. It is highly recommended not to use the default setting.

Requires user role: ADMIN

Value space:

<Personal/Shared>

Personal: Set to Personal when the system is for personal use.
Shared: Set to Shared when the system is used in a multiuser environment.

Example:

xConfiguration SystemUnit Type: Shared

xConfiguration SystemUnit CallLogging Mode

Set the call logging mode for calls that are received or placed by the system. The call logs may then be viewed via the web interface or using the xHistory command.

Requires user role: ADMIN

Value space:

<On/Off>

On: Enable logging.
Off: Disable logging.

Example:

xConfiguration SystemUnit CallLogging Mode: On

xConfiguration SystemUnit IrSensor

Both the Codec C Series and PrecisionHD camera have IR sensors, and only one of them needs to be enabled at the time. The IR sensor LED is located on the front of the codec and the camera and flickers when an IR signal is received from the remote control.

Requires user role: ADMIN

Value space:

<On/Off/Auto>

On: Enable the IR sensor on the codec.
Off: Disable the IR sensor on the codec.
Auto: The system will automatically disable the IR sensor on the codec if the IR sensor at camera is enabled. Otherwise, the IR sensor on the codec will be enabled.

Example:

xConfiguration SystemUnit IrSensor: Auto

The xConfiguration Time commands

xConfiguration Time Zone

Set the time zone where the system is located, using Windows time zone description format.

Requires user role: USER

Value space:

<GMT-12:00 (International Date Line West)/GMT-11:00 (Midway Island, Samoa)/GMT-10:00 (Hawaii)/GMT-09:00 (Alaska)/GMT-08:00 (Pacific Time (US & Canada); Tijuana)/GMT-07:00 (Arizona)/GMT-07:00 (Mountain Time (US & Canada))/GMT-07:00 (Chihuahua, La Paz, Mazatlan)/GMT-06:00 (Central America)/GMT-06:00 (Saskatchewan)/GMT-06:00 (Guadalajara, Mexico City, Monterrey)/GMT-06:00 (Central Time (US & Canada))/GMT-05:00 (Indiana (East))/GMT-05:00 (Bogota, Lima, Quito)/GMT-05:00 (Eastern Time (US & Canada))/GMT-04:30 (Caracas)/GMT-04:00 (La Paz)/GMT-04:00 (Santiago)/GMT-04:00 (Atlantic Time (Canada))/GMT-03:30 (Newfoundland)/GMT-03:00 (Buenos Aires, Georgetown)/GMT-03:00 (Greenland)/GMT-03:00 (Brasilia)/GMT-02:00 (Mid-Atlantic)/GMT-01:00 (Cape Verde Is.)/GMT-01:00 (Azores)/GMT (Casablanca, Monrovia)/GMT (Coordinated Universal Time)/GMT (Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London)/GMT+01:00 (West Central Africa)/GMT+01:00 (Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna)/GMT+01:00 (Brussels, Copenhagen, Madrid, Paris)/GMT+01:00 (Sarajevo, Skopje, Warsaw, Zagreb)/GMT+01:00 (Belgrade, Bratislava, Budapest, Ljubljana, Prague)/GMT+02:00 (Harare, Pretoria)/GMT+02:00 (Jerusalem)/GMT+02:00 (Athens, Istanbul, Minsk)/GMT+02:00 (Helsinki, Kyiv, Riga, Sofia, Tallinn, Vilnius)/GMT+02:00 (Cairo)/GMT+02:00 (Bucharest)/GMT+03:00 (Nairobi)/GMT+03:00 (Kuwait, Riyadh)/GMT+03:00 (Moscow, St. Petersburg, Volgograd)/GMT+03:00 (Baghdad)/GMT+03:30 (Tehran)/GMT+04:00 (Abu Dhabi, Muscat)/GMT+04:00 (Baku, Tbilisi, Yerevan)/GMT+04:30 (Kabul)/GMT+05:00 (Islamabad, Karachi, Tashkent)/GMT+05:00 (Ekaterinburg)/GMT+05:30 (Chennai, Kolkata, Mumbai, New Delhi)/GMT+05:45 (Kathmandu)/GMT+06:00 (Sri Jayawardenepura)/GMT+06:00 (Astana, Dhaka)/GMT+06:00 (Almaty, Novosibirsk)/GMT+06:30 (Rangoon)/GMT+07:00 (Bangkok, Hanoi, Jakarta)/GMT+07:00 (Krasnoyarsk)/GMT+08:00 (Perth)/GMT+08:00 (Taipei)/GMT+08:00 (Kuala Lumpur, Singapore)/GMT+08:00 (Beijing, Chongqing, Hong Kong, Urumqi)/GMT+08:00 (Irkutsk, Ulaan Bataar)/GMT+09:00 (Osaka, Sapporo, Tokyo)/GMT+09:00 (Seoul)/GMT+09:00 (Yakutsk)/GMT+09:30 (Darwin)/GMT+09:30 (Adelaide)/GMT+10:00 (Guam, Port Moresby)/GMT+10:00 (Brisbane)/GMT+10:00 (Vladivostok)/GMT+10:00 (Hobart)/GMT+10:00 (Canberra, Melbourne, Sydney)/GMT+11:00 (Magadan, Solomon Is., New Caledonia)/GMT+12:00 (Fiji, Kamchatka, Marshall Is.)/GMT+12:00 (Auckland, Wellington)/GMT+13:00 (Nuku alofa)>

Range: Select a time zone from the list time zones. If using a command line interface; watch up for typos.

Example:

xConfiguration Time Zone: "GMT (Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London)"

xConfiguration Time TimeFormat

Set the time format.

Requires user role: USER

Value space:

<24H/12H>

24H: Set the time format to 24 hours.
12H: Set the time format to 12 hours (AM/PM).

Example:

xConfiguration Time TimeFormat: 24H

xConfiguration Time DateFormat

Set the date format.

Requires user role: USER

Value space:

<DD_MM_YY/MM_DD_YY/YY_MM_DD>

DD_MM_YY: The date January 30th 2010 will be displayed: 30.01.10
MM_DD_YY: The date January 30th 2010 will be displayed: 01.30.10
YY_MM_DD: The date January 30th 2010 will be displayed: 10.01.30

Example:

xConfiguration Time DateFormat: DD_MM_YY

The xConfiguration UserInterface commands

xConfiguration UserInterface TouchPanel DefaultPanel

Select whether to display the list of contacts or the list of scheduled meetings on the Touch panel as default.

Requires user role: USER

Value space:

<ContactList/MeetingList>

ContactList: The contact list (favorites, directory and history) will appear as default on the Touch panel.
MeetingList: The list of scheduled meetings will appear as default on the Touch panel.

Example:

xConfiguration UserInterface TouchPanel DefaultPanel: ContactList

The xConfiguration Video commands

xConfiguration Video Input Source [1..5] Name

Enter a name for the video input source.

Requires user role: ADMIN

Value space:

<S: 0, 50>

Format: String with a maximum of 50 characters.

Example:

xConfiguration Video Input Source 1 Name: ""

xConfiguration Video Input Source [1] Connector

Select which video input connector to be active on video input source 1.

Requires user role: ADMIN

Value space:

<HDMI/HDSDI/YPbPr>

HDMI: Select HDMI when you want to use the HDMI 1 as input source 1.
HDSDI: Select HD-SDI when you want to use the HD-SDI 1 as input source 1.
YPbPr: Select YPbPr when you want to use the YPbPr 1 (Component) as input source 1. Connect to the first row of Y, Pb and Pr connectors.

Example:

xConfiguration Video Input Source 1 Connector: HDMI

xConfiguration Video Input Source [2] Connector

Select which video input connector to be active on video input source 2.

Requires user role: ADMIN

Value space:

<HDMI/HDSDI/YPbPr>

HDMI: Select HDMI when you want to use the HDMI 2 as input source 2.
HDSDI: Select HD-SDI when you want to use the HD-SDI 2 as input source 2.
YPbPr: Select YPbPr when you want to use the YPbPr 2 (Component) as input source 2. Connect to the second row of Y, Pb and Pr connectors.

Example:

xConfiguration Video Input Source 2 Connector: HDMI

xConfiguration Video Input Source [3] Connector

Select which video input connector to be active on video input source 3.

Requires user role: ADMIN

Value space:

<HDMI/HDSDI/DVI>

DVI: Select DVI-I when you want to use the DVI-I 3 as input source 3.
HDMI: Select HDMI when you want to use the HDMI 3 as input source 3.
HDSDI: Select HD-SDI when you want to use the HD-SDI 3 as input source 3.

Example:

xConfiguration Video Input Source 3 Connector: DVI

xConfiguration Video Input Source [4] Connector

Select which video input connector to be active on video input source 4.

Requires user role: ADMIN

Value space:

<HDMI/HDSDI>

HDMI: Select HDMI when you want to use the HDMI 4 as input source 4.
HDSDI: Select HD-SDI when you want to use the HD-SDI 4 as input source 4.

Example:

xConfiguration Video Input Source 4 Connector: HDMI

xConfiguration Video Input Source [5] Connector

Select which video input connector to be active on video input source 5.

Requires user role: ADMIN

Value space:

<DVI/Composite/YC>

DVI: Select DVI-I when you want to use the DVI-I 5 as input source 5.
Composite: Select Composite when you want to use Composite as input source 5.
YC: Select YC when you want to use the S-Video (YC) as input source 5. Connect to the two connectors marked Y/Comp and C.

Example:

xConfiguration Video Input Source 5 Connector: DVI

xConfiguration Video Input Source [1..5] Type

Set which type of input source is connected to the video input.

Requires user role: ADMIN

Value space:

<other/camera/PC/DVD/document_camera>

Other: Select Other when some other type of equipment is connected to the selected video input.
Camera: Select Camera when you have a camera connected to the selected video input.
PC: Select PC when you have a PC connected to the selected video input.
DVD: Select DVD when you have a DVD player connected to the selected video input.
Document_Camera: Select Document_Camera when you have a document camera connected to the selected video input.

Example:

xConfiguration Video Input Source 1 Type: PC

xConfiguration Video Input Source [1..5] CameraControl Mode

Set the camera control mode for the camera associated with the video source.

Requires user role: ADMIN

Value space:

<On/Off>

On: Enable camera control.
Off: Disable camera control.

Example:

xConfiguration Video Input Source 1 CameraControl Mode: On

xConfiguration Video Input Source [1..5] CameraControl CameraId

Select the ID of the camera in the Visca chain that is connected to this camera source. The CameraId setting represents the camera's position in the Visca chain.

Requires user role: ADMIN

Value space:

<1..7>

Range: Select the ID of the camera in the Visca chain.

Example:

xConfiguration Video Input Source 1 CameraControl CameraId: 1

xConfiguration Video Input Source [1..5] OptimalDefinition Profile

Adjust how rapidly the system will increase the transmitted resolution when increasing the bandwidth. NOTE: Requires that the Video Input Source Quality is set to Motion.

Normal: Use this setting for normal to poorly lit environment. If the source is a camera with 1920x1080p60, the system will transmit 1920x720p60 at about 2.2Mb/sec and above with this setting set to normal.

Medium: Requires better than normal and consistent lighting and good quality video inputs. If the source is a camera with 1920x1080p60, the system will transmit 1920x720p60 at about 1.4Mb/sec and above with this setting set to medium.

High: Requires good lighting conditions for a good overall experience and good quality video inputs. If the source is a camera with 1920x1080p60, the system will transmit 1920x720p60 at about 1.1Mb/sec and above with this setting set to high.

Requires user role: ADMIN

Value space:

<Normal/Medium/High>

Optimal definition for systems supporting 1080p
Normal: w288p30: 256kbit/s; w448p30: 512kbit/s; w576p30: 768kbit/s; 720p30: 1152kbit/s; 1080p30: 2560kbit/s
Medium: w288p30: 128kbit/s; w448p30: 384kbit/s; w576p30: 512kbit/s; 720p30: 1152kbit/s; 1080p30: 1920kbit/s
High: w288p30: 128kbit/s; w448p30: 256kbit/s; w576p30: 512kbit/s; 720p30: 768kbit/s; 1080p30: 1472kbit/s

Optimal definition for systems supporting 720p60
Normal: w144p60: 128kbit/s; w288p60: 512kbit/s; w448p60: 1152kbit/s; w576p60: 1472kbit/s; 720p60: 2240kbit/s
Medium: w144p60: 128kbit/s; w288p60: 384kbit/s; w448p60: 768kbit/s; w576p60: 1152kbit/s; 720p60: 1920kbit/s
High: w144p60: 128kbit/s; w288p60: 256kbit/s; w448p60: 512kbit/s; w576p60: 768kbit/s; 720p60: 1152kbit/s

Example:

xConfiguration Video Input Source 1 OptimalDefinition Profile: Normal

xConfiguration Video Input Source [1..5] OptimalDefinition Threshold60fps

For each video input, this setting tells the system the lowest resolution where it should transmit 60fps. So for all resolutions lower than this, the maximum transmitted framerate would be 30fps, while above this resolution 60fps would also be possible, if the available bandwidth is adequate.

Requires user role: ADMIN

Value space:

<512_288/768_448/1024_576/1280_720/Never>

512_288: Set the threshold to 512x288.
768_448: Set the threshold to 768x448.
1024_576: Set the threshold to 1024x576.
1280_720: Set the threshold to 1280x720.
Never: Do not set a threshold for transmitting 60fps.

Example:

xConfiguration Video Input Source 1 OptimalDefinition Threshold60fps: 1280_720

xConfiguration Video Input Source [1..5] Quality

When encoding and transmitting video there will be a tradeoff between high resolution and high framerate. For some video sources it is more important to transmit high framerate than high resolution and vice versa. The Quality setting specifies whether to give priority to high frame rate or to high resolution for a given source.

Requires user role: ADMIN

Value space:

<Motion/Sharpness>

Motion: Gives the highest possible framerate. Used when there is a need for higher frame rates, typically when a large number of participants are present or when there is a lot of motion in the picture.
Sharpness: Gives the highest possible resolution. Used when you want the highest quality of detailed images and graphics.

Example:

xConfiguration Video Input Source 1 Quality: Motion

xConfiguration Video DefaultPresentationSource

Define which video input source shall be used as the default presentation source (when you press the Presentation key on the remote control). The input source is configured to a video input connector. See the Video Input Matrix table at the back of the codec and the description of the Video Input Matrix in the Interfaces section.

Requires user role: USER

Value space:

<1..5>

Range: Select the video source to be used as the presentation source.

Example:

xConfiguration Video DefaultPresentationSource: 3

xConfiguration Video Input DVI [3, 5] Type

The official DVI standard supports both digital and analog signals. In most cases the default AutoDetect setting can detect whether the signal is analog RGB or digital. However, in some rare cases when DVI-I cables are used (these cables can carry both the analog and digital signals) the auto detection fails. This setting makes it possible to override the AutoDetect and select the correct DVI video input. This setting should also be used if the video input is an analog component (YPbPr) type signal. This is used by some cameras (Sony EVI-HD1) and DVD/Blu-ray players. Since it is not possible to auto detect the difference between AnalogRGB and AnalogYPbPr, the AnalogYPbPr setting must be selected.

Requires user role: ADMIN

Value space:

<AutoDetect/Digital/AnalogRGB/AnalogYPbPr>

AutoDetect: Set to AutoDetect to automatically detect if the signal is analog RGB or digital.
Digital: Set to Digital to force the DVI video input to Digital when using DVI-I cables with both analog and digital pins and AutoDetect fails.
AnalogRGB: Set to AnalogRGB to force the DVI video input to AnalogRGB when using DVI-I cables with both analog and digital pins and AutoDetect fails.
AnalogYPbPr: Set to AnalogYPbPr to force the DVI video input to AnalogYPbPr, as the component (YPbPr) signal cannot be auto detected.

Example:

xConfiguration Video Input DVI 3 Type: AutoDetect

xConfiguration Video Layout Scaling

Define how the system shall adjust the aspect ratio for images or frames when there is a difference between the image and the frame it is to be placed in.

Requires user role: ADMIN

Value space:

<On/Off>

On: Let the system automatically adjust aspect ratio.
Off: No adjustment of the aspect ratio.

Example:

xConfiguration Video Layout Scaling: On

xConfiguration Video Layout ScaleToFrame

Define what to do if the aspect ratio of a video input source doesn't match the aspect ratio of the corresponding image frame in a composition. For example if you have a 4:3 input source (like XGA) to be displayed on a 16:9 output (like HD720).

Requires user role: ADMIN

Value space:

<Manual/MaintainAspectRatio/StretchToFit>

Manual: If the difference in aspect ratio between the video input source and the target image frame is less than the ScaleToFrameThreshold configuration (in percent), the image is stretched to fit. If not, the system will maintain the original aspect ratio.
MaintainAspectRatio: Will maintain the aspect ratio of the input source, and fill in black in the rest of the frame (letter boxing or pillar boxing).
StretchToFit: Will stretch (horizontally or vertically) the input source to fit into the image frame. NOTE: The general limitation is that you cannot upscale in one direction and at the same time downscale in the other direction. In such situations the codec will apply letterboxing.

Example:

xConfiguration Video Layout ScaleToFrame: MaintainAspectRatio

xConfiguration Video Layout ScaleToFrameThreshold

Only applicable if the ScaleToFrame configuration is set to manual. If the difference in aspect ratio between the video input source and the target image frame is less than the ScaleToFrameThreshold configuration (in percent), the image is stretched to fit. If not, the system will maintain the original aspect ratio.

Requires user role: ADMIN

Value space:

<0..100>

Range: Select a value from 0 to 100 percent.

Example:

xConfiguration Video Layout ScaleToFrameThreshold: 5

xConfiguration Video SelfviewPosition

Select where the small selfview PiP (Picture-in-Picture) will appear on screen.

Requires user role: ADMIN

Value space:

<UpperLeft/UpperRight/LowerLeft/LowerRight/CenterRight>

UpperLeft: The selfview PiP will appear in the upper left corner of the screen.
UpperRight: The selfview PiP will appear in the upper right corner of the screen.
LowerLeft: The selfview PiP will appear in the lower left corner of the screen.
LowerRight: The selfview PiP will appear in the lower right corner of the screen.
CenterRight: The selfview PiP will appear in to the right side of the screen, in center.

Example:

xConfiguration Video SelfviewPosition: LowerRight

xConfiguration Video Layout LocalLayoutFamily

Select which video layout family to be used locally.

Requires user role: ADMIN

Value space:

<Auto/FullScreen/Equal/PresentationSmallSpeaker/PresentationLargeSpeaker>

Auto: The default layout family, as given by the layout database, will be used as the local layout. For more information about the layout database, see the command: xCommand Video Layout LoadDb.
FullScreen: The FullScreen layout family will be used as the local layout.
Equal: The Equal layout family will be used as the local layout.
PresentationSmallSpeaker: The PresentationSmallSpeaker layout family will be used as the local layout.
PresentationLargeSpeaker: The PresentationLargeSpeaker layout family will be used as the local layout.

Example:

xConfiguration Video Layout LocalLayoutFamily: Auto

xConfiguration Video Layout RemoteLayoutFamily

Select which video layout family to be used for the remote participants.

Requires user role: ADMIN

Value space:

<Auto/FullScreen/Equal/PresentationSmallSpeaker/PresentationLargeSpeaker>

Auto: The default layout family, as given by the local layout database, will be used as the remote layout. For more information about the layout database, see the command: xCommand Video Layout LoadDb.
FullScreen: The FullScreen layout family will be used as the remote layout.
Equal: The Equal layout family will be used as the remote layout.
PresentationSmallSpeaker: The PresentationSmallSpeaker layout family will be used as the remote layout.
PresentationLargeSpeaker: The PresentationLargeSpeaker layout family will be used as the remote layout.

Example:

xConfiguration Video Layout RemoteLayoutFamily: Auto

xConfiguration Video MainVideoSource

Define which video input source shall be used as the main video source.

Requires user role: USER

Value space:

<1..5>

Range: Select the source to be used as the main video source.

Example:

xConfiguration Video MainVideoSource: 1

xConfiguration Video Monitors

Set the monitor layout mode.

Requires user role: ADMIN

Value space:

<Single/Dual/DualPresentationOnly/Quadruple>

Single: The same layout is shown on all monitors.
Dual: The layout is distributed on two monitors.
DualPresentationOnly: All participants in the call will be shown on the first monitor, while the presentation (if any) will be shown on the second monitor.
Quadruple: The layout is distributed on four monitors, so that each remote participant and the presentation will be shown on separate monitors

Example:

xConfiguration Video Monitors: Single

xConfiguration Video OSD Mode

The Video OSD (On Screen Display) Mode lets you define if information and icons should be displayed on screen.

Requires user role: ADMIN

Value space:

<On/Off>

On: Display the on screen menus, icons and indicators.
Off: Hide the on screen menus, icons and indicators.

Example:

xConfiguration Video OSD Mode: On

xConfiguration Video OSD AutoSelectPresentationSource

Determine if the presentation source should be automatically selected.

Requires user role: ADMIN

Value space:

<On/Off>

On: Enable automatic selection of the presentation source.
Off: Disable automatic selection of the presentation source.

Example:

xConfiguration Video OSD AutoSelectPresentationSource: Off

xConfiguration Video OSD TodaysBookings

This setting can be used to display the systems bookings for today on the main OSD menu. This requires that the system is bookable by an external booking system, like Cisco TelePresence Management Suite (TMS).

Requires user role: ADMIN

Value space:

<On/Off>

On: Displays information about this systems bookings on screen.
Off: Do not display todays bookings.

Example:

xConfiguration Video OSD TodaysBookings: Off

xConfiguration Video OSD MyContactsExpanded

Set how the local contacts will be displayed in the phone book dialog in the OSD (On Screen Display).

Requires user role: ADMIN

Value space:

<On/Off>

On: The local contacts in the phone book will be shown in the top level of the phonebook dialog.
Off: The local contacts will be placed in a separate folder called MyContacts in the phonebook dialog.

Example:

xConfiguration Video OSD MyContactsExpanded: Off

xConfiguration Video OSD Output

The Video OSD (On Screen Display) Output lets you define which monitor should display the on screen menus, information and icons. By default the OSD is sent to the monitor connected to the Video OSD Output 1. If you cannot see the OSD on screen, then you must re-configure the OSD Output. You can do this by entering a key sequence on the remote control, from the web interface, or by a command line interface.

Using the remote control: Press the Disconnect key followed by: * # * # 0 x # (where x is output 1 to 4).

Using the web interface: Open a web browser and enter the IP address of the codec. Open the Advanced Configuration menu and navigate to Video OSD Output and select the video output.

Using a command line interface: Open a command line interface and connect to the codec (if in doubt of how to do this, see the API Guide for the codec). Enter the command: xConfiguration Video OSD Output [1..4] (select the OSD Output)

Requires user role: ADMIN

Value space:

<1..4>

Range: Select 1 for HDMI 1 output, select 2 for DVI-I 2 output, select 3 for HDMI 3 output, or select 4 for DVI-I 4 output.

Example:

xConfiguration Video OSD Output: 1

xConfiguration Video OSD InputMethod InputLanguage

The codec can be enabled for Cyrillic input characters in the menus on screen. NOTE: Requires that xConfiguration Video OSD inputMethod Cyrillic is set to On.

Requires user role: ADMIN

Value space:

<Latin/Cyrillic>

Latin: Latin characters can be entered when using the remote control (default).
Cyrillic: Cyrillic characters can be entered using the remote control. NOTE: Requires a Cisco TelePresence Remote Control with Cyrillic fonts.

Example:

xConfiguration Video OSD InputMethod InputLanguage: Latin

xConfiguration Video OSD InputMethod Cyrillic

Set the Cyrillic mode for the menu input language in the menus on screen.

Requires user role: ADMIN

Value space:

<On/Off>

On: Cyrillic mode is available as a menu input language in the menus on screen. This will enable the setting xConfiguration Video OSD InputMethod InputLanguage.
Off: Cyrillic mode is NOT available as a menu input language in the menus on screen.

Example:

xConfiguration Video OSD InputMethod Cyrillic: Off

xConfiguration Video OSD LoginRequired

Determine if the system should require the user to login before accessing the On Screen Display (OSD). If enabled, the user must enter his username and his PIN. After the user has logged in he can only execute to the configurations changes and commands allowed by his Role.

Requires user role: ADMIN

Value space:

<On/Off>

On: The user must log in to access the On Screen Display (OSD).
Off: No login to the OSD is required.

Example:

xConfiguration Video OSD LoginRequired: Off

xConfiguration Video AllowWebSnapshots

Allow or disallow that snapshots captured by the video input main source can be displayed in the web interface Call Control page.

NOTE: This feature is disabled by default, and must be enabled from the On Screen Display (OSD), from a directly connected Touch controller, or when connected directly to the serial port (COM 1 port) on the codec.

Requires user role: ADMIN

Value space:

<On/Off>

On: If set to on, a web snapshot can be generated and displayed on the web interface.
Off: The generation of web snapshots is not allowed.

Example:

xConfiguration Video AllowWebSnapshots: Off

xConfiguration Video Output HDMI [1, 3] CEC Mode

The HDMI outputs support Consumer Electronics Control (CEC). When set to on (default is off), and the monitor connected to the HDMI output is CEC compatible and CEC is configured, the system will use CEC to set the monitor in standby when the system enters standby. Likewise the system will wake up the monitor when the system wakes up from standby. Please note that the different manufacturers uses different marketing names for CEC: Anynet+ (Samsung); Aquos Link (Sharp); BRAVIA Sync (Sony); HDMI-CEC (Hitachi); Kuro Link (Pioneer); CE-Link and Regza Link (Toshiba); RIHD (Onkyo); SimpLink (LG); HDAVI Control, EZ-Sync, VIERA Link (Panasonic); EasyLink (Philips); and NetCommand for HDMI (Mitsubishi).

Requires user role: ADMIN

Value space:

<On/Off>

On: Enable CEC control.
Off: Disable CEC control.

Example:

xConfiguration Video Output HDMI 1 CEC Mode: Off

xConfiguration Video Output HDMI [1, 3] MonitorRole

The HDMI monitor role describes what video stream will be shown on the monitor connected to the video output HDMI connector. Applicable only if the monitor configuration is set to dual or quadruple.

Requires user role: ADMIN

Value space:

<First/Second/PresentationOnly/Third/Fourth>

First: Show main video stream.
Second: Show presentation video stream if active, or other participants.
PresentationOnly: Show presentation video stream if active, and nothing else.
Third: Use for remote participants (only for quadruple monitor setup).
Fourth: Use for remote participants (only for quadruple monitor setup).

Example:

xConfiguration Video Output HDMI 1 MonitorRole: First

xConfiguration Video Output HDMI [1, 3] OverscanLevel

Some TVs or other monitors may not display the whole image sent out on the systems video output, but cuts the outer parts of the image. In this case this setting can be used to let the system not use the outer parts of video resolution. Both the video and the OSD menu will be scaled in this case.

Requires user role: ADMIN

Value space:

<Medium/High/None>

Medium: The system will not use the outer 3% of the output resolution.
High: The system will not use the outer 6% of the output resolution
None: The system will use all of the output resolution.

Example:

xConfiguration Video Output HDMI 1 OverscanLevel: None

xConfiguration Video Output HDMI [1, 3] Resolution

Select the preferred resolution for the monitor connected to the video output HDMI connector. This will force the resolution on the monitor.

Requires user role: ADMIN

Value space:

<Auto/640_480_60/800_600_60/1024_768_60/1280_1024_60/1280_720_50/1280_720_60/1920_1080_50/1920_1080_60/1280_768_60/1360_768_60/1366_768_60/1600_1200_60/1920_1200_60>

Auto: The system will automatically try to set the optimal resolution based on negotiation with the connected monitor.
Range: 640x480@60p, 800x600@60p, 1024x768@60p, 1280x1024@60p, 1280x720@50p, 1280x720@60p, 1920x1080@50p, 1920x1080@60p, 1280x768@60p, 1360x768@60p, 1366x768@60p, 1600x1200@60p, 1920x1200@60p

Example:

xConfiguration Video Output HDMI 1 Resolution: 1920_1080_60

xConfiguration Video Output DVI [2, 4] MonitorRole

The DVI monitor role describes what video stream will be shown on the monitor connected to the video output DVI-I connector. Applicable only if the monitor configuration is set to dual or quadruple.

Requires user role: ADMIN

Value space:

<First/Second/PresentationOnly/Third/Fourth>

First: Show main video stream.
Second: Show presentation video stream if active, or other participants.
PresentationOnly: Show presentation video stream if active, and nothing else.
Third: Use for remote participants (only for quadruple monitor setup).
Fourth: Use for remote participants (only for quadruple monitor setup).

Example:

xConfiguration Video Output DVI 4 MonitorRole: First

xConfiguration Video Output DVI [2, 4] OverscanLevel

Some TVs or other monitors may not display the whole image sent out on the systems video output, but cuts the outer parts of the image. In this case this setting can be used to let the system not use the outer parts of video resolution. Both the video and the OSD menu will be scaled in this case.

Requires user role: ADMIN

Value space:

<Medium/High/None>

Medium: The system will not use the outer 3% of the output resolution.
High: The system will not use the outer 6% of the output resolution
None: The system will use all of the output resolution.

Example:

xConfiguration Video Output DVI 2 OverscanLevel: None

xConfiguration Video Output DVI [2, 4] Resolution

Select the preferred resolution for the monitor connected to the video output DVI-I connector. This will force the resolution on the monitor.

Requires user role: ADMIN

Value space:

<Auto/640_480_60/800_600_60/1024_768_60/1280_1024_60/1280_720_50/1280_720_60/1920_1080_50/1920_1080_60/1280_768_60/1360_768_60/1366_768_60/1600_1200_60/1920_1200_60>

Auto: The system will automatically try to set the optimal resolution based on negotiation with the connected monitor.
Range: 640x480@60p, 800x600@60p, 1024x768@60p, 1280x1024@60p, 1280x720@50p, 1280x720@60p, 1920x1080@50p, 1920x1080@60p, 1280x768@60p, 1360x768@60p, 1366x768@60p, 1600x1200@60p, 1920x1200@60p

Example:

xConfiguration Video Output DVI 2 Resolution: 1920_1080_60

xConfiguration Video Output Composite [5] MonitorRole

The Composite monitor role describes what video stream will be shown on the monitor connected to the video output Composite connector. Applicable only if the monitor configuration is set to dual or quadruple.

Requires user role: ADMIN

Value space:

<First/Second/PresentationOnly/Third/Fourth>

First: Show main video stream.
Second: Show presentation video stream if active, or other participants.
PresentationOnly: Show presentation video stream if active, and nothing else.
Third: Use for remote participants (only for quadruple monitor setup).
Fourth: Use for remote participants (only for quadruple monitor setup).

Example:

xConfiguration Video Output Composite 5 MonitorRole: First

xConfiguration Video Output Composite [5] OverscanLevel

Some TVs or other monitors may not display the whole image sent out on the systems video output, but cuts the outer parts of the image. In this case this setting can be used to let the system not use the outer parts of video resolution. Both the video and the OSD menu will be scaled in this case.

Requires user role: ADMIN

Value space:

<Medium/High/None>

Medium: The system will not use the outer 3% of the output resolution.
High: The system will not use the outer 6% of the output resolution
None: The system will use all of the output resolution.

Example:

xConfiguration Video Output Composite 5 OverscanLevel: None

xConfiguration Video Output Composite [5] Resolution

Select the preferred resolution for the monitor connected to the video output Composite connector. This will force the resolution on the monitor.

Requires user role: ADMIN

Value space:

<PAL/NTSC>

Range: PAL, NTSC

Example:

xConfiguration Video Output Composite 5 Resolution: NTSC

xConfiguration Video Selfview

Determine if the main video source (selfview) shall be displayed on screen.

Requires user role: USER

Value space:

<On/Off>

On: Display selfview on screen.
Off: Do not display selfview on screen.

Example:

xConfiguration Video Selfview: On

xConfiguration Video WallPaper

Determine if a background picture should be displayed on screen when idle.

Requires user role: USER

Value space:

<None/Growing/Summersky/Custom/Waves>

None: No wallpaper will be displayed on screen.
Summersky, Growing, Waves: Select one of the predefined wallpapers to be displayed on screen.
Custom: The custom wallpaper must be uploaded to the codec from the web interface before selecting Custom. The maximum supported resolution is 1920x1280.
1) On the video system: Find the IP address of the codec. Open the menu on screen and go to Home > Settings > System information to find the IP Address.
2) On your computer: Open a web browser and enter the IP address of the codec. Select "Wallpaper" from the menu, browse for the file, and press the "Upload" button.
3) On the video system: Open the menu on screen and go to Home > Settings > Wallpaper > Custom. Give it a few seconds to display the new picture. If the picture does not show, toggle once between "None" and "Custom" wallpaper to make the change take effect.

Example:

xConfiguration Video Wallpaper: Summersky

The xConfiguration Experimental commands

The Experimental settings are beta preview features and can be used 'as is'. They are not fully documented. NOTE: The Experimental settings are likely to change without further notice.

xConfiguration Experimental Audio Panning Mode

NOTE: This Experimental command can be used 'as is' and will not be further documented. The Experimental settings WILL change.

Requires user role: ADMIN

Value space:

<Off/Auto>

Example:

xConfiguration Experimental Audio Panning Mode: Off

xConfiguration Experimental Audio Panning MaxAngle

NOTE: This Experimental command can be used 'as is' and will not be further documented. The Experimental settings WILL change.

Requires user role: ADMIN

Value space:

<0..90>

Example:

xConfiguration Experimental Audio Panning MaxAngle: 0

xConfiguration Experimental Audio Panning MonitorLeft

NOTE: This Experimental command can be used 'as is' and will not be further documented. The Experimental settings WILL change.

Requires user role: ADMIN

Value space:

<1/2/3/4/5>

Example:

xConfiguration Experimental Audio Panning MonitorLeft: 1

xConfiguration Experimental Audio Panning MonitorRight

NOTE: This Experimental command can be used 'as is' and will not be further documented. The Experimental settings WILL change.

Requires user role: ADMIN

Value space:

<1/2/3/4/5>

Example:

xConfiguration Experimental Audio Panning MonitorRight: 1

xConfiguration Experimental Audio EcReferenceDelay

NOTE: This Experimental command can be used 'as is' and will not be further documented. The Experimental settings WILL change.

Requires user role: ADMIN

Value space:

<0..300>

Example:

xConfiguration Experimental Audio EcReferenceDelay: 0

xConfiguration Experimental Audio Input Microphone [1..8] EchoControl HighPassFilter

NOTE: This Experimental command can be used 'as is' and will not be further documented. The Experimental settings WILL change.

Requires user role: ADMIN

Value space:

<On/Off>

Example:

xConfiguration Experimental Audio Input Microphone 1 EchoControl HighPassFilter: Off

xConfiguration Experimental Audio Input Microphone [1..8] EchoControl ResidualEchoMasking

NOTE: This Experimental command can be used 'as is' and will not be further documented. The Experimental settings WILL change.

Requires user role: ADMIN

Value space:

<Normal/Aggressive>

Example:

xConfiguration Experimental Audio Input Microphone 1 EchoControl ResidualEchoMasking: Normal

xConfiguration Experimental Audio Input Microphone [1..8] Channel

NOTE: This Experimental command can be used 'as is' and will not be further documented. The Experimental settings WILL change.

Define whether the microphone connector is a mono signal or part of a multichannel signal.

Requires user role: ADMIN

Value space:

<Left/Right/Mono>

Left: The microphone signal is the left channel of a stereo signal.
Right: The microphone signal is the right channel of a stereo signal.
Mono: The microphone signal is a mono signal.

Example:

xConfiguration Experimental Audio Input Microphone 1 Channel: Mono

xConfiguration Experimental Audio MicrophoneReinforcement Gain

NOTE: This Experimental command can be used 'as is' and will not be further documented. The Experimental settings WILL change.

Microphone reinforcement is local amplification of one or several input connectors, directly to one or several output connectors, with minimum delay.

For software version TC4.0: Microphone reinforcement should not be enabled on a codec that is also configured using the Audio Console application.

This setting configures the gain of this path, from -53 dB to +15 dB. The value -54 corresponds to mute.

Requires user role: ADMIN

Value space:

<-54..15>

Example:

xConfiguration Experimental Audio MicrophoneReinforcement Gain: -19

xConfiguration Experimental Audio MicrophoneReinforcement AGC

NOTE: This Experimental command can be used 'as is' and will not be further documented. The Experimental settings WILL change.

Microphone reinforcement is local amplification of one or several input connectors, directly to one or several output connectors, with minimum delay.

For software version TC4.0: Microphone reinforcement should not be enabled on a codec that is also configured using the Audio Console application.

This setting controls an AGC on the mix of all input connectors attached to the Microphone reinforcement.

Requires user role: ADMIN

Value space:

<On/Off>

Example:

xConfiguration Experimental Audio MicrophoneReinforcement AGC: Off

xConfiguration Experimental Audio MicrophoneReinforcement Input Microphone [1..8] Mode

NOTE: This Experimental command can be used 'as is' and will not be further documented. The Experimental settings WILL change.

Microphone reinforcement is local amplification of one or several input connectors, directly to one or several output connectors, with minimum delay.

For software version TC4.0: Microphone reinforcement should not be enabled on a codec that is also configured using the Audio Console application.

Configuring this setting to On for a microphone, means to attach it to the microphone reinforcement for local amplification. This is done in parallel to the microphone's existing connections, and will not affect any of these.

Requires user role: ADMIN

Value space:

<On/Off>

Example:

xConfiguration Experimental Audio MicrophoneReinforcement Input Microphone 1 Mode: On

xConfiguration Experimental Audio MicrophoneReinforcement Output Line [1..6] Mode

NOTE: This Experimental command can be used 'as is' and will not be further documented. The Experimental settings WILL change.

Microphone reinforcement is local amplification of one or several input connectors, directly to one or several output connectors, with minimum delay.

For software version TC4.0: Microphone reinforcement should not be enabled on a codec that is also configured using the Audio Console application.

Configuring this setting to On for an output line, means to attach that output connector to the microphone reinforcement for local amplification. If the output connector already is attached to a Local Output, it will first be detached from that before being attached to the Microphone reinforcement. When this setting is On, the output connector cannot be attached to any Local Output.

Requires user role: ADMIN

Value space:

<On/Off>

Example:

xConfiguration Experimental Audio MicrophoneReinforcement Output Line 1 Mode: On

xConfiguration Experimental AudioTracking Camera [1..7] Mode

NOTE: This Experimental command can be used 'as is' and will not be further documented. The Experimental settings WILL change.

Requires user role: ADMIN

Value space:

<On/Off>

Example:

xConfiguration Experimental AudioTracking Camera 1 Mode: Off

xConfiguration Experimental BrightnessGradient Camera [1..7] Mode

NOTE: The Experimental settings can be used 'as is' and will not be further documented. The Experimental settings WILL change.

NOTE: Applies to Cisco TelePresence T1/T3. This settings can be configured from the command line interface, and not from the menu.

Requires user role: ADMIN

Value space:

<On/Off>

On: Enable row dependent digital gain.
Off: Disable row dependent digital gain.

Example:

xConfiguration Experimental BrightnessGradient Camera 1 Mode: Off

xConfiguration Experimental BrightnessGradient Camera [1..7] Level

NOTE: The Experimental settings can be used 'as is' and will not be further documented. The Experimental settings WILL change.

NOTE: Applies to Cisco TelePresence T1/T3. This settings can be configured from the command line interface, and not from the menu. Set the camera brightness gradient level to control the row dependent digital gain for the top row of the image. The gain gradient is applied so that intermediate rows have gains that are determined by linear interpolation of the top row gain and the gain for the bottom row. A gain of 1.0x is always applied to the bottom row of the image.

Requires user role: ADMIN

Value space:

<10..39>

Range: The range 10 to 39 corresponds to gains in the range 1.0x to 3.9x.

Example:

xConfiguration Experimental BrightnessGradient Camera 1 Level: 10

xConfiguration Experimental CapsetFilter

NOTE: This Experimental command can be used 'as is' and will not be further documented. The Experimental settings WILL change.

Requires user role: ADMIN

Value space:

<S: 0, 100>

Example:

xConfiguration Experimental CapsetFilter: ""

xConfiguration Experimental CapsetReduction

NOTE: This Experimental command can be used 'as is' and will not be further documented. The Experimental settings WILL change.

Requires user role: ADMIN

Value space:

<Auto/Reduced>

Example:

xConfiguration Experimental CapsetReduction: Auto

xConfiguration Experimental Conference [1..1] PacketLossResilience ForwardErrorCorrection

NOTE: This Experimental command can be used 'as is' and will not be further documented. The Experimental settings WILL change.

Will enable ForwardErrorCorrection (RFC5109) mechanism as part of the PacketLossResilience mechanism. Default value is On.

On: Forward error correction will be used as part of the PacketLossResilience mechanism.

Off: Forward error correction will NOT be used as part of the PacketLossResilience mechanism.

Requires user role: ADMIN

Value space:

<On/Off>

Example:

xConfiguration Experimental Conference 1 PacketLossResilience ForwardErrorCorrection: On

xConfiguration Experimental Conference [1..1] PacketLossResilience RateAdaption

NOTE: This Experimental command can be used 'as is' and will not be further documented. The Experimental settings WILL change.

Will use the a RateAdaption algorithm adapted to the PacketLossResilience mechanism. Default value is On.

Requires user role: ADMIN

Value space:

<On/Off>

On: RateAdaption will be used as part of the PacketLossResilience mechanism.
Off: RateAdaption will NOT be used as part of the PacketLossResilience mechanism.

Example:

xConfiguration Experimental Conference 1 PacketLossResilience RateAdaption: On

xConfiguration Experimental Conference [1..1] ReceiverBasedDownspeeding

NOTE: This Experimental command can be used 'as is' and will not be further documented. The Experimental settings WILL change.

Requires user role: ADMIN

Value space:

<On/Off>

Example:

xConfiguration Experimental Conference 1 ReceiverBasedDownspeeding: Off

xConfiguration Experimental CustomSoftbuttons HoldResume

NOTE: This Experimental command can be used 'as is' and will not be further documented. The Experimental settings WILL change.

This configuration is used to enable Call Hold and Resume in the OSD. Note that Call Hold and Resume will be available even if this setting is set to Off, if Multiway is configured.

Requires user role: ADMIN

Value space:

<Off/On>

Off: Call Hold and Resume is not available (unless Multiway is configured).
On: Call Hold/Resume is available while the system is in a call. It will be available on softbuttons, and when receiving incoming calls the user will have the option of holding any current calls while accepting the new call.

Example:

xConfiguration Experimental CustomSoftbuttons HoldResume: Off

xConfiguration Experimental CustomSoftbuttons State [1..2] Softbutton [1..5] Type

NOTE: This Experimental command can be used 'as is' and will not be further documented. The Experimental settings WILL change.

Requires user role: ADMIN

Value space:

<NotSet/MainSource/PresentationSource/CameraPreset/Actions/SpeedDial>

Example:

xConfiguration Experimental CustomSoftbuttons State 1 Softbutton 1 Type: NotSet

xConfiguration Experimental CustomSoftbuttons State [1..2] Softbutton [1..5] Value

NOTE: This Experimental command can be used 'as is' and will not be further documented. The Experimental settings WILL change.

Requires user role: ADMIN

Value space:

<S: 0, 255>

Example:

xConfiguration Experimental CustomSoftbuttons State 1 Softbutton 1 Value: ""

xConfiguration Experimental Enable1080p60

NOTE: This Experimental command can be used 'as is' and will not be further documented. The Experimental settings WILL change.

Requires user role: ADMIN

Value space:

<On/Off>

Example:

xConfiguration Experimental Enable1080p60: Off

xConfiguration Experimental NetworkServices UPnP Mode

NOTE: This Experimental command can be used 'as is' and will not be further documented. The Experimental settings WILL change.

Requires user role: ADMIN

Value space:

<On/Off>

Example:

xConfiguration Experimental NetworkServices UPnP Mode: Off

xConfiguration Experimental NetworkServices UPnP Timeout

NOTE: This Experimental command can be used 'as is' and will not be further documented. The Experimental settings WILL change.

Requires user role: ADMIN

Value space:

<0..3600>

Example:

xConfiguration Experimental NetworkServices UPnP Timeout: 0

xConfiguration Experimental CTMSSupport Mode

NOTE: This Experimental command can be used 'as is' and will not be further documented. The Experimental settings WILL change.

This configuration tells whether CTMS (Cisco TelePresence Multipoint Switch) is supported or not.

Requires user role: ADMIN

Value space:

<Off/On>

Off: CTMS is not supported.
On: CTMS is supported.

Example:

xConfiguration Experimental CTMSSupport Mode: On

xConfiguration Experimental PacketOverloadHandling WhenDetected

NOTE: This Experimental command can be used 'as is' and will not be further documented. The Experimental settings WILL change.

Requires user role: ADMIN

Value space:

<Off/CallRate2256/CallRate768/ReduceTo576p/ReduceTo360p/Unencrypted/Disconnect>

Example:

xConfiguration Experimental PacketOverloadHandling WhenDetected: Off

xConfiguration Experimental SystemUnit MenuType

NOTE: This Experimental command can be used 'as is' and will not be further documented. The Experimental settings WILL change.

Requires user role: ADMIN

Value space:

<Indicators/Full>

Example:

xConfiguration Experimental SystemUnit MenuType: Full

xConfiguration Experimental SystemUnit SoftwareUpgrade RequireAuthentication

NOTE: This Experimental command can be used 'as is' and will not be further documented. The Experimental settings WILL change.

Requires user role: ADMIN

Value space:

<On/Off>

Example:

xConfiguration Experimental SystemUnit SoftwareUpgrade RequireAuthentication: Off

xConfiguration Experimental SystemUnit CrashReporting Mode

NOTE: This Experimental command can be used 'as is' and will not be further documented. The Experimental settings WILL change.

Requires user role: ADMIN

Value space:

<Off/On>

Example:

xConfiguration Experimental SystemUnit CrashReporting Mode: Off

xConfiguration Experimental SystemUnit CrashReporting URI

NOTE: This Experimental command can be used 'as is' and will not be further documented. The Experimental settings WILL change.

Requires user role: ADMIN

Value space:

<S: 0, 255>

Example:

xConfiguration Experimental SystemUnit CrashReporting URI: ""

xConfiguration Experimental SystemUnit Controller Address

NOTE: This Experimental command can be used 'as is' and will not be further documented. The Experimental settings WILL change.

Requires user role: ADMIN

Value space:

<S: 0, 255>

Example:

xConfiguration Experimental SystemUnit Controller Address: ""