Cisco Cisco TelePresence MCU 4510 Developer's Guide
XML-RPC protocol overview
Cisco TelePresence MCU API 2.8
Page 15 of 120
<fault>
<value>
<struct>
<member>
<name>faultCode</name>
<value>
<int>2</int>
</value>
</member>
<member>
<name>faultString</name>
<value>
<string>duplicate conference name</string>
</value>
</member>
</struct>
</value>
</fault>
</methodResponse>
The complete list of command messages, their required and optional parameters, and the expected
responses are detailed in the
Unicode support
Parameters in this version of the API can be in ASCII text or Unicode (UTF-8). You can distinguish
between these encodings as follows; if no method is present, ASCII is assumed.
HTTP headers
There are two different ways of specifying Unicode in the HTTP headers; either using "Accept-
Encoding: utf-8"
Encoding: utf-8"
, or modifying the Content-Type header to read "Content-Type:
text/xml; charset=utf-8"
.
XML header
The <?xml> tag is required at the top of each XML file. The API will accept an encoding parameter
for this tag with value UTF-8; that is <?xml version="1.0" encoding="UTF-8"?>.
Common message elements
Authentication
All messages must contain a user name and password as follows:
Parameter
Type
Comments
authenticationUser
String
Name of a user with sufficient privilege for the
operation being performed. The name is case sensitive.
authenticationPassword String
The user’s password. If there is no password stored
against the corresponding username, any supplied
value is accepted.