Manuel d'utilisation / d'entretien du produit 3.0 du fabricant TANDBERG
Aller à la page of 66
Reference guide Codian Remote Management API Document version 3.0 September 2008.
Copyright © TANDBERG 2008 TANDBERG Philip Pedersens vei 20 1366 Lysaker Norway Telephone: +47 67 125 125 Telefax: +47 67 125 234 Video: +47 67 117 777 E-mail: tandberg@tandberg.
Copyright © TANDBERG 2008 Co nt e n t s 1 Introduc tion ................................................................................................................... ................... 1 1.1 HTTP and HTTPS .....................................
Copyright © TANDBERG 2008 6 ISDN Gatewa y methods ........................................................................................................... ...... 38 6.1 Common structures ............................................................
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 1 1 Intr oduc tion This document contains the specification of the TANDBERG Codian Remote Management API, by which it is possible to control several Codian products. This is accomplished via messages sent using the X ML-RPC protocol.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 2 2 Proto co l over vi ew 2.1 Authentication In order to manage the device, the controlling applicat ion must authenticate itself as a user with relevant privileges. Accordingly, each message contai ns a user name and password; see section 2.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 3 <member> <name>durationSeconds</name> <value> <int>3600</int> </value> </member> </struct> </value> </param> </params> </methodCall> If the command was successful, the MCU sends a success re sponse.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 4 </member> <member> <name>faultString</name> <value> <string>duplicate conference name</string>.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 5 2.4.2 Participant identification parameters The following parameters appear in the majority of conference control messages, and identify a specific participant on which operations are to be performed.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 6 3. If there is an enumerateID , the client should call the enumerate method again, with any parameters that are required or desired, and an enumerateID parameter containing the ID returned by the device from the previous call.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 7 Operator Description - Unary minus + Unary plus ! Logical negation ~ Bitwise negation An example filter would be !( expression 1 &&.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 8 3 Messages suppor ted by multiple product t ypes The methods in this section are co mmon to many devices, including vi deo conferencing servers, IP VCR products, ISDN GW products, and IP GW products.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 9 Field Type Comments domainName (optional) String The domain name of this port. nameServer (optional) String a.b.c.d format. nameServerSecondary (optional) String a.b.c.d format. linkStatus Boolean true if the link is up, false if the link is down.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 10 The "log" array consists of structures which contai n the following fields. Field Type Comments time dateTime.iso8601 The time of the last reboot. reason String The reason for the reboot (one of unknown , User requested shutdown or User requested upgrade ).
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 11 Response Type Comments currently configured SIP proxy. conferenceRegistration String This value is only present if the device being queried is an MCU.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 12 Field Type Comments name String Endpoint name. address String IP address. e164 String E.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 13 This method returns: Response Type Comments enumerateID (optional) String The value which should be used in the next call to get the next set of data. If this is omitted, no further data is available from the MCU.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 14 4 C onfer enc e rela ted methods Methods in this section are only implemented on produc ts, such as the Codian MCU 4200 seri es, which act as a video conferencing server. Throughout this sect ion, the term MCU refers to any such device.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 15 Parameter Type Comments reservedVideoPorts (optional) Integar repetition(optional) String One of: none , daily , weekly , everyTwoWeeks or monthly . weekDay(optional) String Must be prese nt if repetition is monthly .
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 16 Parameter Type Comments chairControl (optional) String The chair control setting for the conference.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 17 Parameter Type Comments weekDays String terminationType String terminationDate dateTime.iso8601 numberOfRepeats Integer h239Important Boolean Optional. Sets the h239 channel to be important.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 18 Valid expressions within the enumerate filter are as follows: Expression Type Comments active Boolean True if the conference is active. completed Boolean True if the conference has finished.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 19 Field Type Comments layout is enabled. newParticipantsCustomLayout Boolean True if new participants will use the conference custom layout. private Boolean True if this conference is a private conference.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 20 4.6 conference.streaming.query This returns some details on the current st ate of streaming viewers for a conference. Parameter Type Comments conferenceName String Name of the conference from which streaming information is required.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 21 height (optional) Integer This method will return a fault code of "no such conference" if there is no active conference with the given name, regardless of the presence a configured but inactive conferenc e of that name.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 22 4.9 conference.paneplacement.modify Modifies the pane placement configuration of a particular conferen ce. Parameter Type Comments conferenceName String Name of th e conference to be queried.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 23 Parameter Type Comments (optional) the only protocols th at the API can currently use. participantType (optional) String If present, must be by_address or ad_hoc . Note that if this conference is an ad_hoc conference, this value should also be ad_hoc .
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 24 Parameter Type Comments form suitable for a widescreen (16:9) display. videoTxMaxResolution String One of: cif , 4cif or max .
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 25 4.12 participant.modify Depending on the operationScope parameter below, this call modifies the configuration of a participant (configuredState), or the active state of a pa rticipant in a conference (activeState).
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 26 Parameter Type Comments important (optional) Boolean This setting shoul d not be present if operationScope is "configuredState". Specifies whether this participant is important.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 27 Parameter Type Comments participantProtocol String participantType String newConferenceName String The name of the conference to move the participant to. This will only move an active participant.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 28 Field Type Comments participantType String conferenceName String autoAttendantUniqueId String connectionUniqueId Integer Correspon ds to the uniqueId returned by a conference or autoattendant.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 29 Field Type Comments address String gatewayAddress String The address used to co nnect to the remote endpoint in question.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 30 Field Type Comments audioRxGainMillidB Integer Only pr esent if the audioRxGainMode is fixed .
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 31 Field Type Comments callIdentifier base64 The h323 id of this caller. borderWidth Integer 0 (no border), or 1, 2, or 3 for +1/+2/+3.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 32 Parameter Type Comments verticalPosition (optional) String Specifies where to show the message: “top”, “middle” or “bottom”. Message is always horizontally centered, and omitting this parameter is equivalent to choosing “middle”.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 33 This method returns: Response Type Comments enumerateID(optional) String The value whic h should be used in the next call to get the next set of data. If this is omitted, then no further data is available from the MCU.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 34 5 IP VCR methods Methods in this section are present only where the pro duct supports video recording and playback, such as the Codian IP VCR 2200 Series. Throughout this section, any such product is referred to as an IP VCR.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 35 5.3 recording.delete This method deletes a record ing from the IP VCR. Parameter Type Comments recordingId Integer The recording ID for the recording to delete. This should be the identi fier as returned by recording.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 36 5.5 recording.stop This method stops a recording in progre ss on the IP VCR software version 2.2(1.15) and later. The connection between the IP VCR and the endpoi nt (or endpoints) involved in the call will be dropped.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 37 Field Type Comments pointToPointIncomingPrefix String pointToPointOutgoingPrefix String The folder’s configured point to point recordi ng prefixes. These values are only present with IP VCR software version 2.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 38 6 ISDN Gate way methods The following methods are present on ISDN gate way products, such as the ISDN GW 3220.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 39 6.2 calls.active.enumerate Returns a list of all currently ac tive calls on the ISDN gateway. Parameter Type Comments enumerateID (optional) String An enumer ateID, as specified in section 2.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 40 The calls structure contains the following members: Field Type Comments uniqueId Integer A unique identifier for this call. participantOne Struct participantTwo Struct Participant identification structures, as defined in common structures above.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 41 Response Type Comments the search order is low to high. directoryNumber String The directory number of this port. The bChannels structure has the following members: Field Type Comments id Integer The channel index.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 42 7 IP Gatewa y methods The following methods are present on the IP GW 3500 Series and MSE IP GW 8350 blade.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 43 8 Depreca ted messages These messages were supported in ve rsion 1.0 of the MCU 4200 Series Mana gement API, but have since been superseded. 8.1 system.query This method is deprecated in favour of “device.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 44 Response Type Comments displayName String The name used by the endpoint to identify itself. This may be different to the participantName. Only returned when the participant is connected.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 45 Response Type Comments deferConnection Boolean displayName string The name used by the endpoint to identify itself. This may be different to the participantName. Only available after the participant has connected.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 46 Response Type Comments participant - see appendi x A. This parameter will be present only for participants configured via the API. currentLayout Integer Actual layout in use for the video stream being sent by the MCU to this participant.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 47 9 Relat ed informa tion sources 9.1 system.xml While not strictly part of the XML-RPC API, some in formation can be retrieved from the system.xml file. This can be downloaded via HTTP as the file system.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 48 10 Required user privileges The following table summarises which users are permit ted to perform which remote management operations. Method Valid users device.query Any user with administrator privileges.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 49 11 Fa u l t c o d e s The MCU has a series of fault codes which are given when a fault occurs during the processing of an XML-RPC request.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 50 Fault Code Description correct type, but falls ou tside the valid values; for example an integer is too high or a string value for a protocol contains an invalid protocol.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 51 12 P ar ticipant disc onnec t reasons These are the possible values of the “disconnectRe ason” field in participant informa tion r.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 52 13 Refer enc es [1] XML-RPC, http://www.xmlrpc.com/ [2] RFC 2616, http://www.faqs.org/rfcs/r fc2616.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 53 Appendix A - C onfer enc e lay outs The participant.add and participant.modify methods allow a particul ar layout to be specified for video sent to that participant via the “cpLayout” parameter.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 54 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 1.0 55 Appendix B - Linking confer enc es across MCU s For the purposes of this description, two conferences are said to be "li nked" if there is a bi-direct ional H.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 1.0 56 <string>admin</string> </value> </member> <member> <name>conferenceName</name> <value>.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 1.0 57 B.3 Example message 3 - calling into "linked2" from "linked1" <?xml version="1.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 1.0 58 B.4 Example message 4 - setting the new "linked2" participant to use a full screen view layout <?xml version="1.0"?> <methodCall> <methodName>participant.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 1.0 59 B.5 Message responses The response to each of the ab ove method invocations should be the same normal success indication: <?xml version="1.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 1.0 60 Appendix C - Revision Numbers Note : This feature is available from API version 2.4 onwa rds. An application can determine the API version supported by a device from the apiVersion value returned in the response to a device.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 1.0 61 There are two solutions to this proble m; the first is the listAll parame ter and the second is described in the next section.
Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 1.0 62 Appendix D - HT TP K eep-alives Note : This feature is available fr om API version 2.4 onwards. Another method of reducing the amount of TCP traffic wh en polling the MCU (see Appendix C ) via the API is to use HTTP keep-alives.
Un point important après l'achat de l'appareil (ou même avant l'achat) est de lire le manuel d'utilisation. Nous devons le faire pour quelques raisons simples:
Si vous n'avez pas encore acheté TANDBERG 3.0 c'est un bon moment pour vous familiariser avec les données de base sur le produit. Consulter d'abord les pages initiales du manuel d'utilisation, que vous trouverez ci-dessus. Vous devriez y trouver les données techniques les plus importants du TANDBERG 3.0 - de cette manière, vous pouvez vérifier si l'équipement répond à vos besoins. Explorant les pages suivantes du manuel d'utilisation TANDBERG 3.0, vous apprendrez toutes les caractéristiques du produit et des informations sur son fonctionnement. Les informations sur le TANDBERG 3.0 va certainement vous aider à prendre une décision concernant l'achat.
Dans une situation où vous avez déjà le TANDBERG 3.0, mais vous avez pas encore lu le manuel d'utilisation, vous devez le faire pour les raisons décrites ci-dessus,. Vous saurez alors si vous avez correctement utilisé les fonctions disponibles, et si vous avez commis des erreurs qui peuvent réduire la durée de vie du TANDBERG 3.0.
Cependant, l'un des rôles les plus importants pour l'utilisateur joués par les manuels d'utilisateur est d'aider à résoudre les problèmes concernant le TANDBERG 3.0. Presque toujours, vous y trouverez Troubleshooting, soit les pannes et les défaillances les plus fréquentes de l'apparei TANDBERG 3.0 ainsi que les instructions sur la façon de les résoudre. Même si vous ne parvenez pas à résoudre le problème, le manuel d‘utilisation va vous montrer le chemin d'une nouvelle procédure – le contact avec le centre de service à la clientèle ou le service le plus proche.
