Avaya 4600 Series Application Note download pdf (Page 31)

The Display Push Type

Issue 1 April 2005 31

Successful Push Response

If the phone is in a pushable state, the Push Agent sends the Push Initiator the following

response for all Push request modes and all Push request types:

Normal Priority

When the mode attribute in the <Push> tag is set to normal, the telephone state for the Display

push type is as follows:

● When the telephone is in any of the non-pushable states, the screen currently displayed

continues to be displayed (i.e., the Display push is rejected).

● If the telephone is in the pushable state, the telephone accepts the Push Message and

generates appropriate notification tone(s).

A normal push is accepted when the telephone is in text edit mode in applications other than the

Web. If a non-Web application, such as Speed Dial, is in text-edit mode, then x-Push-Status

204 “Not in Push State: Push Accepted” is sent:

Parameter Status Code Response

HTTP Status Code 200 “OK”

x-Push-Status 200 “Push Message Accepted”

Parameter Status Code Reason Phrase

HTTP Status Code 200 “OK”

x-Push-Status 204 “Not in Push State: Push Accepted”

Use Case Scenario:

Q. What happens when a user is editing or adding an entry on the

Speed Dial screen and a normal priority Display push Message is sent?

A. If an alert is associated with this message, then the alert sounds first.

The pushed content is loaded in the background. The message is not

displayed until the user elects to view it by clicking the Web tab to

launch the Web browser.

1 2 ... 26 27 28 29 30 31 32 33 34 35 36 ... 205 206

No comments

Avaya 4600 Series Application Note Page 31