Issues Resolved in Release 3.2.2
23
RN-001037-02 REV03 – 06.2011
DEF23028
When some XML UI objects were show (i.e. TextMenu, ImageMenu), the Line
and Speaker keys are not functional if there was no “Dial” tag involved. Now
the Line and Speaker keys are functional while the phone shows any type of
XML UI object.
DEF23082
6739i: Latin-2 characters were not properly displayed on a softkey label. Now
the default font used for softkey labels fully supports Latin-2 characters.
DEF23129
When the phone sends Register, and the server responds 2000K with XML
body for local mode status, the phone failed to display “localmode” on the UI.
Now the LocalMode status feature is working properly.
DEF23139
When the AastraIPPhoneInputScreen object is sent to the phone, the cursor is
on the Name field and the type of character is capitals (ABC). After the first
character, the character type doesn't change automatically to lowercase (abc).
Now the character type automatically changes to lowercase once the first
character is entered.
DEF24026
The ChangeMode softkey label does not switch automatically to lowercase
(abc) when the mode actually switches from uppercase to lowercase after the
first character has been entered. The ChangeMode softkey label now auto-
matically switches to lowercase once the first character is entered.
DEF23232
6739i: The custom Exit softkey did not work in the XML AastraIPPhoneInput-
Screen UI object with multiple inputs. Now the custom Exit softkey works as
expected.
DEF23512
When a 3-line LCD phone was playing a WAV file, the characters ‘>>’ were not
displayed at the end of the 2nd line on the phone display. Now when the Aas-
traIPPhoneExecute object (with Wav.Play command and a valid WAV file) is
assigned to a key, and the users presses the key, the WAV file starts streaming
and the characters display properly.
DEF24029
When the phone is playing a WAV file, the characters ‘>>’ were incorrectly dis-
played at the end of the first line on the phone UI and the WAV file name was
shown on the second line. Now the WAV file name is on the first line and the
characters ‘>>’ are on the second line.
DEF23618
6739i: When a TextMenu with, for example, 20 elements is displayed with
unitScroll set to ‘no’, if selected item was item 6 (the second item on the sec-
ond page), pressing the up arrow displayed items 2-5 whereas it should have
displayed items 1-4. When the user pressed the down arrow, the UI displayed
items 6-9, whereas it should have displayed items 5-8.
The up and down arrows now behave like a “page up/down” arrow, showing
the first/last non-visible elements on the list. When the user presses the up or
down arrow, they will go to the previous or next page, showing the correct
items.
Issue Number
Description of Fix
