H. 323 Software ip interface Requirements / Feature Specifications compas id 143543 Issue 4 June 02, 2014 John W. Soltes (retired)



Download 4.77 Mb.
Page26/48
Date28.05.2018
Size4.77 Mb.
#51006
1   ...   22   23   24   25   26   27   28   29   ...   48

3.2 Local Procedures




96x1H-IPI.3.2.50: Local procedure security


Approved

No local procedures will be supported except as explicitly specified by this document or by other applicable requirements documents.

Rationale:

The intent of this requirement is to explicitly disallow any local procedures that could compromise operation, security or privacy. ANY UNSPECIFIED LOCAL PROCEDURES IMPLEMENTED FOR DEVELOPMENT OR OTHER PURPOSES SHOULD NOT BE ACTIVE IN ANY EXTERNALLY RELEASED VERSION OF TELEPHONE SOFTWARE!



96x1H-IPI.3.2.80: Softkeys on startup screens


Approved

On telephones that do not have a touchscreen, when button labels are specified on the bottom reserved text line of startup screens, they will be aligned as closely as possible with the corresponding button(s) in the topmost row of physical buttons under the display, and the buttons will be referred to as “softkeys” with the specified labels, even if the buttons have different fixed labels or icons that are used during normal telephone operation. If a label is specified as aligning with the “center” button under the display on a telephone with four “softkeys”, the label will be centered over the middle two buttons and pressing either will invoke the specified procedure.

If a label is specified for even one button in the topmost row of physical buttons under the display, all of the buttons in that row will be treated as “softkeys”. If a “softkey” is pressed for which no procedure is specified, error beep tone will not be generated.



On telephones that have a touchscreen, when button labels are specified on the bottom reserved text line of startup screens, they will be able to be activated via the touchscreen.

Note:

Startup procedures are the procedures specified in this document that occur before the end of the last flowchart in 96x1H-IPI.3.1.100. Startup screens are screens displayed during startup procedures. Interrupt screens are not startup screens.



96x1H-IPI.3.2.90: Button presses during startup


Approved

Buttons pressed during startup procedures will be processed as specified in the following flowchart.



Note:

Startup procedures are the procedures specified in this document that occur before the end of the last flowchart in 96x1H-IPI.3.1.100. Startup screens are screens displayed during startup procedures. Interrupt screens are not startup screens.



96x1H-IPI.3.2.100: Text entry and editing


Approved

The following apply to all text entry procedures that reference this requirement:

  • A cursor will be displayed at the location where the next character will be displayed.

  • As each character is entered, the cursor will move one position to the right if another character position is available on the display line.

  • If the cursor is in the rightmost position on the display and another character is entered, the cursor remains in the same position and the input string is scrolled one character to the left. The prompt on the left side of the display line, if any, remains fully displayed, so if the input string scrolls to the left, the leftmost displayed character of the input string is removed from the display, but not from the input buffer.

  • Pressing the leftmost button on the topmost row of physical buttons under the display (the leftmost softkey on most 96xx telephones or the Contacts button on the 9670G) or the left navigation button (if the telephone has navigation buttons) during data entry will result in a destructive backspace: the most recently entered character will be removed from the display and deleted from the input buffer and, if the entire input string is currently shown on the display, the cursor will be displayed in the deleted character’s former location. If the entire input string is not currently shown on the display, the cursor will remain in the rightmost position, the next character on the left side of the input string will be redisplayed, and the displayed portion of the input string will shift one position to the right. Pressing the leftmost button under the display or the left navigation button when no characters have been entered or when no characters remain after all entered characters have been deleted will result in error beep tone being generated (see AUDIO.210.300 in [7.1-11]) and the cursor will remain where it is.

  • If a button is pressed that would cause the value being entered to become invalid (e.g., longer than the allowed maximum input length), error beep tone will be generated, nothing will be added to the input buffer, and the cursor will remain where it is.

The following apply only to numeric-only text entry procedures that reference this requirement:

  • If a numeric dialpad button is pressed, the character for that digit will be immediately displayed, the digit will be entered into the input buffer and the cursor will be moved to the next character location.

  • If a password is being entered, one asterisk will be displayed for each digit in the input buffer instead of the character for that digit.




The following apply only to alphanumeric text entry procedures that reference this requirement:

  • If multiple characters are specified for a button that is pressed (see the table below), one character will be displayed at a time, replacing the previous character, if any, at the current cursor location in the sequence specified below (from left to right), wrapping back to the beginning of the list if necessary, each time the same button is pressed. If a different button is pressed, or if no button is pressed for one second, the last character displayed will be entered into the input buffer and the cursor will be moved to the next character location. If a different button was pressed, the first character specified for that button will be displayed at the new cursor location.

  • If only one character is specified for a button that is pressed, that character will be immediately displayed, it will be entered into the input buffer, and the cursor will be moved to the next character location.

  • If a password is being entered, one asterisk will be displayed, replacing the displayed character, each time the cursor is moved to the next character location.







Dialpad Button

Characters










1

1@.!”#$%&’()*+,-/:;<=>?[\]^_`{|}~










2

abcABC2










3

defDEF3










4

ghiGHI4










5

jklJKL5










6

mnoMNO6










7

pqrsPQRS7










8

tuvTUV8










9

wxyzWXYZ9










0

0










*

*










#

#




Note:

The above data entry requirements are referenced by 96x1H-IPI.3.1.300 for Access Code entry, by 96x1H-IPI.4.2.210 for VPN user authentication, by 96x1H-IPI.5.1.240 for entry of 802.1X credentials during startup

Note:

These data entry requirements only support left-to-right entry of ASCII characters.




Directory: public -> downloadFile.jsp?file= -> resources -> sites -> AVAYA -> content -> live -> SOLUTIONS
public -> The german unification, 1815-1870
public ->  Preparation of Papers for ieee transactions on medical imaging
public -> Harmonised compatibility and sharing conditions for video pmse in the 7 9 ghz frequency band, taking into account radar use
public -> Adjih, C., Georgiadis, L., Jacquet, P., & Szpankowski, W. (2006). Multicast tree structure and the power law
public -> Duarte, G. Pujolle: fits: a flexible Virtual Network Testbed Architecture
public -> Swiss Federal Institute of Technology (eth) Zurich Computer Engineering and Networks Laboratory
public -> Tr-41. 4-03-05-024 Telecommunications
public -> Chris Young sets 2016 “I’m Comin’ Over” Tour headlining dates
SOLUTIONS -> CM: How to enable 'auto answer' feature

Download 4.77 Mb.

Share with your friends:
1   ...   22   23   24   25   26   27   28   29   ...   48




The database is protected by copyright ©ininet.org 2024
send message

    Main page