Cisco Cisco TelePresence MCU 4510 Developer's Guide
XML-RPC protocol overview
Cisco TelePresence MCU API 2.8
Page 13 of 120
XML-RPC protocol overview
Message flow
An application external to the MCU can create and manage conferences by sending command
messages to the MCU. For each command sent (provided the message is correctly formatted
according to the
), the MCU responds with a message indicating success or failure.
The response message may also contain any data that was requested.
Authentication
To manage the MCU, the controlling application must authenticate itself as a user with relevant
privileges. Accordingly, each message contains a user name and password (for details see the
Common message elements
Common message elements
CAUTION: Authentication information is sent using plain text and should only be sent
over a trusted network.
over a trusted network.
All calls require administrator privileges.
Example command message
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>