Building Cisco IP Phone Services (Part 2) : The Payload

In?Part 1?of this series, we went over basic introduction of Cisco IP Phone services and what kind of XML Objects are available to us within the phone’s firmware vis-à-vis different phone models.

In this part 2 of the series, we will look at the payload that we need to send as a part of the request to execute an HTTP POST action on the phone. We are focusing only on one of the XML objects called Cisco IP Phone Execute because that gives you the most bang for your buck. This is the object that can we can leverage to handle the use cases we had highlighted in the previous post. The table of contents is listed below. You may click directly on the links to jump to relevant sections

1. Introduction
2. Common URIs
3. Use Case
4. Payload

Introduction

The purpose of the Cisco IP Phone Execute object is to deliver single or multiple execution requests to the phone. As these are XML objects, it is no surprise that the payload also has to adhere to XML standards. Each?<CiscoIPPhoneExecute>?tag has a sub tag called?<ExecuteItem>. As the name suggests, whatever you put under this sub tag will be what gets executed on the phone. It can be a URI of an internal phone resource or an explicit URL of an external entity. The basic syntax is given below.

<CiscoIPPhoneExecute>

<ExecuteItem URL="the URL or URI to be executed"/>

</CiscoIPPhoneExecute>

To explore the article in detail, please head over to the following link

Building Cisco IP Phone Services (Part 2) : The Payload