TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
• Designe d for custom integrations
• 19” mountab le codecs
• Expan dability f or future ap plications
• Total management via serial p ort, embedded we b
server, SNM P, Telnet, XML, HT TP / HT TPS, F TP and
on screen menu
• Best possible call for ea ch MultiSite p articipant with
rate matching and transcoding
• URI dialling
• H.323, H.320 & SI P suppor t
• TANDBERG E xpressway™ Technology
• Protection against net work inter ruptions in point-
to-p oint and multipoint calls with automati c
downspee ding and IPL R
• Standards- based embe dded encr yption
(AES & DES)
Software version F7.X
D 13887.08
MAY 2008
Codec
MXP
3000
6000
REFERENCE
FOR SYSTEM
INTEGRATORS
We rec ommen d that you check out the
TANDBE RG web s ite regularly for up dated
versions of this manual:
http://ww w.tandberg.com/support/
documentation.php
Thank you for choosing TANDBERG!
The TANDBERG Codec 3000 MXP and Codec 6000 MXP
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
3
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
What’s New in This Version?
Finding the Information You Need
There are a nu mber of new and altered instructions av ailable in
version F 7.1
Configuration Commands
CallVideoSource: <0/1/5/6>
New in this version. The Call Video Source is the default call
video source you would prefer to use in a call.
Conference PeriodicIntra: <0..1000>
New in this version. Use this setting to generate a new intra
frame with a congurable interval. Use this setting with caution
since it in a normal network will decrease the video quality. The
default value is set to 0 which means off. If you congure it to
10 it will send an intra every 10th second.
Conferen ce VideoText: <On/Of f/Auto>
New in this version. In MultiSite calls you can display the names
of the participants on screen. By setting the Video Text Time-out
setting, the system is congured to display the names for a
period of time or as long as you are connected.
Conference VideoTextTimeout: <0..30>
New in this version. 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.
CorporateDirectory Protocol: <HTTP/HTTPS>
New in this version. TANDBERG MXP systems now support
secure management when communicating with the TMS
(TANDBERG Management Suite).
Directory CallLog: <On/Off>
New in this version. Enable/disable Call Logs for Placed calls,
Missed calls and Received calls in the Phone Book.
DynamicResolution Mode <Auto/Off>
New in this version. With Dynamic Resolution the system will
use the optimal video resolution for the chosen bandwidth. This
feature is only applicable to HD (high denition) 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).
ExternalManager Protocol: <HTTP/HTTPS>
New in this version. Enables/disables for secure management.
ExternalServices Protocol: <HTTP/HTTPS>
New in this version. Enables/disables for secure management.
HTTPS VerifyServerCerticate: <On/Off>
New in this version. TANDBERG MXP systems now support
secure management when communicating with the TMS.
For more information see the TANDBERG White Paper “Imple-
menting Secure Management” which describes how to congure
secure HTTPS between TANDBERG products. To nd the docu-
ment, follow the link: http://www.tandberg.com/support/documentation.php and select White Papers.
Kiosk OneClickConnect: <On/Off>
New in this version. If turned On, you can make a call with a
single click on the green call button on the remote control. The
system will call the rst entry in “My Contacts” in the Phone
Book. NOTE: This functionality will only work in Kiosk Mode
If set to Off: Does not allow for one click connect in Kiosk mode.
MaxBandwidth: <128..10240>
New in this version. Limit max bandwidth usage for the system.
Related to IPMedia MaxVideoTXRate, which only controls upstream bandwidth.
OSD CallDuration Mode: <On/Off>
New in this version. 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.
OSD Menu IconPlacement: <Left/Right>
New in this version. 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.
OSD Menu Language: < English/German/Norwegian/French/
Swedish/Danish/Italian/Portuguese/Japanese/Chinese/TraditionalChinese/Russian/Spanish/Korean/Finnish/Thai/Arabic>
Altered in this version. Added Danish menu language to the list.
SerialPort 1 Mode: <Control/Transparent/Direct>
Altered in this version. Control: Gives access to the Command
Line Interface. Transparent: Enables transmission of text during
call on a line by line basis. Direct: Enables transmission on
binary data during call. NOTE! Only Serial Port 1.
SerialPort 1 Direct Buffer: <0..16384>
New in this version. Species the size of the buffer used in di-
rect mode. Try setting this value higher if you need a continuous
stream of data on the receiving end. Higher values introduces
more delay. NOTE! Only Serial Port 1.
SIP ReplyTo URI: <S: 0, 60>
New in this version. If congured it is this URI that will be dis-
played in the call lists.
SIP Server Type: <S: 0, 60>
Altered in this version. Added Siemens to the list of SIP server
type. Must be used when registering to a Siemens HiPath 8000.
Video Inputs Source 5 HorizAdjust: <0..255>
New in this version. This gives you the possibility to adjust the
placement of the pc image on screen. Much like the setting you
nd on a regular pc screen. NOTE! Only Video Input Source 5.
Video Outputs Animation <On/Off>
New in this version. 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.
Conguration commands for TANDBERG Remote Control
Enable or disable keys, and using conguration instead of commands.
Key Number0: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control.
4
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
What’s New in This Version?
Finding the Information You Need
Key Number1: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control.
Key Number2: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control.
Key Number3: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control.
Key Number4: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control.
Key Number5: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control.
Key Number6: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control.
Key Number7: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control.
Key Number8: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control.
Key Number9: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control.
Key Star: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control.
Key Square: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control.
Key Connect: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control.
Key Disconnect: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control.
Key Up: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control.
Key Down: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control.
Key Right: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control.
Key Left: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control.
Key Selfview: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control.
Key Layout: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control.
Key Phonebook: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control.
Key Cancel: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control.
Key MicOff: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control.
Key Presentation: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control.
Key VolumeUp: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control.
Key VolumeDown: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control.
Key Ok: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control.
Key ZoomIn: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control.
Key ZoomOut: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control.
Key Grab: <On/Off>
New in this version. Enables/disables the signal which is sent
to the codec when grabbing the TANDBERG Remote Control.
Key Cabinet: <On/Off>
New in this version. Enables/disables the headset key in front
of the cabinet. Applies to TANDBERG 1000 MXP only.
Key Presets: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control (TRC4).
Key FarEnd: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control (TRC4).
Key Services: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control (TRC4).
5
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Key Help: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control (TRC4).
Key MainCam: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control (TRC4).
Key PC: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control (TRC4).
Key DocCam: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control (TRC4).
Key VCR: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control (TRC4).
Key AUX: <On/Off>
New in this version. Enables/disables the given key on the
TANDBERG Remote Control (TRC4).
Command Instructions
Obser ve that the (r) in the Command instructions denotes tha t
the parameter is required. The (r) appear s for your infor mation
only and is not a p art of the i nstruction.
There are no n ew xComman d instructions for this version.
Status Information Commands
There are no n ew xStatus in structi ons for this ver sion.
What’s New in This Version?
Finding the Information You Need
D 138 87.08
MAY 2008
6
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Finding the Information You Need
What’s New in This Version? ............................................... 3
Configur ation Comm ands .............................................. 3
Command Instructi ons ..................................................5
Status Information C ommands ...................................... 5
Intellectual Property Rights
Disclaimer
License Information and Patent Information
License A greemen ts ....................................................11
Patent Information ...................................................... 11
Operator Safety / Environmental Issues
Safety In structi ons ...........................................................1 3
Water and Moisture ..................................................... 13
Cleaning .....................................................................13
Ventilation .................................................................. 13
Lightning .....................................................................13
Dust ........................................................................... 13
Vibration ..................................................................... 13
Power Conne ction and Ha zardous Vo lta ge .................... 13
Servicing .................................................................... 13
Accessories ................................................................ 13
Communic ation Lines ..................................................13
Environme ntal Issues ....................................................... 14
TANDBERG’s Environmental Polic y ............................... 14
European Environment al Directives .............................. 14
Waste Handlin g .......................................................... 14
Informat ion for Recyc lers ............................................. 14
Digital Us er Guides .................................................... 14
China RoHS Table........................................................ 15
What’s in the Shipping Box?
Contents of t he 3000 MXP Codec Shipping Box ................. 17
Contents of t he 6000 MXP Codec Shipping Box .................18
Interfaces and Sockets – Codec 3000 MXP
Rear Panel So cket– and Interface G roups .........................20
Codec 30 00 M X P .................................................................... 20
Codec 30 00 M X P Net .................................................. 20
Audio Sockets.................................................................. 21
Audio signal levels in Vpp and dB u .................................... 22
Video Sockets ................................................................. 23
Camera So cket ................................................................ 24
ISDN BRI so ckets ............................................................ 25
Net socket ....................................................................... 26
Networ k Interface Sockets ...............................................27
Power Socket & On/Off Switc h ......................................... 28
Interfaces and Sockets – Codec 6000 MXP
Rear Panel So cket– and Interface G roups .........................3 0
Audio Sockets.................................................................. 31
Audio Sign al Levels in Vpp and dBu................................... 32
Video Sockets ................................................................. 33
Net Inter face Soc ket ........................................................ 34
Networ k Interface Sockets ...............................................35
Camera So ckets ..............................................................36
Data Por ts ....................................................................... 37
Power Socket & On/Off Switc h .........................................3 8
About the TANDBERG API
Introduction ..................................................................... 40
Basic Princ iples .......................................................... 40
The TANDBERG A PI Engine ........................................... 40
Structuring of Info rmation ............................................ 40
Addressing Using XPat h or TANDBERG SimplePath ....... 40
Feedback .................................................................... 40
Datapor t Inter face on the Classic Systems ................... 41
XACLI .............................................................................. 42
Accessin g XACLI ......................................................... 42
Connect ing to XACL I using the Datapor t (RS 232) ......... 42
Hardware & Cabling (RS 232) ....................................... 42
Troubleshooti ng (RS 232) ............................................. 42
Data Por t (RS 232) ...................................................... 42
Cable wiring TANDBERG MX P ↔ PC via RS 232 ............. 42
XACLI – the Basics ........................................................... 43
Root Commands .........................................................43
XACLI – Main Types of Commands ....................................44
Special Co mmands .....................................................4 4
Configur ation Type Com mands ..................................... 44
Status Type Commands ............................................... 44
Command Type C ommands ......................................... 44
XACLI – Configuration Type Commands .............................45
XACLI – Configuration Type Oper ation .............................. 46
Configur ation Help ...................................................... 46
Configur ation Read ...................................................... 46
Configur ation Set ( Write) ............................................. 46
XACLI – Configuration Types ............................................. 47
Format fo r Value Types ................................................47
XACLI – Command-type – xc ommands/xdire ctory ............... 48
Gettin g an Overview ....................................................48
What’s in this
User Guide?
D 138 87.08
MAY 2008
7
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Command help ............................................................4 8
How to Get an Overview of Suppor ted Comman ds .........48
XACLI – Command-type – Issuing a Command ................... 49
Issuing a Com mand ..................................................... 49
Sequenc e Notation ..................................................... 49
Command Re sponse ...................................................49
Combination of Markup N otation and Sequence ...........49
XACLI – Command-type – P arameter Value Types .............. 50
Command Parameter Value Typ es ................................ 50
Format fo r Value Types ................................................50
XACLI – S tatus Type Commands .......................................51
Underst anding St atus Inform ation Str ucturing .............. 51
XACLI – S tatus Type – Def ault Formatting .......................... 52
Default X ACLI For matting ............................................. 52
About th e Example s Provided ...................................... 52
XACLI – S tatus Type – Comp lete Path Formattin g............... 53
XACLI – S tatus Type – XML F ormatt ing .............................. 54
XACLI – S tatus Type – Addressing St atus Inform ation ........ 55
XACLI – S tatus Type – Ex posure Options ...........................56
XACLI – Sp ecial Comm ands – xfee dback ........................... 57
XACLI – Sp ecial Comm ands – xpref erences ....................... 59
The xpref erences Op tions ............................................ 59
xprefere nces xpat hwrite .............................................. 59
xprefere nces xmlco mmandresult ................................. 59
xprefere nces detaillevel ............................................... 59
xprefere nces xmlco nfigfeedback .................................. 59
xprefere nces xmlst atusfeedback ................................. 60
xprefere nces itemnu mber ............................................ 60
xprefere nces compl etepath ......................................... 61
XACLI – Sp ecial Comm ands – xget xml ............................... 62
TXA S - TANDBERG XML A PI Serv ice ................................... 63
Bare- bone HT TP(S) Access ..........................................63
Configuration- type Commands
Underst anding the Table L ayout ........................................ 65
AdditionalCamera ........................................................66
AlertSpeaker ............................................................... 66
AlertTone .................................................................... 66
AllowLatency ............................................................... 66
AutoAnswer ................................................................. 70
AutoDisplaySnapshot .................................................. 70
AutoLayout..................................................................70
AutoPIP ....................................................................... 70
Bonding ...................................................................... 70
CallManager ............................................................... 70
CallVideoSource .......................................................... 71
Camera ...................................................................... 71
CameraDVI ................................................................. 72
CameraSleep .............................................................. 72
CameraTracking ..........................................................73
Conference ................................................................. 73
CorporateDirectory ...................................................... 77
DefaultPIPPosition ...................................................... 77
Directory ..................................................................... 78
DoNotDisturb .............................................................. 78
DualMonitor ................................................................ 78
DuoVideoSource ......................................................... 78
DynamicResolution ..................................................... 78
E1 .............................................................................. 78
Ethernet .....................................................................78
ExternalManager ......................................................... 78
ExternalNet work .......................................................... 79
ExternalSer vices ......................................................... 79
FECC .......................................................................... 80
FeedbackFilter ............................................................80
FTP ............................................................................. 80
G703 ..........................................................................80
H320 .......................................................................... 81
H323 .......................................................................... 81
H323CallSetup ........................................................... 81
H323Gatekeeper......................................................... 81
H323Prefix .................................................................83
HTTP ..........................................................................83
HTTPS ........................................................................83
IdReport ..................................................................... 83
IEEE802.1x ................................................................. 84
IMUX ..........................................................................84
Integrator .................................................................... 89
IP ............................................................................... 89
IPMedia ...................................................................... 90
IPProtocol ...................................................................90
IRControl ....................................................................90
ISDN ........................................................................... 90
Keyboard .................................................................... 94
Kiosk .......................................................................... 94
Key ............................................................................. 94
Kiosk .......................................................................... 98
LocalLayout ..............................................................100
Logo ......................................................................... 100
LoS ..........................................................................10 0
MainVideoSource ...................................................... 101
MaxBandwidth .......................................................... 101
MCU ......................................................................... 101
NAT .......................................................................... 101
NetProfile ................................................................. 101
NTP .......................................................................... 102
OptionKey ................................................................. 102
OSD ......................................................................... 102
PictureProgram ......................................................... 105
PresentationStart ...................................................... 105
PacketlossDownSpeed .............................................. 105
Preset ......................................................................10 6
QoS .......................................................................... 108
RemoteSwUpgrade .................................................... 110
RTP ..........................................................................110
Screensaver .............................................................. 110
SelfView OnStartup ....................................................110
SerialPort ................................................................. 110
SIP ........................................................................... 111
SNMP ....................................................................... 112
StartupVideoSource .................................................. 113
StillImageSource ....................................................... 113
SSH .......................................................................... 113
Streaming ................................................................. 114
Strict Password: <O n/Off> ......................................... 115
Switch ...................................................................... 115
SystemUnit ............................................................... 115
T1 ............................................................................ 116
Telnet ....................................................................... 116
TelnetChallenge ........................................................ 116
Time ......................................................................... 116
UseAsLocalPCM onitor ...............................................117
Video ........................................................................ 117
VNC .......................................................................... 121
LocalEnt ry — GroupEntr y ................................................. 122
LocalEnt ry [1..200] ....................................................122
GroupEntry [1..50] .....................................................122
GlobalEntry .................................................................... 123
Configuration Storage Levels
Underst anding the Table L ayout ...................................... 125
HTTP M ode — IPProtocol ................................................. 131
Video Inputs Source [1..6] Name — VNC Passwor d .........139
Command Information Tables
Underst anding the Table L ayout ...................................... 141
AlertToneTest ............................................................142
AudioTestSignal ......................................................... 142
Boot ......................................................................... 143
CallAccept ................................................................143
CallMute ................................................................... 143
CallMuteOutgoing ...................................................... 143
CallSetAudioTP .......................................................... 144
CameraFocus ............................................................ 144
CameraForceUpgrade ................................................ 144
D 138 87.08
MAY 2008
8
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
CameraHalt ..............................................................144
CameraMove.............................................................14 5
CameraPosition ........................................................145
CameraReconfigure ................................................... 145
CameraTrackingStart ................................................. 146
CameraTrackingStop .................................................146
CameraUpgrade ........................................................ 146
CameraWhiteBalance ................................................ 146
ChairRelease ............................................................14 6
ChairTake .................................................................. 146
ConferenceDisconnect .............................................. 147
ConferenceTerminate.................................................147
CorpDirSearch .......................................................... 148
CorpDirGetNext ......................................................... 149
CorpDirGetPrevious ................................................... 150
DefaultValuesSet ......................................................151
Dial ..........................................................................152
DialGlobalEntry .........................................................153
DialGroupEntry .......................................................... 153
DialLocalEntr y ........................................................... 153
DisconnectCall .......................................................... 154
DuoVideoStart ..........................................................154
DuoVideoStop ........................................................... 154
DTMFSe nd ................................................................ 154
FECCF ocus ............................................................... 154
FECCM ove ................................................................155
FECCPresetActivate ................................................... 155
FECCPresetStore ....................................................... 155
FECCRequestStill ...................................................... 155
FECCSelectSource .................................................... 155
FeedbackDeregister ..................................................155
FeedbackRegister .....................................................156
FIPSMode ................................................................. 156
FloorRelease ............................................................. 156
FloorRequest ............................................................156
FloorToSite ................................................................ 157
FloorToSiteEnd .......................................................... 157
GroupEntr yAdd .......................................................... 157
GroupEntry Delete ...................................................... 157
KeyDown .................................................................. 157
KeyRelease ...............................................................158
KeyPress ..................................................................158
KeyDisable ............................................................... 158
KeyEnable ................................................................. 158
LocalEntryAdd ........................................................... 159
LocalEntryD elete ....................................................... 159
MessageBoxDelete ................................................... 159
MessageBoxDisplay .................................................. 160
PIPHide ..................................................................... 160
PIPShow ...................................................................16 0
PresetActivate ..........................................................16 0
PresetClear ............................................................... 161
PresetStore ..............................................................161
ProfileActivate ........................................................... 161
ProfileCreate ............................................................. 161
ProfileDelete ............................................................. 161
ProfileList ................................................................. 161
ScreensaverActivate .................................................. 161
ScreensaverDeactivate .............................................. 162
ScreensaverReset ..................................................... 162
SiteDisconnect .........................................................162
SiteView ...................................................................162
SiteViewEnd .............................................................. 162
SPIDAutoConfigure .................................................... 163
StillImageSend .......................................................... 163
StreamingStart ......................................................... 163
StreamingStop .......................................................... 163
TextDelete ................................................................163
TextDisplay ...............................................................163
VirtualMonitorReset ..................................................16 4
VirtualMonitorSet ...................................................... 164
Status Information Tables
Underst anding the Table L ayout ...................................... 166
Audio............................................................................. 167
BRI ................................................................................ 168
Call ............................................................................... 170
Camera ......................................................................... 182
CameraSWUpgrade ........................................................18 3
CameraTracking ............................................................. 184
Conference .................................................................... 185
Ethernet ........................................................................ 191
ExternalManager ............................................................ 192
ExternalNet work ............................................................193
FarEndInformatio n ........................................................19 4
Feedback ....................................................................19 6
G703 ............................................................................. 197
H323Gatekeeper ...........................................................198
IP .................................................................................. 199
NTP ............................................................................... 200
PRI ................................................................................ 201
RemoteSwUpgrade ........................................................ 204
Screensaver .................................................................. 205
SIP .............................................................................. 206
SoftwareUpgrade ........................................................... 207
Switch ..........................................................................208
SystemUni t ... ................................................. 210
VirtualMonitor ................................................................ 211
Warning ......................................................................... 212
Call ...............................................................................213
Call - DisconnectCause ..................................................214
Call - DisconnectCauseValues ........................................ 215
AuthenticationFailure .....................................................218
CallDisconnected ........................................................... 219
CallSuccessful ............................................................... 220
DownspeedingF inished .................................................. 221
MessageBoxResult ........................................................222
PacketlossDownSpeed ................................................... 223
SString .......................................................................... 224
SystemActivity ...............................................................225
Controlling External Cameras
Extc am Protocol B asics .................................................. 227
Far End Video Source Sw itching .................................227
Far End Pres et Switching ........................................... 227
The extcap and the ext name ...................................... 227
The extsw itch ............................................................ 227
Interf acing to the TAND BERG WAVE II Came ra ................228
Command an d Response E xchange Se quence ............ 228
Connect ing to the Camera .........................................231
Interf acing to the Precision HD Camera ........................... 231
New Commands and Inquir ies .................................... 231
TANDBERG Video Switch
Unpackin g the Video S witch ........................................... 233
The TANDBERG V ideo Switc h set contains: ................. 233
Cameras ................................................................... 233
Connect ing the Video Switch ..........................................234
Installation of the Video Switch ...................................... 237
Communic ating with t he Video Switch ............................. 238
Communic ating Using VI SCA ...................................... 238
VISCA Inter face Basics .............................................. 238
VISCA Serial Ports ..................................................... 238
Enhanced VISCA ....................................................... 238
VISCA Mess ages ....................................................... 238
VISCA Standard Commands ....................................... 238
VISCA Standard Inqu iries ........................................... 238
VISCA Standard Push M essages ................................ 238
Configur ation Comm ands ..........................................239
Switch control comma nds .......................................... 239
Disclaimer and Safety I nstruct ions ................................. 240
Product D eclaration ....................................................... 241
We rec ommen d that you check out the
TANDBE RG web s ite regularly for up dated
versions of this manual:
http://ww w.tandberg.com/support/
documentation.php
This Reference Guide for System Integrators and the Products to
which it relates contain information that is proprietary to TANDBERG
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 proper ty notices, in
limi ted quant iti es in c onn ection wit h th e us e of the Pr odu cts. Exc ept
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 other wise,
without the prior written permission of TANDBERG. Requests for
such permission should be addressed to tandberg@tandberg.com.
TANDBERG® is a registered trademark belonging to Tandberg ASA.
Other trademarks used in this document are the property of their
respective holders.
COPYRIGHT © 2008, TANDBERG
All rights reserved.
Philip Pedersens vei 22, 1366 Lysaker, Norway
Tel: +47 67 125 125 Fax: +47 67 125 234
E-mail: tandberg@tandberg.com
Intellectual Property Rights
We rec ommen d that you check out the
TANDBE RG web s ite regularly for up dated
versions of this manual:
http://ww w.tandberg.com/support/
documentation.php
The specifications for the Products and the information in this
document are subject to change at any time, without notice, by
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 © 2008, TANDBERG
All rights reserved.
Disclaimer
D 138 87.08
MAY 2008
11
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
License Agreements
Copyrig ht notices for third- part y soft ware on the TAND BERG
MXP syste ms are listed bel ow:
The non-commercial third p arty c ode is distri buted in binary •
form unde r the terms of no n-c opyleft style open source
licenses su ch as BSD, Artistic, or MIT/X Consortium.
The produ ct also cont ains some binary code distribute d in •
binary form under the terms of the G NU public license with
an exemption w hich allows static links to non -cop yleft co mmercial co de.
In accord ance with section (3) of the GN U General P ublic •
License, copies of such code will be provided upon re quest
by contac ting TANDBERG . Please cont act us by using t he
Online Supp ort sec tion at ww w.tandber g.com or the “contact us” sec tion of this manual. Please prov ide USD 10.00
for media and shipping.
Agfa
Contains i Type™ from Mono type Ima ging Corp oration .
CMU-SNMP
Copyri ght © 1988, 19 89, 1991, 1992 by Car negie Mell on University All Ri ghts Reser ved
CMU- SNMP is dis tributed u nder the te rms of the CMU S NMP
license wh ich is an open s ource lice nse similar to a BS D or X
Consor tium Lice nse.
Dropbear - an SSH2 server
Copyri ght © 2002,2 003 Matt J ohnston All r ights res erved.
The Drop bear SSH2 se rver is dis tribute d under the te rms of the
Dropbe ar License w hich is a MIT/X Conso rtium st yle ope n source
license.
eCos
eCos, the E mbedded C onfigur able Oper ating Sys tem.
Portio ns of eCos cod e are distri buted und er several B SD style
licenses. O ther por tions of e Cos code ar e distribu ted under th e
terms of the G NU Gener al Public Li cense with a n on- copylef t excep tion which a llows staic li nks to non- copyl eft prog rams. Por tions
of the code a re distrib uted under t he terms of v arious BSD s tyle
licenses.
Copyri ght © 1998, 199 9, 2000, 2001, 20 02, 2003 Red H at, Inc.
Copyri ght © 2002, 20 03 John Dalla way
Copyri ght © 2002, 20 03 Nick Gar nett
Copyri ght © 2002, 20 03 Jonath an Larmou r
Copyri ght © 2002, 20 03 Andrew Lu nn
Copyri ght © 2002, 20 03 Gary T homas
Copyri ght 9 2002, 20 03 Bart Vee r
Copyri ght © 1982, 1986, 1 991, 1993 The Re gents of the
Universi ty of Califo rnia. All rig hts reser ved.
Copyri ght © UNIX Sy stem Labo ratories, I nc.
All or some p ortion s of this file ar e derived f rom materi al licensed
to the Unive rsity of Ca lifornia by A merican Telep hone and Telegr aph
Co. or Unix Sys tem Labor atories, I nc. and are rep roduce d herein
with the p ermission o f UNIX Syst em Labor atories, In c.
Copyri ght © 1995, 1996, 1 997, and 1998 WIDE Projec t. All righ ts
reserved.
Copyri ght © 2000 B rian Somer s <brian@Aw fulhak.o rg>
Copyri ght © 1998 The N etBSD Fo undation, I nc. All righ ts reser ved.
Copyri ght © 1997 Niklas Ha llqvist. A ll rights re served .
Copyri ght © 1988 St ephen Dee ring.
Copyri ght © 1992, 1993 T he Regents of t he Univers ity of
Californ ia. All right s reser ved.
This code is d erived fr om soft ware cont ributed to B erkeley by
Stephen D eering of S tanford U niversit y.
ExPat XML Parser
Copyri ght © 1998, 199 9, 2000 Thai O pen Sourc e Soft ware Cente r
Ltd and Clar k Cooper
Copyri ght © 2001, 200 2, 2003, 200 4, 2005, 200 6 Expat m aintainers.
The Ex Pat XML par ser is distri buted und er the terms o f the ExP at
License w hich is a MIT/X Conso rtium st yle ope n source lic ense
ICU
ICU Licen se - ICU 1.8.1 Co pyright © 1 995-20 03 Intern ational Busi ness Mach ines Corp oration an d others. All r ights res erved.
ICU is distr ibuted und er the term s of the ICU lic ense which is a
MIT/X Consor tium sty le license.
OpenSSL
Copyri ght © 1998 -2004 The O penSSL Pr oject. All r ights res erved.
This prod uct includ es soft ware develo ped by the Op enSSL Pro ject
for use in the O penSSL Toolki t (http://www.openssl.o rg/)”
Copyri ght © 1995 -1998 Eric Young (eay @cryp tsoft. com) * All
rights re serve d.
OpenSS L is distribu ted under th e terms of th e OpenSSL an d SSLeay licens es which are b oth BSD st yle open so urce licen ses.
snprintf
Copyri ght © 1999, Mark M artin ec. All righ ts reser ved
Snprint f is distrib uted under t he terms of t he snprint f license w hich
is a Frontier A rtist ic style o pen sourc e license.
xSupplic ant (wpa_ supplica nt) 802.1x
Copyri ght © 2002-20 05, Jouni Ma linen jkmalin e@cc.hu t.fi
xSupplic ant is distri buted und er the terms o f the xSuppli cant
license wh ich is a BSD st yle open so urce licen se.
Patent Information
The prod ucts desc ribed in thi s manual are co vered by one or m ore
of the follow ing patent s:
US6,584,077 US5,83 8,664 US5,600,64 6
US5,768,263 US5,991,277 US7,034,860
US5.886 .734 US5990.933 US7,010,119
US7,283,588 EP01953201 GB1338127
Other pa tents pen ding.
View ww w.tandberg.com/tandberg_pm.jsp for a n updated lis t
License Information and Patent Information
We rec ommen d that you check out the
TANDBE RG web s ite regularly for up dated
versions of this manual:
http://ww w.tandberg.com/support/
documentation.php
For your own protection, please read the overleaf safety
instructions completely, before operating the equipment
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.
Operator Safety / Environmental Issues
D 138 87.08
MAY 2008
13
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
For your protection pl ease read the se safety
instruc tions compl etely before y ou connect
the equipm ent to the power source. Car efully
observe all warnings, p recautio ns and instructions both on the appara tus and in thes e
operating instruc tions.
Retain this ma nual for futu re referenc e.
Water and Moisture
Do not oper ate the appa ratus under or •
near water – fo r example near a b athtub,
kitchen sin k, or laundr y tub, in a wet base ment, near a swimming pool o r in other
areas with hi gh humidit y.
Never install jacks for com municatio n •
cables in wet l ocations un less the jack is
specifically desig ned for wet lo cations.
Do not touch t he produc t with wet han ds.•
Cleaning
Unplug the apparatus f rom communi cation •
lines, mains po wer-out let or any power
source before cleanin g or polishing. D o not
use liquid cle aners or aerosol cleaner s.
Use a lint-fr ee cloth ligh tly moistene d with
water for cleaning the exterior of the ap paratus.
Unplug the apparatus f rom communi cation •
lines before cleaning or polishing. Do not
use liquid cle aners or aerosol cleaner s.
Use a lint-fr ee cloth ligh tly moistene d with
water for cleaning the exterior of the ap paratus.
Ventilation
Do not block a ny of the ventilation open -•
ings of the app aratus. Never cover the
slots and openings with a cloth or other
material. Never install th e apparatus n ear
heat sourc es such as radiators, heat registers, stoves, or other appar atus (including
amplifie rs) that produ ce heat.
Do not plac e the produ ct in direct su nlight •
or close to a sur face directly heated by the
sun.
Lightning
Never use this a pparatus, o r connect /disconnect comm unication c ables or power cables
during lig htning stor ms.
Dust
Do not oper ate the appa ratus in areas w ith
high concentration of dust
Vibration
Do not oper ate the appa ratus in areas w ith
vibratio n or place it on an unstable surface.
Power Connection and Hazardous
Voltage
The produ ct may have hazardous vol tage •
inside. Never a ttempt to op en this product,
or any perip herals conn ected to the product, where this action requires a tool.
This produ ct should alw ays be powere d •
from an ear thed pow er outlet.
Never conn ect atta ched power s upply cord •
to other pro ducts.
In case any parts of the p roduct has visual •
damage neve r attempt to c onnect mains
power, or any other p ower sourc e, before
consultin g service personn el
The plug co nnecting t he power cor d to the •
product/power supply s erves as the main
disconnect device fo r this equipme nt. The
power cord m ust always be easily acces sible.
Route the power cord so as to avoid it be-•
ing walked on or p inched by items placed
upon or against it. Pay par ticular at tention
to the plugs, re ceptacl es and the point
where the c ord exits from the appar atus.
Do not tug the power cord.•
If the provided plug do es not fit into your •
outlet, consult an elect rician.
Never install cables, or any p eripher als, •
without f irst unplu gging the device fr om it's
power sour ce.
Always use the power supp ly (AC–D C adap-•
tor) provid ed with this product (adaptor is
supplied wi th 3000 MXP only).
Replace only with power supply (AC– DC •
adaptor) specified by TAND BERG (adaptor
is supplied wi th 3000 MXP only).
Never conn ect atta ched power s upply •
(AC–D C adaptor) to ot her products (adaptor
is supplied wi th 3000 MXP only).
Servicing
Do not atte mpt to ser vice the app aratus •
yourself as opening or rem oving cover s
may expose yo u to dangerous voltages or
other hazards, and will void the warranty.
Refer all ser vicing to qu alified service
personn el.
Unplug the apparatus f rom its powe r •
source and refer ser vicing to qualified
personn el under the following conditions:
If the power c ord or plug is damaged or •
frayed.
If liquid has be en spilled into t he •
apparatus.
If object s have fallen into the appar atus. •
If the apparatus has bee n exposed to •
rain or moisture
If the apparatus has bee n subjected to •
excessive sh ock by being dr opped.
If the cabin et has been damaged.•
If the apparatus seems to b e •
overheate d.
If the apparatus emits smoke or •
abnormal odor.
If the apparatus fails to op erate •
in accord ance with the operati ng
instructions.
Accessories
Use only acc essories sp ecified b y the
manufac turer, or sold with t he apparatus.
Communication Lines
Do not use com municatio n equipment to
repor t a gas leak in the vicinity of t he leak.
Safety Instructions
D 138 87.08
MAY 2008
14
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Thank you for buying a pro duct whic h contribu tes to a reduc tion in pollu tion, and thereby helps save t he environm ent. Our
products reduce the need for tr avel and transport and thereby
reduce pollution. Our p roducts have either no ne or few consum able par ts (chemicals, toner, gas, paper). Our p roducts a re low
energ y consuming products.
TANDBERG’s Environmental Policy
Environme ntal stewardship is impor tant to TANDB ERG’s
culture. As a gl obal company with stron g corpor ate values,
TANDBERG is com mitted to following inter national env ironmen tal legisla tion and designing techn ologies that help companies,
individu als and communities creat ively addre ss environm ental
challenges.
TANDBERG’s environmental objectives are to:
Develop pro ducts that reduce en ergy consumption, CO•
2
emissions, and traff ic congest ion
Provide pr oducts an d servi ces that improve qualit y of life for •
our custome rs
Produce p roducts t hat can be re cycled or disp osed of safel y •
at the end of product life
Comply with all relevant e nvironmental legislat ion.•
European Environmental Directives
As a manufa cturer of electrical an d electronic equipmen t TANDBERG is responsible for compliance with the requirements in
the European Directives 2002/96/EC (WEEE) and 2002/95/EC
(RoHS).
The prima ry aim of the WEEE Direct ive and RoHS Dir ective is
to reduce t he impact of disposal of elec trical and electroni c
equipment at end- of-life. T he WEEE Direc tive aims to reduce
the amount of WEEE sent for dis posal to land fill or incin eration
by requirin g produce rs to arran ge for collect ion and recy cling.
The RoHS Directive bans t he use of cer tain heav y metals an d
brominate d flame ret ardants to re duce the env ironment al
impact of WEEE which is land filled or in cinerated.
TANDBERG has implemented necessar y proces s changes to
comply with the European RoHS Direc tive (2002/95/EC) and
the Europe an WEEE Direc tive (2002/96/EC).
Waste Handling
In order to avoid the dissemination of haz ardous subs tances
in our environment and to dimi nish the pressure on natur al
resource s, we encourage you to use the appropria te take- back
systems in you r area. Those sy stems will reuse or recycle most
of the materials of your end of li fe equipmen t in a sound way.
TANDBERG pro ducts put on the market a fter Augus t
2005 are marked with a crossed- out wheelie bin symbol that invites you to use those take- back systems.
Please cont act your local supplier, the re gional waste
administr ation or http://www.tandberg.com/recycling
if you need mo re information on the collection and recycling
system in your a rea.
Information for Recyclers
As part o f complianc e with the European WEEE Directive, TAND BERG provi des recycli ng information on reque st for all typ es of
new equipme nt put on the m arket in Europ e after August 13th
2005.
Please cont act TANDBERG and provide the following details
for the pro duct for whi ch you would like to r eceive rec ycling
information:
Model number of TANDBERG p roduct •
Your company’s name •
Contact name •
Address •
Telephone numb er •
E-mail. •
Digital User Guides
TANDBERG is ple ased to announ ce that we have replaced t he
printed versions of our Use r Guides wit h a digital CD ve rsion.
Instead of a range of diff erent user manuals, there is now one
CD – which can b e used with all TANDBERG prod ucts – in a
variety o f languages. The environmental benef its of this are
significant. The CDs are recycla ble and the savings on pape r
are huge. A simpl e web- based search feature helps you direct ly
access th e information you need. In a ddition, th e TANDBERG
video systems now have an intu itive on-screen h elp functio n,
which prov ides a range of useful features and tips. Th e contents of the CD can still be pr inted locall y, whenever need ed.
Environmental Issues
D 138 87.08
MAY 2008
15
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
China RoHS Table
Environmental Issues
We rec ommen d that you check out the
TANDBE RG web s ite regularly for up dated
versions of this manual:
http://ww w.tandberg.com/support/
documentation.php
What’s in the Shipping Box?
This part of the Reference Guide for System Integrators
presents the contents of the shipping box to ease your
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.
17
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Remote control
Batteries for remote control
CD with user documentation
Rack mounting kit (I)
Rack mounting kit (II)
Codec 3000 MXP
User
registration
card
Power supply
Up to 4 mains cables
(depending on region)
4 ISDN BRI cables
(not included with the
NET version)
Video DVI–VGA cable
Split cable for
non-TANDBERG WAVE II
cameras
1 LAN / Ethernet cable
What’s in the Shipping Box?
Contents of the 3000 MXP Codec Shipping Box
18
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
What’s in the Shipping Box?
Contents of the 6000 MXP Codec Shipping Box
Remote control
Batteries for remote control
CD with user documentation
Rack mounting kit (I)
Rack mounting kit (II)
Codec 6000 MXP
User
registration
card
6 ISDN BRI cables
1 ISDN PRI cable
1 LAN / Ethernet cable
DVI–VGA cable
Up to 4 mains cables
(depending on region)
Mains
extension
cable
We rec ommen d that you check out the
TANDBE RG web s ite regularly for up dated
versions of this manual:
http://ww w.tandberg.com/support/
documentation.php
Interfaces and Sockets – Codec 3000 MXP
This part of the manual provides an in-depth presentation
of the rear panel sockets and interfaces of the Codec
3000 MXP, including the audio signal levels and the
formats supported.
20
Interfaces and Sockets – Codec 3000 MXP
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Audio sockets
Video sockets
DC power socket
and On/Off switch
Network
interface
sockets
PC card
Camera
ISDN BRI
Net socket
Camera
Audio sockets
Video sockets
DC power socket
and On/Off switch
Network
interface
sockets
PC card
Codec 3000 M X P
Codec 3000 M X P Net
The Codec 3000 MXP comes in two avours – with ISDN BRI sockets (upper) or with Net socket (lower).
Ethernet
Ethernet
Rear Panel Socket– and Interface Groups
21
Interfaces and Sockets – Codec 3000 MXP
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Microphone Inputs Nos. 1–2.
Two balanced microphone
inputs for electret microphones
balanced, 24V phantom
powered via XLR connectors.
Use Audio Input No. 3 to
connect to external playback
devices. This input can also
be congured as a microphone
input. It will then function in
lieu of the Mic. 2 input and be
connected to Mic. 2’s echo
canceller (which can be turned
on/off).
Use Audio Input No. 4 to
connect a VCR or DVD player
to the system. For systems
congured with stereo I/O,
connect the VCR/DVD right
channel to this input. This
input should be used when
connecting a telephone add-on
system.
Tip! Audio Input No. 4 is not
equipped with an acoustic
echo canceller. Connecting a
microphone to this input can
therefore not be recommended.
Use Audio Output No. 2 (the VCR out put) to
provide a mi xed signal consisting of audi o
from the lo cal side (VC R not include d) and
audio from t he far end.
This outpu t should be use d when connecting a
telephone a dd- on system.
For system c ongured wi th stereo I/O and
with SPDI F† active on Audio Outpu t No. 1, this
output will provide th e VCR left ch annel stereo
informat ion.
For systems c ongured wi th stereo I/O, stereo
speakers and SPDIF† not active, t his output
will provid e the right channel of the loudspeaker signal (the left channel will be prov ided on
the Audio Ou tput No. 1).
Hardware Information
Microphone(s) Audio Input(s) Audio Outputs
Signal type Balanced Unbalanced
Socket XLR-F RCA/phono
Input impedance
2400 W
(pin 2–3)
10 kW
Output impedance
680 W
Max input level when set to
min. input level
83 mVpp 15.5 Vpp
Max output level when set
to max. output level
15.5 Vpp
Max input level when set to
max. input level
6.2 mVpp 1.2 Vpp
Max output level when set
to min. output level
1.2 Vpp
Gain range 22.5 dB (16 steps of 1.5 dB)
Phantom power 24 V ± 5 %
Phantom power resistor
pin 2
1200 W
Phantom power resistor
pin 3
1200 W
Max phantom power
current
12 mA
XLR pin-out
External view of socket
PIN 1: Gnd
PIN 2: Hot
PIN 3: Cold/neutral
12
3
RCA pin-out
External view of socket
GNDSignal
Use Audio Output No. 1 to provid e a mixed
signal of audio from far end and local
external devices connected to inp ut 3 & 4 in
addition to d ial tones.
This outpu t should be co nnected to the local
loudspeaker system, whic h may, or may not,
include th e TANDBERG Digital Natur al Audio
Module.
For systems c ongured wi th stereo
speakers and SPDIF† active, the left and
right channel of the loudspeaker sig nal will
both be provided on this o utput.
For systems c ongured wi th stereo
speakers and SPDIF† not active, t he
left channel of the lou dspeaker sig nal
will be prese nt on this outp ut. The rig ht
loudspeaker channel will b e provide d on
Audio Outp ut No. 2.
†
SPDIF (Sony/Philips Digital Interface)
is used by the Digital Natural Audio module.
Stereo Settings
Settings Output Response
Out 1 mode Stereo
I/O mode
Stereo
speakers
Audio Out 1 Audio Out 2
Analogue Off Off Loudspeaker mono VCR
Analogue Off On Loudspeaker L
Loudspeaker R
Analogue On Off Loudspeaker mono VCR
Analogue On On Loudspeaker L Loudspeaker R
SPDIF Off Off Loudspeaker mono VCR
SPDIF Off On Loudspeaker L & R VCR
SPDIF On Off Loudspeaker mono VCR
SPDIF On On Loudspeaker L & R VCR
Tip! Audio signal levels
expressed in volts and dBu
can be found overleaf.
NoTe! Audio inputs 3 &
4 are referred to as Line
input 1 & 2 in the API.
Tip! Unused, but connected
audio inputs should be set
to Off to avoid unwanted
audio/noise.
Audio Sockets
22
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Interfaces and Sockets – Codec 3000 MXP
Audio Inputs 3 & 4
Signal levels
Signal
levels
Clipping levels Nominal
level
Input
menu
level
setting
[dB] [Vpp] [dBu] [dBu]
0.0 15.5 17.0 –1.0
1.5 13.0 15.5 –2.5
3.0 11.0 14.0 –4.0
4.5 9.2 12.5 –5.5
6.0 7.8 11.0 –7.0
7.5 6.5 9.5 –8.5
9.0 5.5 8.0 –10.0
10.5 4.6 6.5 –11.5
12.0 3.9 5.0 –13.0
13.5 3.3 3.5 –14.5
15.0 2.8 2.0 –16.0
16.5 2.3 0.5 –17.5
18.0 2.0 -1.0 –19.0
19.5 1.6 -2.5 –20.5
21.0 1.4 -4.0 –22.0
22.5 1.2 -5.5 –23.5
Microphone Inputs 1 & 2
Signal levels
Signal
levels
Clipping levels Nominal
level
Input
menu
level
setting
[dB] [mVpp] [dBu] [dBu]
0.0 83.0 –28.4 –46.4
1.5 69.8 –29.9 –47.9
3.0 58.8 –31.4 –49.4
4.5 49.4 –32.9 –50.9
6.0 41.6 –34.4 –52.4
7.5 35.0 –35.9 –53.9
9.0 29.4 –37.4 –55.4
10.5 24.8 –38.9 –56.9
12.0 20.8 –40.4 –58.4
13.5 17.5 –41.9 –59.9
15.0 14.8 –43.4 –61.4
16.5 12.4 –44.9 –62.9
18.0 10.4 –46.4 –64.4
19.5 8.8 –47.9 –65.9
21.0 7.4 –49.4 –67.4
22.5 6.2 –50.9 –68.9
Audio Outputs 1 & 2
Signal levels
Signal
levels
Absolute max output
level
Nominal
level
Input
menu
level
setting
[dB] [Vpp] [dBu] [dBu]
0.0 1.2 –5.5 –23.5
1.5 1.4 –4.0 –22.0
3.0 1.6 –2.5 –20.5
4.5 1.9 –1.0 –19.0
6.0 2.3 0.5 –17.5
7.5 2.8 2.0 –16.0
9.0 3.3 3.5 –14.5
10.5 3.9 5.0 –13.0
12.0 4.6 6.5 –11.5
13.5 5.5 8.0 –10.0
15.0 6.5 9.5 –8.5
16.5 7.8 11.0 –7.0
18.0 9.2 12.5 –5.5
19.5 11.0 14.0 –4.0
21.0 13.0 15.5 –2.5
22.5 15.5 17.0 –1.0
Default levels are denoted as follows:
–31.4
NoTe! The input clipping levels and
the absolute max output levels all
assume sinusoidal signals for the dBu
values.
Tip! To convert dBu values to dBV,
subtract 2.2 dB from the dBu value.
example: –10 dBu => –12.2 dBV
Audio inputs 3 & 4
NoTe! Audio inputs 3 & 4 are referred
to as Line input 1 & 2 in the API.
Audio signal levels in Vpp and dBu
Microphone inputs 1 & 2
Audio outputs 1 & 2
23
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Interfaces and Sockets – Codec 3000 MXP
Single
S-video output
Mini-DIN socket
S-video input
Mini-DIN socket
Aux. camera
Single Dual
Composite video output
RCA sockets
Composite video input RCA sockets
Doc. camera VCR
PC DVI-I input sockets
(Digital Video Interface,
Integrated digital
and analogue)
DVI output
NoTe! The system
will automatically
adapt to a PAL or
NTSC input.
DVI-I Pin-out
Pin Assignment Pin Assignment Pin Assignment
1 T.M.D.S. Data 2– 9 T.M.D.S. Data 1– 17 T.M.D.S. Data 0–
2 T.M.D.S. Data 2+ 10 T.M.D.S. Data 1+ 18 T.M.D.S. Data 0+
3 T.M.D.S. Data 2/4
Shield
11 T.M.D.S. Data 1/3
Shield
19 T.M.D.S. Data 0/5
Shield
4 T.M.D.S. Data 4– 12 T.M.D.S. Data 3– 20 T.M.D.S. Data 5–
5 T.M.D.S. Data 4+ 13 T.M.D.S. Data 3+ 21 T.M.D.S. Data 5+
6 DDC Clock 14 +5 V power 22 T.M.D.S. Clock
Shield
7 DDC Data 15 GND
(return for +5 V,
HSync and Vsync)
23 T.M.D.S. Clock+
8 Analogue Vertical
Sync
16 Hot plug detect 24 T.M.D.S. Clock–
C1 Analogue Red C2 Analogue Green C3 Analogue Blue
C4 Analogue
Horizontal Sync
C5 Analogue GND
(analogue
R, G & B return)
DVI-I pin-out
Note: TANDBERG s upports DVI- D
Single -Link, DV I-A an d DVI-I Single- Link format cables.
DVI- D cables tr ansmit digit al
T.M.D.S. signals, DVI-A cables
transmit a nalogue VGA signals
and DVI- I cables c an transmit
either digital or analo gue signals.
If your DVI cable is not long
enough, use extension ca bles.
Observe, however, that the
maximum c able leng th should not
exceed 5 m to avoid quality loss.
Formats supported on DVI-I out:
SVGA (800 × 600) 75 Hz
XGA (1024 × 76 8) 60 Hz
SXGA (1280 × 1024) 60 Hz
HD720p (1280 × 720) 50 Hz, 6 0 Hz
WXGA (1280×768) 6 0 Hz
Formats supported on DVI-I in:
SVGA (800 × 600) 60 Hz, 72 Hz , 75 Hz, 8 5 Hz
XGA (1024 × 76 8) 60 Hz, 70 Hz, 75 Hz
SXGA (1280 × 1024) 60 Hz
HD720p (1280 × 720) 50 Hz, 6 0 Hz
Levels
Composite: 1 Vpp, 75 W
S-Video (Y/C):
Y: 1 Vpp, 75 W
C (PAL): 0.3 Vpp, 75 W
C (NTSC): 0.28 Vpp, 75 W
Do as follows to get WXGA:
1 VGA Out Quality must be set to Auto.
2 VGA Monitor Format must be set to Wide.
3 PC Picture Format must be set to Normal.
If you are using TANDBERG supplied monitors this will give WXGA out
when displaying graphics.
If non-TANDBERG provided displays are used, you must in addition
execute the command:
xConguration Video Outputs AllowWXGA: On
Video Sockets
GND
RCA pin-out
External view of socket
Signal
S-video Mini-DIN pin-out
External view of socket
Pin 1: Ground (Luminance)
Pin 2: Ground (Chrominance)
Pin 3: Luminance (Y)
Pin 4: Chrominance (C)
1
3
4
2
24
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Interfaces and Sockets – Codec 3000 MXP
Camera Socket
S-video Mini-DIN pin-out
External view of socket
Pin 1: Ground (Luminance)
Pin 2: Ground (Chrominance)
Pin 3: Luminance (Y)
Pin 4: Chrominance (C)
1
3
4
2
Camera Connect the camera here. Use
a TANDBERG 3000 WAVE II Camera
cable or similar.
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
69
1
5
TANDBERG 3000 WAVE II
Camera cable pin-out
SIGNAL
NAME
RJ-45 S-VIDEO DSUB
+12V DC 8 — 4
GND 7 — 5
+12V DC 3 — 4
TXD 4 — 3
RXD 5 — 2
GND 6 — 5
GND 2 — 5
+12V DC 1 — 4
Y-GND — 1 8
C_GND — 2 1
Y — 3 9
C — 4 6
NC — — 7
Split cable for nonTANDBERG WAVE II
cameras
Non-TANDBERG
Camera cable pin-out
SIGNAL
NAME
DSUB
Camera
S-VIDEO DSUB
Codec
+12V DC 1 — 4
GND 2 — 5
+12V DC 3 — 4
TXD 4 — 3
RXD 5 — 2
GND 6 — 5
GND 7 — 5
+12V DC 8 — 4
Y-GND — 1 8
C_GND — 2 1
Y — 3 9
C — 4 6
NC — — 7
TANDBERG HD 3000
Camera cable pin-out
SIGNAL
NAME
RJ-45 DSUB
+12V DC 1
Twisted
pair
4
GND 2 1
Rx 3
Twisted
pair
2
TX 4 6
LVDS+ 5
Twisted
pair
9
LVDS– 6 3
GND 7
Twisted
pair
5
+12V DC 8 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!
Camera sid e
Codec sid e
Tip! Wherever applicable, the use
of Category 5 cabling or better is
strongly recommended! For HD camera
applications, however, Category 7.5 is
required.
25
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Interfaces and Sockets – Codec 3000 MXP
RJ-45 Connector pin-out ISDN BRI interface. ISDN I.420
(RJ-45 Jack) Basic Rate Interface
S/T (2B + D), 128 kbps per ISDN
I/F. Use any standard BRI cable
to connect the Codec to BRI.
S/T Interface
BRI Pin out
Pin 3 TX+
Pin 4 RX+
Pin 5 RX–
Pin 6 TX–
ISDN BRI sockets (not applicable to 3000 MXP Net)
Tip! Wherever applicable, the use
of Category 5 cabling or better is
strongly recommended! For HD camera
applications, however, Category 7.5 is
required.
26
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Interfaces and Sockets – Codec 3000 MXP
V35 DTE → DCE
Pin Signal name Direction Description
1 FGND
↔
Frame GND on equipment
11 SD(A)
→
Send Data / Transmit
12 SD(B)
→
Send Data / Transmit
13 RD(A)
←
Receive Data
14 RD(B)
←
Receive Data
15 SCR(A)
←
Signal Clock Receive
16 SCR(B)
←
Signal Clock Receive
17 SCT(A)
←
Signal Clock Transmit
18 SCT(B)
←
Signal Clock Transmit
19 GND
1
↔
Signal GND
22 RLSD(CD)
←
Received Line Signal Detector /
Carrier Detect
23 RLSD(GND)
1
←
Signal GND
24 RI
←
Ring Indicator
25 LOS
→
Loss of Signal (KG194)
26 DTR
→
Data Terminal Ready
1) This pin is co nnected to groun d for corre ct operations
RS449 DTE → DCE
Pin Signal name Direction Description
1 FGND
↔
Frame GND
11 SD(A)
→
Send Data
12 SD(B)
→
Send Data
13 RD(A)
←
Receive Data
14 RD(B)
←
Receive Data
15 RT(A)
←
Receive Timing
16 RT(B)
←
Send Timing
17 ST(A)
←
Send Timing
18 ST(B)
←
Send Timing
19 GND
1
↔
GND
20 TR(A)
→
Terminal Ready
21 TR(B)
→
Terminal Ready
22 RR(A)
←
Carrier Detect / Receiver Ready
23 RR(B)
←
Carrier Detect / Receiver Ready
24 IC
←
Incoming Call
25 LOS
→
Loss of Signal (KG194)
Frame GN D is connected to pi n 1 on DTE
1) This pin is co nnected to groun d for corre ct operations
X.21 DTE → DCE
Pin Signal name Direction Description
1 FGND
↔
Frame GND
11 T(A)
→
Send Data / Transmit
12 T(B)
→
Send Data / Transmit
13 R(A)
←
Received Data / Receive
14 R(B)
←
Received Data / Receive
15 S(A)
←
Signal Element Timing
16 S(B)
←
Signal Element Timing
20 C(A)
→
Terminal Ready / Control
21 C(B)
→
Terminal Ready / Control
22 I(A)
←
Carrier Detect
23 I(B)
←
Carrier Detect
Net interface socket. 1 × X.21 / V.35 / RS449
with 1 × RS366 Call Control up to 2 Mbps
Note the following:
V.10 (RS423). Fo r balanced signal s a
0 = low voltage, is de ned as terminal
A positive with respe ct to terminal B.
For unba lanced si gnals a 0 = low volt-
age, is dened a s terminal positi ve
with resp ect to GND. Cable l ength
for Leased Li ne Control should not
exceed 20 m.
R S 3 6 6 . All bala nced inputs and
outputs (A and B) use balance d line
signals accordi ng to V.11 (RS 422),
while sin gle ended s ignals are in
accord ance with V.10 (RS423). The
0 = low voltage d enitions are the
same as for V.10 ab ove. Max cable
lengt h, as for V.10 above.
X.21. Signals are as for RS 366 above.
Cable length should not exceed 50 m.
RS366 DTE → DCE
Pin Signal name Direction 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
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
91
10
19
18
26
Net socket (applies to 3000 MXP Net only)
27
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Interfaces and Sockets – Codec 3000 MXP
Ethernet LAN (RJ-45 Jack) interface (10/100 Mb).
Up to 4 or 6 Mbps, depending on the bandwidth option installed. Use any standard Ethernet cable to
connect the Codec to a LAN.
If no LAN is available and the Codec is connected
directly to a computer, use a crossover cable.
USB interface.
For future use.
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
conguring a back-to-back connection between the PC and the Codec,
make sure both static IP addresses exist on the same subnet.
Data port
Pin Signal name Direction
1 Carrier
detect, CD
From DCE
2 Receive data,
RXD
From DCE
3 Transmit
data, TXD
To DCE
4 Data terminal
ready, DTR
From DCE
5 Signal GND
6 Data set
ready, DSR
From DCE
7 Ready to
send, RTS
To DCE
8 Clear to
send, CTS
From DCE
9 Ring
indicator, RI
From DCE
Data port. The Data port is
implemented as a Digital Circuit
Terminating Equipment (DCE).
9-pin D-SUB pin-out
External view of socket
Ethernet cable
1 ---------- 1
2 ---------- 2
3 ---------- 3
6 ---------- 6
1 1
2 2
3 3
6 6
Wiring diagram
standard cable
Wiring diagram
crossover cable
PC card. Wireless LAN PC card
may be inserted here.
RJ-45 Connector pin-out
Network Interface Sockets
Tip! Wherever applicable, the use
of Category 5 cabling or better is
strongly recommended! For HD camera
applications, however, Category 7.5 is
required.
69
1
5
28
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Interfaces and Sockets – Codec 3000 MXP
Power cord socket.
Accepts 12 V DC / 4.3 A
Power switch
CauTioN! This equipment
must be earthed!
Power Socket & On/Off Switch
We rec ommen d that you check out the
TANDBE RG web s ite regularly for up dated
versions of this manual:
http://ww w.tandberg.com/support/
documentation.php
Interfaces and Sockets – Codec 6000 MXP
This part of the manual provides an in-depth presentation
of the rear panel sockets and interfaces of the Codec
6000 MXP, including the audio signal levels and the
formats supported.
30
Interfaces and Sockets – Codec 6000 MXP
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Audio sockets
Video sockets
Rear Panel Socket– and Interface Groups
Network interface sockets
Power socket
and On/Off switch
31
Interfaces and Sockets – Codec 6000 MXP
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Audio Sockets
Microphone Inputs
Nos. 1–3.
Three balanced
microphone inputs for
electret microphones
balanced, 24V phantom
powered via XLR
connectors.
The phantom powering
of XLR socket No. 3 can
be switched off. The
Mic. input No. 3 will
then be a balanced line
level input.
Tip! Unused, but connected
audio inputs should be set
to Off to avoid unwanted
audio/noise.
Use Audio Input No. 4
to connect to an external
microphone amplier or to
an external mixer.
Use Audio Input No. 5 to
connect to external playback
devices or to telephone add-on
hybrids. For systems congured
with stereo I/O, connect the
VCR/DVD left channel to this
input.
Use Audio Input No. 6 to
connect a VCR or DVD player
to the system. For systems
congured with stereo I/O,
connect the VCR/DVD right
channel to this input.
Tip! Audio inputs Nos. 5
& 6 are not equipped with
acoustic echo canceller.
Connecting microphones to
these inputs can therefore
not be recommended.
Use Audio Out put No. 2 (the
AUX output) to p rovide a mixe d
signal consisting of audio f rom
the local si de (AUX input not
included) a nd audio from the
far end.
This outpu t should be use d
when connecting a telephone
add- on system.
For system c ongured wi th
stereo I/O and with S PDIF†
active on Audio Outpu t No. 1,
this outpu t will provid e the VCR
left channel stereo informatio n.
For systems c ongured wi th
stereo I/O, stereo spe akers and
SPDIF† not active, t his output
will provid e the right channel of
the loudsp eaker signal (t he left
channel will b e provided on the
Audio Outp ut No. 1).
Use Audio Out put No. 3
(the VCR outp ut) to provid e
a mixed signal consisting
of audio from t he local sid e
(VCR inpu t not include d)
and audio from the far end.
This outpu t should be use d
when connecting a VCR to
the system.
For system c ongured wi th
stereo I/O and with S PDIF†
active on Audio Outpu t No.
1, this outpu t will provide
the VCR right channel
stereo information.
For systems c ongured
with stere o I/O, stereo
speakers and SPDIF† not
active, this o utput will
provide t he mix of lef t and
right channel of the VCR
out signal.
XLR pin-out
External view of socket
Pin 1: Gnd
Pin 2: Hot
Pin 3: Cold/neutral
12
3
Use Audio Out put No. 1 to
provide a mi xed signal of au dio
from far en d and local ex ternal
devices connected to input 5 &
6, in addition to dial tones.
This outpu t should be co nnected
to the local l oudspeaker system,
which may, or may not, i nclude
the TANDBERG D igital Natural
Audio Module.
For systems c ongured wi th
stereo speakers and SPD IF†
active, the left and right channel
of the loudsp eaker signal will
both be provided on this o utput.
For systems c ongured wi th
stereo speakers and SPD IF†
not active, t he left ch annel of
the loudsp eaker signal w ill be
present on t his output . The right
loudspeaker channel will b e
provided on Audio Output No. 2.
†
SPDIF (Sony/Philips Digital Interface)
is used by the Digital Natural Audio module.
Stereo Settings
Settings Output Response
Out 1
mode
Stereo
I/O mode
Stereo
speakers
Audio Out 1 Audio Out 2 Audio
Out 3
Analogue Off Off Loudspeaker
mono
Aux VCR
Analogue Off On Loudspeaker L Loudspeaker R VCR
Analogue On Off Loudspeaker
mono
VCR L VCR R
Analogue On On Loudspeaker L Loudspeaker R VCR
SPDIF
Off Off
Loudspeaker
mono
Aux VCR
SPDIF Off On Loudspeaker
L & R
Aux VCR
SPDIF
On Off
Loudspeaker
mono
VCR L VCR R
SPDIF
On On
Loudspeaker
L & R
VCR L VCR R
Tip! Audio signal levels
expressed in volts and dBu
can be found overleaf.
NoTe! Audio
inputs 4–6
are referred
to as Line
input 1–3 in
the API.
Hardware Information
Microphone(s) Audio Input(s) Audio Outputs
Signal type Balanced Unbalanced
Socket XLR-F RCA/phono
Input impedance
2400 W
(pin 2–3)
10 kW
Output impedance
680 W
Max input level when set to
min. input level
83 mVpp 15.5 Vpp
Max output level when set to
max. output level
15.5 Vpp
Max input level when set to
max. input level
6.2 mVpp 1.2 Vpp
Max output level when set to
min. output level
1.2 Vpp
Gain range 22.5 dB (16 steps of 1.5 dB)
Phantom power 24 V ± 5 %
Phantom power resistor
pin 2
1200 W
Phantom power resistor
pin 3
1200 W
Max phantom power current 12 mA
RCA pin-out
External view of socket
GNDSignal
32
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Interfaces and Sockets – Codec 6000 MXP
Audio Signal Levels in Vpp and dBu
Audio Inputs 4, 5 & 6
Signal levels
Signal
levels
Clipping levels Nominal
level
Input
menu level
setting
[dB] [Vpp] [dBu] [dBu]
0.0 15.5 17.0 –1.0
1.5 13.0 15.5 –2.5
3.0 11.0 14.0 –4.0
4.5 9.2 12.5 –5.5
6.0 7.8 11.0 –7.0
7.5 6.5 9.5 –8.5
9.0 5.5 8.0 –10.0
10.5 4.6 6.5 –11.5
12.0 3.9 5.0 –13.0
13.5 3.3 3.5 –14.5
15.0 2.8 2.0 –16.0
16.5 2.3 0.5 –17.5
18.0 2.0 -1.0 –19.0
19.5 1.6 -2.5 –20.5
21.0 1.4 -4.0 –22.0
22.5 1.2 -5.5 –23.5
Microphone Inputs 1, 2 & 3
Signal levels
Signal
levels
Clipping levels Nominal
level
Input
menu level
setting
[dB] [mVpp] [dBu] [dBu]
0.0 83.0 –28.4 –46.4
1.5 69.8 –29.9 –47.9
3.0 58.8 –31.4 –49.4
4.5 49.4 –32.9 –50.9
6.0 41.6 –34.4 –52.4
7.5 35.0 –35.9 –53.9
9.0 29.4 –37.4 –55.4
10.5 24.8 –38.9 –56.9
12.0 20.8 –40.4 –58.4
13.5 17.5 –41.9 –59.9
15.0 14.8 –43.4 –61.4
16.5 12.4 –44.9 –62.9
18.0 10.4 –46.4 –64.4
19.5 8.8 –47.9 –65.9
21.0 7.4 –49.4 –67.4
22.5 6.2 –50.9 –68.9
This specication is always valid for mic 1 and 2, and
for mic 3 if mic level setting is selected.
Microphone Input 3
Line level mode signal levels
Signal
levels
Clipping levels Nominal
level
Input
menu level
setting
[dB] [Vpp] [dBu] [dBu]
0.0 15.5 17.0 –1.0
1.5 13.0 15.5 –2.5
3.0 11.0 14.0 –4.0
4.5 9.2 12.5 –5.5
6.0 7.8 11.0 –7.0
7.5 6.5 9.5 –8.5
9.0 5.5 8.0 –10.0
10.5 4.6 6.5 –11.5
12.0 3.9 5.0 –13.0
13.5 3.3 3.5 –14.5
15.0 2.8 2.0 –16.0
16.5 2.3 0.5 –17.5
18.0 2.0 –1.0 –19.0
19.5 1.6 –2.5 –20.5
21.0 1.4 –4.0 –22.0
22.5 1.2 –5.5 –23.5
This specication is valid for mic 3 if line level setting is
selected.
Audio Outputs 1, 2 & 3
Signal levels
Signal
levels
Absolute max output
level
Nominal
level
Input
menu level
setting
[dB] [Vpp] [dBu] [dBu]
0.0 1.2 –5.5 –23.5
1.5 1.4 –4.0 –22.0
3.0 1.6 –2.5 –20.5
4.5 1.9 –1.0 –19.0
6.0 2.3 0.5 –17.5
7.5 2.8 2.0 –16.0
9.0 3.3 3.5 –14.5
10.5 3.9 5.0 –13.0
12.0 4.6 6.5 –11.5
13.5 5.5 8.0 –10.0
15.0 6.5 9.5 –8.5
16.5 7.8 11.0 –7.0
18.0 9.2 12.5 –5.5
19.5 11.0 14.0 –4.0
21.0 13.0 15.5 –2.5
22.5 15.5 17.0 –1.0
This specication is always valid for output 2 and 3,
and for output 1 at volume setting 15.
Default levels are denoted as follows:
–31.4
NoTe: The input clipping levels and the
absolute max output levels all assume
sinusoidal signals for the dBu values.
Tip: To convert dBu values to dBV, subtract
2.2 dB from the dBu value.
example: –10 dBu ≡ –12.2 dBV
Microphone
inputs 1–3 Audio outputs 1–3
Audio inputs 4–6
NoTe: Audio inputs 4–6 are referred to as Line
input 1–3 in the API.
33
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Interfaces and Sockets – Codec 6000 MXP
DVI-I Pin-out
Pin Assignment Pin Assignment Pin Assignment
1 T.M.D.S. Data 2– 9 T.M.D.S. Data 1– 17 T.M.D.S. Data 0–
2 T.M.D.S. Data 2+ 10 T.M.D.S. Data 1+ 18 T.M.D.S. Data 0+
3 T.M.D.S. Data 2/4
Shield
11 T.M.D.S. Data 1/3
Shield
19 T.M.D.S. Data 0/5
Shield
4 T.M.D.S. Data 4– 12 T.M.D.S. Data 3– 20 T.M.D.S. Data 5–
5 T.M.D.S. Data 4+ 13 T.M.D.S. Data 3+ 21 T.M.D.S. Data 5+
6 DDC Clock 14 +5 V power 22 T.M.D.S. Clock
Shield
7 DDC Data 15 GND
(return for +5 V,
HSync and Vsync)
23 T.M.D.S. Clock+
8 Analogue Vertical
Sync
16 Hot plug detect 24 T.M.D.S. Clock–
C1 Analogue Red C2 Analogue Green C3 Analogue Blue
C4 Analogue
Horizontal Sync
C5 Analogue GND
(analogue
R, G & B return)
DVI-I pin-out
Note: TANDBERG s upports DVI- D
Single -Link, DV I-A an d DVI-I Single- Link format cables.
DVI- D cables tr ansmit digit al
T.M.D.S. signals, DVI-A cables
transmit a nalogue VGA signals
and DVI- I cables c an transmit
either digital or analo gue signals.
If your DVI cable is not long
enough, use extension ca bles.
Observe, however, that the
maximum c able leng th should not
exceed 5 m to avoid quality loss.
Formats supported on DVI-I out:
SVGA (800 × 600) 75 Hz
XGA (1024 × 76 8) 60 Hz
SXGA (1280 × 1024) 60 Hz
HD720p (1280 × 720) 50 Hz, 6 0 Hz
WXGA (1280×768) 6 0 Hz
Formats supported on DVI-I in:
SVGA (800 × 600) 60 Hz, 72 Hz , 75 Hz, 8 5 Hz
XGA (1024 × 76 8) 60 Hz, 70 Hz, 75 Hz
SXGA (1280 × 1024) 60 Hz
HD720p (1280 × 720) 50 Hz, 6 0 Hz
Levels
Composite: 1 Vpp, 75 W
S-Video (Y/C):
Y: 1 Vpp, 75 W
C (PAL): 0.3 Vpp, 75 W
C (NTSC): 0.28 Vpp, 75 W
Do as follows to get WXGA:
1 VGA Out Quality must be set to Auto.
2 VGA Monitor Format must be set to Wide.
3 PC Picture Format must be set to Normal.
If you are using TANDBERG supplied monitors this will give WXGA out
when displaying graphics.
If non-TANDBERG provided displays are used, you must in addition
execute the command:
xConguration Video Outputs AllowWXGA: On
Video Sockets
GND
RCA pin-out
External view of socket
Signal
S-video Mini-DIN pin-out
External view of socket
Pin 1: Ground (Luminance)
Pin 2: Ground (Chrominance)
Pin 3: Luminance (Y)
Pin 4: Chrominance (C)
1
3
4
2
Single Dual
S-video output
Mini-DIN sockets
S-video input Mini-DIN sockets
Main camera Aux. camera
Single Dual
Composite video output
RCA sockets
Composite video input RCA sockets
Doc. camera VCR
PC DVI-I input sockets
(Digital Video Interface,
Integrated digital
and analogue)
Single Dual
DVI output
sockets
The system will
automatically
adapt to a PAL or
NTSC input.
Note that the S-Video/Composite outputs on the
6000 MXP are now by default turned off from
factory.
Ref. xConguration Video Outputs TV [1..2] Mode
34
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Interfaces and Sockets – Codec 6000 MXP
Net Interface Socket
Net interface socket. 1 × X.21 / V.35 / RS449
with 1 × RS366 Call Control up to 2 Mbps
HD D-SUB 26 pin-out
External view of socket
91
10
19
18
26
V.35 DTE - DCE
Pin Signal Name Description
1 FGND Frame GND on equipment
11 SD(A) Send Data / Transmit
12 SD(B) Send Data / Transmit
13 RD(A) Receive Data
14 RD(B) Receive Data
15 SCR(A) Signal Clock Receive
16 SCR(B) Signal Clock Receive
17 SCT(A) Signal Clock Transmit
18 SCT(B) Signal Clock Transmit
19 GND1Signal GND
22 RLSD(CD) Received Line Signal
Detector / Car rier Detect
23 RLSD(GND)1Signal GND
24 RI Ring Indicator
25 LOS Loss of Signal (KG194)
26 DTR Data Terminal Ready
1) This pin is co nnected to groun d for corre ct
operations
RS449 DTE - DCE
Pin Signal Name Description
1 FGND Frame GND
11 SD(A) Send Data
12 SD(B) Send Data
13 RD(A) Receive Data
14 RD(B) Receive Data
15 RT(A) Receive Timing
16 RT(B) Send Timing
17 ST(A) Send Timing
18 ST(B) Send Timing
19 GND1GND
20 TR(A) Terminal Ready
21 TR(B) Terminal Ready
22 RR(A) Carrier Detect / Receiver Ready
23 RR(B) Carrier Detect / Receiver Ready
24 IC Incoming Call
25 LOS Loss of Signal (KG194)
Frame GN D is connected to pi n 1 on DTE
1) This pin is co nnected to groun d for corre ct operations
Note the following:
V.10 (RS423). For balanced sign als a
“0” = low volta ge, is dened as ter minal
A positive w ith respe ct to terminal B . For
unbalanc ed signals a “0” = lo w voltage, is
dened as te rminal posi tive with re spect
to GND. Cable l ength fo r Leased Lin e
Control should not exceed 20 m.
R S 3 6 6 . A ll balanced inputs and ou tputs
(A and B) use balan ced line sign als
according to V.11 (RS 422), while single
ended sig nals are in acc ordance wi th V.10
(RS423). The “0” = low vol tage deni tions
are the sam e as for V.10 above. Max
cable len gth, as for V.10 above.
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
7 NB1 Digit Bit 1
8 NB2 Digit Bit 2
9 NB4 Digit Bit 4
10 NB8 Digit Bit 8
X.21 DTE - DCE
Pin Signal Name Description
1 FGND Frame GND
11 T(A) Send Data / Transmit
12 T(B) Send Data / Transmit
13 R(A) Received Data / Receive
14 R(B) Received Data / Receive
15 S(A) Signal Element Timing
16 S(B) Signal Element Timing
20 C(A) Terminal Ready / Control
21 C(B) Terminal Ready / Control
22 I(A) Carrier Detect
23 I(B) Carrier Detect
35
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Interfaces and Sockets – Codec 6000 MXP
Network Interface Sockets
ISDN BRI interface. ISDN I.420
(RJ-45 Jack) Basic Rate Interface
S/T (2B + D), 128 kbps per ISDN
I/F. Use any standard BRI cable
to connect the Codec to BRI.
ISDN PRI interface. 1 × PRI (RJ-45 Jack) Primary
Rate & Leased Line E1/T1 (G.703) Interface up to
2 Mbps. 1 × PRI (RJ-45 Jack) Primary Rate (for future
use). Use any standard PRI cable to connect the
Codec to PRI.
Tip! Wherever applicable, the use
of Category 5 cabling or better is
strongly recommended! For HD camera
applications, however, Category 7.5 is
required.
Ethernet LAN (RJ-45 Jack) interface (10/100 Mb).
Up to 4 or 6 Mbps, depending on the bandwidth option installed. Use any standard Ethernet cable to
connect the Codec to a LAN.
If no LAN is available and the Codec is connected
directly to a computer, use a crossover cable.
Ethernet cable
1 ---------- 1
2 ---------- 2
3 ---------- 3
6 ---------- 6
1 1
2 2
3 3
6 6
Wiring diagram
standard cable
Wiring diagram
crossover cable
RJ-45 Connector pin-out
E1/T1 Interface
PRI Pin-Out Crossover
PRI cable
Pin 1 RX+ 4
Pin 2 RX– 5
Pin 4 TX+ 1
Pin 5 TX– 2
S/T Interface
BRI Pin-Out
Pin 3 TX+
Pin 4 RX+
Pin 5 RX–
Pin 6 TX–
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
conguring a back-to-back connection between the PC and the Codec,
make sure both static IP addresses exist on the same subnet.
36
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Interfaces and Sockets – Codec 6000 MXP
Camera Sockets
S-video Mini-DIN pin-out
External view of socket
Pin 1: Ground (Luminance)
Pin 2: Ground (Chrominance)
Pin 3: Luminance (Y)
Pin 4: Chrominance (C)
1
3
4
2
9-pin D-SUB pin-out
External view of socket
TANDBERG WAVE II
Camera cable pin-out
SIGNAL
NAME
RJ-45 DSUB
+12V DC 8 4
GND 7 5
+12V DC 3 4
TXD 4 3
RXD 5 2
GND 6 5
GND 2 5
+12V DC 1 4
TANDBERG HD 6000
Camera cable pin-out
SIGNAL
NAME
RJ-45 DSUB
+12V DC 1
Twisted
pair
4
GND 2 5
Rx 3
Twisted
pair
2
TX 6 3
LVDS+ 4
Twisted
pair
1
LVDS– 5 6
GND 7
Twisted
pair
5
+12V DC 8 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!
Tip! Wherever applicable, the use
of Category 5 cabling or better is
strongly recommended! For HD camera
applications, however, Category 7.5 is
required.
69
1
5
37
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Interfaces and Sockets – Codec 6000 MXP
Data Ports
USB interface.
For future use.
Data Ports
Data port 1 Data port 2
Pin Signal name Direction Signal name Direction
1 Carrier detect,
CD
From DCE Car rier detect, CDFrom DCE
2 Receive data,
RXD
From DCE Receive data,
RXD
From DCE
3 Transmit data,
TXD
To DCE Transmit data,
TXD
To DCE
41Data terminal
ready, DTR
From DCE 12 V / 1 A
5 Signal GND
Signal GND
6 Data set ready,
DSR
From DCE
Data set ready,
DSR
From DCE
7 Ready to send,
RTS
To DCE
Ready to send,
RTS
To DCE
8 Clear to send,
CTS
From DCE
Clear to send,
CTS
From DCE
9 Ring indicator,
RI
From DCE
Ring indicator,
RI
From DCE
1) The TANDBERG main camera is normally connected to data port 2 and pin No. 4
provides 12 Vd c / 1 A to the main camera. Otherwise the pin-outs are the same for the
two data ports.
Data port 1 (upper) and 2 (lower). The Data ports
are implemented as Digital Circuit Terminating
Equipment (DCE).
NoTe! The TANDBERG main camera is normally
connected to data port 2 and pin No. 4 provides
12 Vd c / 1 A to the main camera. Otherwise the pinouts are the same for the two data ports.
9-pin D-SUB pin-out
External view of socket
69
1
5
38
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Interfaces and Sockets – Codec 6000 MXP
Power Socket & On/Off Switch
Power cord socket
Accepts 100–240 V 50–60 Hz
1 A max.
Power switch
CauTioN! This equipment must
be earthed!
We rec ommen d that you check out the
TANDBE RG web s ite regularly for up dated
versions of this manual:
http://ww w.tandberg.com/support/
documentation.php
About the TANDBERG API
The heart of the API is the TANDBERG API -Engine. This is
where all information is stored and processed. The APIengine 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.
40
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Introduction
About the TANDBERG API
The hear t of the API is t he TANDBERG
API- Engine. This is where all information is
stored and p rocessed. The API -engin e can
be access ed by an easy- to- use Command
Line Inter face called XACLI using RS 232
or Telnet, or by the TANDB ERG XML API
Service (TX AS) over HT TP/HTTPS.
API-Engin e
XACLI TXAS
R S 2 3 2
Telnet
HTTP
HTTPS
Working with the API -engine is very similar
to working with catalo gues and file s on a
computer. All inf ormation is s tored in a hierarchic tree stru cture which is accessibl e
from dif ferent interfaces.
When accessing the API-e ngine using
XACLI (RS 232 or Telnet), the information
is format ted in a propr ietary Command Lin e
style or in XML formatting.
When accessing the API-e ngine using the
TXAS interf ace (HTT P/HTTPS), XML/SOAP
format ting is suppo rted.
This is similar to viewing files on a computer; acces sing catalo gues on a Windows
computer using the Command Prompt
gives a dif ferent view t han using Win dows
Explor er, but the information is the same.
NOTE! New featur es on the TANDBE RG
MXP will be suppor ted on X ACLI only.
Basic Principles
The TANDBERG API Engine
The TANDBERG API-Engine is optimized for easy, yet advanced, machine-
machine interaction b etween a TAND BERG system an d an external control
application.
The main feat ures can be sum marized to:
Structuring of information•
Addressing using XPat h (XML Pat h Language) or TANDB ERG SimpleP ath•
Feedback •
Structuring of Information
An application programming inte rface (A PI) can be see n as a gate where in formation is exchanged between two systems – a control application and a target
system.
The control application transmits instructions to the target system, while the
target sys tem supplies in formation about how th ese instructions are exec uted,
in addition to other system related infor mation.
Conseque ntly, the exchange of information can be div ided into:
Information flowing 1. from target . This we call READ information (R). The (R)
should not be c onfused wi th the (r) used to indica te required p arameters in
the Commands tables.
Information flowing 2. to targe t. This we call WRITE information (W).
If we now look at t he TANDBERG sys tems we can identify three main ty pes of
information
READ• information (R)
WRITE• information (W)
READ-WRITE• information (RW)
(R) READ information. This is Status Information about the system and system
process es, i.e. informat ion generated by the system.
Typical examples include: status about on going calls, net work status, conference stat us etc.
All status information is structured in a hierar chy, making up a database con stantly b eing update d by the system to r eflect process cha nges.
(W) WRITE information. This is Command Information th e user/control applica -
tion supply to initiate an ac tion.
Typical examples include: instructing the system to place a call, assigning floor
to a specif ic site, disconnecting a call etc.
A command is us ually followed by a set of param eters to spec ify how th e given
action is to be executed.
(RW) READ -WRITE information. T his is Configuration Info rmation de fining sys -
tem settings. This information can both be supplie d and read by th e user/control application. Typical ex amples include: default c all rate, baud ra te of a serial
port, e nabling /disabling of variou s features etc.
All configuration information is structured in a hierarc hy making up a dat abase
of system set tings. But fo r the Configuration information, t he data in th e database can only be updated by t he user/control applic ation.
Addressing Using XPath or TANDBERG SimplePath
To address information in the hierarchic structure of Status and Configuration
information, the TANDBERG systems support abbreviated XML Path Language
(XPath) and a p ropriet ary notation called TAND BERG Simple Path (only available
using XACLI).
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
hierarchy (for example all inf ormation available for a gi ven call).
Feedback
Feedback is an extrem ely power ful featur e where the TAND BERG system
actively r eturns updated status and configur ation infor mation to th e user/
control application whenever changes occur.
The user/control appli cation can specify what par ts of the status and configuration hierarchies it wants to monitor by using XPath. The user/control application
can thereby limit the amount of information it receives from the target system to
only those parts being of interest for the given application. This will also reduce
the load on the link connecting the systems.
Feedback is suppor ted on both X ACLI (RS232/Telnet) and TXA S (HTTP/
HTTPS) simultaneously.
The system us es TANDBERG Simp lePath wh en presenting configurations.
XPath and TANDBERG SimplePath are describ ed more tho roughly lat er in this
section of t he manual.
The stru cturing of information together wit h XPath and TAND BERG SimplePath
for addressing, makes up powerful features like searchability and set ting of
multiple ins tances of a configurat ion.
Examples are provid ed overleaf.
41
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Example showing Ser ial Port co nfigurat ions of a TANDBERG
6000 MXP codec, using the standard XACLI formatt ing for
configurations:
xconfiguration serialport
*c xConfiguration SerialPort 1 BaudRate:
5760 0
*c xConfiguration SerialPort 1 Parity: None
*c xConfiguration SerialPort 1 DataBits: 8
*c xConfiguration SerialPort 1 StopBits: 1
*c xConfiguration SerialPort 1 Mode: Control
*c xConfiguration SerialPort 2 BaudRate: 9600
*c xConfiguration SerialPort 2 Parity: None
*c xConfiguration SerialPort 2 DataBits: 8
*c xConfiguration SerialPort 2 StopBits: 1
*c xConfiguration SerialPort 2 Mode: Auto
OK
Example: To address the BaudRate element of se rial por t 2:
XPath
Each level is s eparated with a slash (‘/’). Item numbers are
added in br ackets af ter the element name:
SerialPort[2]/BaudRate
Example
xconfiguration serialport[2]/baudrate
*c xConfiguration SerialPort 2 BaudRate: 9600
OK
TANDBERG Sim plePath
Both levels an d item numbe rs are separ ated with wh itespac es:
SerialPort 2 BaudR ate
Example
xconfiguration serialport 2 baud rate
*c xConfiguration SerialPort 2 BaudRate: 9600
OK
About the TANDBERG API
The TANDBERG MXP als o suppor ts the RS 232/Telnet Datapor t Interf ace that was s upported on the Classic systems.
You may use any mixtu re of Classic Da tapor t commands a nd
XACLI commands on th e same RS232/Telnet s ession. A
multitude of the commands overlaps, b ut XACLI offers mo re
flexibillity and gives access to the latest featur es suppor ted
by the system.
We recommend the use of XACLI commands whenever
you write new control sys tem modules an d whenever yo u add
new features into existing control modules, but ther e is no
need to to rewr ite already existing control modules based on
Classic commands.
The XACLI API is described in detail in this section of the User
Guide. The Classic Dataport Interface is described in the
TANDBERG 770-8000MXP API (Dataport User Guide), which is
available separately.
NOTE! New featur es on the TANDBE RG MXP will be sup -
porte d on XACLI o nly.
EXAM PLE: To configure t he baudrate of serial por t 1 to
9600:
Classic Dataport: sport data1 9600
XACLI: xconfiguration serialport 1 baudrate:
9600
Example 1
Example 2
What Happened to the RS 232/Telnet Dataport
Interface Suppor ted on the Classic Systems?
42
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
The RS 232 p ort is a 9 -pin, female, D-sub connec tor located
on the back of t he TANDBERG MXP. The port is conf igured
as a DCE (Data C ommunications Equipment). The RS 232
port is d efault set to 9 600 baud, 8 data bits, none p arity
and 1 stop bit from factor y. The RS 232 p ort is also r eferred
to as the DATA PO RT.
The RS 232 D atapor t on the 60 00 MXP Cod ec
The RS 232 D atapor t on the 30 00 M X P Codec
See also the p ages on the 30 00 MXP Dataports and t he
6000 MXP Datapor ts in this User Gui de. Note that one of
the RS 232 p orts of t he 6000 MXP Codec (the lower) is used
as a camera c ontrol socket.
XACLI can be access ed throug h Telnet via the LAN interf ace
or throug h RS 232 by connecting a se rial cable to t he serial
interf ace connector, referred to as t he Dataport. Eight Telnet
sessions ca n be connec ted to the TANDBE RG MXP simult aneously, in addition to the RS 232 connection.
XACLI
About the TANDBERG API
Accessing X ACLI
The pin out s for the RS 232 are defined in the tab les to the
right. Ob serve th at the DTE (Dat a Terminal Equipme nt), could
be a PC or any oth er device capable of ser ial communic ation.
NOTE! A straig ht-throu gh cable sho uld be used between the
TANDBERG MX P’s RS 232 por t and the DTE.
The lower table shows the r ecommended cable -wirin g
scheme wh en connecting the TANDBERG MXP to a PC
through RS 232.
DTR and RTS are i gnored. DSR, CD, and CTS are always asserted, while RI is not use d.
Connecting to XACLI using the Dataport (RS 232)
Hardware & Cabling (RS 232)
Pin Signal name Direction
1 Car rier detect, CD
From DCE
2 Receive data, RXD
From DCE
3 Transmit data, TXD
To DCE
4 Data ter minal ready, DTR
From DCE
5 Signal GND
6 Data set ready, DSR
From DCE
7 Ready to send, RTS
To DCE
8 Clear to send, CTS
From DCE
9 Ring indicator, RI
From DCE
TANDBERG MXP
DCE, 9 pin
Direction PC
DTE, 9 pin
1 CD
→
1 CD
2 RD
→
2 RD
3 TD
←
3 TD
4 DTR
←
4 DTR
5 GND
↔
5 GND
6 DSR
→
6 DSR
7 RTS
←
7 RTS
8 CTS
→
8 CTS
9 RI
→
9 RI
Troubleshooting (RS 232)
If communication cann ot be established between the PC/
terminal an d the TANDBERG M XP’s Datapor t, the foll owing
should be ch ecked:
Verify th at the serial c able is a straight-through 9-pin to •
9-p in cable
Confirm that the configuration of the PC/termin al’s •
serial RS 232 port is identical to the configuration of t he
TANDBERG MX P RS 232 por t.
Verify th at the PC/termin al’s serial RS 232 port is working •
properl y by connecting it back- to- back to anoth er PC/
terminal an d send chara cters in bot h directions.
Data Port (RS 232)
Cable wiring TANDBERG MXP ↔ PC via RS 232
43
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
?
- User Commands about dumph221 layout-keyboard prisearch
access duovideo locald n protect
aim echoctrl los-duration rinfo
alrtvol enable los-inhibit rnum ber
ansdelay encmode los-initial screensaver
audioagc encrypt los-polarity selfview
audiofeature encstatus los-retry sendnum
audiofeedback eventlog maxcall services
audioin extcam mcucom mand snm p
audiolevel extcap mcudirectory spid
audiomix extna me mculine spkr
audiomo dule extswitch mcustat sport
audioout fallback menupassword sstring
autoans fecc mic statin
automute feedback monstat statout
autopip feinfo msn still
beep fevidsrc multisite streaming
bondingtimer g703settings netclock strictpassword
boot globdirectory netctrl sub
callstatus h239 netdtrpulse syslog
camcenter h323alias netisdn system nam e
cam move h323callmanager netpri telephony
campos h323gatekeeper netprole teltone
camsettings h323mtu netstat test
camsleepmode h323nat nettype traceroute
camtrack h323ports optionkey vgaout
chanstat h323prex pardial vidfeature
chat h323qos ping vidin
custominfo h323rate pip vidname
defcall h323status pldownspeed vidtone
defvalues h331m ode preset-activate v nc
delbox help preset-list vol
dial ifcong preset-store websnapshots
directory ipaddress pressource xcommand
disable ipassignment pricable xconguration
disc ipconictcheck pricrc4 xdirectory
dispbox iplr prihighch xev ent
disppara m ippassword prilowch xfeedback
disptxt irctrl prim axcha n xg etx ml
dltxt isdntrace prinsf xhistor y
donotdist key prinu mber xpreferences
downspeed language prinum brange xstatus
dualmon
OK
All root com mands prexed with an ‘x’ belong to the X ACLI interface.
XACLI – the Basics
About the TANDBERG API
Root Commands
By typing ? or help af ter connecting to the
TANDBERG MX P using RS 232/Telnet, the
system will list all suppor ted root com mands.
All root commands pref ixed with an x
belongs to th e XACLI interfac e. These are
shown in orange c olour in the table to the
right. All other root commands belong to
the Classic D atapor t Inter face (described in
a separate d ocument).
NOTE! Classic Da tapor t commands and
XACLI commands can b e used side by side.
However, the use of X ACLI commands is
recommended whenever writing new control
system modules and whenever adding new
features into existing control module s, but
there is no ne ed to rewrite ex isting cod e
based on the C lassic commands.
NOTE! New featur es on the TANDBE RG
MXP will be suppor ted on X ACLI only.
44
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
XACLI – Main Types of Commands
About the TANDBERG API
About Main Types of Commands
The XACLI is divided into three main t ypes
of commands (and a fourth – s ee below),
reflecting the information t ypes supported
by the TANDBERG API Engine.
The main ty pes are:
Configur ation- type commands•
Status -type commands•
Command -typ e commands•
In additio n to the above sets of command s,
XACLI support s the followin g set of special
commands:
xfeedback is a command used to sp ecify
what par ts of the con figurati on and status
hierarchies to monitor. Feedback will onl y
be issued on t he RS 232/ Telnet for which it
is specif ied. If conne cting to the TAND BERG
MXP with multipl e RS 232/Telnet s essions,
each sessio n can defin e feedback individu all y.
More on this c an be found in xfeedback.
xpreferences is used to set vari ous prefer-
ences for the RS 232/Telnet s essions. Eac h
session can d efine pre ferences in dividuall y.
IMPORTANT! This command has various
settings to define the formatt ing of the X ACLI
output. I t is therefor e important to define settings to match t he parser used on the control
system. X ACLI is designed to make parsing of
data from the TANDBERG MXP ver y simple.
More on this c an be found in xpreferences.
xget xm l gives a ccess to the ex act same
informat ion as the Main t ypes of commands
(xstatus, xhistory, xconf iguration etc.), but
returns th e informati on XML form atted.
More on this c an be found in x getxml.
Commands r eturning information a bout
the system and system pro cesses, i.e.
informat ion generated by the system. E.g.
status abo ut ongoing calls, network status,
conferen ce status etc. All status information is stru ctured in a hierarchy, making up
a database constantl y being upda ted by
the system to r eflect system and process
changes.
Suppor ted Status-ty pe comman ds:
xStatu• s
xHistor• y
xEven• t
Commands d efining system settings.
Configur ation- type commands are either
supplied or r ead by the user. E.g. default
callrate, bau drate of a serial port, e nabling/disabling of various fe atures etc.
All Confi gurations are structured in a
hierarchy making up a dat abase of syste m
settings.
Suppor ted Conf iguration -typ e commands:
xConfiguratio• n
xDirector• y
Commands i nstructing the system to perform an act ion. E.g. inst ructing t he system
to place a call, assigning floor to a specific
site, disconn ecting a call e tc. A command
is usually followed by a set of par ameters
to specif y how the giv en action is to b e
executed.
Suppor ted Comma nd-t ype commands:
xComman• d
Status Type Commands
Configuration Type Commands Command Type Commands
Special Commands
45
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
All Confi gurations ar e organized in a hi erarchic t ree structure.
To get an overview of accessibl e top-level confi guration ele ments within a
configur ation- type command, ty pe ? or help af ter the co nfigurat ion-t ype com mands (xconfiguration/xdirectory), as shown in t he example to th e right.
TIP! To list all suppor ted conf igurations w ith corre sponding va luespace:
xConguration ??
Configur ations consists of three p arts:
A Configur ation- type command (xConfiguration or xDirec tory)1.
A Configur ation path (address- expression)2.
A Configur ation value3.
xConguration H323Gatekeeper Discovery: Manual
Configuration-type command
Configur ation path
Configur ation value
XACLI – Conguration Type Commands
About the TANDBERG API
EXAMPLE:
xconguration ?
- User Congurations -
AdditionalCamera FTP OSD
AlertSpeaker G703 PacketlossDownSpeed
AlertTone H320 PictureProgram [1..4]
Audio H323 PresentationStart
AutoAnswer H323CallSetup Preset [1..15]
AutoDisplaySnapshot H323Gatekeeper QoS
AutoLayout H323Prex RemoteSwUpgrade
AutoPIP HTTP RTP
Bonding HTTPS Screensaver
CallManager IdReport SelfViewOnStartup
Camera [1..13] IEEE802.1x SerialPort [1..2]
CameraSleep IP SIP
CameraTracking IPMedia SNMP
Conference IPProtocol StartupVideoSource
CorporateDirectory IRControl StillImageSource
DefaultPIPPosition ISDN Streaming
DoNotDisturb Keyboard StrictPassword
DualMonitor Kiosk SystemUnit
DuoVideoSource LocalLayout T1
E1 Logo Telnet
Ethernet LoS TelnetChallenge
ExternalManager MainVideoSource Time
ExternalNetwork NAT UseAsLocalPCMonitor
ExternalServices NetProle [1..7] Video
FECC NTP VNC
FeedbackFilter OptionKey
OK
xdirectory ?
- Directory -
GlobalEntry [1..400] LocalEntry [1..200]
GroupEntry [1..50]
OK
About Configuration Type Commands
46
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
XACLI – Conguration Type Operation
About the TANDBERG API
Three ope rations can be performed on
congurations:
Configur ation Help•
Configur ation Read•
Configur ation Set ( Write)•
About Configuration Operations
Configuration Help Configuration Read
Configuration Set (Write)
To get help on configurations, t ype ? after the configuration path
(address expr ession):
<configuration-type comma nd> <add ress expression> ?
EXAMPLE:
xconguration h323gatekeeper discovery ?
*h xConguration H323Gatekeeper Discovery: <Manual/Auto>
OK
To read configur ations fro m the system jus t type th e root command
(xConfiguration/xDire ctor y) followed by the p ath (address
exp res sion):
<configuration-type comma nd> <add ress expression>
EXAMPLE:
xconguration h323gatekeeper discovery
*c xConguration H323Gatekeeper Discovery: Manual
OK
Type a root comm and (xConfiguration/xDirectory) followed by
a valid path (add ress expres sion). The path mus t be terminat ed with a
colon before the value is ad ded.
<configuration-type comma nd> <add ress expression>: <value>
EXAMPLE:
xConguration H323Gatekeeper Discovery: Manual
Note!
*h• is used when retur ning the result
of a help quer y
*c is used when ret urning the r esult •
of a read quer y
Nothing is used for confi guration set•
*d is used when returning the result •
of an xdirectory read query.
47
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Integer values:<x..y>
Defines t he valid range for an integer input. x = min value, y = max value.
<1..100>
Literal valu es: <X/Y/../Z>
Defines t he possible v alues for a given configur ation.
<On/Off/Auto>
String values: <S: x, y>
Defines t hat the valid input for this configuration is a Strin g with minimum length x an d maximum le ngth of y ch aracter s.
<S: 0, 49>
IPv4 Address values: <IPAddr>
Defines t hat the inpu t must be an IP v4 address.
<IPAddr>
IPv6 Address values: <IPv6Addr: x, y>
Defines t hat the inpu t must be an IP v6 address with minimu m length x and maximum length y.
<IPv6Addr: 0, 43>
IPv4 or IP v6 Address values: <IPv4v6Addr: x, y>
Defines t hat the inpu t must be an IP v4 or IPv 6 address wi th minimum len gth x and ma ximum leng th y.
<IPv4v6Addr: 0, 43>
XACLI – Conguration Types
About the TANDBERG API
The system su pport s the followin g value
type s:
Integer valu es•
Literal values•
String values•
E164 string values (strings only contain -•
ing digits, ‘#’ an d ‘*’)
IPv4 Add ress values•
IPv6 Address valu es•
IPv4 or IP v6 Addr ess values•
About Configuration Types Format for Value Types
D 138 87.08
MAY 2008
48
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
To get an overview of the suppor ted comm and-t ype commands, typ e ? or help af ter the com mand- type co mmand (xcommand) .
TIP! To list all suppor ted conf igurations w ith corre sponding va luespace:
xcommand ??
xcommand ?
- User Commands -
AlertToneTest DialLocalEntry LocalEntryDelete
AudioTestSignal DisconnectCall MessageBoxDelete
Boot DTMFSend MessageBoxDisplay
CallAccept DuoVideoStart PIPHide
CallMute DuoVideoStop PIPShow
CallMuteOutgoing FECCFocus PresetActivate
CameraFocus FECCMove PresetClear
CameraHalt FECCPresetActivate PresetStore
CameraMove FECCPresetStore ScreensaverActivate
CameraPosition FECCRequestStill ScreensaverDeactivate
CameraTrackingStart FECCSelectSource ScreensaverReset
CameraTrackingStop FeedbackDeregister SiteDisconnect
CameraWhiteBalance FeedbackRegister SiteView
ChairRelease FloorRelease SiteViewEnd
ChairTake FloorRequest SPIDAutoCongure
ConferenceDisconnect FloorToSite SStringSend
ConferenceTerminate FloorToSiteEnd StillImageSend
CorpDirGetNext GroupEntryAdd StreamingStart
CorpDirGetPrevious GroupEntryDelete StreamingStop
CorpDirSearch KeyDisable TextDelete
DefaultValuesSet KeyEnable TextDisplay
Dial KeyPress VirtualMonitorReset
DialGlobalEntry KeyRelease VirtualMonitorSet
DialGroupEntry LocalEntryAdd
OK
Note! The list p rovided here appears as an example only. There may be comm ands available,
not listed her e.
XACLI – Command-type Commands – xcommands/xdirectory
About the TANDBERG API
To get help on a specif ic command, type the c ommand -type command (xco mmand) – then a
command name followed by ? or help:
<command-type c ommand> <co mm and na me> ?
EXAMPLE:
xcommand dial ?
*h xCommand Dial
Number: <S: 0, 60>
SecondNumber: <S: 0, 60>
SubAddress: <S: 0, 20>
CallRate: <Tlph/1xh221/2xh221/64/128/…/4096/Max/Auto>
Restrict: <On/Off>
NetProle: <1..7>
BillingCode: <S: 0, 16>
NOTE! Required p arameter s are identified by an (r) behind the p arameter na me.
EXAMPLE:
xcommand cameramove ?
*h xCommand CameraMove
Camera(r): <1..4>
Direction(r): <Up/Down/Right/Left/In/Out>
OK
Command help
Example Showing How to Get an Over view of Supported Commands
Getting an Overview
D 138 87.08
MAY 2008
49
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
When issuin g a command, th e system will ret urn a set of retur n values. The
response will by default be on the same format as the st andard X ACLI Stat us
format. T he other supp orted status formats (completepath/XML) are also
suppor ted – ref. xpreferences.
EXAM PLE
xcommand dial 558458
*r Result (status=OK):
CallRef: 1
LogTag: 6
*r/end
OK
If complete p ath is enabled for the RS -232/Telnet sessio n
(“xpreferences com pletepath on”):
EXAM PLE
xcom dial 558458
*r Result (status=OK):
*r Result CallRef: 1
*r Result LogTag: 4
OK
XACLI – Command-type Commands – Issuing a Command
About the TANDBERG API
A command must start with the command- type co mmand (xcommand), followed by a comman d name, followe d
by a set of para meters. Par ameters valu es are identified by spe cifyin g the parameter name foll owed by a ‘:’
<command-type c ommand> <co mm and na me> <para meter:value> <parameter:value>...
EXAMPLE:
xcommand dial number:558458 restrict:on callrate:128 subaddress:10
If there are m ultiple inst ances of a par ameter, the item nu mber is adde d after th e tag separ ated with a do t:
<command-type c ommand> <co mm and> <parameter.ite m:value> <parameter.item:value>...
EXAMPLE:
xcommand groupentryadd name:TANDBERG localentryid.1:15 localentryid.2:57
Issuing a Command Command Response
Sequence Notation (Optional)
<command -ty pe root comm and> <comma nd> <value> <value>...
When using t his notation t he parameter values must b e entered in the sequenc e as stated in th e help text:
EXAMPLE:
*h xComm and Dial
Num ber: <S: 0, 60>
SecondNu mb er: <S: 0, 60>
SubAdd ress: <S: 0, 20>
CallRate: <Tlph/1xh221/2x h221/64/128/192/256/320/384/H0/512/768/1152/1472/1
920/2560/3072/4096/Ma x/Au to>
Restrict: <On/Off>
NetProfile: <1..7>
BillingCode: <S: 0, 16>
To dial a participant with the following propert ies: Number: 6 66, SecondNumber:777, SubAddress: 8, CallRate:
128, Restrict: On
xcom mand d ial 666 777 8 128 on
A combination of markup no tation and sequence is als o suppor ted. The
marked par ameters will be assigned t he user enter ed values fir st, then the
system will assign the sequ ence entered parameters for the pa rameters not
yet having been assigne d a value:
EXAM PLE:
xcommand dial 666 restr ict:on 777 8 128
Combination of Markup Notation and Sequence (Optional)
NOTE! When using XACLI as a ma chine- machine interfac e we recommend that
you use markup notation and always supply complete t ag names.
D 138 87.08
MAY 2008
50
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
XACLI – Command-type Commands – Parameter Value Types
About the TANDBERG API
The system su pport s the followin g value typ es:
Integer valu es•
Literal values•
String values•
E164 string values (strings only containing digits, •
‘#’ and ‘*’)
IPv4 Add ress values•
IPv6 Address valu es•
IPv4 or IP v6 Addr ess values•
Integer values:<x..y>
Defines t he valid range for an integer input. x = min value, y = max value.
<1..100>
Literal values: <X/Y/../Z>
Defines t he possible v alues for a given configur ation.
<On/Off/Auto>
String values: <S: x, y>
Defines t hat the valid input for this configuration is a Strin g with minimum length x an d maximum le ngth
of y charac ters.
<S: 0, 49>
IPv4 Address values: <IPAddr>
Defines t hat the inpu t must be an IP v4 address.
<IPAddr>
IPv6 Address values: <IPv6Addr: x, y>
Defines t hat the inpu t must be an IP v6 address with minimum length x and maximum length y.
<IPv6Addr: 0, 43>
IPv4 or IPv6 Address values: <IPv4v6Addr: x, y>
Defines t hat the inpu t must be an IP v4 or IPv 6 address wi th minimum len gth x and ma ximum leng th y.
<IPv4v6Addr: 0, 43>
Command Parameter Value Types
Format for Value Types
51
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
EXAMPLE
xhistory ?
- History -
Call [1..20]
OK
xevent ?
- Event -
AuthenticationFailure MessageBoxResult
CallDisconnected PacketlossDownSpeed
CallStatisticsIP [1..11] SString
CallSuccessful SystemActivity
DownspeedingFinished
OK
All Status i nformatio n is organized in a
hierarchic tree str ucture.
To get an overview of accessibl e toplevel status elements within a status type co mmand, ty pe ? or help af ter the
status-type c ommands (xst atus/xhistory/xevent).
EXAMPLE
Defining Element name s, Values, Attr ibutes, and Item No.:
xstatus call 1
*s Call 1 (status=Synced, type=Vtlph, protocol=H323, direction=Outgoing, logTag=1):
CallRate: 768
RemoteNumber: “558458”
Mute: Off
Microphone: Off
Duration: 20
MuteOutgoing: Off
Channels 1 (type=Incoming):
.
. (some lines have been removed for clarity)
.
Video 2 (status=Inactive): /
Data (status=Inactive): /
*s/end
OK
In the above ex ample. Elemen t names are shown in orange. Value s are shown in green. Att ributes are s hown in magenta. Item No. is show n in cyan
XACLI – Status Type Commands
About the TANDBERG API
About Status Type Commands
All Status i nformatio n is organized in a
hierarchic tree str ucture, ver y much like
files and folders on a com puter. The
tree structure consists of containerelements (folders) and value elements
(files). Container-elem ents contains
sub- elements, while value ele ments
contain values. All elements have an
element nam e and an elemen t item
number. There c an exist multip le
instances of an element.
An element can also have various
attrib utes. Attr ibutes are us ed to add
meta infor mation to an ele ment. The
sub-structure of a container-element may
vary depending on the attribute values.
The relationship between attri bute values
of a given elem ent and its underlying s ubstructure can be read from the sections
documenting the various status elements.
E.g. a call th at is disconne cted does no t
contain any data (except a disconnect
cause value), while a n active call c ontains
information about bandwidths, protocols,
channels etc.
Understanding Status
Information Structuring
EXAMPLE
xstatus ?
- Status -
Audio ExternalNetwork RemoteSwUpgrade
BRI [1..6] FarEndInformation Screensaver
Call [1..11] Feedback [1..3] SIP
Camera [1..13] G703 SoftwareUpgrade
CameraTracking H323Gatekeeper SystemUnit
Conference IP VirtualMonitor [1..4]
Ethernet NTP Warning [1..10]
ExternalManager PRI
OK
52
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
XACLI – Status Type Commands – Default Formatting
About the TANDBERG API
XACLI support s three dif ferent for mattings for status
information:
Default X ACLI form atting, p rovides goo d human •
readability, compact fo rmat. Howev er, a custom parser
must be used
Complete Path format ting. Reco mmended w hen parsing •
the information line by lin e.
XML formatting – to be u sed when usin g an XML-pars er.•
EXAMPLE showing st atus for a disco nnected call.
xstatus call 1
*s Call 1 (status=Disconnected, type=NA, protocol=NA, direction=NA, logTag=NA):
Cause: 16
*s/end
OK
EXAMPLE showing st atus for an act ive call.
xstatus call 1
*s Call 1 (status=Synced, type=Vtlph, protocol=H323, direction=Outgoing, logTag=2):
CallRate: 768
RemoteNumber: “558458”
Mute: Off
Microphone: Off
Duration: 10
MuteOutgoing: Off
Channels 1 (type=Incoming):
Rate: 768
Restrict: Off
Encryption (status=Off): /
Audio (status=Active):
Protocol: G722
Rate: 64
Video 1 (status=Active):
Protocol: H264
Resolution: CIF
Rate: 704
Video 2 (status=Inactive): /
Data (status=Inactive): /
Channels 2 (type=Outgoing):
Rate: 768
Restrict: Off
Encryption (status=Off): /
Audio (status=Active):
Protocol: G722
Rate: 64
Video 1 (status=Active):
Protocol: H264
Resolution: CIF
Rate: 704
Video 2 (status=Inactive): /
Data (status=Inactive): /
*s/end
From the exam ple showing s tatus for a disc onnected c all
(upper right), we c an see that the call element now only
contains one element; th e value- element C ause. The sub elements t hat were pres ent when the call was active (lower
right examp le) are no longer valid (i.e. it makes no sense to
ask for out going video r esolution fo r a disconnec ted call).
About Status Type Commands Formatting
About the Examples Provided Here
The root- element is p refixed wi th • *s (for sta tus), *e (for
event), or *l (for history log)
Root-el ement end is designated by a • *s/e n d (*e/e nd
or *l/e n d respectively)
To write a parser for this format, the parse r must keep •
track of th e levels by count ing white spa ces. The ind ent
is increase d by two whitespaces for ea ch level. Unless
link throug hput is an issue, we recommen d the use
of Complete P ath Forma tting instead of Defaul t XACLI
format ting when pa rsing infor mation sent f rom the cod ec.
Default XACLI Formatting
53
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
EXAMPLE
xpreferences completepath on
OK
xstatus call 1
*s Call 1 (status=Synced, type=Vtlph, protocol=H323, direction=Outgoing, logTag=2):
*s Call 1 CallRate: 768
*s Call 1 RemoteNumber: “558458”
*s Call 1 Mute: Off
*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
*s Call 1 Channels 1 Encryption (status=Off): /
*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 1 Video 1 (status=Active):
*s Call 1 Channels 1 Video 1 Protocol: H264
*s Call 1 Channels 1 Video 1 Resolution: CIF
*s Call 1 Channels 1 Video 1 Rate: 704
*s Call 1 Channels 1 Video 2 (status=Inactive): /
*s Call 1 Channels 1 Data (status=Inactive): /
*s Call 1 Channels 2 (type=Outgoing):
*s Call 1 Channels 2 Rate: 768
*s Call 1 Channels 2 Restrict: Off
*s Call 1 Channels 2 Encryption (status=Off): /
*s Call 1 Channels 2 Audio (status=Active):
*s Call 1 Channels 2 Audio Protocol: G722
*s Call 1 Channels 2 Audio Rate: 64
*s Call 1 Channels 2 Video 1 (status=Active):
*s Call 1 Channels 2 Video 1 Protocol: H264
*s Call 1 Channels 2 Video 1 Resolution: CIF
*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
The followin g should be observed:
Complete Path format ting is recommended for easy •
parsing
All lines are prefixed with • *s (for sta tus), *e (for event),
or *l (fo r history log)
The complete path to an element is supplie d on all lines•
The parse r can work line by line•
Root-el ement end is designated by a *s/end (*e/end or •
*l/end respectively).
NOTE! Complete Path formatting is ena bled by: “xprefer-
ences comp letepath on”, described later in this section of
the User Guide.
NOTE! the xpre ferences is a s ession spec ific comm and and
must be issue d every tim e the control application connec ts
to the code c.
XACLI – Status Type Commands – Complete Path Formatting
About the TANDBERG API
About Complete Path formatting
XACLI support s three dif ferent for mattings for status
information:
Default X ACLI form atting, p rovides goo d human •
readability, compact fo rmat. Howev er, a custom parser
must be used
Complete Path format ting. Reco mmended w hen parsing •
the information line by lin e.
XML formatting – to be u sed when usin g an XML-pars er.•
About Status Type Commands Formatting
54
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
XACLI – Status Type Commands – XML Formatting
About the TANDBERG API
The followin g should be observed:
To be used when the c ontrol application is usin g an XML •
parser
XML formatting is use d when pollin g for information using •
the special command x getxml, des cribed later in this sec tion of the manual.
To enable XML for matting o n feedback issued from t he •
codec, the special com mand xpreferences should b e
used.
EXAMPLE
xgetxml status/call[1]
<Status>
<Call item=”1” status=”Synced” type=”Vtlph” protocol=”H323” direction=”Outgoing” logTag=”2”>
<CallRate item=”1”>768</CallRate>
<RemoteNumber item=”1”>558458</RemoteNumber>
<Mute item=”1”>Off</Mute>
<Microphone item=”1”>Off</Microphone>
<Duration item=”1”>887</Duration>
<MuteOutgoing item=”1”>Off</MuteOutgoing>
<Channels item=”1” type=”Incoming”>
<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>
</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>
<Channels item=”2” type=”Outgoing”>
<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>
</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
About XML Formatting
XACLI support s three dif ferent for mattings for status
information:
Default X ACLI form atting, p rovides goo d human •
readability, compact fo rmat. Howev er, a custom parser
must be used
Complete Path format ting. Reco mmended w hen parsing •
the information line by lin e.
XML formatting – to be u sed when usin g an XML-pars er.•
About Status Type Commands Formatting
55
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
XACLI – Status Type Commands – Addressing Status Information
About the TANDBERG API
You address sta tus information by supply ing a status -typ e
command fo llowed by an add ress- expressio n (XPath or
TANDBERG Simp lePath):
<status-type command> <address expression>
See example 1 a) for an illustration.
If complete p ath is enabled for the RS 232/Telnet session
(xpreferences completepath on), it will look like
example 1 b).
As a second s et of examples let us consider a si tuation
where the user wants to know Audio statu s for both incoming
and outgoing channels f or Call 1. This is sho wn in examples
2 a) and 2 b).
EXAM PLE 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
*s/end
OK
EXAM PLE 1 b) xpreferences completepath set to on:
xstatus call 1 callrate
*s Call 1 (status=Synced, type=Vtlph, protocol=H323, direction=Outgoing, logTag=3):
*s Call 1 CallRate: 768
OK
EXAM PLE 2 a) the user wants to know Audio status for both incoming and out going 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
EXAM PLE 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
About Addressing Status Information
56
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Exposu re options sho uld be used to limit the amount o f informati on returned. By adding an
exposure op tion afte r the addres s expression (XPath or TAND BERG SimplePath), the system
can be instr ucted to ret urn par ts of the infor mation wit hin an element s tructur e only.
<status-type command> <address expression> <exposure op tion>
Suppor ted exposure options:
-• hides all val ue elements
--• hid es all sub- element s
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):
CallRate: 768
RemoteNumber: “558458”
Mute: Off
Microphone: Off
Duration: 10
MuteOutgoing: Off
Channels 1 (type=Incoming):
Rate: 768
Restrict: Off
Encryption (status=Off): /
Audio (status=Active):
Protocol: G722
Rate: 64
Video 1 (status=Active):
Protocol: H264
Resolution: CIF
Rate: 704
Video 2 (status=Inactive): /
Data (status=Inactive): /
Channels 2 (type=Outgoing):
Rate: 768
Restrict: Off
Encryption (status=Off): /
Audio (status=Active):
Protocol: G722
Rate: 64
Video 1 (status=Active):
Protocol: H264
Resolution: CIF
Rate: 704
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):
Channels 1 (type=Incoming):
Encryption (status=Off): /
Audio (status=Active):
Video 1 (status=Active):
Video 2 (status=Inactive): /
Data (status=Inactive): /
Channels 2 (type=Outgoing):
Encryption (status=Off): /
Audio (status=Active):
Video 1 (status=Active):
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
XACLI – Status Type Commands – Exposure Options
About the TANDBERG API
About Exposure Options
57
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
XACLI – Special Commands – xfeedback (I)
About the TANDBERG API
The special command xfeedback lets the user
register user defined X Path expressions (with p ossible exposu re options) to moni tor changes in t he
XML/X ACLI dat a. Whenever there is a change in
one or more elements addressed by a reg istered
XPath exp ression, the p art of the element str ucture containing these changes will be returned.
The system su pport s a total of 20 registered
expressio ns, with a total of 15 expressions for one
RS 232/Telnet s ession.
The xfee dback is a session specif ic command,
i.e. differe nt RS 232/Telnet session can define
feedbac k individually.
This also implies that the feedback expressions
must be set each time the co ntrol application
connect s to the code c, i.e. the control application
should alway s set the necessary feedback exp ressions when co nnecting to the system (or af ter
system reboot when using RS 232).
About the xfeedback Command
EXAMPLE
xfeedback ?
usage: xfeedback register <XPathExpression>
or: xfeedback deregister <index>
or: xfeedback list
(note: deregistration with index=0 will deregister all registered expressions)
OK
EXAMPLE
User wants to monitor all chan ges to the Call st atus elements, the Confer ence status element and
all Configurations:
xfeedback register status/call
OK
xfeedback register status/conference
OK
xfeedback register conguration
OK
EXAMPLE
To list the register ed expression the sub -comm and list should
be used:
xfeedback list
Registered XPath feedback expressions:
*xf 1 status/call
*xf 2 status/conference
*xf 3 conguration
OK
EXAM PLE
User wants to d eregister expression 2 in the left exam ple:
xfeedback deregister 2
OK
xfeedback list
Registered XPath feedback expressions:
*xf 1 status/call
*xf 3 conguration
OK
EXAMPLE
User only wants to monitor call state chan ges. This can be d one by adding the double hy phen exposure option (- -), after t he XPath
expressio n, status/call:
xfeedback register status/call--
OK
xcommand dial number:558458
*s Call 1 (status=EstablOut, type=Vtlph, protocol=H323, direction=Outgoing, logTag=6):
*s/end
*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
58
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
XACLI – Special Commands – xfeedback (II)
About the TANDBERG API
EXAMPLE. User wants to know when calls are connec ted
and when calls are disconnected, with out monitoring any
call data ch anges when the call is active:
This can be do ne by registering feedback on the even ts:
CallSuccessful•
CallDisconnected•
xfeedback register event/callsuccessful
OK
xfeedback register event/calldisconnected
OK
xcommand dial number:558458
*r Result (status=OK):
CallRef: 1
LogTag: 8
*r/end
OK
CONNECT
*e CallSuccessful:
CallRef: 1
LogTag: 8
Protocol: H323
Direction: Outgoing
CallRate: 768
RemoteNumber: “558458”
Encryption:
Incoming: Off
Outgoing: Off
*e/end
xcommand disconnectcall call:1
*r Result (status=OK): /
*r/end
OK
NO CARRIER
*e CallDisconnected:
CallRef: 1
LogTag: 8
*e/end
EXAMPLE. This exampl e shows status for a call that is b eeing
disconnected. The user has register ed a feedbac k expression to
monitor all call changes (xf eedback register status/call).
When the call is active th e Call element c ontains a lar ge sub- struc ture. When the call is disconnected this status tree collapses, i.e.
the only information availible for a disc onnected c all is a Cause
element. All sub-elements that are being removed in this transition
are marked with a gho st=Tr ue attribute when feedback is issued,
see below.
xstatus call 1
*s Call 1 (status=Synced, type=Vtlph,
protocol=H323, direction=Outgoing, logTag=30):
CallRate: 768
RemoteNumber: “558458”
Mute: Off
Microphone: Off
Duration: 62
MuteOutgoing: Off
Channels 1 (type=Incoming):
Rate: 768
Restrict: Off
Encryption (status=On):
Type: AES-128
CheckCode: “C6D478F231E09A04”
Audio (status=Active):
Protocol: G722
Rate: 64
Video 1 (status=Active):
Protocol: H264
Resolution: CIF
Rate: 704
Video 2 (status=Inactive): /
Data (status=Inactive): /
Channels 2 (type=Outgoing):
Rate: 768
Restrict: Off
Encryption (status=On):
Type: AES-128
CheckCode: “C6D478F231E09A04”
Audio (status=Active):
Protocol: G722
Rate: 64
Video 1 (status=Active):
Protocol: H264
Resolution: CIF
Rate: 704
Video 2 (status=Inactive): /
Data (status=Inactive): /
*s/end
OK
xcommand disconnect
*r Result (status=OK): /
*r/end
OK
*s Call 1 (status=ClearOut, type=Vtlph,
protocol=H323, direction=Outgoing, logTag=30):
*s/end
NO CARRIER
*s Call 1 (status=Disconnected, type=NA,
protocol=NA, direction=NA, logTag=NA):
Cause: 16
CallRate (ghost=True): /
RemoteNumber (ghost=True): /
Mute (ghost=True): /
Microphone (ghost=True): /
Duration (ghost=True): /
MuteOutgoing (ghost=True): /
Channels 1 (ghost=True): /
Channels 2 (ghost=True): /
*s/end
xstatus call 1
*s Call 1 (status=Disconnected, type=NA,
protocol=NA, direction=NA, logTag=NA):
Cause: 16
*s/end
OK
NOTE! If sub-elemen ts are remove d from a status structu re betwee n transitio ns, the removed elements will be notified with an at tribute
ghost =Tru e when feedback is issued. This allows f or an extern al control sy stem to be comp letely sync hronised with the code c.
59
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
A command of g reat impor tance, xpreferences lets the
user/control applica tion indivi dually conf igure the Telnet/
RS 232 session in use. When p arsing dat a sent from the codec using a co ntrol system i t is impor tant to set preferences
to match the p arser in use.
The xpref erences is a session specific command, i.e.
differ ent RS 232/ Telnet sessions can define pre ferences
individu ally. This also implies that the preferences must be
set each time the contro l application connect s to the code c,
i.e. the contro l applicati on should always set the nec essary
preferen ces when con necting to t he system (or af ter system
reboot when using RS 232).
The xpreferences Options
xpreferences ?
usage: xpreferences xpathwrite <on/off>
or: xpreferences detaillevel <1..2>
or: xpreferences xmlcongfeedback <on/off>
or: xpreferences xmlstatusfeedback <on/off>
or: xpreferences xmlcommandresult <on/off>
or: xpreferences itemnumber <on/off>
or: xpreferences completepath <on/off>
OK
XACLI – Special Commands – xpreferences (I)
About the TANDBERG API
About xpreferences xpreferences xpathwrite
xpreferences xpathwrite <on/off>
Disables/enables t he XPath se arch engin e when issuing c onfigurations. When the XPath sear ch engine is disabled, the
user/control applica tion must supp ly the complete path to
the configurations to b e set (no “double slash es” allowed).
This will improve the per formanc e of the system w hen issuing many cons ecutive co nfigurat ions.
NOTE! It is always recommend ed to supply the complete
path for configurations to be set whe n issuing comm ands
from an external control application.
xpreferences detaillevel
xpreferences detaillevel <1..2>
Most infor mation elements acces sible by the st atus-t ype
commands a re defined to be level 1 infor mation. However
there are so me information element s defined to be level 2
informat ion. When rea ding status informatio n, only the information elem ents with a detail level equ al to or less than t he
detaillevel d efined for the inter face will be lis ted.
The detaill evel is by defaul t set to 1 when con necting to an
RS 232/Telnet s ession.
xpreferences xmlcongfeedback <on/off>
If xmlconf igfee dback is set to on, feedback on configur ations will be re turned in XM L-format inste ad of the stan dard
XACLI configurat ion format .
EXAMPLE
XACLI-format:
*c xConguration SerialPort 1 BaudRate: 2400
XML format
<Conguration>
<SerialPort item=”1”>
<BaudRate item=”1”>2400</BaudRate>
</SerialPort>
</Conguration>
xpreferences xmlconfigfeedback
xpreferences xmlcommandresult <on/off>
If xmlcommandresult is s et to on, response for comman ds
will be returned in XML-format.
EXAMPLE
XACLI-format:
xcom dial 10.47.15.127
*r Result (status=OK):
CallRef: 1
LogTag: 8
*r/end
XML format
xcom dial 10.47.15.127
<Result item=”1” status=”OK”>
<CallRef item=”1”>1</CallRef>
<LogTag item=”1”>8</LogTag>
</Result>
xpreferences xmlcommandresult
60
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
XACLI – Special Commands – xpreferences (II)
About the TANDBERG API
xpreferences xmlstatusfeedback <on/off>
If xmlstatusfeedback is set to on, all sta tus feedback will be returned
in XML-forma t instead of the d efault X ACLI status f ormat (or complete path for matting ).
EXAMPLE
XACLI-format:
*s Call 1 (status=Synced, type=Vtlph, protocol=H323, direction=Outgoing, logTag=78):
Channels 1 (type=Incoming):
Rate: 768
Audio (status=Active):
Protocol: G722
Rate: 64
*s/end
XML format
<Status>
<Call item=”1” status=”Synced” type=”Vtlph” protocol=”H323” direction=”Outgoing” logtag=”78”>
<Channels item=”1” type=”Incoming”>
<Rate item=”1”>768</Rate>
<Audio item=”1” status=”Active”>
<Protocol item=”1”>G722</Protocol>
<Rate item=”1”>64</Rate>
</Audio>
</Channels>
</Call>
</Status>
xpreferences xmlstatusfeedback
xpreferences itemnumber <on/off>
All Status a nd Configuration elem ents consist of an element nam e and an
element ite m number. However, XACLI hides the i tem number fo r an element
if there onl y exist one item of the given element.
If xprefer ences itemnumber is set to o n, XACLI will display item num bers for
all elements. This is to make it easi er to parse th e informati on sent from
the codec. By settin g “xpreferences item num ber on”, the parser can
always expe ct an item number to follow an ele ment name.
EXAM PLE: Reading configurati ons of Serial Port 1 with xpreferences item -
number is set to OFF:
xconguration serialport 1
*c xConguration SerialPort 1 BaudRate: 9600
*c xConguration SerialPort 1 Parity: None
*c xConguration SerialPort 1 DataBits: 8
*c xConguration SerialPort 1 StopBits: 1
*c xConguration SerialPort 1 Mode: Control
OK
EXAMPLE: Reading conf igurations of Serial Por t 1 with xprefere nces item-
number is set to ON:
xpreferences itemnumber on
OK
xconguration serialport 1
*c xConguration SerialPort 1 BaudRate 1: 9600
*c xConguration SerialPort 1 Parity 1: None
*c xConguration SerialPort 1 DataBits 1: 8
*c xConguration SerialPort 1 StopBits 1: 1
*c xConguration SerialPort 1 Mode 1: Control
OK
xpreferences itemnumber
61
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
XACLI – Special Commands – xpreferences (III)
About the TANDBERG API
xpreferences completepath <on/off>
Used to enabl e Complete Path format ting for all St atus-t ype dat a. If set to on, the c omplete pat h to a status element will be supplied on all lines. R ECOMMENDED to be used whe n parsing st atus
informat ion sent from t he codec lin e by line.The specif ied forma tting will als o apply all fee dback sent f rom the cod ec on this RS 232/Telnet session.
EXAM PLE. Reading status for C all 1 with xpreferences com pletepath off:
xstatus call 1
*s Call 1 (status=Synced, type=Vtlph, protocol=H323, direction=Outgoing, logTag=2):
CallRate: 768
RemoteNumber: “558458”
Mute: Off
Microphone: Off
Duration: 10
MuteOutgoing: Off
Channels 1 (type=Incoming):
Rate: 768
Restrict: Off
Encryption (status=Off): /
Audio (status=Active):
Protocol: G722
Rate: 64
Video 1 (status=Active):
Protocol: H264
Resolution: CIF
Rate: 704
Video 2 (status=Inactive): /
Data (status=Inactive): /
Channels 2 (type=Outgoing):
Rate: 768
Restrict: Off
Encryption (status=Off): /
Audio (status=Active):
Protocol: G722
Rate: 64
Video 1 (status=Active):
Protocol: H264
Resolution: CIF
Rate: 704
Video 2 (status=Inactive): /
Data (status=Inactive): /
*s/end
OK
EXAM PLE. Reading status for C all 1 with xpreferences com pletepath on:
xstatus call 1
*s Call 1 (status=Synced, type=Vtlph, protocol=H323, direction=Outgoing, logTag=2):
*s Call 1 CallRate: 768
*s Call 1 RemoteNumber: “558458”
*s Call 1 Mute: Off
*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
*s Call 1 Channels 1 Encryption (status=Off): /
*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 1 Video 1 (status=Active):
*s Call 1 Channels 1 Video 1 Protocol: H264
*s Call 1 Channels 1 Video 1 Resolution: CIF
*s Call 1 Channels 1 Video 1 Rate: 704
*s Call 1 Channels 1 Video 2 (status=Inactive): /
*s Call 1 Channels 1 Data (status=Inactive): /
*s Call 1 Channels 2 (type=Outgoing):
*s Call 1 Channels 2 Rate: 768
*s Call 1 Channels 2 Restrict: Off
*s Call 1 Channels 2 Encryption (status=Off): /
*s Call 1 Channels 2 Audio (status=Active):
*s Call 1 Channels 2 Audio Protocol: G722
*s Call 1 Channels 2 Audio Rate: 64
*s Call 1 Channels 2 Video 1 (status=Active):
*s Call 1 Channels 2 Video 1 Protocol: H264
*s Call 1 Channels 2 Video 1 Resolution: CIF
*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
xpreferences completepath
62
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
As an altern ative to the X ACLI outp ut format, XML format is
suppor ted through the root co mmand xgetxml. The x getxml
takes an XPath expressi on as parameter and the elem ents
(or complete do cument) matc hing the expr ession will be
returned.
EXAMPLE
xgetxml status/ip
<Status>
<IP item=”1”>
<Address item=”1”>10.47.11.179</Address>
<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
XACLI – Special Commands – xgetxml
About the TANDBERG API
About xgetxml
63
D 138 87.08
MAY 2008
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
TXA S is a service provide d by TANDBERG units for transm itting and rec eiving (tr ansceivin g) informa tion encod ed in XML
format.
The API uses HTTP(S) as the t ranspor t mechanism and connects to th e normal web p ort (80). T XAS can b e accessed
in two ways; bar e-bone HTT P requests w here URL’s uniquely
identif ies the requ est, and SOAP w here a single U RI is used
but the req uest itself is encoded with XML.
TXAS - TANDBERG XML API Service
About the TANDBERG API
The bare -bone H TTP mode uses a unique U RL to identif y the spe cific req uest. The co ntents of
the HTT P body will be a XML docum ent (or part of i t).
Bare- bone HT TP(S) access is accomplish ed by passing arguments in t he query s tring (after
‘?’ in URL) in a GET request, or using t he “applicati on/x-ww w-for m-ur lencode d” content-type
method of POSTing form d ata (Each ar gument starts with a name ‘=’ and a value, and every
paramete r separate d with ‘&’ (and opt NL).)
getxml
REQUEST:
/getxml
PARAM:
location = XPath expression
/ge t x m l request r eturns an XM L document b ased on the lo cation par ameter pass ed to the
request. T he elements (or complete doc ument) matching the expression will be returned.
On Incorrect XPat h expression, a <Fault> ele ment with a <X PathErr or> element will be returned.
formputxml
REQUEST:
/formputxml
PARAM:
xmldoc = “an XML document of Conguration, Directory or Command”
This is most useful in a POST (to extend character limit of 255 of G ET urls). It post s a Configu ration or Command doc ument to set th e configur ations or issu e a command.
Like getx ml, it has the dat a URL form -dat a encoded with one singl e parameter. The ContentType of the document must be of t ype “appli cation/x-w ww- form- urlenc oded” and th e body must
be encoded accordingly (e.g. first line will be xmld oc=<t hen the document>).
putxml
REQUEST:
/putxml
PARAM:
HTTP BODY as argument
Putxm l is like formputxml+, put uses the co mplete BODY as argument (i.e. the con tent of
the xmldo c paramete r). The Content-type should be “tex t/x m l” or “a pp li cation/xm l ” (
or “text/plain”), though no check at the moment. (E xcept for ap plication/x- www -form -url
encoded w hich will caus e a failure).
About TANDBERG XML API Service
Bare-bone HTTP(S) Access
We rec ommen d that you check out the
TANDBE RG web s ite regularly for up dated
versions of this manual:
http://ww w.tandberg.com/support/
documentation.php
This par t of the manual describes the Configuration
information available.
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
65
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
D 138 87.08
MAY 2008
Conguration-type Commands
Understanding the Table Layout
65
TANDBERG 3000 MXP & 6000 MXP
REFERENCE USER GUIDE FOR SYSTEM INTEGRATORS
D 138 8 7 . 0 6
NOVEMBER 2007
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 proper ly, 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
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
tones. To help distinguish between incoming video calls
and ordinary telephone calls, we recommend the use of
different alert tones for video calls and telephone calls.
AlertTone VideoTelephony: <1..10>
Defines the alert tone to use for incoming video telephony calls.
Example:
xconfiguration alerttone videotelephony: 10
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 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
AdditionalCamera — Audio
Configuration-type Commands – xconfiguration / configuration.xml
Configur ation path
Valid range of Co nfigurat ion values (fro m..to)
Description
Syntax example
Some conf iguration s
share a comm on part
of the conf iguration
path, as can b e seen
from thes e examples
Tip or restr ictions
applying
Contents of t his
column is sor ted
alphabetically
TIP! An exhaustive
descript ion of the API
structure can be foun d
in the sect ion
The TANDBERG A PI
Valid settin gs available
(here: On/Off )
66
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
D 138 87.08
MAY 2008
AdditionalCamera Type: <0..6>
This conguration enables improved support for some non-TANDBERG cameras. When using one of the cameras listed below, set the conguration 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 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: If using a Sony EVI-D30: xconguration additionalcamera type: 1
AlertSpeaker Mode: <On/Off>
Turns the internal alert speaker On or Off.
Example: xconguration alertspeaker mode: on
AlertTone Volume: <0..15>
Sets the volume of the alert tone. This volume setting also applies to the internal aler t speaker if turned on.
Example: xconguration alerttone volume: 10
TIP! The system supports as many as 10 different alert
tones. To help distinguish between incoming video calls
and ordinary telephone calls, we recommend the use of
different alert tones for video calls and telephone calls.
AlertTone VideoTelephony: <1..10>
Denes the alert tone to use for incoming video telephony calls.
Example: xconguration alerttone videotelephony: 10
AlertTone Telephony: <1..10>
Denes the alert tone to use for incoming telephony calls.
Example: xconguration alerttone telephony: 8
AllowLatency: <On/Off>
If set to Off (default), the IP call rate will sometimes exceed the maximum callrate specied 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: xConguration AllowLatency: On
Audio Microphones Mode: <On/Off>
Turns all microphones On or Off. This is the conguration that is tied to the “Mic off” key on the TANDBERG MXP remote control.
Example: xconguration 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: xconguration audio microphonemixer mode: xed
AdditionalCamera — Audio
Conguration-type Commands – xconguration / conguration.xml
67
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Conguration-type Commands – xconguration / conguration.xml
D 138 87.08
MAY 2008
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: xconguration 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 unidentied.
Example: xconguration audio audiomodule: NAMII-6000
Audio Volume: <0..21>
Sets the volume level output.
Example: xconguration 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: xconguration 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: xconguration 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 3000 MXP 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 o r Audio 5 & 6 (600 0 MXP), and Line input 1 & 2 or Audio
3 & 4 (3000 MX P)
Example: xconguration audio agc vcr: off
Audio AGC Received: <On/Off>
Turns AGC for received audio On or Off.
Example: xconguration 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: xconguration audio echocontrol 2: On
Audio cont...
68
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Conguration-type Commands – xconguration / conguration.xml
D 138 87.08
MAY 2008
Audio Stereo: <On/Off>
Turns stereo I/O mode On or Off.
Example: xconguration audio stereo: on
Stereo Settings
Output Response Codec 3000 MXP Output Response Codec 6000 MXP
Out 1
mode
Stereo
I/O mode
Stereo
speakers
Audio Out 1 Audio Out 2 Audio Out 1 Audio Out 2 Audio
Out 3
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
Analogue On On Loudspeaker L Loudspeaker R Loudspeaker L Loudspeaker R VCR
SPDIF Off Off Loudspeaker mono VCR Loudspeaker mono Aux VCR
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 i s controll ed throug h the xconf iguratio n audio out puts line t ype comm and (overle af)
Audio StereoSpeakers: <On/Off>
Turns stereo speakers On or Off.
Example: xconguration audio stereospeakers: on
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: xconguration 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: xconguration audio keytones: on
Audio Inputs Microphone [1..x]
6000 MXP: x=3
3000 MXP: x=2
Level: <1..16>
Denes the input levels for the different microphones.
Example: xconguration audio inputs microphone 2 level: 10
By default, all inputs are
enabled. Just plug in an audio
source and it is active. Audio
inputs that are On will automatically be mixed. Unconnected
inputs will automatically be
muted. Select Off to prevent
audio/noise from connected but
unused inputs.
The microphone inputs are
intended for electret type microphones. The microphone inputs
are balanced with 24 V phantom
power.
Audio Inputs Microphone [1..x]
6000 MXP: x=3
3000 MXP: x=2
Mode: <On/Off>
Turns On or Off the different microphone inputs.
Example: xconguration audio inputs microphone 2 mode: off
Turns microphone 2 off.
Audio Inputs Microphone [1..x]
6000 MXP: x=3
3000 MXP: x=2
Mode: <Line>
NOTE! Applies to 6000 MXP only! Here the Microphone 3 Mode can be set to Line. It then
becomes a balanced line level input. The gain will be reduced accordingly.
Example: xconguration audio inputs microphone 3 mode: line
Sets microphone input 3 on a 6000 MXP to a balanced line level input.
Audio Inputs Line [1..x]
6000 MXP: x=3
3000 MXP: x=2
Level: <1..16>
Denes the input levels for the different line inputs.
Example: xconguration audio inputs line 2 level: 10
Audio cont...
69
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Conguration-type Commands – xconguration / conguration.xml
D 138 87.08
MAY 2008
Audio Inputs Line [1..x]
6000 MXP: x=3
3000 MXP: x=2
For 3000 MXP, Line 1:
Mode: <On/Off/Microphone>
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: xconguration audio inputs line 2 mode: off
Audio Outputs Line [1..x]
6000 MXP: x=3
3000 MXP: x=2
Level: <1..16>
Denes the output level of the specied output line
Example: xconguration audio outputs line 2 level: 10
Audio Outputs Line [1..x]
6000 MXP: x=3
3000 MXP: x=2
Mode: <On/Off>
Enables or disables the specied output line.
Example: xconguration audio outputs line 2 mode: off
Audio Outputs Line [1]
6000 MXP: x=3
3000 MXP: x=2
Type: <Analog/SPDIF/Auto>
NOTE! Applies to Line 1 only! This conguration is also referred to as Out 1 Mode.
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: xconguration 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 aler t 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 congured with the intention of listening into a condential
conversation/meeting without the meeting participants noticing.
Example: xconguration audio localdetection mode: On
Audio cont...
70
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Conguration-type Commands – xconguration / conguration.xml
D 138 87.08
MAY 2008
Audio Feedback Mode: <Normal/Fast>
This conguration 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: xconguration audio feedback mode: normal
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: xconguration autoanswer mode: mute
AutoAnswer Delay: <1..50>
Denes how long (in seconds) an incoming call has to wait before it is answered automatically by the system (autoanswer must be enabled).
Example: xconguration autoanswer delay: 10
AutoDisplaySnapshot: <On/Off>
If set to On the system will automatically display snapshots (stillimages) when received from the other side.
Example: xconguration autodisplaysnapshot: 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 pictrure layout during the conference. All desired layout changes must be done manually, ref. LocalLayout.
Example: xconguration autolayout mode: off
AutoPIP Mode: <On/Off/Auto>
This conguration only applies if LocalLayout Toggle is set to PIP.
If set to On, the system will display a PIP containing the farend mainstream when dual video stream is activated.
If set to Auto, the system will display a PIP containing the farend mainstream when dual video stream is activated. This PIP will disappear automatically after a few seconds.
If set to Off, no PIP will be displayed when dual video stream is activated. Requires AutoLayout Mode set to Off.
Example: xconguration autopip mode: on
Example: xconguration autopip mode: 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: xconguration 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: xconguration bonding rebonding: off
CallManager
Address: <S: 0, 64>
Denes the address of the call manager to use (if any).
Example: xconguration callmanager address: 10.47.9.1
Audio cont... — CallManager
71
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Conguration-type Commands – xconguration / conguration.xml
D 138 87.08
MAY 2008
CallVideoSource: <0/1/5/6>
The Call Video Source is the default call video source you would prefer to use in a call..
Example: xconguration callvideosource: 0
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: xconguration camera 1 brightness mode: manual
If a TANDBERG Video Switch is
connected, the camera ranges
will behave as follows:
Camera 1 will b e the video •
switch.
Camera range 2..7 will •
be cameras connecte d to
secondary chain (the chain
originat ing from Dat a port 2
of the switc h).
Camera range 8..13 will be •
cameras c onnected to the
primar y chain (the ch ain
originat ing from Dat a port 1
of the switc h).
Go to the TANDBERG Video
Switch section to read more.
Camera [1..13] Brightness Level: <0..16>
Denes the brightness level to use if Brightness Mode is set to Manual.
Example: xconguration camera 1 brightness level: 10
Camera [1..13] Whitebalance Mode: <Manual/Auto>
If set to Auto the camera will continuously adjust the whitebalance depending on the camera view.
When set to Manual the whitebalance can be calibrated manually by the command CameraWhiteBalance. The whitebalance of the camera will then remain constant until a new calibration is performed.
Example: xconguration camera 1 whitebalance mode: auto
Camera [1..13] Whitebalance Level: <0..16>
Species the camera whitebalance level. Applies to TANDBERG Precision HD cameras only.
Example: xconguration camera 1 whitebalance level: 10
Camera [1..13] Focus Mode: <Manual/Auto>
If set to Manual autofocus will never be turned on automatically.
Example: xconguration 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: xconguration 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: xconguration camera 1 dualvisca: on
Camera [1..13] Mirror: <Off/On>
Turns mirror mode on/off. Not applicable to TANDBERG WAVE I cameras.
Example: xConguration camera 1 mirror: on
CallVideoSource — Camera [1..13]
72
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Conguration-type Commands – xconguration / conguration.xml
D 138 87.08
MAY 2008
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: xConguration camera 1 gamma mode: auto
Camera [1..13] Gamma Level: <0..7>
Selects which gamma correction table to use. This setting may be useful in difcult lighting conditions, where
changes to the the brightness setting does not provide satisfactory results. Applies to TANDBERG Precision HD
cameras only.
Example: xConguration camera 1 gamma level: 5
See the comment about camera
ranges on the previous p age.
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: xConguration 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 rst 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 conguration On. When you select the PC Input, you
will gain control of the last camera. This conguration may be useful when using the VGA output on a Sony BRC-H700 camera.
Important: If you set this conguration to on with a single PrecisionHD camera connected, the system will assume that it is connected to the PC Input and avoid
conguring 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: xConguration 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: xconguration camerasleep mode: on
Camera [1..13] cont... — CameraSleep
73
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Conguration-type Commands – xconguration / conguration.xml
D 138 87.08
MAY 2008
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: xconguration cameraswupgrade: Auto
CameraTracking Speed: <Slow/Normal/Fast>
Sets the camera tracking speed. Camera tracking is enabled/disabled by the commands CameraTrackingStart and CameraTrackingStop.
Example: xconguration 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>
Denes 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: xconguration conference defaultcall callrate: 320
The DefaultCall settings specify
call properties to use if proper-
ties are not specied directly
when placing the call.
Conference DefaultCall 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.
To force a restricted call, choose Restrict (56k) On.
Example: xconguration conference defaultcall restrict: off
Conference DefaultCall NetProle: <1..7>
Selects default NetProle. Please refer to the NetProle conguration for further details on the supported NetProles.
Example: xconguration conference defaultcall netprole: 3
Conference H323Alias E164: <E164: 0, 30>
Denes the E164 alias for the system. Valid characters are 0-9, * and #.
Example: xconguration conference h323alias e164: 666666
The aliases dene the telephone
numbers for the unit, i.e. numbers to call to reach the unit.
The system can register both an
E164 alias, which can only contain digits (including *, #) and
an ID, which can also contain
letters.
Conference H323Alias ID: <S: 0, 49>
Denes the H323Alias ID for the system. If no ID is specied the system will use the SystemUnit Name as
H323Alias ID.
Example: xconguration conference h323alias id: MyH323AliasId
Conference PeriodicIntra: <0..1000>
Use this setting to generate a new intra frame with a congurable interval. Use this setting with caution since it in a normal network will decrease the video quality. The default value is set to 0 which means off. If you congure it to 10 it will send an intra every 10th second.
Example: xconguration conference periodicintra: 0
CameraSwUpgrade — Conference
74
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Conguration-type Commands – xconguration / conguration.xml
D 138 87.08
MAY 2008
Conference SIP URI: <S: 0, 60>
The SIP URI is the address to use when calling the system using SIP.
Example: xconguration conference sip uri: MySIP_URI
Conference H263: <On/Off>
Enables/disables H.263 for both transmit and receive.
Example: xconguration conference h263: off
Conference H264: <On/Off>
Enables/disables H.264 for both transmit and receive.
Example: xconguration conference h264: on
Conference H264RCDO: <On/Off>
Enables/disables H.264 RCDO for both transmit and receive.
Example: xconguration conference h264rcdo: off
Conference G722: <On/Off>
Enables/disables G.722 for both transmit and receive.
Example: xconguration conference g722: on
Conference G722.1: <On/Off>
Enables/disables G.722.1 for both transmit and receive.
Example: xconguration conference g722.1: on
Conference G728: <On/Off>
Enables/disables G.728 for both transmit and receive.
Example: xconguration conference g728: on
Conference AAC-LD: <On/Off>
Enables/disables AAC-LD for both transmit and receive.
Example: xconguration 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: xconguration conference h331: on
Conference H239: <On/Off>
Enables/disables H.239 for both transmit and receive.
Example: xconguration conference h239: on
Conference cont...
75
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Conguration-type Commands – xconguration / conguration.xml
D 138 87.08
MAY 2008
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 specied threshold.
Example: xconguration 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: xconguration 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) elds 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 congured to be enabled for callrates above a specied threshold
value.
Example: xconguration 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: xconguration conference picturemode: auto
Conference VideoQualityCP: <Motion/Sharpness/Auto>
Sets the video quality to be used in continuous presence mode (4Split/5+1Split).
Example: xconguration conference videoqualitycp: sharpness
Conference FloorToFull: <On/Off>
If PictureMode is set to 5+1Split, and one of the participants in a MultiSite conference is granted oor this setting determines whether to display the participant having oor in full
screen or just in the main window of the 5+1Split.
Example: xconguration conference oortofull: on
Conference MaxCallLength: <0..999>
Sets the maximum allowed call length in minutes (0 = Disabled).
Example: xconguration 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: xconguration 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: xconguration conference allowincomingmscall: off
Conference cont...
76
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Conguration-type Commands – xconguration / conguration.xml
D 138 87.08
MAY 2008
Conference Downspeed: <On/Off>
Determines whether or not to allow downspeeding.
Example: xconguration 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: xconguration conference fallbacktotelephony: on
Conference Encryption Mode: <On/Off/Auto>
If set to On, the system will not allow unencrypted calls.
If set to Auto, the system will use encryption whenever possible.
If set to Off, encryption will not be used.
Example: xconguration conference encryption mode: auto
Conference Encryption Type: <Auto/DES/AES-128>
Denes 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 on ISDN and IP. If all other sites do not support DES, no other
type of encryption will be initiated.
Example: xconguration 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: xconguration conference aim: on
Conference IPLR Transmit: <On/Off>
Enables/disables Intelligent Packetloss Recovery
Example: xconguration 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 le system.
NOTE! This conguration can only be set using the RS232 port.
Example: xconguration conference websnapshots: on
Conference BillingCode: <On/Off>
This conguration is only relevant when when placing calls using the TANDBERG remote control and the on screen menu. If set to on, all user s 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: xconguration conference billingcode: on
Conference cont...
77
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Conguration-type Commands – xconguration / conguration.xml
D 138 87.08
MAY 2008
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 reect the IP Dualstream Rate
settings of the sender. The settings are 25%, 50% and 75% of the total available video stream.
Example: xconguration 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: xconguration 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 congured to display the names for a period
of time or as long as you are connected.
Example: xconguration 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: xconguration conference videotext: 0
CorporateDirectory Mode: <On/Off>
Enables/disables use of a CorporateDirectory stored on a remote ser ver.
Example: xconguration corporatedirectory mode: on
CorporateDirectory Address: <S: 0, 64>
Species the address to the server where the CorporateDirector y is located.
Example: xconguration corporatedirectory address: 10.47.6.75
CorporateDirectory Path: <S: 0, 255>
Species the path to the CorporateDirectory on the ser ver.
Example: xconguration 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: xconguration corporatedirectory protocol:
DefaultPIPPosition: <BottomLeft/BottomRight/TopLeft/TopRight>
Species the default positioning of the PIP (Picture In Picture).
Example: xconguration defaultpipposition: bottomleft
Conference cont... — DefaultPiPPosition
78
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Conguration-type Commands – xconguration / conguration.xml
D 138 87.08
MAY 2008
Directory CallLog: <On/Off>
Enable/disable Call Logs for Placed calls, Missed calls and Received calls in the Phone Book.
Example: xconguration directory calllog: on
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: xconguration 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: xconguration dualmonitor mode: on
DuoVideoSource: <0/1/2/3/4/5/6>
Denes which video input to be used as the default Dual Stream source. NOTE! 0 means None
Example: xconguration duovideosource: 1
DynamicResolution Mode: <On/Off>
With Dynamic Resolution the system will use the optimal video resolution for the chosen bandwidth. This feature is only applicable to HD (high denition) 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 star t 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: xconguration dynamicresolution mode: off
E1 Interface CRC4: <On/Off>
E1 CRC-4 is used for most E1-PRI congurations. You can turn it off if not supported by the E1 network equipment.
Example: xconguration 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: xconguration ethernet 1 speed: auto
ExternalManager Address: <S: 0, 64>
Species the address to the External Manager/Management system.
Example: xconguration externalmanager address: “10.47.6.75”
If an External Mana ger address a nd a path is configured, the sys tem will post an H TTP mes sage to this
address when star ting up. When r eceiving t his HTTP
posting the Exter nal Manage r (typically a manageme nt
system) can retu rn configu rations/commands to the
unit as a result .
If the DHC P Option 242 is retur ned in the DHCP response fro m the DHCP s erver th e system will inte rpret
this as the E xternal M anager address to use.
ExternalManager Path: <S: 0, 255>
Species the path to the External Manager/Management system.
Example: xconguration externalmanager path: tms/public/external/management/SystemMan-
agementService.asmx
Directory — ExternalManager
79
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Conguration-type Commands – xconguration / conguration.xml
D 138 87.08
MAY 2008
ExternalManager Protocol: <HTTP/HTTPS>
Enables/disables secure management.
Example: xconguration externalmanager protocol: http
ExternalNetwork Clocking: <Dual/Single>
Dual: (RS44 9/V35 Compatible) Use this setting when the external e quipment pr ovides two clock signals, one for transmit and one fo r receive. (The difference bet ween
RS449 and V35 lies solely in t he cable).
Single: (X21 Compat ible) Use this set ting when th e external e quipment provides a com mon clock sig nal for both t ransmit and r eceive.
Example: xconguration 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 por ts.
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 specic sufxes to the dialled number. Should only be used when connected to an ADTRAN IMUX.
The Adtran IMUX uses the following sufxes <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 prex/sufx table which describes the available bandwidths. The prexes/sufxes are set from the Web Interface or Command Line inter-
face. The user (administrator) shall be able to specify a IMUX prex/sufx 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: xconguration externalnetwork callcontrol: rs366
ExternalNetwork DTRPulse: <On/Off>
Congures 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: xconguration externalnetwork dtrpulse: on
ExternalServices Mode: <On/Off>
Enables/disables External Services
Example: xconguration externalservices mode: on
Exter nal Ser vices allows a t hird par ty integr ator to
present se rvice s on the unit usin g XHTML 1.0 strict and
H TT P.
If turned on, a menu choice w ill appear in th e servi ces
menu, and on entering this th e TANDBERG unit w ill
retrieve a default XHTML page as specified in th e External Ser vices conf iguration menu.
ExternalServices Address: <S: 0, 64>
Congures the External Services address.
Example: xconguration externalservices address: 10.47.6.75
ExternalServices Path: <S: 0, 255>
Congures the External Services path.
Example: xconguration externalservices path: “tms/public/EndpointService/”
ExternalManager — ExternalServices
80
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Conguration-type Commands – xconguration / conguration.xml
D 138 87.08
MAY 2008
ExternalServices Protocol: <HTTP/HTTPS>
Enables/disables secure management.
Example: xconguration externalservices protocol: http
FECC Mode: <On/Off>
Sets whether or not to allow the remote site to control the cameras connected to the system.
Example: xconguration fecc mode: on
FeedbackFilter Conference: <0..10>
Denes the Feedback lter (in seconds) for the Conference status element.
Example: xconguration feedbacklter conference: 4
Only releva nt if using feedback (xfe edback over RS-232/Telnet or feedback
over HTT P).
The feedb ack filter l ets the user co nfigure th e maximun fr equency b etween
feedbac k updates. That means if data changes very rapidly, the control appplication will not receive feedback more frequent than every xth second. This will help
reducing the load on both the link and the control system, but some transition
informat ion might be lost.
FeedbackFilter Call: <0..10>
Denes the Feedback lter (in seconds) for the Call status element.
Example: xconguration feedbacklter call: 2
FTP Mode: <On/Off>
Enables or disables the systems embedded FTP server.
Example: xconguration ftp mode: on
G703 PhysicalLayer: <E1/T1>
Selects whether the leased line is E1 or T1.
Example: xconguration g703 physicallayer: e1
G703 Linecoding: <b8zsRestrict/b8zsNoRestrict>
Selects whether the Leased line is a 56kb network (restricted) or a 64kb network.
Example: xconguration 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: xconguration g703 callcontrol: auto
G703 Interface Star tChannel: <1..31>
Indicates the rst 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: xconguration g703 interface startchannel: 6
ExternalServices — G703
81
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Conguration-type Commands – xconguration / conguration.xml
D 138 87.08
MAY 2008
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: xconguration g703 interface maxchannels: 12
H320 NetType: <BRI/PRI/External/G703/None>
NetType: <BRI/None> (Codec 3000)
NetType: <External/None> (Codec 3000NET)
Denes the network type to use for H.320 calls.
Example: xconguration h320 nettype: bri
H323 Mode: <On/Off>
Enables/disables the possibility to place and receive H.323 calls.
Example: xconguration h323 mode: on
H323CallSetup Mode: <Direct/Gatekeeper/CallManager>
Denes 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: xConguration h323callsetup mode: gatekeeper
H323Gatekeeper Discover y: <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 specic 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 specied manually.
Manual: The system will use a specic gatekeeper identied by H323Gatekeeper Address.
Example: xconguration h323gatekeeper discovery: manual
H323Gatekeeper Address: <S: 0, 64>
Species the address of the gatekeeper to use if Discovery is set to Manual.
Example: xconguration h323gatekeeper address: 10.47.9.1
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 specied gatekeeper (xconguration H323Gatekeeper Address) is an Avaya gatekeeper. This enables Avaya-specic behaviour. An
Avaya gatekeeper is called Avaya Communication Manager - Avaya CM for short).
Example: xconguration h323gatekeeper avaya mode: off
G703 cont... — H323Gatekeeper
82
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Conguration-type Commands – xconguration / conguration.xml
D 138 87.08
MAY 2008
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: xconguration 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: xconguration 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: xconguration h323gatekeeper avaya password: 123
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:
H.323 ID1.
International Name2.
System Nam e3.
Example: xconguration 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: xconguration 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: xconguration h323gatekeeper authentication id: TANDBERG
H323Gatekeeper cont...
83
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Conguration-type Commands – xconguration / conguration.xml
D 138 87.08
MAY 2008
H323Gatekeeper Authentication Password: <S: 0, 49>
Please see above. NOTE! The password will not be listed when polling.
Example: xconguration h323gatekeeper authentication password: xxx
H323Prex: <S: 0, 4>
When dialling a number prexed with digits specied by H.323 Prex, and with Net: Auto, an H.323 call will be placed.
Example: xconguration h323prex: 5
HTTP Mode: <On/Off>
Enables/disables HTTP.
Example: xconguration http mode: on
HTTPS Mode: <On/Off>
Enables/disables HTTPS.
Example: xconguration https mode: on
HTTPS VerifySer verCerticate: <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 congure secure HTTPS between TANDBERG products. To nd the document, follow the link: http://www.tandberg.com/support/
documentation.php and select White Papers.
Example: xconguration https verifyservercerticate: on
IdReport H323: <H323Id/E164Alias/IPAddress>
Selects what identier to present as remote number for incoming H.323 calls.
Example: xconguration idreport h323: h323id
H323Gatekeeper cont... — IdReport
84
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Conguration-type Commands – xconguration / conguration.xml
D 138 87.08
MAY 2008
IEEE802.1x Mode: <On/Off>
Enables/disables 802.1x authentication
Example: xconguration ieee802.1x mode: on
The system may be connec ted
to an IEEE 802.1 x LAN network. Supp orted 8 02.1x proto cols are EA P-MD5, EAP- PEA P
and EAP -TTLS.
IEEE802.1x AnonymousIdentity: <S: 0, 64>
The 802.1x Anonymous ID string is to be used as unencrypted 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 (unencrypted) EAP Identity Request
Example: xconguration ieee802.1x anonymousidentity:
IEEE802.1x Identity: <S: 0, 64>
The 802.1x Username is the username needed for 802.1x authentication.
Example: xconguration ieee802.1.x identity: MyString
IEEE802.1x Password: <S: 0, 64>
The 802.1x Password is the password needed for 802.1x authentication.
Example: xconguration ieee802.1x password: MyPassword
IEEE802.1x EAP-MD5: <On/Off>
Enables/disables the EAP-MD5 protocol
Example: xconguration ieee802.1.x eap-md5: on
IEEE802.1x EAP-TTLS: <On/Off>
Enables/disables the EAP-TTLS protocol
Example: xconguration ieee802.1.x eap-ttls: on
IEEE802.1x EAP-PEAP: <On/Off>
Enables/disables the EAP-PEAP protocol
Example: xconguration ieee802.1.x eap-peap: on
IMUX Custom BW64 Prex: <S: 0, 12>
Denes the prex to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconguration imux custom bw64 prex: xxx
IMUX Custom BW64 Sufx: <S: 0, 12>
Denes the sufx to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconguration imux custom bw64 sufx: xxx
IMUX Custom BW64R Prex: <S: 0, 12>
Denes the prex to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconguration imux custom bw64r prex: xxx
IEEE802.1x cont... — IMUX
85
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Conguration-type Commands – xconguration / conguration.xml
D 138 87.08
MAY 2008
IMUX Custom BW64R Sufx: <S: 0, 12>
Denes the sufx to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconguration imux custom bw64r sufx: xxx
IMUX Custom BW128 Prex: <S: 0, 12>
Denes the prex to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconguration imux custom bw128 prex: xxx
IMUX Custom BW128 Sufx: <S: 0, 12>
Denes the sufx to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconguration imux custom bw128 sufx: xxx
IMUX Custom BW128R Prex: <S: 0, 12>
Denes the prex to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconguration imux custom bw128r prex: xxx
IMUX Custom BW128R Sufx: <S: 0, 12>
Denes the sufx to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconguration imux custom bw128r sufx: xxx
IMUX Custom BW192 Prex: <S: 0, 12>
Denes the prex to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconguration imux custom bw192 prex: xxx
IMUX Custom BW192 Sufx: <S: 0, 12>
Denes the sufx to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconguration imux custom bw192 sufx: xxx
IMUX Custom BW192R Prex: <S: 0, 12>
Denes the prex to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconguration imux custom bw192r prex: xxx
IMUX Custom BW192R Sufx: <S: 0, 12>
Denes the sufx to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconguration imux custom bw128r sufx: xxx
IMUX Custom BW256 Prex: <S: 0, 12>
Denes the prex to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconguration imux custom bw256 prex: xxx
IMUX cont...
86
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Conguration-type Commands – xconguration / conguration.xml
D 138 87.08
MAY 2008
IMUX Custom BW256 Sufx: <S: 0, 12>
Denes the sufx to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconguration imux custom bw256 sufx: xxx
IMUX Custom BW256R Prex: <S: 0, 12>
Denes the prex to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconguration imux custom bw256r prex: xxx
IMUX Custom BW256R Sufx: <S: 0, 12>
Denes the sufx to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconguration imux custom bw256r sufx: xxx
IMUX Custom BW320 Prex: <S: 0, 12>
Denes the prex to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconguration imux custom bw320 prex: xxx
IMUX Custom BW320 Sufx: <S: 0, 12>
Denes the sufx to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconguration imux custom bw320 sufx: xxx
IMUX Custom BW320R Prex: <S: 0, 12>
Denes the prex to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconguration imux custom bw320r prex: xxx
IMUX Custom BW320R Sufx: <S: 0, 12>
Denes the sufx to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconguration imux custom bw320r sufx: xxx
IMUX Custom BW384 Prex: <S: 0, 12>
Denes the prex to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconguration imux custom bw384 prex: xxx
IMUX Custom BW384 Sufx: <S: 0, 12>
Denes the sufx to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconguration imux custom bw384 sufx: xxx
IMUX Custom BW384R Prex: <S: 0, 12>
Denes the prex to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconguration imux custom bw384r prex: xxx
IMUX cont...
87
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Conguration-type Commands – xconguration / conguration.xml
D 138 87.08
MAY 2008
IMUX Custom BW384R Sufx: <S: 0, 12>
Denes the sufx to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconguration imux custom bw384r sufx: xxx
IMUX Custom BW512 Prex: <S: 0, 12>
Denes the prex to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconguration imux custom bw512 prex: xxx
IMUX Custom BW512 Sufx: <S: 0, 12>
Denes the sufx to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconguration imux custom bw512 sufx: xxx
IMUX Custom BW512R Prex: <S: 0, 12>
Denes the prex to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconguration imux custom bw512r prex: xxx
IMUX Custom BW512R Sufx: <S: 0, 12>
Denes the sufx to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconguration imux custom bw512r sufx: xxx
IMUX Custom BW768 Prex: <S: 0, 12>
Denes the prex to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconguration imux custom bw768 prex: xxx
IMUX Custom BW768 Sufx: <S: 0, 12>
Denes the sufx to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconguration imux custom bw768 sufx: xxx
IMUX Custom BW768R Prex: <S: 0, 12>
Denes the prex to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconguration imux custom bw768r prex: xxx
IMUX Custom BW768R Sufx: <S: 0, 12>
Denes the sufx to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconguration imux custom bw768r sufx: xxx
IMUX Custom BW1152 Prex: <S: 0, 12>
Denes the prex to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconguration imux custom bw1152 prex: xxx
IMUX cont...
88
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Conguration-type Commands – xconguration / conguration.xml
D 138 87.08
MAY 2008
IMUX Custom BW1152 Sufx: <S: 0, 12>
Denes the sufx to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconguration imux custom bw1152 sufx: xxx
IMUX Custom BW1152R Prex: <S: 0, 12>
Denes the prex to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconguration imux custom bw1152r prex: xxx
IMUX Custom BW1152R Sufx: <S: 0, 12>
Denes the sufx to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconguration imux custom bw1152r sufx: xxx
IMUX Custom BW1472 Prex: <S: 0, 12>
Denes the prex to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconguration imux custom bw1472 prex: xxx
IMUX Custom BW1472 Sufx: <S: 0, 12>
Denes the sufx to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconguration imux custom bw1472 sufx: xxx
IMUX Custom BW1472R Prex: <S: 0, 12>
Denes the prex to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconguration imux custom bw1472r prex: xxx
IMUX Custom BW1472R Sufx: <S: 0, 12>
Denes the sufx to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconguration imux custom bw1472r sufx: xxx
IMUX Custom BW1920 Prex: <S: 0, 12>
Denes the prex to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconguration imux custom bw1920 prex: xxx
IMUX Custom BW1920 Sufx: <S: 0, 12>
Denes the sufx to be used with the RS366 Custom IMUX at this bandwidth.
Example: xconguration imux custom bw1920 sufx: xxx
IMUX Custom BW1920R Prex: <S: 0, 12>
Denes the prex to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconguration imux custom bw1920r prex: xxx
IMUX cont...
89
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Conguration-type Commands – xconguration / conguration.xml
D 138 87.08
MAY 2008
IMUX Custom BW1920R Sufx: <S: 0, 12>
Denes the sufx to be used with the RS366 Custom IMUX at this restricted bandwidth.
Example: xconguration imux custom bw1920r sufx: 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 transmitted as a UDP packet to 239.255.250.250 on port 9131 at random intervals between 30 and 60 secs. The transmission of the Beacon message is by
default set to Off.
Example: xconguration integrator amxbeacon mode: off
Integrator Telepresence Mode: <Off/Point2Point/MultiPoint/Briefer>
Only in use with TANDBERG Experia.
Example: xconguration integrator telepresence mode: off
IP Assignment: <DHCP/Static>
Denes whether to use DHCP or Static IP assignment. NOTE! This conguration only applies to IPv4.
Example: xconguration ip assignment: dhcp
IP Address: <IPAddr>
Denes the IPv4 address to use. Only applicable if Static IP assignment is being used.
Example: xconguration ip address:
IP SubnetMask: <IPAddr>
Denes the subnet mask. Only applicable if Static IP assignment is being used.
Example: xconguration ip subnetmask:
IP V6 Address: <IPv6Addr : 0, 43>
Allows static conguration of IP v6 Address.
Example: xConguration ip v6 address:
IP Gateway: <IPAddr>
Denes the gateway address. Only applicable if Static IP assignment is being used.
Example: xconguration ip gateway:
IP DNS Ser ver [1..5] Address: <IPv4v6Addr: 0, 43>
Denes the network addresses for DNS servers. Up to 5 addresses may be specied. If the network addresses are unknown,
please contact your administrator or Internet Service Provider.
Example: xconguration ip dns server:
IP DNS Domain Name: <S: 0, 64>
DNS Domain Name is the default domain name sufx which is added to unqualied names.
Example: DNS Domain Name is “example.com”, and the name to lookup is “videosystem” will result in a “videosystem.
example.com” DNS lookup.
IMUX cont... — IP
90
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Conguration-type Commands – xconguration / conguration.xml
D 138 87.08
MAY 2008
IPMedia MaxVideoTXRate: <64..4096>
The MaxVideoTXRate (kbps) denes 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 ofces with different upstream and downstream rates, typically ADSL.
Example: xconguration ipmedia maxvideotxrate: 384
IPProtocol: <IPv4/IPv6/Both>
Denes what IP protocol to use. If set to Both the system will support both IPv4 and IPv6.
Example: xconguration ipprotocol: both
IRControl Mode: <On/Off>
Enables/disables the TANDBERG Remote Control.
Example: xconguration 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 congured to act automatically or manually.
Please refer to the Endpoint User Guides for further details.
Example: xconguration ircontrol numberkeymode: DTMF
ISDN CliNumbSpec: <On/Off>
Explicitely specify Calling Party Number elds 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: xConguration isdn clinumbspec: Off
ISDN CliNumbType: <0..6>
Value to be used for Calling Party Number eld 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: xConguration isdn clinumbtype: 5
ISDN CliNumbPlan: <0..14>
Value to be used for Calling Party Number eld 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 required in UAE.
Example: xConguration 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: xconguration 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: xconguration isdn sendnumber: on
IPMedia — ISDN
91
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Conguration-type Commands – xconguration / conguration.xml
D 138 87.08
MAY 2008
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: xconguration 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: xconguration isdn hlc: on
ISDN SpeechTimers: <On/Off>
ISDN Layer 3, telephony calls. When set to Off, there will be no T310, T304, T301
Example: xconguration 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 On only calls to numbers specied for the specic ISDN interfaces will be answered. This service can be ordered from your telephone company.
Example: xconguration 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 addresses. 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: xconguration isdn subaddress: 15
ISDN PRI NSFTelephony Mode: <On/Off>
Enables/disables use of NSF for telephony. NSF = Network Service Facility
Example: xconguration isdn pri nsftelephony mode: on
ISDN cont...
92
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Conguration-type Commands – xconguration / conguration.xml
D 138 87.08
MAY 2008
ISDN PRI NSFTelephony Number: <0..31>
Denes what Service Facility to use for telephony if the NSFTelephony Mode is set to On.
Example: xconguration isdn pri nsftelephony number: 8
ServiceprolesforSprint(ref.2):
NSF Service
0 Reserved
1 Private
2 Inwatts
3 Outwatts
4 FX
5 TieTrunk
ServiceprolesforMCI(ref.3):
NSF Service
1 VNET/Vision
2 800
3 PRISM1, PRISMII, WATS
4 900
5 DAL
ServiceprolesforAT&T(ref.1):
NSF Service
0 Disable
1 SDN (including GSDN)
2 Toll Free Megacom (800)
3 Megacom
6 ACCUNET Switched Digital Service (including Switched Digital International)
7 Long Distance Service (including AT&T World Connect)
8 International Toll Free Service (I800)
16 AT&T MultiQuest
23 Call Redirection Service
ISDN PRI NSFVideoTelephony Mode: <On/Off>
Enables/disables use of NSF for videotelephony. NSF = Network Service Facility
Example: xconguration isdn pri nsfvideotelephony mode: on
ISDN PRI NSFVideoTelephony Number: <0..31>
Denes what Service Facility to use for videotelephony if NSFVideoTelephony Mode is set to On.
Example: xconguration isdn pri nsfvideotelephony number: 8
ISDN PRI SwitchType: <NI/ATT/Euro/Japan>
Selects the type of PRI switch the system is connected to.
Example: xconguration isdn pri switchtype: ni
ISDN PRI InitialRestart: <On/Off>
When restart is set to on the PRI interfaces will be reinitialized after boot.
Example: xconguration 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 rst incoming channel.
Example: xconguration 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: xconguration isdn pri chanid: on
ISDN cont...
93
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Conguration-type Commands – xconguration / conguration.xml
D 138 87.08
MAY 2008
ISDN PRI L2WindowSize: <1..7>
Max. No. of outstanding Iframes (ISDN Layer 2)
Example: xconguration isdn pri L2windowsize:
ISDN PRI Interface MaxChannels: <1..30>
Maximum number of channels the system may use at any given time.
Example: xconguration 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: xconguration 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: xconguration 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: xconguration isdn pri interface search: high
ISDN PRI Interface NumberRangeStar t: <S: 0, 24>
Denes the number range start, supported by the PRI interface.
Example: xconguration isdn pri interface numberrangestart: 1
ISDN PRI Interface NumberRangeStop: <S: 0, 24>
Denes the number range stop, supported by the PRI interface.
Example: xconguration isdn pri interface numberrangestop: 8
ISDN BRI SwitchType: <NI/ATT/Euro/1TR6/Japan/Australia/FETEX>
Selects BRI network type.
Example: xconguration isdn bri switchtype: att
ISDN BRI AutoActivation: <Off/Selected/All>
(ISDN Layer 1) Autoactivation of interface. Selected will activate those already On, All will activate all interfaces regardless of status.
Example: xconguration isdn bri autoactivation: all
ISDN BRI MaxDeactiveTime: <1..60>
Max duration for Layer 1 in deactive state before auto activation (re)starts
Example: xconguration isdn bri maxdeactivetime:
ISDN cont...
94
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Conguration-type Commands – xconguration / conguration.xml
D 138 87.08
MAY 2008
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 rst incoming channel.
Example: xconguration 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: xconguration 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: xconguration isdn bri interfacesearch: high
ISDN BRI Interface [1..6] Mode: <On/Off>
Enables/disables the various BRI interfaces.
Example: xconguration isdn bri interface 4 mode: off
ISDN BRI Interface [1..6] DirectoryNumber [1..2]: <S: 0, 24>
Species the Directory Numbers for the various BRI interfaces.
Example: xconguration 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 SPIDAutoCongure should be used.
Example: xconguration isdn bri interface 4 spid 2: 55
Keyboard Layout: <English/US/Norwegian/Swedish/German/French/User>
Denes the layout of the keyboard, if connected.
Example: xconguration keyboard layout: us
Kiosk Mode: <On/Off>
Enables (On) or diables (Off) Kiosk mode.
Example: xconguration kiosk mode: on
Key Number0: <On/Off>
Enable or disable the given key on the TANDBERG Remote Control, and using conguration instead of commands.
Example: xconguration key number0: on
Key Number1: <On/Off>
Enable or disable the given key on the TANDBERG Remote Control, and using conguration instead of commands.
Example: xconguration key number1: on
ISDN cont... — Key
95
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Conguration-type Commands – xconguration / conguration.xml
D 138 87.08
MAY 2008
Key Number2: <On/Off>
Enable or disable the given key on the TANDBERG Remote Control, and using conguration instead of commands.
Example: xconguration key number2: on
Key Number3: <On/Off>
Enable or disable the given key on the TANDBERG Remote Control, and using conguration instead of commands.
Example: xconguration key number3: on
Key Number4: <On/Off>
Enable or disable the given key on the TANDBERG Remote Control, and using conguration instead of commands.
Example: xconguration key number4: on
Key Number5: <On/Off>
Enable or disable the given key on the TANDBERG Remote Control, and using conguration instead of commands.
Example: xconguration key number5: on
Key Number6: <On/Off>
Enable or disable the given key on the TANDBERG Remote Control, and using conguration instead of commands.
Example: xconguration key number6: on
Key Number7: <On/Off>
Enable or disable the given key on the TANDBERG Remote Control, and using conguration instead of commands.
Example: xconguration key number7: on
Key Number8: <On/Off>
Enable or disable the given key on the TANDBERG Remote Control, and using conguration instead of commands.
Example: xconguration key number8: on
Key Number9: <On/Off>
Enable or disable the given key on the TANDBERG Remote Control, and using conguration instead of commands.
Example: xconguration key number9: on
Key Star : <On/Off>
Enable or disable the given key (*) on the TANDBERG Remote Control, and using conguration instead of commands.
Example: xconguration key star: on
Key Square: <On/Off>
Enable or disable the given key (#) on the TANDBERG Remote Control, and using conguration instead of commands.
Example: xconguration key square: on
Key cont...
96
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Conguration-type Commands – xconguration / conguration.xml
D 138 87.08
MAY 2008
Key Connect: <On/Off>
Enable or disable the given key (green Call key) on the TANDBERG Remote Control, and using conguration instead of commands.
Example: xconguration key connect: on
Key Disconnect: <On/Off>
Enable or disable the given key (red End Call key) on the TANDBERG Remote Control, and using conguration instead of commands.
Example: xconguration key disconnect: on
Key Up: <On/Off>
Enable or disable the given key (arrow up) on the TANDBERG Remote Control, and using conguration instead of commands.
Example: xconguration key up: on
Key Down: <On/Off>
Enable or disable the given key (arrow down) on the TANDBERG Remote Control, and using conguration instead of commands.
Example: xconguration key down: on
Key Right: <On/Off>
Enable or disable the given key (arrow right) on the TANDBERG Remote Control, and using conguration instead of commands.
Example: xconguration key right: on
Key Left: <On/Off>
Enable or disable the given key (arrow left) on the TANDBERG Remote Control, and using conguration instead of commands.
Example: xconguration key left: on
Key Selfview: <On/Off>
Enable or disable the given key (Selfview) on the TANDBERG Remote Control, and using conguration instead of commands.
Example: xconguration key selfview: on
Key Layout: <On/Off>
Enable or disable the given key (Layout) on the TANDBERG Remote Control, and using conguration instead of commands.
Example: xconguration key layout: on
Key Phonebook: <On/Off>
Enable or disable the given key (Phonebook) on the TANDBERG Remote Control, and using conguration instead of commands.
Example: xconguration key phonebook: on
Key Cancel: <On/Off>
Enable or disable the given key (x - Cancel) on the TANDBERG Remote Control, and using conguration instead of commands.
Example: xconguration key cancel: on
Key cont...
97
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Conguration-type Commands – xconguration / conguration.xml
D 138 87.08
MAY 2008
Key MicOff: <On/Off>
Enable or disable the given key (yellow Mic Off key) on the TANDBERG Remote Control, and using conguration instead of commands.
Example: xconguration key micoff: on
Key Presentation: <On/Off>
Enable or disable the given key (blue Presentation key) on the TANDBERG Remote Control, and using conguration instead of commands.
Example: xconguration key presentation: on
Key VolumeUp: <On/Off>
Enable or disable the given key (Volume +) on the TANDBERG Remote Control, and using conguration instead of commands.
Example: xconguration key volumeup: on
Key VolumeDown: <On/Off>
Enable or disable the given key (Volume –) on the TANDBERG Remote Control, and using conguration instead of commands.
Example: xconguration key volumedown: on
Key Ok: <On/Off>
Enable or disable the given key (OK - Menu key) on the TANDBERG Remote Control, and using conguration instead of commands.
Example: xconguration key ok: on
Key ZoomIn: <On/Off>
Enable or disable the given key (Zoom +) on the TANDBERG Remote Control, and using conguration instead of commands.
Example: xconguration key zoomin: on
Key ZoomOut: <On/Off>
Enable or disable the given key (Zoom –) on the TANDBERG Remote Control, and using conguration instead of commands.
Example: xconguration 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: xconguration key grab: on
Key Cabinet: <On/Off>
Enables/disables the headset key in front of the cabinet. Applies to TANDBERG 1000 MXP only.
Example: xconguration key cabinet: on
Key Presets: <On/Off>
Enable or disable the given key on the TANDBERG Remote Control (TRC4), and using conguration instead of commands.
Example: xconguration key presets: on
Key cont...
98
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Conguration-type Commands – xconguration / conguration.xml
D 138 87.08
MAY 2008
Key FarEnd: <On/Off>
Enable or disable the given key on the TANDBERG Remote Control (TRC4), and using conguration instead of commands.
Example: xconguration key farend: on
Key Ser vices: <On/Off>
Enable or disable the given key on the TANDBERG Remote Control (TRC4), and using conguration instead of commands.
Example: xconguration key services: on
Key Help: <On/Off>
Enable or disable the given key on the TANDBERG Remote Control (TRC4), and using conguration instead of commands.
Example: xconguration key help: on
Key MainCam: <On/Off>
Enable or disable the given key on the TANDBERG Remote Control (TRC4), and using conguration instead of commands.
Example: xconguration key maincam: on
Key PC: <On/Off>
Enable or disable the given key on the TANDBERG Remote Control (TRC4), and using conguration instead of commands.
Example: xconguration key pc: on
Key DocCam: <On/Off>
Enable or disable the given key on the TANDBERG Remote Control (TRC4), and using conguration instead of commands.
Example: xconguration key doccam: on
Key VCR: <On/Off>
Enable or disable the given key on the TANDBERG Remote Control (TRC4), and using conguration instead of commands.
Example: xconguration key vcr: on
Key AUX: <On/Off>
Enable or disable the given key on the TANDBERG Remote Control (TRC4), and using conguration instead of commands.
Example: xconguration key aux: on
Kiosk Menu: <On/Off>
Enables (On) or diables (Off) Kiosk menu to appear on screen.
Example: xconguration kiosk menu: on
Kiosk LanguageMenu Mode: <On/Off>
Enables (On) or diables (Off) language menu in Kiosk mode.
Example: xconguration kiosk languagemenu mode: on
Key cont... — Kiosk
99
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Conguration-type Commands – xconguration / conguration.xml
D 138 87.08
MAY 2008
Kiosk LanguageMenu English: <On/Off>
Enables (On) or diables (Off) language menu in English.
Example: xconguration kiosk languagemenu english: on
Kiosk LanguageMenu Ger man: <On/Off>
Enables (On) or diables (Off) language menu in German
Example: xconguration kiosk languagemenu german: on
Kiosk LanguageMenu French: <On/Off>
Enables (On) or diables (Off) language menu in French
Example: xconguration kiosk languagemenu french: on
Kiosk LanguageMenu Italian: <On/Off>
Enables (On) or diables (Off) language menu in Italian
Example: xconguration kiosk languagemenu italian: on
Kiosk LanguageMenu Norwegian: <On/Off>
Enables (On) or diables (Off) language menu in Norwegian
Example: xconguration kiosk languagemenu norwegian: on
Kiosk LanguageMenu Swedish: <On/Off>
Enables (On) or diables (Off) language menu in Swedish
Example: xconguration kiosk languagemenu swedish: on
Kiosk LanguageMenu Spanish: <On/Off>
Enables (On) or diables (Off) language menu in Spanish
Example: xconguration kiosk languagemenu spanish: on
Kiosk AllowIRControl: <On/Off>
Enables (On) or diables (Off) the use of all keys on the remote control.
Example: xconguration kiosk allowircontrol: on
Kiosk Phonebook: <Local/CorporateDirector y>
Local: The system will use the Local Phone Book in Kiosk Mode. CorporateDirectory: The system will use the Corporate Director y in Kiosk Mode.
Example: xconguration kiosk phonebook: local
Kiosk AutoDial: <On/Off>
Enables (On) or diables (Off) autodial. The system will automatically dial to the rst 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: xconguration kiosk autodial: on
Kiosk cont...
100
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
Conguration-type Commands – xconguration / conguration.xml
D 138 87.08
MAY 2008
Kiosk OneClickConnect: <On/Off>
If turned On, you can make a call with a single click on the green call button on the remote control. The system will call the rst entry in “My Contacts” in the Phone Book. NOTE:
This functionality will only work in Kiosk Mode. If set to Off: Does not allow for one click connect in Kiosk mode.
Example: xconguration kiosk oneclickconnect: off
LocalLayout Mode: <Full/2Split/POP/POPwide>
Denes the picture layout to use on the local main monitor. POP and POPWide should only be used on wide screen monitor s.
Example: xconguration locallayout mode: full
LocalLayout Toggle: <PIP/POP>
Denes the behaviour of the Layout button on 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: xconguration 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: xconguration logo: on
LoS Duration Exponent: <10..30>
Example: xconguration los duration exponent: 15
The duration of the LoS-pulse can be calculated from:
Duration =
Offset + 2
Exponent
bit rate
LoS congurations are relevant
for systems with NET interface
(External Network) only.
LoS Duration Offset: <0..65534>
Offset is specied in milliseconds
Example: xconguration los duration offset: 100
LoS Inhibit: <0..65534>
Species the number of seconds to wait before issuing a new LOS pulse if the codec regains and subsequently loses H.221 frame alignment.
Example: xconguration los inhibit: 15
Kiosk cont... — LoS
Loading...