Avaya 4600 Series Anwendungshinweis PDF herunterladen (Seite 124)

Web Browser for 4610SW, 4620/4620SW, 4621SW, and 4622SW IP Telephones

124 4600 Series IP Telephones Application Programmer Interface (API) Guide

The Web pages resulting from Dialpad button presses are part of the history stack. This is

normal browser behavior.

AIM is re-enabled when the phone goes back on-hook and the current Web page has valid

access keys.

An error beep sounds if the user presses any Dialpad buttons while a new page is loading.

If the accesskey attribute is on the page, then:

● Text Entry/Editing (TE) softkeys do not appear when the user is in AIM. AIM does not have

the default Text Editing softkeys such as alpha, backwards, etc.

● The Top Line help states “Use dial pad for text entry” when the user is in AIM mode. The

message displays when the page first loads and when the user restarts AIM. When AIM is

disabled the message no longer appears. When AIM is restarted, the message reappears.

● The <a> and <anchor> links that would normally appear on the screen are hidden.

● Normal text entry (<input> tags) is prohibited because it cannot co-exist with access keys.

If, by error, regular Text Entry and access keys are on the same page, AIM rules take

precedence. This means when the accesskey attribute appears on a page, the regular text

entry (TE) softkeys do not appear.

● If the user enters the AIM Application, and there is an input field for TE, the field will not get

focus. Focus does not occur, regardless of how many times the user selects the Feature

button next to the TE input field. Since TE is prohibited when access keys are present on a

page, TE does not get focus.

● The server must send back a resulting page with the access keys for each Dialpad button

in the page. Doing so maintains AIM across pages and retains dialpad ownership. The

URLs associated with each accesskey can differ from the starting page in case the proxy

server caches Web pages.

For example, after the page with access keys loads and the user pushes Feature button 2, the

Web server launches the URL:

In the resulting page, the page author can send a different URL to be associated with the same

access key:

1 2 ... 119 120 121 122 123 124 125 126 127 128 129 ... 205 206

Keine Kommentare

Avaya 4600 Series Anwendungshinweis Seite 124