TANDBERG 3.0 - Manual (Page 6)

Copyright © TANDBERG 2008 Reference Guide Version 3.0 rev 3.0 2
2 Protocol overview
2.1 Authentication
In order to manage the device, the controlling application must authenticate itself as a user with relevant
privileges. Accordingly, each message contains a user name and password; see section 2.4.1 for details of the
format. It is worth noting that authentication information is sent using plain text and should only be sent over a
trusted network.
2.2 Message flow
An application can create and manage conferences by sending command messages to the device. For each
command sent (provided the message is correctly formatted according to the XML-RPC spec), the device
responds with a message indicating success or failure. The response message may also contain any data that was
requested.
Command messages are sent in XML format. For example, the following message schedules a conference on an
MCU to begin at 10:45 on 18 February 2005 and last for one hour:
POST /RPC2 HTTP/1.1
User-Agent: Frontier/5.1.2 (WinNT)
Host: 10.2.1.100
Content-Type: text/xml
Content-length: 713
<?xml version="1.0"?>
<methodCall>
<methodName>conference.create</methodName>
<params>
<param>
<value>
<struct>
<member>
<name>authenticationUser</name>
<value>
<string>api_test</string>
</value>
</member>
<member>
<name>authenticationPassword</name>
<value>
<string>123456</string>
</value>
</member>
<member>
<name>conferenceName</name>
<value>
<string>Meeting 1</string>
</value>
</member>
<member>
<name>startTime</name>
<value>
<dateTime.iso8601>20050218T10:45:00</dateTime.iso8601>
</value>
</member>