TANDBERG 3000 MXP & 6000 MXP

REFERENCE GUIDE FOR SYSTEM INTEGRATORS

• Designed for custom integrations

Codec
• 19” mountable codecs
• Expandability for future applications
• Total management via serial port, embedded web
server, SNMP, Telnet, XML, HTTP / HTTPS, FTP and
on screen menu

3000 • Best possible call for each MultiSite participant with

rate matching and transcoding

6000 • URI dialling

• H.323, H.320 & SIP support
MXP • TANDBERG Expressway™ Technology
• Protection against network interruptions in point-
to-point and multipoint calls with automatic
downspeeding and IPLR

• Standards-based embedded encryption

(AES & DES)

REFERENCE

FOR SYSTEM
INTEGRATORS
Software version F8.X
D 13887.09
APRIL 2009
 Finding the Information You Need
We recommend that you check out the
TANDBERG web site regularly for updated
Thank you for choosing TANDBERG!
versions of this manual: The TANDBERG Codec 3000 MXP and Codec 6000 MXP
http://www.tandberg.com/docs have been designed to provide you with many years of
safe, reliable operation.
This section of the User Guides contains an overview of
what’s new in this version and the Table of Contents.
Our objective with this Reference User Guide for System
Integrators has been to address your goals and needs.
Please let us know how well we succeeded!
Finding the Information You Need
What’s New in This Version? TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

There are a number of new and altered instructions available in Camera [1..13] Whitebalance Mode: <Auto/Manual/Indoor/Out- uses of the TANDBERG/Codian MCU software Ver. 3.0 or higher.
version F8.0 door/Gain> Set to MultiSite if you have the optional feature MultiSite installed.
Altered. The camera picture control white balance setting has Set to Off if none of the above features are being used.
Software release note been enhanced with Indoor and Outdoor settings in addition to the
Auto and Manual settings. Multipoint MulitwayURI <S: 0, 60>
The F8 software release note is found at the TANDBERG web
site. Go to: http://www.tandberg.com/support/documentation. New in version F8. Specify the Multiway URI. When calling
php?p=Upgrades_and_Diagnostics Camera [1..13] Whitebalance Gain Red: <0..255> Multiway on SIP the SIP prefix must be added to the URI for the
New in version F8. The camera picture control white balance set- endpoint who initiates the Multiway call.
ting has been enhanced with a new Red Gain setting.
Multipoint MulitwayMultiprotocol <On/Off>
Configuration Commands Camera [1..13] Whitebalance Gain Blue: <0..255> New in version F8. Enable/disable the Multiway multi protocol.
New in version F8. The camera picture control white balance set-
Audio HearingImpaired Mode: <On/Off> ting has been enhanced with a new Blue Gain setting. Multipoint MulitwayStartupPeriod <0..21>
New in version F8. If set to On the Hearing Impaired Mode New in version F8. Specify the startup period (in seconds) for the
reduces the delay on audio output 3 from 100 ms to 23 ms, CameraReverseControl: <On/Off> Multiway call.
allowing an assisted listening device (ALD) to be installed in New in version F8. Reverse the local camera control, allowing
conjunction with this output and still maintain a high level of lip the camera to more naturally mimic the directional arrows of the OSD Menu Language: <English/German/Norwegian/French/Swed-
synchronization. remote control. ish/Italian/Portuguese/Japanese/Chinese/TraditionalChinese/
Russian/Spanish/Korean/Finnish/Thai/Arabic/Polish/Czech/
Audio Delay AUX: <On/Off> Conference VideoFormatCP: <16:9/4:3> Hungarian/Turkish/Danish/Romanian/Welsh>
New in version F8. The audio delay on AUX can be enabled/dis- New in version F8. As an enhancement to the Continuous Altered. The menu language has been enhanced with more lan-
abled. Presence (CP) layouts already supported by the MXP endpoints, guages: Polish, Czech, Hungarian, Turkish, Romanian and Welsh.
this version includes support for wide CP layouts, transmitted in
Audio Delay VCR: <On/Off> w576p (1024x576) in both the 4-split and 5+1-split video layout OSD Menu InputEditor Language: <Off/Japanese/Chinese/Ko-
New in version F8. The audio delay on VCR can be enabled/ to the far-end systems. If the normal CP layout is preferred the rean/Russian>
disabled. host will transmit all CP layouts using 4CIF (704x576). Altered. The input editor menu language has been enhanced with
Russian language.
Audio HearingImpaired NoiseReduction: <On/Off> KeepDuoOpen: <On/Off>
New in version F8. The noise reduction can be controlled on the New in version F8. Keeps the dual channel open even when there PresentationSoftkey: <DuoScr/MainScr>
endpoint. Noise reduction is added to the output used for hearing is no presentation video source connected to the endpoint.
New in version F8.
impaired devices installed on output 3. You can configure the Presentation key on the remote control to
MaxBandwidth: <128..6144>
either select dual source or main source when in a call, Default is
Audio HearingImpaired EQ: <On/Off> Altered. Limit max bandwidth usage for the system. Related to IP- DuoSrc (dual source).
New in version F8. An equalizer (EQ) can be enabled on the end- Media MaxVideoTXRate, which only controls upstream bandwidth.
point, adding more amplification to the higher frequencies typically Updated the value space from MaxBandwidth: <128..10240> to
Preset [1..15] Camera Brightness Level: <0..31>
found in voices. MaxBandwidth: <128..6144>.
Altered. Defines the brightness level to use if Brightness Mode is
Multipoint Mode <Off/Multisite/Multiway> set to Manual. Updated the value space from 0..16 to 0..31.
Camera [1..13] Brightness Level: <0..31>
Altered. Defines the brightness level to use if Brightness Mode is New in version F8. The Multiway feature will extend point to point
RTP MTU: <400..1400>
set to Manual. Updated the value space from 0..16 to 0..31. calls to conferences on MCU’s hosted on the network over H.323
and SIP. The new participant will be consulted before he is added Altered. Maximum Transfer Unit is the number of bytes of video
to the conference. Requires the uses of the TANDBERG Vide Com- payload per packet. Updated the value space from 1200..1400 to
munications Server (VCS) software Ver. X4.1 or higher, and the 400..1400.

D 13887.09
APRIL 2009 3
Finding the Information You Need
What’s New in This Version? TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Security Level: <0..2> SIP TURN Server: <S: 0, 60> OSD Menu DisplayWelcomeTime: <On/Off>
New in version F8. A Security level parameter has been added to New in version F8. Address of the TURN server for data redirec- Added to the guide. Enables/disables the date and time to be
the configuration of the endpoint, restricting access to the system. tion. A fully qualified domain name or an IP address can be used. displayed on the welcome menu. Requires the NTP IP settings to
When configured for level 0, the system will have a similar security Default port 3478 is assumed. Optional port can be provided be configured to synchronize with the NTP time server.
regime as F7.x. Password storage, encryption, logging etc. will not using ”:nnnnn” notation.
be influenced by setting this to 0. When configured for level 1, the OSD Menu Simple: <On/Off>
system password can only be changed once every 24 hours and ThreePartyLayout: <On/Off> Added to the guide. Enables/disables the Simple Menu mode
three failed attempts to log into the system will lock the inter-
New in version F8. The 3 party layout on the multisite host with some of the menus and buttons hidden.
face for 30 minutes. If a password is set, the system will ask for
utilizes the dual monitor setting of the system to display the two
password confirmation from all web sessions every 15 minutes to
far-end sites on individual monitors. This feature is supported OSD Menu CodecLabel: <S: 0, 48>
ensure the session is still active. When set to level 2, the system
when the multisite picture mode is set to Auto Split or 4 split.
will include all security parameters within level 1 and will also pre- Added to the guide. Specify the text of the codec label.
When a dual stream is started during the conference, the screen
vent normal access to the web server. If a password is set, level
will return to a standard 4-split in order to display the dual stream
2 will time out all active management sessions every 15 minutes, OSD Menu DisplayLogo: <On/Off>
on the second monitor. Upon termination of the dual stream, the
prompting for password input.
layout will return to the 3 party layout. Added to the guide. Enables/disables the Display Logo on
screen.
SecurityLog Mode: <On/Off> Video Outputs DVI [1,2] AspectChoice: <Auto/Clip/Letterbox/Fill>
New in version F8. When enabled, the security log feature will New in version F8. The aspect ratio for the DVI-I outputs can be OSD Icon DuoVideo: <On/Off>
now log all security related events and configuration changes adjusted to Auto, Clip, Letterbox, and Fill to customize the aspect Added to the guide. Enables/Disables the DuoVideo icon.
within the event-log file on the endpoint, allowing an administra- ratio of the monitor to the preferred configuration.
tor to ensure all access to the system is properly logged and can
be reviewed at a later point. When enabled, the security log will OSD Icon CameraTracking: <On/Off>
Video Outputs TV [1,2] AspectChoice: <Auto/Clip/Letterbox/Fill>
maintain a record of events. Added to the guide. Enables/Disables the Camera Tracking icon.
New in version F8. The aspect ratio for the TV outputs can be
adjusted to Auto, Clip, Letterbox, and Fill to customize the aspect
SIP ICE Mode: <On/Off> ratio of the monitor to the preferred configuration. OSD CallDuration Mode: <On/Off>
New in version F8. This version supports SIP interactive con- Added to the guide. Enables/Disables the display of the call
nectivity establishment (ICE) for SIP traversal. ICE is a client duration on screen while in a call.
protocol that governs NAT traversal for SIP endpoints through a Other updates to the xConfiguration commands
combination use of Simple Traversal of UDP through NAT (STUN)
and Traversal Using Relay NAT (TURN, also known as STUN Relay) The following xConfiguration settings were new in a previous ver-
Command Instructions
by allowing the endpoint to determine the best possible path to sion and have now been added to this guide.
the far end system. Observe that the (r) in the Command instructions denotes that
the parameter is required. The (r) appears for your information
AutoPIP Timeout: <1..60>
only and is not a part of the instruction.
SIP MNS Mode: <On/Off> Added to the guide. Controls the timeout for the PIP (Picture-
There are no new xCommand instructions for this version.
New in version F8. This version supports Media Network Services In-Picture) containing the far-end mainstream when dual video
mode for SIP traversal functionality that prioritizes the use of stream is activated. To make the PIP disappear automatically
TURN, so that all media traffic is relayed, unless sent to an end- after a few seconds set the AutoPIP Mode to Auto and define the Status Information Commands
point on the local network. AutoPIP Timeout.
xStatus H323Gatekeeper
SIP ForceTurn Mode: <On/Off> Directory SmartSearch: <On/Off> Run this command from the data port to display the alternate
New in version F8. This version supports SIP traversal using relay Added to the guide. Enables/disables Smart Search in the Phone gatekeepers.
NAT (TURN) for SIP traversal, allowing endpoints behind a NAT to Book.
traverse the firewall through a relay server, such as a TANDBERG
VCS.

D 13887.09
APRIL 2009 4
 Finding the Information You Need About the TANDBERG API TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
What’s New in This Version?................................................ 3 Introduction...................................................................... 39
XACLI - Basic Principles................................................ 39
Intellectual Property Rights Root Commands.......................................................... 42
About Main Types of Commands................................... 43
XACLI – Configuration Type Commands.............................. 44
Disclaimer XACLI – Configuration Type Operation ............................... 45
Configuration Help....................................................... 45
Configuration Read....................................................... 45
License Information and Patent Information
Configuration Set (Write).............................................. 45
License Agreements......................................................... 10 About Configuration Types............................................ 46
Patent Information............................................................ 10 Format for Value Types................................................. 46
XACLI – xcommands/xdirectory.......................................... 47
Operator Safety / Environmental Issues Getting an Overview..................................................... 47
Safety Instructions............................................................ 12 Command help............................................................. 47
Environmental Issues........................................................ 13 Issuing a Command...................................................... 48
China RoHS Table............................................................. 14 Command Response.................................................... 48
Command Parameter Value Types................................. 49
Format for Value Types................................................. 49
What’s in the Shipping Box?
XACLI – Status Type Commands........................................ 50
Contents of the 3000 MXP Codec Shipping Box.................. 16 About Status Type Commands...................................... 50
Contents of the 6000 MXP Codec Shipping Box.................. 17 Understanding Status Information Structuring............... 50
About Status Type Commands Formatting..................... 51
Interfaces and Sockets – Codec 3000 MXP Default XACLI Formatting.............................................. 51
Rear Panel Socket– and Interface Groups.......................... 19 About Complete Path formatting................................... 52
Audio Sockets.................................................................. 20 About XML Formatting.................................................. 53
Audio signal levels in Vpp and dBu..................................... 21 About Addressing Status Information............................ 54
Video Sockets.................................................................. 22 About Exposure Options............................................... 55
Camera Socket................................................................. 23 XACLI – Special Commands – xfeedback (I)........................ 56
ISDN BRI sockets (not applicable to 3000 MXP Net)........... 24 About the xfeedback Command.................................... 56
Net socket (applies to 3000 MXP Net only)........................ 25 XACLI – Special Commands – xpreferences (I).................... 58
Network Interface Sockets................................................ 26 About xpreferences...................................................... 58
Power Socket & On/Off Switch.......................................... 27 The xpreferences Options............................................. 58
xpreferences xpathwrite............................................... 58
xpreferences xmlcommandresult.................................. 58
Interfaces and Sockets – Codec 6000 MXP xpreferences detaillevel................................................ 58
Rear Panel Socket– and Interface Groups.......................... 29 xpreferences xmlconfigfeedback................................... 58
Audio Sockets.................................................................. 30 xpreferences xmlstatusfeedback.................................. 59
Audio Signal Levels in Vpp and dBu................................... 31 xpreferences itemnumber............................................. 59
Video Sockets.................................................................. 32 xpreferences completepath.......................................... 60
Net Interface Socket......................................................... 33 XACLI – Special Commands – xgetxml................................ 61
Network Interface Sockets................................................ 34 About xgetxml.............................................................. 61
What’s in this Camera Sockets............................................................... 35
Data Ports........................................................................ 36
TXAS - TANDBERG XML API Service.................................... 62
About TANDBERG XML API Service................................ 62
User Guide? Power Socket & On/Off Switch.......................................... 37 Bare-bone HTTP(S) Access........................................... 62

D 13887.09
APRIL 2009 5
 Configuration-type Commands IP................................................................................ 89 TANDBERG 3000 MXP & 6000 MXP
VNC........................................................................... 123
IPMedia....................................................................... 90 REFERENCE
LocalEntry — GroupEntry. GUIDE FOR SYSTEM INTEGRATORS
................................................. 124
Understanding the Table Layout......................................... 64
AdditionalCamera......................................................... 65 IRControl..................................................................... 90 LocalEntry [1..200]..................................................... 124
AlertSpeaker................................................................ 65 ISDN............................................................................ 90 GroupEntry [1..50]...................................................... 124
AlertTone..................................................................... 65 Key.............................................................................. 94 GlobalEntry..................................................................... 125
AllowLatency................................................................ 65 Keyboard..................................................................... 98
AutoAnswer.................................................................. 69 Kiosk........................................................................... 98 Configuration Storage Levels
AutoPIP........................................................................ 70 LocalLayout............................................................... 100
Understanding the Table Layout....................................... 127
AutoLayout.................................................................. 70 Logo.......................................................................... 100
AutoDisplaySnapshot................................................... 70 LoS........................................................................... 100
Bonding....................................................................... 70 MainVideoSource....................................................... 101 Command Information Tables
CallManager................................................................ 70 MaxBandwidth........................................................... 101 Understanding the Table Layout....................................... 143
CallVideoSource........................................................... 70 Multipoint.................................................................. 101 AlertToneTest............................................................. 144
Camera [1..13]............................................................. 71 NAT........................................................................... 102 AudioTestSignal.......................................................... 144
CameraDVI.................................................................. 72 NetProfile [1..7].......................................................... 102 Boot.......................................................................... 145
CameraSleep............................................................... 72 NTP........................................................................... 102 CallAccept................................................................. 145
CameraTracking........................................................... 73 OptionKey.................................................................. 103 CallMute.................................................................... 145
Conference.................................................................. 73 OSD.......................................................................... 103 CallMuteOutgoing....................................................... 145
CorporateDirectory....................................................... 77 PictureProgram [1..4].................................................. 106 CallSetAudioTP........................................................... 146
DefaultPIPPosition....................................................... 78 PresentationStart....................................................... 106 CameraFocus............................................................. 146
Directory...................................................................... 78 PacketlossDownSpeed............................................... 106 CameraForceUpgrade................................................. 146
DoNotDisturb............................................................... 78 PresentationSoftkey................................................... 107 CameraHalt............................................................... 146
DualMonitor................................................................. 78 Preset [1..15]............................................................. 107 CameraMove............................................................. 147
DuoVideoSource.......................................................... 78 QoS........................................................................... 108 CameraPosition......................................................... 147
DynamicResolution...................................................... 78 RemoteSwUpgrade..................................................... 110 CameraReconfigure.................................................... 147
E1............................................................................... 79 RTP........................................................................... 110 CameraTrackingStart.................................................. 148
Ethernet [1..2].............................................................. 79 Screensaver............................................................... 110 CameraTrackingStop.................................................. 148
ExternalManager.......................................................... 79 SecurityLog................................................................ 111 CameraUpgrade......................................................... 148
ExternalNetwork........................................................... 79 Security..................................................................... 111 CameraWhiteBalance................................................. 148
ExternalServices.......................................................... 80 SelfViewOnStartup..................................................... 111 ChairRelease............................................................. 148
FECC........................................................................... 80 SerialPort.................................................................. 112 ChairTake................................................................... 148
FeedbackFilter............................................................. 80 SIP............................................................................ 112 ConferenceDisconnect............................................... 149
FTP.............................................................................. 80 SNMP........................................................................ 114 ConferenceTerminate................................................. 149
G703........................................................................... 80 StartupVideoSource................................................... 115 CorpDirSearch........................................................... 150
H320........................................................................... 81 StillImageSource........................................................ 115 CorpDirGetNext.......................................................... 151
H323........................................................................... 81 SSH........................................................................... 115 CorpDirGetPrevious.................................................... 152
H323CallSetup............................................................ 81 Streaming.................................................................. 116 DefaultValuesSet....................................................... 153
H323Gatekeeper......................................................... 82 StrictPassword........................................................... 117 Dial........................................................................... 154
H323Prefix.................................................................. 83 Switch....................................................................... 117 DialGlobalEntry.......................................................... 155
HTTP........................................................................... 83 SystemUnit................................................................ 117 DialGroupEntry........................................................... 155
HTTPS......................................................................... 83 T1............................................................................. 118 DialLocalEntry............................................................ 155
IdReport...................................................................... 83 Telnet........................................................................ 118 DisconnectCall........................................................... 156
IEEE802.1x.................................................................. 84 TelnetChallenge......................................................... 118 DuoVideoStart........................................................... 156
IMUX........................................................................... 84 Time.......................................................................... 118 DuoVideoStop............................................................ 156
Integrator..................................................................... 89 ThreePartyLayout....................................................... 119 DTMFSend................................................................. 156
IPProtocol.................................................................... 89 UseAsLocalPCMonitor................................................ 119 FECCFocus................................................................ 156
Video......................................................................... 119 FECCMove................................................................. 157

D 13887.09
APRIL 2009 6
 FECCPresetActivate.................................................... 157 Status Information Tables TANDBERG 3000 MXP & 6000 MXP
Controlling External Cameras
FECCPresetStore........................................................ 157 REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Understanding the Table Layout....................................... 168 Extcam Protocol Basics................................................... 231
FECCRequestStill....................................................... 157 Audio............................................................................. 169 Far End Video Source Switching.................................. 231
FECCSelectSource..................................................... 157 BRI................................................................................. 170 Far End Preset Switching............................................ 231
FeedbackDeregister................................................... 157 Call................................................................................ 172 The extcap and the extname....................................... 231
FeedbackRegister...................................................... 158 Camera.......................................................................... 184 The extswitch............................................................. 231
FIPSMode.................................................................. 158 CameraSWUpgrade......................................................... 185 Interfacing to the TANDBERG WAVE II Camera ................. 232
FloorRelease.............................................................. 158 CameraTracking.............................................................. 186 Commands..................................................................... 233
FloorRequest............................................................. 158 Conference..................................................................... 187 Interfacing to the Precision HD Camera............................ 235
FloorToSite................................................................. 159 Ethernet......................................................................... 193
FloorToSiteEnd........................................................... 159 ExternalManager............................................................. 194
GroupEntryAdd........................................................... 159 TANDBERG Video Switch
ExternalNetwork............................................................. 195
GroupEntryDelete....................................................... 159 Unpacking the Video Switch............................................ 237
FarEndInformation ......................................................... 196
KeyDown................................................................... 159 Connecting the Video Switch........................................... 238
Feedback ..................................................................... 198
KeyRelease................................................................ 160 Installation of the Video Switch....................................... 241
G703.............................................................................. 199
KeyPress................................................................... 160 Communicating with the Video Switch.............................. 242
H323Gatekeeper............................................................ 200
KeyDisable................................................................ 160 Disclaimer and Safety Instructions.................................. 244
IP................................................................................... 201
KeyEnable.................................................................. 160 Product Declaration........................................................ 245
NTP................................................................................ 202
LocalEntryAdd............................................................ 161 PRI................................................................................. 203
LocalEntryDelete........................................................ 161 RemoteSwUpgrade......................................................... 206
MessageBoxDelete.................................................... 161 Screensaver................................................................... 207
MessageBoxDisplay................................................... 162 SIP . ............................................................................. 208
PIPHide...................................................................... 162 SoftwareUpgrade............................................................ 209
PIPShow.................................................................... 162 Switch ........................................................................... 210
PresetActivate........................................................... 162 VirtualMonitor................................................................. 213
PresetClear................................................................ 163 Warning.......................................................................... 214
PresetStore............................................................... 163 Call................................................................................ 215
ProfileActivate............................................................ 163 Call - DisconnectCause................................................... 216
ProfileCreate.............................................................. 163 Call - DisconnectCauseValue........................................... 217
ProfileDelete.............................................................. 163 AuthenticationFailure...................................................... 220
ProfileList.................................................................. 163 CallDisconnected............................................................ 221
ScreensaverActivate................................................... 163 CallSuccessful................................................................ 222
ScreensaverDeactivate............................................... 164 DownspeedingFinished................................................... 223
ScreensaverReset...................................................... 164 MessageBoxResult......................................................... 224
SiteDisconnect.......................................................... 164 PacketlossDownSpeed.................................................... 225
SiteView.................................................................... 164 SString........................................................................... 226
SiteViewEnd............................................................... 164 SystemActivity................................................................ 227
SPIDAutoConfigure..................................................... 165
StillImageSend........................................................... 165
StreamingStart.......................................................... 165 Startup Scripts
StreamingStop........................................................... 165 How to create and run a startup script............................. 229
TextDelete................................................................. 165 Create a startup script............................................... 229
TextDisplay................................................................ 165 Upload the file to the codec........................................ 229
VirtualMonitorReset................................................... 166 Run the startup script................................................ 229
VirtualMonitorSet....................................................... 166

D 13887.09
APRIL 2009 7
 Intellectual Property Rights
We recommend that you check out the This Reference Guide for System Integrators and the Products to
TANDBERG web site regularly for updated
versions of this manual: which it relates contain information that is proprietary to TANDBERG
http://www.tandberg.com/docs and its licensors. Information regarding the Products is found on the
page entitled License Agreements and Patent Information.
This Reference Guide for System Integrators may be reproduced in
its entirety, including all copyright and intellectual property notices, in
limited quantities in connection with the use of the Products. Except
for the limited exception set forth in the previous sentence, no part
of this Reference Guide for System Integrators may be reproduced,
stored in a retrieval system, or transmitted, in any form, or by any
means, electronically, mechanically, by photocopying, or otherwise,
without the prior written permission of TANDBERG. Requests for
such permission should be addressed to [email protected].
TANDBERG® is a registered trademark belonging to Tandberg ASA.
Other trademarks used in this document are the property of their
respective holders.
COPYRIGHT © 2009, TANDBERG
All rights reserved.
Philip Pedersens vei 20, 1366 Lysaker, Norway
Tel: +47 67 125 125 Fax: +47 67 125 234
E-mail: [email protected]
 Disclaimer
We recommend that you check out the The specifications for the Products and the information in this
TANDBERG web site regularly for updated
versions of this manual:
document are subject to change at any time, without notice, by
http://www.tandberg.com/docs
TANDBERG.
Every effort has been made to supply complete and accurate
information in this Reference Guide for System Integrators,
however, TANDBERG assumes no responsibility or liability for any
errors or inaccuracies that may appear in this document.
INTELLECTUAL PROPERTY RIGHTS
The Products that are covered by this Reference Guide for System
Integrators are protected under copyright, patent, and other
intellectual property rights of various jurisdictions. Any applicable
software licenses and any limited warranty are located in the
License Information section in this System Integrator Reference
Guide.
This Product is
COPYRIGHT © 2009, TANDBERG
All rights reserved.
License Information and Patent Information TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

License Agreements licenses.

Copyright © 1998, 1999, 2000, 2001, 2002, 2003 Red Hat, Inc.
OpenSSL
Copyright © 1998-2004 The OpenSSL Project. All rights reserved.
Copyright notices for third-party software on the TANDBERG Copyright © 2002, 2003 John Dallaway This product includes software developed by the OpenSSL Project
MXP systems are listed below: Copyright © 2002, 2003 Nick Garnett for use in the OpenSSL Toolkit (http://www.openssl.org/)”
• The non-commercial third party code is distributed in binary Copyright © 2002, 2003 Jonathan Larmour Copyright © 1995-1998 Eric Young ([email protected]) * All
form under the terms of non-copyleft style open source rights reserved.
Copyright © 2002, 2003 Andrew Lunn
licenses such as BSD, Artistic, or MIT/X Consortium. OpenSSL is distributed under the terms of the OpenSSL and SS-
Copyright © 2002, 2003 Gary Thomas
• The product also contains some binary code distributed in Leay licenses which are both BSD style open source licenses.
binary form under the terms of the GNU public license with Copyright 9 2002, 2003 Bart Veer
an exemption which allows static links to non-copyleft com- Copyright © 1982, 1986, 1991, 1993 The Regents of the
mercial code. University of California. All rights reserved.
snprintf
Copyright © 1999, Mark Martinec. All rights reserved
• In accordance with section (3) of the GNU General Public Copyright © UNIX System Laboratories, Inc.
License, copies of such code will be provided upon request Snprintf is distributed under the terms of the snprintf license which
All or some portions of this file are derived from material licensed
is a Frontier Artistic style open source license.
by contacting TANDBERG. Please contact us by using the to the University of California by American Telephone and Telegraph
Online Support section at www.tandberg.com or the “con- Co. or Unix System Laboratories, Inc. and are reproduced herein xSupplicant (wpa_supplicant) 802.1x
tact us” section of this manual. Please provide USD 10.00 with the permission of UNIX System Laboratories, Inc. Copyright © 2002-2005, Jouni Malinen [email protected]
for media and shipping. Copyright © 1995, 1996, 1997, and 1998 WIDE Project. All rights xSupplicant is distributed under the terms of the xSupplicant
reserved. license which is a BSD style open source license.
Agfa Copyright © 2000 Brian Somers <[email protected]>
Contains iType™ from Monotype Imaging Corporation. Copyright © 1998 The NetBSD Foundation, Inc. All rights reserved.
Copyright © 1997 Niklas Hallqvist. All rights reserved. Patent Information
CMU-SNMP Copyright © 1988 Stephen Deering.
The products described in this manual are covered by one or more
Copyright © 1988, 1989, 1991, 1992 by Carnegie Mellon Univer- Copyright © 1992, 1993 The Regents of the University of of the following patents:
sity All Rights Reserved California. All rights reserved.
US6,584,077 US5,838,664 US5,600,646
CMU-SNMP is distributed under the terms of the CMU SNMP This code is derived from software contributed to Berkeley by
US5,768,263 US5,991,277 US7,034,860
license which is an open source license similar to a BSD or X Stephen Deering of Stanford University.
Consortium License. US5.886.734 US5990.933 US7,010,119
US7,283,588 EP01953201 GB1338127
ExPat XML Parser
Dropbear - an SSH2 server Other patents pending.
Copyright © 1998, 1999, 2000 Thai Open Source Software Center
Copyright © 2002,2003 Matt Johnston All rights reserved. Ltd and Clark Cooper View http://www.tandberg.com/tandberg_pm.jsp for an updated
list
The Dropbear SSH2 server is distributed under the terms of the Copyright © 2001, 2002, 2003, 2004, 2005, 2006 Expat main-
Dropbear License which is a MIT/X Consortium style open source tainers.
license. The ExPat XML parser is distributed under the terms of the ExPat
License which is a MIT/X Consortium style open source license

eCos ICU
eCos, the Embedded Configurable Operating System. ICU License - ICU 1.8.1 Copyright © 1995-2003 International Busi-
ness Machines Corporation and others. All rights reserved.
Portions of eCos code are distributed under several BSD style
licenses. Other portions of eCos code are distributed under the ICU is distributed under the terms of the ICU license which is a
terms of the GNU General Public License with a non-copyleft excep- MIT/X Consortium style license.
tion which allows staic links to non-copyleft programs. Portions
of the code are distributed under the terms of various BSD style

D 13887.09
APRIL 2009 10
 Operator Safety / Environmental Issues
We recommend that you check out the
TANDBERG web site regularly for updated
For your own protection, please read the overleaf safety
versions of this manual: instructions completely, before operating the equipment
http://www.tandberg.com/docs and keep this manual for future reference. The information
in this summary is intended for operators. Carefully
observe all warnings, precautions and instructions both on
the apparatus and in the operating instructions.
Safety Instructions TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

For your protection please read these safety • Do not place the product in direct sunlight • Do not tug the power cord. in accordance with the operating
instructions completely before you connect or close to a surface directly heated by the • If the provided plug does not fit into your instructions.
the equipment to the power source. Carefully sun. outlet, consult an electrician.
observe all warnings, precautions and instruc-
• Never install cables, or any peripherals, Accessories
tions both on the apparatus and in these
Lightning without first unplugging the device from it's Use only accessories specified by the
operating instructions.
Never use this apparatus, or connect/discon- power source. manufacturer, or sold with the apparatus.
Retain this manual for future reference.
nect communication cables or power cables • Always use the power supply (AC–DC adap-
during lightning storms. tor) provided with this product (adaptor is Communication Lines
Water and Moisture supplied with 3000 MXP only).
Do not use communication equipment to
• Do not operate the apparatus under or near Dust • Replace only with power supply (AC–DC report a gas leak in the vicinity of the leak.
water – for example near a bathtub, kitchen adaptor) specified by TANDBERG (adaptor
Do not operate the apparatus in areas with
sink, or laundry tub, in a wet basement, is supplied with 3000 MXP only).
high concentration of dust
near a swimming pool or in other areas • Never connect attached power supply
with high humidity. (AC–DC adaptor) to other products (adaptor
• Never install jacks for communication Vibration is supplied with 3000 MXP only).
cables in wet locations unless the jack is Do not operate the apparatus in areas with
specifically designed for wet locations. vibration or place it on an unstable surface.
Servicing
• Do not touch the product with wet hands.
• Do not attempt to service the apparatus
Power Connection and Hazardous yourself as opening or removing covers
Cleaning Voltage may expose you to dangerous voltages or
• Unplug the apparatus from communication • The product may have hazardous voltage other hazards, and will void the warranty.
lines, mains power-outlet or any power inside. Never attempt to open this product, Refer all servicing to qualified service
source before cleaning or polishing. Do or any peripherals connected to the prod- personnel.
uct, where this action requires a tool.
not use liquid cleaners or aerosol clean- • Unplug the apparatus from its power
ers. Use a lint-free cloth lightly moistened • This product should always be powered source and refer servicing to qualified
with water for cleaning the exterior of the from an earthed power outlet. personnel under the following conditions:
apparatus. • Never connect attached power supply cord • If the power cord or plug is damaged or
• Unplug the apparatus from communication to other products. frayed.
lines before cleaning or polishing. Do not • In case any parts of the product has visual • If liquid has been spilled into the
use liquid cleaners or aerosol cleaners. damage never attempt to connect mains apparatus.
Use a lint-free cloth lightly moistened with power, or any other power source, before
water for cleaning the exterior of the ap- • If objects have fallen into the apparatus.
consulting service personnel
paratus. • If the apparatus has been exposed to
• The plug connecting the power cord to the rain or moisture
product/power supply serves as the main
Ventilation disconnect device for this equipment. The • If the apparatus has been subjected to
power cord must always be easily acces- excessive shock by being dropped.
• Do not block any of the ventilation openings
of the apparatus. Never cover the slots sible. • If the cabinet has been damaged.
and openings with a cloth or other mate- • Route the power cord so as to avoid it be- • If the apparatus seems to be
rial. Never install the apparatus near heat ing walked on or pinched by items placed overheated.
sources such as radiators, heat registers, upon or against it. Pay particular attention • If the apparatus emits smoke or
stoves, or other apparatus (including ampli- to the plugs, receptacles and the point abnormal odor.
fiers) that produce heat. where the cord exits from the apparatus.
• If the apparatus fails to operate

D 13887.09
APRIL 2009 12
Environmental Issues TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Thank you for buying a product which contributes to a reduc- European Environmental Directives Information for Recyclers
tion in pollution, and thereby helps save the environment. Our
As a manufacturer of electrical and electronic equipment TAND- As part of compliance with the European WEEE Directive, TAND-
products reduce the need for travel and transport and thereby
BERG is responsible for compliance with the requirements in BERG provides recycling information on request for all types of
reduce pollution. Our products have either none or few consum-
the European Directives 2002/96/EC (WEEE) and 2002/95/EC new equipment put on the market in Europe after August 13th
able parts (chemicals, toner, gas, paper). Our products are low
(RoHS). 2005.
energy consuming products.
The primary aim of the WEEE Directive and RoHS Directive is Please contact TANDBERG and provide the following details
to reduce the impact of disposal of electrical and electronic for the product for which you would like to receive recycling
TANDBERG’s Environmental Policy equipment at end-of-life. The WEEE Directive aims to reduce information:
Environmental stewardship is important to TANDBERG’s the amount of WEEE sent for disposal to landfill or incineration • Model number of TANDBERG product
culture. As a global company with strong corporate values, by requiring producers to arrange for collection and recycling.
• Your company’s name
TANDBERG is committed to following international environmen- The RoHS Directive bans the use of certain heavy metals and
tal legislation and designing technologies that help companies, brominated flame retardants to reduce the environmental • Contact name
individuals and communities creatively address environmental impact of WEEE which is landfilled or incinerated. • Address
challenges. TANDBERG has implemented necessary process changes to • Telephone number
TANDBERG’s environmental objectives are to: comply with the European RoHS Directive (2002/95/EC) and • E-mail.
• Develop products that reduce energy consumption, CO2 the European WEEE Directive (2002/96/EC).
emissions, and traffic congestion Digital User Guides
• Provide products and services that improve quality of life for Waste Handling TANDBERG is pleased to announce that we have replaced the
our customers In order to avoid the dissemination of hazardous substances printed versions of our User Guides with a digital CD version.
• Produce products that can be recycled or disposed of safely in our environment and to diminish the pressure on natural Instead of a range of different user manuals, there is now one
at the end of product life resources, we encourage you to use the appropriate take-back CD – which can be used with all TANDBERG products – in a
variety of languages. The environmental benefits of this are
• Comply with all relevant environmental legislation. systems in your area. Those systems will reuse or recycle most
of the materials of your end of life equipment in a sound way. significant. The CDs are recyclable and the savings on paper
are huge. A simple web-based search feature helps you directly
TANDBERG products put on the market after August access the information you need. In addition, the TANDBERG
2005 are marked with a crossed-out wheelie bin sym- video systems now have an intuitive on-screen help function,
bol that invites you to use those take-back systems. which provides a range of useful features and tips. The con-
Please contact your local supplier, the regional waste tents of the CD can still be printed locally, whenever needed.
administration or http://www.tandberg.com/recycling
if you need more information on the collection and recycling
system in your area.

D 13887.09
APRIL 2009 13
Environmental Issues TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

China RoHS Table

D 13887.09
APRIL 2009 14
 What’s in the Shipping Box?
We recommend that you check out the This part of the Reference Guide for System Integrators
TANDBERG web site regularly for updated
versions of this manual: presents the contents of the shipping box to ease your
http://www.tandberg.com/docs acceptance test as well as assist you in making sure
you’ve got everything with you if you need to take the
codec along for installation etc.
What’s in the Shipping Box?
Contents of the 3000 MXP Codec Shipping Box TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

CD with user documentation

Remote control

4 ISDN BRI cables Up to 4 mains cables

(not included with the Batteries for remote control (depending on region)
NET version)

Rack mounting kit (II)

Rack mounting kit (I)

Codec 3000 MXP

User
registration
card

Power supply Split cable for

non-TANDBERG WAVE II
cameras

Video DVI–VGA cable

1 LAN / Ethernet cable

D 13887.09
APRIL 2009 16
What’s in the Shipping Box?
Contents of the 6000 MXP Codec Shipping Box TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

CD with user documentation Up to 4 mains cables

Remote control (depending on region)

Batteries for remote control

Rack mounting kit (II)

6 ISDN BRI cables
Rack mounting kit (I)

Codec 6000 MXP

User
Mains
registration
extension
card
cable

1 ISDN PRI cable

1 LAN / Ethernet cable DVI–VGA cable

D 13887.09
APRIL 2009 17
 Interfaces and Sockets – Codec 3000 MXP
We recommend that you check out the This part of the manual provides an in-depth presentation
TANDBERG web site regularly for updated
versions of this manual: of the rear panel sockets and interfaces of the Codec
http://www.tandberg.com/docs 3000 MXP, including the audio signal levels and the
formats supported.
Interfaces and Sockets – Codec 3000 MXP
Rear Panel Socket– and Interface Groups TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

The Codec 3000 MXP comes in two flavours – with ISDN BRI sockets (upper) or with Net socket (lower).

Codec 3000 MXP

PC card Camera

DC power socket Network

and On/Off switch Video sockets
interface Audio sockets
Ethernet ISDN BRI
sockets

Codec 3000 MXP Net

PC card Camera

DC power socket Network

and On/Off switch interface Video sockets
Audio sockets Ethernet
sockets Net socket

D 13887.09
APRIL 2009 19
Interfaces and Sockets – Codec 3000 MXP
Audio Sockets TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Tip! Audio signal levels Use Audio Input No. 3 to Use Audio Input No. 4 to Tip! Audio Input No. 4 is not Stereo Settings
expressed in volts and dBu connect to external playback connect a VCR or DVD player equipped with an acoustic
Settings Output Response
can be found overleaf. devices. This input can also to the system. For systems echo canceller. Connecting a
be configured as a microphone configured with stereo I/O, microphone to this input can Out 1 mode Stereo Stereo Audio Out 1 Audio Out 2
input. It will then function in connect the VCR/DVD right therefore not be recommended. I/O mode speakers
Note! Audio inputs 3 &
4 are referred to as Line lieu of the Mic. 2 input and be channel to this input. This Analogue Off Off Loudspeaker mono VCR

input 1 & 2 in the API. connected to Mic. 2’s echo input should be used when Analogue Off On Loudspeaker L Loudspeaker R
canceller (which can be turned connecting a telephone add-on
Analogue On Off Loudspeaker mono VCR
on/off). system.
Tip! Unused, but connected Analogue On On Loudspeaker L Loudspeaker R
audio inputs should be set
SPDIF Off Off Loudspeaker mono VCR
to Off to avoid unwanted
audio/noise. SPDIF Off On Loudspeaker L & R VCR

SPDIF On Off Loudspeaker mono VCR

SPDIF On On Loudspeaker L & R VCR

Use Audio Output No. 1 to provide a mixed

signal of audio from far end and local
external devices connected to input 3 & 4 in
addition to dial tones. Use Audio Output No. 2 (the VCR output) to Microphone Inputs Nos. 1–2. Hardware Information
provide a mixed signal consisting of audio Two balanced microphone Microphone(s) Audio Input(s) Audio Outputs
This output should be connected to the local
from the local side (VCR not included) and inputs for electret microphones
loudspeaker system, which may, or may not, Signal type Balanced Unbalanced
audio from the far end. balanced, 24V phantom
include the TANDBERG Digital Natural Audio
powered via XLR connectors. Socket XLR-F RCA/phono
Module. This output should be used when connecting a
telephone add-on system. Input impedance 2400 W 10 kW
For systems configured with stereo (pin 2–3)
speakers and SPDIF† active, the left and For system configured with stereo I/O and
XLR pin-out Output impedance 680 W
right channel of the loudspeaker signal will with SPDIF† active on Audio Output No. 1, this
both be provided on this output. output will provide the VCR left channel stereo External view of socket Max input level when set to
83 mVpp 15.5 Vpp
min. input level
information.
For systems configured with stereo 2 1 Max output level when set
speakers and SPDIF† not active, the For systems configured with stereo I/O, stereo Pin 1: Gnd to max. output level
15.5 Vpp
left channel of the loudspeaker signal speakers and SPDIF† not active, this output
Pin 2: Hot Max input level when set to
will be present on this output. The right will provide the right channel of the loudspeak- max. input level
6.2 mVpp 1.2 Vpp
loudspeaker channel will be provided on er signal (the left channel will be provided on Pin 3: Cold/neutral
3
Max output level when set
Audio Output No. 2. the Audio Output No. 1). to min. output level
1.2 Vpp

Gain range 22.5 dB (16 steps of 1.5 dB)

†
SPDIF (Sony/Philips Digital Interface)
RCA pin-out is used by the Digital Natural Audio module. Phantom power 24 V ± 5 %

External view of socket Phantom power resistor

1200 W
pin 2
Signal GND
Phantom power resistor
1200 W
pin 3

Max phantom power

12 mA
current

D 13887.09
APRIL 2009 20
Interfaces and Sockets – Codec 3000 MXP
Audio signal levels in Vpp and dBu TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Microphone Inputs 1 & 2 Audio Inputs 3 & 4 Audio Outputs 1 & 2 Note! Audio inputs 3 & 4 are referred
Signal levels Signal levels Signal levels to as Line input 1 & 2 in the API.
Signal Clipping levels Nominal Signal Clipping levels Nominal Signal Absolute max output Nominal
levels level levels level levels level level Tip! To convert dBu values to dBV,
subtract 2.2 dB from the dBu value.
Input Input Input
menu menu menu Example: –10 dBu => –12.2 dBV
level level level
setting setting setting Note! The input clipping levels and
[dB] [mVpp] [dBu] [dBu] [dB] [Vpp] [dBu] [dBu] [dB] [Vpp] [dBu] [dBu] the absolute max output levels all
assume sinusoidal signals for the dBu
0.0 83.0 –28.4 –46.4 0.0 15.5 17.0 –1.0 0.0 1.2 –5.5 –23.5
values.
1.5 69.8 –29.9 –47.9 1.5 13.0 15.5 –2.5 1.5 1.4 –4.0 –22.0
3.0 58.8 –31.4 –49.4 3.0 11.0 14.0 –4.0 3.0 1.6 –2.5 –20.5
4.5 49.4 –32.9 –50.9 4.5 9.2 12.5 –5.5 4.5 1.9 –1.0 –19.0
6.0 41.6 –34.4 –52.4 6.0 7.8 11.0 –7.0 6.0 2.3 0.5 –17.5
7.5 35.0 –35.9 –53.9 7.5 6.5 9.5 –8.5 7.5 2.8 2.0 –16.0
9.0 29.4 –37.4 –55.4 9.0 5.5 8.0 –10.0 9.0 3.3 3.5 –14.5
10.5 24.8 –38.9 –56.9 10.5 4.6 6.5 –11.5 10.5 3.9 5.0 –13.0
12.0 20.8 –40.4 –58.4 12.0 3.9 5.0 –13.0 12.0 4.6 6.5 –11.5
13.5 17.5 –41.9 –59.9 13.5 3.3 3.5 –14.5 13.5 5.5 8.0 –10.0
15.0 14.8 –43.4 –61.4 15.0 2.8 2.0 –16.0 15.0 6.5 9.5 –8.5
16.5 12.4 –44.9 –62.9 16.5 2.3 0.5 –17.5 16.5 7.8 11.0 –7.0
18.0 10.4 –46.4 –64.4 18.0 2.0 -1.0 –19.0 18.0 9.2 12.5 –5.5
19.5 8.8 –47.9 –65.9 19.5 1.6 -2.5 –20.5 19.5 11.0 14.0 –4.0
21.0 7.4 –49.4 –67.4 21.0 1.4 -4.0 –22.0 21.0 13.0 15.5 –2.5
22.5 6.2 –50.9 –68.9 22.5 1.2 -5.5 –23.5 22.5 15.5 17.0 –1.0

Audio inputs 3 & 4 Default levels are denoted as follows:

–31.4

Audio outputs 1 & 2 Microphone inputs 1 & 2

D 13887.09
APRIL 2009 21
Interfaces and Sockets – Codec 3000 MXP
Video Sockets TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Note! The system S-video input Composite video input RCA sockets PC DVI-I input sockets
will automatically Mini-DIN socket Doc. camera VCR (Digital Video Interface,
adapt to a PAL or Aux. camera Integrated digital
NTSC input. and analogue)

Single
S-video output
Mini-DIN socket

Single Dual DVI output

Composite video output
RCA sockets
S-video Mini-DIN pin-out
DVI-I pin-out DVI-I Pin-out External view of socket
4 3
Pin Assignment Pin Assignment Pin Assignment
Formats supported on DVI-I out: Levels
1 T.M.D.S. Data 2– 9 T.M.D.S. Data 1– 17 T.M.D.S. Data 0– SVGA (800 × 600) 75 Hz Composite: 1 Vpp, 75 W
XGA (1024 × 768) 60 Hz S-Video (Y/C):
2 T.M.D.S. Data 2+ 10 T.M.D.S. Data 1+ 18 T.M.D.S. Data 0+ SXGA (1280 × 1024) 60 Hz
HD720p (1280 × 720) 50 Hz, 60 Hz Y: 1 Vpp, 75 W 2 1
3 T.M.D.S. Data 2/4 11 T.M.D.S. Data 1/3 19 T.M.D.S. Data 0/5
Shield Shield Shield WXGA (1280×768) 60 Hz C (PAL): 0.3 Vpp, 75 W Pin 1: Ground (Luminance)
Note: TANDBERG supports DVI-D C (NTSC): 0.28 Vpp, 75 W
Single-Link, DVI-A and DVI-I Sin- 4 T.M.D.S. Data 4– 12 T.M.D.S. Data 3– 20 T.M.D.S. Data 5– Formats supported on DVI-I in: Pin 2: Ground (Chrominance)
gle-Link format cables. SVGA (800 × 600) 60 Hz, 72 Hz, 75 Hz, 85 Hz Pin 3: Luminance (Y)
5 T.M.D.S. Data 4+ 13 T.M.D.S. Data 3+ 21 T.M.D.S. Data 5+
XGA (1024 × 768) 60 Hz, 70 Hz, 75 Hz
DVI-D cables transmit digital 6 DDC Clock 14 +5 V power 22 T.M.D.S. Clock SXGA (1280 × 1024) 60 Hz Pin 4: Chrominance (C)
T.M.D.S. signals, DVI-A cables Shield HD720p (1280 × 720) 50 Hz, 60 Hz

transmit analogue VGA signals 7 DDC Data 15 GND 23 T.M.D.S. Clock+ Do as follows to get WXGA:
and DVI-I cables can transmit (return for +5 V, 1 VGA Out Quality must be set to Auto. RCA pin-out
HSync and Vsync) External view of socket
either digital or analogue signals. 2 VGA Monitor Format must be set to Wide.
8 Analogue Vertical 16 Hot plug detect 24 T.M.D.S. Clock– 3 PC Picture Format must be set to Normal.
If your DVI cable is not long Sync If you are using TANDBERG supplied monitors this will give WXGA out Signal GND
enough, use extension cables. when displaying graphics.
C1 Analogue Red C2 Analogue Green C3 Analogue Blue
Observe, however, that the If non-TANDBERG provided displays are used, you must in addition
maximum cable length should not C4 Analogue C5 Analogue GND execute the command:
Horizontal Sync (analogue
exceed 5 m to avoid quality loss. xConfiguration Video Outputs AllowWXGA: On
R, G & B return)

D 13887.09
APRIL 2009 22
Interfaces and Sockets – Codec 3000 MXP
Camera Socket TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Tip! Wherever applicable, the use

Camera Connect the camera here. Use
of Category 5 cabling or better is
a TANDBERG 3000 WAVE II Camera
strongly recommended! For HD camera
cable or similar.
applications, however, Category 7.5 is
required. To connect a non-TANDBERG camera
use the split cable supplied. This cable
has a female D-SUB and an S-video
connector in one end and a male D-SUB
connector in the other end.

9-pin D-sub pin-out

External view of socket
5 1

9 6

Codec side
S-video Mini-DIN pin-out
Split cable for non- External view of socket
TANDBERG 3000 WAVE II TANDBERG HD 3000 Non-TANDBERG
Camera cable pin-out Camera cable pin-out Camera cable pin-out TANDBERG WAVE II 4 3
cameras
SIGNAL RJ-45 S-VIDEO DSUB SIGNAL RJ-45 DSUB SIGNAL DSUB S-VIDEO DSUB
NAME NAME NAME Camera Codec

+12V DC 8 — 4 +12V DC 1 Twisted 4 +12V DC 1 — 4

pair
2 1
GND 7 — 5 GND 2 1 GND 2 — 5
Pin 1: Ground (Luminance)
+12V DC 3 — 4 Rx 3 2 +12V DC 3 — 4 Camera side
Twisted Pin 2: Ground (Chrominance)
TXD 4 — 3 TX 4 pair 6 TXD 4 — 3
Pin 3: Luminance (Y)
RXD 5 — 2 LVDS+ 5 Twisted 9 RXD 5 — 2
Pin 4: Chrominance (C)
GND 6 — 5 LVDS– 6 pair 3 GND 6 — 5

GND 2 — 5 GND 7 Twisted 5 GND 7 — 5

+12V DC 1 — 4 +12V DC 8 pair 4 +12V DC 8 — 4 RJ-45 Connector pin-out

Y-GND — 1 8 Y-GND — 1 8
Cable is Category 7.5/ Class F AWG24.
C_GND — 2 1 Extreme care should be taken if you choose C_GND — 2 1
to make your own version of this cable!
Y — 3 9 Y — 3 9

C — 4 6 C — 4 6

NC — — 7 NC — — 7

D 13887.09
APRIL 2009 23
Interfaces and Sockets – Codec 3000 MXP
ISDN BRI sockets (not applicable to 3000 MXP Net) TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Tip! Wherever applicable, the use

of Category 5 cabling or better is
strongly recommended! For HD camera
applications, however, Category 7.5 is
required.

S/T Interface
RJ-45 Connector pin-out ISDN BRI interface. ISDN I.420
BRI Pin out (RJ-45 Jack) Basic Rate Interface
Pin 3 TX+ S/T (2B + D), 128 kbps per ISDN
Pin 4 RX+ I/F. Use any standard BRI cable
Pin 5 RX– to connect the Codec to BRI.
Pin 6 TX–

D 13887.09
APRIL 2009 24
Interfaces and Sockets – Codec 3000 MXP
Net socket (applies to 3000 MXP Net only) TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

RS366 DTE → DCE

Pin Signal name Direction Description

1 FGND ↔ Frame GND Net interface socket. 1 × X.21 / V.35 / RS449

2 DPR → Digit Present with 1 × RS366 Call Control up to 2 Mbps
3 ACR ← Abandon Call & Retry

4 CRQ → Call Request

5 PND ← Present Next Digit

6 DLO ← Data Line Occupied

7 NB1 → Digit Bit 1

8 NB2 → Digit Bit 2

9 NB4 → Digit Bit 4

10 NB8 → Digit Bit 8

HD D-SUB 26 pin-out
External view of socket
V35 DTE → DCE RS449 DTE → DCE Note the following:
Pin Signal name Direction Description Pin Signal name Direction Description V.10 (RS423). For balanced signals a
1 9
0 = low voltage, is defined as terminal 10 18
1 FGND ↔ Frame GND on equipment 1 FGND ↔ Frame GND
A positive with respect to terminal B. 19 26
11 SD(A) → Send Data / Transmit 11 SD(A) → Send Data
For unbalanced signals a 0 = low volt-
 
12 SD(B) → Send Data / Transmit 12 SD(B) → Send Data age, is defined as terminal positive
13 RD(A) ← Receive Data 13 RD(A) ← Receive Data with respect to GND. Cable length X.21 DTE → DCE
for Leased Line Control should not
14 RD(B) ← Receive Data 14 RD(B) ← Receive Data Pin Signal name Direction Description
exceed 20 m.
15 SCR(A) ← Signal Clock Receive 15 RT(A) ← Receive Timing 1 FGND ↔ Frame GND
16 SCR(B) ← Signal Clock Receive 16 RT(B) ← Send Timing RS 366. All balanced inputs and 11 T(A) → Send Data / Transmit
17 SCT(A) ← Signal Clock Transmit 17 ST(A) ← Send Timing outputs (A and B) use balanced line 12 T(B) → Send Data / Transmit
18 SCT(B) ← Signal Clock Transmit 18 ST(B) ← Send Timing signals according to V.11 (RS 422), 13 R(A) ← Received Data / Receive
while single ended signals are in
19 GND1 ↔ Signal GND 19 GND1 ↔ GND 14 R(B) ← Received Data / Receive
accordance with V.10 (RS423). The
22 RLSD(CD) ←
Received Line Signal Detector / 20 TR(A) → Terminal Ready 0 = low voltage definitions are the 15 S(A) ← Signal Element Timing
Carrier Detect
21 TR(B) → Terminal Ready same as for V.10 above. Max cable 16 S(B) ← Signal Element Timing
23 RLSD(GND)1 ← Signal GND length, as for V.10 above.
22 RR(A) ← Carrier Detect / Receiver Ready 20 C(A) → Terminal Ready / Control
24 RI ← Ring Indicator
23 RR(B) ← Carrier Detect / Receiver Ready
X.21. Signals are as for RS 366 above.
21 C(B) → Terminal Ready / Control
25 LOS → Loss of Signal (KG194)
24 IC ← Incoming Call Cable length should not exceed 50 m. 22 I(A) ← Carrier Detect
26 DTR → Data Terminal Ready
25 LOS → Loss of Signal (KG194) 23 I(B) ← Carrier Detect
1) This pin is connected to ground for correct operations
Frame GND is connected to pin 1 on DTE
1) This pin is connected to ground for correct operations

D 13887.09
APRIL 2009 25
Interfaces and Sockets – Codec 3000 MXP
Network Interface Sockets TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Tip! Wherever applicable, the use

of Category 5 cabling or better is PC card. Wireless LAN PC card
strongly recommended! For HD camera may be inserted here.
applications, however, Category 7.5 is
required.

USB interface. Ethernet LAN (RJ-45 Jack) interface (10/100 Mb).

For future use. Up to 4 or 6 Mbps, depending on the bandwidth op-
tion installed. Use any standard Ethernet cable to
Data port. The Data port is connect the Codec to a LAN.
Data port
implemented as a Digital Circuit
Pin Signal name Direction If no LAN is available and the Codec is connected
Terminating Equipment (DCE).
directly to a computer, use a crossover cable.
1 Carrier From DCE
detect, CD 9-pin D-sub pin-out Ethernet cable
2 Receive data, From DCE External view of socket 1 ---------- 1 1 1
RXD
5 1 2 ---------- 2 2 2
3 Transmit To DCE
data, TXD 3 ---------- 3 3 3
4 Data terminal From DCE 6 ---------- 6 6 6
ready, DTR
9 6 Wiring diagram Wiring diagram
5 Signal GND standard cable crossover cable
6 Data set From DCE
ready, DSR RJ-45 Connector pin-out
7 Ready to To DCE
send, RTS Tip! If you connect your Codec directly to a PC, make sure you set up
8 Clear to From DCE the system to use static TCP/IP settings. There will be no DHCP server
send, CTS controlling the little LAN created by the computer and the Codec. When
9 Ring From DCE configuring a back-to-back connection between the PC and the Codec,
indicator, RI make sure both static IP addresses exist on the same subnet.

D 13887.09
APRIL 2009 26
Interfaces and Sockets – Codec 3000 MXP
Power Socket & On/Off Switch TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Caution! This equipment

must be earthed!

Power switch Power cord socket.

Accepts 12 V DC / 4.3 A

D 13887.09
APRIL 2009 27
 Interfaces and Sockets – Codec 6000 MXP
We recommend that you check out the This part of the manual provides an in-depth presentation
TANDBERG web site regularly for updated
versions of this manual: of the rear panel sockets and interfaces of the Codec
http://www.tandberg.com/docs 6000 MXP, including the audio signal levels and the
formats supported.
Interfaces and Sockets – Codec 6000 MXP
Rear Panel Socket– and Interface Groups TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Network interface sockets

Audio sockets
Video sockets

Power socket
and On/Off switch

D 13887.09
APRIL 2009 29
Interfaces and Sockets – Codec 6000 MXP
Audio Sockets TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Use Audio Input No. 4 Use Audio Input No. 5 to Use Audio Input No. 6 to Tip! Audio inputs Nos. 5 Stereo Settings
to connect to an external connect to external playback connect a VCR or DVD player & 6 are not equipped with
Settings Output Response
microphone amplifier or to devices or to telephone add-on to the system. For systems acoustic echo canceller.
an external mixer. hybrids. For systems configured configured with stereo I/O, Connecting microphones to Out 1 Stereo Stereo Audio Out 1 Audio Out 2 Audio
with stereo I/O, connect the connect the VCR/DVD right these inputs can therefore mode I/O mode speakers Out 3
VCR/DVD left channel to this channel to this input. not be recommended. Analogue Off Off Loudspeaker Aux VCR
input. mono
Note! Audio Tip! Unused, but connected Analogue Off On Loudspeaker L Loudspeaker R VCR
inputs 4–6 audio inputs should be set
Analogue On Off Loudspeaker VCR L VCR R
are referred to Off to avoid unwanted mono
to as Line RCA pin-out audio/noise.
Analogue On On Loudspeaker L Loudspeaker R VCR
input 1–3 in
External view of socket Tip! Audio signal levels SPDIF Loudspeaker Aux VCR
the API. Off Off
mono
Signal GND expressed in volts and dBu
can be found overleaf. SPDIF Off On Loudspeaker
Aux VCR
L & R

SPDIF Loudspeaker
On Off VCR L VCR R
mono

SPDIF Loudspeaker
On On VCR L VCR R
L & R

Microphone Inputs Use Audio Output No. 1 to Use Audio Output No. 2 (the Use Audio Output No. 3 Hardware Information
Nos. 1–3. provide a mixed signal of audio AUX output) to provide a mixed (the VCR output) to provide
Microphone(s) Audio Input(s) Audio Outputs
Three balanced from far end and local external signal consisting of audio from a mixed signal consisting
microphone inputs for devices connected to input 5 & the local side (AUX input not of audio from the local side Signal type Balanced Unbalanced
electret microphones 6, in addition to dial tones. included) and audio from the (VCR input not included) Socket XLR-F RCA/phono
balanced, 24V phantom This output should be connected far end. and audio from the far end.
Input impedance 2400 W 10 kW
powered via XLR to the local loudspeaker system, This output should be used This output should be used (pin 2–3)
connectors. which may, or may not, include when connecting a telephone when connecting a VCR to Output impedance 680 W
The phantom powering the TANDBERG Digital Natural add-on system. the system.
Max input level when set to
of XLR socket No. 3 can Audio Module. For system configured with For system configured with min. input level
83 mVpp 15.5 Vpp
be switched off. The For systems configured with stereo I/O and with SPDIF† stereo I/O and with SPDIF† Max output level when set to
Mic. input No. 3 will stereo speakers and SPDIF† active on Audio Output No. 1, active on Audio Output No. max. output level
15.5 Vpp
then be a balanced line active, the left and right channel this output will provide the VCR 1, this output will provide Max input level when set to
level input. of the loudspeaker signal will left channel stereo information. the VCR right channel max. input level
6.2 mVpp 1.2 Vpp

both be provided on this output. For systems configured with stereo information.
XLR pin-out Max output level when set to
1.2 Vpp
For systems configured with stereo I/O, stereo speakers and For systems configured min. output level
External view of socket
stereo speakers and SPDIF† SPDIF† not active, this output with stereo I/O, stereo Gain range 22.5 dB (16 steps of 1.5 dB)
2 1 not active, the left channel of will provide the right channel of speakers and SPDIF† not Phantom power 24 V ± 5 %
the loudspeaker signal will be the loudspeaker signal (the left active, this output will
Phantom power resistor
Pin 1: Gnd present on this output. The right channel will be provided on the provide the mix of left and pin 2
1200 W
loudspeaker channel will be Audio Output No. 1). right channel of the VCR
Pin 2: Hot Phantom power resistor
3 provided on Audio Output No. 2. out signal. pin 3
1200 W
Pin 3: Cold/neutral
Max phantom power current 12 mA
†
SPDIF (Sony/Philips Digital Interface)
is used by the Digital Natural Audio module.

D 13887.09
APRIL 2009 30
Interfaces and Sockets – Codec 6000 MXP
Audio Signal Levels in Vpp and dBu TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Microphone Inputs 1, 2 & 3 Microphone Input 3 Audio Inputs 4, 5 & 6 Audio Outputs 1, 2 & 3
Signal levels Line level mode signal levels Signal levels Signal levels
Signal Clipping levels Nominal Signal Clipping levels Nominal Signal Clipping levels Nominal Signal Absolute max output Nominal
levels level levels level levels level levels level level
Input Input Input Input
menu level menu level menu level menu level
setting setting setting setting
[dB] [mVpp] [dBu] [dBu] [dB] [Vpp] [dBu] [dBu] [dB] [Vpp] [dBu] [dBu] [dB] [Vpp] [dBu] [dBu]
0.0 83.0 –28.4 –46.4 0.0 15.5 17.0 –1.0 0.0 15.5 17.0 –1.0 0.0 1.2 –5.5 –23.5
1.5 69.8 –29.9 –47.9 1.5 13.0 15.5 –2.5 1.5 13.0 15.5 –2.5 1.5 1.4 –4.0 –22.0
3.0 58.8 –31.4 –49.4 3.0 11.0 14.0 –4.0 3.0 11.0 14.0 –4.0 3.0 1.6 –2.5 –20.5
4.5 49.4 –32.9 –50.9 4.5 9.2 12.5 –5.5 4.5 9.2 12.5 –5.5 4.5 1.9 –1.0 –19.0
6.0 41.6 –34.4 –52.4 6.0 7.8 11.0 –7.0 6.0 7.8 11.0 –7.0 6.0 2.3 0.5 –17.5
7.5 35.0 –35.9 –53.9 7.5 6.5 9.5 –8.5 7.5 6.5 9.5 –8.5 7.5 2.8 2.0 –16.0
9.0 29.4 –37.4 –55.4 9.0 5.5 8.0 –10.0 9.0 5.5 8.0 –10.0 9.0 3.3 3.5 –14.5
10.5 24.8 –38.9 –56.9 10.5 4.6 6.5 –11.5 10.5 4.6 6.5 –11.5 10.5 3.9 5.0 –13.0
12.0 20.8 –40.4 –58.4 12.0 3.9 5.0 –13.0 12.0 3.9 5.0 –13.0 12.0 4.6 6.5 –11.5
13.5 17.5 –41.9 –59.9 13.5 3.3 3.5 –14.5 13.5 3.3 3.5 –14.5 13.5 5.5 8.0 –10.0
15.0 14.8 –43.4 –61.4 15.0 2.8 2.0 –16.0 15.0 2.8 2.0 –16.0 15.0 6.5 9.5 –8.5
16.5 12.4 –44.9 –62.9 16.5 2.3 0.5 –17.5 16.5 2.3 0.5 –17.5 16.5 7.8 11.0 –7.0
18.0 10.4 –46.4 –64.4 18.0 2.0 –1.0 –19.0 18.0 2.0 -1.0 –19.0 18.0 9.2 12.5 –5.5
19.5 8.8 –47.9 –65.9 19.5 1.6 –2.5 –20.5 19.5 1.6 -2.5 –20.5 19.5 11.0 14.0 –4.0
21.0 7.4 –49.4 –67.4 21.0 1.4 –4.0 –22.0 21.0 1.4 -4.0 –22.0 21.0 13.0 15.5 –2.5
22.5 6.2 –50.9 –68.9 22.5 1.2 –5.5 –23.5 22.5 1.2 -5.5 –23.5 22.5 15.5 17.0 –1.0

This specification is always valid for mic 1 and 2, and This specification is valid for mic 3 if line level setting is Default levels are denoted as follows: –31.4 This specification is always valid for output 2 and 3,
for mic 3 if mic level setting is selected. selected. and for output 1 at volume setting 15.

Audio inputs 4–6 Note: Audio inputs 4–6 are referred to as Line
Tip: To convert dBu values to dBV, subtract
input 1–3 in the API.
2.2 dB from the dBu value.
Example: –10 dBu ≡ –12.2 dBV

Note: The input clipping levels and the

absolute max output levels all assume
Microphone sinusoidal signals for the dBu values.
inputs 1–3 Audio outputs 1–3

D 13887.09
APRIL 2009 31
Interfaces and Sockets – Codec 6000 MXP
Video Sockets TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

The system will S-video input Mini-DIN sockets Composite video input RCA sockets PC DVI-I input sockets Note that the S-Video/Composite outputs on the
automatically Main camera Aux. camera Doc. camera VCR (Digital Video Interface, 6000 MXP are now by default turned off from
adapt to a PAL or Integrated digital factory.
NTSC input. and analogue) Ref. xConfiguration Video Outputs TV [1..2] Mode

Single Dual Single Dual Single Dual

S-video output Composite video output DVI output
Mini-DIN sockets RCA sockets sockets
S-video Mini-DIN pin-out
DVI-I pin-out DVI-I Pin-out External view of socket
4 3
Pin Assignment Pin Assignment Pin Assignment
Formats supported on DVI-I out: Levels
1 T.M.D.S. Data 2– 9 T.M.D.S. Data 1– 17 T.M.D.S. Data 0– SVGA (800 × 600) 75 Hz Composite: 1 Vpp, 75 W
XGA (1024 × 768) 60 Hz S-Video (Y/C):
2 T.M.D.S. Data 2+ 10 T.M.D.S. Data 1+ 18 T.M.D.S. Data 0+ SXGA (1280 × 1024) 60 Hz
HD720p (1280 × 720) 50 Hz, 60 Hz Y: 1 Vpp, 75 W 2 1
3 T.M.D.S. Data 2/4 11 T.M.D.S. Data 1/3 19 T.M.D.S. Data 0/5
Shield Shield Shield WXGA (1280×768) 60 Hz C (PAL): 0.3 Vpp, 75 W Pin 1: Ground (Luminance)
Note: TANDBERG supports DVI-D C (NTSC): 0.28 Vpp, 75 W
Single-Link, DVI-A and DVI-I Sin- 4 T.M.D.S. Data 4– 12 T.M.D.S. Data 3– 20 T.M.D.S. Data 5– Formats supported on DVI-I in: Pin 2: Ground (Chrominance)
gle-Link format cables. SVGA (800 × 600) 60 Hz, 72 Hz, 75 Hz, 85 Hz Pin 3: Luminance (Y)
5 T.M.D.S. Data 4+ 13 T.M.D.S. Data 3+ 21 T.M.D.S. Data 5+
XGA (1024 × 768) 60 Hz, 70 Hz, 75 Hz
DVI-D cables transmit digital 6 DDC Clock 14 +5 V power 22 T.M.D.S. Clock SXGA (1280 × 1024) 60 Hz Pin 4: Chrominance (C)
T.M.D.S. signals, DVI-A cables Shield HD720p (1280 × 720) 50 Hz, 60 Hz

transmit analogue VGA signals 7 DDC Data 15 GND 23 T.M.D.S. Clock+ Do as follows to get WXGA:
and DVI-I cables can transmit (return for +5 V, 1 VGA Out Quality must be set to Auto. RCA pin-out
HSync and Vsync) External view of socket
either digital or analogue signals. 2 VGA Monitor Format must be set to Wide.
8 Analogue Vertical 16 Hot plug detect 24 T.M.D.S. Clock– 3 PC Picture Format must be set to Normal.
If your DVI cable is not long Sync If you are using TANDBERG supplied monitors this will give WXGA out Signal GND
enough, use extension cables. when displaying graphics.
C1 Analogue Red C2 Analogue Green C3 Analogue Blue
Observe, however, that the If non-TANDBERG provided displays are used, you must in addition
maximum cable length should not C4 Analogue C5 Analogue GND execute the command:
Horizontal Sync (analogue
exceed 5 m to avoid quality loss. xConfiguration Video Outputs AllowWXGA: On
R, G & B return)

D 13887.09
APRIL 2009 32
Interfaces and Sockets – Codec 6000 MXP
Net Interface Socket TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

HD D-SUB 26 pin-out
External view of socket
1 9
10 18
19 26
Net interface socket. 1 × X.21 / V.35 / RS449
with 1 × RS366 Call Control up to 2 Mbps
RS366 DTE - DCE

Pin Signal Name Description

1 FGND Frame GND

2 DPR Digit Present

3 ACR Abandon Call & Retry

4 CRQ Call Request

5 PND Present Next Digit

6 DLO Data Line Occupied

V.35 DTE - DCE RS449 DTE - DCE 7 NB1 Digit Bit 1

8 NB2 Digit Bit 2

Pin Signal Name Description Pin Signal Name Description
9 NB4 Digit Bit 4
Note the following:
1 FGND Frame GND on equipment 1 FGND Frame GND 10 NB8 Digit Bit 8
V.10 (RS423). For balanced signals a
11 SD(A) Send Data / Transmit 11 SD(A) Send Data
“0” = low voltage, is defined as terminal
12 SD(B) Send Data / Transmit 12 SD(B) Send Data A positive with respect to terminal B. For
13 RD(A) Receive Data 13 RD(A) Receive Data unbalanced signals a “0” = low voltage, is
defined as terminal positive with respect X.21 DTE - DCE
14 RD(B) Receive Data 14 RD(B) Receive Data
to GND. Cable length for Leased Line
15 SCR(A) Signal Clock Receive 15 RT(A) Receive Timing Pin Signal Name Description
Control should not exceed 20 m.
16 SCR(B) Signal Clock Receive 16 RT(B) Send Timing RS 366. All balanced inputs and outputs 1 FGND Frame GND
17 SCT(A) Signal Clock Transmit 17 ST(A) Send Timing (A and B) use balanced line signals
11 T(A) Send Data / Transmit
18 SCT(B) Signal Clock Transmit 18 ST(B) Send Timing according to V.11 (RS 422), while single
ended signals are in accordance with V.10 12 T(B) Send Data / Transmit
19 GND1 Signal GND 19 GND1 GND
(RS423). The “0” = low voltage definitions 13 R(A) Received Data / Receive
22 RLSD(CD) Received Line Signal 20 TR(A) Terminal Ready are the same as for V.10 above. Max 14 R(B) Received Data / Receive
Detector  / Carrier Detect
21 TR(B) Terminal Ready cable length, as for V.10 above.
15 S(A) Signal Element Timing
23 RLSD(GND)1 Signal GND
22 RR(A) Carrier Detect / Receiver Ready
16 S(B) Signal Element Timing
24 RI Ring Indicator
23 RR(B) Carrier Detect / Receiver Ready
20 C(A) Terminal Ready / Control
25 LOS Loss of Signal (KG194)
24 IC Incoming Call
21 C(B) Terminal Ready / Control
26 DTR Data Terminal Ready
25 LOS Loss of Signal (KG194)
22 I(A) Carrier Detect
1) This pin is connected to ground for correct Frame GND is connected to pin 1 on DTE
operations 23 I(B) Carrier Detect
1) This pin is connected to ground for correct operations

D 13887.09
APRIL 2009 33
Interfaces and Sockets – Codec 6000 MXP
Network Interface Sockets TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Tip! Wherever applicable, the use

of Category 5 cabling or better is ISDN PRI interface. 1 × PRI (RJ-45 Jack) Primary E1/T1 Interface
strongly recommended! For HD camera Rate & Leased Line E1/T1 (G.703) Interface up to
PRI Pin-Out Crossover
applications, however, Category 7.5 is 2 Mbps. 1 × PRI (RJ-45 Jack) Primary Rate (for future PRI cable
required. use). Use any standard PRI cable to connect the
Codec to PRI. Pin 1 RX+ 4
Pin 2 RX– 5
Pin 4 TX+ 1
Pin 5 TX– 2

Ethernet LAN (RJ-45 Jack) interface (10/100 Mb).

Up to 4 or 6 Mbps, depending on the bandwidth op-
tion installed. Use any standard Ethernet cable to
connect the Codec to a LAN.
S/T Interface If no LAN is available and the Codec is connected
ISDN BRI interface. ISDN I.420
directly to a computer, use a crossover cable.
(RJ-45 Jack) Basic Rate Interface
BRI Pin-Out
S/T (2B + D), 128 kbps per ISDN Ethernet cable
Pin 3 TX+ I/F. Use any standard BRI cable 1 ---------- 1 1 1
to connect the Codec to BRI.
Pin 4 RX+ 2 ---------- 2 2 2
Pin 5 RX– 3 ---------- 3 3 3
Pin 6 TX– 6 ---------- 6 6 6
Wiring diagram Wiring diagram
standard cable crossover cable

RJ-45 Connector pin-out

Tip! If you connect your Codec directly to a PC, make sure you set up
the system to use static TCP/IP settings. There will be no DHCP server
controlling the little LAN created by the computer and the Codec. When
configuring a back-to-back connection between the PC and the Codec,
make sure both static IP addresses exist on the same subnet.

D 13887.09
APRIL 2009 34
Interfaces and Sockets – Codec 6000 MXP
Camera Sockets TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Tip! Wherever applicable, the use

of Category 5 cabling or better is
strongly recommended! For HD camera
applications, however, Category 7.5 is
required.

S-video Mini-DIN pin-out

External view of socket
4 3

2 1
Pin 1: Ground (Luminance) 9-pin D-sub pin-out
TANDBERG WAVE II TANDBERG HD 6000
Pin 2: Ground (Chrominance) Camera cable pin-out Camera cable pin-out External view of socket
Pin 3: Luminance (Y) SIGNAL RJ-45 DSUB SIGNAL RJ-45 DSUB 5 1
NAME NAME
Pin 4: Chrominance (C)
+12V DC 8 4 +12V DC 1 Twisted 4

GND 7 5 GND 2 pair 5

9 6
+12V DC 3 4 Rx 3 Twisted 2

TXD 4 3 TX 6 pair 3

RXD 5 2 LVDS+ 4 Twisted 1

GND 6 5 LVDS– 5 pair 6

GND 2 5 GND 7 Twisted 5

+12V DC 1 4 +12V DC 8 pair 4 RJ-45 Connector pin-out

Cable is Category 7.5/ Class F AWG24.

Extreme care should be taken if you choose
to make your own version of this cable!

D 13887.09
APRIL 2009 35
Interfaces and Sockets – Codec 6000 MXP
Data Ports TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

9-pin D-sub pin-out

External view of socket
5 1

9 6

Data Ports
Data port 1 Data port 2

Pin Signal name Direction Signal name Direction USB interface. Data port 1 (upper) and 2 (lower). The Data ports
From DCE Carrier detect, From DCE
For future use. are implemented as Digital Circuit Terminating
1 Carrier detect,
CD CD Equipment (DCE).
2 Receive data, From DCE Receive data, From DCE Note! The TANDBERG main camera is normally
RXD RXD connected to data port 2 and pin No. 4 provides
3 Transmit data, To DCE Transmit data, To DCE 12 Vdc / 1 A to the main camera. Otherwise the pin-
TXD TXD outs are the same for the two data ports.
41 Data terminal From DCE 12 V / 1 A
ready, DTR

5 Signal GND Signal GND

6 Data set ready, From DCE Data set ready, From DCE
DSR DSR

7 Ready to send, To DCE Ready to send, To DCE

RTS RTS

8 Clear to send, From DCE Clear to send, From DCE

CTS CTS

9 Ring indicator, From DCE Ring indicator, From DCE

RI RI

1) The TANDBERG main camera is normally connected to data port 2 and pin No. 4
provides 12 Vdc / 1 A to the main camera. Otherwise the pin-outs are the same for the
two data ports.

D 13887.09
APRIL 2009 36
Interfaces and Sockets – Codec 6000 MXP
Power Socket & On/Off Switch TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Caution! This equipment must

be earthed!

Power cord socket

Accepts 100–240 V 50–60 Hz
1 A max.

Power switch

D 13887.09
APRIL 2009 37
 About the TANDBERG API
We recommend that you check out the The heart of the API is the TANDBERG API-Engine. This is
TANDBERG web site regularly for updated
versions of this manual: where all information is stored and processed. The API-
http://www.tandberg.com/docs engine can be accessed by an easy-to-use Command Line
Interface called XACLI using RS 232 or Telnet, or by the
TANDBERG XML API Service (TXAS) over HTTP/HTTPS.
Both alternatives are described in detail in this section of
the User Guide.
About the TANDBERG API
Introduction TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Basic Principles The TANDBERG API Engine

The heart of the API is the TANDBERG The TANDBERG API-Engine is optimized for easy, yet advanced, machine- A command is usually followed by a set of parameters to specify how the given
API-Engine. This is where all information is machine interaction between a TANDBERG system and an external control action is to be executed.
stored and processed. The API-engine can application.
be accessed by an easy-to-use Command (RW) Read-Write information. This is Configuration Information defining sys-
Line Interface called XACLI using RS 232 The main features can be summarized to: tem settings. This information can both be supplied and read by the user/con-
or Telnet, or by the TANDBERG XML API • Structuring of information trol application. Typical examples include: default call rate, baud rate of a serial
Service (TXAS) over HTTP/HTTPS. • Addressing using XPath (XML Path Language) or TANDBERG SimplePath port, enabling/disabling of various features etc.
• Feedback All configuration information is structured in a hierarchy making up a database
of system settings. But for the Configuration information, the data in the data-
XACLI TXAS
Structuring of Information base can only be updated by the user/control application.
An application programming interface (API) can be seen as a gate where infor-
mation is exchanged between two systems – a control application and a target Addressing Using XPath or TANDBERG SimplePath
system. To address information in the hierarchic structure of Status and Configuration
RS 232 HTTP
Telnet HTTPS The control application transmits instructions to the target system, while the information, the TANDBERG systems support abbreviated XML Path Language
target system supplies information about how these instructions are executed, (XPath) and a proprietary notation called TANDBERG SimplePath (only available
in addition to other system related information. using XACLI).
API-Engine Consequently, the exchange of information can be divided into: This allows the user/control application to address everything from a single
element of data (for example the call rate of a specific call) to larger parts of the
1. Information flowing from target. This we call read information (R). The (R) hierarchy (for example all information available for a given call).
should not be confused with the (r) used to indicate required parameters in
the Commands tables.
Working with the API-engine is very similar 2. Information flowing to target. This we call write information (W). Feedback
to working with catalogues and files on a Feedback is an extremely powerful feature where the TANDBERG system
computer. All information is stored in a hi- actively returns updated status and configuration information to the user/
If we now look at the TANDBERG systems we can identify three main types of
erarchic tree structure which is accessible control application whenever changes occur.
information
from different interfaces.
• read information (R) The user/control application can specify what parts of the status and configura-
When accessing the API-engine using tion hierarchies it wants to monitor by using XPath. The user/control application
• write information (W)
XACLI (RS 232 or Telnet), the information can thereby limit the amount of information it receives from the target system to
• read-write information (RW)
is formatted in a proprietary Command Line only those parts being of interest for the given application. This will also reduce
style or in XML formatting. (R) Read information. This is Status Information about the system and system the load on the link connecting the systems.
When accessing the API-engine using the processes, i.e. information generated by the system. Feedback is supported on both XACLI (RS232/Telnet) and TXAS (HTTP/
TXAS interface (HTTP/HTTPS), XML/SOAP Typical examples include: status about ongoing calls, network status, confer- HTTPS) simultaneously.
formatting is supported. ence status etc. The system uses TANDBERG SimplePath when presenting configurations.
This is similar to viewing files on a compu- All status information is structured in a hierarchy, making up a database con- XPath and TANDBERG SimplePath are described more thoroughly later in this
ter; accessing catalogues on a Windows stantly being updated by the system to reflect process changes. section of the manual.
computer using the Command Prompt
gives a different view than using Windows (W) Write information. This is Command Information the user/control applica- The structuring of information together with XPath and TANDBERG SimplePath
Explorer, but the information is the same. tion supply to initiate an action. for addressing, makes up powerful features like searchability and setting of
Typical examples include: instructing the system to place a call, assigning floor multiple instances of a configuration.
NOTE! New features on the TANDBERG
MXP will be supported on XACLI only. to a specific site, disconnecting a call etc. Examples are provided overleaf.

D 13887.09
APRIL 2009 39
About the TANDBERG API
XACLI and the classic data port commands TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

What Happened to the RS 232/Telnet Dataport

Interface Supported on the Classic Systems? Example 1 Example 2

The TANDBERG MXP also supports the RS 232/Telnet Da- Example showing Serial Port configurations of a TANDBERG Example: To address the BaudRate element of serial port 2:
taport Interface that was supported on the Classic systems. 6000 MXP codec, using the standard XACLI formatting for XPath
You may use any mixture of Classic Dataport commands and configurations:
Each level is separated with a slash (‘/’). Item numbers are
XACLI commands on the same RS232/Telnet session. A xconfiguration serialport added in brackets after the element name:
multitude of the commands overlaps, but XACLI offers more
flexibillity and gives access to the latest features supported *c xConfiguration SerialPort 1 BaudRate: SerialPort[2]/BaudRate
by the system. 57600 Example
We recommend the use of XACLI commands whenever *c xConfiguration SerialPort 1 Parity: None xconfiguration serialport[2]/baudrate
you write new control system modules and whenever you add
new features into existing control modules, but there is no *c xConfiguration SerialPort 1 DataBits: 8 *c xConfiguration SerialPort 2 BaudRate: 9600
need to to rewrite already existing control modules based on *c xConfiguration SerialPort 1 StopBits: 1 OK
Classic commands.
The XACLI API is described in detail in this section of the User *c xConfiguration SerialPort 1 Mode: Control
Guide. The Classic Dataport Interface is described in the TANDBERG SimplePath
*c xConfiguration SerialPort 2 BaudRate: 9600
TANDBERG 770-8000MXP API (Dataport User Guide), which is Both levels and item numbers are separated with whitespac-
available separately. *c xConfiguration SerialPort 2 Parity: None es:
NOTE! New features on the TANDBERG MXP will be sup- *c xConfiguration SerialPort 2 DataBits: 8 SerialPort 2 BaudRate
ported on XACLI only. Example
*c xConfiguration SerialPort 2 StopBits: 1
Example: To configure the baudrate of serial port 1 to xconfiguration serialport 2 baudrate
9600: *c xConfiguration SerialPort 2 Mode: Auto
*c xConfiguration SerialPort 2 BaudRate: 9600
Classic Dataport: sport data1 9600 OK OK
XACLI: xconfiguration serialport 1 baudrate:
9600

D 13887.09
APRIL 2009 40
About the TANDBERG API
XACLI TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Accessing XACLI Hardware & Cabling (RS 232) Data Port (RS 232)

XACLI can be accessed through Telnet via the LAN interface The pin outs for the RS 232 are defined in the tables to the
or through RS 232 by connecting a serial cable to the serial right. Observe that the DTE (Data Terminal Equipment), could Pin Signal name Direction
interface connector, referred to as the Dataport. Eight Telnet be a PC or any other device capable of serial communica- 1 Carrier detect, CD From DCE
sessions can be connected to the TANDBERG MXP simulta- tion.
2 Receive data, RXD From DCE
neously, in addition to the RS 232 connection. NOTE! A straight-through cable should be used between the
TANDBERG MXP’s RS 232 port and the DTE. 3 Transmit data, TXD To DCE
The lower table shows the recommended cable-wiring 4 Data terminal ready, DTR From DCE
scheme when connecting the TANDBERG MXP to a PC
5 Signal GND
through RS 232.
Connecting to XACLI using the Dataport (RS 232) 6 Data set ready, DSR From DCE
DTR and RTS are ignored. DSR, CD, and CTS are always as-
serted, while RI is not used. 7 Ready to send, RTS To DCE
8 Clear to send, CTS From DCE
The RS 232 port is a 9-pin, female, D-sub connector located
on the back of the TANDBERG MXP. The port is configured 9 Ring indicator, RI From DCE
as a DCE (Data Communications Equipment). The RS 232
port is default set to 9600 baud, 8 data bits, none parity
and 1 stop bit from factory. The RS 232 port is also referred
to as the Dataport.

Troubleshooting (RS 232) Cable wiring TANDBERG MXP ↔ PC via RS 232

The RS 232 Dataport on the 6000 MXP Codec

If communication cannot be established between the PC/

terminal and the TANDBERG MXP’s Dataport, the following TANDBERG MXP Direction PC
should be checked: DCE, 9 pin DTE, 9 pin
• Verify that the serial cable is a straight-through 9-pin to 1 CD → 1 CD
The RS 232 Dataport on the 3000 MXP Codec 9-pin cable
2 RD → 2 RD
• Confirm that the configuration of the PC/terminal’s
serial RS 232 port is identical to the configuration of the 3 TD ← 3 TD
TANDBERG MXP RS 232 port. 4 DTR ← 4 DTR
• Verify that the PC/terminal’s serial RS 232 port is working 5 GND ↔ 5 GND
properly by connecting it back-to-back to another PC/
See also the pages on the 3000 MXP Dataports and the terminal and send characters in both directions. 6 DSR → 6 DSR
6000 MXP Dataports in this User Guide. Note that one of 7 RTS ← 7 RTS
the RS 232 ports of the 6000 MXP Codec (the lower) is used
8 CTS → 8 CTS
as a camera control socket.
9 RI → 9 RI

D 13887.09
APRIL 2009 41
About the TANDBERG API
XACLI – the Basics TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

?
Root Commands - User Commands -
about dumph221 layout-keyboard prisearch
access duovideo localdn protect
By typing ? or help after connecting to the aim echoctrl los-duration rinfo
TANDBERG MXP using RS 232/Telnet, the alrtvol enable los-inhibit rnumber
system will list all supported root com- ansdelay encmode los-initial screensaver
mands. audioagc encrypt los-polarity selfview
audiofeature encstatus los-retry sendnum
All root commands prefixed with an x
audiofeedback eventlog maxcall services
belongs to the XACLI interface. These are
audioin extcam mcucommand snmp
shown in orange colour in the table to the audiolevel extcap mcudirectory spid
right. All other root commands belong to audiomix extname mculine spkr
the Classic Dataport Interface (described in audiomodule extswitch mcustat sport
a separate document). audioout fallback menupassword sstring
NOTE! Classic Dataport commands and autoans fecc mic statin
XACLI commands can be used side by side. automute feedback monstat statout
However, the use of XACLI commands is autopip feinfo msn still
recommended whenever writing new control beep fevidsrc multisite streaming
system modules and whenever adding new bondingtimer g703settings netclock strictpassword
features into existing control modules, but boot globdirectory netctrl sub
there is no need to rewrite existing code callstatus h239 netdtrpulse syslog
based on the Classic commands. camcenter h323alias netisdn systemname
cammove h323callmanager netpri telephony
Note! New features on the TANDBERG campos h323gatekeeper netprofile teltone
MXP will be supported on XACLI only. camsettings h323mtu netstat test
camsleepmode h323nat nettype traceroute
camtrack h323ports optionkey vgaout
chanstat h323prefix pardial vidfeature
chat h323qos ping vidin
custominfo h323rate pip vidname
defcall h323status pldownspeed vidtone
defvalues h331mode preset-activate vnc
delbox help preset-list vol
dial ifconfig preset-store websnapshots
directory ipaddress pressource xcommand
disable ipassignment pricable xconfiguration
disc ipconflictcheck pricrc4 xdirectory
dispbox iplr prihighch xevent
dispparam ippassword prilowch xfeedback
disptxt irctrl primaxchan xgetxml
dltxt isdntrace prinsf xhistory
donotdist key prinumber xpreferences
downspeed language prinumbrange xstatus
dualmon
OK

All root commands prefixed with an ‘x’ belong to the XACLI interface.

D 13887.09
APRIL 2009 42
About the TANDBERG API
XACLI – Main Types of Commands TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

About Main Types of Commands Configuration Type Commands Status Type Commands Command Type Commands

The XACLI is divided into three main types Commands defining system settings. Commands returning information about Commands instructing the system to per-
of commands (and a fourth – see below), Configuration-type commands are either the system and system processes, i.e. form an action. E.g. instructing the system
reflecting the information types supported supplied or read by the user. E.g. default information generated by the system. E.g. to place a call, assigning floor to a specific
by the TANDBERG API Engine. callrate, baudrate of a serial port, ena- status about ongoing calls, network status, site, disconnecting a call etc. A command
bling/disabling of various features etc. conference status etc. All status informa- is usually followed by a set of parameters
The main types are: tion is structured in a hierarchy, making up to specify how the given action is to be
All Configurations are structured in a
• Configuration-type commands hierarchy making up a database of system a database constantly being updated by executed.
• Status-type commands settings. the system to reflect system and process
• Command-type commands changes. Supported Command-type commands:
Supported Configuration-type commands: • xCommand
Supported Status-type commands:
• xConfiguration
• xStatus
• xDirector y
• xHistor y
• xEvent

Special Commands

In addition to the above sets of commands, xfeedback is a command used to specify xpreferences is used to set various prefer- xgetxml gives access to the exact same
XACLI supports the following set of special what parts of the configuration and status ences for the RS 232/Telnet sessions. Each information as the Main types of commands
commands: hierarchies to monitor. Feedback will only session can define preferences individually. (xstatus, xhistory, xconfiguration etc.), but
be issued on the RS 232/Telnet for which it IMPORTANT! This command has various returns the information XML formatted.
is specified. If connecting to the TANDBERG settings to define the formatting of the XACLI More on this can be found in xgetxml.
MXP with multiple RS 232/Telnet sessions, output. It is therefore important to define set-
each session can define feedback individu- tings to match the parser used on the control
ally. system. XACLI is designed to make parsing of
More on this can be found in xfeedback. data from the TANDBERG MXP very simple.
More on this can be found in xpreferences.

D 13887.09
APRIL 2009 43
About the TANDBERG API
XACLI – Configuration Type Commands TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

xconfiguration ?
About Configuration Type Commands
- User Configurations -
AdditionalCamera FTP PacketlossDownSpeed
All Configurations are organized in a hierarchic tree structure.
AlertSpeaker G703 PictureProgram [1..4]
To get an overview of accessible top-level configuration elements within a AlertTone H320 PresentationSoftkey
configuration-type command, type ? or help after the configuration-type com- AllowLatency H323 PresentationStart
mands (xconfiguration/xdirectory), as shown in the example to the right. Audio H323CallSetup Preset [1..15]
AutoAnswer H323Gatekeeper QoS
Tip! To list all supported configurations with corresponding valuespace: AutoDisplaySnapshot H323Prefix RemoteSwUpgrade
xConfiguration ?? AutoLayout HTTP Robotron
AutoPIP HTTPS RTP
Configurations consists of three parts: Bonding IdReport Screensaver
CallManager IEEE802.1x Security
1. A Configuration-type command (xConfiguration or xDirectory) CallVideoSource IMUX SecurityLog
2. A Configuration path (address-expression) Camera [1..13] Integrator SelfViewOnStartup
3. A Configuration value CameraDVI IP SerialPort [1..2]
CameraReverseControl IPMedia SIP
CameraSleep IPProtocol SNMP
Configuration-type command Configuration value CameraSwUpgrade IRControl SSH
CameraTracking ISDN StartupVideoSource
xConfiguration H323Gatekeeper Discovery: Manual Conference KeepDuoOpen StillImageSource
CorporateDirectory Key Streaming
Configuration path DefaultPIPPosition Keyboard StrictPassword
Directory Kiosk Switch
DoNotDisturb LocalLayout SystemUnit
DualMonitor Logo T1
DuoVideoSource LoS Telnet
DynamicResolution MainVideoSource TelnetChallenge
E1 MaxBandwidth ThreePartyLayout
Ethernet Multipoint Time
ExternalManager NAT TURN
ExternalNetwork NetProfile [1..7] UseAsLocalPCMonitor
ExternalServices NTP Video
FECC OptionKey VNC
FeedbackFilter OSD
OK

xdirectory ?

- Directory -
GlobalEntry [1..400] LocalEntry [1..200]
GroupEntry [1..50]
OK

D 13887.09
APRIL 2009 44
About the TANDBERG API
XACLI – Configuration Type Operation TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

About Configuration Operations Configuration Help Configuration Read

Three operations can be performed on To get help on configurations, type ? after the configuration path To read configurations from the system just type the root command
configurations: (address expression): (xConfiguration/xDirectory) followed by the path (address
• Configuration Help <configuration-type command> <address expression> ? expression):
• Configuration Read <configuration-type command> <address expression>
• Configuration Set (Write) Example:
xconfiguration h323gatekeeper discovery ? Example:
*h xConfiguration H323Gatekeeper Discovery: <Manual/Auto> xconfiguration h323gatekeeper discovery
OK *c xConfiguration H323Gatekeeper Discovery: Manual
OK

Note! Configuration Set (Write)

Type a root command (xConfiguration/xDirectory) followed by

• *h is used when returning the result a valid path (address expression). The path must be terminated with a
of a help query colon before the value is added.
• *c is used when returning the result
of a read query <configuration-type command> <address expression>: <value>
• Nothing is used for configuration set Example:
• *d is used when returning the result xConfiguration H323Gatekeeper Discovery: Manual
of an xdirectory read query.

D 13887.09
APRIL 2009 45
About the TANDBERG API
XACLI – Configuration Types TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

About Configuration Types Format for Value Types

Integer values:<x..y>
The system supports the following value
Defines the valid range for an integer input. x = min value, y = max value.
types:
<1..100>
• Integer values
• Literal values Literal values: <X/Y/../Z>
• String values Defines the possible values for a given configuration.
• E164 string values (strings only contain- <On/Off/Auto>
ing digits, ‘#’ and ‘*’)
• IPv4 Address values String values: <S: x, y>
Defines that the valid input for this configuration is a String with minimum length x and maximum length of y characters.
• IPv6 Address values
<S: 0, 49>
• IPv4 or IPv6 Address values
IPv4 Address values: <IPAddr>
Defines that the input must be an IPv4 address.
<IPAddr>

IPv6 Address values: <IPv6Addr: x, y>

Defines that the input must be an IPv6 address with minimum length x and maximum length y.
<IPv6Addr: 0, 43>

IPv4 or IPv6 Address values: <IPv4v6Addr: x, y>

Defines that the input must be an IPv4 or IPv6 address with minimum length x and maximum length y.
<IPv4v6Addr: 0, 43>

D 13887.09
APRIL 2009 46
About the TANDBERG API
XACLI – Command-type Commands – xcommands/xdirectory TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Getting an Overview Example Showing How to Get an Overview of Supported Commands

To get an overview of the supported command-type commands, type ? or help after the com- xcommand ?
mand-type command (xcommand) .
Tip! To list all supported configurations with corresponding valuespace: - User Commands -
xcommand ?? AlertToneTest DefaultValueSet LocalEntryAdd
AudioTestSignal Dial LocalEntryDelete
Boot DialGlobalEntry MessageBoxDelete
CallAccept DialGroupEntry MessageBoxDisplay
CallHold DialLocalEntry PIPHide
Command help CallJoin DisconnectCall PIPShow
CallMute DTMFSend PresenceForce
CallMuteOutgoing DuoVideoStart PresetActivate
To get help on a specific command, type the command-type command (xcommand) – then a CallResume DuoVideoStop PresetClear
command name followed by ? or help: CallSetAudioTP FECCFocus PresetStore
<command-type command> <command name> ? CallTransfer FECCMove ProfileActivate
CameraFocus FECCPresetActivate ProfileCreate
Example: CameraForceUpgrade FECCPresetStore ProfileDelete
xcommand dial ? CameraHalt FECCRequestStill ProfileList
CameraMove FECCSelectSource ScreensaverActivate
*h xCommand Dial CameraPosition FeedbackDeregister ScreensaverDeactivate
Number: <S: 0, 60>
CameraReConfigure FeedbackRegister ScreensaverReset
SecondNumber: <S: 0, 60>
CameraTrackingStart FIPSMode SiteDisconnect
SubAddress: <S: 0, 20>
CallRate: <Tlph/1xh221/2xh221/64/128/…/4096/Max/Auto> CameraTrackingStop FloorRelease SiteView
Restrict: <On/Off> CameraUpgrade FloorRequest SiteViewEnd
NetProfile: <1..7> CameraWhitebalance FloorToSite SPIDAutoConfigure
BillingCode: <S: 0, 16> ChairRelease FloorToSiteEnd SStringSend
ChairTake GroupAddEntry StillImageSend
NOTE! Required parameters are identified by an (r) behind the parameter name. ConferenceDisconnect GroupEntryDelete StreamingStart
ConferenceMoveToMCU KeyDisable StreamingStop
Example:
ConferenceTerminate KeyDown TextDelete
xcommand cameramove ?
CorpDirGetNext KeyEnable TextDisplay
CorpDirGetPrevious KeyPress VirtualMonitorReset
*h xCommand CameraMove
Camera(r): <1..4> CorpDirSearch KeyRelease VirtualMonitorSet
Direction(r): <Up/Down/Right/Left/In/Out>
OK
OK

D 13887.09
APRIL 2009 47
About the TANDBERG API
XACLI – Command-type Commands – Issuing a Command TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Issuing a Command Command Response

A command must start with the command-type command (xcommand), followed by a command name, followed When issuing a command, the system will return a set of return values. The
by a set of parameters. Parameters values are identified by specifying the parameter name followed by a ‘:’ response will by default be on the same format as the standard XACLI Status
<command-type command> <command name> <parameter:value> <parameter:value>... format. The other supported status formats (completepath/XML) are also
supported – ref. xpreferences.
Example: Example
xcommand dial 558458
xcommand dial number:558458 restrict:on callrate:128 subaddress:10
*r Result (status=OK):
CallRef: 1
If there are multiple instances of a parameter, the item number is added after the tag separated with a dot: LogTag: 6
<command-type command> <command> <parameter.item:value> <parameter.item:value>... *r/end
OK
Example: If complete path is enabled for the RS-232/Telnet session
xcommand groupentryadd name:TANDBERG localentryid.1:15 localentryid.2:57 (“xpreferences completepath on”):
Example
xcom dial 558458
*r Result (status=OK):
*r Result CallRef: 1
Sequence Notation (Optional) *r Result LogTag: 4
OK

<command-type root command> <command> <value> <value>...

When using this notation the parameter values must be entered in the sequence as stated in the help text:

Example: Combination of Markup Notation and Sequence (Optional)

*h xCommand Dial
Number: <S: 0, 60>
A combination of markup notation and sequence is also supported. The
SecondNumber: <S: 0, 60> marked parameters will be assigned the user entered values first, then the
SubAddress: <S: 0, 20> system will assign the sequence entered parameters for the parameters not
CallRate: <Tlph/1xh221/2xh221/64/128/192/256/320/384/H0/512/768/1152/1472/1 yet having been assigned a value:
920/2560/3072/4096/Max/Auto>
Restrict: <On/Off> Example:

NetProfile: <1..7> xcommand dial 666 restrict:on 777 8 128

BillingCode: <S: 0, 16>

To dial a participant with the following properties: Number: 666, SecondNumber:777, SubAddress: 8, CallRate:
128, Restrict: On NOTE! When using XACLI as a machine-machine interface we recommend that
xcommand dial 666 777 8 128 on you use markup notation and always supply complete tag names.

D 13887.09
APRIL 2009 48
About the TANDBERG API
XACLI – Command-type Commands – Parameter Value Types TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Command Parameter Value Types Format for Value Types

The system supports the following value types: Integer values:<x..y>

• Integer values Defines the valid range for an integer input. x = min value, y = max value.
• Literal values <1..100>
• String values
• E164 string values (strings only containing digits, Literal values: <X/Y/../Z>
‘#’ and ‘*’) Defines the possible values for a given configuration.
• IPv4 Address values
<On/Off/Auto>
• IPv6 Address values
• IPv4 or IPv6 Address values
String values: <S: x, y>
Defines that the valid input for this configuration is a String with minimum length x and maximum length
of y characters.

<S: 0, 49>

IPv4 Address values: <IPAddr>

Defines that the input must be an IPv4 address.

<IPAddr>

IPv6 Address values: <IPv6Addr: x, y>

Defines that the input must be an IPv6 address with minimum length x and maximum length y.

<IPv6Addr: 0, 43>

IPv4 or IPv6 Address values: <IPv4v6Addr: x, y>

Defines that the input must be an IPv4 or IPv6 address with minimum length x and maximum length y.
<IPv4v6Addr: 0, 43>

D 13887.09
APRIL 2009 49
About the TANDBERG API
XACLI – Status Type Commands TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

About Status Type Commands Example

Defining Element names, Values, Attributes, and Item No.:
xstatus call 1
All Status information is organized in a *s Call 1 (status=Synced, type=Vtlph, protocol=H323, direction=Outgoing, logTag=1):
hierarchic tree structure. CallRate: 768
RemoteNumber: “558458”
To get an overview of accessible top- Mute: Off
level status elements within a status- Microphone: Off
type command, type ? or help after the Duration: 20
status-type commands (xstatus/xhis- MuteOutgoing: Off
tory/xevent). Channels 1 (type=Incoming):
.
. (some lines have been removed for clarity)
.
Video 2 (status=Inactive): /
Understanding Status Data (status=Inactive): /
Information Structuring *s/end
OK
In the above example. Element names are shown in orange. Values are shown in green. Attributes are shown in magenta. Item No. is shown in cyan
All Status information is organized in a
hierarchic tree structure, very much like
files and folders on a computer. The Example example
tree structure consists of container-
elements (folders) and value elements xstatus ? xhistory ?
(files). Container-elements contains - Status -
- History -
sub-elements, while value elements
contain values. All elements have an Audio FarEndInformation SIP
Call [1..20]
element name and an element item BRI [1..6] Feedback [1..3] SoftwareUpgrade
number. There can exist multiple Call [1..11] G703 Switch OK
instances of an element. Camera [1..13] H323Gatekeeper SystemUnit xevent ?
An element can also have various CameraSwUpgrade ICE [1..11] Video
attributes. Attributes are used to add CameraTracking IP VirtualMonitor [1..4] - Event -
meta information to an element. The AuthenticationFailure MessageBoxResult
Conference NTP VNC
sub-structure of a container-element may CallDisconnected PacketlossDownSpeed
Ethernet [1..2] PRI Warnings [1..10]
vary depending on the attribute values. CallStatisticsIP [1..11] SString
The relationship between attribute values ExternalManager RemoteSwUpgrade
CallSuccessful SystemActivity
of a given element and its underlying sub- ExternalNetwork ScreenSaver DownspeedingFinished
structure can be read from the sections
documenting the various status elements. OK
OK
E.g. a call that is disconnected does not
contain any data (except a disconnect
cause value), while an active call contains
information about bandwidths, protocols,
channels etc.

D 13887.09
APRIL 2009 50
About the TANDBERG API
XACLI – Status Type Commands – Default Formatting TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Example showing status for a disconnected call.

About Status Type Commands Formatting
xstatus call 1
*s Call 1 (status=Disconnected, type=NA, protocol=NA, direction=NA, logTag=NA):
Cause: 16
XACLI supports three different formattings for status
*s/end
information:
OK
• Default XACLI formatting, provides good human
readability, compact format. However, a custom parser
must be used
Example showing status for an active call.
• Complete Path formatting. Recommended when parsing
the information line by line. xstatus call 1
• XML formatting – to be used when using an XML-parser. *s Call 1 (status=Synced, type=Vtlph, protocol=H323, direction=Outgoing, logTag=2):
CallRate: 768
RemoteNumber: “558458”
Mute: Off
Microphone: Off
Duration: 10
Default XACLI Formatting MuteOutgoing: Off
Channels 1 (type=Incoming):
Rate: 768
Restrict: Off
• The root-element is prefixed with *s (for status), *e (for Encryption (status=Off): /
event), or *l (for history log) Audio (status=Active):
• Root-element end is designated by a *s/end (*e/end Protocol: G722
or *l/end respectively) Rate: 64
• To write a parser for this format, the parser must keep Video 1 (status=Active):
track of the levels by counting white spaces. The indent Protocol: H264
is increased by two whitespaces for each level. Unless Resolution: CIF
link throughput is an issue, we recommend the use Rate: 704
of Complete Path Formatting instead of Default XACLI Video 2 (status=Inactive): /
formatting when parsing information sent from the codec. Data (status=Inactive): /
Channels 2 (type=Outgoing):
Rate: 768
Restrict: Off
Encryption (status=Off): /
Audio (status=Active):
About the Examples Provided Here Protocol: G722
Rate: 64
Video 1 (status=Active):
Protocol: H264
From the example showing status for a disconnected call
Resolution: CIF
(upper right), we can see that the call element now only
Rate: 704
contains one element; the value-element Cause. The sub-
Video 2 (status=Inactive): /
elements that were present when the call was active (lower
Data (status=Inactive): /
right example) are no longer valid (i.e. it makes no sense to
*s/end
ask for outgoing video resolution for a disconnected call).

D 13887.09
APRIL 2009 51
About the TANDBERG API
XACLI – Status Type Commands – Complete Path Formatting TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Example
About Status Type Commands Formatting

xpreferences completepath on
XACLI supports three different formattings for status
information: OK
xstatus call 1
• Default XACLI formatting, provides good human
readability, compact format. However, a custom parser
*s Call 1 (status=Synced, type=Vtlph, protocol=H323, direction=Outgoing, logTag=2):
must be used
*s Call 1 CallRate: 768
• Complete Path formatting. Recommended when parsing *s Call 1 RemoteNumber: “558458”
the information line by line. *s Call 1 Mute: Off
• XML formatting – to be used when using an XML-parser. *s Call 1 Microphone: Off
*s Call 1 Duration: 527
*s Call 1 MuteOutgoing: Off
*s Call 1 Channels 1 (type=Incoming):
*s Call 1 Channels 1 Rate: 768
*s Call 1 Channels 1 Restrict: Off
About Complete Path formatting
*s Call 1 Channels 1 Encryption (status=Off): /
*s Call 1 Channels 1 Audio (status=Active):
*s Call 1 Channels 1 Audio Protocol: G722
The following should be observed: *s Call 1 Channels 1 Audio Rate: 64
*s Call 1 Channels 1 Video 1 (status=Active):
• Complete Path formatting is recommended for easy *s Call 1 Channels 1 Video 1 Protocol: H264
parsing *s Call 1 Channels 1 Video 1 Resolution: CIF
• All lines are prefixed with *s (for status), *e (for event), *s Call 1 Channels 1 Video 1 Rate: 704
or *l (for historylog) *s Call 1 Channels 1 Video 2 (status=Inactive): /
• The complete path to an element is supplied on all lines *s Call 1 Channels 1 Data (status=Inactive): /
*s Call 1 Channels 2 (type=Outgoing):
• The parser can work line by line *s Call 1 Channels 2 Rate: 768
• Root-element end is designated by a *s/end (*e/end or *s Call 1 Channels 2 Restrict: Off
*l/end respectively). *s Call 1 Channels 2 Encryption (status=Off): /
*s Call 1 Channels 2 Audio (status=Active):
NOTE! Complete Path formatting is enabled by: “xprefer- *s Call 1 Channels 2 Audio Protocol: G722
ences completepath on”, described later in this section of *s Call 1 Channels 2 Audio Rate: 64
the User Guide. *s Call 1 Channels 2 Video 1 (status=Active):
NOTE! the xpreferences is a session specific command and *s Call 1 Channels 2 Video 1 Protocol: H264
must be issued every time the control application connects *s Call 1 Channels 2 Video 1 Resolution: CIF
to the codec. *s Call 1 Channels 2 Video 1 Rate: 704
*s Call 1 Channels 2 Video 2 (status=Inactive): /
*s Call 1 Channels 2 Data (status=Inactive): /
*s/end

OK

D 13887.09
APRIL 2009 52
About the TANDBERG API
XACLI – Status Type Commands – XML Formatting TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Example
About Status Type Commands Formatting
xgetxml status/call[1]
<Status>
XACLI supports three different formattings for status <Call item=”1” status=”Synced” type=”Vtlph” protocol=”H323” direction=”Outgoing” logTag=”2”>
information: <CallRate item=”1”>768</CallRate>
<RemoteNumber item=”1”>558458</RemoteNumber>
• Default XACLI formatting, provides good human <Mute item=”1”>Off</Mute>
readability, compact format. However, a custom parser
<Microphone item=”1”>Off</Microphone>
must be used
<Duration item=”1”>887</Duration>
• Complete Path formatting. Recommended when parsing <MuteOutgoing item=”1”>Off</MuteOutgoing>
the information line by line. <Channels item=”1” type=”Incoming”>
• XML formatting – to be used when using an XML-parser. <Rate item=”1”>768</Rate>
<Restrict item=”1”>Off</Restrict>
<Encryption item=”1” status=”Off”/>
<Audio item=”1” status=”Active”>
<Protocol item=”1”>G722</Protocol>
<Rate item=”1”>64</Rate>
About XML Formatting
</Audio>
<Video item=”1” status=”Active”>
<Protocol item=”1”>H264</Protocol>
The following should be observed: <Resolution item=”1”>CIF</Resolution>
<Rate item=”1”>704</Rate>
• To be used when the control application is using an XML </Video>
parser
<Video item=”2” status=”Inactive”/>
• XML formatting is used when polling for information using <Data item=”1” status=”Inactive”/>
the special command xgetxml, described later in this sec- </Channels>
tion of the manual. <Channels item=”2” type=”Outgoing”>
• To enable XML formatting on feedback issued from the <Rate item=”1”>768</Rate>
codec, the special command xpreferences should be <Restrict item=”1”>Off</Restrict>
used. <Encryption item=”1” status=”Off”/>
<Audio item=”1” status=”Active”>
<Protocol item=”1”>G722</Protocol>
<Rate item=”1”>64</Rate>
</Audio>
<Video item=”1” status=”Active”>
<Protocol item=”1”>H264</Protocol>
<Resolution item=”1”>CIF</Resolution>
<Rate item=”1”>704</Rate>
</Video>
<Video item=”2” status=”Inactive”/>
<Data item=”1” status=”Inactive”/>
</Channels>
</Call>
</Status>
OK

D 13887.09
APRIL 2009 53
About the TANDBERG API
XACLI – Status Type Commands – Addressing Status Information TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

About Addressing Status Information Example 1 a) Addressing status information, user wants to know callrate of call 1:
xstatus call 1 callrate
*s Call 1 (status=Synced, type=Vtlph, protocol=H323, direction=Outgoing, logTag=3):
CallRate: 768
You address status information by supplying a status-type *s/end
command followed by an address-expression (XPath or
OK
TANDBERG SimplePath):
<status-type command> <address expression>
See example 1 a) for an illustration.
Example 1 b) xpreferences completepath set to on:
If complete path is enabled for the RS 232/Telnet session xstatus call 1 callrate
(xpreferences completepath on), it will look like
example 1 b). *s Call 1 (status=Synced, type=Vtlph, protocol=H323, direction=Outgoing, logTag=3):
As a second set of examples let us consider a situation *s Call 1 CallRate: 768
where the user wants to know Audio status for both incoming
OK
and outgoing channels for Call 1. This is shown in examples
2 a) and 2 b).

Example 2 a) the user wants to know Audio status for both incoming and outgoing channels for Call 1.
xstatus call 1 channels audio
*s Call 1 (status=Synced, type=Vtlph, protocol=H323, direction=Outgoing, logTag=3):
Channels 1 (type=Incoming):
Audio (status=Active):
Protocol: G722
Rate: 64
Channels 2 (type=Outgoing):
Audio (status=Active):
Protocol: G722
Rate: 64
*s/end
OK

Example 2 b) xpreferences completepath set to on:

xstatus call 1 channels audio
*s Call 1 (status=Synced, type=Vtlph, protocol=H323, direction=Outgoing, logTag=3):
*s Call 1 Channels 1 (type=Incoming):
*s Call 1 Channels 1 Audio (status=Active):
*s Call 1 Channels 1 Audio Protocol: G722
*s Call 1 Channels 1 Audio Rate: 64
*s Call 1 Channels 2 (type=Outgoing):
*s Call 1 Channels 2 Audio (status=Active):
*s Call 1 Channels 2 Audio Protocol: G722
*s Call 1 Channels 2 Audio Rate: 64
OK

D 13887.09
APRIL 2009 54
About the TANDBERG API
XACLI – Status Type Commands – Exposure Options TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

About Exposure Options Request for Call 1 element with no exposure option
xstatus call 1

*s Call 1 (status=Synced, type=Vtlph, protocol=H323, direction=Outgoing, logTag=3):

Exposure options should be used to limit the amount of information returned. By adding an CallRate: 768
exposure option after the address expression (XPath or TANDBERG SimplePath), the system RemoteNumber: “558458”
can be instructed to return parts of the information within an element structure only. Mute: Off
<status-type command> <address expression> <exposure option> Microphone: Off
Duration: 10
Supported exposure options: MuteOutgoing: Off
• - hides all value elements Channels 1 (type=Incoming):
• -- hides all sub-elements Rate: 768
Restrict: Off
Encryption (status=Off): /
Audio (status=Active):
Protocol: G722
Request for Call 1 element with exposure option -: Rate: 64
xstatus call 1 - Video 1 (status=Active):
Protocol: H264
*s Call 1 (status=Synced, type=Vtlph, protocol=H323, direction=Outgoing, logTag=3): Resolution: CIF
Channels 1 (type=Incoming): Rate: 704
Encryption (status=Off): / Video 2 (status=Inactive): /
Audio (status=Active): Data (status=Inactive): /
Video 1 (status=Active): Channels 2 (type=Outgoing):
Video 2 (status=Inactive): / Rate: 768
Data (status=Inactive): / Restrict: Off
Channels 2 (type=Outgoing): Encryption (status=Off): /
Encryption (status=Off): / Audio (status=Active):
Audio (status=Active): Protocol: G722
Video 1 (status=Active): Rate: 64
Video 2 (status=Inactive): / Video 1 (status=Active):
Data (status=Inactive): / Protocol: H264
*s/end Resolution: CIF
Rate: 704
OK Video 2 (status=Inactive): /
Data (status=Inactive): /
*s/end

OK
Request for Call 1 element with exposure option --:
xstatus call 1 --

*s Call 1 (status=Synced, type=Vtlph, protocol=H323, direction=Outgoing, logTag=3):

*s/end

OK

D 13887.09
APRIL 2009 55
About the TANDBERG API
XACLI – Special Commands – xfeedback (I) TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

About the xfeedback Command Example Example

To list the registered expression the sub-command list should User wants to deregister expression 2 in the left example:
be used: xfeedback deregister 2
The special command xfeedback lets the user xfeedback list
register user defined XPath expressions (with pos- Registered XPath feedback expressions: OK
sible exposure options) to monitor changes in the *xf 1 status/call xfeedback list
XML/XACLI data. Whenever there is a change in *xf 2 status/conference Registered XPath feedback expressions:
one or more elements addressed by a registered *xf 3 configuration *xf 1 status/call
XPath expression, the part of the element struc- *xf 3 configuration
ture containing these changes will be returned. OK OK
The system supports a total of 20 registered
expressions, with a total of 15 expressions for one
RS 232/Telnet session.
The xfeedback is a session specific command, Example
i.e. different RS 232/Telnet session can define User only wants to monitor call state changes. This can be done by adding the double hyphen exposure option (--), after the XPath
feedback individually. expression, status/call:
This also implies that the feedback expressions xfeedback register status/call--
must be set each time the control application OK
connects to the codec, i.e. the control application xcommand dial number:558458
should always set the necessary feedback expres-
*s Call 1 (status=EstablOut, type=Vtlph, protocol=H323, direction=Outgoing, logTag=6):
sions when connecting to the system (or after
*s/end
system reboot when using RS 232).
*r Result (status=OK):
CallRef: 1
LogTag: 6
*r/end
OK
*s Call 1 (status=Syncing, type=Vtlph, protocol=H323, direction=Outgoing, logTag=6):
*s/end
CONNECT
*s Call 1 (status=Synced, type=Vtlph, protocol=H323, direction=Outgoing, logTag=6):
*s/end
Example
User wants to monitor all changes to the Call sta-
tus elements, the Conference status element and Example
all Configurations:
xfeedback ?
xfeedback register status/call
usage: xfeedback register <XPathExpression>
OK or: xfeedback deregister <index>
xfeedback register status/conference or: xfeedback list
OK -
xfeedback register configuration (note: deregistration with index=0 will deregister all registered expressions)
OK OK

D 13887.09
APRIL 2009 56
About the TANDBERG API
XACLI – Special Commands – xfeedback (II) TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Example. User wants to know when calls are connected Note! If sub-elements are removed from a status structure between transitions, the removed elements will be notified with an attribute
and when calls are disconnected, without monitoring any ghost=True when feedback is issued. This allows for an external control system to be completely synchronised with the codec.
call data changes when the call is active:
This can be done by registering feedback on the events:
• CallSuccessful Example. This example shows status for a call that is beeing Rate: 64
• CallDisconnected disconnected. The user has registered a feedback expression to Video 1 (status=Active):
monitor all call changes (xfeedback register status/call). Protocol: H264
When the call is active the Call element contains a large sub-struc- Resolution: CIF
xfeedback register event/callsuccessful Rate: 704
ture. When the call is disconnected this status tree collapses, i.e.
OK the only information availible for a disconnected call is a Cause Video 2 (status=Inactive): /
xfeedback register event/calldisconnected element. All sub-elements that are being removed in this transition Data (status=Inactive): /
OK are marked with a ghost=True attribute when feedback is issued, *s/end
xcommand dial number:558458 see below. OK
*r Result (status=OK): xstatus call 1 xcommand disconnect
CallRef: 1 *s Call 1 (status=Synced, type=Vtlph, *r Result (status=OK): /
LogTag: 8 protocol=H323, direction=Outgoing, logTag=30): *r/end
*r/end CallRate: 768 OK
RemoteNumber: “558458”
OK *s Call 1 (status=ClearOut, type=Vtlph,
Mute: Off
CONNECT protocol=H323, direction=Outgoing, logTag=30):
Microphone: Off
*e CallSuccessful: *s/end
Duration: 62
CallRef: 1 NO CARRIER
MuteOutgoing: Off
LogTag: 8 Channels 1 (type=Incoming):
Protocol: H323 *s Call 1 (status=Disconnected, type=NA,
Rate: 768
Direction: Outgoing protocol=NA, direction=NA, logTag=NA):
Restrict: Off
Cause: 16
CallRate: 768 Encryption (status=On):
RemoteNumber: “558458” CallRate (ghost=True): /
Type: AES-128
Encryption: RemoteNumber (ghost=True): /
CheckCode: “C6D478F231E09A04”
Incoming: Off Mute (ghost=True): /
Audio (status=Active):
Microphone (ghost=True): /
Outgoing: Off Protocol: G722
Duration (ghost=True): /
*e/end Rate: 64
MuteOutgoing (ghost=True): /
Video 1 (status=Active):
Channels 1 (ghost=True): /
xcommand disconnectcall call:1 Protocol: H264
Channels 2 (ghost=True): /
*r Result (status=OK): / Resolution: CIF
*s/end
*r/end Rate: 704
Video 2 (status=Inactive): / xstatus call 1
OK Data (status=Inactive): / *s Call 1 (status=Disconnected, type=NA,
NO CARRIER Channels 2 (type=Outgoing): protocol=NA, direction=NA, logTag=NA):
Rate: 768 Cause: 16
*e CallDisconnected: Restrict: Off *s/end
CallRef: 1 Encryption (status=On): OK
LogTag: 8 Type: AES-128
*e/end CheckCode: “C6D478F231E09A04”
Audio (status=Active):
Protocol: G722

D 13887.09
APRIL 2009 57
About the TANDBERG API
XACLI – Special Commands – xpreferences (I) TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

About xpreferences xpreferences xpathwrite xpreferences detaillevel

A command of great importance, xpreferences lets the xpreferences xpathwrite <on/off> xpreferences detaillevel <1..2>
user/control application individually configure the Telnet/
Disables/enables the XPath search engine when issuing con- Most information elements accessible by the status-type
RS 232 session in use. When parsing data sent from the co-
figurations. When the XPath search engine is disabled, the commands are defined to be level 1 information. However
dec using a control system it is important to set preferences
user/control application must supply the complete path to there are some information elements defined to be level 2
to match the parser in use.
the configurations to be set (no “double slashes” allowed). information. When reading status information, only the infor-
The xpreferences is a session specific command, i.e. This will improve the performance of the system when issu- mation elements with a detail level equal to or less than the
different RS 232/Telnet sessions can define preferences ing many consecutive configurations. detaillevel defined for the interface will be listed.
individually. This also implies that the preferences must be
NOTE! It is always recommended to supply the complete The detaillevel is by default set to 1 when connecting to an
set each time the control application connects to the codec,
path for configurations to be set when issuing commands RS 232/Telnet session.
i.e. the control application should always set the necessary
from an external control application.
preferences when connecting to the system (or after system
reboot when using RS 232).

The xpreferences Options

xpreferences ?
xpreferences xmlcommandresult xpreferences xmlconfigfeedback
usage: xpreferences xpathwrite <on/off>
or: xpreferences detaillevel <1..2>
or: xpreferences xmlconfigfeedback <on/off>
or: xpreferences xmlstatusfeedback <on/off> xpreferences xmlcommandresult <on/off> xpreferences xmlconfigfeedback <on/off>
or: xpreferences xmlcommandresult <on/off> If xmlcommandresult is set to on, response for commands If xmlconfigfeedback is set to on, feedback on configura-
or: xpreferences itemnumber <on/off> will be returned in XML-format. tions will be returned in XML-format instead of the standard
or: xpreferences completepath <on/off> XACLI configuration format.
Example
OK XACLI-format:
xcom dial 10.47.15.127 Example
XACLI-format:
*r Result (status=OK):
CallRef: 1 *c xConfiguration SerialPort 1 BaudRate: 2400
LogTag: 8 XML format
*r/end
<Configuration>
<SerialPort item=”1”>
XML format <BaudRate item=”1”>2400</BaudRate>
xcom dial 10.47.15.127 </SerialPort>
</Configuration>
<Result item=”1” status=”OK”>
<CallRef item=”1”>1</CallRef>
<LogTag item=”1”>8</LogTag>
</Result>

D 13887.09
APRIL 2009 58
About the TANDBERG API
XACLI – Special Commands – xpreferences (II) TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

xpreferences xmlstatusfeedback xpreferences itemnumber

xpreferences xmlstatusfeedback <on/off> xpreferences itemnumber <on/off>

If xmlstatusfeedback is set to on, all status feedback will be returned All Status and Configuration elements consist of an element name and an
in XML-format instead of the default XACLI status format (or complete path formatting). element item number. However, XACLI hides the item number for an element
if there only exist one item of the given element.
Example If xpreferences itemnumber is set to on, XACLI will display item numbers for
XACLI-format: all elements. This is to make it easier to parse the information sent from
*s Call 1 (status=Synced, type=Vtlph, protocol=H323, direction=Outgoing, logTag=78): the codec. By setting “xpreferences itemnumber on”, the parser can
Channels 1 (type=Incoming): always expect an item number to follow an element name.
Rate: 768
Audio (status=Active):
Protocol: G722 Example: Reading configurations of Serial Port 1 with xpreferences item-
Rate: 64 number is set to off:
*s/end xconfiguration serialport 1
XML format
<Status> *c xConfiguration SerialPort 1 BaudRate: 9600
<Call item=”1” status=”Synced” type=”Vtlph” protocol=”H323” direction=”Outgoing” logtag=”78”> *c xConfiguration SerialPort 1 Parity: None
<Channels item=”1” type=”Incoming”>
<Rate item=”1”>768</Rate> *c xConfiguration SerialPort 1 DataBits: 8
<Audio item=”1” status=”Active”>
<Protocol item=”1”>G722</Protocol> *c xConfiguration SerialPort 1 StopBits: 1
<Rate item=”1”>64</Rate>
*c xConfiguration SerialPort 1 Mode: Control
</Audio>
</Channels> OK
</Call>
</Status>
Example: Reading configurations of Serial Port 1 with xpreferences item-
number is set to on:
xpreferences itemnumber on

OK
xconfiguration serialport 1
*c xConfiguration SerialPort 1 BaudRate 1: 9600
*c xConfiguration SerialPort 1 Parity 1: None
*c xConfiguration SerialPort 1 DataBits 1: 8
*c xConfiguration SerialPort 1 StopBits 1: 1
*c xConfiguration SerialPort 1 Mode 1: Control
OK

D 13887.09
APRIL 2009 59
About the TANDBERG API
XACLI – Special Commands – xpreferences (III) TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

xpreferences completepath

xpreferences completepath <on/off>

Used to enable Complete Path formatting for all Status-type data. If set to on, the complete path to a status element will be supplied on all lines. RECOMMENDED to be used when parsing status
information sent from the codec line by line.The specified formatting will also apply all feedback sent from the codec on this RS 232/Telnet session.

Example. Reading status for Call 1 with xpreferences completepath on: Example. Reading status for Call 1 with xpreferences completepath off:
xstatus call 1 xstatus call 1
*s Call 1 (status=Synced, type=Vtlph, protocol=H323, direction=Outgoing, logTag=2): *s Call 1 (status=Synced, type=Vtlph, protocol=H323, direction=Outgoing, logTag=2):
*s Call 1 CallRate: 768 CallRate: 768
*s Call 1 RemoteNumber: “558458” RemoteNumber: “558458”
*s Call 1 Mute: Off Mute: Off
*s Call 1 Microphone: Off Microphone: Off
*s Call 1 Duration: 527 Duration: 10
*s Call 1 MuteOutgoing: Off MuteOutgoing: Off
*s Call 1 Channels 1 (type=Incoming): Channels 1 (type=Incoming):
*s Call 1 Channels 1 Rate: 768 Rate: 768
*s Call 1 Channels 1 Restrict: Off Restrict: Off
*s Call 1 Channels 1 Encryption (status=Off): / Encryption (status=Off): /
*s Call 1 Channels 1 Audio (status=Active): Audio (status=Active):
*s Call 1 Channels 1 Audio Protocol: G722 Protocol: G722
*s Call 1 Channels 1 Audio Rate: 64 Rate: 64
*s Call 1 Channels 1 Video 1 (status=Active): Video 1 (status=Active):
*s Call 1 Channels 1 Video 1 Protocol: H264 Protocol: H264
*s Call 1 Channels 1 Video 1 Resolution: CIF Resolution: CIF
*s Call 1 Channels 1 Video 1 Rate: 704 Rate: 704
*s Call 1 Channels 1 Video 2 (status=Inactive): / Video 2 (status=Inactive): /
*s Call 1 Channels 1 Data (status=Inactive): / Data (status=Inactive): /
*s Call 1 Channels 2 (type=Outgoing): Channels 2 (type=Outgoing):
*s Call 1 Channels 2 Rate: 768 Rate: 768
*s Call 1 Channels 2 Restrict: Off Restrict: Off
*s Call 1 Channels 2 Encryption (status=Off): / Encryption (status=Off): /
*s Call 1 Channels 2 Audio (status=Active): Audio (status=Active):
*s Call 1 Channels 2 Audio Protocol: G722 Protocol: G722
*s Call 1 Channels 2 Audio Rate: 64 Rate: 64
*s Call 1 Channels 2 Video 1 (status=Active): Video 1 (status=Active):
*s Call 1 Channels 2 Video 1 Protocol: H264 Protocol: H264
*s Call 1 Channels 2 Video 1 Resolution: CIF Resolution: CIF
*s Call 1 Channels 2 Video 1 Rate: 704 Rate: 704
*s Call 1 Channels 2 Video 2 (status=Inactive): / Video 2 (status=Inactive): /
*s Call 1 Channels 2 Data (status=Inactive): / Data (status=Inactive): /
*s/end *s/end
OK OK

D 13887.09
APRIL 2009 60
About the TANDBERG API
XACLI – Special Commands – xgetxml TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Example
About xgetxml

xgetxml status/ip
As an alternative to the XACLI output format, XML format is
supported through the root command xgetxml. The xgetxml <Status>
takes an XPath expression as parameter and the elements <IP item=”1”>
(or complete document) matching the expression will be <Address item=”1”>10.47.11.179</Address>
returned. <SubnetMask item=”1”>255.255.248.0</SubnetMask>
<Gateway item=”1”>10.47.8.1</Gateway>
<V6 item=”1”>
<Address item=”1” type=”NA”></Address>
<Address item=”2” type=”NA”></Address>
</V6>
<DNS item=”1”>
<Server item=”1”>
<Address item=”1”>10.0.0.10</Address>
</Server>
<Server item=”2”>
<Address item=”1”>10.0.0.2</Address>
</Server>
<Server item=”3”>
<Address item=”1”></Address>
</Server>
<Server item=”4”>
<Address item=”1”></Address>
</Server>
<Server item=”5”>
<Address item=”1”></Address>
</Server>
<Domain item=”1”>
<Name item=”1”>eu.tandberg.int</Name>
</Domain>
</DNS>
</IP>
</Status>

OK

D 13887.09
APRIL 2009 61
About the TANDBERG API
TXAS - TANDBERG XML API Service TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

About TANDBERG XML API Service Bare-bone HTTP(S) Access

TXAS is a service provided by TANDBERG units for transmit- The bare-bone HTTP mode uses a unique URL to identify the specific request. The contents of
ting and receiving (transceiving) information encoded in XML the HTTP body will be a XML document (or part of it).
format. Bare-bone HTTP(S) access is accomplished by passing arguments in the query string (after
The API uses HTTP(S) as the transport mechanism and con- ‘?’ in URL) in a GET request, or using the “application/x-www-form-urlencoded” content-type
nects to the normal web port (80). TXAS can be accessed method of POSTing form data (Each argument starts with a name ‘=’ and a value, and every
in two ways; bare-bone HTTP requests where URL’s uniquely parameter separated with ‘&’ (and opt NL).)
identifies the request, and SOAP where a single URI is used getxml
but the request itself is encoded with XML. REQUEST:
/getxml
PARAM:
location = XPath expression

/getxml request returns an XML document based on the location parameter passed to the
request. The elements (or complete document) matching the expression will be returned.
On Incorrect XPath expression, a <Fault> element with a <XPathError> element will be re-
turned.
formputxml
REQUEST:
/formputxml
PARAM:
xmldoc = “an XML document of Configuration, Directory or Command”

This is most useful in a POST (to extend character limit of 255 of GET urls). It posts a Configu-
ration or Command document to set the configurations or issue a command.
Like getxml, it has the data URL form-data encoded with one single parameter. The Content-
Type of the document must be of type “application/x-www-form-urlencoded” and the body must
be encoded accordingly (e.g. first line will be xmldoc=<then the document>).
putxml
REQUEST:
/putxml
PARAM:
HTTP BODY as argument

Putxml is like formputxml+, put uses the complete BODY as argument (i.e. the content of
the xmldoc parameter). The Content-type should be “text/xml” or “application/xml” (
or “text/plain”), though no check at the moment. (Except for application/x-www-form-url
encoded which will cause a failure).

D 13887.09
APRIL 2009 62
 Configuration-type Commands
We recommend that you check out the This part of the manual describes the Configuration
TANDBERG web site regularly for updated
versions of this manual: information available.
http://www.tandberg.com/docs There are two types of configuration-type commands
available:
• xconfiguration / configuration.xml
• xdirectory / directory.xml
Both types are covered in this section.
Configuration-type Commands
Understanding the Table Layout TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Valid settings available

Valid range of Configuration values (from..to)
(here: On/Off)

Description
Configuration-type Commands – xconfiguration / configuration.xml
AdditionalCamera — Audio TANDBERG 3000 MXP & 6000 MXP
REFERENCE USER GUIDE FOR SYSTEM INTEGRATORS
Configuration path
AdditionalCamera Type: <0..4>
This configuration enables improved support for some non-TANDBERG cameras. When using one of the cameras listed below, set the configuration accordingly. Software version
F5 offers camera type autodetection. Should, however, the camera you use fail to to be detected properly, you may use this command to select the camera type that best resem-
bles the camera used.
0 = TANDBERG Wave 2 (default)
1 = Sony EVI-D30
2 = Sony BRC-300
3 = Sony EVI-D100
4 = Sony EVI-D70
5 = Sony BRC-H700
6 = Sony EVI-HD1
ExAMplE: If using a Sony EVI-D30: xconfiguration additionalcamera type: 1

AlertSpeaker Mode: <On/Off>

Turns the internal alert speaker On or Off.
Example: xconfiguration alertspeaker mode: on Syntax example
AlertTone Volume: <0..15>
Sets the volume of the alert tone. This volume setting also applies to the internal alert speaker if turned on.
Example: xconfiguration alerttone volume: 10
Some configurations TIp! The system supports as many as 10 different alert
AlertTone VideoTelephony: <1..10>
share a common part Defines the alert tone to use for incoming video telephony calls.
tones. To help distinguish between incoming video calls
and ordinary telephone calls, we recommend the use of
of the configuration Example: xconfiguration alerttone videotelephony: 10
different alert tones for video calls and telephone calls.
path, as can be seen Tip or restrictions
AlertTone Telephony: <1..10>
from these examples Defines the alert tone to use for incoming telephony calls.
applying
Example: xconfiguration alerttone telephony: 8

Allowlatency: <On/Off>
If set to Off (default), the IP call rate will sometimes exceed the maximum callrate specified for the call to reduce latency.
In some cases with poor network quality this might however result in increased packet loss. To avoid this, AllowLatency should be set to On.
Example: xConfiguration AllowLatency: On

Audio Microphones Mode: <On/Off>

Turns all microphones On or Off. This is the configuration that is tied to the “Mic off” key on the TANDBERG MXP remote control.
Example: xconfiguration audio microphones mode: off

Audio MicrophoneMixer Mode: <Fixed/Auto>

When set to Auto the adjustment of each microphone signal is done automatically to obtain the best possible audio and minimize the background noise.
When set to Fixed the system will maintain a constant weighting of all microphones.
Example: xconfiguration audio microphonemixer mode: fixed

D 13887.06
NOVEMBER 2007 65
Tip! An exhaustive
description of the API
structure can be found Contents of this
in the section column is sorted
The TANDBERG API alphabetically

D 13887.09
APRIL 2009 64
Configuration-type Commands – xconfiguration / configuration.xml
AdditionalCamera — Audio TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

AdditionalCamera Type: <0..6>

This configuration enables improved support for some non-TANDBERG cameras. When using one of the cameras listed below, set the configuration accordingly. Software ver-
sion F5 offers camera type auto-detection. Should, however, the camera you use fail to to be detected properly, you may use this command to select the camera type that best
resembles the camera used.
0 = TANDBERG Wave 2 (default)
1 = Sony EVI-D30
2 = Sony BRC-300
3 = Sony EVI-D100
4 = Sony EVI-D70
5 = Sony BRC-H700
6 = Sony EVI-HD1
Example: xconfiguration additionalcamera type: 1

AlertSpeaker Mode: <On/Off>

Turns the internal alert speaker On or Off.
Example: xconfiguration alertspeaker mode: on

AlertTone Volume: <0..15>

Sets the volume of the alert tone. This volume setting also applies to the internal alert speaker if turned on.
Example: xconfiguration alerttone volume: 10

Tip! The system supports as many as 10 different alert

AlertTone VideoTelephony: <1..10>
tones. To help distinguish between incoming video calls
Defines the alert tone to use for incoming video telephony calls.
and ordinary telephone calls, we recommend the use of
Example: xconfiguration alerttone videotelephony: 10
different alert tones for video calls and telephone calls.

AlertTone Telephony: <1..10>

Defines the alert tone to use for incoming telephony calls.
Example: xconfiguration alerttone telephony: 8

AllowLatency: <On/Off>
If set to Off (default), the IP call rate will sometimes exceed the maximum call rate specified for the call to reduce latency.
In some cases with poor network quality this might however result in increased packet loss. To avoid this, AllowLatency should be set to On.
Example: xconfiguration AllowLatency: On

Audio Microphones Mode: <On/Off>

Turns all microphones On or Off. This is the configuration that is tied to the “Mic off” key on the TANDBERG MXP remote control.
Example: xconfiguration audio microphones mode: off

Audio MicrophoneMixer Mode: <Fixed/Auto>

When set to Auto the adjustment of each microphone signal is done automatically to obtain the best possible audio and minimize the background noise.
When set to Fixed the system will maintain a constant weighting of all microphones.
Example: xconfiguration audio microphonemixer mode: fixed

D 13887.09
APRIL 2009 65
Configuration-type Commands – xconfiguration / configuration.xml
Audio cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Audio AutoMute: <On/Off/Unmute>

When automute is set to On, the microphones will be turned off (muted) automatically at boot and at end of calls.
When automute is set to Unmute, the microphones will be turned on (unmuted) automatically at boot and at end of calls.
Example: xconfiguration audio automute: on

Audio AudioModule: <NAMII-6000/NAMII-7000/NAMII-8000/Digital NAM/None>

Select Audio Module according to the type of Audio Module installed, if this is not automatically detected.
The Audio Module setting will only take effect if the audio module of the system is unidentified.
Example: xconfiguration audio audiomodule: NAMII-6000

Audio Volume: <0..21>

Sets the volume level output.
Example: xconfiguration audio volume: 10

Audio AGC Microphones: <On/Off>

Turns the AGC connected to the microphone mixer On or Off. On a 6000 MXP, Line input 1
(denoted Audio input 4 on the rear panel) is also connected to this AGC.
Example: xconfiguration audio agc microphones: on

Audio AGC AUX: <On/Off>

Turns the AGC connected to the AUX input On or Off.
NOTE! The AUX input is also sometimes referred to as Line Input 2 or AUX / Audio in 5 (6000 MXP) and Line Input 1 or Audio In 3 (3000 MXP).
Example: xconfiguration audio agc aux: on

Audio AGC VCR: <On/Off>

Turns the AGC connected to the VCR input On or Off.
NOTE! On the 6000MXP, the VCR input is also sometimes referred to as Line Input 3 or Audio in 6, while on the 3000MXP the VCR input is referred to as
Line Input 2 or Audio In 4. When Stereo I/O is set to On, the VCR input will be Line input 1 & 2 or Audio 5 & 6 (6000 MXP), and Line input 1 & 2 or Audio 3
& 4 (3000 MXP)
Example: xconfiguration audio agc vcr: off

Audio AGC Received: <On/Off>

Turns AGC for received audio On or Off.
Example: xconfiguration audio agc received: on

Audio EchoControl [1..x]: <On/Off/NoiseReduction>

6000 MXP: x=4
3000 MXP: x=2
Turns echo control On or Off for the various microphone inputs. Microphone 1 is connected to EchoControl 1, Microphone 2 is connected to EchoControl 2 etc.
Line input 1 (Audio input 4 on 6000 MXP) is connected to EchoControl 4 on a 6000 MXP.
Example: xconfiguration audio echocontrol 2: On

D 13887.09
APRIL 2009 66
Configuration-type Commands – xconfiguration / configuration.xml
Audio cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Stereo Settings Output Response Codec 3000 MXP Output Response Codec 6000 MXP
Audio Stereo: <On/Off>
Turns stereo I/O mode On or Off. Out 1 Stereo Stereo Audio Out 1 Audio Out 2 Audio Out 1 Audio Out 2 Audio
mode I/O mode speakers Out 3
Example: xconfiguration audio stereo: on
Analogue Off Off Loudspeaker mono VCR Loudspeaker mono Aux VCR

Analogue Off On Loudspeaker L Loudspeaker R Loudspeaker L Loudspeaker R VCR

Analogue On Off Loudspeaker mono VCR Loudspeaker mono VCR L VCR R

Audio StereoSpeakers: <On/Off> Analogue On On Loudspeaker L Loudspeaker R Loudspeaker L Loudspeaker R VCR
Turns stereo speakers On or Off.
SPDIF Off Off Loudspeaker mono VCR Loudspeaker mono Aux VCR
Example: xconfiguration audio stereospeakers: on
SPDIF Off On Loudspeaker L & R VCR Loudspeaker L & R Aux VCR

SPDIF On Off Loudspeaker mono VCR Loudspeaker mono VCR L VCR R

SPDIF On On Loudspeaker L & R VCR Loudspeaker L & R VCR L VCR R

Out 1 mode is controlled through the xconfiguration audio outputs line type command (overleaf)

Audio VCRDucking: <On/Off>

If VCR Ducking is set to On, the VCR audio level will be attenuated if someone talks into the microphone or at the far end.
Example: xconfiguration audio vcrducking: on

Audio KeyTones: <On/Off>

If set to On there will be a sound indicator when pressing keys on the remote control.
Example: xconfiguration audio keytones: on

Audio Inputs Microphone [1..x] Level: <1..16> By default, all inputs are
6000 MXP: x=3 Defines the input levels for the different microphones. enabled. Just plug in an audio
3000 MXP: x=2 Example: xconfiguration audio inputs microphone 2 level: 10 source and it is active. Audio
inputs that are On will auto-
Audio Inputs Microphone [1..x] Mode: <On/Off> matically be mixed. Unconnected
6000 MXP: x=3 Turns On or Off the different microphone inputs. inputs will automatically be
3000 MXP: x=2 Example: xconfiguration audio inputs microphone 2 mode: off muted. Select Off to prevent
Turns microphone 2 off. audio/noise from connected but
unused inputs.
Audio Inputs Microphone [1..x] Mode: <Line> The microphone inputs are
6000 MXP: x=3 Note! Applies to 6000 MXP only! Here the Microphone 3 Mode can be set to Line. It then intended for electret type micro-
3000 MXP: x=2 becomes a balanced line level input. The gain will be reduced accordingly. phones. The microphone inputs
Example: xconfiguration audio inputs microphone 3 mode: line are balanced with 24 V phantom
Sets microphone input 3 on a 6000 MXP to a balanced line level input. power.

Audio Inputs Line [1..x] Level: <1..16>

6000 MXP: x=3 Defines the input levels for the different line inputs.
3000 MXP: x=2 Example: xconfiguration audio inputs line 2 level: 10

D 13887.09
APRIL 2009 67
Configuration-type Commands – xconfiguration / configuration.xml
Audio cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Audio Inputs Line [1..x] For 3000 MXP, Line 1:

6000 MXP: x=3 Mode: <On/Off/Microphone>
3000 MXP: x=2 Turns the input On or Off. If set to Microphone, the audio on this input will not be outputted locally. Microphone input 2 will be
disabled and this Line input will use the Echo canceller of Mic. input 2. To be used when using an external microphone mixer.
For 3000 MXP, Line 2:
Mode: <On/Off/Auto>
Turns the input On or Off. If set to Auto the input will be active when VCR is selected as video input source.
For 6000 MXP, Line 1 & 2:
Mode: <On/Off>
Turns the input On or Off.
For 6000 MXP, Line 3:
Mode: <On/Off/Auto>
Turns the input On or Off. If set to Auto the input will be active when VCR is selected as video input source.
Example: xconfiguration audio inputs line 2 mode: off

Audio Outputs Line [1..x] Level: <1..16>

6000 MXP: x=3 Defines the output level of the specified output line
3000 MXP: x=2 Example: xconfiguration audio outputs line 2 level: 10

Audio Outputs Line [1..x] Mode: <On/Off>

6000 MXP: x=3 Enables or disables the specified output line.
3000 MXP: x=2 Example: xconfiguration audio outputs line 2 mode: off

Audio Outputs Line [1] Type: <Analog/SPDIF/Auto>

6000 MXP: x=3 Note! Applies to Line 1 only! This configuration is also referred to as Out 1 Mode.
3000 MXP: x=2 If Out 1 Mode is set to Auto, the system will select analogue or digital (SPDIF) mode depending on the detected Audio Module. If
a TANDBERG Digital NAM is detected, SPDIF mode will be selected, otherwise analogue mode will be selected.
Setting the Out 1 Mode to either Analogue or SPDIF will override the auto-detected mode.
Example: xconfiguration audio outputs line 1 type: SPDIF

Audio LocalDetection Mode: <On/Off>

The Local Detection is a feature to detect possible eavesdropping activity. If such activity is detected it will be stopped. The system will disconnect
the ongoing call and start an alarm / warning signal on the internal alert speaker on the codec. This will prevent audio and video to be sent from a
TANDBERG system without the user noticing.
Local Detection is based on a detection of an acoustical connection between the loudspeaker system and the microphone(s). If there is no such connec-
tion, and the loudspeaker is disconnected or switched off, it may indicate that the system is configured with the intention of listening into a confidential
conversation/meeting without the meeting participants noticing.
Example: xconfiguration audio localdetection mode: On

D 13887.09
APRIL 2009 68
Configuration-type Commands – xconfiguration / configuration.xml
Audio cont... — AutoAnswer TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Audio Feedback Mode: <Normal/Fast>

This configuration alters how fast the audio feedback will react. Set to Normal to allow for some distortion before the feedback response. When set to
Fast, the audio feedback response will be faster but also more nervous.
Example: xconfiguration audio feedback mode: normal

Audio Delay AUX: <On/Off>

Enables/disables the AUX delay.
Example: xconfiguration audio delay aux: off

Audio Delay VCR: <On/Off>

Enables/disables the VCR delay.
Example: xconfiguration audio delay vcr: off

Audio HearingImpaired Mode: <On/Off>

If set to On the Hearing Impaired Mode reduces the delay on audio output 3 from 100 ms to 23 ms, allowing an assisted listening device (ALD) to be
installed in conjunction with this output and still maintain a high level of lip synchronization.
Set to Off when there is no assisted listening device (ALD) connected to audio output 3.
Example: xconfiguration audio hearingimpaired mode: off

Audio HearingImpaired NoiseReduction: <On/Off>

If set to On the Noise reduction will be added to the output used for hearing impaired devices installed on audio output 3.
Set to Off when there is no assisted listening device (ALD) connected to audio output 3.
Example: xconfiguration audio hearingimpaired noisereduction: off

Audio HearingImpaired EQ: <On/Off>

If set to On an equalizer is enabled on the system, adding more amplification to the higher frequencies typically found in voices. The setting is by default
set to On.
Set to Off to disable the equalizer.
Example: xconfiguration audio hearingimpaired eq: on

AutoAnswer Mode: <On/Off/Mute>

Turns autoanswer On or Off. If set to Mute, incoming calls will be answered automatically, but the microphones will be muted.
Example: xconfiguration autoanswer mode: mute

AutoAnswer Delay: <1..50>

Defines how long (in seconds) an incoming call has to wait before it is answered automatically by the system (autoanswer must be enabled).
Example: xconfiguration autoanswer delay: 10

D 13887.09
APRIL 2009 69
Configuration-type Commands – xconfiguration / configuration.xml
AutoPIP — CallVideoSource TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

AutoPIP Mode: <On/Off/Auto>

This configuration only applies if LocalLayout Toggle is set to PIP.
If set to On, the system will display a PIP containing the far-end mainstream when dual video stream is activated.
If set to Auto, the system will display a PIP containing the far-end mainstream when dual video stream is activated. This PIP will disappear automatically after a few seconds, set
byt the AutoPIP Timeout setting.
If set to Off, no PIP will be displayed when dual video stream is activated. Requires AutoLayout Mode set to Off.
Example: xconfiguration autopip mode: on

AutoPIP Timeout: <1..60>

If the AutoPIP Mode setting is set to Auto, the system will display a PIP containing the far-end mainstream when dual video stream is activated. This PIP will disappear automati-
cally after a few seconds. The time out is set by the AutoPIP Timeout setting.
Example: xconfiguration autopip mode: on

AutoLayout Mode: <On/Off>

If set to On the system will change the local picture layout automatically depending on the number of participants in the conference and wether or not dual stream is active.
If set to Off there will be no automatic change of the local picture layout during the conference. All desired layout changes must be done manually, ref. LocalLayout.
Example: xconfiguration autolayout mode: off

AutoDisplaySnapshot: <On/Off>
If set to On the system will automatically display snapshots (still images) when received from the other side.
Example: xconfiguration autodisplaysnapshot: on

Bonding Timer: <Normal/Relaxed>

Relaxed bonding timing should be used with applications where the B channels use some additional time before they become transparent, like external encryption devices etc.
Example: xconfiguration bonding timer: relaxed

Bonding Rebonding: <On/Off>

The default value is On. Rebonding is used to re-establish H.320 calls if corrupted data is received for a longer period (10 - 15s).
Some manufactures don’t support this, and by setting Rebonding to Off this functionality will be disabled.
Example: xconfiguration bonding rebonding: off

CallManager Address: <S: 0, 64>

Defines the address of the call manager to use (if any).
Example: xconfiguration callmanager address: 10.47.9.1

CallVideoSource: <0/1/5/6>
The Call Video Source is the default call video source you would prefer to use in a call..
Example: xconfiguration callvideosource: 0

D 13887.09
APRIL 2009 70
Configuration-type Commands – xconfiguration / configuration.xml
Camera [1..13] TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Camera [1..13] Brightness Mode: <Manual/Auto>

Sets whether to control camera brightness of the different cameras manually or to have it automatically set by the
system.
Example: xconfiguration camera 1 brightness mode: manual

Camera [1..13] Brightness Level: <0..31>

Defines the brightness level to use if Brightness Mode is set to Manual.
Example: xconfiguration camera 1 brightness level: 10

Camera [1..13] Whitebalance Mode: <Auto/Manual/Indoor/Outdoor/Gain>

If set to Auto the camera will continuously adjust the white balance depending on the camera view.
If set to Indoor the camera will adjust the whitebalance for in-door lighting conditions.
If set to Outdoor the camera will adjust the whitebalance for out-door lighting conditions.
When set to Manual the white balance can be calibrated manually by the instruction xcommand camerawhite- If a TANDBERG Video Switch is
balance camera:<1..13>. The whitebalance of the camera will then remain constant until a new calibration is connected, the camera ranges
performed. will behave as follows:
Example: xconfiguration camera 1 whitebalance mode: auto • Camera 1 will be the video
switch.
Camera [1..13] Whitebalance Level: <0..16> • Camera range 2..7 will
Specifies the camera whitebalance level. Applies to TANDBERG Precision HD cameras only. be cameras connected to
Example: xconfiguration camera 1 whitebalance level: 10 secondary chain (the chain
originating from Data port 2
of the switch).
Camera [1..13] Whitebalance Gain Red: <0..255>
Adjust the red white balance gain. • Camera range 8..13 will be
Example: xconfiguration camera 1 whitebalance gain red: 128 cameras connected to the
primary chain (the chain
originating from Data port 1
Camera [1..13] Whitebalance Gain Blue: <0..255> of the switch).
Adjust the blue white balance gain.
Go to the TANDBERG Video
Example: xconfiguration camera 1 whitebalance gain blue: 128
Switch section to read more.

Camera [1..13] Focus Mode: <Manual/Auto>

If set to Manual autofocus will never be turned on automatically.
Example: xconfiguration camera 1 focus mode: manual

Camera [1..13] Backlight: <On/Off>

Turns backlight compensation of camera On/Off. Not applicable to TANDBERG WAVE I cameras.
Example: xconfiguration camera 1 backlight: on

Camera [1..13] DualVisca: <Off/On>

Enables or disables dual visca mode. If enabled, visca control will be available on the RJ11 connector on the camera. If disabled, the RJ11
connector will work as a normal daisy chain port. Applies to TANDBERG Precision HD cameras only.
Example: xconfiguration camera 1 dualvisca: on

D 13887.09
APRIL 2009 71
Configuration-type Commands – xconfiguration / configuration.xml
Camera[1..13] cont.. — CameraSleep TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Camera [1..13] Mirror: <Off/On>

Turns mirror mode on/off. Not applicable to TANDBERG WAVE I cameras.
Example: xConfiguration camera 1 mirror: on

Camera [1..13] Gamma Mode: <Auto/Manual>

Auto is the default and the recommended setting. However, in severe light conditions, you may switch mode to
manual and specify explicitly which gamma table to use by setting the level. Applies to TANDBERG Precision HD
cameras only.
Example: xConfiguration camera 1 gamma mode: auto
See the comment about camera
ranges on the previous page.
Camera [1..13] Gamma Level: <0..7>
Selects which gamma correction table to use. This setting may be useful in difficult lighting conditions, where chang-
es to the brightness setting does not provide satisfactory results. Applies to TANDBERG Precision HD cameras only.
Example: xConfiguration camera 1 gamma level: 5

Camera [1..13] IR: <Off/On>

Default is On for camera 1 and 8. Default is Off for cameras 2 - 7 and 9 - 13.
Enables or disables the IR receiver of the camera. Only supported on WAVE, WAVE II and Precision HD cameras
Example: xConfiguration camera 1 ir: on

CameraDVI Mode: <On/Off/Auto>

Lets you control cameras connected to the PC Input.

The Auto mode, which is the default, will detect if you connect two PrecisionHD cameras, where one is first and the other is last in the chain. If that’s the case, control of the 2nd
PrecisionHD camera is automatic when the PC Input is selected.

If you have any other type of camera with a VGA/DVI/HDMI output, you must put it last in the chain, and manually turn this configuration. When you select the PC Input, you will
gain control of the last camera. This configuration may be useful when using the VGA output on a Sony BRC-H700 camera.
Important: If you set this configuration to on with a single PrecisionHD camera connected, the system will assume that it is connected to the PC Input and avoid configuring
the THSI interface. This may or may not be what you intended.

When set to Off the system assumes all cameras are connected to the normal video inputs, and/or THSI. May be useful if you connect a 2nd PrecisionHD camera to the codec
via an HDMI to s-video/composite converter.

Important: Changing any of these options may require a hard boot of connected PrecisionHD cameras and a soft boot of the codec. If you experience problems, like no video
or get the message “unsupported video format”, make sure that all connected PrecisionHD cameras are turned off, reboot the codec, and turn cameras back on.

Example: xConfiguration cameradvi mode: auto

CameraSleep Mode: <On/Off>

If turned On, the main camera will go into sleep position (maximum right panning) when screensaver is activated.
In addition, video source 1 (maincam) will be selected (if not allready active).
Example: xconfiguration camerasleep mode: on

D 13887.09
APRIL 2009 72
Configuration-type Commands – xconfiguration / configuration.xml
CameraSwUpgrade — Conference TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

CameraSwUpgrade: <Auto/Off>
If set to Auto the Camera software will be automatically upgraded by the codec. If set to Off, camera software upgrade must be initiated manually by the command CameraForceUpgrade.
NOTE! If codec software is downgraded the camera software must be downgraded manually by the command CameraForceUpgrade. Applies to TANDBERG Precision HD camera only!
Example: xconfiguration cameraswupgrade: Auto

CameraReverseControl: <On/Off>
Set to On to enable the reverse camera control, allowing the local camera to more naturally mimic the directional arrows of the remote control. The setting does not affect the camera sleep pan.
Set to Off to disable the camera reverse control
Example: xconfiguration camerareversecontrol: off

CameraTracking Speed: <Slow/Normal/Fast>

Sets the camera tracking speed. Camera tracking is enabled/disabled by the commands CameraTrackingStart and CameraTrackingStop.
Example: xconfiguration cameratracking speed: normal

Conference DefaultCall CallRate: <Tlph/1xh221/2xh221/64/128/192/256/320/384/H0/512/768/1152/1472/1920/2560/3072/4096/

Max/Auto>
Defines the default call rate to use when placing calls from the system.
NOTE! The supported call rates will depend on product type and software options.
NOTE! Auto: 384 kbps on ISDN/768 kbps on LAN
Example: xconfiguration conference defaultcall callrate: 320
The DefaultCall settings specify
Conference DefaultCall Restrict: <On/Off> call properties to use if proper-
A restricted call uses 56kbps channels rather than the default unrestricted 64kbps channels. Some older networks ties are not specified directly
(primarily in the USA) do not support 64kbps channels and require the use of restricted 56kbps calls. By default, the when placing the call.
system will dial an unrestricted call and downspeed to 56kbps if necessary.
To force a restricted call, choose Restrict (56k) On.
Example: xconfiguration conference defaultcall restrict: off

Conference DefaultCall NetProfile: <1..7>

Selects default NetProfile. Please refer to the NetProfile configuration for further details on the supported NetProfiles.
Example: xconfiguration conference defaultcall netprofile: 3

Conference H323Alias E164: <E164: 0, 30> The aliases define the tele-
Defines the E164 alias for the system. Valid characters are 0-9, and #.
Example: xconfiguration conference h323alias e164: 666666
* phone numbers for the unit, i.e.
numbers to call to reach the
unit. The system can register
Conference H323Alias ID: <S: 0, 49> both an E164 alias, which can
Defines the H323Alias ID for the system. If no ID is specified the system will use the SystemUnit Name as
#) and an ID, which can also
*
only contain digits (including ,
H323Alias ID.
Example: xconfiguration conference h323alias id: MyH323AliasId contain letters.

D 13887.09
APRIL 2009 73
Configuration-type Commands – xconfiguration / configuration.xml
Conference cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Conference PeriodicIntra: <0..1000>

Use this setting to generate a new intra frame with a configure-able interval. Use this setting with caution since it in a normal network will de-
crease the video quality. The default value is set to 0 which means off. If you configure it to 10 it will send an intra every 10th second.
Example: xconfiguration conference periodicintra: 0

Conference SIP URI: <S: 0, 60>

The SIP URI is the address to use when calling the system using SIP.
Example: xconfiguration conference sip uri: MySIP_URI

Conference H263: <On/Off>

Enables/disables H.263 for both transmit and receive.
Example: xconfiguration conference h263: off

Conference H264: <On/Off>

Enables/disables H.264 for both transmit and receive.
Example: xconfiguration conference h264: on

Conference H264RCDO: <On/Off>

Enables/disables H.264 RCDO for both transmit and receive.
Example: xconfiguration conference h264rcdo: off

Conference G722: <On/Off>

Enables/disables G.722 for both transmit and receive.
Example: xconfiguration conference g722: on

Conference G722.1: <On/Off>

Enables/disables G.722.1 for both transmit and receive.
Example: xconfiguration conference g722.1: on

Conference G728: <On/Off>

Enables/disables G.728 for both transmit and receive.
Example: xconfiguration conference g728: on

Conference AAC-LD: <On/Off>

Enables/disables AAC-LD for both transmit and receive.
Example: xconfiguration conference aac-ld: on

Conference H331: <On/Off>

Turns broadcast mode on or off. When set to on it is possible to make an outgoing call without any capability exchange.
Example: xconfiguration conference h331: on

D 13887.09
APRIL 2009 74
Configuration-type Commands – xconfiguration / configuration.xml
Conference cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Conference H239: <On/Off>

Enables/disables H.239 for both transmit and receive.
Example: xconfiguration conference h239: on

Conference AAC-LD-128-Threshold: <384/512/768/1152/1472/1920/2560/3072/4096>

The system will not transmit AAC-LD-128 unless the call rate is equal to or above the specified threshold.
Example: xconfiguration conference aac-ld-128-threshold: 768

Conference AAC-LD-128-Mono: <On/Off>

If set to Off and the system is transmitting mono, the system will not use AAC-LD-128 even though the call rate is above the AAC-LD-128 Threshold.
Example: xconfiguration conference aac-ld-128-mono: off

Conference NaturalVideo: <Off/Auto/384/512/768/1152/1472/1920>

Enabling Natural Video will enable 60 (50 on PAL) fields per second true interlaced picture for high motion video. The use of Natural Video requires that H.263+ or H.263++ video
protocols are being used. Natural video will be disabled in H.323 MultiSite calls and in H.320 Continuous Presence MultiSite calls.
When set to Off, Natural Video will be disabled for both transmit and receive.
When set to Auto, the system will enable transmission of Natural Video from 768 kbps and above. Reception of Natural Video is in this case always enabled. However, when set
to Auto the unit will still prioritize the 448p and w448p format over Natural Video. Natural Video can also be configured to be enabled for call rates above a specified threshold
value.
Example: xconfiguration conference naturalvideo: 768
This will enable NaturalVideo for callrate 768 kbps and above

Conference PictureMode: <4Split/5+1Split/VS/Auto>

Sets the picture layout to be used in a MultiSite conference. If set to Auto the system will change the picture layout depending on the number of participants in the conference.
Example: xconfiguration conference picturemode: auto

Conference VideoQualityCP: <Motion/Sharpness/Auto>

Sets the video quality to be used in continuous presence mode (4Split/5+1Split).
Example: xconfiguration conference videoqualitycp: sharpness

Conference VideoFormatCP: <4:3/16:9>

Sets the video format to be used in continuous presence mode (4Split/5+1Split).
If set to normal CP which is 4:3, the host will transmit all CP layouts using 4CIF (704x576).
If set to wide CP which is 16:9, the host will transmit all CP layouts using w576p (1024x576).
Example: xconfiguration conference videoformatcp: 16:9

Conference FloorToFull: <On/Off>

If PictureMode is set to 5+1Split, and one of the participants in a MultiSite conference is granted floor this setting determines whether to display the participant having floor in full
screen or just in the main window of the 5+1Split.
Example: xconfiguration conference floortofull: on

D 13887.09
APRIL 2009 75
Configuration-type Commands – xconfiguration / configuration.xml
Conference cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Conference MaxCallLength: <0..999>

Sets the maximum allowed call length in minutes (0 = Disabled).
Example: xconfiguration conference maxcalllength: 0

Conference AllowIncomingTlphCall: <On/Off>

If set to Off, the system will not accept incoming telephone calls to an already active conference.
Example: xconfiguration conference allowincomingtlphcall: off

Conference AllowIncomingMSCall: <On/Off>

If set to Off, the system will not accept incoming calls to an already active multisite conference.
Example: xconfiguration conference allowincomingmscall: off

Conference Downspeed: <On/Off>

Determines whether or not to allow down speeding.
Example: xconfiguration conference downspeed: on

Conference FallbackToTelephony: <On/Off>

If set to On, the system will try to establish a telephone call if a video telephone call failed to connect.
Example: xconfiguration conference fallbacktotelephony: on

Conference Encryption Mode: <On/Off/Auto>

If set to On, the system will not allow un-encrypted calls.
If set to Auto, the system will use encryption whenever possible.
If set to Off, encryption will not be used.
Example: xconfiguration conference encryption mode: auto

Conference Encryption Type: <Auto/DES/AES-128>

Defines the encryption algorithm to use.
If set to Auto, the system will try to use the most secure encryption - AES, dependent on the capabilities of the other sites. For sites that do not support
AES encryption, DES encryption will be tried.
If set to AES-128, the system will try to use AES with 128 bits encryption when setting up calls. If AES is not supported by the other site(s), no other type
of encryption will be initiated.
If set to DES, the system will always try to set up the call using DES with 56 bits encryption ISDN and IP. If all other sites do not support DES, no other
type of encryption will be initiated.
Example: xconfiguration conference encryption type: AES-128

Conference AIM: <On/Off>

Enables/disables Auto Indicate Mute. If disabled, the system will not signal to the other side that the microphone is turned off.
Example: xconfiguration conference aim: on

D 13887.09
APRIL 2009 76
Configuration-type Commands – xconfiguration / configuration.xml
Conference cont... — CorporateDirectory TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Conference IPLR Transmit: <On/Off>

Enables/disables Intelligent Packetloss Recovery
Example: xconfiguration conference iplr transmit: on

Conference WebSnapshots: <On/Off>

If set to On, snapshots of the conference can be viewed from the systems web interface and also accessed through the units file system.
NOTE! This configuration can only be set using the RS232 port.
Example: xconfiguration conference websnapshots: on

Conference BillingCode: <On/Off>

This configuration is only relevant when placing calls using the TANDBERG remote control and the on screen menu. If set to on, all users must enter a code to identify themselves
before dialling. The billing code will be attached to the call when the call is placed in the call log after it is disconnected. When placing calls using the command Dial, a billing
code can be added to identify the call in the call log regardless of this setting.
Example: xconfiguration conference billingcode: on

Conference IPDualstreamRate: <25Percent/50Percent/75Percent>

When setting up an ip call the bandwidth can be controlled by the user. The IPDualstreamRate is expressed in percent of the Call Rate and shall reflect the IP Dualstream Rate
settings of the sender. The settings are 25%, 50% and 75% of the total available video stream.
Example: xconfiguration conference ipdualstreamrate: 50percent

Conference FarTlphEchoSupression: <Off/Normal/High>

Analogue telephone lines, speaker phones and telephone headsets may all cause echoes. The FarTlphEchoSupression function eliminates some – or all – of the experienced
echo. Weak echoes are removed with the Normal setting enabled and strong echoes are removed with the High setting enabled.
Example: xconfiguration conference FarTlphEchoSupression: Normal

Conference VideoText: <On/Off/Auto>

In MultiSite calls you can display the names of the participants on screen. By setting the Video Text Time-out setting, the system is configured to display the names for a period
of time or as long as you are connected.
Example: xconfiguration conference videotext: on

Conference VideoTextTimeout: <0..30>

Sets the timer for the On-screen name of participants in MultiSite calls. Set the timer to display the names for a period of time or as long as you are connected. Requires the
VideoText setting to be enabled.
Example: xconfiguration conference videotext: 0

CorporateDirectory Mode: <On/Off>

Enables/disables use of a CorporateDirectory stored on a remote server.
Example: xconfiguration corporatedirectory mode: on

CorporateDirectory Address: <S: 0, 64>

Specifies the address to the server where the CorporateDirectory is located.
Example: xconfiguration corporatedirectory address: 10.47.6.75

D 13887.09
APRIL 2009 77
Configuration-type Commands – xconfiguration / configuration.xml
CorporateDirectory cont... — DynamicResolution TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

CorporateDirectory Path: <S: 0, 255>

Specifies the path to the CorporateDirectory on the server.
Example: xconfiguration corporatedirectory path: TMS/Public/external/phonebook/PhoneBookService.asmx

CorporateDirectory Protocol: <HTTP/HTTPS>

TANDBERG MXP systems now support secure management when communicating with the TMS (TANDBERG Management Suite).
Example: xconfiguration corporatedirectory protocol:

DefaultPIPPosition: <BottomLeft/BottomRight/TopLeft/TopRight>
Specifies the default positioning of the PIP (Picture In Picture).
Example: xconfiguration defaultpipposition: bottomleft

Directory CallLog: <On/Off>

Enable/disable Call Logs for Placed calls, Missed calls and Received calls in the Phone Book.
Example: xconfiguration directory calllog: on

Directory SmartSearch: <On/Off>

Enable/disable Smart Search in the Phone Book.
Example: xconfiguration directory smartsearch: off

DoNotDisturb Mode: <On/Off>

When DoNotDisturb Mode is set to On, the codec will not alert the user to incoming calls. The calling side will receive a busy signal when trying to call the codec. DoNotDisturb
will be turned off if the codec receives any IR signal from the handheld remote control.
Example: xconfiguration donotdisturb mode: off

DualMonitor Mode: <On/Off>

Sets the codec’s monitor mode. It allows the user to set up the codec so it can utilize two displays.
Example: xconfiguration dualmonitor mode: on

DuoVideoSource: <0/1/2/3/4/5/6>
Defines which video input to be used as the default Dual Stream source. Note! 0 means None
Example: xconfiguration duovideosource: 1

DynamicResolution Mode: <Auto/Off>

With Dynamic Resolution the system will use the optimal video resolution for the chosen bandwidth. This feature is only applicable to HD (high definition) calls.
If set to Auto and in a HD call: the resolution will differ between the bandwidths 720p, 576p and 448p, dependent on how much motion it is in the picture. The call will start with
720p and change to a lower resolution when there is a lot motion. It will go back to 720p with less motion.
If set to Off: Disables the Dynamic Resolution feature (the default setting).
Example: xconfiguration dynamicresolution mode: off

D 13887.09
APRIL 2009 78
Configuration-type Commands – xconfiguration / configuration.xml
E1 — ExternalNetwork TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

E1 Interface CRC4: <On/Off>

E1 CRC-4 is used for most E1-PRI configurations. You can turn it off if not supported by the E1 network equipment.
Example: xconfiguration e1 interface crc4: on

Ethernet [1..2] Speed: <Auto/10half/10full/100half/100full>

Sets the Ethernet speed. When set to Auto the codec will automatically negotiate with the network and use the best available setting.
Example: xconfiguration ethernet 1 speed: auto

ExternalManager Address: <S: 0, 64> If an External Manager address and a path is config-
Specifies the address to the External Manager/Management system. ured, the system will post an HTTP message to this
Example: xconfiguration externalmanager address: “10.47.6.75” address when starting up. When receiving this HTTP
posting the External Manager (typically a management
ExternalManager Path: <S: 0, 255> system) can return configurations/commands to the
Specifies the path to the External Manager/Management system. unit as a result.
Example: xconfiguration externalmanager path: tms/public/external/management/SystemMan- If the DHCP Option 242 is returned in the DHCP re-
agementService.asmx sponse from the DHCP server the system will interpret
this as the External Manager address to use.

ExternalManager Protocol: <HTTP/HTTPS>

Enables/disables secure management.
Example: xconfiguration externalmanager protocol: http

ExternalNetwork Clocking: <Dual/Single>

Dual: (RS449/V35 Compatible) Use this setting when the external equipment provides two clock signals, one for transmit and one for receive. (The difference between RS449
and V35 lies solely in the cable).
Single: (X21 Compatible) Use this setting when the external equipment provides a common clock signal for both transmit and receive.
Example: xconfiguration externalnetwork clocking: dual

ExternalNetwork Callcontrol: <RS366/RS366AdtranIMUX/RS366CustomIMUX/LeasedLine/DataTriggered/Manual>

RS366: This is the only dialling protocol supported and would normally be used together with Dual network clocking when the external equipment uses RS366 ports.
RS366AdtranIMUX: This setting offers extra usability when dialing RS366 via an ADTRAN IMUX. This dialling scheme will map the call type and bandwidth selection to ADTRAN
IMUX specific suffixes to the dialled number. Should only be used when connected to an ADTRAN IMUX.
The Adtran IMUX uses the following suffixes <Number>#C#R
#C = Call Type #2 = audio #3 = 56kbps #4 = 64kbps #R = Channel Rate #0 = 2xh221 (2x56\64kbps) #1 to 8 = the Call Rate.
RS366CustomIMUX: Uses a custom prefix/suffix table which describes the available bandwidths. The prefixes/suffixes are set from the Web Interface or Command Line interface.
The user (administrator) shall be able to specify a IMUX prefix/suffix table for the following bandwidths (kbps): 64, 64 Restrict, 128, 128 Restrict, 192, 192 Restrict, 256, 256
Restrict, 320, 320 Restrict, 384, 384 Restrict, 512, 512 Restrict, 768, 768 Restrict, 1152, 1152 Restrict, 1472, 1472 Restrict, 1920, 1920 Restrict.
LeasedLine: Leased Line is a non-dialling protocol and should be used when two codecs are connected in a point-to-point connection. Use Leased Line when the handshaking
signals DTR and CD are available. DTR and CD correspond to the X.21 network’s C and I signals.
DataTriggered: Data Triggered mode uses TxData (transmit data), RxData (receive data) and clock signals only. Use Data Triggered when no handshake signals are available.
Manual: Manual should be used when no handshake signals are available and the external equipment requires a constantly connected line.
Example: xconfiguration externalnetwork callcontrol: rs366

D 13887.09
APRIL 2009 79
Configuration-type Commands – xconfiguration / configuration.xml
ExternalNetwork cont... — G703 TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

ExternalNetwork DTRPulse: <On/Off>

Configures the DTR signal on the External Network port (V.35).
On: The DTR signal will give a low pulse lasting for 5 seconds
Off: The DTR pulse will stay low.
Example: xconfiguration externalnetwork dtrpulse: on

ExternalServices Mode: <On/Off>

Enables/disables External Services
Example: xconfiguration externalservices mode: on External Services allows a third party integrator to
present services on the unit using XHTML 1.0 strict and
ExternalServices Address: <S: 0, 64> HTTP.
Configures the External Services address. If turned on, a menu choice will appear in the services
Example: xconfiguration externalservices address: 10.47.6.75 menu, and on entering this the TANDBERG unit will
retrieve a default XHTML page as specified in the Exter-
ExternalServices Path: <S: 0, 255> nal Services configuration menu.
Configures the External Services path.
Example: xconfiguration externalservices path: “tms/public/EndpointService/”

ExternalServices Protocol: <HTTP/HTTPS>

Enables/disables secure management.
Example: xconfiguration externalservices protocol: http

FECC Mode: <On/Off>

Sets whether or not to allow the remote site to control the cameras connected to the system. FECC = Far End Camera Control
Example: xconfiguration fecc mode: on

FeedbackFilter Conference: <0..10> Only relevant if using feedback (xfeedback over RS-232/Telnet or feedback
Defines the Feedback filter (in seconds) for the Conference status element. over HTTP).
Example: xconfiguration feedbackfilter conference: 4 The feedback filter lets the user configure the maximum frequency between
feedback updates. That means if data changes very rapidly, the control application
FeedbackFilter Call: <0..10> will not receive feedback more frequent than every xth second. This will help reduc-
Defines the Feedback filter (in seconds) for the Call status element. ing the load on both the link and the control system, but some transition information
Example: xconfiguration feedbackfilter call: 2 might be lost.

FTP Mode: <On/Off>

Enables or disables the systems embedded FTP server.
Example: xconfiguration ftp mode: on

G703 PhysicalLayer: <E1/T1>

Selects whether the leased line is E1 or T1.
Example: xconfiguration g703 physicallayer: e1

D 13887.09
APRIL 2009 80
Configuration-type Commands – xconfiguration / configuration.xml
G703 cont... — H323CallSetup TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

G703 Linecoding: <b8zsRestrict/b8zsNoRestrict>

Selects whether the Leased line is a 56kb network (restricted) or a 64kb network.
Example: xconfiguration g703 linecoding: b8zsrestrict

G703 Callcontrol: <Manual/Auto>

When Auto is selected, the system will automatically initiate a connection as soon as it detects that the far end tries to make a call. This mode is also commonly known as “data
triggered” mode, because the existence of certain data patterns on the line triggers a connection.
When Manual is selected, you must explicitly issue a dial command to make the system connect to the far end system. Receiving an incoming call is not possible.
Example: xconfiguration g703 callcontrol: auto

G703 Interface StartChannel: <1..31>

Indicates the first E1/T1 channel the codec is allowed to use. This setting might be used if the E1/T1 line is shared with other equipment.
Example: xconfiguration g703 interface startchannel: 6

G703 Interface MaxChannels: <1..30/23>

Indicates the maximum number of channels the codec is allowed to use on the E1/T1 interface.
When E1 is selected, maximum is 30 channels. When T1 is selected, maximum is 24 channels.
Example: xconfiguration g703 interface maxchannels: 12

H320 NetType: <BRI/PRI/External/G703/None> (Codec 6000)

NetType: <BRI/None> (Codec 3000)
NetType: <External/None> (Codec 3000NET)
Defines the network type to use for H.320 calls.
Example: xconfiguration h320 nettype: bri

H323 Mode: <On/Off>

Enables/disables the possibility to place and receive H.323 calls.
Example: xconfiguration h323 mode: on

H323CallSetup Mode: <Direct/Gatekeeper/CallManager>

Defines how to establish H.323 calls.
Direct: An IP-address must be used in order to make a H.323 call. The system will not use a gatekeeper or CallManager.
Gatekeeper: The system will use a gatekeeper to make a H.323 call.
CallManager: The system will use a CallManager to make a H.323 call.
NOTE! Direct H.323calls can be made even though the H323CallSetup Mode is set to Gatekeeper or Callmanager.
Example: xConfiguration h323callsetup mode: gatekeeper

D 13887.09
APRIL 2009 81
Configuration-type Commands – xconfiguration / configuration.xml
H323Gatekeeper TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

H323Gatekeeper Discovery: <Manual/Auto>

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 gate-
keeper will be used. This requires auto discovery on the gatekeeper 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.
Manual: The system will use a specific gatekeeper identified by H323Gatekeeper Address.
Example: xconfiguration h323gatekeeper discovery: manual

H323Gatekeeper Address: <S: 0, 64>

Specifies the address of the gatekeeper to use if Discovery is set to Manual.
Example: xconfiguration h323gatekeeper address: 10.47.9.1

H323Gatekeeper MultipleAlias: <On/Off>

If set to On, the system will register multiple H.323-IDs on the Gatekeeper based on the values of the parameters: System Name, International Name and H.323 ID.
Up to 3 aliases are possible.
If set to Off, the system will register a single H.323-IDs on the Gatekeeper based on the following priority:
1. H.323 ID
2. International Name
3. System Name
Example: xconfiguration h323gatekeeper multiplealias: On

H323Gatekeeper Authentication Mode: <Auto/Off>

If Authentication Mode is set to Auto and the gatekeeper indicates that it requires authentication, the endpoint will automatically try to authenticate itself to the
Gatekeeper.
If Authentication Mode is set to Off the system will not try to authenticate itself to a Gatekeeper, but will still try a normal registration.
Example: xconfiguration h323gatekeeper authentication mode: auto

H323Gatekeeper Authentication ID: <S: 0, 49>

The system sends the Authentication ID and Password to a Gatekeeper for authentication. The authentication is a one way authentication from the endpoint
system to a Gatekeeper, i.e. the endpoint is authenticated to the Gatekeeper. If the Gatekeeper indicates that no authentication is required, the endpoint will
still try to register.
Example: xconfiguration h323gatekeeper authentication id: TANDBERG

H323Gatekeeper Authentication Password: <S: 0, 49>

Please see above. Note! The password will not be listed when polling.
Example: xconfiguration h323gatekeeper authentication password: xxx

H323Gatekeeper Avaya Mode: <On/Off>

NOTE! The Mode setting is the main switch to the rest of the options. If Mode is set to Off the other Avaya options will be ignored by the system.
Set to On when the specified gatekeeper (xconfiguration H323Gatekeeper Address) is an Avaya gatekeeper. This enables Avaya-specific behavior.
An Avaya gatekeeper is called Avaya Communication Manager - Avaya CM for short).
Example: xconfiguration h323gatekeeper avaya mode: off

D 13887.09
APRIL 2009 82
Configuration-type Commands – xconfiguration / configuration.xml
H323Gatekeeper cont... — IdReport TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

H323Gatekeeper Avaya AnnexH: <On/Off>

Set AnnexH to On to enable Avaya strongest level of encryption (H.235.5 with Avaya extensions). When set to Off, the Avaya CM needs to have a “green
license” installed to support non-encrypted endpoints.
Example: xconfiguration h323gatekeeper avaya annexh: off

H323Gatekeeper Avaya MultipointCount: <0..9>

The Avaya MultipointCount decides how many simultaneous calls the endpoint will be able to handle. If it is non-zero, that value will be used (there is a
maximum to what the Avaya CM can handle depending on its software version. Change this value only if you know what you’re doing). If set to “0”, default
safe values will be used. The default safe values are:
4 if AnnexH is turned on.
6 if AnnexH is turned off.

NOTE! The MultiPointCount setting is only used when in an Avaya environment.

Example: xconfiguration h323gatekeeper avaya multipointcount: 0

H323Gatekeeper Avaya Password: <S: 0, 49>

The Avaya password is a hidden write-only parameter that sets the PIN code to use for AnnexH encryption.
Example: xconfiguration h323gatekeeper avaya password: 123

H323Prefix: <S: 0, 4>

When dialling a number prefixed with digits specified by H.323 Prefix, and with Net: Auto, an H.323 call will be placed.
Example: xconfiguration h323prefix: 5

HTTP Mode: <On/Off>

Enables/disables HTTP.
Example: xconfiguration http mode: on

HTTPS Mode: <On/Off>

Enables/disables HTTPS.
Example: xconfiguration https mode: on

HTTPS VerifyServerCertificate: <On/Off>

TANDBERG MXP systems now support secure management when communicating with the TMS. For more information see the TANDBERG White Paper “Implementing
Secure Management” which describes how to configure secure HTTPS between TANDBERG products. To find the document, follow the link: http://www.tandberg.com/support/
documentation.php and select White Papers.
Example: xconfiguration https verifyservercertificate: on

IdReport H323: <H323Id/E164Alias/IPAddress>

Selects what identifier to present as remote number for incoming H.323 calls.
Example: xconfiguration idreport h323: h323id

D 13887.09
APRIL 2009 83
Configuration-type Commands – xconfiguration / configuration.xml
IEEE802.1x — IMUX TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

IEEE802.1x Mode: <On/Off>

Enables/disables 802.1x authentication
Example: xconfiguration ieee802.1x mode: on

IEEE802.1x AnonymousIdentity: <S: 0, 64>

The 802.1x Anonymous ID string is to be used as un-encrypted identity with EAP types that support different tunneled identity, EAP-PEAP and
EAP-TTLS. The anonymous ID, if set, will be used for the initial (un-encrypted) EAP Identity Request
Example: xconfiguration ieee802.1x anonymousidentity:

IEEE802.1x Identity: <S: 0, 64>

The 802.1x Identity is the user name needed for 802.1x authentication.
Example: xconfiguration ieee802.1.x identity: MyString
The system may be connected
to an IEEE 802.1x LAN net-
IEEE802.1x Password: <S: 0, 64>
work. Supported 802.1x proto-
The 802.1x Password is the password needed for 802.1x authentication.
cols are EAP-MD5, EAP-PEAP
Example: xconfiguration ieee802.1x password: MyPassword
and EAP-TTLS.

IEEE802.1x EAP-MD5: <On/Off>

Enables/disables the EAP-MD5 protocol
Example: xconfiguration ieee802.1.x eap-md5: on

IEEE802.1x EAP-TTLS: <On/Off>

Enables/disables the EAP-TTLS protocol
Example: xconfiguration ieee802.1.x eap-ttls: on

IEEE802.1x EAP-PEAP: <On/Off>

Enables/disables the EAP-PEAP protocol
Example: xconfiguration ieee802.1.x eap-peap: on

IMUX Custom BW64 Prefix: <S: 0, 12>

Defines the prefix to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconfiguration imux custom bw64 prefix: xxx

IMUX Custom BW64 Suffix: <S: 0, 12>

Defines the suffix to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconfiguration imux custom bw64 suffix: xxx

IMUX Custom BW64R Prefix: <S: 0, 12>

Defines the prefix to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconfiguration imux custom bw64r prefix: xxx

D 13887.09
APRIL 2009 84
Configuration-type Commands – xconfiguration / configuration.xml
IMUX cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

IMUX Custom BW64R Suffix: <S: 0, 12>

Defines the suffix to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconfiguration imux custom bw64r suffix: xxx

IMUX Custom BW128 Prefix: <S: 0, 12>

Defines the prefix to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconfiguration imux custom bw128 prefix: xxx

IMUX Custom BW128 Suffix: <S: 0, 12>

Defines the suffix to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconfiguration imux custom bw128 suffix: xxx

IMUX Custom BW128R Prefix: <S: 0, 12>

Defines the prefix to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconfiguration imux custom bw128r prefix: xxx

IMUX Custom BW128R Suffix: <S: 0, 12>

Defines the suffix to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconfiguration imux custom bw128r suffix: xxx

IMUX Custom BW192 Prefix: <S: 0, 12>

Defines the prefix to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconfiguration imux custom bw192 prefix: xxx

IMUX Custom BW192 Suffix: <S: 0, 12>

Defines the suffix to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconfiguration imux custom bw192 suffix: xxx

IMUX Custom BW192R Prefix: <S: 0, 12>

Defines the prefix to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconfiguration imux custom bw192r prefix: xxx

IMUX Custom BW192R Suffix: <S: 0, 12>

Defines the suffix to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconfiguration imux custom bw128r suffix: xxx

IMUX Custom BW256 Prefix: <S: 0, 12>

Defines the prefix to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconfiguration imux custom bw256 prefix: xxx

D 13887.09
APRIL 2009 85
Configuration-type Commands – xconfiguration / configuration.xml
IMUX cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

IMUX Custom BW256 Suffix: <S: 0, 12>

Defines the suffix to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconfiguration imux custom bw256 suffix: xxx

IMUX Custom BW256R Prefix: <S: 0, 12>

Defines the prefix to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconfiguration imux custom bw256r prefix: xxx

IMUX Custom BW256R Suffix: <S: 0, 12>

Defines the suffix to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconfiguration imux custom bw256r suffix: xxx

IMUX Custom BW320 Prefix: <S: 0, 12>

Defines the prefix to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconfiguration imux custom bw320 prefix: xxx

IMUX Custom BW320 Suffix: <S: 0, 12>

Defines the suffix to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconfiguration imux custom bw320 suffix: xxx

IMUX Custom BW320R Prefix: <S: 0, 12>

Defines the prefix to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconfiguration imux custom bw320r prefix: xxx

IMUX Custom BW320R Suffix: <S: 0, 12>

Defines the suffix to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconfiguration imux custom bw320r suffix: xxx

IMUX Custom BW384 Prefix: <S: 0, 12>

Defines the prefix to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconfiguration imux custom bw384 prefix: xxx

IMUX Custom BW384 Suffix: <S: 0, 12>

Defines the suffix to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconfiguration imux custom bw384 suffix: xxx

IMUX Custom BW384R Prefix: <S: 0, 12>

Defines the prefix to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconfiguration imux custom bw384r prefix: xxx

D 13887.09
APRIL 2009 86
Configuration-type Commands – xconfiguration / configuration.xml
IMUX cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

IMUX Custom BW384R Suffix: <S: 0, 12>

Defines the suffix to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconfiguration imux custom bw384r suffix: xxx

IMUX Custom BW512 Prefix: <S: 0, 12>

Defines the prefix to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconfiguration imux custom bw512 prefix: xxx

IMUX Custom BW512 Suffix: <S: 0, 12>

Defines the suffix to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconfiguration imux custom bw512 suffix: xxx

IMUX Custom BW512R Prefix: <S: 0, 12>

Defines the prefix to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconfiguration imux custom bw512r prefix: xxx

IMUX Custom BW512R Suffix: <S: 0, 12>

Defines the suffix to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconfiguration imux custom bw512r suffix: xxx

IMUX Custom BW768 Prefix: <S: 0, 12>

Defines the prefix to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconfiguration imux custom bw768 prefix: xxx

IMUX Custom BW768 Suffix: <S: 0, 12>

Defines the suffix to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconfiguration imux custom bw768 suffix: xxx

IMUX Custom BW768R Prefix: <S: 0, 12>

Defines the prefix to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconfiguration imux custom bw768r prefix: xxx

IMUX Custom BW768R Suffix: <S: 0, 12>

Defines the suffix to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconfiguration imux custom bw768r suffix: xxx

IMUX Custom BW1152 Prefix: <S: 0, 12>

Defines the prefix to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconfiguration imux custom bw1152 prefix: xxx

D 13887.09
APRIL 2009 87
Configuration-type Commands – xconfiguration / configuration.xml
IMUX cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

IMUX Custom BW1152 Suffix: <S: 0, 12>

Defines the suffix to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconfiguration imux custom bw1152 suffix: xxx

IMUX Custom BW1152R Prefix: <S: 0, 12>

Defines the prefix to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconfiguration imux custom bw1152r prefix: xxx

IMUX Custom BW1152R Suffix: <S: 0, 12>

Defines the suffix to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconfiguration imux custom bw1152r suffix: xxx

IMUX Custom BW1472 Prefix: <S: 0, 12>

Defines the prefix to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconfiguration imux custom bw1472 prefix: xxx

IMUX Custom BW1472 Suffix: <S: 0, 12>

Defines the suffix to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconfiguration imux custom bw1472 suffix: xxx

IMUX Custom BW1472R Prefix: <S: 0, 12>

Defines the prefix to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconfiguration imux custom bw1472r prefix: xxx

IMUX Custom BW1472R Suffix: <S: 0, 12>

Defines the suffix to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconfiguration imux custom bw1472r suffix: xxx

IMUX Custom BW1920 Prefix: <S: 0, 12>

Defines the prefix to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconfiguration imux custom bw1920 prefix: xxx

IMUX Custom BW1920 Suffix: <S: 0, 12>

Defines the suffix to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconfiguration imux custom bw1920 suffix: xxx

IMUX Custom BW1920R Prefix: <S: 0, 12>

Defines the prefix to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconfiguration imux custom bw1920r prefix: xxx

D 13887.09
APRIL 2009 88
Configuration-type Commands – xconfiguration / configuration.xml
IMUX cont... — IP TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

IMUX Custom BW1920R Suffix: <S: 0, 12>

Defines the suffix to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconfiguration imux custom bw1920r suffix: xxx

Integrator AMXBeacon Mode: <On/Off>

If set to On, the system will start transmitting beacon messages to support AMX’s Dynamic Device Discovery Protocol (DDDP). The beacon string is trans-
mitted as a UDP packet to 239.255.250.250 on port 9131 at random intervals between 30 and 60 seconds. The transmission of the Beacon message
is by default set to Off.
Example: xconfiguration integrator amxbeacon mode: off

Integrator Telepresence Mode: <Off/Point2Point/MultiPoint/Briefer>

Only in use with TANDBERG Experia.
Example: xconfiguration integrator telepresence mode: off

IPProtocol: <IPv4/IPv6/Both>
Defines what IP protocol to use. If set to Both the system will support both IPv4 and IPv6.
Example: xconfiguration ipprotocol: both

IP Assignment: <DHCP/Static>
Defines whether to use DHCP or Static IP assignment. NOTE! This configuration only applies to IPv4.
Example: xconfiguration ip assignment: dhcp

IP Address: <IPAddr>
Defines the IPv4 address to use. Only applicable if Static IP assignment is being used.
Example: xconfiguration ip address:

IP SubnetMask: <IPAddr>
Defines the subnet mask. Only applicable if Static IP assignment is being used.
Example: xconfiguration ip subnetmask:

IP Gateway: <IPAddr>
Defines the gateway address. Only applicable if Static IP assignment is being used.
Example: xconfiguration ip gateway:

IP V6 Address: <IPv6Addr: 0, 43>

Allows static configuration of IP v6 Address.
Example: xConfiguration ip v6 address:

IP DNS Server [1..5] Address: <IPv4v6Addr: 0, 43>

Defines the network addresses for DNS servers. Up to 5 addresses may be specified. If the network addresses are unknown,
please contact your administrator or Internet Service Provider.
Example: xconfiguration ip dns server:

D 13887.09
APRIL 2009 89
Configuration-type Commands – xconfiguration / configuration.xml
IP cont... — ISDN TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

IP DNS Domain Name: <S: 0, 64>

DNS Domain Name is the default domain name suffix which is added to unqualified names.
Example: DNS Domain Name is “example.com”, and the name to lookup is “videosystem” will result in a “videosystem.
example.com” DNS lookup.

IPMedia MaxVideoTXRate: <64..4096>

The MaxVideoTXRate (kbps) defines the desired maximum transmitted call rate for IP calls. This is to be able to limit the outgoing bandwidth
whilst keeping the maximum incoming bandwidth, especially useful for home offices with different upstream and downstream rates, typically ADSL.
Example: xconfiguration ipmedia maxvideotxrate: 384

IRControl Mode: <On/Off>

Enables/disables the TANDBERG Remote Control.
Example: xconfiguration ircontrol mode: off

IRControl NumberKeyMode: <AddCall/DTMF/Presets/Manual>

When pressing a number key on the remote control, while in a call, the user can decide what shall happen. The system can be configured to act automatically or manually.
Please refer to the MXP Administrator Guide and MXP User Guide for further details.
Example: xconfiguration ircontrol numberkeymode: DTMF

ISDN CliNumbSpec: <On/Off>

Explicitely specify Calling Party Number fields Type/Plan to be used in outgoing calls in the ISDN setup message. Using default values if set to Off. When set to on, the system
will use the values set by “ISDN ClinNumPlan” and “ISDN ClinNumbType”.
Example: xConfiguration isdn clinumbspec: Off

ISDN CliNumbType: <0..6>

Value to be used for Calling Party Number field Type. If the value is set to 2, the number type in the setup message will be set to National. This is required in the UAE.
Example: xConfiguration isdn clinumbtype: 5

ISDN CliNumbPlan: <0..14>

Value to be used for Calling Party Number field Plan in the ISDN setup message. If the value is set to 1, the numbering plan in the setup message will signal ISDN. This is re-
quired in UAE.
Example: xConfiguration isdn clinumbplan: 12

ISDN SendComplete: <On/Off>

If set to On the system will send the ISDN message information element Sending Complete.
If set to Off The system will not send Sending Complete. Default is Off.
Example: xconfiguration isdn sendcomplete: on

ISDN SendNumber: <On/Off>

When set to On, the system will send its own numbers to the far end.
When set to Off, the system will not send its own numbers to the far end, but please note that the network may still send your numbers to the far end.
Example: xconfiguration isdn sendnumber: on

D 13887.09
APRIL 2009 90
Configuration-type Commands – xconfiguration / configuration.xml
ISDN cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

ISDN ParallelDial: <On/Off>

When set to On, channels will be dialed and connected in parallel when setting up a BONDING call.
When set to Off, channels will be dialled one by one, which may increase the dialling time.
Example: xconfiguration isdn paralleldial: on

ISDN HLC: <On/Off>

Turns sending of HLC information element in setup message on or off (video calls only). When HLC (Higher Level Capability) is set to on the system will signal, type of call i.e.
video call, telephony or data. HLC must be set to on to work with some PRIs in Italy.
Example: xconfiguration isdn hlc: on

ISDN SpeechTimers: <On/Off>

ISDN Layer 3, telephony calls. When set to Off, there will be no T310, T304, T301
Example: xconfiguration isdn speechtimers: on

ISDN MSN: <On/Off>

The use of MSN (Multiple Subscriber Number) enables you to attach different ISDN terminals, with different numbers, to the same physical ISDN telephone line.
If MSN is set to Only calls to numbers specified for the specific ISDN interfaces will be answered. This service can be ordered from your telephone company.
Example: xconfiguration isdn msn: on

ISDN SubAddress: <S: 0, 20>

Using a sub address enables you to connect up to eight ISDN terminals to the same ISDN telephone number and line. The terminals are addressed by using different sub ad-
*
dresses. To call a terminal with a sub address, separate the ISDN telephone number and the sub address with a . Note that this service has limited access on some ISDN
networks.
Example: xconfiguration isdn subaddress: 15

ISDN PRI NSFTelephony Mode: <On/Off>

Enables/disables use of NSF for telephony. NSF = Network Service Facility
Example: xconfiguration isdn pri nsftelephony mode: on

D 13887.09
APRIL 2009 91
Configuration-type Commands – xconfiguration / configuration.xml
ISDN cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

ISDN PRI NSFTelephony Number: <0..31> Service profiles for Sprint (ref. 2):
Defines what Service Facility to use for telephony if the NSFTelephony Mode is set to On. NSF Service
Example: xconfiguration isdn pri nsftelephony number: 8 0 Reserved
1 Private
2 Inwatts
Service profiles for AT&T (ref.1): 3 Outwatts
4 FX
NSF Service 5 TieTrunk
0 Disable
1 SDN (including GSDN)
2 Toll Free Megacom (800) Service profiles for MCI (ref. 3):
NSF Service
3 Megacom 1 VNET/Vision
6 ACCUNET Switched Digital Service (including Switched Digital International) 2 800
7 Long Distance Service (including AT&T World Connect) 3 PRISM1, PRISMII, WATS
8 International Toll Free Service (I800) 4 900
16 AT&T MultiQuest 5 DAL
23  Call Redirection Service

ISDN PRI NSFVideoTelephony Mode: <On/Off>

Enables/disables use of NSF for video telephony. NSF = Network Service Facility
Example: xconfiguration isdn pri nsfvideotelephony mode: on

ISDN PRI NSFVideoTelephony Number: <0..31>

Defines what Service Facility to use for video telephony if NSFVideoTelephony Mode is set to On.
Example: xconfiguration isdn pri nsfvideotelephony number: 8

ISDN PRI SwitchType: <NI/ATT/Euro/Japan>

Selects the type of PRI switch the system is connected to.
Example: xconfiguration isdn pri switchtype: ni

ISDN PRI InitialRestart: <On/Off>

When restart is set to on the PRI interfaces will be re-initialized after boot.
Example: xconfiguration isdn pri initialrestart: on

ISDN PRI Alert: <On/Off>

If set to On, the system will respond with an alert message to all incoming setup messages. If set to Off (default) the system will respond with an alert
message only to the incoming setup message related to the initial channel. If, in addition, the PBX requires this signalling you will only get connected on
the first incoming channel.
Example: xconfiguration isdn pri alert: on

ISDN PRI ChanId: <On/Off>

Can be used to force sending of channel id information. When set to “on”, the system will signal to the PBX which PRI channels is used for the call.
Default setting is off. Note: This setting must be set to on, to work with an Ericsson MD110 PBX.
Example: xconfiguration isdn pri chanid: on

D 13887.09
APRIL 2009 92
Configuration-type Commands – xconfiguration / configuration.xml
ISDN cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

ISDN PRI L2WindowSize: <1..7>

Max. No. of outstanding Iframes (ISDN Layer 2)
Example: xconfiguration isdn pri L2windowsize:

ISDN PRI Interface MaxChannels: <1..30>

Maximum number of channels the system may use at any given time.
Example: xconfiguration isdn pri interface maxchannels: 23

ISDN PRI Interface HighChannel: <1..31>

The highest numbered B-channel that may be used by the system when selecting channels for outgoing calls.
Example: xconfiguration isdn pri interface highchannel:31

ISDN PRI Interface LowChannel: <1..31>

The lowest numbered B-channel that may be used by the system when selecting channels for outgoing calls.
Example: xconfiguration isdn pri interface lowchannel:1

ISDN PRI Interface Search: <High/Low>

Selects whether to start searching for available B-channels from the highest numbered channel or from the lowest numbered channel.
Example: xconfiguration isdn pri interface search: high

ISDN PRI Interface NumberRangeStart: <S: 0, 24>

Defines the number range start, supported by the PRI interface.
Example: xconfiguration isdn pri interface numberrangestart: 1

ISDN PRI Interface NumberRangeStop: <S: 0, 24>

Defines the number range stop, supported by the PRI interface.
Example: xconfiguration isdn pri interface numberrangestop: 8

ISDN BRI SwitchType: <NI/ATT/Euro/1TR6/Japan/Australia/FETEX>

Selects BRI network type.
Example: xconfiguration isdn bri switchtype: att

ISDN BRI AutoActivation: <Off/Selected/All>

(ISDN Layer 1) Auto activation of the BRI interface. Selected will activate those already On, All will activate all interfaces regardless of status.
Example: xconfiguration isdn bri autoactivation: all

ISDN BRI MaxDeactiveTime: <1..60>

Max duration for Layer 1 in de-active state before auto activation (re)starts
Example: xconfiguration isdn bri maxdeactivetime:

D 13887.09
APRIL 2009 93
Configuration-type Commands – xconfiguration / configuration.xml
ISDN cont... — Key TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

ISDN BRI Alert: <On/Off>

If set to On, the system will respond with an alert message to all incoming setup messages. If set to Off (default) the system will respond with an alert message only
to the incoming setup message related to the initial channel. If, in addition, the PBX requires this signalling you will only get connected on the first incoming channel.
Example: xconfiguration isdn bri alert: on

ISDN BRI ChanId: <On/Off>

Can be used to force sending of channel id information. When set to “on”, the system will signal to the PBX which PRI channels is used for the call.
Default setting is off. Note: This setting must be set to on, to work with an Ericsson MD110 PBX.
Example: xconfiguration isdn bri chanid: on

ISDN BRI InterfaceSearch: <High/Low>

Selects whether to start searching for available B-channels from the highest numbered interface or from the lowest numbered interface.
Example: xconfiguration isdn bri interfacesearch: high

ISDN BRI Interface [1..6] Mode: <On/Off>

Enables/disables the various BRI interfaces.
Example: xconfiguration isdn bri interface 4 mode: off

ISDN BRI Interface [1..6] DirectoryNumber [1..2]: <S: 0, 24>

Specifies the Directory Numbers for the various BRI interfaces.
Example: xconfiguration isdn bri interface 4 directorynumber 2: 6623

ISDN BRI Interface [1..6] SPID [1..2]: <S: 0, 20>

If the network supports automatically retrieval of SPIDs, the command SPIDAutoConfigure should be used.
Example: xconfiguration isdn bri interface 4 spid 2: 55

KeepDuoOpen <On/Off>
Keeps the dual channel open even when there is no presentation video source connected to the endpoint. Requires the optional Natural Presenter Package to be installed.
Example: xconfiguration keepduoopen: off

Key Number0: <On/Off>

Enable or disable the given key on the TANDBERG Remote Control, and using configuration instead of commands.
Example: xconfiguration key number0: on

Key Number1: <On/Off>

Enable or disable the given key on the TANDBERG Remote Control, and using configuration instead of commands.
Example: xconfiguration key number1: on

Key Number2: <On/Off>

Enable or disable the given key on the TANDBERG Remote Control, and using configuration instead of commands.
Example: xconfiguration key number2: on

D 13887.09
APRIL 2009 94
Configuration-type Commands – xconfiguration / configuration.xml
Key cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Key Number3: <On/Off>

Enable or disable the given key on the TANDBERG Remote Control, and using configuration instead of commands.
Example: xconfiguration key number3: on

Key Number4: <On/Off>

Enable or disable the given key on the TANDBERG Remote Control, and using configuration instead of commands.
Example: xconfiguration key number4: on

Key Number5: <On/Off>

Enable or disable the given key on the TANDBERG Remote Control, and using configuration instead of commands.
Example: xconfiguration key number5: on

Key Number6: <On/Off>

Enable or disable the given key on the TANDBERG Remote Control, and using configuration instead of commands.
Example: xconfiguration key number6: on

Key Number7: <On/Off>

Enable or disable the given key on the TANDBERG Remote Control, and using configuration instead of commands.
Example: xconfiguration key number7: on

Key Number8: <On/Off>

Enable or disable the given key on the TANDBERG Remote Control, and using configuration instead of commands.
Example: xconfiguration key number8: on

Key Number9: <On/Off>

Enable or disable the given key on the TANDBERG Remote Control, and using configuration instead of commands.
Example: xconfiguration key number9: on

Key Star: <On/Off>

Enable or disable the given key (*) on the TANDBERG Remote Control, and using configuration instead of commands.
Example: xconfiguration key star: on

Key Square: <On/Off>

Enable or disable the given key (#) on the TANDBERG Remote Control, and using configuration instead of commands.
Example: xconfiguration key square: on

Key Connect: <On/Off>

Enable or disable the given key (green Call key) on the TANDBERG Remote Control, and using configuration instead of commands.
Example: xconfiguration key connect: on

D 13887.09
APRIL 2009 95
Configuration-type Commands – xconfiguration / configuration.xml
Key cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Key Disconnect: <On/Off>

Enable or disable the given key (red End Call key) on the TANDBERG Remote Control, and using configuration instead of commands.
Example: xconfiguration key disconnect: on

Key Up: <On/Off>

Enable or disable the given key (arrow up) on the TANDBERG Remote Control, and using configuration instead of commands.
Example: xconfiguration key up: on

Key Down: <On/Off>

Enable or disable the given key (arrow down) on the TANDBERG Remote Control, and using configuration instead of commands.
Example: xconfiguration key down: on

Key Right: <On/Off>

Enable or disable the given key (arrow right) on the TANDBERG Remote Control, and using configuration instead of commands.
Example: xconfiguration key right: on

Key Left: <On/Off>

Enable or disable the given key (arrow left) on the TANDBERG Remote Control, and using configuration instead of commands.
Example: xconfiguration key left: on

Key Selfview: <On/Off>

Enable or disable the given key (Selfview) on the TANDBERG Remote Control, and using configuration instead of commands.
Example: xconfiguration key selfview: on

Key Layout: <On/Off>

Enable or disable the given key (Layout) on the TANDBERG Remote Control, and using configuration instead of commands.
Example: xconfiguration key layout: on

Key Phonebook: <On/Off>

Enable or disable the given key (Phonebook) on the TANDBERG Remote Control, and using configuration instead of commands.
Example: xconfiguration key phonebook: on

Key Cancel: <On/Off>

Enable or disable the given key (x - Cancel) on the TANDBERG Remote Control, and using configuration instead of commands.
Example: xconfiguration key cancel: on

Key MicOff: <On/Off>

Enable or disable the given key (yellow Mic Off key) on the TANDBERG Remote Control, and using configuration instead of commands.
Example: xconfiguration key micoff: on

D 13887.09
APRIL 2009 96
Configuration-type Commands – xconfiguration / configuration.xml
Key cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Key Presentation: <On/Off>

Enable or disable the given key (blue Presentation key) on the TANDBERG Remote Control, and using configuration instead of commands.
Example: xconfiguration key presentation: on

Key VolumeUp: <On/Off>

Enable or disable the given key (Volume +) on the TANDBERG Remote Control, and using configuration instead of commands.
Example: xconfiguration key volumeup: on

Key VolumeDown: <On/Off>

Enable or disable the given key (Volume ­–) on the TANDBERG Remote Control, and using configuration instead of commands.
Example: xconfiguration key volumedown: on

Key Ok: <On/Off>

Enable or disable the given key (OK - Menu key) on the TANDBERG Remote Control, and using configuration instead of commands.
Example: xconfiguration key ok: on

Key ZoomIn: <On/Off>

Enable or disable the given key (Zoom +) on the TANDBERG Remote Control, and using configuration instead of commands.
Example: xconfiguration key zoomin: on

Key ZoomOut: <On/Off>

Enable or disable the given key (Zoom –) on the TANDBERG Remote Control, and using configuration instead of commands.
Example: xconfiguration key zoomout: on

Key Grab: <On/Off>

Enables/disables the signal which is sent to the codec when grabbing and touching the rubber lines on each side of the TANDBERG Remote Control.
Example: xconfiguration key grab: on

Key Cabinet: <On/Off>

Enables/disables the headset key in front of the cabinet. Applies to TANDBERG 1000 MXP only.
Example: xconfiguration key cabinet: on

Key Presets: <On/Off>

Enable or disable the given key on the TANDBERG Remote Control (TRC4), and using configuration instead of commands.
Example: xconfiguration key presets: on

Key FarEnd: <On/Off>

Enable or disable the given key on the TANDBERG Remote Control (TRC4), and using configuration instead of commands.
Example: xconfiguration key farend: on

D 13887.09
APRIL 2009 97
Configuration-type Commands – xconfiguration / configuration.xml
Key cont... — Kiosk TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Key Services: <On/Off>

Enable or disable the given key on the TANDBERG Remote Control (TRC4), and using configuration instead of commands.
Example: xconfiguration key services: on

Key Help: <On/Off>

Enable or disable the given key on the TANDBERG Remote Control (TRC4), and using configuration instead of commands.
Example: xconfiguration key help: on

Key MainCam: <On/Off>

Enable or disable the given key on the TANDBERG Remote Control (TRC4), and using configuration instead of commands.
Example: xconfiguration key maincam: on

Key PC: <On/Off>

Enable or disable the given key on the TANDBERG Remote Control (TRC4), and using configuration instead of commands.
Example: xconfiguration key pc: on

Key DocCam: <On/Off>

Enable or disable the given key on the TANDBERG Remote Control (TRC4), and using configuration instead of commands.
Example: xconfiguration key doccam: on

Key VCR: <On/Off>

Enable or disable the given key on the TANDBERG Remote Control (TRC4), and using configuration instead of commands.
Example: xconfiguration key vcr: on

Key AUX: <On/Off>

Enable or disable the given key on the TANDBERG Remote Control (TRC4), and using configuration instead of commands.
Example: xconfiguration key aux: on

Keyboard Layout: <English/US/Norwegian/Swedish/German/French/User>

Defines the layout of the keyboard, if connected.
Example: xconfiguration keyboard layout: us

Kiosk AllowIRControl: <On/Off>

Enables (On) or disables (Off) the use of all keys on the remote control.
Example: xconfiguration kiosk allowircontrol: on

Kiosk AutoDial: <On/Off>

Enables (On) or disables (Off) auto dial. The system will automatically dial to the first contact in the Phone Book when the handset is lifted. If this contact is busy, the system will call
the second number in the Phone Book and so on. If the user places the handset in the cradle, the system will switch to Speaker Mode. Only the Far End system can end the call.
Example: xconfiguration kiosk autodial: on

D 13887.09
APRIL 2009 98
Configuration-type Commands – xconfiguration / configuration.xml
Kiosk cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Kiosk LanguageMenu Mode: <On/Off>

Enables (On) or disables (Off) language menu in Kiosk mode.
Example: xconfiguration kiosk languagemenu mode: on

Kiosk LanguageMenu English: <On/Off>

Enables (On) or disables (Off) language menu in English.
Example: xconfiguration kiosk languagemenu english: on

Kiosk LanguageMenu German: <On/Off>

Enables (On) or disables (Off) language menu in German
Example: xconfiguration kiosk languagemenu german: on

Kiosk LanguageMenu French: <On/Off>

Enables (On) or disables (Off) language menu in French
Example: xconfiguration kiosk languagemenu french: on

Kiosk LanguageMenu Italian: <On/Off>

Enables (On) or disables (Off) language menu in Italian
Example: xconfiguration kiosk languagemenu italian: on

Kiosk LanguageMenu Norwegian: <On/Off>

Enables (On) or disables (Off) language menu in Norwegian
Example: xconfiguration kiosk languagemenu norwegian: on

Kiosk LanguageMenu Swedish: <On/Off>

Enables (On) or disables (Off) language menu in Swedish
Example: xconfiguration kiosk languagemenu swedish: on

Kiosk LanguageMenu Spanish: <On/Off>

Enables (On) or disables (Off) language menu in Spanish
Example: xconfiguration kiosk languagemenu spanish: on

Kiosk Menu: <On/Off>

Enables (On) or disables (Off) Kiosk menu to appear on screen.
Example: xconfiguration kiosk menu: on

Kiosk Mode: <On/Off>

Enables (On) or disables (Off) Kiosk mode.
Example: xconfiguration kiosk mode: on

D 13887.09
APRIL 2009 99
Configuration-type Commands – xconfiguration / configuration.xml
Kiosk cont... — LoS TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Kiosk OneClickConnect: <On/Off>

If turned On, you can make a call with a single click on the green call button the remote control. The system will call the first entry in “My Contacts” in the Phone Book. NOTE!
The one-click-connect functionality will only work in Kiosk Mode. If set to Off: Does not allow for one click connect in Kiosk mode.
Example: xconfiguration kiosk oneclickconnect: off

Kiosk Phonebook: <Local/CorporateDirectory>

Local: The system will use the Local Phone Book in Kiosk Mode. CorporateDirectory: The system will use the Corporate Directory in Kiosk Mode.
Example: xconfiguration kiosk phonebook: local

LocalLayout Mode: <Full/2Split/POP/POPwide>

Defines the picture layout to use on the local main monitor. POP and POPWide should only be used on wide screen monitors.
Example: xconfiguration locallayout mode: full

LocalLayout Toggle: <PIP/POP>

Defines the behaviour of the Layout button the remote control.
If set to POP the system will toggle through the different LocalLayout modes when pressing the Layout button.
If set to PIP, the system will display a PIP when pressing the Layout button.
Example: xconfiguration locallayout toggle: pip

Logo: <On/Off>
If set to On the system will display a company logo will appear in the background of the welcome menu. NOTE! The TANDBERG logo will be displayed if no other company logo is uploaded.
Example: xconfiguration logo: on

LoS Duration Exponent: <10..30> The duration of the LoS-pulse can be calcu-
lated from:
Example: xconfiguration los duration exponent: 15
Offset + 2 Exponent
Duration =
LoS Duration Offset: <0..65534> bit rate
LoS configurations are relevant
Offset is specified in milliseconds
for systems with NET interface
Example: xconfiguration los duration offset: 100
(External Network) only.

LoS Inhibit: <0..65534>

Specifies the number of seconds to wait before issuing a new LOS pulse if the codec regains and subsequently loses H.221 frame align-
ment.
Example: xconfiguration los inhibit: 15

D 13887.09
APRIL 2009 100
Configuration-type Commands – xconfiguration / configuration.xml
LoS cont... — Multipoint TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

LoS Initial: <0..65534> LoS configurations are relevant

Specifies the maximum number of seconds to wait for H.221 frame alignment during call setup before asserting the LOS signal. for systems with NET interface
Example: xconfiguration los initial: 5 (External Network) only.

LoS Polarity: <Positive/Negative>

Set LOS pulse polarity.
Example: xconfiguration los polarity: positive

LoS Retry: <0..65534>

Specifies the number of seconds to wait before issuing a new LOS pulse in case the codec does not regain H.221 frame alignment.
Example: xconfiguration los retry: 25

MainVideoSource: <1/2/3/4/5/6>
Defines which video input to be used as the main video source.
Example: xconfiguration mainvideosource: 2

MaxBandwidth: <128..6144>
Limit max bandwidth usage for the system. Related to IPMedia MaxVideoTXRate, which only controls upstream bandwidth.
Example: xconfiguration maxbandwidth: 6144

Multipoint Mode: <Off/Multisite/Multiway>

Set to MultiSite if you have the optional feature MultiSite installed.
Set to Multiway to enable this feature. TANDBERG MultiwayTF will extend point to point calls to conferences on MCU’s hosted on the network over H.323 and SIP. The new partici-
pant will be consulted before he is added to the conference. The Multiway feature requires the uses of the TANDBERG Vide Communications Server (VCS) software Ver. X4.1 or
higher, and the uses of the TANDBERG/Codian MCU software Ver. 3.0 or higher.
Set to Off if none of the above features are being used.
Example: xconfiguration multipoint mode: off

Multipoint MultiwayURI: <S: 0, 60>

Specify the Multiway URI. When calling Multiway on SIP the SIP prefix must be added to the URI for the endpoint who initiates the Multiway call
Example: xconfiguration multipoint multiwayuri: “[email protected]“
Example with SIP prefix: xconfiguration multipoint multiwayuri: “sip:[email protected]“

Multipoint MultiwayMultiprotocol: <On/Off>

Enable/disable the Multiway multi-protocol.
Example: xconfiguration multipoint multiwaymultiprotocol: off

Multipoint MultiwayStartupPeriod: <0..21>

Specify the startup period (in seconds) for the Multiway call.
Example: xconfiguration multipoint multiwaystartupperiod: 10

D 13887.09
APRIL 2009 101
Configuration-type Commands – xconfiguration / configuration.xml
NAT — NTP TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

NAT Mode: <On/Off/Auto>

When set to On the system will signal the configured “NAT Address” in place of its own IP-address within Q.931 and H.245. When set to
Off the system will signal the real IP Address. When set to Auto the system will try to 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.
Example: xconfiguration nat mode: on Configuration of NAT (Network
Address Translation) router.
NAT Address: <IPAddr>
This must be 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-2373.
Example: xconfiguration nat address: 127.0.0.1

NetProfile [1..7] Name: <S: 0, 8>

Defines the name of the NetProfile.
Example: xconfiguration netprofile 4 name: MyProfile

NetProfile [1..7] CallPrefix: <S: 0, 9>

A call prefix can be added to each NetProfile. If a call prefix is added, this prefix will automatically be added in front of the number being dialled. This is useful if you have a fixed
prefix for a specific service provider.
Example: xconfiguration netprofile 4 callprefix: 50

NetProfile [1..7] CallSuffix: <S: 0, 30>

A call suffix can be added to each NetProfile. If a call suffix is added, the suffix will automatically be appended to the number being dialled.
Example: xconfiguration netprofile 2 CallSuffix: 24

NetProfile [1..7] Network: <H320/H323/SIP/Auto>

Defines what type of Network the NetProfile will use. The NetProfile 4, 5 and 6 can be configured, the other ones are predefined and cannot be changed by the user.
NetProfile 1 is Auto; NetProfile 2 is H320; NetProfile 3 is H323; NetProfile 7 is SIP;
If set to Auto the system will parse the number to dial and decide what network to use based on this.
Example: xconfiguration netprofile 4 network: h323

NTP Mode: <Manual/Auto>

If set to 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 The Network Time Protocol (NTP) is used to synchronize
will use the static defined NTP server address specified by the user. the time of the system to a reference time server. The
If set to Manual the system will always use the static defined NTP server address specified by the user. time server will subsequently be queried every 24th hour
Example: xconfiguration ntp mode: manual for time updates.
The system will use the time to timestamp messages
NTP Address: <S: 0, 64> transmitted to Gatekeepers or Border Controllers requir-
Defines the NTP server address. Will be used if NTP Mode is set to Manual or if set to Auto and no address is sup- ing H.235 authentication.
plied by a DHCP server.
Example: xconfiguration ntp address:

D 13887.09
APRIL 2009 102
Configuration-type Commands – xconfiguration / configuration.xml
OptionKey — OSD TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

OptionKey Features: <S: 0, 16>

The system requires a valid option key to activate MultiSite and/or Presenter functionality.
Example: xconfiguration optionkey features: 5952754234583129

OptionKey Bandwidth: <S: 0, 16>

The system requires a valid option key to define the maximum bandwidth to use.
Example: xconfiguration optionkey bandwidth: 9952754234483329

OSD CallDuration Mode: <On/Off>

The call duration can be displayed on screen. The timer showing the duration of the call is displayed in the bottom right corner of the screen.
Example: xconfiguration osd callduration mode: on

OSD Mode: <On/Off>

Enables/disables the On Screen Display (OSD). If set to Off there will be no graphics displayed on the monitors.
Example: xconfiguration osd mode: on

OSD Menu Mode: <On/Off>

Enabled/disables the navigation menu on the system. If set to Off no system menus may be entered, but the system will still display icons, call progress
information boxes etc. We recommend that you to set this to Off when controlling the system from an external control system.
Example: xconfiguration osd menu mode: off

OSD Menu Password: <S: 0, 5>

If a Menu Password is defined, the user has to enter this password when accessing the Administrator Settings page in the menu.
Example: xconfiguration osd menu password: 123

OSD Menu Language: <English/German/Norwegian/French/Swedish/Italian/Portuguese/Japanese/Chinese/TraditionalChinese/Russian/Spanish/Korean/Finnish/Thai/Arabic/

Polish/Czech/Hungarian/Turkish/Danish/Romanian/Welsh>
Defines the menu language.
Example: xconfiguration osd menu language: english

OSD Menu WelcomeMenu: <On/Off>

The Welcome Menu contains the Main Menu, System Status, System Name and Dial in numbers.
If set to On, the Welcome Menu is shown when the system wakes up from standby mode.
If set to Off, the Welcome Menu is not shown when the system wakes up from standby mode.
However, pressing the OK button the remote control will display the Welcome Menu.
Example: xconfiguration osd menu welcomemenu: on

OSD Menu DisplayWelcomeTime: <On/Off>

If set to On the welcome date and time is displayed on the welcome menu. Requires the NTP IP settings to be configured to synchronize with the NTP
time server.
If set to Off the welcome date and time is hidden from the welcome menu.
Example: xconfiguration osd menu displaywelcometime: on

D 13887.09
APRIL 2009 103
Configuration-type Commands – xconfiguration / configuration.xml
OSD cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

OSD Menu DisplayWelcomeText: <On/Off>

If set to Off, the system will use the system name and dial in numbers as default Welcome Text.
If set to On the system will display the Welcome Text defined by the user.
Example: xconfiguration osd menu displaywelcometext: on

OSD Menu WelcomeText: <S: 0, 30>

Defines the welcome text to be displayed if DisplayWelcomeText is set to On.
Example: xconfiguration osd menu welcometext: “Welcome to MyTANDBERG”

OSD Menu DisableTimeout: <On/Off>

If set to On, the menu will not time out automatically. Press Cancel on the remote control to hide the main menu manually.
If set to Off, the menu will time out automatically after 15 seconds if there is no activity on the remote control. The time-out applies when the system is in
a call only. Outside a call, the menu will not time out.
Example: xconfiguration osd menu disabletimeout: off

OSD Menu BalloonHelp: <On/Off>

Enables/Disables the Balloon Help window.
Example: xconfiguration osd menu balloonhelp: on

OSD Menu InputEditor Language: <Off/Japanese/Chinese/Korean/Russian>

When the Input Editor Language is set to Chinese, Korean, Japanese or Russian the user will be able to enter Chinese/Korean/
Japanese/Russian characters into an input field like the System Name or Phone Book, using the remote control.
When set to Off the user will only be able to enter ASCII characters into an input field like the System Name or Phone Book, using
the remote control.
Example: xconfiguration osd menu inputeditor language: off

OSD Menu Simple: <On/Off>

Set to On to enable the Simple Menu mode with some of the buttons hidden. The menus affected and the visible buttons are:
• Make a Call - Make a Call (green), Standby (red), Presentation, Control Panel and Back.
• Presentation - PC and Back.
• Control Panel - Diagnostics, Restart, Administrator Settings and Back.
• Control Panel (Administrator Settings) - Diagnostics, Restart and Back
Set to Off to enable normal menu mode.
Example: xconfiguration osd menu simple: off

OSD Menu IconPlacement: <Left/Right>

Applies to the following icon indicators: Microphone Off, Volume Off, On Air, Encryption, Bad Network, Telephone, Duo Video and Camera Tracking. Places
the icons in the top left corner or the top right corner of the screen.
Example: xconfiguration osd menu iconplacement: right

OSD Menu CodecLabel: <S: 0, 48>

Specify the text of the codec label.
Example: xconfiguration osd menu codeclabel:

D 13887.09
APRIL 2009 104
Configuration-type Commands – xconfiguration / configuration.xml
OSD cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

OSD Menu DisplayLogo: <On/Off>

Enables/disables the Display Logo on screen.
Example: xconfiguration osd menu displaylogo: on

OSD Icon MicOff: <On/Off>

Enables/Disables the Microphone Off icon.
Example: xconfiguration osd icon micoff: on

OSD Icon VolumeOff: <On/Off>

Enables/Disables the Volume Off icon.
Example: xconfiguration osd icon volumeoff: on

OSD Icon OnAir: <On/Off>

Enables/Disables the On Air icon.
Example: xconfiguration osd iconair: on

OSD Icon Encryption: <On/Off>

Enables/Disables the Encryption icon.
Example: xconfiguration osd icon encryption: on

OSD Icon BadNetwork: <On/Off>

Enables/Disables the Bad Network icon.
Example: xconfiguration osd icon warning: on

OSD Icon Telephone: <On/Off>

Enables/Disables the Telephone icon.
Example: xconfiguration osd icon telephone: on

OSD Icon DuoVideo: <On/Off>

Enables/Disables the DuoVideo icon.
Example: xconfiguration osd icon duovideo: on

OSD Icon CameraTracking: <On/Off>

Enables/Disables the Camera Tracking icon.
Example: xconfiguration osd icon cameratracking: on

OSD Icon Headset: <On/Off>

Enables/Disables the Headset icon. Applies to systems with headset.
Example: xconfiguration osd icon headset: on

D 13887.09
APRIL 2009 105
Configuration-type Commands – xconfiguration / configuration.xml
OSD cont... — PacketlossDownSpeed TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

OSD MCUStatusLine Mode: <On/Off/Auto>

If set to On the MultiSite/MCU/DuoVideo indicators will be displayed and provide information about the conference.
If set to Off the MultiSite/MCU/DuoVideo indicators will not be displayed.
If set to Auto the MultiSite/MCU/DuoVideo indicators will be displayed for a few seconds and then timed out. When grabbing the remote control, the
indicators will be shown again.
Example: xconfiguration osd mcustatusline mode: on

OSD Offset Mode: <On/Off>

Set Offset Mode to On to add extra margins for the on screen menu. If you experience problems viewing all text or buttons on the screen you can try to
set Offset Mode to Off. This problem can occur on some 720p screens.
Example: xconfiguration osd offset mode: off

OSD CallDuration Mode: <On/Off>

Set to On to display the call duration on screen while in a call. Set to Off to not display the call duration.
Example: xconfiguration osd callduration mode: off

OSD PasswordViewAdminSettings: <On/Off>

When set to On, you will need to enter the menu password to view the administrator settings.
Example: xconfiguration osd passwordviewadminsettings: off

PictureProgram [1..4] Layout: <Full/2Split/4Split/2+1Split/3+1Split/5+1Split>

Example: xconfiguration pictureprogram 1 layout: full

PictureProgram [1..4] Window [1..6] Picture: <LocalMain/LocalDuo/Current/Previous/Duo/RemoteMain/RemoteDuo/JPEG/TandbergMonitor1/TandbergMoni- The Picture Programs are used
tor2/None> to define custom picture layouts
Example: xconfiguration pictureprogram 1 window 2 picture: localmain to be displayed locally.

PictureProgram [1..4] Window [1..6] Call: <1..11>

Example: xconfiguration pictureprogram 1 window 2 call: 4

PresentationStart: <Manual/Auto>
If set to Auto, the Dual Stream is started automatically when a presentation is initiated from the menu or directly from the remote control
(requires that the system has Presenter option installed and the far end side also supports Dual Stream).
If set to Manual, the Dual Stream must be started manually.
Example: xconfiguration presentationstart: auto

PacketlossDownSpeed Mode: <Auto/Off>

If set to Auto, the system will attempt to down speed the video channel from the sender by sending flow control messages if packet loss is encountered.
If set to Off, the system will not request down speeding based on packet loss.
Example: xconfiguration packetlossdownspeed mode: auto

D 13887.09
APRIL 2009 106
Configuration-type Commands – xconfiguration / configuration.xml
PresentationSoftKey — Preset [1..15] TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

PresentationSoftkey: <DuoScr/MainScr>
You can configure the Presentation key on the remote control to either select dual source or main source when in a call, Default is DuoSrc (dual source).
Example: xconfiguration presentationsoftkey: mainscr

Preset [1..15] Name: <S: 0, 20>

Defines the Preset Name.
Example: xconfiguration preset 1 name: AnyName

Preset [1..15] Audio Inputs Microphone [1..3] Mode: <On/Off>

Example: xconfiguration preset 1 audio inputs mi-

crophone 2: on

Preset [1..15] Audio Inputs Line [1..3] Mode: <On/Off>

Example: xconfiguration preset 1 audio inputs line Presets should never be

2: on modified manually, except for the
Preset Name.
Preset [1..15] MainVideoSource: <1/2/3/4/5/6> Please refer to the xcommands:
- PresetStore
Example: xconfiguration preset 1 mainvideosource: 1 - PresetClear

Preset [1..15] DuoVideoSource: <0/1/2/3/4/5/6> NOTE! The preset configurations

are numbered from 1 to 15,
Example: xconfiguration preset 1 duovideosource: 1 whilst the PresetStore/
PresetClear commands are
referring presets from 0 to 14,
Preset [1..15] SwitchVideoSource: <0/1/2/3/4/5/6>
i.e. the configurations are offset
Will switch the TANDBERG Video Switch to the given input when the preset is activated.
by 1.
Example: xconfiguration preset 1 switchvideosource: 1

Preset [1..15] Camera Brightness Mode: <Manual/Auto>

Interpretation of the settings chosen will depend on the camera type you use. If in doubt,
consult your camera’s user documentation.
Example: xconfiguration preset 1 camera brightness mode: auto

Preset [1..15] Camera Brightness Level: <0..31>

Interpretation of the settings chosen will depend on the camera type you use. If in doubt,
consult your camera’s user documentation.
Example: xconfiguration preset 1 camera brightness level: 12

D 13887.09
APRIL 2009 107
Configuration-type Commands – xconfiguration / configuration.xml
Preset [1..15] cont... — QoS TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Preset [1..15] Camera Autofocus: <On/Off>

Enables or disables auto focus when activating a preset. If enabled, auto focus will be turned on for 5 seconds. If
disabled, the preset’s focus value will be used. Default is Off.
Example: xconfiguration preset 1 camera autofocus: off

Preset [1..15] Camera Focus: <0..65534>

Presets should never be
Interpretation of the settings chosen will depend on the camera type you use. If in doubt, consult your camera’s user modified manually, except for the
documentation. Preset Name.
Example: xconfiguration preset 1 camera focus: 32768
Please refer to the xcommands:
- PresetStore
Preset [1..15] Camera Pan: <-32768..32766 >
- PresetClear
Interpretation of the settings chosen will depend on the camera type you use. If in doubt, consult your camera’s user
documentation. NOTE! The preset configurations
Example: xconfiguration preset 1 camera pan: 0 are numbered from 1 to 15,
whilst the PresetStore/
Preset [1..15] Camera Tilt: <-32768..32766> PresetClear commands are
Interpretation of the settings chosen will depend on the camera type you use. If in doubt, consult your camera’s user referring presets from 0 to 14,
documentation. i.e. the configurations are offset
Example: xconfiguration preset 1 camera tilt: 0 by 1.

Preset [1..15] Camera Zoom: <0..65534>

Interpretation of the settings chosen will depend on the camera type you use. If in doubt, consult your camera’s user
documentation.
Example: xconfiguration preset 1 camera zoom: 32768

QoS Precedence Telephony Audio: <0/1/2/3/4/5/6/7/Auto/Off>

Example: xconfiguration qos precedence telephony audio: auto

QoS Precedence Telephony Signalling: <0/1/2/3/4/5/6/7/Auto/Off>

Configures the different Quality
Example: xconfiguration qos precedence telephony signalling: auto of Service (QoS) algorithms
supported by the system. QoS
QoS Precedence VideoTelephony Audio: <0/1/2/3/4/5/6/7/Auto/Off> are used to set priority on QoS
enabled IP networks.
Example: xconfiguration qos precedence videotelephony audio: auto

QoS Precedence VideoTelephony Signalling: <0/1/2/3/4/5/6/7/Auto/Off>

Example: xconfiguration qos precedence videotelephony signalling: auto

D 13887.09
APRIL 2009 108
Configuration-type Commands – xconfiguration / configuration.xml
QoS cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

QoS Precedence VideoTelephony Video: <0/1/2/3/4/5/6/7/Auto/Off>

Example: xconfiguration qos precedence videotelephony video: auto

QoS Precedence VideoTelephony Data: <0/1/2/3/4/5/6/7/Auto/Off>

Example: xconfiguration qos precedence videotelephony data: auto

QoS Diffserv Telephony Audio: <0..63>

Example: xconfiguration qos diffserv telephony audio: 15

QoS DiffServ Telephony Signalling: <0..63>

Example: xconfiguration qos diffserv telephony signalling: 25

QoS DiffServ VideoTelephony Audio: <0..63>

Configures the different Quality
Example: xconfiguration qos diffserv videotelephony audio: 15 of Service (QoS) algorithms
supported by the system. QoS
QoS DiffServ VideoTelephony Signalling: <0..63> are used to set priority on QoS
enabled IP networks
Example: xconfiguration qos diffserv videotelephony signalling: 15

QoS DiffServ VideoTelephony Video: <0..63>

Example: xconfiguration qos diffserv videotelephony video: 15

QoS DiffServ VideoTelephony Data: <0..63>

Example: xconfiguration qos diffserv videotelephony data: 15

QoS Mode: <Precedence/Diffserv/Off>

Example: xconfiguration qos mode: precedence

QoS ToS: <MinDelay/MaxThrough/MaxReliable/MinCost/Off>

Example: xconfiguration qos tos: mindelay

D 13887.09
APRIL 2009 109
Configuration-type Commands – xconfiguration / configuration.xml
QoS cont... — ScreenSaver TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

QoS RSVP: <Auto/Off>

Example: xconfiguration qos rsvp: auto

RemoteSwUpgrade Mode: <On/Off>

If set to On, software can be upgraded from a far end system.
Example: xconfiguration remoteswupgrade mode: on

RemoteSwUpgrade Password: <S: 0, 16>

If RemoteSwUpgrade Mode is set to On and a Password is defined, the remote system must supply this Password in order to upload new software to the unit.
Example: xconfiguration remoteswupgrade password: 123

RTP Ports: <Static/Dynamic>

Affects the port numbers used for H.323 call signalling. Dynamic will give random ports. Static will give ports within a static predefined range [5555–5574]. Dynamic should be
used during firewall traversal.
Example: xconfiguration rtp ports: dynamic

RTP MTU: <400..1400>

Maximum Transfer Unit is the number of bytes of video payload per packet.
Example: xconfiguration rtp mtu: 1200

Screensaver Mode: <On/Off>

Enables/disables if screen saver is to be activated if there is no system activity.
Example: xconfiguration screensaver mode: on

Screensaver Delay: <1..480>

Specifies how long (in minutes) the system shall wait before activating screen saver when there is now system activity.
Example: xconfiguration screensaver delay: 15

D 13887.09
APRIL 2009 110
Configuration-type Commands – xconfiguration / configuration.xml
SecurityLog — SelfViewOnStartup TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

SecurityLog Mode: <On/Off>

When enabled, the security log feature will now log all security related events and configuration changes within the eventlog file on the endpoint, allowing an administrator to
ensure all access to the system is properly logged and can be reviewed at a later point. When enabled, the security log will maintain a record of the following events:

Failed password attempts

• Successful logins
• Software upgrades
• System restarts

The following configuration changes will also be logged:

• System Unit name • External Services Mode and Protocol • DNS Server [1..5] Address
• International Name Display Name • External Manager Protocol • VNC Password
• Option Keys, Feature Keys, Bandwidth • SNMP Community Name, System Contact, • Streaming Password
• IP Protocol System Location, Host IP Address • Remote Software Upgrade Password
• Telnet Challenge Port • H.323 Call Setup Mode • IEEE 802.1x Password
• Auto Answer Mode • H.323 Gatekeeper Discovery, Address, Au- • On Screen Display Menu Password
thentication Mode
• Far End Camera Control Mode • Serial Port Mode
• IP Assignment, IP Address, Subnet Mask,
• Strict Password Default Gateway, DNS Domain Name • Security Level
• Corporate Directory Protocol • IPv6 Address • Security Log

Enabling/Disabling the following services:

• Telnet, SSH, HTTP, H.323, Remote Software Upgrade, SNMP, FTP, Remote Parameter, Telnet Challenge, HTTPS, SIP, HTTPSVerify.

Example: xconfiguration securitylog mode: on

Security Level: <0..2>

The Security level parameter restricts the access to the system:
When configured for level 0, the system will have a similar security regime as F7.x. Password storage, encryption, logging etc. will not be influenced by setting this to 0.
When configured for level 1, the system password can only be changed once every 24 hours and three failed attempts to log into the system will lock the interface for 30 min-
utes. If a password is set, the system will ask for password confirmation from all web sessions every 15 minutes to ensure the session is still active.
When set to level 2, the system will include all security parameters within level 1 and will also prevent normal access to the web server. If a password is set, level 2 will time out
all active management sessions every 15 minutes, prompting for password input.
Example: xconfiguration security level: 0

SelfViewOnStartup: <On/Off>
If set to On the system will display the local main video source on the main monitor when the system is started.
Example: xconfiguration selfviewonstartup: on

D 13887.09
APRIL 2009 111
Configuration-type Commands – xconfiguration / configuration.xml
SerialPort — SIP TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

SerialPort [1] Mode: <Control/Transparent/Direct/Off> NOTE! Port 1 Only

Control: Gives access to the Command Line Interface.
Transparent: Enables transmission of text during call on a line by line basis.
Direct: Enables transmission binary data during call.
Off: Disables any of the options above.
Example: xconfiguration serialport 1 mode: control

SerialPort [2] Mode: <VISCA/Auto/Off> NOTE! Port 2 Only

Defines Camera control mode.
Example: xconfiguration serialport 2 mode: auto

SerialPort [1] Direct Buffer: <0..16384> NOTE! Port 1 Only

Specifies the size of the buffer used in direct mode. Try setting this value higher if you need a continuous stream of data on the receiving end. Higher
values introduces more delay.
Example: xconfiguration serialport 1 direct buffer: 5120

SerialPort [1..2] BaudRate: <1200/2400/4800/9600/19200/38400/57600/115200>

Specify the baud rate on a serial port.
Example: xconfiguration serialport 1 baudrate: 9600

SerialPort [1..2] Parity: <None/Odd/Even>

Specify the Parity on a Serial Port
Example: xconfiguration serialport 1 parity: odd

SerialPort [1..2] DataBits: <7/8>

Specify the number of databits on a Serial Port
Example: txconfiguration serialport 1 databits: 7

SerialPort [1..2] StopBits: <1/2>

Specify the number of stopbits on a Serial Port
Example: xconfiguration serialport 1 stopbits: 2

SIP Mode: <On/Off>

On: Setting the SIP mode to on will enable the system for incoming and outgoing SIP calls.
Off: Setting the SIP mode to off will disable incoming and outgoing SIP calls from the system.
Example: xconfiguration sip mode: on

SIP Server Discovery: <Manual/Auto>

Manual: When Manual is selected, the manually configured SIP Server address will be used
Auto: When Auto is selected, the SIP Server address is obtained using Dynamic Host Configuration Protocol (DHCP).
Example: xconfiguration sip server discovery: manual

D 13887.09
APRIL 2009 112
Configuration-type Commands – xconfiguration / configuration.xml
SIP cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

SIP Server Address: <S: 0, 255>

The Server Address is the manually configured address for the outbound proxy and registrar. 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
Example: xconfiguration sip server address:

SIP Server Type: <Auto/Nortel/Microsoft/Cisco/Siemens/Alcatel/Experimental>

Enables SIP extensions and special behavior for a SIP Server vendor.
Auto: Should be used when registering to standard SIP servers like OpenSer.
Nortel: Must be used when registering to a Nortel MCS 5100 or MCS 5200 PBX.
Microsoft: Must be used when registering to a Microsoft LCS or OCS server.
Cisco: Must be used when registering to a Cisco CallManager version 5 or later.
Alcatel: Must be used when registering to a Alcatel-Lucent OmniPCX Enterprise R7 or later.
Siemens: Must be used when registering to a Siemens HiPath 8000.
Telio: Must be used in combination with a Telio subscription (www.telio.no).
Experimental: Can be used if auto is not working. NOTE! This mode is for testing purposes only.
Example: xconfiguration sip server type: microsoft

SIP Authentication UserName: <S: 0, 80>

This is the user name part of the credentials used to authenticate towards the SIP Server.
Example: xconfiguration sip authentication username:

SIP Authentication Password: <S: 0, 60>

This is the password part of the credentials used to authenticate towards the SIP Server.
Example: xconfiguration sip authentication password:

SIP Transport Default: <Auto/TCP/UDP/TLS>

Select the default transport type to be used for SIP signalling.
Example: xconfiguration sip transport default: tcp

SIP TLS Verify: <On/Off>

For TLS connections a CA-list can be uploaded from the web interface.
Set to On to verify TLS connections. Only TLS connections to servers, whom x.509 certificate is validated against the CA-list, will be allowed.
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 tls verify: off

SIP ICE Mode: <On/Off>

The system support ICE (“Interactive Connectivity Establishment”) NAT traversal, and TURN (“Traversal Using Relays around NAT”) media relays.
When set to On, the system will choose between the available servers in the following order:
1. Local
2. STUN / public IP
3. TURN / Media redirection
Off : Set to Off to disable ICE.
Example: xconfiguration sip ice mode: off

D 13887.09
APRIL 2009 113
Configuration-type Commands – xconfiguration / configuration.xml
SIP cont... — SNMP TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

SIP MNS Mode: <On/Off>

The MNS (”Media Network Services”) mode operates similarly to the ICE mode, but the system will prioritize use of the TURN server:
1. Local
2. TURN / Media redirection
Media packets will be sent directly only to endpoints determined to be on the local LAN. Media packets to all other destinations will be sent through the
TURN server. The MNS mode is typically used to improve the network transport quality. There are commercial services available providing dedicated wide-
area video networks, see e.g. ”http://www.medianetworkservices.com”
On: Setting the MNS mode to On will enable and prioritize media redirection through the dedicated network identified by the TURN server.
Off : Normal operation mode (standard ICE)
Example: xconfiguration sip mns mode: off

SIP ForceTurn Mode: <On/Off>

In this mode media is always sent using the TURN relay. One usage for this mode is media relaying from installations on a public IP network.
On: Setting the Force TURN mode to On will force media redirection through the dedicated network identified by the TURN server.
Off : Normal operation mode (standard ICE or MNS).
Example: xconfiguration sip forceturn mode: off

SIP TURN Server: <S: 0, 60>

Address of the TURN server for data redirection. A fully qualified domain name or an IP address can be used. Default port 3478 is assumed. Optional
port can be provided using ”:nnnnn” notation. Examples: ”93.93.102.102:7000”, ”turn.mnsbone.net”.
Example: xconfiguration sip turn address:

SIP ReplyTo URI: <S: 0, 60>

If configured it is this URI that will be displayed in the call lists.
Example: xconfiguration sip replyto uri:

SNMP Mode: <On/Off/ReadOnly/TrapsOnly>

If set to On, both Read and sending of Traps will be enabled.
If set to Off, all SNMP functionality will be disabled.
ReadOnly: The system will not send SNMP traps, but it will be possible to read data from the SNMP MIB.
TrapsOnly: The system will send SNMP traps, but it will not be possible to read data from the SNMP MIB.
Example: xconfiguration snmp mode: readonly

SNMP CommunityName: <S: 0, 16>

Defines the SNMP community name.
Example: xconfiguration snmp communityname:

SNMP SystemContact: <S: 0, 70>

Defines the SNMP system contact.
Example: xconfiguration snmp systemcontact:

D 13887.09
APRIL 2009 114
Configuration-type Commands – xconfiguration / configuration.xml
SNMP cont... — SSH TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

SNMP SystemLocation: <S: 0, 70>

Defines the SNMP system location.
Example: xconfiguration snmp systemlocation:

SNMP HostIPAddr [1..3]: <IPAddr>

Defines SNMP host addresses.
Example: xconfiguration snmp hostipaddr:

StartupVideoSource: <0/1/2/3/4/5/6>
Defines the video source the system will use as default after a reboot, and after the system goes out from screen saver mode.
If set to 0, the system will use the video source that was selected before reboot.
Example: xconfiguration startupvideosource: 1

StillImageSource: <0/1/2/3/4/5/6>
Defines the default still image source. If set to 0, the system will use the current main video source as still image source.
Example: xconfiguration stillimagesource: 4

SSH Mode: <On/Off>

If set to Off, it will not be possible to connect to the system using SSH. The Command Line Interface can be accessed using SSH (Secure Shell), which allows for secure control
of the TANDBERG MXP.
Example: xconfiguration SSH Mode: On

D 13887.09
APRIL 2009 115
Configuration-type Commands – xconfiguration / configuration.xml
Streaming TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Streaming Port: <0..65534>

Specifies the port, which the codec shall stream to. If several codec’s are streaming to the same IP-address, different ports have to be used
in order for the client to know which stream to receive. If the first codec streams on port 2240 and the second codec on port 2250, the cli-
ent has to specify which port to listen to. Video is transmitted on the specified port; audio is transmitted on the port number 4 greater than
the specified video port, in this case 2244 and 2254.
Example: xconfiguration streaming port: 2240

Streaming Hops: <0..255>

Number of router hops you want the codec to stream to. The default value 1 will normally allow the streaming data to pass one router.
Example: xconfiguration streaming hops: 1

Streaming Address: <S: 0, 64>

The address, which you want the codec to stream to. This address could be a multicast address, broadcast address or a uni-cast address. You can stream in a MCU call
Example: xconfiguration streaming address: for systems with MS installed.
Streaming will count as 1 site.
However, you cannot stream
Streaming VideoRate: <16/32/64/128/192/256/320> when Dual Stream/H.239 is
Selects the video rate in kbps to stream out on the network. activated.
Example: xconfiguration streaming videorate: 128
Dual Stream = Tandberg
specific method of sending Dual
Streaming Announcements: <On/Off> Images.
Turn On or Off Streaming Announcement Protocol.
H.239 = ITU ratified way of
Example: xconfiguration streaming announcements: on sending Dual Images.
TANDBERG uses Dual Stream to
Streaming Source: <Local/Remote/Auto> cover both these two technolo-
Select streaming source as Local, Remote or Auto. If set to Auto the streaming will be voice switched. The site currently speaking will be gies.
streamed.
Example: xconfiguration streaming source: auto

Streaming Password: <S: 0, 16>

Streaming password. This password and the ip password will give access to the streaming page in he internal web browser. By using this
password the more sensitive ip password can be reserved to the administrator.
Example: xconfiguration streaming password: xxx

Streaming Quality: <Motion/Sharpness>

When set to Motion the video is optimized for smooth motion video.
When set to Sharpness the video is optimized for sharp video.
Example: xconfiguration streaming quality: motion

Streaming AllowRemoteStart: <On/Off>

If set to Off, streaming can only be started locally from the menu interface or from the dataport (RS-232). If set to On, streaming can also be
See comment on previous page
started from the Web interface, the XML interface and from Telnet.
Example: xconfiguration streaming allowremotestart: off

D 13887.09
APRIL 2009 116
Configuration-type Commands – xconfiguration / configuration.xml
StrictPassword — SystemUnit TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

StrictPassword: <On/Off>
When enabled, strict password now requires the following restrictions to be met for all newly configured passwords on the system:
• Password cannot be the same as any of the previous 10 passwords used.
• Password must be 15 characters or more.
• Password must have at least 2 lower case letters, 2 upper case letters, 2 numeric characters and 2 special characters (e.g. #, *, &, %, etc).
• Three (3) consecutive characters cannot be the same..
Example: xconfiguration strictpassword: on

Switch Source: <1..6>

Select a physical input on the TANDBERG Video Switch.
Example: xconfiguration switch source: 1

Switch Configuration Primary: <On/Off>

Default is on. If off, the codec will only do a basic setup of the primary chain and report what kind of cameras are connected. The codec will not set up
brightness, white balance, gamma etc. for each camera. Turn it off if an external control system handles all the configuration.
Example: xconfiguration switch configuration primary: on

Switch Configuration Secondary: <On/Off>

Default is on. If off, the codec will only do a basic setup of the secondary chain and report what kind of cameras are connected. The codec will not set up
brightness, white balance, gamma etc. for each camera. Turn it off if an external control system handles all the configuration.
Example: xconfiguration switch configuration secondary: on

Switch LogicalInput [1..5] Mode: <On/Off>

Logical inputs are used when accessing inputs from the menu, remote control and FECC. There are five input buttons on the top of the TRC4 remote
1 MainCam control, and these can be remapped to any switch input you wish. The same five buttons are visible in the Presentation/Main Video menu, and these will
2 AUX be remapped in the same manner. If the switch is connected with no special configuration, selecting “main cam” in the menu will give the current input
3 Doc Cam on the switch. Default value is Off.
4 VCR Will set the logical input on the TANDBERG Video Switch to the given mode.
5 PC Example: xconfiguration switch logicalinput 1 mode: On

Switch LogicalInput [1..5] Map: <1..6>

The Map [1..6] represents the switch inputs.
1 MainCam Remaps the five source buttons on top of the extended remote control to any switch input you wish. Will also remap inputs selected from the menu, and
2 AUX change FECC accordingly. If mode for a key is on, the table entry will be used to specify which input on the switch to activate.
3 Doc Cam Example: xconfiguration switch logicalinput 1 map: 1
4 VCR
5 PC

SystemUnit Name: <S: 0, 49>

Defines the name of the system unit.
Example: xconfiguration systemunit name: MySystem

D 13887.09
APRIL 2009 117
Configuration-type Commands – xconfiguration / configuration.xml
SystemUnit cont... — Time TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

SystemUnit InternationalName: <S: 0, 49>

Defines the international name of the system unit – ASCII characters only!
Example: xconfiguration systemunit internationalname: MySystem

SystemUnit DisplayName: <S: 0, 50>

The Display Name part of the SIP Address (URI)
Example: xconfiguration systemunit displayname: MyDisplayNmae

SystemUnit Password: <S: 0, 16>

Defines the system unit password.
Example: xconfiguration systemunit password: xxx

T1 Interface CableLength: <Range1/Range2/Range3/Range4/Range5>

Specifies the length of the cable connected to the T1 interface.
Range1: 0–133 ft (0–40 m)
Range2: 133–266 ft (40–81 m)
Range3: 266–399 ft (81–122 m)
Range4: 399–533 ft (122–162 m)
Range5: 533–655 ft (162–200 m)
Example: xconfiguration t1 interface cablelength: range4

Telnet Mode: <On/Off>

If set to Off, it will not be possible to connect to the system using Telnet.
Example: xconfiguration telnet mode: on

TelnetChallenge Mode: <On/Off> TelnetChallenge can be enabled on either ip port 23 or ip port 57.
Enables/disables TelnetChallenge. When connecting to an ip port that has telnetChallenge set to On, an MD5
Example: xconfiguration telnetchallenge mode: on encryption challenge string are being issued instead of a password prompt. An
encrypted password based on the challenge string must then be generated by
TelnetChallenge Port: <23/57> an MD5 encryptor and sent back to the system as a response in order to get
Specifies whether to port 23 or port 57 for TelnetChallenge. access to the system.
Example: xconfiguration telnetchallenge port: 57 NOTE! Regular Telnet are using ip port 23. When TelnetChallenge is set to ip port
23, this will override regular Telnet.

Time Zone: <GMT-1200/GMT-1100/GMT-1000/GMT-0930/GMT-0900/GMT-0800/GMT-0700/GMT-0600/GMT-0500/GMT-0400/GMT-0330/GMT-0300/GMT-0200/GMT-0100/GMT/

GMT+0100/GMT+0200/GMT+0300/GMT+0330/GMT+0400/GMT+0430/GMT+0500/GMT+0530/GMT+0545/GMT+0600/GMT+0630/GMT+0700/GMT+0800/GMT+0845/
GMT+0900/GMT+0930/GMT+1000/GMT+1030/GMT+1100/GMT+1130/GMT+1200/GMT+1245/GMT+1300/GMT+1400>
Specifies the time zone where the system is located.
Example: xconfiguration time zone: GMT+0100

D 13887.09
APRIL 2009 118
Configuration-type Commands – xconfiguration / configuration.xml
Time cont... ­— Video TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Time DateFormat: <DD_MM_YY/MM_DD_YY/YY_MM_DD>

Species the date format to use when presenting dates on the system.
Example: xconfiguration time dateformat: dd_mm_yy

Time TimeFormat: <24H/12H>

Specifies the time format to use.
Example: xconfiguration time timeformat: 24h

Time DaylightSavings: <On/Off>

Enables/Disables Daylight Savings.
Example: xconfiguration time daylightsavings: on

ThreePartyLayout: <On/Off>
3 party layout on the multisite host utilizes the dual monitor setting of the system to display the two far-end sites on individual monitors. This feature is supported when the MultiSite Picture mode is set
to Auto split or 4Split, and the Dual Monitor setting is enabled. When a dual stream is started during the conference, the screen will return to a standard 4-split in order to display the dual stream on the
second monitor. Upon termination of the dual stream, the layout will return to the 3 party layout. NOTE! 3 Party Mode will not function if the MultiSite Picture mode is set to 5+1Split or VoiceSwitched.
Example: xconfiguration threepartylayout: on

UseAsLocalPCMonitor: <On/Off>
If the main monitor is used as a local PC display, UseAsLocalPCMonitor should be set to On. This will avoid transmitting the local PC image while the system is in a video conference.
Example: xconfiguration useaslocalpcmonitor: on

Video Inputs Source [1..6] Name: <S: 0, 16>

Defines the name of the video source.
Example: xconfiguration video inputs source 5 name: MyPCInput

Video Inputs Source [1..6] ForceAnalog: <On/Off>

This setting corresponds to the Presentation > Force Mac Input setting in the menu (GUI).
On: If set to On, the system will only provide analog EDID information, and thus will only work with analog devices.
Off : If set to Off, the system will provide both analog and digital EDID information.
Example: xconfiguration video inputs source 5 forceanalog: off

Video Inputs Source 5 HorizAdjust: <0..255> NOTE! Only Video Input Source 5
Gives you the possibility to adjust the placement of the PC image on screen. Much like the setting you find on a regular PC
screen.
Example: xconfiguration video inputs source 5 horizadjust: 0

D 13887.09
APRIL 2009 119
Configuration-type Commands – xconfiguration / configuration.xml
Video cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Video Inputs Source [1..6] Quality: <Motion/Sharpness>

When encoding and transmitting video there will be a trade-off between high resolution and high frame rate. For some video
sources it is more important to transmit high frame rate 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.
Motion: 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.
At low bit rate the following resolution will be transmitted:
• CIF will be used from a PAL video input
• SIF from NTSC
• w288p from wide format (HD720p) input
• VGA/SVGA/XGA from PC, Digital Clarity
At high bit rate the following resolution will be transmitted:
• 448p will be used from a PAL video input if Natural Video is ‘Off’ or ‘Auto’ or if Natural Video is ‘x kbps’ and the bit rate is
lower than x kbps
• 400p from NTSC if Natural Video is ‘Off’ or ‘Auto’ or if Natural Video is ‘x kbps’ and the bit rate is lower than x kbps
• iCIF will be used from a PAL video input, if Natural Video is ‘x kbps’ and the bit rate is higher than or equal to x kbps
• iSIF from NTSC, if Natural Video is ‘x kbps’ and the bit rate is higher than or equal to x kbps
• w448p will be used from a wide format (HD720p) input
• VGA/SVGA/XGA from PC, Digital Clarity
Sharpness: Improved quality of detailed images and graphics:
• 4xCIF will be used from a PAL video input, Digital Clarity
• 4xSIF will be used from a NTSC video input, Digital Clarity
• w720p will be used from a wide format (HD720p) input
• VGA/SVGA/XGA will be used from a PC input, Digital Clarity
Example: xconfiguration video inputs source 5 quality: sharpness

Video Outputs Animation: <On/Off>

The new PiP/PoP animation makes the windows fade or slide into position when changing the picture layout. PiP means Picture in Picture layout and PoP
means Picture outside Picture layout.
Example: xconfiguration video outputs animation: on

Video Outputs ScreenFormatTV: <4:3/16:9>

Specifies whether the monitors connected to the TV (S-video/Composite) outputs are 4:3 or 16:9 monitors. If this configuration is not set according to
the monitors in use, the images will either be over-stretch or compressed.
Example: xconfiguration video outputs screenformattv: 4:3

Video Outputs ScreenFormatPC: <4:3/16:9>

Specifies whether the monitors connected to the PC (DVI) outputs are 4:3 or 16:9 monitors. If this configuration is not set according to the monitors in
use, the images will either be stretched or compressed. See FormatPCWideScreen for more on this.
Example: xconfiguration video outputs screenformatpc: 16:9

D 13887.09
APRIL 2009 120
Configuration-type Commands – xconfiguration / configuration.xml
Video cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Video Outputs DVIResolution [1..x]: <Auto/SVGA/XGA/w720p/WXGA> Supported formats:

x = 2 on 6000 MXP • SVGA (800x600) 75Hz
x = 1 on 3000 MXP • XGA (1024x768) 60Hz / 75Hz
Defines resolution for the supported DVI outputs. • WXGA (1280x768) 60Hz
Auto: VGA output format will be optimized depending on the video
source format, refresh rate and of the EDID information available. • SVGA: VGA output format is forced to SVGA format (800x600) 75Hz
Example:
• XGA: VGA output format is forced to XGA format (1024x768) 60Hz
xconfiguration video outputs dviresolution 1: auto • VGA Out Quality for Wide XGA: If ScreenFormatPC is set to Wide, Format-
PCWideScreen is set to Normal, VGA Out Quality is set to Auto, the layout
on the monitor is either fullscreen or POP, and the input source to the larg-
est window is PC with resolution 1024x768, the system will use WideXGA
(1280x768) instead of XGA, when the monitor supports this.

Video Outputs Letterbox: <On/Off>

This setting will only take effect on video displayed in full screen. When set to On, the system will use horizontal black bars to compensate for aspect
ratio mismatch between a wide output and a narrow input. When set to Off, the system will crop vertically to compensate.
Example: xconfiguration video outputs letterbox: on

Video Outputs TestPattern: <0..10>

The system has a selection of test patterns on the displays. TestPattern = 0 is normal operation without any pattern. TestPattern = <1..10> will turn on
the given pattern.
Example: xconfiguration video outputs testpattern: 0

Video Outputs TV [1..2] VirtualMonitor: <1..4>

The system supports 4 Virtual Monitors. To see pictures displayed on Virtual Monitors on physical monitors connected to video
outputs, the different video outputs must make connections to the Virtual Monitors.
Virtual Monitor 1 displays by default the Main Monitor picture, while Virtual Monitor 2 displays by default the Second Monitor
picture (Virtual Monitor 3 and 4 are not in use by default).
TV output 1 shows by default Virtual Monitor 1 (Main Monitor), while TV output 2 shows by default Virtual Monitor 2 (Second
Monitor). To make TV output 2 also show Virtual Monitor 1:
Example: xconfiguration video outputs tv 1 virtualmonitor: 1

Video Outputs TV [1..2] OSD: <On/Off>

Specifies whether or not to display On Screen Display on the supported TV outputs.
Example: xconfiguration video outputs tv 1 osd: on

Video Outputs TV [1..2] Mode: <On/Off>

Turns On/Off the TV (Composite/S-Video) outputs. On 6000MXP, the TV 1 and TV 2 Mode are default set to to Off.
NOTE! We recommend that you turn off video on all unused video outputs.
Example: xconfiguration video outputs tv 1 mode: on

D 13887.09
APRIL 2009 121
Configuration-type Commands – xconfiguration / configuration.xml
Video cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Video Outputs TV [1..2] AspectChoice: <Auto/Clip/Letterbox/Fill>

You can adjust the aspect ratio for the TV and DVI-I outputs to customize the aspect ratio of the monitor to the preferred configu-
ration.
Auto: The endpoint determines the best aspect ratio to display by combining Clip, Fill, and Letter Box.
Clip: Adjusts the source by clipping, to match the aspect ratio of the display window.
Letterbox: Adjusts the source by adding black bars, to match the aspect ratio of the display window.
Fill: Stretch or shrink the source to fill the display window. The aspect ratio of the source does not match the display.
Example: xconfiguration video outputs tv 1 aspectchoice: auto

Video Outputs DVI [1..x] VirtualMonitor: <1..4>

x = 2 on 6000 MXP Defines the connections between the DVI outputs and the Virtual Monitors (see above).
x = 1 on 3000 MXP 6000 MXP: DVI output 1 shows by default Virtual Monitor 1 (Main Monitor), while DVI output 2 shows by default Virtual Monitor 2
(Second Monitor).
3000 MXP: DVI output 1 shows by default Virtual Monitor 2 (Second Monitor).
To have DVI output 2 to also show Virtual Monitor 1:
Example: xconfiguration video outputs dvi 1 virtualmonitor: 1

Video Outputs DVI [1..x] OSD: <On/Off>

x = 2 on 6000 MXP Specifies whether or not to display On Screen Display on the supported TV outputs.
x = 1 on 3000 MXP Example: xconfiguration video outputs dvi 1 osd: on

Video Outputs DVI [1..x] Mode: <On/Off>

x = 2 on 6000 MXP Turns On/Off the DVI outputs.
x = 1 on 3000 MXP
NOTE! We recommend that you turn off video all unused video outputs.
Example: xconfiguration video outputs dvi 1 mode: On

Video Outputs DVI [1..x] AspectChoice: <Auto/Clip/Letterbox/Fill>

x = 2 on 6000 MXP You can adjust the aspect ratio for the TV and DVI-I outputs to customize the aspect ratio of the monitor to the preferred configu-
x = 1 on 3000 MXP ration.
Auto: The endpoint determines the best aspect ratio to display by combining Clip, Fill, and Letter Box.
Clip: Adjusts the source by clipping, to match the aspect ratio of the display window.
Letterbox: Adjusts the source by adding black bars, to match the aspect ratio of the display window.
Fill: Stretch or shrink the source to fill the display window. The aspect ratio of the source does not match the display.
Example: xconfiguration video outputs dvi 1 aspectchoice: auto

D 13887.09
APRIL 2009 122
Configuration-type Commands – xconfiguration / configuration.xml
VNC cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

VNC IPAddress: <S: 0, 64>

Defines the IP address of the VNC server.
Example: xconfiguration vnc ipaddress: 10.47.15.49

VNC DisplayNumber: <S: 0, 5>

The display number of the VNC service must match the display number of the VNC server.
Example: xconfiguration vnc displaynumber: 2

VNC Password: <S: 0, 8>

Defines the password to use when connecting to the VNC service.
Example: xconfiguration vnc password: xxx

D 13887.09
APRIL 2009 123
Configuration-type Commands – xdirectory / directory.xml
LocalEntry — GroupEntry TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

LocalEntry [1..200] Name: <S: 0, 48>

The local entry’s name.
Example: xdirectory localentry 26 name: john doe

LocalEntry [1..200] Number: <S: 0, 60>

The local entry’s number.
Example: xdirectory localentry 26 number: 5566

LocalEntry [1..200] SecondNumber: <S: 0, 60>

2Xh221 second number.
Example: xdirectory localentry 26 secondnumber: 5566

LocalEntry [1..200] SubAddress: <S: 0, 20> Defines entries stored on the

codec.
Example: xdirectory localentry 26 subaddress: 5436
NOTE! To add new entries and
remove existing entries, the
LocalEntry [1..200] CallRate: <Tlph/1xh221/2xh221/64/128/192/256/320/384/512/768/1152/1472/1920/2560/3072/4096/Max/Auto> commands LocalEntryAdd / Lo-
Specifies the callrate to use when calling this entry. calEntryDelete should be used.
Example: xdirectory localentry 26 callrate: 64

LocalEntry [1..200] Restrict: <On/Off>

Specifies wether or not to use Restrict when calling this entry.
A restricted call uses 56kbps channels rather than the default unrestricted 64kbps channels. Some older networks (primarily in the USA)
do not support 64kbps channels and require the use of restricted 56kbps calls. By default the system will dial an unrestricted call and
downspeed to 56kbps if necessary.
Example: xdirectory localentry 26 restrict: on

LocalEntry [1..200] NetProfile: <1..7>

Defines the NetProfile to use when calling this entry. A NetProfile defines network type and a possible prefix, ref. configuration Netprofile.
Example: xdirectory localentry 26 netprofile: 5

GroupEntry [1..50] Name: <S: 0, 48> Defines group entries (MultiSite

The Group entry’s name. entries) stored on the codec.
Example: xdirectory groupentry 22 number: 5566 NOTE! To add new entries and
remove existing entries, the
commands GroupEntryAdd /
GroupEntry [1..50] LocalEntryId [1..10]: <0..200>
GroupEntryDelete should be
References to the local entries to be included in the group entry.
used.
Example: directory groupentry 45 localentryid 7 number: 167

D 13887.09
APRIL 2009 124
Configuration-type Commands – xdirectory / directory.xml
GlobalEntry TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

GlobalEntry [1..400] Name: <S: 0, 48>

The global entry’s name.
Example: xdirectory globalentry 26 name: john doe

GlobalEntry [1..400] Number: <S: 0, 60>

The global entry’s number.
Example: xdirectory globalentry 26 number: 5566

GlobalEntry [1..400] SecondNumber: <S: 0, 60>

2Xh221 second number.
Example: xdirectory globalentry 26 secondnumber: 4563

GlobalEntry [1..400] SubAddress: <S: 0, 20> Defines global entries to be

Example: xdirectory globalentry 26 subaddress: 2233 stored on the codec. Global
entries should be used by an
centralized directory server
GlobalEntry [1..400] CallRate: <Tlph/1xh221/2xh221/64/128/192/256/320/384/512/768/1152/1472/1920/2560/3072/4096/Max/Auto> to update the systems phone
Specifies the callrate to use when calling this entry. book.
Example: xdirectory globalentry 26 callrate: 1xh221

GlobalEntry [1..400] Restrict: <On/Off>

Specifies wether or not to use Restrict when calling this entry. A restricted call uses 56kbps channels rather than the default unrestricted
64kbps channels. Some older networks (primarily in the USA) do not support 64kbps channels and require the use of restricted 56kbps
calls. By default the system will dial an unrestricted call and down speed to 56kbps if necessary.
Example: xdirectory globalentry 26 restrict: off

GlobalEntry [1..400] NetProfile: <1..7>

Defines the NetProfile to use when calling this entry.
A NetProfile defines network type and a possible prefix, ref. configuration Netprofile.
Example: xdirectory globalentry 26 netprofile: 3

D 13887.09
APRIL 2009 125
 Configuration Storage Levels
We recommend that you check out the You may reset configuration settings to their default
TANDBERG web site regularly for updated
versions of this manual: values. Whether a specific configuration command will be
http://www.tandberg.com/docs affected by the reset command depends on two things;
which class(es) of configuration commands you want to
reset and which class the specific configuration command
belongs to.
Configuration Storage Levels
Understanding the Table Layout TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Configuration Commands
shown on this page.

Configuration Storage Levels

NetProfile 7 Network — PictureProgram [1..4] Window [1..6] Picture TANDBERG 3000 MXP & 6000 MXP
REFERENCE USER GUIDE FOR SYSTEM INTEGRATORS

Storage Level: Configuration:

3 NetProfile 7 Network: <SIP>

By use of the command 3 NTP Address: <S: 0, 64>
DefaultValuesSet you may 3 NTP Mode: <Manual/Auto>
reset configurations to their 3 OptionKey Bandwidth: <S: 0, 16>
default settings. To be able 3 OptionKey Features: <S: 0, 16>
to discriminate between
1 OSD Icon BadNetwork: <On/Off>
the different Configuration
1 OSD Icon Encryption: <On/Off>
commands (without having
1 OSD Icon MicOff: <On/Off>
to specify each one of them),
the Configuration commands 1 OSD Icon OnAir: <On/Off>

have been grouped into 1 OSD Icon Telephone: <On/Off>

3 different storage levels, 1 OSD Icon VolumeOff: <On/Off>

denoted 1, 2 and 3. 2 OSD MCUStatusLine Mode: <On/Off/Auto>

The command DefaultValues- 1 OSD Menu BallonHelp: <On/Off>

Set is thus followed by a 2 OSD Menu DisableTimeout: <On/Off>

level parameter (1, 2, or 3). 2 OSD Menu DisplayWelcomeText: <On/Off>

3 OSD Menu InputEditor Language: <Off/Chinese/Korean>

If you specify the use of
level parameter 1, only level 3 OSD Menu Language: <English/German/Norwegian/French/Swedish/Italian/Portuguese/Japanese/ Chinese/TraditionalChinese/Russian/Spanish/Korean/Finnish/Thai/Arabic>

1 Configuration commands 3 OSD Menu Mode: <On/Off>

will be reset. 3 OSD Menu Password: <S: 0, 5>

3 OSD Menu WelcomeMenu: <On/Off>

If you specify the use of
level parameter 2, level 1 2 OSD Menu WelcomeText: <S: 0, 30>

and level 2 Configuration 3 OSD Mode: <On/Off>

commands will be reset. 3 PacketlossDownSpeed Mode: <Auto/Off>

If you specify the use of 1 PictureProgram [1..4] Layout: <Full/2Split/4Split/2+1Split/3+1Split/5+1Split>

level parameter 3, all Con- 1 PictureProgram [1..4] Window [1..6] Call: <1..11>

figuration commands will be 1 PictureProgram [1..4] Window [1..6] Picture: <LocalMain/LocalDuo/Current/Previous/Duo/RemoteMain/RemoteDuo/JPEG/ TandbergMonitor1/TandbergMonitor2/None>

reset (1, 2, and 3).

D 13887.X3
AUGUST 2006 85
Tip! An exhaustive
description of the API Configuration Command
structure can be found
in the section
Corresponding Storage Level
The TANDBERG API

D 13887.09
APRIL 2009 127
Configuration Storage Levels
AdditionalCamera — Audio MicrophoneMixer Mode TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Storage Level: Configuration:

3 AdditionalCamera Type: <0..4>

1 AlertSpeaker Mode: <On/Off>

1 AlertTone Telephony: <1..10>

1 AlertTone VideoTelephony: <1..10>

1 AlertTone Volume: <0..15>

1 AllowLatency: <On/Off>

1 Audio AGC AUX: <On/Off>

1 Audio AGC Microphones: <On/Off>

1 Audio AGC Received: <On/Off>

1 Audio AGC VCR: <On/Off>

1 Audio AudioModule: <NAMII-6000/NAMII-7000/NAMII-8000/Digital NAM/None>

1 Audio AutoMute: <On/Off/Unmute>

1 Audio EchoControl [1..4]: <On/Off/NoiseReduction>

1 Audio Feedback Mode: <Normal/Fast>

1 Audio Inputs Line [1..3] Level: <1..16>

1 Audio Inputs Line 1 Mode: <On/Off/Microphone> (3000 MXP)

1 Audio Inputs Line 2 Mode: <On/Off/Auto> (3000 MXP)

1 Audio Inputs Line [1..2] Mode: <On/Off> (6000 MXP)

1 Audio Inputs Line 3 Mode: <On/Off/Auto> (6000 MXP)

1 Audio Inputs Microphone [1..3] Level: <1..16>

1 Audio Inputs Microphone 1 Mode: <On/Off>

1 Audio Inputs Microphone 2 Mode: <On/Off>

1 Audio Inputs Microphone 3 Mode: <On/Off/Line>

1 Audio KeyTones: <On/Off>

1 Audio LocalDetection Mode: <On/Off>

1 Audio MicrophoneMixer Mode: <Fixed/Auto>

D 13887.09
APRIL 2009 128
Configuration Storage Levels
Audio Microphones Mode — Camera [1..13] WhiteBalance Level TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Storage Level: Configuration:

1 Audio Microphones Mode: <On/Off>

1 Audio Outputs Line [1..3] Level: <1..16>

1 Audio Outputs Line [1..3] Mode: <On/Off>

1 Audio Outputs Line 1 Type: <Analog/SPDIF/Auto>

1 Audio Stereo: <On/Off>

1 Audio StereoSpeakers: <On/Off>

1 Audio VCRDucking: <On/Off>

1 Audio Volume: <0..21>

1 AutoAnswer Delay: <1..50>

1 AutoAnswer Mode: <On/Off/Mute>

1 AutoDisplaySnapshot: <On/Off>

1 AutoLayout Mode: <On/Off>

1 AutoPIP Mode: <On/Off/Auto>

3 Bonding Timer: <Normal/Relaxed>

3 CallManager Address: <S: 0, 64>

1 Camera [1..13] Backlight: <On/Off>

1 Camera [1..13] Brightness Level: <0..16>

1 Camera [1..13] Brightness Mode: <Manual/Auto>

1 Camera [1..13] DualVisca <Off/On>

1 Camera [1..13] Focus Mode: <Manual/Auto>

1 Camera [1..13] Gamma Level <0..7>

1 Camera [1..13] Gamma Mode <Auto/Manual>

1 Camera [1..13] IR <Off/On>

1 Camera [1..13] Mirror <Off/On>

1 Camera [1..13] Whitebalance Level: <0..16>

D 13887.09
APRIL 2009 129
Configuration Storage Levels
Camera [1..13] WhiteBalance Mode — Conference H263 TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Storage Level: Configuration:

1 Camera [1..13] Whitebalance Mode: <Manual/Auto>

1 CameraDVI Mode: <On/Off/Auto>

1 CameraSleep Mode: <On/Off>

1 CameraSwUpgrade: <Auto/Off>

1 CameraTracking Speed: <Slow/Normal/Fast>

2 Conference AAC-LD: <On/Off>

2 Conference AAC-LD-128-Mono: <On/Off>

2 Conference AAC-LD-128-Threshold: <384/512/768/1152/1472/1920/2560/3072/4096>

3 Conference AIM: <On/Off>

1 Conference AllowIncomingMSCall: <On/Off>

1 Conference AllowIncomingTlphCall: <On/Off>

1 Conference BillingCode: <On/Off>

1 Conference DefaultCall CallRate: <Tlph/1xh221/2xh221/64/128/192/256/320/384/H0/512/768/1152/1472/1920/2560/3072/4096/Max/Auto>

1 Conference DefaultCall NetProfile: <1..7>

1 Conference DefaultCall Restrict: <On/Off>

2 Conference Downspeed: <On/Off>

3 Conference Encryption Mode: <On/Off/Auto>

3 Conference Encryption Type: <Auto/DES/AES-128>

2 Conference FallbackToTelephony: <On/Off>

1 Conference FarTlphEchoSupression: <Off/Normal/High>

1 Conference FloorToFull: <On/Off>

2 Conference G722.1: <On/Off>

2 Conference G722: <On/Off>

2 Conference G728: <On/Off>

2 Conference H239: <On/Off>

2 Conference H263: <On/Off>

D 13887.09
APRIL 2009 130
Configuration Storage Levels
Conference H264 — ExternalNetwork Clocking TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Storage Level: Configuration:

2 Conference H264: <On/Off>

2 Conference H264RCDO: <On/Off>

3 Conference H323Alias E164: <E164: 0, 30>

3 Conference H323Alias ID: <S: 0, 49>

1 Conference H331: <On/Off>

2 Conference IPDualstreamRate <25percent/50percent/75percent>

1 Conference IPLR Transmit: <On/Off>

1 Conference MaxCallLength: <0..999>

2 Conference NaturalVideo: <Off/Auto/384/512/768/1152/1472/1920>

1 Conference PictureMode: <4Split/5+1Split/VS/Auto>

3 Conference SIP URI: <S: 0, 60>

2 Conference VideoQualityCP: <Motion/Sharpness/Auto>

1 Conference WebSnapshots: <On/Off>

3 CorporateDirectory Address: <S: 0, 64>

3 CorporateDirectory Mode: <On/Off>

3 CorporateDirectory Path: <S: 0, 255>

1 DefaultPIPPosition: <BottomLeft/BottomRight/TopLeft/TopRight>

1 DoNotDisturb Mode: <On/Off>

3 DualMonitor Mode: <On/Off>

1 DuoVideoSource: <0/1/2/3/4/5/6>

3 E1 Interface CRC4: <On/Off>

3 Ethernet [1..2] Speed: <Auto/10half/10full/100half/100full>

3 ExternalManager Address: <S: 0, 64>

3 ExternalManager Path: <S: 0, 255>

3 ExternalNetwork Callcontrol: <RS366/RS366AdtranIMUX/ RS366CustomIMUX/LeasedLine/DataTriggered/Manual>

3 ExternalNetwork Clocking: <Dual/Single>

D 13887.09
APRIL 2009 131
Configuration Storage Levels
ExternalNetwork DTRPulse — H323Prefix TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Storage Level: Configuration:

3 ExternalNetwork DTRPulse: <On/Off>

3 ExternalServices Address: <S: 0, 64>

3 ExternalServices Mode: <On/Off>

3 ExternalServices Path: <S: 0, 255>

1 FECC Mode: <On/Off>

1 FeedbackFilter Call: <0..10>

1 FeedbackFilter Conference: <0..10>

1 FTP Mode: <On/Off>

3 G703 Callcontrol: <Manual/Auto>

3 G703 Interface MaxChannels: <1..30>

3 G703 Interface StartChannel: <1..31>

3 G703 Linecoding: <b8zsRestrict/b8zsNoRestrict>

3 G703 PhysicalLayer: <E1/T1>

3 H320 NetType: <BRI/PRI/External/G703/None>

3 H323 Mode: <On/Off>

3 H323CallSetup Mode: <Direct/Gatekeeper/CallManager>

3 H323Gatekeeper Address: <S: 0, 64>

3 H323Gatekeeper Authentication ID: <S: 0, 49>

3 H323Gatekeeper Authentication Mode: <Auto/Off>

3 H323Gatekeeper Authentication Password: <S: 0, 49>

3 H323Gatekeeper Avaya AnnexH: <On/Off>

3 H323Gatekeeper Avaya Mode: <On/Off>

3 H323Gatekeeper Avaya MultipointCount: <0..9>

3 H323Gatekeeper Discovery: <Manual/Auto>

3 H323Gatekeeper MultipleAlias: <On/Off>

3 H323Prefix: <S: 0, 4>

D 13887.09
APRIL 2009 132
Configuration Storage Levels
HTTP Mode — IPProtocol TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Storage Level: Configuration:

1 HTTP Mode: <On/Off>

1 HTTPS Mode: <On/Off>

1 IdReport H323: <H323Id/E164Alias/IPAddress>

3 IEEE802.1x AnonymousIdentity: <S: 0, 64>

3 IEEE802.1x EAP-MD5: <On/Off>

3 IEEE802.1x EAP-PEAP: <On/Off>

3 IEEE802.1x EAP-TTLS: <On/Off>

3 IEEE802.1x Identity: <S: 0, 64>

3 IEEE802.1x Mode: <On/Off>

3 IEEE802.1x Password: <S: 0, 64>

3 Integrator AMXBeacon Mode: <On/Off>

3 Integrator Telepresence Mode: <Off/Point2Point/MultiPoint/Briefer>

3 IMUX Custom [BW64/BW128/BW192/BW256/BW320/BW384/BW512/BW768/BW1152/BW1472/BW1920] Prefix <S: 0, 12>

3 IMUX Custom [BW64/BW128/BW192/BW256/BW320/BW384/BW512/BW768/BW1152/BW1472/BW1920] Suffix <S: 0, 12>

3 IMUX Custom [BW64R/BW128R/BW192R/BW256R/BW320R/BW384R/BW512R/BW768R/BW1152R/BW1472R/BW1920R] Prefix <S: 0, 12>

3 IMUX Custom [BW64R/BW128R/BW192R/BW256R/BW320R/BW384R/BW512R/BW768R/BW1152R/BW1472R/BW1920R] Suffix <S: 0, 12>

3 IP Address: <IPAddr>

3 IP Assignment: <DHCP/Static>

3 IP DNS Domain Name: <S: 0, 64>

3 IP DNS Server [1..5] Address: <IPv4v6Addr: 0, 43>

2 IPDualstreamRate: <25Percent/50Percent/75Percent>

3 IP Gateway: <IPAddr>

3 IP SubnetMask: <IPAddr>

3 IP V6 Address: <IPv6Addr: 0, 43>

1 IPMedia MaxVideoTXRate: <64..4096>

3 IPProtocol: <IPv4/IPv6/Both>

D 13887.09
APRIL 2009 133
Configuration Storage Levels
IRControl NumberKeyMode — ISDN PRI Interface Search TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Storage Level: Configuration:

1 IRControl NumberKeyMode: <AddCall/DTMF/Presets/Manual>

1 IRControl Mode: <On/Off>

3 ISDN BRI Alert: <On/Off>

3 ISDN BRI AutoActivation: <Off/Selected/All>

3 ISDN BRI ChanId: <On/Off>

3 ISDN BRI Interface [1..6] DirectoryNumber [1..2]: <S: 0, 24>

3 ISDN BRI Interface [1..6] Mode: <On/Off>

3 ISDN BRI Interface [1..6] SPID [1..2]: <S: 0, 20>

1 ISDN BRI InterfaceSearch: <High/Low>

3 ISDN BRI MaxDeactiveTime: <1..60>

3 ISDN BRI SwitchType: <NI/ATT/Euro/1TR6/Japan/Australia/FETEX>

1 ISDN CliNumbPlan: <0..14>

1 ISDN CliNumbSpec: <On/Off>

1 ISDN CliNumbType: <0..6>

3 ISDN HLC: <On/Off>

3 ISDN MSN: <On/Off>

3 ISDN ParallelDial: <On/Off>

3 ISDN PRI Alert: <On/Off>

3 ISDN PRI ChanId: <On/Off>

3 ISDN PRI InitialRestart: <On/Off>

3 ISDN PRI Interface HighChannel: <1..31>

3 ISDN PRI Interface LowChannel: <1..31>

3 ISDN PRI Interface MaxChannels: <1..30>

3 ISDN PRI Interface NumberRangeStart: <S: 0, 24>

3 ISDN PRI Interface NumberRangeStop: <S: 0, 24>

3 ISDN PRI Interface Search: <High/Low>

D 13887.09
APRIL 2009 134
Configuration Storage Levels
ISDN PRI L2WindowSize — LocalLayout Toggle TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Storage Level: Configuration:

3 ISDN PRI L2WindowSize: <1..7>

3 ISDN PRI NSFTelephony Mode: <On/Off>

3 ISDN PRI NSFTelephony Number: <0..31>

3 ISDN PRI NSFVideoTelephony Mode: <On/Off>

3 ISDN PRI NSFVideoTelephony Number: <0..31>

3 ISDN PRI SwitchType: <NI/ATT/Euro/Japan>

3 ISDN SendComplete: <On/Off>

3 ISDN SendNumber: <On/Off>

3 ISDN SpeechTimers: <On/Off>

3 ISDN SubAddress: <S: 0, 20>

1 Keyboard Layout: <English/US/Norwegian/Swedish/German/French/User>

1 Kiosk AllowIRControl: <On/Off>

1 Kiosk AutoDial: <On/Off>

1 Kiosk LanguageMenu English: <On/Off>

1 Kiosk LanguageMenu French: <On/Off>

1 Kiosk LanguageMenu German: <On/Off>

1 Kiosk LanguageMenu Italian: <On/Off>

1 Kiosk LanguageMenu Mode: <On/Off>

1 Kiosk LanguageMenu Norwegian: <On/Off>

1 Kiosk LanguageMenu Spanish: <On/Off>

1 Kiosk LanguageMenu Swedish: <On/Off>

1 Kiosk Menu: <On/Off>

1 Kiosk Mode: <On/Off>

1 Kiosk Phonebook: <Local/CorporateDirectory>

1 LocalLayout Mode: <Full/2Split/POP/POPwide>

1 LocalLayout Toggle: <PIP/POP>

D 13887.09
APRIL 2009 135
Configuration Storage Levels
Logo — OptionKey Features TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Storage Level: Configuration:

1 Logo: <On/Off>

1 LoS Duration Exponent: <10..30>

1 LoS Duration Offset: <0..65534>

1 LoS Inhibit: <0..65534>

1 LoS Initial: <0..65534>

1 LoS Polarity: <Positive/Negative>

1 LoS Retry: <0..65534>

1 MainVideoSource: <1/2/3/4/5/6>

3 MCU MultiSite <On/Off>

3 MCU MultiWay <On/Off>

3 NAT Address: <IPAddr>

3 NAT Mode: <On/Off/Auto>

3 NetProfile [1..7] CallPrefix: <S: 0, 9>

3 NetProfile [1..7] CallSuffix: <S: 0, 30>

3 NetProfile [1..7] Name: <S: 0, 8>

3 NetProfile 1 Network: <Auto>

3 NetProfile 2 Network: <H320>

3 NetProfile 3 Network: <H323>

3 NetProfile 4 Network: <H320/H323/SIP/Auto>

3 NetProfile 5 Network: <H320/H323/SIP/Auto>

3 NetProfile 6 Network: <H320/H323/SIP/Auto>

3 NetProfile 7 Network: <SIP>

3 NTP Address: <S: 0, 64>

3 NTP Mode: <Manual/Auto>

3 OptionKey Bandwidth: <S: 0, 16>

3 OptionKey Features: <S: 0, 16>

D 13887.09
APRIL 2009 136
Configuration Storage Levels
OSD Icon BadNetwork — Preset [1..15] Camera Autofocus TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Storage Level: Configuration:

1 OSD Icon BadNetwork: <On/Off>

1 OSD Icon Encryption: <On/Off>

1 OSD Icon MicOff: <On/Off>

1 OSD Icon OnAir: <On/Off>

1 OSD Icon Telephone: <On/Off>

1 OSD Icon VolumeOff: <On/Off>

2 OSD MCUStatusLine Mode: <On/Off/Auto>

1 OSD Menu BallonHelp: <On/Off>

2 OSD Menu DisableTimeout: <On/Off>

2 OSD Menu DisplayWelcomeText: <On/Off>

3 OSD Menu InputEditor Language: <Off/Chinese/Korean/Japanese>

3 OSD Menu Language: <English/German/Norwegian/French/Swedish/Italian/Portuguese/Japanese/ Chinese/TraditionalChinese/Russian/Spanish/Korean/Finnish/Thai/Arabic>

3 OSD Menu Mode: <On/Off>

3 OSD Menu Password: <S: 0, 5>

3 OSD Menu WelcomeMenu: <On/Off>

2 OSD Menu WelcomeText: <S: 0, 30>

3 OSD Mode: <On/Off>

1 OSD Offset Mode: <On/Off>

3 PacketlossDownSpeed Mode: <Auto/Off>

1 PictureProgram [1..4] Layout: <Full/2Split/4Split/2+1Split/3+1Split/5+1Split>

1 PictureProgram [1..4] Window [1..6] Call: <1..11>

1 PictureProgram [1..4] Window [1..6] Picture: <LocalMain/LocalDuo/Current/Previous/Duo/RemoteMain/RemoteDuo/JPEG/ TandbergMonitor1/TandbergMonitor2/None>

1 PresentationStart: <Manual/Auto>

1 Preset [1..15] Audio Inputs Line [1..3] Mode: <On/Off>

1 Preset [1..15] Audio Inputs Microphone [1..3] Mode: <On/Off>

1 Preset [1..15] Camera Autofocus: <On/Off>

D 13887.09
APRIL 2009 137
Configuration Storage Levels
Preset [1..15] Camera Brightness — RemoteSwUpgrade Password TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Storage Level: Configuration:

1 Preset [1..15] Camera Brightness Level: <0..16>

1 Preset [1..15] Camera Brightness Mode: <Manual/Auto>

1 Preset [1..15] Camera Focus: <0..65534>

1 Preset [1..15] Camera Pan: <-32768..32767>

1 Preset [1..15] Camera Tilt: <-32768..32767>

1 Preset [1..15] Camera Zoom: <0..65534>

1 Preset [1..15] DuoVideoSource: <0/1/2/3/4/5/6>

1 Preset [1..15] MainVideoSource: <1/2/3/4/5/6>

1 Preset [1..15] Name: <S: 0, 20>

3 QoS Diffserv Telephony Audio: <0..63>

3 QoS Diffserv Telephony Signalling: <0..63>

3 QoS Diffserv VideoTelephony Audio: <0..63>

3 QoS Diffserv VideoTelephony Data: <0..63>

3 QoS Diffserv VideoTelephony Signalling: <0..63>

3 QoS Diffserv VideoTelephony Video: <0..63>

3 QoS Mode: <Precedence/Diffserv/Off>

3 QoS Precedence Telephony Audio: <0/1/2/3/4/5/6/7/Auto/Off>

3 QoS Precedence Telephony Signalling: <0/1/2/3/4/5/6/7/Auto/Off>

3 QoS Precedence VideoTelephony Audio: <0/1/2/3/4/5/6/7/Auto/Off>

3 QoS Precedence VideoTelephony Data: <0/1/2/3/4/5/6/7/Auto/Off>

3 QoS Precedence VideoTelephony Signalling: <0/1/2/3/4/5/6/7/Auto/Off>

3 QoS Precedence VideoTelephony Video: <0/1/2/3/4/5/6/7/Auto/Off>

3 QoS RSVP: <Auto/Off>

3 QoS ToS: <MinDelay/MaxThrough/MaxReliable/MinCost/Off>

1 RemoteSwUpgrade Mode: <On/Off>

1 RemoteSwUpgrade Password: <S: 0, 16>

D 13887.09
APRIL 2009 138
Configuration Storage Levels
RTP MTU — SSH Mode TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Storage Level: Configuration:

1 RTP MTU: <400..1400>

1 RTP Ports: <Static/Dynamic>

1 Screensaver Delay: <1..480>

1 Screensaver Mode: <On/Off>

1 SelfViewOnStartup: <On/Off>

3 SerialPort [1..2] BaudRate: <1200/2400/4800/9600/19200/38400/57600/115200>

3 SerialPort [1..2] DataBits: <7/8>

3 SerialPort [1..2] Parity: <None/Odd/Even>

3 SerialPort [1..2] StopBits: <1/2>

3 SerialPort 1 Mode: <Control/Transparent>

3 SerialPort 2 Mode: <VISCA/Auto>

3 SIP Authentication Password: <S: 0, 60>

3 SIP Authentication UserName: <S: 0, 80>

3 SIP Mode: <On/Off>

3 SIP Server Address: <S: 0, 255>

3 SIP Server Discovery: <Manual/Auto>

3 SIP Server Type: <Auto/Nortel/Microsoft/Cisco/Alcatel/Experimental>

3 SIP TLS Verify <On/Off>

3 SIP Transport Default: <Auto/TCP/UDP/TLS>

3 SNMP CommunityName: <S: 0, 16>

3 SNMP HostIPAddr [1..3]: <S: 0, 64>

3 SNMP Mode: <On/Off/ReadOnly/TrapsOnly>

3 SNMP SystemContact: <S: 0, 70>

3 SNMP SystemLocation: <S: 0, 70>

1 SSH Mode: <On/Off>

D 13887.09
APRIL 2009 139
Configuration Storage Levels
StartupVideoSource — UseAsLocalPCMonitor TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Storage Level: Configuration:

1 StartupVideoSource: <0/1/2/3/4/5/6>

1 StillImageSource: <0/1/2/3/4/5/6>

3 Streaming Address: <S: 0, 64>

3 Streaming AllowRemoteStart: <On/Off>

3 Streaming Announcements: <On/Off>

3 Streaming Hops: <0..255>

3 Streaming Password: <S: 0, 16>

3 Streaming Port: <0..65534>

3 Streaming Quality <Motion/Sharpness>

3 Streaming Source: <Local/Remote/Auto>

3 Streaming VideoRate: <16/32/64/128/192/256/320>

1 StrictPassword: <On/Off>

3 SystemUnit DisplayName: <S: 0, 50>

3 SystemUnit InternationalName: <S: 0, 49>

3 SystemUnit Name: <S: 0, 49>

3 SystemUnit Password: <S: 0, 16>

3 T1 Interface CableLength: <Range1/Range2/Range3/Range4/Range5>

1 Telnet Mode: <On/Off>

1 TelnetChallenge Mode: <On/Off>

1 TelnetChallenge Port: <23/57>

1 Time DateFormat: <DD_MM_YY/MM_DD_YY/YY_MM_DD>

1 Time DaylightSavings: <On/Off>

1 Time TimeFormat: <24H/12H>

1 Time Zone: <GMT-1200/.../GMT+1400>

1 UseAsLocalPCMonitor: <On/Off>

D 13887.09
APRIL 2009 140
Configuration Storage Levels
Video Inputs Source [1..6] Name — VNC Password TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Storage Level: Configuration:

1 Video Inputs Source [1..6] Name: <S: 0, 16>

2 Video Inputs Source [1..6] Quality: <Motion/Sharpness>

1 Video Outputs AllowHD720p: <On/Off>

1 Video Outputs AllowWXGA: <On/Off>

1 Video Outputs DVI [1..2] Mode: <On/Off>

1 Video Outputs DVI [1..2] OSD: <On/Off>

1 Video Outputs DVI [1..2] VirtualMonitor: <1..4>

1 Video Outputs DVIResolution [1..2]: <Auto/SVGA/XGA>

3 Video Outputs FormatPCWideScreen: <Normal/Wide>

3 Video Outputs Letterbox <On/Off>

1 Video Outputs TestPattern <0..10>

1 Video Outputs TV [1..2] Mode: <On/Off>

1 Video Outputs TV [1..2] OSD: <On/Off>

1 Video Outputs TV [1..2] VirtualMonitor: <1..4>

3 Video Outputs ScreenFormatPC: <4:3/16:9>

3 Video Outputs ScreenFormatTV: <4:3/16:9>

3 VNC DisplayNumber: <S: 0, 5>

3 VNC IPAddress: <S: 0, 64>

3 VNC Password: <S: 0, 8>

D 13887.09
APRIL 2009 141
 Command Information Tables
We recommend that you check out the This part of the manual describes the Command
TANDBERG web site regularly for updated
versions of this manual: Information available.
http://www.tandberg.com/docs
Command Information
Understanding the Table Layout TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Status Information Example of the

AlertToneTest — CallMute TANDBERG 000 MXP & 6000 MXP
REFERENCE USER GUIDE FOR SYSTEM INTEGRATORS command when
executed succesfully.
Command Description Parameters Result parameters Result parameters Example
when OK when error

Command AlertToneTest Command used to Tone(r): <1..10> None Cause: <1…> xcommand alerttonetest tone:5
test the supported The tone to test. Cause code *r Result (status=OK):
alert tones. When the specifying why the *r/end
command is issued the command was not OK
Brief description of system will playback the accepted by the
what the command specified alert tone. system
Description:
is used to. Textual description
of the cause code.
Parameters used with this
Boot Command used to ParameterRestore: <On/Off> None As above. xcommand boot parameterrestore: on
command. If there is an (r) reboot the system. When rebooting the system after *r Result (status=OK):
*r/end
appearing, this indicates a software upgrade, all configurations
OK
will be restored.
required parameter (i.e. a
By setting ParameterRestore to Off,
parameter that always must the system configurations prior to
be specified. The (r) is not software upgrade will be lost.

to be written – it appears CallAccept Command used to None None As above xcommand callaccept If the command was not
for your information only. answer an incoming *r Result (status=OK): / executed succesfully,
call if autoanswer is *r/end
disabled. OK a description telling
why will be provided.
CallMute Command used to mute Call(r): <1..11> None As above xcommand callmute call:2 mode:on
incoming audio from a Reference to the call to be muted or *r Result (status=OK): Details are found in this
*r/end
specific call in a Multi-
Site conference.
unmuted.
OK
column.
Mode(r): <On/Off>
Denotes whether the call is to be
muted or unmuted.

If the command is
executed succesfully,
any result parameter
returned will be stated
here.
Required parameters are identified by an (r) behind the parameter name. The (r) appears in this table for your information only and shall not be included when writing the commands – see the column Example for an illustration of this. Empty lines in the examples provided may have been removed to save space in the tables.

D 13887.X3
AUGUST 2006 
Tip! An exhaustive
description of the API
structure can be found
in the section
The TANDBERG API

D 13887.09
APRIL 2009 143
Command Information
AlertToneTest — AudioTestSignal TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Command Description Parameters Result parameters Result parameters Example

when OK when error

AlertToneTest Command used to Tone(r): <1..10> None Cause: <1…> xcommand alerttonetest tone:5
test the supported The tone to test. Cause code *r Result (status=OK):
alert tones. When the specifying why the *r/end
command is issued the command was not OK
system will playback the accepted by the
specified alert tone. system
Description:
Textual description
of the cause code.

AudioTestSignal Command used to test Type(r):<None/Sine/White/Pink> None As above Example #1:

an audio channel with Sine wave of 3kHz with level –20dB on
a specific test signal; The test signal. local speakers:
sine, white noise or Level: <-60..0>
pink noise. When the xcommand audiotestsignal type:sine
command is issued the Level in dB. The level is dependent level:-20 output:speaker frq:3000
system will send out on the output level settings on the *r Result (status=OK): /
the specified test signal system. When the output levels are *r/end
to the specified output set to default level settings, 0 dB will
channel. correspond to 1 Vrms. OK
If not specified, 0 dB will be
selected.
Example #2:
Output: <FarEnd/Speaker/AUX/ White noise with level –10 dB to FarEnd:
VCR>
xcommand audiotestsignal white -10
The output channel where the audio *r Result (status=OK): /
test signal will be activated. If not *r/end
specified, the FarEnd output will be
selected OK
Frq: <100..20000>
The frequency, in Hz, of the sine-
tone. If not specified, 1 kHz will be
selected. This setting does only
apply to the sine test signal.

Required parameters are identified by an (r) appended to the parameter name. The (r) appears in this table for your information only and shall not be included when writing the commands – see the column Example for an illustration of this. Empty lines in the examples provided may have been removed to save space in the tables.

D 13887.09
APRIL 2009 144
Command Information
Boot — CallMuteOutgoing TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Command Description Parameters Result parameters Result parameters Example

when OK when error

Boot Command used to ParameterRestore: <On/Off> None As above. xcommand boot parameterrestore: on
reboot the system. When rebooting the system after *r Result (status=OK):
software upgrade, all configurations *r/end
will be restored. OK

By setting ParameterRestore to Off,

the system configurations prior to
software upgrade will be lost.

CallAccept Command used to None None As above xcommand callaccept

answer an incoming *r Result (status=OK): /
call if autoanswer is *r/end
disabled. OK

CallMute Command used to mute Call(r): <1..11> None As above xcommand callmute call:2 mode:on
incoming audio from a Reference to the call to be muted or *r Result (status=OK):
specific call in a Multi- unmuted. *r/end
Site conference. OK
Mode(r): <On/Off>
Denotes whether the call is to be
muted or unmuted.

CallMuteOutgoing Command used to Call(r): <1..11> None As above xcommand callmuteoutgoing call:2 mode:on
mute outgoing audio Reference to the call to be muted or *r Result (status=OK):
to a specific call in a unmuted. *r/end
MultiSite conference. OK
Mode(r): <On/Off>
Typical user scenario
for this command is a Denotes whether the call is to be
three-part conference muted or unmuted.
where two of the
participants are from
the same company
discussing an issue with
a sub-contractor.
During the conference
the participants from
the same company want
to share some thoughts
in private before making
the final decision.

Required parameters are identified by an (r) appended to the parameter name. The (r) appears in this table for your information only and shall not be included when writing the commands – see the column Example for an illustration of this. Empty lines in the examples provided may have been removed to save space in the tables.

D 13887.09
APRIL 2009 145
Command Information
CameraFocus — CameraHalt TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Command Description Parameters Result parameters Result parameters Example

when OK when error

CallSetAudioTP Command used with Call(r): <1..11> None As above xcommand callsetaudiotp call:2 mode:on
TANDBERG Experia. *r Result (status=OK):
*r/end
Mode(r): <On/Off> OK

CameraFocus Command used to Camera(r): <1..13> None As above xcommand camerafocus camera:1 value:+
change focus of a spe- Addresses which camera to have its *r Result (status=OK):
cific camera. focus changed. *r/end
OK
Value(r): <Auto/Manual/+/->
Specifies the wanted operation.

CameraForceUpgrade Command used to Camera(r): <1..13> None As above xcommand cameraforceupgrade camera:1
initiate software *r Result (status=OK):
upgarde of the *r/end
TANDBERG Precision HD OK
Camera. Should only be
used after downgrade
of the TANDBERG
MXP Codec software
or if the configuration
CameraSwUpgrade is
set to Off. When the
TANDBERG MXP Codec
software is upgraded,
the TANDBERG Precision
HD Camera will be
upgraded automatically
if the configuration
CameraSwUpgrade is
set to Auto.

CameraHalt Command used to stop None None As above xcommand camerahalt

moving a specific *r Result (status=OK):
camera. *r/end
OK

Required parameters are identified by an (r) appended to the parameter name. The (r) appears in this table for your information only and shall not be included when writing the commands – see the column Example for an illustration of this. Empty lines in the examples provided may have been removed to save space in the tables.

D 13887.09
APRIL 2009 146
Command Information
CameraMove — CameraReconfigure TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Command Description Parameters Result parameters Result parameters Example

when OK when error

CameraMove Command used to Camera(r): <1..13> None As above xcommand cameramove camera:1 direction:
instruct the camera Addresses the camera to move. right
to move in a specified *r Result (status=OK):
direction. The camera Direction(r): <Up/Down/Right/ *r/end
will continue moving Left/In/Out/FocusIn/FocusOut > OK
until the CameraHalt Specifies the direction to move.
command is issued.

CameraPosition Command used to Camera(r): <1..13> None As above xcommand cameraposition camera:1
instruct the camera Addresses the camera to position. pan:1700 tilt:1700
to move to a specific *r Result (status=OK):
position. Pan: <-32768..32767> *r/end
Pan value. OK

Tilt: <-32768..32767>
Tilt value.
Zoom: <0..65534>
Zoom value.
Focus: <0..65534>
Focus value.
Note! The supported values for pan,
tilt, zoom, focus will depend on the
type of camera in use. For example:
Sony cameras have value ranges
different from TANDBERG cameras.

CameraReconfigure Re-configures all None None As above xcommand camerareconfigure

cameras connected to *r Result (status=OK):
the switch or codec. *r/end
This may be useful OK
if you connect new
cameras without turning
the power off, since the
switch does not auto
detect such changes.

Required parameters are identified by an (r) appended to the parameter name. The (r) appears in this table for your information only and shall not be included when writing the commands – see the column Example for an illustration of this. Empty lines in the examples provided may have been removed to save space in the tables.

D 13887.09
APRIL 2009 147
Command Information
CameraTrackingStart — ChairTake TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Command Description Parameters Result parameters Result parameters Example

when OK when error

CameraTrackingStart Command used to turn None None As above xcommand cameratrackingstart

camera tracking on. *r Result (status=OK):
*r/end
OK

CameraTrackingStop Command used to turn None None As above xcommand cameratrackingstop

cameratracking off. *r Result (status=OK):
*r/end
OK

CameraUpgrade Upgrade camera or (r): <1..13> <filename> None As above xcommand cameraupgrade:1 s01692.pkg
video switch with new Addresses the specific camera or *r Result (status=OK):
software. The software TANDBERG Video Switch. *r/end
must be put on a folder OK
named either /tmp or Camera software files are named
/user. s01692.pkg.

Currently only upgrading Video Switch software files are

of the first camera named s51200.pkg.
or video switch is
supported.

CameraWhiteBalance Command used to Camera(r): <1..13> None As above xcommand camerawhitebalance camera:1
initiate calibration of Addresses the specific camera. *r Result (status=OK):
the whitebalance of the *r/end
camera. The command OK
is valid only when the
Camera Whitebalance
Mode is configured to
Manual.

ChairRelease Command used to None None As above xcommand chairrelease

release chair in a *r Result (status=OK):
conference supporting *r/end
chair control. OK

ChairTake Command used to take None None As above xcommand chairtake

chair in a conference *r Result (status=OK):
supporting chair control. *r/end
OK

Required parameters are identified by an (r) appended to the parameter name. The (r) appears in this table for your information only and shall not be included when writing the commands – see the column Example for an illustration of this. Empty lines in the examples provided may have been removed to save space in the tables.

D 13887.09
APRIL 2009 148
Command Information
ConferenceDisconnect — ConferenceTerminate TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Command Description Parameters Result parameters Result parameters Example

when OK when error

ConferenceDisconnect Command used to None None As above xcommand ConferenceDisconnect

disconnect all calls *r Result (status=OK):
connected to the *r/end
system. OK

ConferenceTerminate ConferenceTerminate None None As above xcommand ConferenceTerminate

is only valid if the *r Result (status=OK):
system is participant in *r/end
a MultiSite conference OK
supporting Chair
Control, and for
the system granted
chair. The command
will disconnect all
participants in the
conference (not only the
calls connected locally
to the system).

Required parameters are identified by an (r) appended to the parameter name. The (r) appears in this table for your information only and shall not be included when writing the commands – see the column Example for an illustration of this. Empty lines in the examples provided may have been removed to save space in the tables.

D 13887.09
APRIL 2009 149
Command Information
CorpDirSearch TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Command Description Parameters Result parameters Result parameters Example

when OK when error

CorpDirSearch Command to search With no parameters specified the None As above xcommand corpdirsearch
for contacts in the result will show the first 40 catalogs. *r Result (status=OK):
corporate directory Entity 1 <type:Catalog>:
phone book. Name: “0.1 - Personal Systems“
Use the CorpDirGetNext Path: <S: 0, 256> Path: ““
and the ID of the last Enter the path, which is the ID of the ID: “138“
entity to search for the folder or subfolder, to search in. IsFirst: True
next contacts. The result will show the first 40 IsLast: False
entries in the given catalog. If no Entity 2 <type:Catalog>:
Use the Name: “0.2 - Meeting Rooms“
CorpDirGetPrevious catalog specified by Path, then the
root catalog is used. Path: ““
and the ID of the first ID: “140“
entity to search for the Query: <S: 0, 81> IsFirst: False
previous contacts. IsLast: True
Enter the query to search for.
*r/end
StartsWith: <S: 0, 81> OK
The search string should start with.
xcommand corpdirsearch query:charlie
Hits: <1..40> hits:1
Specify the number of hits to show. *r Result (status=OK):
Entity 1 <type:Entry>:
SubFolders: <On/Off>
Name: “charlie.brown“
Define if the search should also Path: ““
include subfolders. ID: “29“
IsFirst: True
IsLast: False
IsFirst: <True/False> ContactInfo 1:
True indicates that this is the first hit Protocol: H323
matching the search criteria. CallRate: 384
False indicates that this is not the Restrict: Off
first hit matching the search criteria. DialString: “[email protected]“
CorpDirGetPrevious can be used to Description: “[email protected]
search for more contacts. <H323>“
ContactInfo 2:
IsLast: <True/False> Protocol: H320
True indicates that this is the last hit CallRate: 384
matching the search criteria. Restrict: Off
DialString: “791“
False indicates that this is not the
Description: “791 <ISDN>“
last hit matching the search criteria.
*r/end
CorpDirGetNext can be used to
OK
search for more contacts.

Required parameters are identified by an (r) appended to the parameter name. The (r) appears in this table for your information only and shall not be included when writing the commands – see the column Example for an illustration of this. Empty lines in the examples provided may have been removed to save space in the tables.

D 13887.09
APRIL 2009 150
Command Information
CorpDirGetNext TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Command Description Parameters Result parameters Result parameters Example

when OK when error

CorpDirGetNext After having used the With no parameters specified the None As above xcommand corpdirgetnext path:138 query:
CorpDirSearch, this result will show first 40 catalogs. charlie id:29 hits:5
command is used when *r Result (status=OK):
you want to search for ...
the next contacts in Path: <S: 0, 256> <The next 5 entries, from id 29 for the given search
the corporate directory Enter the path, which is the ID of the will show>
phone book. folder or subfolder, to search in. ...
The result will show the first 40 *r/end
entries in the given catalog. If no OK
The ID is found in the
CorpDirSearch result. catalog specified by Path, then the
root catalog is used. xcommand corpdirgetnext path:138 query:
charlie id:34 hits:5
Query: <S: 0, 81> *r Result (status=OK):
Enter the query to search for. ...
<The next 5 entries, from id 34 for the given search
StartsWith: <S: 0, 81> will show>
The search string should start with. ...
*r/end
Hits: <1..40> OK
Specify the number of hits to show.
ID: <S: 0, 21>
Define the ID of an entity.
The ID is relative to a specific
search. When using the
CorpDirGetNext command you
need to specify the same Query
and StartsWith strings as in the
CorpDirSearch command.
SubFolders: <On/Off>
Define if the search should also
include subfolders

Required parameters are identified by an (r) appended to the parameter name. The (r) appears in this table for your information only and shall not be included when writing the commands – see the column Example for an illustration of this. Empty lines in the examples provided may have been removed to save space in the tables.

D 13887.09
APRIL 2009 151
Command Information
CorpDirGetPrevious TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Command Description Parameters Result parameters Result parameters Example

when OK when error

CorpDirGetPrevious After having used the With no parameters specified the None As above xcommand corpdirgetprevious path:138
CorpDirSearch, this result will show first 40 catalogs. query:charlie id:29 hits:5
command is used when *r Result (status=OK):
you want to search for ...
the previous contacts in Path: <S: 0, 256> <The previous 5 entries, from id 29 for the given
the corporate directory Enter the path, which is the ID of the search will show>
phone book. folder or subfolder, to search in. ...
The result will show the first 40 *r/end
entries in the given catalog. If no OK
The ID is found in the
CorpDirSearch result. catalog specified by Path, then the
root catalog is used. xcommand corpdirgetprevious path:138
query:charlie id:34 hits:5
Query: <S: 0, 81>
*r Result (status=OK):
Enter the query to search for. ...
StartsWith: <S: 0, 81> <The previous 5 entries, from id 34 for the given
search will show>
The search string should start with. ...
Hits: <1..40> *r/end
OK
Specify the number of hits to show.
ID: <S: 0, 21>
Define the ID of an entity.
The ID is relative to a specific
search. When using the
CorpDirGetPrevious command you
need to specify the same Query
and StartsWith strings as in the
CorpDirSearch command
SubFolders: <On/Off>
Define if the search should also
include subfolders

Required parameters are identified by an (r) appended to the parameter name. The (r) appears in this table for your information only and shall not be included when writing the commands – see the column Example for an illustration of this. Empty lines in the examples provided may have been removed to save space in the tables.

D 13887.09
APRIL 2009 152
Command Information
DefaultValueSet TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Command Description Parameters Result parameters Result parameters Example

when OK when error

DefaultValuesSet Command used to reset Level: <1..3> None As above xcommand defaultvaluesset level:2
configurations to factory Configurations are divided into *r Result (status=OK):
default values. three different storage levels. *r/end
The level parameter denotes that OK
configurations on this level and all
levels below (lower value) are to be
reset.
The complete list of Storage Levels
can be found in Configuration
Storage Levels.

Required parameters are identified by an (r) appended to the parameter name. The (r) appears in this table for your information only and shall not be included when writing the commands – see the column Example for an illustration of this. Empty lines in the examples provided may have been removed to save space in the tables.

D 13887.09
APRIL 2009 153
Command Information
Dial TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Command Description Parameters Result parameters Result parameters Example

when OK when error

Dial Command used to dial Number: <S: 0, 60> CallRef: <1..11> As above xcommand dial number:123 callrate:256
out from the system. Number to dial. Reference to the netprofile:3
call. To be used *r Result (status=OK):
SecondNumber: <S: 0, 60> as reference when CallRef: 1
2Xh221 second number. monitoring the call. LogTag: 312
*r/end
SubAddress: <S: 0, 20> LogTag: <1…> OK
Sub address. Unique reference
to call. Identifies
CallRate: <Tlph/1xh221/xh221/6 the call in the call
4/128/192/256/320/384/512/7 log.
68/1152/1472/1920/2560/3072
/4096/H0/Max/Auto>
Specifies the callrate to use. The
CallRates supported for a system
will depend on model and software
options.
Restrict: <On/Off>
A restricted call uses 56kbps
channels rather than the default
unrestricted 64kbps channels. Some
older networks (primarily in the USA)
do not support 64kbps channels and
require the use of restricted 56kbps
calls. By default the system will dial
an unrestricted call and downspeed
to 56kbps if necessary.
NetProfile: <1..7>
Defines the NetProfile to use. A
NetProfile defines network type and
a possible prefix, ref. configuration
Netprofile.
BillingCode: <S: 0, 16>
By adding a Billing Code when
placing a call, the call can be
identified in the call log (xhistory/
history.xml) after it is disconnected.

Required parameters are identified by an (r) appended to the parameter name. The (r) appears in this table for your information only and shall not be included when writing the commands – see the column Example for an illustration of this. Empty lines in the examples provided may have been removed to save space in the tables.

D 13887.09
APRIL 2009 154
Command Information
DialGlobalEntry — DialLocalEntry TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Command Description Parameters Result parameters Result parameters Example

when OK when error

DialGlobalEntry Command used to dial a GlobalEntryId(r): <1..400> CallRef: <1..11> As above xcommand dialglobalentry globalentry-
number from the global Reference to the directory entry to Reference to the id:19
directory (the Global be dialed. call. To be used *r Result (status=OK):
Directory is downloaded as reference when CallRef: 1
to the system by an monitoring the call. LogTag: 312
external application). *r/end
LogTag: <1…> OK
Unique reference
to call. Identifies
the call in the call
log.

DialGroupEntry Command used to dial GroupEntryId(r): <1..50 > The system As above xcommand dialgroupentry groupentryid:19
an entry from the Group Reference to the directory entry to will return the *r Result (status=OK):
Directory. Dialling from be dialed. following elements CallRef: 2
the Group Directory for each call LogTag: 313
makes it possible to initiated. CallRef: 1
set up a MultiSite CallRef: <1..11> LogTag: 312
conference in one CallRef:
operation. Reference to the *r/end
call. To be used OK
as reference when
monitoring the call.
LogTag: <1…>
Unique reference
to call. Identifies
the call in the call
log.

DialLocalEntry Command used to dial a LocalEntryId(r): <1..200> CallRef: <1..11> As above xcommand diallocalentry localentryid:15
number from the locally Reference to the directory entry to Reference to the *r Result (status=OK):
stored directory. be dialed. call. To be used CallRef: 1
as reference when LogTag: 312
monitoring the call. *r/end
OK
LogTag: <1…>
Unique reference
to call. Identifies
the call in the call
log.

Required parameters are identified by an (r) appended to the parameter name. The (r) appears in this table for your information only and shall not be included when writing the commands – see the column Example for an illustration of this. Empty lines in the examples provided may have been removed to save space in the tables.

D 13887.09
APRIL 2009 155
Command Information
DisconnectCall — FECCFocus TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Command Description Parameters Result parameters Result parameters Example

when OK when error

DisconnectCall Command used to Call: <1..11> None As above xcommand disconnectcall call:9
disconnect a call. Reference to the call to be *r Result (status=OK):
disconnected. If this parameter is *r/end
omitted, all active calls in the system OK
will be disconnected.

DuoVideoStart Command used to VideoSource: <1..6> None As above xcommand duovideostart videosource:5
initiate DuoVideo/H.239 Specifies which video source to be *r Result (status=OK):
from the system. used for the additional video stream. *r/end
If this parameter is omitted, the OK
system will use the default DuoVideo
source configured for the system,
ref. configuration DuoVideoSource

DuoVideoStop Command used to stop None None As above xcommand duovideostop

DuoVideo/H.239. *r Result (status=OK):
*r/end
OK

DTMFSend Command used to send Value(r): <E164: 1, 1> None As above xcommand dtmfsend value:5
DTMF tones to the far The DTMF tone to send. *r Result (status=OK):
end. *r/end
OK
NOTE! The DTMF tones
are also played back
locally.
NOTE! This command
is also supported when
the system is not in a
call (the tones will only
be played back locally).

FECCFocus Command used to Value(r): <+/-> None As above xcommand feccfocus value:+
change focus of a far Specifies whether to increase or *r Result (status=OK):
end camera. decrease focus. *r/end
OK

Required parameters are identified by an (r) appended to the parameter name. The (r) appears in this table for your information only and shall not be included when writing the commands – see the column Example for an illustration of this. Empty lines in the examples provided may have been removed to save space in the tables.

D 13887.09
APRIL 2009 156
Command Information
FECCMove — FeedbackDeregister TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Command Description Parameters Result parameters Result parameters Example

when OK when error

FECCMove Command used Direction(r): <Up/Down/Right/Left/ None As above xcommand feccmove direction:right
to issue a Far End In/Out/FocusIn/FocusOut> *r Result (status=OK):
Camera Control – Move Specifies the direction to move. *r/end
command. OK

FECCPresetActivate Command used to Number(r): <0..15> None As above xcommand feccpresetactivate number:4
activate a far end The preset number to activate. *r Result (status=OK):
preset. *r/end
OK

FECCPresetStore Command used to store Number(r): <0..15> None As above xcommand feccpresetstore number:4
a far end preset. The preset number to store. *r Result (status=OK):
*r/end
OK

FECCRequestStill Command used to Source(r): <0..15> None As above xcommand requeststill source:4
request a still image The far end source to select. *r Result (status=OK):
from a specific source *r/end
on the far end side. OK

FECCSelectSource Command used to Source(r): <0..15> None As above xcommand feccselectsource source:4
select a far end source. The far end source to select. *r Result (status=OK):
*r/end
OK

FeedbackDeregister Command used ID: <1..3> None As above xcommand feedbackderegister id:1
to deregister XML ID for the registration to deregister. *r Result (status=OK):
feedback over HTTP(S). ID: 2
*r/end
OK

Required parameters are identified by an (r) appended to the parameter name. The (r) appears in this table for your information only and shall not be included when writing the commands – see the column Example for an illustration of this. Empty lines in the examples provided may have been removed to save space in the tables.

D 13887.09
APRIL 2009 157
Command Information
FeedbackRegister — FloorRequest TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Command Description Parameters Result parameters Result parameters Example

when OK when error

FeedbackRegister Command used to ID: <1..3> ID: <1..3> As above xcommand feedbackregister url:http://10.
instruct the system to ID for the registration. If this 47.14.185:8000
return XML feedback parameter is omitted the system expression.1:status/call
over HTTP(S) to uses the first vacant ID. expression.2:status/conference
specific URLs. What *r Result (status=OK):
parts of the Status URL(r): <S: 0, 256> ID: 2
and Configuration XML The URL to post feedback to. *r/end
documents to monitor OK
are specified by XPath Expression.1..15: <S: 0, 256>
expressions. XPath expression
The system supports
issuing feedback to 3
different URLs.
The system allows
a total of 20 XPath
expressions to be
registered, with a
maximum of 15 for a
single URL.

FIPSMode Command to activate Mode(r): <On/Off> On: “Entering FIPS As above xcommand fipsmode:off
and deactivate FIPS Denotes whether the video system is mode, restart *r Result (status=OK):
mode. to be in FIPS mode or not. required.” *r/end
OK
Off: “Exiting FIPS
mode, restart
required.”
The codec wil
restart.

FloorRelease Command used to None None As above xcommand floorrelease

release floor in a *r Result (status=OK):
MultiSite conference. *r/end
OK

FloorRequest Command used to None None As above xcommand floorrequest

request floor in a *r Result (status=OK):
MultiSite conference. *r/end
OK

Required parameters are identified by an (r) appended to the parameter name. The (r) appears in this table for your information only and shall not be included when writing the commands – see the column Example for an illustration of this. Empty lines in the examples provided may have been removed to save space in the tables.

D 13887.09
APRIL 2009 158
Command Information
FloorToSite — KeyDown TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Command Description Parameters Result parameters Result parameters Example

when OK when error

FloorToSite Command used to MCUID(r): <1..191> None As above xcommand floortosite mcuid:85 terminal-
assign floor to a specific MCUID to the MultiSite the site is id:2
site in a MultiSite connected to. *r Result (status=OK):
conference supporting *r/end
H.243. TerminalID(r): <1..191> OK
The site’s terimnal id, referenced to
the MultiSite it is connected to.

FloorToSiteEnd Command used to end None None As above xcommand floortositeend

the assignment of floor *r Result (status=OK):
to a specific site in a *r/end
MultiSite conference OK
supporting H.243.
Requires that the
command FloorToSite
has been issued in
advance

GroupEntryAdd Command used to add Name: <S: 0, 48> GroupEntryId: As above xcommand groupentryadd name:”My Group
a new Group entry to The entry’s name. <1..50> Entry” localentryid.1:1 localentryid.2:7
the locally stored Group Reference to the localentryid.3:9
Directory (or MultiSite LocalEntryId.1..10: <1..200> Group Directory *r Result (status=OK):
Directory). The entry is References to local entry ids to be position the entry GroupEntryId: 17
stored in the first vacant included in this Group entry. is stored. *r/end
position in the Group OK
Directory.

GroupEntryDelete Command used to GroupEntryId(r): <1..50> None As above xcommand groupentrydelete groupentryid:30
delete an entry in the Reference to the entry to delete. *r Result (status=OK):
locally stored Group *r/end
Directory. OK

KeyDown Command used to Key(r): <0/1/2/3/4/5/6/7/8/ None As above xcommand keydown key: phonebook
emulate pressing a key 9/*/#/Connect/Disconnect/ *r Result (status=OK):
on the TANDBERG MXP Up/Down/Right/Left/Selfview/ *r/end
remote control without Layout/Phonebook/Cancel/ OK
releasing it. The KeyDown MicOff/Presentation/VolumeUp/
command should be VolumeDown/OK/ZoomIn/
followed by a KeyRelease ZoomOut/Grab>
command to emulate
releasing the key.

Required parameters are identified by an (r) appended to the parameter name. The (r) appears in this table for your information only and shall not be included when writing the commands – see the column Example for an illustration of this. Empty lines in the examples provided may have been removed to save space in the tables.

D 13887.09
APRIL 2009 159
Command Information
KeyRelease — KeyEnable TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Command Description Parameters Result parameters Result parameters Example

when OK when error

KeyRelease Command used to Key(r): <0/1/2/3/4/5/6/7/8/ None As above xcommand keyrelease key: phonebook
emulate release an 9/*/#/Connect/Disconnect/ *r Result (status=OK):
already pressed key on Up/Down/Right/Left/Selfview/ *r/end
the TANDBERG MXP Layout/Phonebook/Cancel/ OK
remote control. The MicOff/Presentation/VolumeUp/
KeyRelease command VolumeDown/OK/ZoomIn/
should be preceded by ZoomOut/Grab>
a KeyDown command to
emulate pressing the key.

KeyPress Command used to Key(r): <0/1/2/3/4/5/6/7/8/ None As above xcommand keypress key: phonebook
emulate pressing a 9/*/#/Connect/Disconnect/ *r Result (status=OK):
key on the TANDBERG Up/Down/Right/Left/Selfview/ *r/end
MXP remote control Layout/Phonebook/Cancel/ OK
for a short while. This MicOff/Presentation/VolumeUp/
command needs no VolumeDown/OK/ZoomIn/
release command. ZoomOut/Grab>

KeyDisable Command used to Key(r): <0/1/2/3/4/5/6/7/8/ None As above xcommand keydisable key: micoff
disable a key on the 9/*/#/Connect/Disconnect/ *r Result (status=OK):
TANDBERG MXP remote Up/Down/Right/Left/Selfview/ *r/end
control. Layout/Phonebook/Cancel/ OK
MicOff/Presentation/VolumeUp/
VolumeDown/OK/ZoomIn/
ZoomOut/Grab>

KeyEnable Command used to Key(r): <0/1/2/3/4/5/6/7/8/ None As above xcommand keyenable key: micoff
enable a key on the 9/*/#/Connect/Disconnect/ *r Result (status=OK):
TANDBERG MXP remote Up/Down/Right/Left/Selfview/ *r/end
control. Layout/Phonebook/Cancel/ OK
MicOff/Presentation/VolumeUp/
VolumeDown/OK/ZoomIn/
ZoomOut/Grab>

Required parameters are identified by an (r) appended to the parameter name. The (r) appears in this table for your information only and shall not be included when writing the commands – see the column Example for an illustration of this. Empty lines in the examples provided may have been removed to save space in the tables.

D 13887.09
APRIL 2009 160
Command Information
LocalEntryAdd — MessageBoxDelete TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Command Description Parameters Result parameters Result parameters Example

when OK when error

LocalEntryAdd Command used to Name: <S: 0, 48> LocalEntryId: As above xcommand localentryadd name:”John Galt”
add a new entry to the The entry’s name. <1..200> number:123
Directory stored locally. Reference to the *r Result (status=OK):
The entry is stored in Number: <S: 0, 60> Directory position LocalEntryId: 17
the first vacant position The entry’s number. the entry is stored. *r/end
in the Directory. OK
SecondNumber: <S: 0, 60>
The entry’s second number (2XH221
number).
SubAddress: <S: 0, 10>
The entry’s sub address.
CallRate:
<Tlph/1xh221/2xh221/64/128/
192/256/320/384/512/768/115
2/1472/1920/2560/3072/4096/
H0/Max/Auto>
The callrate to use when calling this
entry.
Restrict: <On/Off>
Whether to use restrict or not when
calling this entry.
NetProfile: <1..7>
The Net Profile to use when calling
this entry.

LocalEntryDelete Command used to LocalEntryId(r): <1..200> None As above xcommand localentrydelete localentry-
delete an entry in the Reference to the entry to delete. id:66
locally stored Directory. *r Result (status=OK):
*r/end
OK

MessageBoxDelete Command used to None None As above xcommand messageboxdelete

delete a message box *r Result (status=OK):
on the screen. *r/end
OK

Required parameters are identified by an (r) appended to the parameter name. The (r) appears in this table for your information only and shall not be included when writing the commands – see the column Example for an illustration of this. Empty lines in the examples provided may have been removed to save space in the tables.

D 13887.09
APRIL 2009 161
Command Information
MessageBoxDisplay — PresetActivate TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Command Description Parameters Result parameters Result parameters Example

when OK when error

MessageBoxDisplay Command used to add a Title(r): <S: 0, 40> None As above xcommand messageboxdisplay title:Welcome
graphical message box Message box title. line.1:”How are you?”
on the screen. key.1:Good
Line.1..3: <S: 0, 40> key.2:Bad
Text to be displayed on the lines *r Result (status=OK):
within the box. *r/end
OK
Key.1..3: <S: 0, 15>
Text to be displayed on the keys

PIPHide Command used to hide VirtualMonitor(r): <1..4> None As above xcommand piphide virtualmonitor:1
a PIP on a specific Addresses which VirtualMonitor to *r Result (status=OK):
VirtualMonitor. apply the command. *r/end
OK

PIPShow Command used to VirtualMonitor(r): <1..4> None As above xcommand pipshow virtualmonitor:1 pic-
display a specific picture Addresses which VirtualMonitor to ture:remoteduo call:5
in a PIP on a selected apply the command. postion:topright
VirtualMonitor *r Result (status=OK):
Picture(r): <LocalMain/LocalDuo/ *r/end
RemoteMain/RemoteDuo/ OK
JPEG/TandbergMonitor1/
TandbergMonitor2/None>
Specifies which of the supported
pictures to display in the PIP on the
addressed VirtualMonitor.
Call: <1..11>
If RemoteMain or RemoteDuo is
selected, this parameter must be
supplied to select the correct remote
call.
Position: <BottomLeft/
BottomRight/TopLeft/TopRight>
Specifies where to postion the PIP.

PresetActivate Command used to Number(r): <0..14> None As above xcommand presetactivate number:4
activate a stored preset. The preset to activate. *r Result (status=OK):
*r/end
OK

Required parameters are identified by an (r) appended to the parameter name. The (r) appears in this table for your information only and shall not be included when writing the commands – see the column Example for an illustration of this. Empty lines in the examples provided may have been removed to save space in the tables.

D 13887.09
APRIL 2009 162
Command Information
PresetClear — ScreensaverActivate TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Command Description Parameters Result parameters Result parameters Example

when OK when error

PresetClear Command used to clear Number(r): <0..14> None As above xcommand presetclear number:4
a preset previously The preset to clear. *r Result (status=OK):
stored. *r/end
OK

PresetStore Command used to store Number(r): <0..14> None As above xcommand presetstore number:4
a preset. The number where to store the *r Result (status=OK):
preset. *r/end
OK

ProfileActivate Command to activate an Name(r): <S: 0, 16> None As above xcommand profileactivate:profilename
existing user profile. The name of the user profile to *r Result (status=OK):
activate. *r/end
OK

ProfileCreate Configure the video Name(r): <S: 0, 16> None As above xcommand profilecreate:profilename
system and use this The name of the user profile to *r Result (status=OK):
command to create a create. *r/end
new user profile. OK

ProfileDelete Command to delete an Name(r): <S: 0, 16> None As above xcommand profiledelete:profilename
user profile. The name of the user profile to *r Result (status=OK):
delete. *r/end
OK

ProfileList Command to list user None None As above xcommand profilelist

profiles. *r Result (status=OK):
Available 1: “Office”
Available 2: “Home”
*r/end
OK

ScreensaverActivate Command used to None None As above xcommand screensaveractivate

activate screensaver. *r Result (status=OK):
*r/end
OK

Required parameters are identified by an (r) appended to the parameter name. The (r) appears in this table for your information only and shall not be included when writing the commands – see the column Example for an illustration of this. Empty lines in the examples provided may have been removed to save space in the tables.

D 13887.09
APRIL 2009 163
Command Information
ScreensaverDeactivate — SiteViewEnd TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Command Description Parameters Result parameters Result parameters Example

when OK when error

ScreensaverDeactivate Command used to None None As above xcommand screensaverdeactivate

deactivate screensaver. *r Result (status=OK):
Note: Warranty will *r/end
be void if used with OK
TANDBERG systems
shipped with Plasma
monitors.

ScreensaverReset Command used to reset Delay(r): <1..480> None As above xcommand screensaverreset delay:90
the screensaver timer. Specifies the screensaver delay in *r Result (status=OK):
minutes. *r/end
OK

SiteDisconnect Command used to MCUID(r): <1..191> None As above xcommand sitedisconnect mcuid:85 termi-
disconnect a specific MCUID to the MultiSite the site is nalid:2
site from a MultiSite connected to. *r Result (status=OK):
conference supporting *r/end
H.243. TerminalID(r): <1..191> OK
The site’s terimnal id, referenced to
the MultiSite it is connected to.

SiteView Command used to MCUID(r): <1..191> None As above xcommand siteview mcuid:85 terminalid:2
request view of a MCUID to the MultiSite the site is *r Result (status=OK):
specific site in a connected to. *r/end
MultiSite conference OK
supporting H.243. TerminalID(r): <1..191>
The site’s terimnal id, referenced to
the MultiSite it is connected to.

SiteViewEnd Command used to end None None As above xcommand siteviewend

viewing of a specific *r Result (status=OK):
site in a MultiSite *r/end
conference supporting OK
H.243. Requires that
the SiteView command
has been issued in
advance.

Required parameters are identified by an (r) appended to the parameter name. The (r) appears in this table for your information only and shall not be included when writing the commands – see the column Example for an illustration of this. Empty lines in the examples provided may have been removed to save space in the tables.

D 13887.09
APRIL 2009 164
Command Information
SPIDAutoConfigure — TextDisplay TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Command Description Parameters Result parameters Result parameters Example

when OK when error

SPIDAutoConfigure Command used to None None As above xcommand spidautoconfigure

initiate automatic *r Result (status=OK):
configuration of SPIDs. *r/end
OK

StillImageSend Command used to send VideoSource: <1..6> None As above xcommand stillimagesend videosource:5
a still image. Specifies from which video source to *r Result (status=OK):
send a still image. If this parameter *r/end
is omitted, the system will use the OK
default still image source configured
for the system.

StreamingStart Command used to start None None As above xcommand streamingstart

streaming from the *r Result (status=OK):
system. *r/end
OK

StreamingStop Command used to stop None None As above xcommand streamingstop

streaming from the *r Result (status=OK):
system. *r/end
OK

TextDelete Command used to Layer(r): <1..3> None As above xcommand textdelete layer:1
delete a text line added The layer to delete. *r Result (status=OK):
by the TextDisplay *r/end
command. OK

TextDisplay Command used add a Layer(r): <1..3> None As above xcommand textdisplay layer:1 text:TAND-
text line on screen. Defines the lines position. BERG timeout:100
*r Result (status=OK):
Text: <S: 0, 38> *r/end
The text to display. OK

TimeOut: <0..999>
Sets the timeout value for the text
line.

Required parameters are identified by an (r) appended to the parameter name. The (r) appears in this table for your information only and shall not be included when writing the commands – see the column Example for an illustration of this. Empty lines in the examples provided may have been removed to save space in the tables.

D 13887.09
APRIL 2009 165
Command Information
VirtualMonitorReset — VirtualMonitorSet TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Command Description Parameters Result parameters Result parameters Example

when OK when error

VirtualMonitorReset Command used to VirtualMonitor(r): <1..4> None As above xcommand virtualmonitorreset virtual-
reset a VirtualMonitor. Addresses which VirtualMonitor to monitor:2
By resetting a apply the command. *r Result (status=OK):
VirtualMonitor the *r/end
system itself retakes OK
control over what to
be displayed on the
VirtualMonitor.

VirtualMonitorSet Command used to VirtualMonitor(r): <1..4> None As above xcommand virtualmonitorset virtualmoni-
instruct the system Addresses the VirtualMonitor to tor:2 picture:still
to display a specific which the command is to be applied. *r Result (status=OK):
picture on a specific *r/end
VirtualMonitor. A Picture(r): <LocalMain/LocalDuo/ OK
VirtualMonitor can Still/RemoteMain/RemoteDuo/
be displayed on one JPEG/TandbergMonitor1/
or more of the local TandbergMonitor2/
video outputs (which PictureProgram1/PictureProgram2/
VirtualMonitor a specific PictureProgram3/
video output is to PictureProgram4/None>
display is configurable). Specifies which of the supported
When this command pictures to display on the addressed
is issued for a specific VirtualMonitor.
VirtualMonitor the Call: <1..11>
picture displayed on this
If RemoteMain or RemoteDuo is
monitor will not change
selected, this parameter must be
until the VirtualMonitor
supplied to select the correct remote
is reset or set to display
call.
another picture.

Required parameters are identified by an (r) appended to the parameter name. The (r) appears in this table for your information only and shall not be included when writing the commands – see the column Example for an illustration of this. Empty lines in the examples provided may have been removed to save space in the tables.

D 13887.09
APRIL 2009 166
 Status Information Tables
We recommend that you check out the This part of the manual describes the Status information
TANDBERG web site regularly for updated
versions of this manual: available.
http://www.tandberg.com/docs There are three types of status information available:
• xstatus / status.xml
• xhistory / history.xml
• xevent / event.xml
Status Information
Understanding the Table Layout TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

The status element listed The / means logical OR.

on this page

Status Information
Conference TANDBERG 3000 MXP & 6000 MXP
REFERENCE USER GUIDE FOR SYSTEM INTEGRATORS

The status element Conference (type = Idle / PointToPoint / PointToMultiSite / MultiSite):

listing starts here If type = Idle the following will be included:

<Nothing>

Example:
*s Conference (type=Idle): /
*s/end Which status elements
to show in a given
If type = PointToPoint the following will be included: situation is context
Calls: dependent. The
CallRef [1..11]: 1..11 context is reflected in
DuoVideo (status = None / Ready / On): the attribute values.
If status = None / Ready the following will be included: Certain conditions will
<Nothing> cause some status
This condition If status = On the following will be included: elements to be shown,
causes CallRef [1..11]: 0..11 while other conditions
this to appear LoudestParticipant: will produce other
CallRef: 0..11 status elements.
Example: The conditions are
Example showing *s Conference (type=PointToPoint): always shown on grey
Calls:
status of a real CallRef 1: 1 background and start
DuoVideo (status=Ready): /
case. LoudestParticipant: with an If statement.
CallRef: 1
*s/end

If type = PointToMultiSite the following will be included:

Calls:

CallRef [1..11]: 1..11

DuoVideo (status = None / Ready / On):

If status = None / Ready the following will be included:

<Nothing>

D 13887.X3
AUGUST 2006 20

Indenting is used to keep track of the Tip! For easy line-by-line parser, use the complete path formatter,
levels. In the tables one light grey square described in XACLI – Status-type commands – complete path formatting
is used per level.

D 13887.09
APRIL 2009 168
Status Information – xstatus /xstatus.xml
Audio TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Audio

AudioModule: None / NAMI / NAMII / Digital NAM / mDNAM

Inputs

Microphone [1..3]:

Active: True / False

Line [1..3]:

Active: True / False

Example:
*s Audio:
AudioModule: None
Inputs:
Microphone 1:
Active: True
Microphone 2:
Active: False
Microphone 3:
Active: False
Line 1:
Active: False
Line 2:
Active: False
Line 3:
Active: False
*s/end

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 169
Status Information – xstatus /xstatus.xml
BRI TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

BRI [1..6] (ready= Unknown / True / False)

If ready = Unknown / True, the following will be included:

Channel [1..2] (type = BChannel , status=Idle / Calling / Answering / Proceeding / Connect / Disconnecting / Disconnected)

If type = Bchannel and status=Idle, the following will be included:

<Nothing>

If type = Bchannel and status = Calling / Answering / Proceeding / Connect the following will be included:

CallingNumber:

ConnectionTime:

If type = Bchannel and status = Disconnecting / Disconnected the following will be included:

CallingNumber:

CauseLocation:

ChannelCause:

ConnectionTime:

If ready = False the following will be included:

Layer1Alarm: <NA>

Layer2Alarm: <NA>

Example – see overleaf.

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 170
Status Information – xstatus /xstatus.xml
BRI cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Example:
*s BRI 1 (ready=True):
Channel 1 (type=BChannel, status=Idle): /
Channel 2 (type=BChannel, status=Disconnected):
CallingNumber: “8770”
CauseLocation: 0
ChannelCause: 41
ConnectionTime: 258
*s/end

*s BRI 2 (ready=True):
Channel 1 (type=BChannel, status=Connect):
CallingNumber: “8770”
ConnectionTime: 346
Channel 2 (type=BChannel, status=Connect):
CallingNumber: “8770”
ConnectionTime: 346
*s/end

*s BRI 3 (ready=True):
Channel 1 (type=BChannel, status=Connect):
CallingNumber: “8770”
ConnectionTime: 345
Channel 2 (type=BChannel, status=Connect):
CallingNumber: “8770”
ConnectionTime: 345
*s/end

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 171
Status Information – xstatus /xstatus.xml
Call TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Call [1..10] (status=Disconnected / CallIDLE / Dialing / Alerting / Proceeding / EstablOut / EstablIn / AwaitInCnf / Connected / Disconnecting / Await2ndnr / ClearOut / ClearIn / Syncing / Capex / Synced / Unframed,
type = NA / Tlph / Vtlph,
protocol = NA / ISDN / H320 / H323 / SIP,
direction = NA / Incoming / Outgoing,
logTag = 1..x )

If status = Disconnected
and type = NA
and protocol = NA
and direction = NA
and logtag = x
the following will be included:

Cause:

If status = Dialing / Alerting / Proceeding / EstablOut / EstablIn / AwaitInCnf / Connected / Disconnecting / Await2ndnr / ClearOut / ClearIn / Syncing / Capex / Synced / Unframed
and type = Tlph
and protocol = ISDN
and direction = Incoming / Outgoing
and logTag = x
the following will be included:

CallRate: 64

RemoteNumber [1..2]:

RemoteSubAddress:

IncomingNumber:
Appears for incoming calls only
IncomingSubAddress:

Mute: On/Off

Microphone: On/Off

Duration: 0...

MuteOutgoing: On/Off

Channels [1..2] (type = Incoming / Outgoing):

If type = incoming / outgoing the following will be included:

Rate: 64

Restrict: On/Off

Audio (status = Active / Inactive):

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 172
Status Information – xstatus /xstatus.xml
Call cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

If status = Inactive the following will be included

<Nothing>

If status = Active the following will be included

Protocol: G711 / G722 / G722.1 / G728 / AAC-LD

Rate: 16...

Example:
*s Call 1 (status=Synced, type=Tlph, protocol=ISDN, direction=Incoming, logTag=5944):
CallRate: 64
RemoteNumber 1: “8733”
RemoteNumber 2: “”
RemoteSubAddress: “”
IncomingNumber: “8770”
IncomingSubAddress: “”
Mute: Off
Microphone: On
Duration: 127
MuteOutgoing: Off
Channels 1 (type=Incoming):
Rate: 64
Restrict: Off
Audio (status=Active):
Protocol: G711
Rate: 64
Channels 2 (type=Outgoing):
Rate: 64
Restrict: Off
Audio (status=Active):
Protocol: G711
Rate: 64
*s/end

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 173
Status Information – xstatus /xstatus.xml
Call cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

If status = Dialing / Alerting / Proceeding / EstablOut / EstablIn / AwaitInCnf / Connected / Disconnecting / Await2ndnr / ClearOut / ClearIn / Syncing / Capex / Synced / Unframed
and type = Vtlph
and protocol = H320
and direction = Incoming / Outgoing
and logTag = x
the following will be included:

CallRate: 64/128/../4096

RemoteNumber [1..2]:

RemoteSubAddress:

IncomingNumber:
Appears for incoming calls only
IncomingSubAddress:

Mute: On / Off

Microphone: On / Off

Duration: 0...

MuteOutgoing: On / Off

Channels [1..2] (type = Incoming / Outgoing):

If type = Incoming / Outgoing the following will be included:

Rate: 64 / .. / 4096

Restrict: On / Off

Encryption (status = Off / Negotiate / On):

If status = Off / Negotiate the following will be included:

<Nothing>

If status = On the following will be included:

Type: DES / AES-128

CheckCode:

Audio (status = Active / Inactive):

If status = Inactive the following will be included:

<Nothing>

If status = Active the following will be included:

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 174
Status Information – xstatus /xstatus.xml
Call cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Protocol: G711 / G722 / G722.1 / G728 /AAC-LD

Rate:

Video [1..2] (status = Active / Inactive):

If status = Inactive the following will be included:

<Nothing>

If status = Active the following will be included:

Protocol: H261 / H263 / H263+ / H264

Resolution: QCIF / SQCIF / CIF / 2CIF / 4CIF / ICIF / SIF / 4SIF /ISIF /VGA / SVGA / XGA / QVGA / 448p / 400p / w288p / w448p / w576p / w720p

Rate:

Data (status = Active / Inactive):

If status = Inactive the following will be included:

<Nothing>

If status = Active the following will be included:

Type: LSD / MLP

Protocol: FECC

Rate:

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 175
Status Information – xstatus /xstatus.xml
Call cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Example (see previous page for the status information applicable):

*s Call 1 (status=Synced, type=Vtlph, protocol=H320, direction=Outgoing, logTag=3):
CallRate: 384
Bonding: On
RemoteNumber 1: “8776”
RemoteNumber 2: “”
RemoteSubAddress: “”
Mute: Off
Microphone: On
Duration: 32
MuteOutgoing: Off
Channels 1 (type=Incoming):
Rate: 384
Restrict: Off
Encryption (status=On):
Type: AES-128
CheckCode: “BA8C78DAD933C3DD”
Audio (status=Active):
Protocol: AAC-LD
Rate: 64
Video 1 (status=Active):
Protocol: H264
Resolution: 2.5SIF
Rate: 317
Video 2 (status=Inactive): /
Data (status=Inactive): /
Channels 2 (type=Outgoing):
Rate: 384
Restrict: Off
Encryption (status=On):
Type: AES-128
CheckCode: “BA8C78DAD933C3DD”
Audio (status=Active):
Protocol: AAC-LD
Rate: 64
Video 1 (status=Active):
Protocol: H264
Resolution: 4CIF
Rate: 317
Video 2 (status=Inactive): /
Data (status=Inactive): /
*s/end

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 176
Status Information – xstatus /xstatus.xml
Call cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

If status = Dialing / Alerting / Proceeding / EstablOut / EstablIn / AwaitInCnf / Connected / Disconnecting / Await2ndnr / ClearOut / ClearIn / Syncing / Capex / Synced / Unframed
and type = Tlph
and protocol = H323 / SIP
and direction = Incoming / Outgoing
and logTag = x
the following will be included:

CallRate: 64

RemoteNumber:

RemoteSubAddress:

IncomingNumber:
Appears for incoming calls only
IncomingSubAddress:

Mute: On / Off

Microphone: On / Off

Duration: 0...

MuteOutgoing: On / Off

Channels [1..2] (type = Incoming / Outgoing):

If type = Incoming / Outgoing the following will be included:

Rate: 64 / .. / 4096

Restrict: On / Off

Encryption (status = Off / Negotiate / On):

If status = Off / Negotiate the following will be included:

<Nothing>

If status = On the following will be included:

Type: DES / AES-128

RSVP*: On/Off

RSVPRate*:

DynamicRate*:

TotalPackets*:

PacketLoss*:

Jitter*:

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 177
Status Information – xstatus /xstatus.xml
Call cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

PacketsDropped*: Appears with incoming calls only

Example:
*s Call 1 (status=Synced, type=Tlph, protocol=H323, direction=Incoming, logTag=5):
CallRate: 64
RemoteNumber: “5020019”
IncomingNumber: “5020059”
IncomingSubAddress: “”
Mute: Off
Microphone: On
Duration: 16
MuteOutgoing: Off
Channels 1 (type=Incoming):
Rate: 64
Restrict: Off
Encryption (status=On):
Type: AES-128
CheckCode: “E2957C90C5DF0649”
Audio (status=Active):
Protocol: G711
Rate: 64
RemoteIPAddress: “”
LocalIPAddress: “10.47.20.59:2334”
Encryption (status=On):
Type: AES-128
RSVP: Off
RSVPRate: 0
DynamicRate: 64
TotalPackets: 725
PacketLoss: 0
Jitter: 0
PacketsDropped: 0
Data (status=Inactive): /
Channels 2 (type=Outgoing):
Rate: 64
Restrict: Off
Encryption (status=On):
Type: AES-128
CheckCode: “E2957C90C5DF0649”
Audio (status=Active):
Protocol: G711
Rate: 64
RemoteIPAddress: “10.47.20.19:2334”
LocalIPAddress: “10.47.20.59:2334”
Encryption (status=On):
Type: AES-128
RSVP: Off
RSVPRate: 0
DynamicRate: 64
TotalPackets: 725
PacketLoss: 0
Jitter: 0
Data (status=Inactive): /
*s/end

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 178
Status Information – xstatus /xstatus.xml
Call cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

If status = Dialing / Alerting / Proceeding / EstablOut / EstablIn / AwaitInCnf / Connected / Disconnecting / Await2ndnr / ClearOut / ClearIn / Syncing / Capex / Synced / Unframed
and type = Vtlph
and protocol = H323 / SIP
and direction = Incoming / Outgoing
and logTag = x
the following will be included:

CallRate: 64 / 128 / .. / 4096

RemoteNumber:

RemoteSubAddress:

IncomingNumber:
Appears for incoming calls only
IncomingSubAddress:

Mute: On / Off

Microphone: On / Off

Duration: 0...

MuteOutgoing: On / Off

Channels [1..2] (type = Incoming / Outgoing):

If type = Incoming / Outgoing the following will be included:

Rate: 64 / .. / 4096

Restrict: On / Off

Encryption (status = Off / Negotiate / On):

If status = Off / Negotiate the following will be included:

<Nothing>

If status = On the following will be included:

Type: DES / AES-128

CheckCode:

Audio (status = Active / Inactive):

If status = Inactive the following will be included:

<Nothing>

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 179
Status Information – xstatus /xstatus.xml
Call cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

If status = Active the following will be included:

Protocol: G711 / G722 / G722.1 / G728 / AAC-LD

Rate:

RemoteIPAddress*:

LocalIPAddress*:

Encryption* (status = On / Off)

If status = Off the following will be included:

<Nothing>

If status = On the following will be included:

Type: DES / AES-128

RSVP*: On / Off

DynamicRate*:

TotalPackets*:

PacketLoss*:

Jitter*:

PacketsDropped*: Appears for incoming calls only

Video [1..2] (status = Active / Inactive):

If status = Inactive the following will be included:

<Nothing>

If status = Active the following will be included:

Protocol: H261 / H263 /H263+ / H264

Resolution: QCIF / SQCIF / CIF / 2CIF / 4CIF / ICIF / SIF / 4SIF /ISIF /VGA / SVGA / XGA / QVGA / 448p / 400p / w288p / w448p / w576p / w720p

Rate:

RemoteIPAddress*:

LocalIPAddress*:

Encryption* (status = On / Off)

If status = Off the following will be included:

<Nothing>

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 180
Status Information – xstatus /xstatus.xml
Call cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

If status = On the following will be included:

Type: DES / AES-128

RSVP*: On / Off

DynamicRate*:

TotalPackets*:

PacketLoss*:

Jitter*:

PacketsDropped*: Appears for incoming calls only

Data (status = Active / Inactive):

If status = Inactive the following will be included:

<Nothing>

If status = Active the following will be included:

Type: LSD/MLP

Protocol: FECC

Rate:

RemoteIPAddress*:

LocalIPAddress*:

Encryption* (status = On / Off)

If status = Off the following will be included:

<Nothing>

If status = On the following will be included:

Type: DES / AES-128

RSVP*: On / Off

DynamicRate*:

TotalPackets*:

PacketLoss*:

Jitter*:

PacketsDropped*: Appears for incoming calls only

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 181
Status Information – xstatus /xstatus.xml
Call cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Example:
*s Call 1 (status=Synced, type=Vtlph, protocol=H323, direction=Incoming, logTag=6):
CallRate: 768
RemoteNumber: “5020019”
IncomingNumber: “5020059”
IncomingSubAddress: “”
Mute: Off
Microphone: On
Duration: 10
MuteOutgoing: Off
Channels 1 (type=Incoming):
Rate: 768
Restrict: Off
Encryption (status=On):
Type: AES-128
CheckCode: “C442803A9A470B7F”
Audio (status=Active):
Protocol: AAC-LD
Rate: 64
RemoteIPAddress: “”
LocalIPAddress: “10.47.20.59:2334”
Encryption (status=On):
Type: AES-128
RSVP: Off
RSVPRate: 0
DynamicRate: 64
TotalPackets: 474
PacketLoss: 0
Jitter: 1
PacketsDropped: 0
Video 1 (status=Active):
Protocol: H264
Resolution: Off
Rate: 704
RemoteIPAddress: “”
LocalIPAddress: “10.47.20.59:2336”
Encryption (status=On):
Type: AES-128
RSVP: Off
RSVPRate: 0
DynamicRate: 677

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 182
Status Information – xstatus /xstatus.xml
Call cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

TotalPackets: 817
PacketLoss: 0
Jitter: 0
PacketsDropped: 0
Video 2 (status=Inactive): /
Data (status=Inactive): /
Channels 2 (type=Outgoing):
Rate: 768
Restrict: Off
Encryption (status=On):
Type: AES-128
CheckCode: “C442803A9A470B7F”
Audio (status=Active):
Protocol: AAC-LD
Rate: 64
RemoteIPAddress: “10.47.20.19:2334”
LocalIPAddress: “10.47.20.59:2334”
Encryption (status=On):
Type: AES-128
RSVP: Off
RSVPRate: 0
DynamicRate: 63
TotalPackets: 475
PacketLoss: 0
Jitter: 2
Video 1 (status=Active):
Protocol: H264
Resolution: 2.5SIF
Rate: 704
RemoteIPAddress: “10.47.20.19:2336”
LocalIPAddress: “10.47.20.59:2336”
Encryption (status=On):
Type: AES-128
RSVP: Off
RSVPRate: 0
DynamicRate: 701
TotalPackets: 936
PacketLoss: 0
Jitter: 6
Video 2 (status=Inactive): /
Data (status=Inactive): /
*s/end

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 183
Status Information – xstatus /xstatus.xml
Camera TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Camera [1..13] (connected = True / False):

Type:

ID:

Pan:

Tilt:

Zoom:

Focus:

Example:
*s Camera 1 (connected=True):
Type: WaveII
ID: “0c0e0006”
SoftwareID: “”
Pan: 647
Tilt: 172
Zoom: 0
Focus: 27501
*s/end

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 184
Status Information – xstatus /xstatus.xml
CameraSWUpgrade TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

CameraSWUpgrade (status = N/A):

Example:
*s CameraSwUpgrade (status=NA): /
*s/end

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 185
Status Information – xstatus /xstatus.xml
CameraTracking TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

CameraTracking (status = On / Off):

If status = On / Off the following will be included:

<Nothing>

Example:
*s CameraTracking (status=Off): /
*s/end

*s CameraTracking (status=On): /
*s/end

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 186
Status Information – xstatus /xstatus.xml
Conference TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Conference (type = Idle / PointToPoint / PointToMultiSite / MultiSite):

If type = Idle the following will be included:

<Nothing>

Example:
*s Conference (type=Idle): /
*s/end

If type = PointToPoint the following will be included:

Calls:

CallRef [1..11]: 1..11

DuoVideo (status = None / Ready / On):

If status = None / Ready the following will be included:

<Nothing>

If status = On the following will be included:

CallRef [1..11]: 0..11

LoudestParticipant:

CallRef: 0..11

Example:
*s Conference (type=PointToPoint):
Calls:
CallRef 1: 1
DuoVideo (status=Ready): /
LoudestParticipant:
CallRef: 1
*s/end

If type = PointToMultiSite the following will be included:

Calls:

CallRef [1..11]: 1..11

DuoVideo (status = None / Ready / On):

If status = None / Ready the following will be included:

<Nothing>

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 187
Status Information – xstatus /xstatus.xml
Conference cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

If status = On the following will be included:

CallRef [1..11]: 0..11

LoudestParticipant:

CallRef: 0..11

NumberOfSites: 1..191

MCUSiteList:

Site [1..191]:

MCUID:

TerminalID:

Name:

CallRef:

LocalSite:

Self:

MCUID:

TerminalID:

OnAir: On / Off

Floor: On / Off

Chair: UnSupported

View:

MCUID:

TerminalID:

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 188
Status Information – xstatus /xstatus.xml
Conference cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Example:
*s Conference (type=PointToMultisite):
Calls:
CallRef 1: 1
DuoVideo (status=None): /
LoudestParticipant:
CallRef: 1
NumberOfSites: 3
MCUSiteList:
Site 1:
MCUID: 85
TerminalID: 3
Name: “Boardroom1”
CallRef: 1
Site 2:
MCUID: 85
TerminalID: 1
Name: “Boardroom2”
CallRef: None
Site 3:
MCUID: 85
TerminalID: 2
Name: “Boardroom3”
CallRef: None
LocalSite:
Self:
MCUID: 85
TerminalID: 3
OnAir: On
Floor: Off
Chair: UnSupported
View:
MCUID: 0
TerminalID: 0
*s/end

If type = MultiSite the following will be included:

Calls:

CallRef [1..11]: 1..11

DuoVideo (status = None / Ready / On):

If status = None / Ready the following will be included:

<Nothing>

If status = On the following will be included:

CallRef [1..11]: 0..11

LoudestParticipant:

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 189
Status Information – xstatus /xstatus.xml
Conference cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

CallRef: 0..11

Floor: None / FloorRequest / FloorAssign

Current:

CallRef: 0..11

Previous:

CallRef: 0..11

OutgoingPicture [1..3] (name = Current / Previous / Duo):

If name = Current / Previous / Duo the following will be included:

Layout (type = Full / 4Split / 5+1Split):

Window [1..6]:

Picture: LocalMain / RemoteMain

CallRef: 0..11

MCUID: 1..

CascadingMode: StandAlone / Master / Slave

NumberOfSites: 1..191

MCUSiteList:

Site [1..191]:

MCUID:

TerminalID:

Name:

CallRef:

LocalSite:

Self:

MCUID:

TerminalID:

OnAir: On/Off

Floor: On/Off

Chair: UnSupported

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 190
Status Information – xstatus /xstatus.xml
Conference cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

View:

MCUID: 1..

TerminalID: 1..

Example
*s Conference (type=Multisite):
Calls:
CallRef 1: 1
CallRef 2: 2
DuoVideo (status=Ready): /
LoudestParticipant:
CallRef: 2
Floor: None
Current:
CallRef: 2
Previous:
CallRef: 1
OutgoingPicture 1 (name=Current):
Layout (type=Full):
Window 1:
Picture: RemoteMain
CallRef: 2
OutgoingPicture 2 (name=Previous):
Layout (type=Full):
Window 1:
Picture: RemoteMain
CallRef: 1
OutgoingPicture 3 (name=Duo):
Layout (type=NA): /
MCUID: 1
CascadingMode: StandAlone
NumberOfSites: 3
MCUSiteList:
Site 1:
MCUID: 1
TerminalID: 2
Name: “john.doe”
CallRef: 1
Site 2:
MCUID: 1
TerminalID: 3
Continues overleaf...

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 191
Status Information – xstatus /xstatus.xml
Conference cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Continued from the previous page:

Name: “john.doe.150”
CallRef: 2
Site 3:
MCUID: 1
TerminalID: 4
Name: “john.doe.mxp”
CallRef: 0
LocalSite:
Self:
MCUID: 1
TerminalID: 4
OnAir: Off
Floor: Off
Chair: UnSupported
View:
MCUID: 1
TerminalID: 3
*s/end

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 192
Status Information – xstatus /xstatus.xml
Ethernet TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Ethernet:

MacAddress:

Speed: 10half / 10full / 100half / 100full

Example:
*s Ethernet:
MacAddress: “00:50:60:01:85:F1”
Speed: 100full
*s/end

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 193
Status Information – xstatus /xstatus.xml
ExternalManager TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

ExternalManager:

Address:

Protocol: HTTP / HTTPS

URL:

Example:
*s ExternalManager:
Address: “10.47.6.75”
Protocol: HTTP
URL: “tms/public/external/management/SystemManagementService.asmx”
*s/end

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 194
Status Information – xstatus /xstatus.xml
ExternalNetwork TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

ExternalNetwork (ready = True / False):

If ready = False the following will be included:

<Nothing>

If ready = True the following will be included:

ExternalClockRate:

Channel (status = Idle / Calling / Answering / Proceeding / Connect / Disconnecting / Disconnected)

If status = Idle the following will be included:

<Nothing>

If status = Calling / Answering / Proceeding / Connect the following will be included:

CallingNumber:

ConnectionTime:

If status = Disconnecting / Disconnected the following will be included:

CallingNumber:

CauseLocation:

ChannelCause:

ConnectionTime:

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 195
Status Information – xstatus /xstatus.xml
FarEndInformation TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

FarEndInformation:

FECC (status = On / Off)

If status = Off the following will be included:

<Nothing>

T140: Off

SString: Off

Example:
*s FarEndInformation:
FECC (status=Off): /
T140: Off
SString: Off
*s/end

If status = On the following will be included:

NumberOfPresets: x

NumberOfSources: x

Source [1..x]:

Name:

Capabilities: “ptzfms”

CurrentSource:

BroadcastSwitch: On / Off

T140: On/Off

Sstring: On/Off

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 196
Status Information – xstatus /xstatus.xml
FarEndInformation cont...
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Example:
*s FarEndInformation:
FECC (status=On):
NumberOfPresets: 15
NumberOfSources: 5
Source 1:
Name: “main cam”
Capabilities: “ptzfms”
Source 2:
Name: “aux”
Capabilities: “ms”
Source 3:
Name: “doc cam”
Capabilities: “ms”
Source 4:
Name: “vcr”
Capabilities: “ms”
Source 5:
Name: “pc”
Capabilities: “ms”
CurrentSource: 1
BroadcastSwitch: On
T140: On
SString: On
*s/end

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 197
Status Information – xstatus /xstatus.xml
Feedback TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Feedback [1..3] (status = On / Off):

If status = Off the following will be included:

<Nothing>

Example:
*s Feedback 1 (status=Off): /
*s/end

If status = On the following will be included:

URL:

Expression [1..15]:

Example:
*s Feedback 2 (status=On):
URL: “http://10.47.6.75/tms/public/feedback/code.aspx”
Expression 1: “/History/Call”
Expression 2: “/Status/Call[@status=’Synced’]”
Expression 3: “/Status/SoftwareUpgrade”
Expression 4: “/Status/BRI”
Expression 5: “/Configuration/Conference/PictureMode”
*s/end

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 198
Status Information – xstatus /xstatus.xml
G703 TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

G703 (ready = True / False)

If ready = False the following will be included:

Layer1Alarm: RedAlarm / YellowAlarm / BlueAlarm

If ready = True the following will be included:

Channel [1..24 / 31] (status = NA / Idle / Calling / Answering / Proceeding / Connect / Disconnecting / Disconnected)

If status = NA / Idle the following will be included:

<Nothing>

If status = Calling / Answering / Proceeding / Connect the following will be included:

CallingNumber:

ConnectionTime:

If status = Disconnecting/Disconnected the following will be included:

CallingNumber:

CauseLocation:

ChannelCause:

ConnectionTime:

Example:

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 199
Status Information – xstatus /xstatus.xml
H323Gatekeeper TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

H323Gatekeeper (status = Required / Discovering / Discovered / Authenticating / Authenticated / Registering / Registered / Rejected / Inactive)

If status = Inactive the following will be included:

<Nothing>

Example:
*s H323Gatekeeper (status=Inactive): /
*s/end

If status = Required / Discovering / Discovered / Authenticating/ Authenticated / Registering / Registered the following will be included:

Alias:
Address:
Port:
Alternates:

Example:
*s H323Gatekeeper (status=Registered):
Alias: “5584582”
Address: “10.47.9.1”
Port: 1719
Alternates:
Server 1:
Address: “10.1.214.87”
Port: 1719
Server 2:
Address: “10.1.214.88”
Port: 1719
*s/end

If status = Rejected the following will be included:

Address:
Port:
Cause:
Alternates:

Example:
*s H323Gatekeeper (status=Rejected):
Address: “10.47.9.1”
Port: 0
Cause: “Duplicate alias”
Alternates: /
*s/end

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 200
Status Information – xstatus /xstatus.xml
IP TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

IP

Address:

SubnetMask:

Gateway:

V6:

Adress [1..2] (type = NA / IPv4 / IPv6):

DNS:

Server [1..5]:

Address:

Domain:

Name:

Example:
*s IP
Address: “10.47.11.179”
SubnetMask: “255.255.248.0”
Gateway: “10.47.8.1”
V6:
Address 1 (type=NA): “”
Address 2 (type=NA): “”
DNS:
Server 1:
Address: “10.0.0.10”
Server 2:
Address: “10.0.0.2”
Server 3:
Address: “”
Server 4:
Address: “”
Server 5:
Address: “”
Domain:
Name: “eu.tandberg.int”
*s/end

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 201
Status Information – xstatus /xstatus.xml
NTP TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

NTP:

Address:

Example:
*s NTP:
Address: “10.0.0.2”
*s/end

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 202
Status Information – xstatus /xstatus.xml
PRI TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

PRI (ready = True / False)

If ready = False the following will be included:

Layer1Alarm: RedAlarm / YellowAlarm / BlueAlarm

Example:
*s PRI (ready=False):
Layer1Alarm: RedAlarm
*s/end

If ready = True the following will be included:

Channel [1..24/31] (type = BChannel / DChannel

status = NA / Idle / Calling / Answering / Proceeding / Connect / Disconnecting / Disconnected)

If type = DChannel and status = NA the following will be included:

<Nothing>

If type = BChannel / DChannel and status = Idle the following will be included:

<Nothing>

If type = BChannel and status = Calling / Answering / Proceeding / Connect the following will be included:

CallingNumber:

ConnectionTime:

If type = BChannel and status = Disconnecting / Disconnected the following will be included:

CallingNumber

CauseLocation

ChannelCause

ConnectionTime

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 203
Status Information – xstatus /xstatus.xml
PRI cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Example:
*s PRI (ready=True):
BChannelsTotal: 8
BChannelsFree: 8
H0ChannelsFree: 1
Channel 1 (type=BChannel, status=Connect):
CallingNumber: “6700”
ConnectionTime: 18
Channel 2 (type=BChannel, status=Idle): /
Channel 3 (type=BChannel, status=Disconnected):
CallingNumber: “6700”
CauseLocation: 1
ChannelCause: 1
ConnectionTime: 0
Channel 4 (type=BChannel, status=Disconnected):
CallingNumber: “08733”
CauseLocation: 0
ChannelCause: 16
ConnectionTime: 120
Channel 5 (type=BChannel, status=Disconnected):
CallingNumber: “08733”
CauseLocation: 0
ChannelCause: 16
ConnectionTime: 120
Channel 6 (type=BChannel, status=Disconnected):
CallingNumber: “08733”
CauseLocation: 0
ChannelCause: 16
ConnectionTime: 120
Channel 7 (type=BChannel, status=Disconnected):
CallingNumber: “08733”
CauseLocation: 0
ChannelCause: 16
ConnectionTime: 120
Channel 8 (type=BChannel, status=Disconnected):
CallingNumber: “08733”
CauseLocation: 0
ChannelCause: 16
ConnectionTime: 120
Channel 9 (type=BChannel, status=Disconnected):
CallingNumber: “08733”
CauseLocation: 0
ChannelCause: 16
ConnectionTime: 120
Continues overleaf

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 204
Status Information – xstatus /xstatus.xml
PRI cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Channel 10 (type=BChannel, status=Disconnected):

CallingNumber: “08733”
CauseLocation: 0
ChannelCause: 16
ConnectionTime: 120
Channel 11 (type=BChannel, status=Disconnected):
CallingNumber: “08733”
CauseLocation: 0
ChannelCause: 16
ConnectionTime: 56
Channel 12 (type=BChannel, status=Disconnected):
CallingNumber: “08733”
CauseLocation: 0
ChannelCause: 16
ConnectionTime: 56
Channel 13 (type=BChannel, status=Disconnected):
CallingNumber: “08733”
CauseLocation: 0
ChannelCause: 16
ConnectionTime: 56
Channel 14 (type=BChannel, status=Disconnected):
CallingNumber: “08733”
CauseLocation: 0
ChannelCause: 16
ConnectionTime: 56
Channel 15 (type=BChannel, status=Disconnected):
CallingNumber: “08733”
CauseLocation: 0
ChannelCause: 16
ConnectionTime: 113
Channel 16 (type=BChannel, status=Idle): /
Channel 17 (type=BChannel, status=Idle): /
Channel 18 (type=BChannel, status=Idle): /
Channel 19 (type=BChannel, status=Connect):
CallingNumber: “6700”
ConnectionTime: 21
Channel 20 (type=BChannel, status=Connect):
CallingNumber: “6700”
ConnectionTime: 20
Channel 21 (type=BChannel, status=Connect):
CallingNumber: “6700”
ConnectionTime: 19
Channel 22 (type=BChannel, status=Connect):
CallingNumber: “6700”
ConnectionTime: 19
Channel 23 (type=BChannel, status=Connect):
CallingNumber: “6700”
ConnectionTime: 18
Channel 24 (type=DChannel, status=NA): /
*s/end

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 205
Status Information – xstatus /xstatus.xml
RemoteSwUpgrade TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

RemoteSwUpgrade (status = NA / Started / Checking / Completed / Aborted / NotValid / RestoringSettings / Failed/WrongPassword / Granted / NoDataLink / WrongFormat / ErrorWrite / WrongReleaseKey / Incompatible / FileToo-
Large / Requesting)

If status = Started the following will be included:

Progress:

Example:
*s RemoteSwUpgrade (status=Started):
Progress: 12
*s/end

If status = NA / Checking / Completed / Aborted / NotValid / RestoringSettings / Failed/WrongPassword / Granted / NoDataLink / WrongFormat / ErrorWrite / WrongReleaseKey / Incompatible / FileTooLarge / Requesting) the following
will be included:

<Nothing>

Example:
*s RemoteSwUpgrade (status=NA): /
*s/end

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 206
Status Information – xstatus /xstatus.xml
Screensaver TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Screensaver (status = On / Off)

If status = On the following will be included:

<Nothing>

Example:
*s Screensaver (status=On): /
*s/end

If status = Off the following will be included:

Timer:

Example:
*s Screensaver (status=Off):
Timer: 37
*s/end

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 207
Status Information – xstatus /xstatus.xml
SIP TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

SIP

Server (status = Inactive / DNSFailed / Timeout / NoConnectionTCP / NoConnectionTLS / Active / Unknown)

If status = Inactive the following will be included:

<Nothing>

If status = DNSFailed / Timeout / NoConnectionTCP / NoConnectionTLS / Active / Unknown

the following will be included:

Address:

Authentication: On/Off

Registration (status = Inactive / Registering / Registered / Deregister / Failed)

If status = Inactive/Registering/Registered/Deregister the following will be included:

URI:

If status = Failed the following will be included:

URI:

Cause:

Example:
*s SIP:
Server (status=Active):
Address: “10.47.8.88”
Authentication:
Registration (status=Registered):
URI: “[email protected]”
*s/end

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 208
Status Information – xstatus /xstatus.xml
SoftwareUpgrade TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

SoftwareUpgrade (status = NA / Started / Checking / Completed / Aborted / NotValid / RestoringSettings / Failed)

If status = Started the following will be included:

Progress:

Example:
*s SoftwareUpgrade (status=Started):
Progress: 12
*s/end

If status = NA / Checking / Completed / Aborted / NotValid / RestoringSettings / Failed the following will be included:

<Nothing>

Example:
*s SoftwareUpgrade (status=NA): /
*s/end

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 209
Status Information – xstatus /xstatus.xml
Switch TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Switch (connected = True / False):

Input:

Format:

Sync:

Sync 1:

Sync 2:

Sync 3:

Sync 4:

Example:
*s Switch (connected=True):
Input: 1
Format: 1280X720p60
Sync: True
Sync 1: True
Sync 2: True
Sync 3: False
Sync 4: False
*s/end

Info: xstatus switch will give information about sync status for the active input, the format, and sync status for all DVI-D inputs. Active input may differ from what is given in the xconfiguration Switch Source
setting. This is because an external control system may also change the input. Information about software version and ID will be given by xstatus camera 1.

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 210
Status Information – xstatus /xstatus.xml
SystemUnit cont...
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

SystemUnit:

ProductType:

ProductId:

Uptime:

Software:

Version:

Name:

ReleaseDate:

Configuration:

Telephony:

VideoTelephony:

TotalBandwidth

ISDNBandwidth:

LANBandwidth:

PresenterOption: True/False

MultisiteOption: True/False

StreamingSupport: True/False

Encryption: True/False

Hardware:

SerialNumber:

MainBoard:

AdditionalBoard:

BootSoftware:

Configuration:

PRI:

BRI:

ExternalNetwork:

VGA:

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 211
Status Information – xstatus /xstatus.xml
SystemUnit cont...
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

DataPorts:

AudioInputs:

Settop: True/False

TV-Standard: PAL/NTSC

TemperatureCelcius:

TemperatureFahrenheit:

Example:
*s SystemUnit:
ProductType: “TANDBERG Codec”
ProductId: “TANDBERG 6000MXP PORTABLE”
Uptime: 10136
Software:
Version: “F4.0Beta2 NTSC”
Name: “s50000”
ReleaseDate: “2005-11-17”
Configuration:
Telephony: 5
VideoTelephony: 5
TotalBandwidth: 6144
ISDNBandwidth: 1920
LANBandwidth: 4096
PresenterOption: True
MultisiteOption: True
StreamingSupport: True
Encryption: True
Hardware:
SerialNumber: “25A00309”
MainBoard: “100670 rev. 05”
AdditionalBoard: “”
BootSoftware: “Rev. 1.12, 2005-10-13”
Configuration:
PRI: 1
BRI: 6
ExternalNetwork: 1
VGA: 2
DataPorts: 2
AudioInputs: 6
Settop: False
TV-Standard: NTSC
TemperatureCelcius: 55
TemperatureFahrenheit: 131
*s/end

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 212
Status Information – xstatus /xstatus.xml
VirtualMonitor TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

VirtualMonitor [1..4]:

Layout (type = Full / 2Split / 2+1Split / 3+1Split / 4Split / 5+1Split, persistent = On/Off):

Window [1..6]:

Picture: LocalMain / LocalDuo / Current /Previous / Duo / RemoteMain / RemoteDuo / JPEG / Still / None

CallRef: 1..11

Example:
*s VirtualMonitor 1:
Layout (type=3+1Split, persistent=Off):
Window 1:
Picture: RemoteMain
CallRef: 1
Window 2:
Picture: Local Main
CallRef: 0
Window 3:
Picture: NA
CallRef: 0
Window 4:
Picture: NA
CallRef: 0
PIP (status=Off): /
*s/end

*s VirtualMonitor 2:
Layout (type=Full, persistent=Off):
Window 1:
Picture: RemoteDuo
CallRef: 1
PIP (status=Off): /
*s/end

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 213
Status Information – xstatus /xstatus.xml
Warning TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Warning [1..10] (status = NA / Active)

If status = NA the following will be included:

<Nothing>

Example:
*s Warning 7 (status=NA): /
*s/end

If status = Active the following will be included:

ID: 101 / 102 / 131 / 132 / 133 / 134 / 161 / 191 / 192 / 193 / 201 / 202 / 203 / 204 / 205 / 206 / 207 / 208 / 301 / 1001 / 1002 / 1003

Value: 1

Example:
*s Warning 1 (status=Active):
ID: 101
Value: 1
*s/end

ID Description
101 Warning BRI 1 Layer 1 Alarm: Line is disconnected
102 Warning BRI 2 Layer 1 Alarm: Line is disconnected
131 Warning PRI Layer 1 Red Alarm: Red alarm or Loss of signal (LOS) means that there is no signal and thus no framing information received (this has the same effect as pulling out the PRI cable)
132 Warning PRI Layer 1 Blue Alarm: Blue alarm indicates that the network on the far side of the CSU is unavailable
133 Warning PRI Layer 1 Yellow Alarm: Yellow alarm or Remote Alarm Indicator (RAI) may indicate a weak or noisy signal or a broken connector in the TX part of the system PRI cable
134 Warning PRI Layer 2 Not Active
161 Warning External Network, No Clock: If no clock is detected you will not be able to place calls
191 Warning G.703 Layer 1 Red Alarm: Red alarm or Loss of signal (LOS) means that there is no signal and thus no framing information received (this has the same effect as pulling out the PRI cable)
192 Warning G.703 Layer 1 Blue Alarm: Blue alarm indicates that the network on the far side of the CSU is unavailable
193 Warning G.703 Layer 1 Yellow Alarm: Yellow alarm or Remote Alarm Indicator (RAI) may indicate a weak or noisy signal or a broken connector in the TX part of the system PRI cable
201 Warning H.323 GateKeeper Rejected: Registration to the GateKeeper has been rejected. Please check GateKeeper setting
202 Warning H.323 GateKeeper Rejected, duplicate alias: GateKeeper registration is rejected because you try to register with an Alias, which is already registered on the GateKeeper
203 Warning H.323 GateKeeper Resources Unavailable
204 Warning H.323 GateKeeper Rejected, invalid alias: The alias you try to register with is not accepted by the GateKeeper
205 Warning H.323 GateKeeper Rejected Security Denial: The GateKeeper rejects registration because the user name and/or password is incorrect
206 Warning H.323 GateKeeper Rejected, Not Reachable
207 Warning H.323 GateKeeper Rejected, No Authenitcation Configuration
208 Warning H.323 GateKeeper Rejected, No Authenitcation Time
301 Warning IP No Net: The system does not detect any IP connection
1001 Warning High Packet Loss
1002 Warning High Jitter
1003 Warning High Packet Drop

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 214
Status Information – xhistory / xhistory.xml
Call TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Call [1..20] type = NA / Tlph / Vtlph

protocol = NA / ISDN / H320 / H323 / SIP
direction = NA / Incoming / Outgoing

If type = NA
and protocol = NA
and direction = NA
the following will be included:

<Nothing>

If type = Tlph / Vtlph

and protocol = ISDN / H320 /H323 / SIP
and direction = Incoming / Outgoing
the following will be included:

LogTag: 1

RemoteNumber:

EncryptionIn: Off/DES/AES-128

EncryptionOut: Off/DES/AES-128

CallRate:

DisconnectCauseValue*:

DisconnectCause*:

Duration:

UptimeAtEndOfCall:

BillingCode:

Audio**: PacketsReceived, PacketsLost, PacketsDropped, DurationLossLevel1, DurationJitterLevel1, NumberOfLevel1Bursts, DurationLossLevel2, DurationJitterLevel2, NumberOfLevel2Bursts

Video**: PacketsReceived, PacketsLost, PacketsDropped, DurationLossLevel1, DurationJitterLevel1, NumberOfLevel1Bursts, DurationLossLevel2, DurationJitterLevel2, NumberOfLevel2Bursts

* Disconnect Cause Overview

The DisconnectCause indicates the reason why the call was disconnected. See DisconnectCause for an overview of the disconnect causes.
The DisconnectCauseValue contains additional information to the DisconnectCause. See DisconnectCauseValue for an overview of the disconnect cause values.

** Packet Loss Levels

Level 1: Packet loss > 5% and Jitter > 100ms
Level 2: Packet loss > 10% and Jitter > 200ms

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 215
Status Information – xhistory / xhistory.xml
Call - DisconnectCause TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

The DisconnectCause may show as a result of the xhistory Call command and indicates the reason why the call was disconnected. See Call for an overview of the xhistory Call command.

• AdaptiveBusy • MasterSlaveFailed • UndefinedReason

• AddativeRegNotSupported • NeededFeatureNotSupported • UnreachableDestination
• AliasInconsisten • NewConnectionNeeded • UnreachableGatekeeper
• BadFormatAddress • NoBandwidth
• CalledPartyNotRegistered • NonStandardReason
• CallerNotRegistered • NoPermission
• CallInProgress • NormalDrop
• CapExchangeFailed • NotAccepted
• CollectDestination • NotBound
• CollectPin • NotCurrentlyRegistered
• DestinationRej • NoUserResponding
• DiscoveryRequired • OutOfLocalResources
• DuplicateAlias • PeerNotResponding
• ExceedsCallCapacity • PermissionDenied
• FacilityCallDeflection • ProxyNeeded
• ForcedDrop • QoSControlNotSupported
• FullRegistrtionRequired • QoSNotSupported
• GatekeeperResources • ReasonUndefined
• GatewayResources • ReasonUnknown
• GenericDataReason • RejectedByRemote
• IncompleteAddress • ReplaceWithConfInvite
• InConf • RequestDenied
• InsufficientResources • ResourceUnavaliable
• InvalidAlias • RouteCallToGk
• InvalidCallSignalAdr • RouteCallToSCN
• InvalidConferenceID • ScurityDenied
• InvalidDestinationURL • SecurityDenial
• InvalidEndpointID • SecurityError
• InvalidPermission • SystemNotReady
• InvalidRASAdr • TerminalExcluded
• InvalidRevision • TransportNotSupported
• InvalidSDP • TunnelledSignalingRej
• InvalidTerminalAlias • Unautorized
• InvalidTerminalName • UndefinedDrop

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 216
Status Information – xhistory / xhistory.xml
Call - DisconnectCauseValue (1:3) TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

The DisconnectCauseValue may show as a result of the xhistory Call com- munication user is temporarily not addressable at any user-network
mand and contains additional information to the DisconnectCause result. Cause No. 6 - Channel Unacceptable interface.
See Call for an overview of the xhistory Call command.
This cause indicates that the channel most recently identified is not
See DisconnectCause for an overview of the disconnect causes. acceptable to the sending party for use in this call. Cause No. 21 - Call Rejected
Cause No. 7 - call awarded, being delivered in an established chan- This cause indicates that the equipment sending this cause does not
Disconnect Cause Codes nel wish to accept this call, although it could have accepted the call be-
You can also find the list of disconnect causes by opening a web browser This cause indicates that the user has been awarded the incoming cause the equipment sending this cause is neither busy nor incompat-
and enter the IP address of the MPS followed by the filename: call, and that the incoming call is being connected to a channel already
causecd.htm. ible. This cause may also be generated by the network, indicating that
established to that user for similar calls (e.g. packet-mode x.25 virtual the call was cleared due to a supplementary service constraint. The
calls). diagnostic field may contain additional information about the supple-
Example:
http://<ip-address>/causecd.htm mentary service and reason for rejection.

http://192.168.10.2/causecd.htm Cause No. 8 - Preemption

This cause indicates the call is being preempted. Cause No. 22 - Number Changed
Cause Codes This cause is returned to a calling party when the called party number
Cause No. 9 - Preemption - Circuit Reserved For Reuse indicated by the calling party is no longer assigned. The new called
Cause No. 1 - Unallocated (Unassigned) Number
This cause indicates that the call is being preempted and the circuit is party number may optionally be included in the diagnostic field. If the
This cause indicates that the destination requested by the calling user
reserved for reuse by the preempting exchange. network does not support this cause, cause no: 1, unallocated (unas-
cannot be reached because, although the number is in a valid format, it
signed) will be used instead.
is not currently assigned.
Cause No. 16 - Normal Call Clearing
This cause indicates that the call is being cleared because one of the Cause No. 26 - Non-Selected User Clearing
Cause No. 2 - No Route To Specified Transit Network
users involved in the call has requested that the call be cleared. This cause indicates that the user has not been awarded the incoming
This cause indicates that the equipment sending this cause has
call.
received a request to route the call through a particular transit network
which it does not recognize. The equipment sending this cause does Cause No. 16/4 or 17 - User Busy
not recognize the transit network either because the transit network This cause is used when the called user has indicated the inability to Cause No. 27 - Destination Out Of Order
does not exist or because that particular transit network, while it does accept another call. This cause code may be generated by the called This cause indicates that the destination cannot be reached because
exist, does not serve the equipment which is sending this cause. user or by the network. Please note that the use equipment is compat- the interface to the destination is not functioning correctly. The signal-
ible with the call. ing message was unable to be delivered due to a hardware failure.

Cause No. 3 - No Route To Destination

This cause indicates that the called party cannot be reached because Cause No. 16/3 or 18 - No User Responding Cause No. 28 - Invalid Number Format (Address Incomplete)
the network through which the call has been routed does not serve the This cause is used when a called party does not respond to a call This cause indicates that the called party cannot be reached because
destination desired. This cause is supported on a network dependent establishment message with either an alerting or connect indication the called party number is not in a valid format or is not complete.
basis. within the prescribed period of time allocated (in Q.931 by the expiry of
either time T303 or T310). Cause No. 29 - Facilities Rejected
Cause No. 4 - Send Special Information Tone (Five One Zero NT) This cause is returned when a facility requested by the user cannot be
This cause indicates that the called party cannot be reached for Cause No. 19 - No Answer From User (User Alerted) provide by the network.
reasons that are of a long term nature and that the special information This cause is used when a user has provided an alerting indication but
tone should be returned to the calling party. has not provided a connect indication within a prescribed period of Cause No. 30 - Response To Status Inquiry
time. Note: This cause is not necessarily generated by the customer This cause is included in the STATUS message when the reason for
premise equipment, but may be generated by internal network timers. generating the STATUS message was the prior receipt of a STATUS
Cause No. 5 - Misdialed Trunk Prefix
This cause indicates the erroneous inclusion of a trunk prefix in the ENQUIRY.
called party number. This number is supposed to be stripped from the Cause No. 20 - Subscriber Absent
dialed number being sent to the network by the customer premises This cause value is used when a mobile station has logged off, radio
equipment. contact is not obtained with a mobile station or if a personal telecom-

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 217
Status Information – xhistory / xhistory.xml
Call - DisconnectCauseValue (2:3) TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Cause No. 31 - Normal, Unspecified indicated in the diagnostic. Cause No. 57 - Bearer Capability Not Authorized
This cause is used to report a normal event only when no other cause in This cause indicates that the user has requested a bearer capability
the normal class applies. which is implemented by their equipment but the user is not authorized
Cause No. 44 - Requested Circuit/Channel Not Available
to use.
This cause is returned when the circuit or channel indicated by the
Cause No. 34 - No Circuit/Channel Available requesting entity cannot be provided by the other side of the interface.
This cause indicates that there is no appropriate circuit/channel Cause No. 58 - Bearer Capability Not Presently Available
presently available to handle the call. Note: If you receive this call, try This cause indicates that the user has requested a bearer capability
Cause No. 46 - Precedence Call Blocked
another data-service, such as dropping from a 64K to 56K data rate. which is implemented by the equipment which generated this cause but
This cause indicates that there are no pre-emptable circuits or that the
which is not available at this time.
called user is busy with a call of equal or higher pre-emptable level.
Cause No. 35 - Call Queued
This cause indicates that the call has been queued for service by the Cause No. 62 - Inconsistency In Outgoing Information Element
Cause No. 47 - Resource Unavailable, Unspecified
next available device. This cause indicates an inconsistency in the designated outgoing ac-
This cause is used to report a resource unavailable event only when no
cess information and subscriber class.
other cause in the resource unavailable class applies.
Cause No. 38 - Network Out Of Order
This cause indicates that the network is not functioning correctly and Cause No. 63 - Service Or Option Not Available, Unspecified
Cause No. 49 - Quality Of Service Not Available
that the conditions are likely to last a relatively long period of time. This cause is used to report a service or option not available event
This cause is used to report that the requested Quality of Service can-
A call that is attempted soon afterwards will most likely not connect only when no other cause in the service or option not available class
not be provided (delay cannot be supported).
successfully. applies.

Cause No. 50 - Requested facility not subscribed

Cause No. 39 - Permanent Frame Mode Connection Out-Of-Service Cause No. 65 - Bearer Capability Not Implemented
This cause indicates that the requested supplementary service could
This cause is included in a STATUS message to indicate that a perma- This cause indicates that the equipment sending this cause does not
not be provided due to user oversight. This cause code is often caused
nently established frame mode connection is out-of-service (e.g. due to support the bearer capability requested.
by the CPE being configured for the wrong switch type.
equipment or section failure) [see Annex A/Q.933].
Cause No. 66 - Channel Type Not Implemented
Cause No. 52 - Outgoing calls barred
Cause No. 40 - Permanent Frame Mode Connection Operational This cause indicates that the equipment sending this cause does not
This cause indicates that because of call screening provided by the
This cause is included in a STATUS message to indicate that a perma- support the channel type requested.
network, the calling user is not permitted to make a call.
nently established frame mode connection is operational and capable
of carrying user information. [see Annex A/Q.933].
Cause No. 69 - Requested Facility Not Implemented
Cause No. 53 - Outgoing Calls Barred Within CUG
This cause indicates that the equipment sending this cause does not
This cause indicates that although the calling party is a member of the
Cause No. 41 - Temporary Failure support the requested supplemental service.
CUG for the outgoing CUG call, outgoing calls are not allowed for this
This cause indicates that the network is not functioning correctly and
member of the CUG.
that the condition is not likely to last a very long period of time. A call
Cause No. 70 - Only Restricted Digital Information Bearer Capability
that is attempted almost immediately afterwards will most likely con- Is Available
nect successfully. Cause No. 54 - Incoming calls barred
This cause indicates that on equipment has requested an unrestricted
This cause indicates that the called user will not accept the call deliv-
bearer service but that the equipment sending the cause only supports
ered in the SETUP message.
Cause No. 42 - Switching Equipment Congestion the restricted version of the requested bearer capability.
This cause indicates that the switching equipment generating this
cause is experiencing a period of high traffic. Cause No. 55 - Incoming Calls Barred Within CUG
Cause No. 79 - Service Or Option Not Implemented, Unspecified
This cause indicates that although the calling party is a member of the
This cause is used to report a service r option not implemented but only
CUG for the incoming CUG call, incoming calls are not allowed for this
Cause No. 43 - Access Information Discarded when no other cause in this class applies.
member of the CUG.
This cause indicates that the network could not deliver access informa-
tion, low layer compatibility, high layer compatibility, or sub-address as

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 218
Status Information – xhistory / xhistory.xml
Call - DisconnectCauseValue (3:3) TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Cause No. 81 - Invalid Call Reference Value This cause indicates that the equipment sending this cause has equipment sending the cause to process the message.
This cause indicates that the equipment sending this cause has re- received a request to establish a call which has low layer compatibility,
ceived a message with a call reference which is not currently in use on high layer compatibility, or other compatibility attributes (e.g. data rate)
Cause No. 100 - Invalid Information Element Contents
the user-network interface. which cannot be accommodated.
This cause indicates that the equipment sending this cause has
received and information element which it has implemented; however,
Cause No. 82 - Identified Channel Does Not Exist Cause No. 90 - Non-Existent CUG one or more fields in the information elements are coded in such a way
This cause indicates that the equipment sending this cause has This cause indicates that the specified CUG does not exist. which has not been implemented by the equipment sending this cause.
received a request to use a channel not activated on the interface for
a call. For example, if the user only subscribed to channels 1 to 12
Cause No. 91 - Invalid Transit Network Selection Cause No. 101 - Message Not Compatible With Call State
and channel 13 through 23 is requested by either side, this cause is
This cause indicates that a transit network identification was received This cause indicates that a message has been received which is incom-
generated.
which is of an incorrect format as defined in Annex C/Q.931 patible with the call state.

Cause No. 83 - A Suspended Call Exists, But This Call Identify Does
Cause No. 95 - Invalid Message, Unspecified Cause No. 102 - Recovery On Timer Expiry
Not
This cause is used to report an invalid message event only when no This cause indicates that a procedure has been initiated by the expiry
This cause indicates that a call resume has been attempted with a
other cause in the invalid class applies. of a timer in association with Q.931 error handling procedures.
call identity which differs from that in use for any presently suspended
call(s).
Cause No, 96 - Mandatory Information Element Is Missing Cause No. 103 - Parameter Non-Existent Or Not Implemented -
This cause indicates that the equipment sending this cause has re- Passed On
Cause No. 84 - Call Identity In Use
ceived a message which is missing an information element which must This cause indicates that the equipment sending this cause has
This cause indicates that the network has received a call resume
be present in the message before that message can be processed. received a message which includes parameters not recognized because
request. The call resume request contained a call identity information
the parameters are not defined or are defined but not implemented by
element which presently does not indicate any suspended call within
the equipment sending this cause.
the domain of interfaces over which calls may be resumed. Cause No. 97 - Message Type Non-Existent Or Not Implemented
This cause indicates that the equipment sending this cause has
received a message with a message type it does not recognize either Cause No. 110 - Message With Unrecognized Parameter Discarded
Cause No. 85 - No Call Suspended
because this is a message not defined of defined but not implemented This cause indicates that the equipment sending this cause has
This cause indicates that the network has received a call resume
by the equipment sending this cause. discarded a received message which includes a parameter that is not
request containing a Call identity information element which presently
recognized.
does not indicate any suspended call within the domain of interfaces
over which calls may be resumed. Cause No. 98 - Message Not Compatible With Call State Or Message
Type Non-Existent Or Not Implemented Cause No. 111 - Protocol Error, Unspecified
This cause indicates that the equipment sending this cause has This cause is used to report a protocol error event only when no other
Cause No. 86 - Call Having The Requested Call Identity Has Been
received a message such that the procedures do not indicate that this cause in the protocol error class applies.
Cleared
is a permissible message to receive while in the call state, or a STATUS
This cause indicates that the network has received a call resume re-
message was received indicating an incompatible call state.
quest. The request contained a call identity information element which Cause No. 127 - Interworking, Unspecified
once indicated a suspended call, however, that the call was cleared This cause indicates that there has been interworking which does not
while suspended (either a network time-out or remote user). Cause No. 99 - Information Element / Parameter Non-Existent Or Not provide causes for actions. The precise cause for a message being sent
Implemented is not known.
This cause indicates that the equipment sending this cause has re-
Cause No. 87 - User Not A Member Of CUG
ceived a message which includes information element(s)/parameter(s)
This cause indicates that the called user for the incoming CUG call is
not recognized because the information element(s)/parameter name(s)
not a member of the specified CUG or that the calling user is an ordi-
are not defined or are defined but not implemented by the equip-
nary subscriber calling a CUG subscriber.
ment sending the cause. This cause indicates that the information
element(s)/parameter(s) were discarded. However, the information
Cause No. 88 - Incompatible Destination element is not required to be present in the message in order for the

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 219
Status Information – xevent /xevent.xml
AuthenticationFailure TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

AuthenticationFailure

Service:

RemoteIPAddress:

Uptime:

Example:
Polling:

*e AuthenticationFailure:
Service: /
RemoteIPAddress: /
Uptime: /
*e/end

Feedback:

*e AuthenticationFailure:
Service: FTP
RemoteIPAddress: “10.47.11.82:1459”
Uptime: 417490
*e/end

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 220
Status Information – xevent /xevent.xml
CallDisconnected TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

CallDisconnected:

CallRef:

LogTag:

Example:
Polling:
*e CallDisconnected:
CallRef: /
LogTag: /
*e/end

Feedback:

*e CallDisconnected:
CallRef: 2
LogTag: 11
*e/end

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 221
Status Information – xevent /xevent.xml
CallSuccessful TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

CallSuccessful:

CallRef:

LogTag:

Protocol:

Direction:

CallRate:

RemoteNumber:

Encryption:

Incoming:

Outgoing:

Example:
Polling:
*e CallSuccessful:
CallRef: /
LogTag: /
Protocol: /
Direction: /
CallRate: /
RemoteNumber: /
Encryption:
Incoming: /
Outgoing: /
*e/end

Feedback:
*e CallSuccessful:
CallRef: 1
LogTag: 12
Protocol: H323
Direction: Outgoing
CallRate: 768
RemoteNumber: “558458”
Encryption:
Incoming: Off
Outgoing: Off
*e/end

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 222
Status Information – xevent /xevent.xml
DownspeedingFinished TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

DownspeedingFinished:

CallRef:

LogTag:

Rate:

Example:
Polling:

*e DownspeedingFinished:
CallRef: /
LogTag: /
Rate: /
*e/end

Feedback:

*e DownspeedingFinished:
CallRef: 3
LogTag: 7
Rate: 384
*e/end

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 223
Status Information – xevent /xevent.xml
MessageBoxResult TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

MessageBoxResult:

Button:

Example:
Polling:

*e MessageBoxResult:
Button: /
*e/end

Feedback:

*e MessageBoxResult:
Button: 1
*e/end

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 224
Status Information – xevent /xevent.xml
PacketlossDownSpeed TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

PacketlossDownSpeed:

CallRef:

LogTag:

Example:
Polling:

*e PacketlossDownSpeed:
CallRef: /
LogTag: /
*e/end

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 225
Status Information – xevent /xevent.xml
SString TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

SString:

Example:
Polling:

*e SString: /
*e/end

Feedback:

*e SString: “Testing SString”

*e/end

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 226
Status Information – xevent /xevent.xml
SystemActivity TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

SystemActivity:

Service:

RemoteIPAddress:

Uptime:

Description:

Example:
Polling:
*e SystemActivity:
Service: /
RemoteIPAddress: /
Uptime: /
Description: /
*e/end

Feedback:

*e SystemActivity:
Service: FTP
RemoteIPAddress: “Unknown”
Uptime: 417995
Description: “get all.prm”
*e/end

Status information followed by a

* will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
D 13887.09
APRIL 2009 227
 Startup Scripts
We recommend that you check out the A startup script runs automatically when starting up the
TANDBERG web site regularly for updated
versions of this manual: codec. With startup scripts you can configure the codec
http://www.tandberg.com/docs individually as well as implement a standard corporate
setup for all codecs.
Startup scripts
How to create and run a startup script TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

When you want the codec to startup with the same configura- Example 1
tion for one or more settings you can create startup script.
The script runs automatically when rebooting the codec.
There may be more than one startup script on the codec. To *P xconfiguration audio volume: 10
ensure the script isn’t run too early during the startup proce- *P xconfiguration autoanswer mode: mute
dure, use the following name on the file startup2.prm *P xconfiguration duovideosource: 5

Create a startup script NOTE! Make sure you remember to

1. Open Notepad and save the file as startup2.prm end the list of commands with a page
2. Enter the text starting with *P <the command> follow by return.
a page return, example:

*P xconfiguration audio volume: 16

<enter a page return>

3. Save and close the file

Upload the file to the codec

• Open a DOS prompt and go to the folder where you saved
the script file named startup2.prm.
Example 2
• Type ftp <ip address of the TANDBERG MXP system> for
example ‘ftp 10.0.8.77’
*P xcommand dial number:12345 callrate:768 netprofile:3
• Type cd user to go this folder
• Type put startup2.prm and press Enter. The script file
will now be uploaded to the TANDBERG MXP system. You can also use xCommand instruc-
tions in the startup script.
• Type dir to verify the upload of the file
• Exit the DOS window.

Run the startup script

• Restart the TANDBERG MXP system to run the startup
script.

D 13887.09
APRIL 2009 229
 Controlling External Cameras
We recommend that you check out the Assume you have your cameras connected to an external
TANDBERG web site regularly for updated
versions of this manual: control system, and that you want to be able to control
http://www.tandberg.com/docs these cameras using the TANDBERG remote or from the
remote site using FECC (Far End Camera Control). To do
this you will need to make use of the Extcam Protocol.
This section of the Reference User Guide explains
Extcam Protocol Basics as well as how to interface to the
TANDBERG WAVE II camera and the TANDBERG Precision
HD camera.
Controlling External Cameras
Extcam Protocol Basics TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

A ssume you have your cameras connected

to an external control system, and that you
want to be able to control these cameras using
Example: extcam on source=4
This tells the far end that your control system
by the internal camera driver. If you have start-
ed extcam with the source=<n> option, these
capabilities and names will probably not match
The extswitch
The extswitch is used to inform the far
has four sources. If a far end video switch end that you have switched video source with
the TANDBERG remote or from the remote site command is received, it will be routed to the with what you have in your control system.
your control system. Extcam must be started
using FECC (Far End Camera Control). So, when you use the source=<n> option,
telnet/serial port as follows: with the source=<n> option for this to be
The control system issues the following com- *C vs 1 m the names and capabilities specified by the meaningful.
mand on a telnet session or on a serial port extname and extcap commands will be used
Meaning that the far end wants to switch to Example: Assume you have two sources con-
connection: instead.
video source 1, with m – motion video. nected to your control system:
extcam on Readers of the original documentation† may
Note! The source option affects video switch extcam on source=2
Now, when you select a video input with no recall that it stated that extcap and ext-
commands received over FECC only. name will output the normal codec settings if You do a local switch to the 2nd source on
codec controllable camera connected, the xConfiguration MainVideoSource etc. extcam is off, ie. extname will function as your control system, and we inform the far end
following commands will be output to the tel- commands are not affected by this, so you are vidname. This is not correct! so it can show information about the selected
net/serial port when you attempt to control the still able to do local switching as you want. source and use correct capabilities:
camera with the TANDBERG remote: However, the list will be limited to the number
of entries given the last time you started extswitch 2
*C <direction> start
*C <direction> stop
Far End Preset Switching extcam with the source option. This is not very The extswitch is also used to confirm that
The far end may also request that a preset obvious. To keep the control system compatible a far end video switch command has been
where <direction> is with different software versions, it is recom-
should be displayed or stored. Since activating properly executed. Failure to reply to a FECC
le for left a codec preset can trigger a video switch, the mended to start extcam first with the number video switch with an extswitch means that
ri for right preset commands can also be routed to the tel- of sources you need, then specify names and the far end will probably assume that no video
up for up net/serial port. Use the pres=<0..15> option capabilities. switch was executed, and continue to use the
do for down to specify this. This option can be combined Example: We have three external video same capabilities and name as the previously
z+ for zoom in with the source option. sources/cameras: selected source.
z- for zoom out
Example: extcam on pres=6 extcam on source=3 Example: Assuming same setup as under
These commands can be parsed by the control extcap/extname and that the far end requests
This tells the far end that you have 6 selecta- We give them custom names:
system and passed on to external cameras as a video change to the DVD source:
ble presets. If a far end preset command is
needed. extname 1 “Front”
received, it will be routed to the telnet/serial * C vs 3 m
Note! For all practical purposes, a start will extname 2 “Document”
port: We change video source in our control system
always be followed by a stop before a new extname 3 “DVD”
*C pa 1 and confirm the change:
movement is allowed. And correct capabilities. “Front” is a full
Meaning that far end wants to activate preset featured camera. “Document” is a document extswitch 3
1 . If the command is ps it wants to store a camera with only zoom. “DVD” is a DVD player. The far end will now know that we are using the
Far End Video Source Switching preset at the given position.
extcap 1 ptzfms DVD source, and should not send any move-
Things get slightly more complicated if you ment commands. The far end may elect to
Note! The pres option affects preset com- extcap 2 zms
need to control all types of video switching in display the source name too.
mands received over FECC only. extcap 3 ms
the codec. The control system does this easily xCommand PresetActivate, Preset-
for the local end, but what about video switch If you make a call, the far end should only list
Store, PresetClear etc. commands are † The original documentation is the TANDBERG 770-
requests from the far end in a call? If you are three possible video sources, with names
not affected by this. 8000MXP Dataport User Guide, which is available separately.
not running extcam, or just issued an extcam as specified. If you select the second video
on command, a far end video switch will cause source, far end should not allow any movement
the codec to change video source. The extcap and the extname other than zoom.
So, how can we route far end video switch com- When you make a call, the codec will send out Note! Do not rely on this. The control system may
mands to the control system? The control system a camera/video source capset consisting of still receive movement commands, even if you
does this by passing the source=<0..9> option video source names as specified by the vid- have no movement specified in the capset. Be
to the extcam command: name command and capabilities as detected sure to ignore commands that you don’t expect!

D 13887.09
APRIL 2009 231
Controlling External Cameras
Interfacing to the TANDBERG WAVE II Camera TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

The TANDBERG WAVE II camera uses a RS-232 control interface responses (messages) have the following format: Command and Response Exchange Sequence
that resembles the Sony VISCA protocol. Address byte (1) - Information bytes (1..14) - Terminating byte (1) When the camera receives a command, it responds with either an
The minimum length of any command or response is 3 bytes. ACKNOWLEDGE response, a COMPLETION response or an ERROR
RS232 Parameters 1. Address byte: Let us assume there is one host, i.e. the Codec
response:
The communication parameters for the RS232 interface must be (the host is the unit controlling the camera). The host has address • ACK message: 90-4Y-FF
set to: 0. The four least significant bits of the address byte contain the Returned by camera when it receives the command. No ACK is
• 9600 bits per second address of the receiver. In the case of a broadcast message, the returned for inquiries.
• 8 databits receiver address should be set to 8. When we are operating a • Completion message: 90-5Y-FF (commands) & 90-5Y-…-FF
• No parity single camera, the address is 1. Hence, address bytes in mes- (inquiries)
• 1 stopbit sages from the host are 0x81, and messages from the camera to Returned by the camera when execution of commands and
• No hardware flow control the host are 0x90 (the protocol allows for up to 7 cameras). inquiries are completed.
• No software flow control 2. Message bytes: Any number of bytes containing the actual mes- • Error packets: 90-6Y-…-FF
These parameters are fixed, and are not user configurable. All sage information. Bytes may have any value in the range 0...254. When command or inquiry failed to be executed.
databytes are pure binary information, i.e. the data is not ASCII- The value 255 (i.e. hexadecimal FF) is reserved for the terminating
• Y = socket number
encoded. byte.
Camera contains two buffers so that two commands, including
3. Terminating byte: All messages must be terminated with a byte the commands being executed, can be received.
Message Format containing all 1’s, i.e. decimal 255 (or hexadecimal FF).
There are of course exceptions to these rules:
Commands are initiated from the host (i.e. the codec or any other • An Initialize message will respond as indicated in the table
external controller) to the camera. After a camera has been issued below (this message is in fact a broadcast message, and any
a command, the camera will generate a response. Commands and unit other than the host receiving a broadcast message must
pass it on).

D 13887.09
APRIL 2009 232
Controlling External Cameras > Interfacing to the TANDBERG WAVE II Camera
Commands TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Command Message Comment

Autofocus on 81 01 04 38 02 FF

Manual focus on 81 01 04 38 03 FF

Focus in start 81 01 04 08 02 FF

Focus out start 81 01 04 08 03 FF

Focus stop 81 01 04 08 00 FF

Focus direct 81 01 04 48 0p 0q 0r 0s FF pqrs: focus position, far 4096 –near 40960

Focus inquiry 81 09 04 48 FF Response: 90 50 0p 0q 0r 0s FF pqrs: focus position

Zoom in start 81 01 04 07 3p FF p: speed parameter, low 0 - high 7

Zoom out start 81 01 04 07 2p FF p: speed parameter, low 0 - high 7

Zoom stop 81 01 04 07 00 FF

Zoom direct 81 01 04 47 00 0q 0r 0s FF qrs: zoom position, 0 – max 1023

Dzoom off 81 01 04 06 03 FF

Zoom inquiry 81 09 04 47 FF Response: 90 50 00 0q 0r 0s FF qrs: zoom posistion

Tilt up start 81 01 06 01 0p 0t 03 01 FF p: pan speed, t: tilt speed, low 0 – high 7

Tilt down start 81 01 06 01 0p 0t 03 02 FF

Pan left start 81 01 06 01 0p 0t 01 03 FF

Pan right start 81 01 06 01 0p 0t 02 03 FF

Pan/tilt stop 81 01 06 01 03 03 03 03 FF

Pan/tilt direct 81 01 06 02 0p 0t 00 0x 0y 0z 00 00 0u 0v FF p: pan speed, t: tilt speed xyz: pan position, left 1295 - centre 647 - right 0 uv: tilt position, up 248 - centre 172 - down 0

Pan/tilt home 81 01 06 04 FF

Pan/tilt inquiry 81 09 06 12 FF Response: 90 50 00 0x 0y 0z 00 00 0u 0v FF, xyz: pan posistion uv: tilt position

Preset store 81 01 04 3F 01 0p FF p: preset number, 1-15

Preset activate 81 01 04 3F 02 0p FF p: preset number, 1-15

Preset inquiry 81 09 10 0p FF Response: 90 50 00 0x 0y 0z 00 00 0u 0v 00 0q 0r 0s FF, p: preset numer, xyz: pan position, uv: tilt position, qrs: zoom position

AE auto 81 01 04 39 00 FF AE: Automatic Exposure

AE manual 81 01 04 39 03 FF

D 13887.09
APRIL 2009 233
Controlling External Cameras > Interfacing to the TANDBERG WAVE II Camera
Commands cont... TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Command Message Comment

Bright exp on 81 01 04 3E 02 FF

Bright exp off 81 01 04 3E 03 FF

Bright exp inc 81 01 04 0E 02 FF

Bright exp dec 81 01 04 0E 03 FF

Bright exp reset 81 01 04 0E 00 FF

WB auto 81 01 04 35 00 FF WB: White Balance

WB manual 81 01 04 35 05 FF

WB one push 81 01 04 10 05 FF

Backlight on 81 01 04 33 02 FF

Backlight off 81 01 04 33 03 FF

Shutter Reset 81 01 04 0A 00 FF

Shutter Up 81 01 04 0A 02 FF

Shutter Down 81 01 04 0A 03 FF

Gain Reset 81 01 04 0B 00 FF

Gain Up 81 01 04 0B 02 FF

Gain Down 81 01 04 0B 03 FF

Bright Reset 81 01 04 0D 00 FF

Bright Up 81 01 04 0D 02 FF

Bright Down 81 01 04 0D 03 FF

IR on 81 01 06 08 02 FF

IR off 81 01 06 08 03 FF

LED on 81 01 33 01 01 FF

LED off 81 01 33 01 00 FF

ID Inquiry 81 09 04 22 FF Response: 90 50 zz xx 00 yy FF zz xx=camera rev, yy=firmware rev

Network initialize 88 30 01 FF Response: 88 30 xx FF xx=(1+number) of cameras in chain

IF clear 88 01 00 01 FF Clears buffer & cancels current command

D 13887.09
APRIL 2009 234
Controlling External Cameras
Interfacing to the Precision HD Camera TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

This document describes how to communicate with the Precision Identification Directly changing the gain value is currently not supported.
HD camera using the VISCA protocol. The Wave 2 interface was The Wave 2 identification command, CAM _ Id _ Inq, is sup- Use the new CAM _ Bright _ Direct command to select a
specified on the previous pages. The Precision HD camera uses ported by the camera. Byte 2 in the reply, counting from 0, will be certain Iris/Gain combination when brightness is in manual mode.
the same interface, with the major differences specified below. 0x0f if this is a PrecisionHD camera.
To find out which software the camera is running, use the CAM _ Whitebalance
Connecting to the Camera Swid _ Inq inquiry command. Note that this inquiry can produce Whitebalance supports auto and manual settings. Currently one
If you intend to use the HDMI output of the camera only, you can a reply up to 128 bytes long. push mode and direct r/b-gain settings are not supported.
use the normal RJ45 connector to communicate with the camera Manual mode is enabled by issuing the CAM _ WB _ Man com-
using VISCA. Focus mand. The CAM _ WB _ Direct command is used to set the
In most cases, however, you probably want to use the high speed Autofocus will automatically be disabled when it locks. So you have value.
serial connection for best image quality. When the camera is oper- to issue a new “Autofocus on” command each time you start a
ated in this mode, you cannot separate the control pins for use in pan/tilt/zoom move. For best results, also issue an “Autofocus on” Gamma
an external control system, since the codec will send important when you stop a move, in case autofocus was locked while moving.
video control commands as VISCA messages over this connection. You may specify which gamma table to use by issuing the CAM _
Gamma _ Set command.
To overcome this problem, you can convert the daisy chain RJ11 Presets
connector on the camera to an extra VISCA control port with the Preset commands are currently not supported. The camera will not
following command: Other
store or activate any presets.
xconfiguration Camera 1 DualVisca: On The camera may be rebooted by issuing a CAM _ Boot command.
Use the CAM _ PTZF _ Set command to directly set the position
The RJ11 connector will then provide a full featured VISCA inter- in one operation.
face.
Brightness, Iris, Gain
Differences from the Wave II Camera
New Commands and Inquiries
Ranges
Command/Inquiry Packet Result/Comments
Pan range is 0..816.
Tilt range is 0..89. CAM_Id_Inq 8x 09 04 22 FF Result: y0 50 pp qq 00 rr FF
Zoom range is 0..2768. pp qq= camera rev
Focus range is 4096..4246. rr= firmware rev
pp = 0x0f for PrecisionHD
Movement Speed CAM_Swid_Inq 8x 09 04 48 FF Result: y0 50 [max 125 bytes of ascii text] ff
The camera does not automatically adjust movement speed CAM_PTZF_Set 8x 01 37 0p 0q 0r 0s 0t 0u 0v 0w 0x 0y 0z 0a ff pqr = pan, st = tilt, uvw= zoom, xyza=focus
depending on zoom level. It is suggested that you use the following
speed values when moving the camera:
CAM_Bright_Direct 8x 01 04 4d 0p 0q 0r 0s ff pqrs = brightness value, range 0..31
Zoom Level Pan Speed Tilt Speed
CAM_WB_Man 8x 01 04 35 05 FF Set manual whitebalance mode. Specify value with CAM_
0..922 6 7
WB_Direct.
923..1845 3 5
CAM_WB_Direct 8x 01 04 75 0p 0q 0r 0s ff pqrs = whitebalance value, range 0..16
1846..2768 1 3
CAM_Gamma_Set 8x 01 3a 0p 0q 0r 0s ff pqrs = gamma table to use, range 0..7
CAM_Boot 81 01 42 ff Reboot the camera.

D 13887.09
APRIL 2009 235
 TANDBERG Video Switch
We recommend that you check out the The TANDBERG Video Switch (TVS) is a rack-mountable
TANDBERG web site regularly for updated
versions of this manual: hardware option for TANDBERG 6000 MXP and 3000 MXP
http://www.tandberg.com/docs codecs that delivers the ability to daisy chain multiple HD
cameras and provides support for third party HD cameras.
This section of the Reference User Guide explains the
TANDBERG Video Switch basics as well as how to set up
different daisy chained solutions.
TANDBERG Video Switch
Unpacking the Video Switch TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

The TANDBERG Video Switch set contains: Cameras

1 Video Switch Unit You may combine TANDBERG HD Precision cameras with analog sources equipped with
4 Rubber Feet component video outputs. Just add them to the chain of cameras in the diagram shown overleaf,
but make sure the added sources appear after the TANDBERG HD Precision cameras in the chain
1 HD Camera cable (1 m) for 6000MXP Codec (i.e. after camera 4 in the diagram overleaf).
1 HD Camera cable (1 m) for 3000MXP Codec Consequently, up to four TANDBERG HD Precision cameras may be combined with up to two
1 Power supply kit incl. cables for Video Switch analog component video sources and up to three TANDBERG WAVE II cameras, bringing the
1 Power supply kit incl. cables for existing camera maximum number of video sources (which in many cases will be all cameras) up to nine!
1 Rack ear set (left and right)
1 Control cable (6.5 m) for Video Switch to Precision HD camera
1 HDMI cable (6.5 m) for Video Switch to precision HD camera
1 TRC4 TANDBERG Remote Control
Please report any discrepancies immediately.

Mount the rack ears

1 Unpack the unit.
2 and/or rubber feet
and mount it in the
rack, if applicable.
Put the Video Switch power
supply here when rack
mounting.

Rubber feet
(rubber pads)

D 13887.09
APRIL 2009 237
TANDBERG Video Switch
Connecting the Video Switch (I) TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

3 Connecting up to four
TANDBERG Precision
HD cameras:

Camera 2 Camera 3 Camera 4

RJ11 – RJ45

RJ11 – RJ45

RJ11 – RJ45
   

Primary chain
 Connect TANDBERG Video

DB 9–RJ 45
Switch power supply here.
RJ 45 – DB 9

 Connect camera power

supply here.
 TANDBERG Video Switch

DVI – HDMI

DVI – HDMI

DVI – HDMI

2. Aux Video in PC DVI-I in Audio in

3. Doc 4. VCR
PC Card
I 3 4 1 2
Ethernet
Camera
Data Video out DVI-I out VCR

1 2
1. Single 2. Single 3. Dual Mic.1 Mic.2
O DC in USB Audio out Net

TANDBERG 6000 MXP Codec TANDBERG 3000 MXP Codec

DB 9 – RJ 45

To upgrade the software of the Precision HD camera, connect the

camera directly to the main camera socket of the Codec (the socket that
otherwise is used when connecting the Video Switch to the Codec).
The Codec must be equipped with RJ45–DB9 pinout is described in Camera Socket RJ11-RJ45 is described
software version F6.1 or higher to sections for Codec 3000 MXP and Codec 6000 MXP. on the next page. Power the units and the upgrade will start automatically. The status will
support the use of the Video Switch. be shown on the video system’s monitor.

D 13887.09
APRIL 2009 238
TANDBERG Video Switch
Connecting the Video Switch (II) TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

4 This diagram shows the additional connections needed to expand from using up to four TANDBERG
Precision HD cameras (see previous page) to also include up to three TANDBERG WAVE II cameras
(i.e. up to seven cameras in total). Connect Video Switch power supply as shown overleaf.

Note!  Connect WAVE

Start by connecting the Camera 1 Camera 2 Camera 3 camera power
Precision HD cameras as supply here.
shown on the previous page.
The connection shown here
comes in addition to the one
on previous page! RJ 11 – RJ45  RJ 11 – RJ45 
RCA – RCA
 RCA – RCA

S-video – S-video

RJ 45 – DB 9 RJ 45 – DB 9
Secondary chain

TANDBERG 6000 MXP Codec

TANDBERG RJ 45 – RJ 11

1 8 1 8

2. Aux Video in
3. Doc 4. VCR
PC DVI-I in Audio in RJ45 RJ11
PC Card
3 4 1 2
I
Ethernet Top Top
Camera
Data Video out DVI-I out VCR

1 2
1. Single 2. Single 3. Dual Mic.1 Mic.2
O DC in USB Audio out Net

TANDBERG 3000 MXP Codec

RJ45 RJ11
Front Front
1 8 1 6

1 2
2 1
3 3
The Codec must be equipped with RJ45–DB9 pinout is described in Camera Socket RJ45
6 4
RJ11

software version F6.1 or higher to sections for Codec 3000 MXP and Codec 6000 MXP. 7 5

support the use of the Video Switch.

D 13887.09
APRIL 2009 239
TANDBERG Video Switch
Connecting the Video Switch (III) TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

5 This diagram shows the connections needed to use a maximum of two analog sources equipped with
component video outputs. Connection diagram uses Sony EVI-HD1 cameras as example. System supports
1280X720p50, 1280X720p59,94, and 1280X720p60 only. For full VISCA control Sony EV1-HDI cameras
or true compatibles must be used. Other units may or may not be partly or fully controllable. Connect Video
Switch power supply as shown overleaf.

Mini DIN – Mini DIN

 Connect camera power

supply here.
Camera 1 Camera 2

Control
Control in
in


RCA – RCA

 RCA – RCA
DB 9– Mini DIN

RJ 45 – DB 9

SONY Mini DIN Precision HD RJ 11

TANDBERG 6000 MXP Codec
1 DTR 1 GND
2 DSR 2 Not Used
3 TXD 3 TXD
2. Aux Video in PC DVI-I in Audio in
3. Doc 4. VCR
PC Card
I 3 4 1 2
Ethernet
Camera
Data Video out DVI-I out VCR

O DC in USB 1. Single 2. Single 3. Dual

1
Audio out
2
Mic.1 Mic.2
Net 4 GND 4 RXD
TANDBERG 3000 MXP Codec 5 RXD 5 GND
6 GND 6 GND

The Codec must be equipped with RJ45–DB9 pinout is described in Camera Socket
SONY Part Numbers: DB9–Mini DIN cable Mini DIN–Mini DIN chain cable
software version F6.1 or higher to sections for Codec 3000 MXP and Codec 6000 MXP.
SONY part number RC893 SONY part number RC815
support the use of the Video Switch.

D 13887.09
APRIL 2009 240
TANDBERG Video Switch
Installation of the Video Switch TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Basic Functionality Since the switch is the first entry in both chains, there is a max of 6 Command Interface – New Commands
cameras per chain. This numbering scheme will be as compatible as
Physical inputs refer to explicit codec input and explicit switch input. Important: All camera commands will get new ranges, Camera
possible with existing camera support. We open up for the possibility
These can only be controlled from the command interface. The com- [1..13] instead of Camera [1..4] . This will work as specified in the
to chain more cameras than 4 in the secondary chain. This will also
mands xconfiguration MainVideoSource, vidin and xconfiguration section above.
be possible when the switch is not connected.
Switch Source always control the inputs directly.
The new commands below are also useful if there is no switch con-
Example: To select physical input 3 on the codec, use xconfiguration xconfiguration Preset [1..15] SwitchVideoSource <0..6> nected.
MainVideoSource: 3, as usual. To see inputs on the switch, select co- Will switch the TANDBERG Video Switch to the given input when the
dec input 1 with xconfiguration MainVideoSource: 1 and select switch preset is activated. xcommand CameraReconfigure
input with xconfiguration Switch Source <1..6>.
Re-configures all cameras connected to the switch or codec. This may
Logical inputs are used when accessing inputs from the menu, re- xconfiguration MainVideoSource/DuoVideoSource <1..6> be useful if you connect new cameras without turning the power off,
mote control and FECC. There are five input buttons on the top of Will not be changed. 1 will mean current input on the switch. since the switch does not auto detect such changes.
the TRC4 remote control, and these can be remapped to any switch
input you wish. The same five buttons are visible in the Presentation/ xconfiguration switch source: <1..6> xcommand CameraUpgrade <1..13> <filename>
Main Video menu, and these will be remapped in the same manner. If Upgrade camera or switch with new software. The software must
Specify which input source to use on the switch. This will only cause a
the switch is connected with no special configuration, selecting “main be put on either /tmp or /user. Camera software files are named
visible change if MainVideoSource is 1.
cam” in the menu will give the current input on the switch. s01692.pkg. Switch software files are named s51200.pkg. Currently
Example: There are two cameras connected to the switch, which we xconfiguration switch config primary: <on/off> only upgrading of the first camera/switch is supported.
want to access from the menu and remote using the “main cam” and
Default is on. If off, the codec will only do a basic setup of the primary
“aux” buttons:
chain and report what kind of cameras are connected. The codec will New Status
xconfiguration Switch LogicalInput 1 Mode: On not set up brightness, whitebalance, gamma etc. for each camera.
xstatus switch
xconfiguration Switch LogicalInput 1 Map: 1 Turn it off if an external control system handles all the configuration.
xconfiguration Switch LogicalInput 2 Mode: On Information about software version and ID will be given by xstatus
xconfiguration Switch LogicalInput 2 Map: 2 camera 1. xstatus switch will give information about sync status for
xconfiguration switch config secondary: <on/off>
the active input, the format, and sync status for all DVI-D inputs.
You can rename the inputs using the standard xconfiguration Vid- Default is on. If off, the codec will only do a basic setup of the second-
eo Inputs Source <1..6> Name or video name: ary chain and report what kind of cameras are connected. The codec xstatus switch
xconfiguration Video Inputs Source 1 Name: “HD Camera 1” will not set up brightness, whitebalance, gamma etc. for each camera.
*s Switch (connected=True):
xconfiguration Video Inputs Source 2 Name: “HD Camera 2” Turn it off if an external control system handles all the configuration.
Input: 1
Format: 1280X720p60
Note: If you select a switch input that has no mapping from the xConfiguration Switch LogicalInput [1..5] Mode: <On/Off> Sync: True
command interface, it will be called Switch-<1..6>. If you select a xConfiguration Switch LogicalInput [1..5] Map: <1..6> Sync 1: True
codec input that has been remapped to the switch from the com- Sync 2: True
Default is LogicalInput [1..5] Mode: Off.
mand interface, it will be called Codec-<1..5>. Sync 3: False
1. Main cam Sync 4: False
2. Aux
Command Interface – Configurations 3. Doc cam Active input may differ from what is given in the xconfiguration Switch
Important: All camera configurations will get new ranges, Camera 4. VCR Source setting. This is because an external control system may also
[1..13] instead of Camera [1..4]. These will behave as follows if a 5. PC change the input.
switch is connected: Remaps the source buttons on top of the extended remote control.
Will also remap inputs selected from the menu, and change FECC ac-
• 1 will be the switch.
cordingly. If mode for a key is on, the table entry will be used to specify
• 2..7 will be cameras connected to secondary chain (chain origi- which input on the switch to activate.
nating from Data port 2 of the switch).
• 8..13 will be cameras connected to the primary chain (chain
originating from Data port 1 of the switch).

D 13887.09
APRIL 2009 241
TANDBERG Video Switch
Communicating with the Video Switch TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Communicating Using VISCA This article covers the use of port 3 as the control VISCA Standard Commands
port for the switch. You may use port 0 if you do
Note! This section applies only to users wanting to
not intend to use the THSI interface, but only use Command Set Command Packet Comments
control the switch directly from an external control
HDMI out.
system connected to Data port 3 on the switch.
CAM_IF_Clear 8x 01 00 01 ff Clear command buffer. Stop any current
The following describes how to communicate with the operation in progress.
TANDBERG Video Switch using the VISCA protocol. Enhanced VISCA
For details about the protocol implementation, refer Since the switch has two possible camera chains, all CAM_Address_Set 8x 30 0p ff p = address for this device. If x=8 (broad-
to the System Integrators Guide – Interfacing to the normally formatted commands will be sent to the pri- cast), increase p with 1 before sending
TANDBERG Wave 2 Camera. mary chain. To access the secondary chain, you must to chain.
first turn Enhanced VISCA on with the SW_eVisca
command. CAM_Command_Cancel 8x 2p ff p = Socket ID. Not supported in TVS
VISCA Interface Basics
Commands going to the secondary chain must be CAM_Power 8x 01 04 00 0p ff p = 2: Power on. p = 3: Power off.
The TANDBERG Video Switch (TVS) uses a RS-232
prefixed with FE 01. Replies from the secondary
control interface that resembles the Sony VISCA
chain will also be prefixed with FE 01. You will only
protocol.
receive push messages from the secondary chain if VISCA Standard Inquiries
TVS is configured in exactly the same way as a Enhanced VISCA is turned on.
VISCA camera. TVS will always be located first in the Command Command Packet Comments
Important: Since the switch can receive VISCA from
camera chain(s).
either the codec or an external control system, and
The main jobs of the VISCA interface in the TVS are: IF_DeviceType_Inq 8x 09 00 02 ff y0 50 gg gg hh hh jj jj kk ff
since there are two possible camera chains, there
gggg = Vendor ID
• Select which video source to use are limitations on how commands are issued and
hhhh = Model ID
• Route VISCA messages to the connected cam- answered:
jjjj = ROM Revision
eras • Only one command can be processed at a time kk = Max sockets
• Control picture resolutions sent to the codec • Sending a new command when you receive an (No support for this in the TANDBERG
Cameras chained to the switch will start with id 2. ACK from a Sony camera is not allowed. ACK mes- Video Switch. Ignore it.)
The codec will automatically recognize this and map sages will be thrown away by the switch
CAM_Power_Inq 8x 09 04 00 ff y0 50 0p ff
the cameras accordingly. • Reply will always go to the source that issued the p = 2: Power on.
command.
p = 3: Power off.
VISCA Serial Ports • Sony push messages will be sent to both
sources.
The switch has a total of 4 serial ports that communi- VISCA Standard Push Messages
cate using the VISCA protocol. If this is not expected behaviour, an external control
system may, of course, be setw to control all con-
• Port 0, on the THSI interface, is always connected nected cameras directly via VISCA. Command Command Packet Comments
to the codec.
• Port 1 is the primary VISCA chain for cameras CAM_Network_Change x0 38 ff This indicates that cameras have been
connected to the Switch. VISCA Messages added to or removed from the camera
Commands that are prefixed with SW_ are new for chain.
• Port 2 is the secondary VISCA chain for the To avoid issues with (some) Sony cam-
cameras that normally are connected to codec the switch. The CAM_ prefix is used for commands
that are copied from TANDBERG Precision HD Cam- eras, the control system or codec should
video inputs 2-5. See the section on Enhanced
era, or are standard VISCA messages. delay 9 seconds before reconfiguring the
VISCA below.
chain.
• Port 3 is intended for external control systems,
and works in the same way as port 0, but with
some limitations on available commands. It is
comparable to running the daisy port on a TAND-
BERG Precision HD Camera in dualvisca mode.

D 13887.09
APRIL 2009 242
TANDBERG Video Switch
Communicating with the Video Switch TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Configuration Commands Inquiries

Messages starting with 8x-01-40-<00..1f> are configuration commands. Messages starting with 8x- 09...

Command Command Packet Comments Command set Command Packet Reply and comments

SW_Port_0_Cfg 8x 01 40 00 ... ff Currently not in use. CAM_ID_Inq 8x 09 04 22 FF Reply: 90 50 zz xx 00 yy FF

zz xx = switch rev, zz=0x40 for TVS
SW_Port_1_Cfg 8x 01 40 01 ... ff Currently not in use.
yy = firmware rev
SW_Port_2_Cfg 8x 01 40 02 0p ff p=0: Disable this port
CAM_SWID_Inq 8x 09 04 23 ff Reply: x0 50 [1-125 bytes SWID] ff.
p=1: Enable this port as a secondary
VISCA chain port for cameras usually con- SW_Input_Inq 8x 09 40 20 ff Reply 90 50 0p ff
nected to codec input 2-5 (default). p=Active input, 0..5
p=2: Use this port as a debug port.

SW_Port_3_Cfg 8x 01 40 03 0p ff p=0: Disable this port SW_Sync_Inq 8x 09 40 e0 0p ff Input: p=Input 0..5

p=1: Enable this port as a dual visca port Reply: 90 50 0p ff
(default). p=2: Input has sync
p=2: Use this port as a debug port. p=3: No sync on input
SW_Port_x_ 8x 01 40 04 0p Configure which push messages to send SW_InputFor- 8x 09 40 e1 ff Reply: 90 50 0p 0q ff
Push_Cfg 0q 0r ff for given port. mat_ Inq pq = Format for active input.
p=0/3: Configure port 0 or 3. 0 = 720p60
qr bit 0: Enable/disable SW_Input_Push. 1 = 720p59.94
qr bit 1: Enable/disable SW_Sync_Push. 2 = 720p50
qr bit 2: Enable/disable Enhanced VISCA.
qr = 00 is default for both ports.
Push Messages
Switch control commands Command set Push Message Comments
Messages starting with 8x-01-40-<20..3f> are switch control commands.

Command Set Command Packet Comments SW_Input_Push x0 01 40 20 0p ff The input has been changed.
p = the new input source
SW_Input_Set 8x 01 40 20 0p ff Sets which input to use.
p=0..5 SW_Sync_Push x0 01 40 e0 0p Sync state has changed on an input.
This will generate a SW_Input_Push on 0q ff This one will also be sent if the format is
the THSI Visca port if issued from the changed, so if sync is on, send a SW_For-
dual visca port and vice versa. mat_Inq.
p = source 0..5
q = state: 2 = sync, 3 = no sync
Misc.
Command Command Packet Comments

CAM_Boot 8x 01 42 ff Reboot the switch. This will also reset se-

rial speed to 9600.

D 13887.09
APRIL 2009 243
TANDBERG Video Switch
Disclaimer and Safety Instructions TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

Disclaimer Lightning Servicing

The information in this document is furnished for informational purposes Never use this apparatus, or connect/disconnect communication • Do not attempt to service the apparatus yourself as opening
only, is subject to change without prior notice, and should not be con- cables or power cables during lightning storms. or removing covers may expose you to dangerous voltages or
strued as a commitment by TANDBERG. other hazards, and will void the warranty. Refer all servicing to
TANDBERG reserves the right to amend any of the information given in qualified service personnel.
this document in order to take account of new developments.
Dust
Do not operate the apparatus in areas with high concentration of
• Unplug the apparatus from its power source and refer servic-
Every effort has been made to supply complete and accurate information, ing to qualified personnel under the following conditions:
however, TANDBERG assumes no responsibility or liability for any errors or
dust.
inaccuracies that may appear in this document, nor for any infringements
• If the power cord or plug is damaged or frayed.
of patents or other rights of third parties resulting from its use. No license Vibration • If liquid has been spilled into the apparatus.
is granted under any patents or patent rights of TANDBERG.
Do not operate the apparatus in areas with vibration or place it • If objects have fallen into the apparatus.
For your protection please read these safety instructions completely on an unstable surface. • If the apparatus has been exposed to rain or moisture
before you connect the equipment to the power source. Carefully observe
all warnings, precautions and instructions both on the apparatus and in
• If the apparatus has been subjected to excessive shock by
Power Connection and Hazardous Voltage being dropped.
these operating instructions.
Retain this manual for future reference. • The product may have hazardous voltage inside. Never at- • If the cabinet has been damaged.
tempt to open this product, or any peripherals connected to • If the apparatus seems to be overheated.
the product, where this action requires a tool. • If the apparatus emits smoke or abnormal odor.
Water and Moisture
• This product should always be powered from an earthed • If the apparatus fails to operate in accordance with the oper-
• Do not operate the apparatus under or near water – for power outlet.
example near a bathtub, kitchen sink, or laundry tub, in a wet ating instructions.
basement, near a swimming pool or in other areas with high
• Never connect attached power supply cord to other products.
humidity. • In case any parts of the product has visual damage never Accessories
attempt to connect mains power, or any other power source,
• Do not touch the product with wet hands. Use only accessories specified by the manufacturer, or sold with
before consulting service personnel.
the apparatus.
• The plug connecting the power cord to the product power sup-
Cleaning ply serves as the main disconnect device for this equipment.
• Unplug the apparatus from communication lines, mains The power cord must always be easily accessible. Communication Lines
power-outlet or any power source before cleaning or polishing. • Route the power cord so as to avoid it being walked on or Do not use communication equipment to report a gas leak in the
Do not use liquid cleaners or aerosol cleaners. Use a lint-free pinched by items placed upon or against it. Pay particular at- vicinity of the leak.
cloth lightly moistened with water for cleaning the exterior of tention to the plugs, receptacles and the point where the cord
the apparatus. exits from the apparatus.
• Unplug the apparatus from communication lines before • Do not tug the power cord.
cleaning or polishing. Do not use liquid cleaners or aerosol
cleaners. Use a lint-free cloth lightly moistened with water for • If the provided plug does not fit into your outlet, consult an
cleaning the exterior of the apparatus. electrician.
• Never install cables, or any peripherals, without first unplug-
ging the device from it’s power source.
Ventilation
• Do not block any of the ventilation openings of the apparatus. • Always use the power supply (AC–DC adapter) provided with
this product.
Never cover the slots and openings with a cloth or other mate-
rial. Never install the apparatus near heat sources such as • Replace only with power supply (AC–DC adapter) specified by
radiators, heat registers, stoves, or other apparatus (including TANDBERG.
amplifiers) that produce heat. • Never connect the attached power supply (AC–DC adapter) to
• Do not place the product in direct sunlight or close to a sur- other products.
face directly heated by the sun.

D 13887.09
APRIL 2009 244
TANDBERG Video Switch
Product Declaration TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS

A 级声明( A Class product declaration)

本产品为 A 级 ITE，在其使用说明,铭牌等显著位置中已包含如下内

容的声明(We declare here that the subject product is A Class ITE

product, and the following statement is clearly marked in the user

manual and nameplate ：

声 明
此为 A 级产品，在生活环境中，该产品可能会造成无线电干扰。在这

种情况下，可能需要用户对其干扰采取切实可行的措施。

WARNING:

This is a class A product. In a domestic environment this product may

cause radio interference in which case the user may be required to take

adequate measures.

声明�在位置 Position of the Declaration：

公司 Company Name：

TANDBERG Telecom AS

签字/盖章 Signature/ Stamp：

D 13887.09
APRIL 2009 245
Philip Pedersens vei 20, 1366 Lysaker, Norway
Telephone: +47 67 125 125
Fax: +47 67 125 234
Video: +47 67 117 777
E-mail: [email protected]