Aastra 9143i Series Release Notes page 47

Issue Number
ENH18198
User Interface
DEF17996
DEF19981
DEF20386
DEF20679
DEF20694
DEF20817
DEF20928
DEF20954
DEF21016
RN-001029-05 REV 00 – 04.2010
Description of Fix
When the phone played the remote RTP stream on a 183 Call Progress (with
SDP), it was not able to come back to the local ring back tone when it received
a 180 Ringing (without incoming RTP stream).
This is now corrected. The phone now switches to local ringing when it
receives a 180 after a 183.
Intermittently, dial tone was heard in the background during an active call on
Aastra phones.
This is now corrected. A dial tone is no longer heard on the voice path of an
active call.
6730i & 6731i: The phone stopped sending audio on the headset mode after a
user retrieved a call on hold.
This is now corrected.
When a call came into the phone, the display showed the correct calling
number but an incorrect calling name. If the call that came in had a stored
name in the phone's Directory, the name displayed correctly but displayed an
incorrect calling number.
This is now corrected.
After repeated use of the Icom key on the phone, the key stopped working.
This is now corrected.
The phone was not processing a pause in the speeddial correctly if "Suppress
DTMF Playback" was enabled on SCA lines.
This is now corrected. The phone processes the pause correctly.
On some intercom calls, the phone showed "No Lines Available. "
This is now corrected.
XML: The LED for an XML Callers List key did not flash after an incoming call
was received. When the AastraIPPhoneExecute was pushed to the phone
instructing it to turn on the LED, it wouldn't turn on until the user performed
an action on the phone.
This is now corrected. The XML Callers List key now flashes as expected when
an incoming call is received.
The HTTP digest authentication feature was not working correctly. The phone
was not sending a GET request after sending the default username and pass-
word.
This issue is now corrected.
Issues Resolved in Release 2.6
47