Specifications

PA-001011-03-04 Aastra July 2014

 ImageMenu (UI)

 Execute object

 Configuration object

 Status object

Some of these objects also support customizable softkeys that are declared as an independent

object.

The following sections describe the process of creating XML objects for the Aastra SIP phones.

2.3 How does it work?

Leveraging on the IP infrastructure, Aastra has decided to develop the browser capability on the

phone using the HTTP transport protocol but as a direct support of HTML would not be suitable for

the phone horsepower and limited display, the choice has been made to support only XML objects

in the browser.

The Aastra SIP phones support two types of applications:

 Phone-initiated

 Server-initiated

2.3.1 Phone initiated application

The phone issues an HTTP (or HTTPS) GET command to the Web server, waits for the answer,

decodes and displays this answer as any Web browser such as Microsoft Internet Explorer or

Firefox would do as a Web client.

This can be done through a phone custom softkey and from the list of custom features (see chapter

7 for more details).

Figure 2: Aastra IP Phone acting as a client

When the phone performs an HTTP GET, it is a non blocking operation (phone will keep

processing other events) as long as the GET is not requested by an action uri.

2.3.2 Server initiated application

The other type of application would be more used for alerting as an application is pushing an XML

object to the phone. The phone is now acting as a limited Web Server.