Vai alla pagina of
Manuali d’uso simili
-
Network Card
TANDBERG D14128.02
130 pagine 10.25 mb -
Network Card
TANDBERG MSE 8420
20 pagine 1.85 mb -
Network Card
TANDBERG Management Server D13939
22 pagine 0.81 mb -
Network Card
TANDBERG D1408803
2 pagine 0.3 mb -
Network Card
TANDBERG MPS API Interface D13639
84 pagine 0.26 mb -
Network Card
TANDBERG MSE 8350
17 pagine 1.84 mb -
Network Card
TANDBERG D1392602
33 pagine 0.23 mb -
Network Card
TANDBERG D13939
22 pagine 0.77 mb
Un buon manuale d’uso
Le regole impongono al rivenditore l'obbligo di fornire all'acquirente, insieme alle merci, il manuale d’uso TANDBERG D13639. La mancanza del manuale d’uso o le informazioni errate fornite al consumatore sono la base di una denuncia in caso di inosservanza del dispositivo con il contratto. Secondo la legge, l’inclusione del manuale d’uso in una forma diversa da quella cartacea è permessa, che viene spesso utilizzato recentemente, includendo una forma grafica o elettronica TANDBERG D13639 o video didattici per gli utenti. La condizione è il suo carattere leggibile e comprensibile.
Che cosa è il manuale d’uso?
La parola deriva dal latino "instructio", cioè organizzare. Così, il manuale d’uso TANDBERG D13639 descrive le fasi del procedimento. Lo scopo del manuale d’uso è istruire, facilitare lo avviamento, l'uso di attrezzature o l’esecuzione di determinate azioni. Il manuale è una raccolta di informazioni sull'oggetto/servizio, un suggerimento.
Purtroppo, pochi utenti prendono il tempo di leggere il manuale d’uso, e un buono manuale non solo permette di conoscere una serie di funzionalità aggiuntive del dispositivo acquistato, ma anche evitare la maggioranza dei guasti.
Quindi cosa dovrebbe contenere il manuale perfetto?
Innanzitutto, il manuale d’uso TANDBERG D13639 dovrebbe contenere:
- informazioni sui dati tecnici del dispositivo TANDBERG D13639
- nome del fabbricante e anno di fabbricazione TANDBERG D13639
- istruzioni per l'uso, la regolazione e la manutenzione delle attrezzature TANDBERG D13639
- segnaletica di sicurezza e certificati che confermano la conformità con le norme pertinenti
Perché non leggiamo i manuali d’uso?
Generalmente questo è dovuto alla mancanza di tempo e certezza per quanto riguarda la funzionalità specifica delle attrezzature acquistate. Purtroppo, la connessione e l’avvio TANDBERG D13639 non sono sufficienti. Questo manuale contiene una serie di linee guida per funzionalità specifiche, la sicurezza, metodi di manutenzione (anche i mezzi che dovrebbero essere usati), eventuali difetti TANDBERG D13639 e modi per risolvere i problemi più comuni durante l'uso. Infine, il manuale contiene le coordinate del servizio TANDBERG in assenza dell'efficacia delle soluzioni proposte. Attualmente, i manuali d’uso sotto forma di animazioni interessanti e video didattici che sono migliori che la brochure suscitano un interesse considerevole. Questo tipo di manuale permette all'utente di visualizzare tutto il video didattico senza saltare le specifiche e complicate descrizioni tecniche TANDBERG D13639, come nel caso della versione cartacea.
Perché leggere il manuale d’uso?
Prima di tutto, contiene la risposta sulla struttura, le possibilità del dispositivo TANDBERG D13639, l'uso di vari accessori ed una serie di informazioni per sfruttare totalmente tutte le caratteristiche e servizi.
Dopo l'acquisto di successo di attrezzature/dispositivo, prendere un momento per familiarizzare con tutte le parti del manuale d'uso TANDBERG D13639. Attualmente, sono preparati con cura e tradotti per essere comprensibili non solo per gli utenti, ma per svolgere la loro funzione di base di informazioni e di aiuto.
Sommario del manuale d’uso
-
Pagina 1
TANDBERG MPS API User Guide TANDBERG D13639 Rev 07 March 2008[...]
-
Pagina 2
TANDBERG MPS API User Guide ii Table of Contents User Guide ..................................................................................................................... ............ 1 1 The TAND BERG API ............................................................................................................. . 1 1.1 Introducti on to XM[...]
-
Pagina 3
TANDBERG MPS API User Guide 1 1 The T ANDBERG API This document is a guide to the API interf ace of the TANDBERG M PS products. All rights reserved. This document contains information that is proprietary to TANDBERG. No pa rt of this publication may be reproduced, stored in a re trieval system, or transmitted, in any form, or by any means, electron[...]
-
Pagina 4
TANDBERG MPS API User Guide 2 1.1 Introduction to XML XML is a markup language for document s co ntaining structured information. All information elements in an XML document are marked by a tag and a correspondin g end- tag. The end-tag has the same name as the tag, but is prefixed with a sla sh, “/”. All tags are put within angular bracket s ([...]
-
Pagina 5
TANDBERG MPS API User Guide 3 Example 1.3 If we now look at the call element for an active call we see that call element contains a large sub-stru cture: <Status> <Call item="1" status="Synced" type="Vtlph" protocol="H323"> <CallRate item="1">768</CallRate> <RemoteNumber i[...]
-
Pagina 6
TANDBERG MPS API User Guide 4 <StopBits item="1">1</StopBits> <Mode item="1">Auto</Mode> </SerialPort> </Configuration>[...]
-
Pagina 7
TANDBERG MPS API User Guide 5 1.2 Introduction to XML Path Language (XPath) XPath is a comprehensive langu age to address data in XML documents. It is though very simple to understand the basi c s. If you are able to spe cify the path to a file on your computer, you are able to specify t he path to an element in a XML stru cture. Example 1.5 Let us[...]
-
Pagina 8
TANDBERG MPS API User Guide 6 Example 1.8 XPath also supports addressing by putting constr ain t s on eleme nt attributes. Let’s go back to the Call element in Example 1.2. The below expression will address the CallRate element of all Synced calls in a system: Status/Call[@status=”Synced”]/CallRate To add more constraints o n element attribut[...]
-
Pagina 9
TANDBERG MPS API User Guide 7 1.3 The TANDBERG XML Engine The TANDBERG XML engine is optimi ze d for advan ced machine-machine interaction between a TANDBERG system and an external contro l appli cation. The main features can be summarized to: • Structuring of information • Addressing using XPath • Feedback 1.3.1 Structuring of Informati on A[...]
-
Pagina 10
TANDBERG MPS API User Guide 8 configuration hierarchie s it wants to monitor by using XPath. The user/control ap plicatio n can therefore limit the amount of information it rece ives from the target system to only those pa rts being of interest for the given application.[...]
-
Pagina 11
TANDBERG MPS API User Guide 9 1.4 The XML Documents 1.4.1 Documents The XML Data in the TANDBERG systems a re divid ed into three main types of documents. The division is based on whether the informatio n is Read Information , Write Information or Read-Write information: 1. Status do cuments ( r) : Documents holding all availabl e Status Informatio[...]
-
Pagina 12
TANDBERG MPS API User Guide 10 <RemoteIPAddress item="1" /> <LocalIPAddress item="1">10.47.8.41:2326</LocalIPAddress> <Encryption item="1" status="On"> <Type item="1">AES-128</Type> </Encryption> <RSVP item="1">Off</RSVP> <RSVPRate i[...]
-
Pagina 13
TANDBERG MPS API User Guide 11 Example 10 From the XML structure below we see that the BaudRate element of SerialPort[1] is configured to 9600 . The BaudRate element references the SerialPortBaudrate element in the ValueSpace document, showing the value domain for this configu ration. <Configuration>> <SerialPort item="1"> [...]
-
Pagina 14
TANDBERG MPS API User Guide 12 <CallRate item="1" required="False" valueSpaceRef="/ValueSpace/Bandwidth"/> <Restrict item="1" required="False" valueSpaceRef="/ValueSpace/OnOff"/> <NetProfile item="1" required="False" valueSpaceRef="/ValueSpace/Netpro[...]
-
Pagina 15
TANDBERG MPS API User Guide 13 Example 14 Below is an example of the Dial comm and, not being accepted by the system: <Command> <DialResult item="1" status="Error"> <Cause item="1">17</Cause > <Description item="1">Too much bandwidth requested</Description > </DialResult[...]
-
Pagina 16
TANDBERG MPS API User Guide 14 1.5 Introduction to TANDBERG XML API Service (TXAS) TXAS is a service provided by TANDBERG units for transmitting and rece iving (transceiving) information encoded in XML format. The API uses HTTP(S) as the transport mech ani sm and connects to the normal web p ort (80). TXAS can be accessed in two ways; bare-bone HTT[...]
-
Pagina 17
TANDBERG MPS API User Guide 15 1.6 Exercises The exercises in this section are b ased on using a TANDBERG 6000 MXP codec and Microsoft Internet Explorer. Some of the exam ples may however also apply to other systems and other browsers. NOTE! Replace the ip address, 10.47.8. 41, in the bel ow exampl es with the ip address of your system. Exercise 1 [...]
-
Pagina 18
TANDBERG MPS API User Guide 16 <SerialPort> <BaudRate>2400</BaudRate> </SerialPort> <Conference> <H263>Off</H263> <Downspeed>Off</Downspeed> </Conference> </Configuration> --- <Command> <Dial> <Number>10.47.8.42</Number> </Dial> </Command> --- <[...]
-
Pagina 19
TANDBERG MPS API User Guide 17 2 The XML-based Advanced Command Line Interface The XML-based Advanced Command Line Interfa ce, XACLI, is a very flexible interface both optimized for machine-machine interacti on and man-machine interaction. It is based on the powerful TANDBERG XML engine and offers many of the same feature s as the T A NDBERG XML in[...]
-
Pagina 20
TANDBERG MPS API User Guide 18 2.1 XACLI 2.1.1 Accessing XACLI XACLI can be accessed through Telne t via the LA N interface or th rough RS-232 by connecting a serial cable to the serial interface co nnector, referred to as the Dataport . 48 Telnet sessions can be active at the same time in addition to the RS-232 con nection. 2.1.2 Root commands For[...]
-
Pagina 21
TANDBERG MPS API User Guide 19 2.1.4 Exposure options By adding an exposure option after the address (XPa t h or SimplePath) expression, the system can be instructed to return only parts of t he information within an element structu re. <root command> <ad dress expression> <exposure option> Supported exposure options: • “-“ [...]
-
Pagina 22
TANDBERG MPS API User Guide 20 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 Request fo r Call 1 element with exposure option ?[...]
-
Pagina 23
TANDBERG MPS API User Guide 21 2.2 The Status-type root commands – xstatus / xhistory The information accessible through the s e comm and s is the exact same information that is available in the corresponding XML docu ments. To get an overview of accessible top-level el ements within a status-type root com mand, type ? or help after the status-ty[...]
-
Pagina 24
TANDBERG MPS API User Guide 22 o XACLI is using indent spaces to present the data structure o XACLI hides instance num ber ( item number in XML ) of an element if there only exist one instance of a given element o A status top level element starts with “ *s ” Example 2.5 shows XML formatting and XACLI formatting for the same statu s el ement, I[...]
-
Pagina 25
TANDBERG MPS API User Guide 23 2.3 The Configuration-type root commands - xconfiguration/xdirectory The information accessible through the s e comm and s is the exact same information that is available in the corresponding XML docu ments. To get an overview of accessible t op-level configurati on elements, type ? or help after the configuration-typ[...]
-
Pagina 26
TANDBERG MPS API User Guide 24 <configuration-type root command> <address expr> ?/help Example 2.7 User wants to configure IP: xconfiguration ip ? *h xConfiguration IP Assignment: <DHCP/Static> *h xConfiguration IP Address: <IPAddr> *h xConfiguration IP SubnetMask: <IPAddr> *h xConfiguration IP Gateway: <IPAddr> [...]
-
Pagina 27
TANDBERG MPS API User Guide 25 Example 2.9 User wants to set IP assignment: xconfiguration ip assignment: static or xconfiguration ip/assignment: static[...]
-
Pagina 28
TANDBERG MPS API User Guide 26 2.4 The Command-type root commands - xcommand To get an overview of the supported commands within a comm and-type root command, type ? or help after the command-type root com mand. <command-type root command> ? Example 2.10 xcommand ? - User Commands - Boot DuoVideoStart MessageBoxDisplay CallAccept DuoVideoStop[...]
-
Pagina 29
TANDBERG MPS API User Guide 27 Example 2.12 xcommand Dial ? *h xCommand Dial Number(r): <S: 0, 30> SubAddress: <S: 0, 10> CallRate: <1xh221/2xh221/64/128/256... Restrict: <On/Off> NetProfile: <1..6> OK NOTE! Required pa rameters are identified by an “(r)” behind the pa rameter name. 2.4.2 Issui ng a com mand A command[...]
-
Pagina 30
TANDBERG MPS API User Guide 28 Sequence notation <command-type root command> <c ommand> <value> <value>... When using this notation the parameter values must be entered in the seq uence as stated in the help text: Example 2.16 xcommand dial 666 10 128 on Combination A combin ation of mark-up notation and seq uence are also s[...]
-
Pagina 31
TANDBERG MPS API User Guide 29 2.5 XML Output - xgetxml As an alternative to the standard XACLI output format, XML format is supported through the root command xgetxml . xgetxml takes an XPath expressio n as parameter and the elements (or complete document) matching the expression will be returned. Example 2.19 xgetxml status/ip <Status> <[...]
-
Pagina 32
TANDBERG MPS API User Guide 30 2.6 Special Commands In addition to the root commands descri bed ab ove, XACLI support a set of root commands that only applies to the Telnet session or RS232 sessio n from where they are issued . This lets the user/control application individually configure the se ssion(s) in use. Supported special comma nds: • xfe[...]
-
Pagina 33
TANDBERG MPS API User Guide 31 Example 2.21 Exposure options are al so supported together with feedback. User only wants to monitor call setup progression. xfeedback register status/call-- OK xcom dial 10.47.15.127 *s Call 1 (status=EstablOut, type=Vtlph, protocol=H323, direction=Outgoing): *s/end *r Result (status=OK): CallRef: 1 LogTag: 3 *r/end [...]
-
Pagina 34
TANDBERG MPS API User Guide 32 *s/end xcom disc *r Result (status=OK): / *r/end OK NO CARRIER *s Call 1 (status=Disconnected, type=NA, protocol=NA, direction=NA): *s/end When conditional XPath expressio ns are used, the system will provide feedback on all elements within the address the first time the condition is true. Example 2.23 User wants to m[...]
-
Pagina 35
TANDBERG MPS API User Guide 33 Rate: 768 Restrict: Off Encryption (status=Off): / Audio (status=Active): Protocol: G722 Rate: 64 Video 1 (status=Active): Protocol: H263+ Resolution: ICIF Rate: 704 Video 2 (status=Inactive): / Data (status=Inactive): / *s/end …suddenly there is a chan ge in audi o protocol: *s Call 1 (status=Synced, type=Vtlph, pr[...]
-
Pagina 36
TANDBERG MPS API User Guide 34 xpreferences detaillevel <1..2> Most information elements acce ssi ble by t he status-type root commands are defined to be level1 information. However there are some info rmation eleme nts which are defined to be level2 information. When reading status information, only the information element s with a detail le[...]
-
Pagina 37
TANDBERG MPS API User Guide 35 <BaudRate item="1">2400</BaudRate> </SerialPort> </Configuration> xpreferences xmlstatusfeedback <on/off> If xmlstatusfeedback is set to on, all status feedback will be retu rned in XML-format instead of the standard XACLI status format. Example 2.26 XACLI-format: *s Call 1 (sta[...]
-
Pagina 38
TANDBERG MPS API User Guide 36 3 API - Configurations This section gives an overview of the Configuration Informatio n available in the Configuration XML documents ( configuration.xm l / directory.xm l ) and the Configuration root commands ( xconfiguration / xdirectory ) of the XACLI interface. All examples are presented using the st andard XACLI f[...]
-
Pagina 39
TANDBERG MPS API User Guide 37 3.1 configuration.xml – xconfiguration AllowIncomingTlphCall AllowIncomingTlphCall: <On/Off> Conference Conference [1..35] Numbers E164Alia s: <E1 64: 0, 31> Conference [1..35] Numbers PRI: <S: 0, 60> Conference [1..35] Numbers H323ID: <S: 0, 50> Conference [1..35] Numbers SIP URI: <S: 0, [...]
-
Pagina 40
TANDBERG MPS API User Guide 38 ConferenceTemplate [1..10] Entry E xitTones : <On/Off> ConferenceTemplate [1..10] WelcomeMessa ge: <On/Off> ConferenceTemplate [1..10] Legacy Level: <0..15> ConferenceTemplate [1..10] DuoVideo : <On/O ff> ConferenceTemplate [1..10] AudioG72 8: <On/Off> ConferenceTemplate [1..10] Casca din[...]
-
Pagina 41
TANDBERG MPS API User Guide 39 <Off/Normal/High> ConferenceTemplate [1..10] OptimalVideoQu ality : <On/Off> ConferenceTemplate [1..10] EncoderS electionPolicy: <BestBitRate/BestVideoStanda rd/Be stResolution> ConferenceTemplate [1..10] Band widthManagement: <Manual/Auto> ConferenceTemplate [1..10] WebSnapshots: <On/ Off&g[...]
-
Pagina 42
TANDBERG MPS API User Guide 40 H323Gatekeeper [1..2 ] Authentication Pass w ord: <S: 0, 50> HTTP HTTP Mode: <On/Off> HTTPS HTTPS Mode: <On/Off> IPProtocol IPProtocol: <IPv4/IPv6/Both> IP IP [1..2] Address: <S: 0, 15> IP [1..2] SubnetMask: <S: 0, 15> IP [1..2] Gateway: <S: 0, 15> IP [1..2] DNS Server [1..5] [...]
-
Pagina 43
TANDBERG MPS API User Guide 41 ISDNInterfaceCard [1..6] ISDN PRI Interface [1..8] MaxChannels: <1..30> ISDNInterfaceCard [1..6] ISDN PRI Interface [1..8] HighChannel: <1..31> ISDNInterfaceCard [1..6] ISDN PRI Interface [1..8] LowChannel: <1..31> ISDNInterfaceCard [1..6] I SDN PRI Interface [1..8] Search: <High/Low> ISDNInter[...]
-
Pagina 44
TANDBERG MPS API User Guide 42 LoS Polarity: <Positive/Negative> LoS Retry: <0..65535> MCU MCU AdditiveRegEnable: <On/Off> MCU H264: <On/Off> MCU H264RCDO: <On/O ff> MediaBoard MediaBoard [1..12] IP Address: <IPAddr> MediaBoard [1..12] IP SubnetMask: <I PAddr> MediaBoard [1..12] IP Gateway: <IPAddr> M[...]
-
Pagina 45
TANDBERG MPS API User Guide 43 QoS [1..2] Precedence Telephony Signalling: <0/1/2/3/4/5/6/7/Auto/Off> QoS [1..2] Precedence VideoTelephony Audio: <0/1/2/3/4/5/6/7/Auto/Off> QoS [1..2] Precedence VideoTelephony Signalling: <0/1/2/3/4/5/6/7/Auto/Off> QoS [1..2] Precedence VideoTelephony Video: <0/1/2/3/4/5/6/7/Auto/Off> QoS [1[...]
-
Pagina 46
TANDBERG MPS API User Guide 44 SingleNumberDialIn SingleNumberDialIn Activ e: <On/Off> SingleNumberDialIn Numbers ISDN: <S: 0, 60> SingleNumberDialIn Numbers IP: <S: 0, 60> SingleNumberDialIn Numbers H323Alias: <E164 : 0, 31> SingleNumberDialIn Numbers H323ID: <S: 0, 50> SingleNumberDialIn Numbers SIP: <S: 0, 60>[...]
-
Pagina 47
TANDBERG MPS API User Guide 45 Default IpConfe rence: < 0..15> TerminalSyncLossTimer: <5..90> GatekeeperAdhocString : <S: 0, 10> TrafficShaping: <On/Off> OutbandDTMF: <On/Off> LanguageAdmin: <S: 0, 3> LanguageGraphic: <S: 0, 3> DefaultConferenceTemplate: <1..10> Telnet Telnet Mode: <On/Off> * Th[...]
-
Pagina 48
TANDBERG MPS API User Guide 46 3.2 directory.xml – xdirectory LocalEntry LocalEntry [1..250] Name: <S: 0, 48> LocalEntry [1.. 250] Numb er: <S: 0, 60> LocalEntry [1.. 250] SecondNumb er: <S: 0, 60> LocalEntry [1.. 250] SubAddre ss : <S: 0, 60> LocalEntry [1.. 250] CallRate: <1xh221/2xh221/64/128/1 92/256/320/3 84/512/76[...]
-
Pagina 49
TANDBERG MPS API User Guide 47 4 API - Commands This section gives an overview of the su pported system Commands. All examples are presented using the st andard XACLI format.[...]
-
Pagina 50
TANDBERG MPS API User Guide 48 4.1 command.xml – xcommand Boot Command used to reboot the syste m. Parameters: None OK Result parameters: None ERROR Result parame ters: • Cause: <1…> Cause code specifying why the comman d wa s not accepted by the system • Description Textual description of the cause code. Example: xcommand boot *r Res[...]
-
Pagina 51
TANDBERG MPS API User Guide 49 • Cause: <1…> Cause code specifying why the comman d wa s not accepted by the system • Description Textual description of the cause code. Example: xcommand callmute call:2 mode:on *r Result (status=OK): *r/end OK CallMuteOutgoing Command used to mute outgoing audio from a specific call. Parameters: • Cal[...]
-
Pagina 52
TANDBERG MPS API User Guide 50 CallMuteVideo Command used to mute incoming video from a spe cific call. Parameters: • Call(r): <1..128> Reference to the call to be muted or unmuted. • Mode(r): <On/Off> Denotes whether video is to be muted or unmuted. OK Result parameters: None ERROR Result parame ters: • Cause: <1…> Cause [...]
-
Pagina 53
TANDBERG MPS API User Guide 51 • EntryExitTones: <On/Off> • LegacyLevel: <0..15> • TelephoneFilter: <On/Off> • FloorToFull: <On/Off> • BandwidthThreshold: <64/128/192/256/320/384/512/76 8/1152/1472/1920> • WebCallListTimeout: <On/Off> • PhoneIndication: <On/Off> • SpeakerIndication: <On/O[...]
-
Pagina 54
TANDBERG MPS API User Guide 52 • AudioG728: <On/Off> • CascadingPreference: <Auto/Ma ster/Slav e> • BillingCode: <S: 0, 16> • CPAutoS witch: <0..60> • NetworkId: <1..32> • ConferenceSelfvie w: <On/Off> • Protect: <On/Off> • TemplateReference: <1..10> • HDEnabled: <On/Off> OK Re[...]
-
Pagina 55
TANDBERG MPS API User Guide 53 • Description Textual description of the cause code. Example: xcommand conferencestart conference:1 *r Result (status=OK): *r/end OK ConferenceStop Command used to stop a conference. All active call s must be disconnected prior to stopping the co nference. Parameters: • Conference(r): <1..35> OK Result param[...]
-
Pagina 56
TANDBERG MPS API User Guide 54 *r/end OK DefaultValuesSet Command used to reset co nfiguratio ns to default values. Parameters: • Level: <1..3> Configurations are divided into three different storage classes. The level parameter den otes that configurations on this level and all levels below are to be reset. OK Result parameters: None ERROR[...]
-
Pagina 57
TANDBERG MPS API User Guide 55 OK DialGroupEntry Command used to dial an entry from th e Grou p Directory. Dialing from the Group Directory makes it possibl e to se t up a MultiSite conference in one operation. Parameters: • Conference(r): <1..35> • GroupEntryId(r): <1.. 16> Reference to the directory entry to be dialed. OK Result p[...]
-
Pagina 58
TANDBERG MPS API User Guide 56 • Cause: <1…> Cause code specifying why the call wa s not accepte d by the system • Description Textual description of the caus e code. DialLocalEntry Command used to dial a number from the locally stored dire cto ry. Parameters: • Conference(r): <1..35> • LocalEntry I d(r): <1..9 9> Refere[...]
-
Pagina 59
TANDBERG MPS API User Guide 57 accepted by the system • Description Textual description of the cause code. Example: xcommand disconnectgwcall gatewaycall:1 *r Result (status=OK): *r/end OK FeedbackDeregiste r Command used to deregist er XML feedback over HTTP(S). Parameters: • ID: <1..3> ID for the registration to deregister. OK Result pa[...]
-
Pagina 60
TANDBERG MPS API User Guide 58 *r/end OK FloorToSite Comm and u sed to assign floor to a specific site in a conference. Parameters: • Conference(r): <1..35> • MCUID(r): <1..191 > M CUID to the MultiSite the site is connected to. • TerminalID(r): <1..191> The site’s terminal id, referenced to the MultiSite it is connected t[...]
-
Pagina 61
TANDBERG MPS API User Guide 59 • GroupEntryId: <1..16> Reference to the Group Directory position the entry is stored. ERROR Result parame ters: • Cause: <1…> Cause code specifying why the comman d wa s not accepted by the system • Description Textual description of the cause code. Example: xcommand groupentryadd name:”The Team[...]
-
Pagina 62
TANDBERG MPS API User Guide 60 • Window(r): <1..16> • CallID(r): <1..176> Call. ERROR Result parame ters: • Cause: <1…> Cause code specifying why the comman d wa s not accepted by the system • Description Textual description of the cause code. LocalEntryAdd Command us ed to add a new entry to the locally stored Directory[...]
-
Pagina 63
TANDBERG MPS API User Guide 61 *r Result (status=OK): *r/end OK OptionKeyAdd Comm and u sed to add option key. Parameters: • Key(r): <S : 0, 90> Opt i on key st ring OK Result parameters: None ERROR Result parame ters: • Cause: <1…> Cause code specifying why the comman d wa s not accepted by the system • Description Textual desc[...]
-
Pagina 64
TANDBERG MPS API User Guide 62 ProtectNumberRemove Command used to remove a prote ct num ber. Parameters: • Conference(r): <1..15> Conferen ce to remove number • NetProfile(r): <2..7> Net Profile to remove • Number(r): <S: 0, 60> Number to remov e OK Result parameters: None ERROR Result parame ters: • Cause: <1…> C[...]
-
Pagina 65
TANDBERG MPS API User Guide 63 5 API - S t atus This section gives an overview of the Status Inform ation available i n the Status XML documents (status.xml / history.xml) and the Status root comma nds (xstatus / xhistory) of the XACLI interface. All examples are presented using the st andard XACLI format.[...]
-
Pagina 66
TANDBERG MPS API User Guide 64 5.1 status.xml – xstatus Call [1..160] Top level attributes: • conferenceRef: 1..9 • direction: Incoming/Outgoing • logTag: 1… Unique number identifying the call. This tag can be used to track the call in the call log ( history.xml / xhisto ry ). • protocol: H320/H323 • status: CallIDLE/Dialing/Alerting/[...]
-
Pagina 67
TANDBERG MPS API User Guide 65 LocalIPAddress: "10.47.9.150:2344" Encryption (status=Off): / RSVP: Off RSVPRate: 0 DynamicRate: 157 TotalPackets: 476674 PacketLoss: 1 Jitter: 10 Video 2 (status=Active): Protocol: H263+ Resolution: XGA Rate: 160 RemoteIPAddress: "" LocalIPAddress: "10.47.9.150:2346" Encryption (status=O[...]
-
Pagina 68
TANDBERG MPS API User Guide 66 Conference [1..40] Top level attributes: • status: NotStarted/Started/Activ e Summary: • Includes references to the calls being con ne cted to the conference • DuoVideo status • Includes information about the pictures gene rated by the MultiSite • Cascading status • MCU Site list • On Air information Exa[...]
-
Pagina 69
TANDBERG MPS API User Guide 67 FarTlphEchoSupression: Normal NetErrorHandling: None IPLRRobustMode: Auto FURBlockSites: Auto FURFilterInterval: 3 HDEnabled: Off VoiceSwitchTimeout: 2 OptimalVideoQuality: On/Off EncoderSelectionPolicy: BestBitRate/BestVideoStandard BandwidthManagement: Auto/Manual WebSnapshots: On/Off AutoAspectRatio4x3: Off *s/end [...]
-
Pagina 70
TANDBERG MPS API User Guide 68 Picture: NA CallRef: None Window 6: Picture: NA CallRef: None OutgoingPicture 3 (name=Duo): Layout (type=NA): / PictureModeActual: Full MCUID: 1 CascadingMode: StandAlone MCUSiteList: Site 1: MCUID: 1 TerminalID: 2 Name: "System1" CallRef: 1 Site 2: MCUID: 1 TerminalID: 3 Name: "System2" CallRef: 2[...]
-
Pagina 71
TANDBERG MPS API User Guide 69 PhoneIndication: On SpeakerIndication: On VideoText: On VideoTextTimeout: 5 ChairControl: Off LectureMode: Off Protect: Off VideoCodingMode: Transcoding SecondaryRate: Off FarTlphEchoSupression: Normal NetErrorHandling: None IPLRRobustMode: Auto FURBlockSites: Auto FURFilterInterval: 3 HDEnabled: Off VoiceSwitchTimeou[...]
-
Pagina 72
TANDBERG MPS API User Guide 70 *s/end H323G atekeepe r [1..2] Top level attributes : • status:Required/Disc overing/ Discovered/Authenticating/ Authenticated/Registering/Regis tered/Rejected/Inactive Summary: • Returns H323Gatekeeper status Examples: *s H323Gatekeeper 1 (status=Inactive): / *s/end *s H323Gatekeeper 1 (status=Registered): Addres[...]
-
Pagina 73
TANDBERG MPS API User Guide 71 Example *s MediaBoard 1: TemperatureCelcius: 30 TemperatureFahrenheit: 86 Description: "" IP: Address: "10.47.9.106" SubnetMask: "255.255.248.0" Gateway: "10.47.8.1" V6: Address 1 (type=NA): "" Address 2 (type=NA): "" Ethernet: MacAddress: "00:50:60:00:E[...]
-
Pagina 74
TANDBERG MPS API User Guide 72 SerialNumber: "44a00003" MainBoard: "113637 MCP 820 System Controller" BootSoftware: "PPCBUG" Used: Total: Conference: 2 Telephony: 0 VideoTelephony: 1 BChanPRI: 0 Bandwidth: 384 Gateway: GatewayCall: 0 BChanPRI: 0 MCU: Conference: 2 Telephony: 0 VideoTelephony: 1 Bandwidth: 384 BChanPRI:[...]
-
Pagina 75
TANDBERG MPS API User Guide 73 Channels 22 (type=BChannel, status=Idle): / Channels 23 (type=BChannel, status=Idle): / Channels 24 (type=BChannel, status=Idle): / Channels 25 (type=BChannel, status=Idle): / Channels 26 (type=BChannel, status=Idle): / Channels 27 (type=BChannel, status=Idle): / Channels 28 (type=BChannel, status=Disconnected): Calli[...]
-
Pagina 76
TANDBERG MPS API User Guide 74 CauseLocation: 2 ChannelCause: 17 ConnectionTime: 0 Channels 26 (type=BChannel, status=Disconnected): CallingNumber: "061336971" CauseLocation: 2 ChannelCause: 17 ConnectionTime: 0 Channels 27 (type=BChannel, status=Disconnected): CallingNumber: "061336971" CauseLocation: 2 ChannelCause: 17 Connect[...]
-
Pagina 77
TANDBERG MPS API User Guide 75 State: RedAlarm *s/end ExternalManager *s ExternalManager: Address: "10.47.1.10" Protocol: URL: "tms/public/external/management/SystemManagementServ ice.asmx" *s/end NTP *s NTP: Address: "127.0.0.1" *s/end SIP *s SIP: Mode: On Interface: Server (status=Active): Address: "10.47.8.88&q[...]
-
Pagina 78
TANDBERG MPS API User Guide 76 URI: "" Registration 21 (status=Inactive): URI: "" Registration 22 (status=Inactive): URI: "" Registration 23 (status=Inactive): URI: "" Registration 24 (status=Inactive): URI: "" Registration 25 (status=Inactive): URI: "" Registration 26 (status=Inactive): U[...]
-
Pagina 79
TANDBERG MPS API User Guide 77 Options *s Options: Option 1: Key: "****" Description: "40 video telephony ports + 16 telephony ports." Option 2: Key: "****" Description: "Advanced Video Option on 40 sites." Option 3: Key: "****" Description: "Encryption on 40 sites." Option 4: / Option 5: [...]
-
Pagina 80
TANDBERG MPS API User Guide 78 Option 52: / Option 53: / Option 54: / Option 55: / Option 56: / Option 57: / Option 58: / Option 59: / Option 60: / Option 61: / Option 62: / Option 63: / Option 64: / *s/end[...]
-
Pagina 81
TANDBERG MPS API User Guide 79 5.2 history.xml – xhistory Call [1..96] Top level attributes: • type: Tlph/Vtlph • protocol: H320/H323/SIP • direction: Incoming/Outgoing • PartOf: Conference/Gate wayCall Summary: • Returns information about discon ne cted calls Examples: *l Call 1 (type=Vtlph, protocol=H323, direction=Outgoing, PartOf=Co[...]
-
Pagina 82
TANDBERG MPS API User Guide 80 5.3 Event.xml – xevent AuthenticationFailure *e AuthenticationFailure: Service: / RemoteIPAddress: / Uptime: / *e/end CallFURErrorAlert *e CallFURErrorAlert: FURAlert: / Rate: / CallRef: / LogTag: / ConferenceRef: / ConferenceLogTag: / *e/end CallMovedFromReception *e CallMovedFromReception: CallRef: / LogTag: / Con[...]
-
Pagina 83
TANDBERG MPS API User Guide 81 Incoming: Audio: TotalPackets: / PacketLoss: / PacketsDropped: / MaxJitter: / Video: TotalPackets: / PacketLoss: / PacketsDropped: / MaxJitter: / *e/end CallSuccessful *e CallSuccessful: CallRef: / LogTag: / ConferenceRef: / ConferenceLogTag: / ServiceType: / Protocol: / Direction: / CallRate: / RemoteNumber: / Encryp[...]
-
Pagina 84
TANDBERG MPS API User Guide 82 *e/end H320Stat istics *e H320 Statist ics: CallRef: / LogTag: / ConferenceRef: / ConferenceLogTag: / Duration: / FramingLoss: Last: / Total: / BondingReSync: Last: / Total: / *e/end SystemActiv ity *e SystemActivi ty : Service: / RemoteIPAddress: / Uptime: / Description: / *e/end[...]