The Push feature allows trusted applications to send their content to Avaya J100 Series IP Phones without any action required from the user.
The Push process is a two-step operation which consists of the following:
-
The Push request to the phone. The Push Initiator (PI), usually a server application, transmits a Push request via an HTTP POST method to the phone’s Push Agent (PA).
-
The Pull request to the trusted server. The Push Agent requests a URI of Push content from a trusted Push server.
The Push content is usually a WML file used by the WML browser or an XML file for setting up an RTP audio stream, displaying a message on the Top line, etc.
The requested Push capability can be one of the following types:
-
audio: the phone receives or transmits a non-call-associated unicast RTP audio stream. The receive or transmit type is specified in the Push Content message.
-
display: the phone downloads and renders a WML file in the browser.
-
receive: the phone receives a non-call-associated unicast RTP audio stream.
-
subscribe: the phone sends a Subscribe message to the server.
-
top line: the phone downloads an .xml file that contains the text to display on the Top line.
-
transmit: the phone transmits a non-call-associated unicast RTP audio stream.
-
multicast: the phone receives a non-call-associated multicast RTP audio stream.
-
phonexml: the phone downloads a .phonexml file.
The Push requests have two priorities, normal and barge-in, which corresponds to the two modes of a Push type: Normal and Barge.
